oops on plugging in DWL-122

Bug #263309 reported by sam tygier
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Linux sam-desktop 2.6.27-2-generic #1 SMP Thu Aug 28 17:18:43 UTC 2008 x86_64 GNU/Linux

from dmesg (whole thing attached)
[ 3897.883967] Oops: 0002 [1] SMP
[ 3897.883973] CPU 1
[ 3897.883976] Modules linked in: prism2_usb(+) p80211 nls_iso8859_1 nls_cp437 vfat fat af_packet binfmt_misc rfcomm l2cap bluetooth ppdev ipv6 cpufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_conservative cpufreq_stats freq_table pci_slot sbs sbshc wmi video output battery iptable_filter ip_tables x_tables ac sbp2 lp arc4 ecb crypto_blkcipher snd_seq_dummy ath5k snd_seq_oss mac80211 serio_raw snd_seq_midi snd_rawmidi psmouse snd_hda_intel led_class snd_pcm_oss cfg80211 snd_seq_midi_event snd_mixer_oss iTCO_wdt iTCO_vendor_support snd_seq snd_pcm snd_seq_device snd_timer i5000_edac snd edac_core soundcore snd_page_alloc parport_pc parport container tpm_infineon tpm tpm_bios button shpchp pci_hotplug evdev ext3 jbd mbcache sr_mod cdrom ata_generic sg sd_mod crc_t10dif ata_piix usb_storage usbhid hid libusual ahci ohci1394 pata_acpi ieee1394 libata scsi_mod uhci_hcd ehci_hcd dock usbcore e1000e thermal processor fan fbcon tileblit font bitblit softcursor uvesafb cn fuse
[ 3897.884056] Pid: 9633, comm: modprobe Not tainted 2.6.27-2-generic #1
[ 3897.884058] RIP: 0010:[<ffffffffa05670e5>] [<ffffffffa05670e5>] wlan_setup+0x135/0x1b0 [p80211]
[ 3897.884064] RSP: 0018:ffff880058543c88 EFLAGS: 00010292
[ 3897.884066] RAX: 0000000000000010 RBX: ffff88006b908758 RCX: 0000000000000000
[ 3897.884068] RDX: 0000000000000000 RSI: ffffffffa05682aa RDI: ffff88006b908758
[ 3897.884070] RBP: ffff880058543c98 R08: ffff88007f802700 R09: 0000000000000000
[ 3897.884071] R10: 0000000000000001 R11: 0000000000000000 R12: ffff8800754d6800
[ 3897.884073] R13: ffff88005854e000 R14: ffff88006a851000 R15: ffffffffa0580a88
[ 3897.884076] FS: 00007ff1becf26e0(0000) GS:ffff88007f802880(0000) knlGS:0000000000000000
[ 3897.884078] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 3897.884080] CR2: 0000000000000010 CR3: 000000005854d000 CR4: 00000000000006e0
[ 3897.884082] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 3897.884084] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 3897.884086] Process modprobe (pid: 9633, threadinfo ffff880058542000, task ffff8800608ed9c0)
[ 3897.884088] Stack: ffff88006b908400 ffff8800754d4888 ffff880058543cc8 ffffffffa0576a07
[ 3897.884095] ffff88006a851030 0000000000000000 ffff88006a851000 ffffffffa0582360
[ 3897.884098] ffff880058543d18 ffffffffa008e6aa ffff880058543ce8 ffffffffa0580a20
[ 3897.884103] Call Trace:
[ 3897.884115] [<ffffffffa0576a07>] prism2sta_probe_usb+0x47/0x1d0 [prism2_usb]
[ 3897.884134] [<ffffffffa008e6aa>] usb_probe_interface+0xca/0x180 [usbcore]
[ 3897.884144] [<ffffffff80430ba2>] really_probe+0x72/0x1a0
[ 3897.884150] [<ffffffff80430d20>] driver_probe_device+0x50/0x60
[ 3897.884153] [<ffffffff80430dbb>] __driver_attach+0x8b/0x90
[ 3897.884156] [<ffffffff80430d30>] ? __driver_attach+0x0/0x90
[ 3897.884159] [<ffffffff8043032b>] bus_for_each_dev+0x6b/0xa0
[ 3897.884164] [<ffffffff802e328b>] ? kmem_cache_alloc+0x8b/0xd0
[ 3897.884169] [<ffffffff80430a01>] driver_attach+0x21/0x30
[ 3897.884172] [<ffffffff8042fb48>] bus_add_driver+0x1f8/0x270
[ 3897.884177] [<ffffffff80430fb5>] driver_register+0x75/0x170
[ 3897.884191] [<ffffffffa008ea19>] usb_register_driver+0xa9/0x120 [usbcore]
[ 3897.884197] [<ffffffffa0081000>] ? prism2usb_init+0x0/0x5d [prism2_usb]
[ 3897.884202] [<ffffffffa008105b>] prism2usb_init+0x5b/0x5d [prism2_usb]
[ 3897.884206] [<ffffffff8020a255>] do_one_initcall+0x45/0x1a0
[ 3897.884213] [<ffffffff8027c8b5>] sys_init_module+0xb5/0x1f0
[ 3897.884217] [<ffffffff8021288a>] system_call_fastpath+0x16/0x1b
[ 3897.884220]
[ 3897.884221]
[ 3897.884222] Code: 64 56 a0 49 c7 84 24 48 04 00 00 b0 64 56 a0 49 c7 84 24 50 04 00 00 30 65 56 a0 49 c7 84 24 40 01 00 00 c0 ae 56 a0 48 8d 42 10 <f0> 80 4a 10 01 49 c7 84 24 90 04 00 00 c0 65 56 a0 49 c7 84 24
[ 3897.884255] RIP [<ffffffffa05670e5>] wlan_setup+0x135/0x1b0 [p80211]
[ 3897.884260] RSP <ffff880058543c88>
[ 3897.884262] CR2: 0000000000000010
[ 3897.884267] ---[ end trace 92d2204df6b84503 ]---

Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Sam,

Can you comment if this existed with the 2.6.26 kernel available previously for Intrepid?

Revision history for this message
sam tygier (samtygier) wrote :

no oops with 2.6.26
(but please don't go back 2.6.27 make my graphics card work Bug 254583 )

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Heh, ok thanks Sam. I'll hold off on tagging this 'regression-2.6.27' which is what the kernel team will likely use to examine reports when they are deciding to stick with 2.6.27 or not. Thanks.

Revision history for this message
KarlRelton (karllinuxtest-relton) wrote :

This bug is almost certainly the same as that reported and fix-offered upstream. Please see
http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2008-August/003861.html

I get the same Ooops in Intrepid-alpha-5. I suspect applying Richard Kennedy's offered patch will resolve this. Richard is an upstream developer who has contributed to linux-wlan-ng before.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

There is a serious bug which may affect some people subscribed to this report so I wanted to pass along the information. Due to an unresolved bug in the e1000e driver in the 2.6.27 Linux kernel, this driver/kernel should not be used on Intel ethernet hardware supported by the e1000e driver (Intel GigE). Doing so may render your network hardware permanently inoperable.

Older Intel ethernet hardware which uses the e1000 driver is not affected by this; however, some hardware which used the e1000 driver in previous Ubuntu releases, such as hardware that uses a PCI Express bus, has been moved from e1000 to e1000e in the latest kernel releases. If in doubt, do not use this driver/kernel and subscribe to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555 to be notified when the bug is fixed.

Thanks.

Revision history for this message
KarlRelton (karllinuxtest-relton) wrote :

I can confirm the Oops in 2.6.27-4-generic, i.e. the current Intrepid kernel, when the p80211 module is loaded (which happens when Prism based wireless cards are present).

I then compiled the kernel myself, and applied Richard Kennedy's patch from
http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2008-August/003861.html

With this patch applied, the modules load and the card starts functioning.

Without this patch Prism hardware will be rendered useless. Note also 2.6.26 was okay, so this bug ought to have the regression-2.6.27 tag.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I would say comment 7 is questionable, this is a regression whether we like it or not.

Changed in linux:
status: New → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I'll have to kernel team look at the patch posted upstream upstream to consider pulling it in prior to Intrepid's kernel freeze. Thanks.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
KarlRelton (karllinuxtest-relton) wrote :

Upstream has now committed a slightly cleaned up version of the patch in their git tree. I have attached the committed patch here for convenience.

see
http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2008-September/003869.html
http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2008-September/003871.html

Revision history for this message
MaxNegro (maxnegro) wrote :

I can confirm the same problem, after updating to intrepid beta. Kernel 2.6.27-5 Oopses as soon as the prism2 module gets loaded and initialized.

I have a Flybook A33i with 124a:168b AirVast wifi module (it's a sort of "virtual" usb device)

Booting with 2.6.24-1 it works flawlessly.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I've sent an email to the Ubuntu kernel team mailing list with the upstream patch:

https://lists.ubuntu.com/archives/kernel-team/2008-October/003259.html

Changed in linux:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 2.6.27-7.10

---------------
linux (2.6.27-7.10) intrepid; urgency=low

  [ Alexey Starikovskiy ]

  * SAUCE: ACPI: EC: do transaction from interrupt context
    - LP: #277802

  [ Ben Collins ]

  * build/d-i: Change virtio-modules udeb to prio standard

  [ Colin Ian King ]

  * SAUCE: Blacklist IBM 2656 in serio/i8042
    - LP: #21558

  [ Henrik Rydberg ]

  * Revert "SAUCE: applesmc: Add MacBookAir"
  * SAUCE: [PATCH 1/5] hwmon: applesmc: Specified number of bytes to read
    should match actual
  * SAUCE: [PATCH 2/5] hwmon: applesmc: Fix the 'wait status failed: c !=
    8' problem
  * SAUCE: [PATCH 3/5] hwmon: applesmc: Prolong status wait
  * SAUCE: [PATCH 4/5] hwmon: applesmc: Allow for variable ALV0 and ALV1
    package length
  * SAUCE: [PATCH 5/5] hwmon: applesmc: Add support for Macbook Air
  * SAUCE: hwmon: applesmc: Add support for Macbook Pro 4
  * SAUCE: hwmon: applesmc: Add support for Macbook Pro 3
  * SAUCE: hwmon: applesmc: Lighter wait mechanism, drastic improvement

  [ Leann Ogasawara ]

  * Add automatic model setting for Samsung Q45
    - LP: #200210

  [ Tim Gardner ]

  * SAUCE: Correctly blacklist Thinkpad r40e in ACPI
    - LP: #278794
  * SAUCE: Update Wacom tablet driver to 1.49
    - LP: #260675
  * SAUCE: ALPS touchpad for Dell Latitude E6500/E6400
    - LP: #270643
  * SAUCE: Fix Wacom tablet 1.49 porting errors
  * SAUCE: Enable an e1000e Intel Corporation 82567 Gigabit controller
  * SAUCE: Fix Oops in wlan_setup
    - LP: #263309

  [ Upstream Kernel Changes ]

  * ath9k: fix oops on trying to hold the wrong spinlock
  * [Bluetooth] Fix double frees on error paths of btusb and bpa10x drivers
  * [Bluetooth] Add reset quirk for new Targus and Belkin dongles
  * [Bluetooth] Add reset quirk for A-Link BlueUSB21 dongle
  * Revert "ax25: Fix std timer socket destroy handling."
  * ax25: Quick fix for making sure unaccepted sockets get destroyed.
  * netrom: Fix sock_orphan() use in nr_release
  * Revert "V4L/DVB (8904): cx88: add missing unlock_kernel"
  * SLOB: fix bogus ksize calculation
  * net: only invoke dev->change_rx_flags when device is UP
  * tcp: Fix possible double-ack w/ user dma
  * net: Fix netdev_run_todo dead-lock
  * tcp: Fix tcp_hybla zero congestion window growth with small rho and large cwnd.
  * [MIPS] Sibyte: Register PIO PATA device only for Swarm and Litte Sur
  * eeepc-laptop: Fix hwmon interface
  * hwmon: (it87) Prevent power-off on Shuttle SN68PT
  * hwmon: Define sysfs interface for energy consumption register
  * hwmon: (adt7473) Fix some bogosity in documentation file
  * hwmon: (abituguru3) Enable reading from AUX3 fan on Abit AT8 32X
  * hwmon: (abituguru3) Enable DMI probing feature on Abit AT8 32X
  * [CPUFREQ] correct broken links and email addresses
  * SLOB: fix bogus ksize calculation fix
  * Don't allow splice() to files opened with O_APPEND
  * Linux 2.6.27

 -- Tim Gardner <email address hidden> Wed, 08 Oct 2008 21:19:34 -0600

Changed in linux:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.