user
July 10, 2008, 12:37am
#1
Need help.
My USB-Wlan adapter Draytek Vigor 510 as no problem with 10.1 64bit but under 11.0 64 bit usb connect end up with the following dmesg message
usb 1-9: new full speed USB device using ohci_hcd and address 5
usb 1-9: configuration #1 chosen from 1 choice
usb 1-9: New USB device found, idVendor=0967, idProduct=0204
usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
usb 1-9: SerialNumber: 0
prism2usb_init: prism2_usb.o: 0.2.7 Loaded
prism2usb_init: dev_info is: prism2_usb
------------ cut here ]------------
kernel BUG at net/core/dev.c:861!
invalid opcode: 0000 [1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/usb1/1-9/1-9:1.0/bInterfaceClass
CPU 0
Modules linked in: prism2_usb(+) p80211 joydev st ide_disk ide_cd_mod ide_core nls_iso8859_1 nls_cp437 vfat fat usb_storage binfmt_misc snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device iptable_filter ip_tables ip6table_filter ip6_tables x_tables ipv6 af_packet cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 fuse reiserfs loop dm_mod ppdev rtc_cmos parport_pc rtc_core floppy snd_intel8x0 rtc_lib parport snd_ac97_codec k8temp ohci1394 fglrx(P) ac97_bus forcedeth ieee1394 snd_pcm sr_mod snd_timer cdrom snd sg soundcore snd_page_alloc usblp button i2c_nforce2 i2c_core sd_mod ehci_hcd ohci_hcd usbcore edd ext3 mbcache jbd fan pata_amd sata_nv libata scsi_mod dock thermal processor
Pid: 12533, comm: modprobe Tainted: P N 2.6.25.9-0.2-default #1
RIP: 0010:<ffffffff803d5dc1>] <ffffffff803d5dc1>] dev_alloc_name+0x1c/0x4f
RSP: 0018:ffff81005dd8bb48 EFLAGS: 00010246
RAX: ffff81007d5b7000 RBX: ffff81006b926800 RCX: ffff81006b926800
RDX: ffff81006cd30430 RSI: ffffffff886ce631 RDI: 0000000000000000
RBP: ffff81005dd8bb78 R08: ffff81005dd8bba8 R09: ffff81006b926800
R10: 0000000000000000 R11: ffff810070cc2388 R12: ffff81007d5b7000
R13: ffff81007d5b7000 R14: ffff81007d96f000 R15: ffff81006cd30400
FS: 00007ff1c43906f0(0000) GS:ffffffff80630000(0000) knlGS:00000000f740d6d0
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f8b98820000 CR3: 000000005dcca000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 12533, threadinfo ffff81005dd8a000, task ffff810070d1a140)
Stack: ffff81005dd8bb68 ffffffff803defcd ffff81007d5b7000 ffff81006b926800
ffff810076878000 ffff81007d5b7000 ffff81005dd8bba8 ffffffff886ccf86
ffff81005dd8bba8 ffff81006b926800 ffff810076878000 ffffffff886e19ab
Call Trace:
<ffffffff886ccf86>] :p80211:register_wlandev+0x26/0xe8
<ffffffff886e0fee>] :prism2_usb:prism2sta_probe_usb+0x16a/0x234
<ffffffff881021df>] :usbcore:usb_probe_interface+0xe5/0x133
<ffffffff8039fd86>] driver_probe_device+0xc0/0x16e
<ffffffff8039fea4>] __driver_attach+0x70/0xae
<ffffffff8039f5d9>] bus_for_each_dev+0x4f/0x89
<ffffffff8039fbd1>] driver_attach+0x1c/0x1e
<ffffffff8039ee83>] bus_add_driver+0xb7/0x200
<ffffffff803a0057>] driver_register+0x5e/0xde
<ffffffff8810243d>] :usbcore:usb_register_driver+0x80/0xe4
<ffffffff88134056>] :prism2_usb:prism2usb_init+0x56/0x58
<ffffffff8025a854>] sys_init_module+0x1b0a/0x1c47
<ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f
DWARF2 unwinder stuck at system_call_after_swapgs+0x8a/0x8f
Leftover inexact backtrace:
Code: 3e 51 80 31 c0 e8 bf 0e e7 ff 5b 41 5c c9 c3 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 8b bf 50 04 00 00 48 85 ff 75 04 <0f> 0b eb fe 4c 8d 6d d0 4c 89 ea e8 2b d8 ff ff 85 c0 89 c3 78
RIP <ffffffff803d5dc1>] dev_alloc_name+0x1c/0x4f
RSP <ffff81005dd8bb48>
— end trace b4e62d6301bf8b45 ]—
kernel
2.6.25.9-0.2-default #1 SMP 2008-06-28 00:00:07 +0200 x86_64 x86_64 x86_64 GNU/Linux
after connecting usb wlan adapter
lsusb command didn’t come back
tryed ndiswrapper but module can’t be created.
Any hint to bring it up again as it was under 10.1
thanks
Thorsten
fischt wrote:
> Need help.
>
> My USB-Wlan adapter Draytek Vigor 510 as no problem with 10.1 64bit but
> under 11.0 64 bit usb connect end up with the following dmesg message
>
> usb 1-9: new full speed USB device using ohci_hcd and address 5
> usb 1-9: configuration #1 chosen from 1 choice
> usb 1-9: New USB device found, idVendor=0967, idProduct=0204
> usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
> usb 1-9: SerialNumber: 0
> prism2usb_init: prism2_usb.o: 0.2.7 Loaded
> prism2usb_init: dev_info is: prism2_usb
> ------------ cut here ]------------
> kernel BUG at net/core/dev.c:861!
> invalid opcode: 0000 [1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:02.0/usb1/1-9/1-9:1.0/bInterfaceClass
> CPU 0
> Modules linked in: prism2_usb(+) p80211 joydev st ide_disk ide_cd_mod
> ide_core nls_iso8859_1 nls_cp437 vfat fat usb_storage binfmt_misc
> snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device iptable_filter
> ip_tables ip6table_filter ip6_tables x_tables ipv6 af_packet
> cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8
> fuse reiserfs loop dm_mod ppdev rtc_cmos parport_pc rtc_core floppy
> snd_intel8x0 rtc_lib parport snd_ac97_codec k8temp ohci1394 fglrx(P)
> ac97_bus forcedeth ieee1394 snd_pcm sr_mod snd_timer cdrom snd sg
> soundcore snd_page_alloc usblp button i2c_nforce2 i2c_core sd_mod
> ehci_hcd ohci_hcd usbcore edd ext3 mbcache jbd fan pata_amd sata_nv
> libata scsi_mod dock thermal processor
> Pid: 12533, comm: modprobe Tainted: P N 2.6.25.9-0.2-default #1
This is a kernel bug; however, your loading of the Nvidia module fglpx has
“tainted” the kernel, which means that no kernel developer will even look at the
problem. The reason is that when you load a driver that has not been seen by the
Linux experts, its bugs could show up anywhere in the kernel. In the past, a lot
of time has been wasted looking for bugs only to find that the vendor’s driver
caused it. That doesn’t happen anymore. If you can reproduce the error using the
open-source video driver, then you can post this dump to the Linux Kernel
Mailing List.
Larry
> RIP: 0010:<ffffffff803d5dc1>] <ffffffff803d5dc1>]
> dev_alloc_name+0x1c/0x4f
> RSP: 0018:ffff81005dd8bb48 EFLAGS: 00010246
> RAX: ffff81007d5b7000 RBX: ffff81006b926800 RCX: ffff81006b926800
> RDX: ffff81006cd30430 RSI: ffffffff886ce631 RDI: 0000000000000000
> RBP: ffff81005dd8bb78 R08: ffff81005dd8bba8 R09: ffff81006b926800
> R10: 0000000000000000 R11: ffff810070cc2388 R12: ffff81007d5b7000
> R13: ffff81007d5b7000 R14: ffff81007d96f000 R15: ffff81006cd30400
> FS: 00007ff1c43906f0(0000) GS:ffffffff80630000(0000)
> knlGS:00000000f740d6d0
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00007f8b98820000 CR3: 000000005dcca000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 12533, threadinfo ffff81005dd8a000, task
> ffff810070d1a140)
> Stack: ffff81005dd8bb68 ffffffff803defcd ffff81007d5b7000
> ffff81006b926800
> ffff810076878000 ffff81007d5b7000 ffff81005dd8bba8 ffffffff886ccf86
> ffff81005dd8bba8 ffff81006b926800 ffff810076878000 ffffffff886e19ab
> Call Trace:
> <ffffffff886ccf86>] :p80211:register_wlandev+0x26/0xe8
> <ffffffff886e0fee>] :prism2_usb:prism2sta_probe_usb+0x16a/0x234
> <ffffffff881021df>] :usbcore:usb_probe_interface+0xe5/0x133
> <ffffffff8039fd86>] driver_probe_device+0xc0/0x16e
> <ffffffff8039fea4>] __driver_attach+0x70/0xae
> <ffffffff8039f5d9>] bus_for_each_dev+0x4f/0x89
> <ffffffff8039fbd1>] driver_attach+0x1c/0x1e
> <ffffffff8039ee83>] bus_add_driver+0xb7/0x200
> <ffffffff803a0057>] driver_register+0x5e/0xde
> <ffffffff8810243d>] :usbcore:usb_register_driver+0x80/0xe4
> <ffffffff88134056>] :prism2_usb:prism2usb_init+0x56/0x58
> <ffffffff8025a854>] sys_init_module+0x1b0a/0x1c47
> <ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f
> DWARF2 unwinder stuck at system_call_after_swapgs+0x8a/0x8f
>
> Leftover inexact backtrace:
>
>
>
> Code: 3e 51 80 31 c0 e8 bf 0e e7 ff 5b 41 5c c9 c3 55 48 89 e5 41 55 41
> 54 49 89 fc 53 48 83 ec 18 48 8b bf 50 04 00 00 48 85 ff 75 04 <0f> 0b
> eb fe 4c 8d 6d d0 4c 89 ea e8 2b d8 ff ff 85 c0 89 c3 78
> RIP <ffffffff803d5dc1>] dev_alloc_name+0x1c/0x4f
> RSP <ffff81005dd8bb48>
> — end trace b4e62d6301bf8b45 ]—
>
> kernel
> 2.6.25.9-0.2-default #1 SMP 2008-06-28 00:00:07 +0200 x86_64 x86_64
> x86_64 GNU/Linux
>
> after connecting usb wlan adapter
> lsusb command didn’t come back
>
> tryed ndiswrapper but module can’t be created.
>
> Any hint to bring it up again as it was under 10.1
>
> thanks
> Thorsten
>
>
Fischt:
See also the discussion on this thread:
Dlink DLW 121 - openSUSE Forums
user
July 11, 2008, 12:04am
#4
Thanks,
I’ll try the open source package.
user
July 11, 2008, 8:41pm
#5
I now reproduce it with radeon driver and unloaded fglrx module.
hub 2-0:1.0: unable to enumerate USB device on port 9
usb 1-9: new full speed USB device using ohci_hcd and address 4
usb 1-9: configuration #1 chosen from 1 choice
usb 1-9: New USB device found, idVendor=0967, idProduct=0204
usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
usb 1-9: SerialNumber: 0
prism2usb_init: prism2_usb.o: 0.2.7 Loaded
prism2usb_init: dev_info is: prism2_usb
------------ cut here ]------------
kernel BUG at net/core/dev.c:861!
invalid opcode: 0000 [1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/usb1/1-9/1-9:1.0/bInterfaceClass
CPU 0
Modules linked in: prism2_usb(+) p80211 binfmt_misc snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device iptable_filter ip_tables ip6table_filter ip6_tables x_tables ipv6 af_packet cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 fuse reiserfs loop dm_mod ppdev snd_intel8x0 rtc_cmos rtc_core parport_pc rtc_lib parport floppy snd_ac97_codec ohci1394 k8temp ac97_bus ieee1394 forcedeth sr_mod snd_pcm cdrom snd_timer sg snd soundcore snd_page_alloc usblp i2c_nforce2 i2c_core button sd_mod ehci_hcd ohci_hcd usbcore edd ext3 mbcache jbd fan pata_amd sata_nv libata scsi_mod dock thermal processor [last unloaded: fglrx]
Pid: 5455, comm: modprobe Tainted: P N 2.6.25.9-0.2-default #1
RIP: 0010:<ffffffff803d5dc1>] <ffffffff803d5dc1>] dev_alloc_name+0x1c/0x4f
RSP: 0018:ffff810075ce1b48 EFLAGS: 00010246
RAX: ffff81006fcc2800 RBX: ffff810071d56c00 RCX: ffff810071d56c00
RDX: ffff810071d56430 RSI: ffffffff88236631 RDI: 0000000000000000
RBP: ffff810075ce1b78 R08: ffff810075ce1ba8 R09: ffff810071d56c00
R10: 0000000000000000 R11: ffff81007dc58308 R12: ffff81006fcc2800
R13: ffff81006fcc2800 R14: ffff81007d9d0000 R15: ffff810071d56400
FS: 00007f6b304076f0(0000) GS:ffffffff80630000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f6b3042a000 CR3: 000000007d94e000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 5455, threadinfo ffff810075ce0000, task ffff81006fd3c540)
Stack: ffff810075ce1b68 ffffffff803defcd ffff81006fcc2800 ffff810071d56c00
ffff810074974000 ffff81006fcc2800 ffff810075ce1ba8 ffffffff88234f86
ffff810075ce1ba8 ffff810071d56c00 ffff810074974000 ffffffff882499ab
Call Trace:
<ffffffff88234f86>] :p80211:register_wlandev+0x26/0xe8
<ffffffff88248fee>] :prism2_usb:prism2sta_probe_usb+0x16a/0x234
<ffffffff881021df>] :usbcore:usb_probe_interface+0xe5/0x133
<ffffffff8039fd86>] driver_probe_device+0xc0/0x16e
<ffffffff8039fea4>] __driver_attach+0x70/0xae
<ffffffff8039f5d9>] bus_for_each_dev+0x4f/0x89
<ffffffff8039fbd1>] driver_attach+0x1c/0x1e
<ffffffff8039ee83>] bus_add_driver+0xb7/0x200
<ffffffff803a0057>] driver_register+0x5e/0xde
<ffffffff8810243d>] :usbcore:usb_register_driver+0x80/0xe4
<ffffffff88134056>] :prism2_usb:prism2usb_init+0x56/0x58
<ffffffff8025a854>] sys_init_module+0x1b0a/0x1c47
<ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f
DWARF2 unwinder stuck at system_call_after_swapgs+0x8a/0x8f
Leftover inexact backtrace:
Code: 3e 51 80 31 c0 e8 bf 0e e7 ff 5b 41 5c c9 c3 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 8b bf 50 04 00 00 48 85 ff 75 04 <0f> 0b eb fe 4c 8d 6d d0 4c 89 ea e8 2b d8 ff ff 85 c0 89 c3 78
RIP <ffffffff803d5dc1>] dev_alloc_name+0x1c/0x4f
RSP <ffff810075ce1b48>
--- end trace 537ae3649d99c763 ]---
I’ll send it to kernel mailing list as well as suggested above.