Bug 13524
| Summary: | Disconnecting Huawei E169 causes kernel oops | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Clemens Eisserer (linuxhippy) |
| Component: | Serial | Assignee: | Russell King (rmk) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | domen, stern, wl |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
|
Description
Clemens Eisserer
2009-06-12 21:51:30 UTC
Just a me-too, with Huawei E160. $ uname -a Linux river 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 06:42:43 UTC 2009 x86_64 Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz GenuineIntel GNU/Linux BUG: unable to handle kernel paging request at 000000000357d181 IP: [<ffffffffa015baa4>] usb_kill_urb+0x14/0xc0 [usbcore] PGD 7dc80067 PUD 7ddc7067 PMD 0 Oops: 0000 [#1] PREEMPT SMP last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/uevent CPU 0 Modules linked in: vboxnetflt vboxdrv ati_remote2 ext2 cbc loop i915 drm i2c_algo_bit ppp_deflate zlib_deflate zlib_inflate bsd_comp ppp_async ipv6 ppp_generic slhc usbhid hid aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod snd_hda_codec_realtek option snd_hda_intel irtty_sir snd_seq_oss usbserial snd_hda_codec snd_seq_midi_event snd_seq snd_seq_device usb_storage sir_dev snd_pcm_oss snd_mixer_oss snd_hwdep snd_pcm irda i2c_i801 iTCO_wdt iTCO_vendor_support ppdev snd_timer uhci_hcd ehci_hcd crc_ccitt i2c_core pcspkr sg parport_pc snd usbcore r8169 mii intel_agp lp parport soundcore snd_page_alloc thermal processor evdev fan button battery ac rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sd_mod ata_generic ata_piix pata_acpi libata scsi_mod [last unloaded: kvm] Pid: 2848, comm: pppd Not tainted 2.6.29-ARCH #1 To Be Filled By O.E.M. RIP: 0010:[<ffffffffa015baa4>] [<ffffffffa015baa4>] usb_kill_urb+0x14/0xc0 [usbcore] RSP: 0018:ffff88007a249d58 EFLAGS: 00010206 RAX: 0000000100000000 RBX: 000000000357d139 RCX: 0000000000000001 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000357d139 RBP: 0000000000000008 R08: ffff88007de11120 R09: 0000000000000000 R10: 2222222222222222 R11: 2222222222222222 R12: ffff88007a001800 R13: ffff88007aec2c00 R14: ffff88007dd38a28 R15: ffffffffa02a7ca0 FS: 00007fcfe87466f0(0000) GS:ffffffff8067a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000357d181 CR3: 000000007a025000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process pppd (pid: 2848, threadinfo ffff88007a248000, task ffff88007a1f4800) Stack: 2222222222222222 ffff88007aebb8b0 ffff88007dd38a28 0000000000000246 ffff88007dd389c0 ffff88007aebb800 ffff88007aebb800 0000000000000008 ffff88007a001800 ffffffffa02a2841 ffff88007aebb800 ffff88007a001800 Call Trace: [<ffffffffa02a2841>] ? option_close+0x81/0x100 [option] [<ffffffffa02744bf>] ? serial_close+0x1df/0x210 [usbserial] [<ffffffff803c4962>] ? tty_release_dev+0x162/0x5a0 [<ffffffff802d9b7d>] ? vfs_ioctl+0x1d/0xb0 [<ffffffff803c4db1>] ? tty_release+0x11/0x20 [<ffffffff802cbdd2>] ? __fput+0xc2/0x210 [<ffffffff802c869b>] ? filp_close+0x5b/0x90 [<ffffffff802c8784>] ? sys_close+0xb4/0x120 [<ffffffff8020c6aa>] ? system_call_fastpath+0x16/0x1b Code: a0 e8 51 d8 0f e0 48 83 c4 38 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 53 48 89 fb 48 83 ec 30 48 85 ff 0f 84 97 00 00 00 <48> 83 7f 48 00 0f 84 8c 00 00 00 48 83 7f 50 00 0f 84 81 00 00 RIP [<ffffffffa015baa4>] usb_kill_urb+0x14/0xc0 [usbcore] RSP <ffff88007a249d58> CR2: 000000000357d181 ---[ end trace 12a69bdddb01d275 ]--- Seems like this patch (merged after .30 release) fixes it: USB: usb-serial: replace shutdown with disconnect, release Alan Stern [Tue, 2 Jun 2009 15:53:55 +0000 (11:53 -0400)] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f9c99bb8b3a1ec81af68d484a551307326c2e933 So far no oopses here. Clemens, can you confirm this, please? I can't try, because as soon as I try to connect I get a hard lockup: http://bugzilla.kernel.org/show_bug.cgi?id=13601 On Fri, 12 Jun 2009 21:51:31 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=13524 Alan has a patch, which worked for Domen: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f9c99bb8b3a1ec81af68d484a551307326c2e933 But that patch a) doesn't have cc:stable in its changelog, b) seems appropriate for -stable and c) is pretty damn big. What should we do? On Mon, Jun 22, 2009 at 02:49:19PM -0700, Andrew Morton wrote: > On Fri, 12 Jun 2009 21:51:31 GMT > bugzilla-daemon@bugzilla.kernel.org wrote: > > > http://bugzilla.kernel.org/show_bug.cgi?id=13524 > > Alan has a patch, which worked for Domen: > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f9c99bb8b3a1ec81af68d484a551307326c2e933 > > But that patch a) doesn't have cc:stable in its changelog, b) seems > appropriate for -stable and c) is pretty damn big. > > What should we do? It was going to be submitted to -stable after it was determined to fix the problem, right Alan? thanks, greg k-h Yep. See also bug #13472. Do you think it has gotten enough testing yet? There hasn't been much feedback. Maybe that's a good sign. FWIW, since I'm using the mentioned patch ( http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f9c99bb8b3a1ec81af68d484a551307326c2e933 ), there have been no more oopses; tried plugging it out/in, suspend to ram etc. Is there a way to get these folks to test it? http://www.kerneloops.org/guilty.php?guilty=option_close&version=2.6.30-release&start=1998848&end=2031615&class=oops I have similar issues, this time with 2.6.31-rc4 (as provided by openSuSE) and model E220. I booted three times to start umtsmon (version 0.9.50-20081117) as root, and it never worked; it always hangs after displaying installing GUI SIGABRT handler The first time pressing ^C to abort umtsmon works, the second time starting umtsmon and quitting with ^C made the kernel always crash with blinking LEDs, and I never got any message in /var/log/messages. I had to revert to an older kernel (2.6.27 in my case since this is what I have on my openSuSE 11.1 DVD). Has the abovementioned patch been integrated into 2.6.31? Does everything now work okay with the latest 2.6.30.stable release? Yes, für me 2.6.30 releases seem to be ok, however I've experienced other problems in 2.6.31.rc2/rc5 http://bugzilla.kernel.org/show_bug.cgi?id=13906 Then this bug report can be closed. |