Bug 236719
| Summary: | Nokia phone causes BUG from usbnet probe | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Bryn M. Reeves <bmr> | ||||||||
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 5.0 | CC: | cyan_00391, pasi.sainio, pkuutn, poelstra, tuju, wtogami | ||||||||
| Target Milestone: | --- | Keywords: | OtherQA | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | RHBA-2008-0314 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-05-21 14:42:29 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | 228231 | ||||||||||
| Bug Blocks: | 246139, 296411, 372911, 420521, 422431, 422441 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Bryn M. Reeves
2007-04-17 11:09:39 UTC
Created attachment 185491 [details]
Test patch 2 - zero the inftdata
I think this has a better chance to help, because the patch I mentioned in the
other bug did not change the path in this specific case. The problem is in
calling the disconnect from within the probe when the driver is unbound from
the interface.
Please try the kernel 2.6.18-44.el5bz236719.1 from http://people.redhat.com/zaitcev/ftp/236719/ Hi Pete, have a report that they're seeing a crash on removal of the device with 2.6.18-44.el5bz236719.1 - they've given me a reference to a kernel.org bz that apparently resolves it for them: http://bugzilla.kernel.org/show_bug.cgi?id=7201#c19 kernel.org bz is down right now, or I'd paste it in here directly. Created attachment 213261 [details]
Daniel's rndis_host patch from 2.6.20
oops reported to be fixed by the patch in comment #5 Memory for crash kernel (0x0 to 0x0) notwithin permissible range <FF>mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x2000000 mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x2000000 mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x2000000 rndis_host 2-1:1.12: RNDIS init failed, -32 rndis_host: probe of 2-1:1.12 failed with error -32 BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: f8df7776 *pde = 3dc44067 Oops: 0000 [#1] SMP last sysfs file: /class/net/eth0/carrier Modules linked in: rndis_host cdc_ether usbnet cdc_acm thinkpad(U) autofs4 hidp rfcomm l2cap bluetooth sunrpc cisco_ipsec(U) arc4 ieee80211_crypt_wep ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink ipt_LOG xt_limit iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables cpufreq_ondemand video sbs ibm_acpi backlight i2c_e c button battery asus_acpi ac radeon drm ipv6 lp snd_intel8x0m ata_piix libata scsi_mod snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_se q_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc parport_pc serio_raw parport ipw2100 ieee80211 e1000 i2c_i801 ieee80211_crypt pcspkr i2c_core cast6 de s blowfish aes_i586 dm_crypt dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd CPU: 0 EIP: 0060:[<f8df7776>] Tainted: P VLI EFLAGS: 00010202 (2.6.18-44.el5bz236719.1 #1) EIP is at usbnet_disconnect+0x2f/0x89 [usbnet] eax: 00000000 ebx: e7a2c400 ecx: 0000000d edx: f8df7747 esi: ea6c9800 edi: ee6c7c00 ebp: ee6c7c58 esp: f7fb1ed8 ds: 007b es: 007b ss: 0068 Process khubd (pid: 108, ti=f7fb1000 task=f7fb0aa0 task.ti=f7fb1000) Stack: ea6c9800 f8f03540 f8f03570 ee6c7c58 c057b253 ea6c988c ea6c9814 c054baa2 ea6c9814 ea6c9814 c0692d40 c054bc9c 00000000 c054b47f ea6c9800 ee6c7c00 ea6c9814 c054a5bf ea6c9800 ee6c7c00 0000000d ea6c9814 c0579bd7 ee6c7eb8 Call Trace: [<c057b253>] usb_unbind_interface+0x34/0x6a [<c054baa2>] __device_release_driver+0x5a/0x79 [<c054bc9c>] device_release_driver+0x1c/0x2b [<c054b47f>] bus_remove_device+0x78/0x8a [<c054a5bf>] device_del+0xe5/0x12b [<c0579bd7>] usb_disable_device+0x62/0xc3 [<c0576b56>] usb_disconnect+0x76/0xd0 [<c057766f>] hub_thread+0x325/0x979 [<c0436025>] autoremove_wake_function+0x0/0x2d [<c057734a>] hub_thread+0x0/0x979 [<c0435f59>] kthread+0xc0/0xeb [<c0435e99>] kthread+0x0/0xeb [<c0405c3b>] kernel_thread_helper+0x7/0x10 ======================= Code: c6 53 8b 98 14 01 00 00 c7 80 14 01 00 00 00 00 00 00 85 db 74 6a 8b b8 88 00 00 00 83 ef 58 f6 83 94 00 00 00 02 74 27 8b 43 04 <ff> 30 8d 47 04 50 8b 47 30 ff 70 08 8b 86 10 01 00 00 ff 30 ff EIP: [<f8df7776>] usbnet_disconnect+0x2f/0x89 [usbnet] SS:ESP 0068:f7fb1ed8 <0>Kernel panic - not syncing: Fatal exception Unfortunately, the patch referenced by the comment #5 is exactly the one already applied to 2.6.18-44.el5bz236719.1. So we cannot trust what they say about any patches fixing this or that, but at least they've captured the trace. I only wish they captured the COMPLETE dmesg (but for all that's sacred please attache complete dmesgs instead of dropping them in the comments). I've stated that when it crashed, it did not crash on fc6 after it got updated. This have been initially found by fedora users, studied and fixed in both fc kernel and kernel.org. That capture has been taken from ttyS0, that's all what came there. Created attachment 247231 [details]
Test patch 3 - same as Daniels this time
I think I understand what is going on. My comment #7 was incorrect. My patch is not the same as patch in comment #5, and is broken. But I saw what I expected to see and not what actually is. I'm sorry. I have built a new test kernel 2.6.18-44.el5bz236719.2, please give it a try. http://people.redhat.com/zaitcev/ftp/236719/ This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Nov 13 15:05:06 x2 kernel: usb 4-1.3.1.3: new full speed USB device using ehci_hcd and address 8 Nov 13 15:05:06 x2 kernel: usb 4-1.3.1.3: configuration #1 chosen from 1 choice Nov 13 15:05:07 x2 kernel: cdc_acm 4-1.3.1.3:1.10: ttyACM0: USB ACM device Nov 13 15:05:07 x2 kernel: usbcore: registered new driver cdc_acm Nov 13 15:05:07 x2 kernel: drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters Nov 13 15:05:07 x2 kernel: usbcore: registered new driver cdc_ether Nov 13 15:05:07 x2 kernel: rndis_host 4-1.3.1.3:1.12: RNDIS init failed, -32 Nov 13 15:05:07 x2 kernel: rndis_host: probe of 4-1.3.1.3:1.12 failed with error -32 Nov 13 15:05:07 x2 kernel: usbcore: registered new driver rndis_host Nov 13 15:05:29 x2 kernel: usb 4-1.3.1.3: USB disconnect, address 8 Nov 13 15:05:29 x2 kernel: usb 4-1.3.1.3: new full speed USB device using ehci_hcd and address 9 Nov 13 15:05:30 x2 kernel: usb 4-1.3.1.3: device not accepting address 9, error -32 but didn't crash this time. # uname -a Linux x2.y.com 2.6.18-44.el5bz236719.2 #1 SMP Sat Nov 3 03:05:29 EDT 2007 i686 i686 i386 GNU/Linux Note that this is tainted kernel with commercial product, but I'd make a guess that it has nothing to do with this issue and we saw the same symptoms in fedora and it was also successfully fixed there. Have not run tests does the interface actually work (nor the ndis stuff). But i guess that's a another story then. Thanks, I would call this resolved. In case anyone is interested, -32 is a so-called "stall" response. It means that the firmware is unwilling to perform the command, but it did not crash. It is a normal reply if something is not right with the parameters. Perhaps the phone does not implement RNDIS correctly but happens to work with Windows, or it's how the phone interlocks between ACM and RNDIS modes. Try to blacklist cdc_acm, see if the issue goes away. in 2.6.18-61.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot1--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot3--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot4--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Tried with http://people.redhat.com/dzickus/el5/90.el5/i686/kernel-2.6.18-90.el5.i686.rpm and can't reproduce it anymore (although can't remember what the exact steps were a year ago). I guess it's fixed now. thanks Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot6--available now on partners.redhat.com. We are nearing GA for 5.2 so please test and confirm that your issue is fixed ASAP. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot7--available now on partners.redhat.com. We are nearing GA for 5.2--this is the last opportunity to test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0314.html |