[Bug 548265] New: Killswitch on some (most? all?) Asus EeePC models causes immediate kernel freeze

newer
[Bug 561177] New: Module ip_set...

older
[Bug 565871] New: YaST2 uses Gnome...

bugzilla_noreply＠novell.com

19 Oct 2009 19 Oct '09

22:31

http://bugzilla.novell.com/show_bug.cgi?id=548265 Summary: Killswitch on some (most? all?) Asus EeePC models causes immediate kernel freeze Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs@forge.provo.novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- Created an attachment (id=323133) --> (http://bugzilla.novell.com/attachment.cgi?id=323133) My asus eee pc 1000h hardware User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 I tested it on an 1000h model. Kill switch is Fn+F2. Scancode when pressing: 0xe0 0x73. Scancode when releasing: 0xe0 0xf3. When the WiFi card is associated with an AP and I press the kill switch, the kernel freezes immediately, so I was unable to find out why. If I disassociate my wireless card (e.g. by disabling (and the re-enabling but not connecting, if I want so) wireless from knetworkmanager) before activating the kill switch, the kernel won't hang. Possibly the same bug at ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/420363 Reproducible: Always Steps to Reproduce: 1. Boot 32bit 11.2 rc1 kde on an asus eeepc 1000h 2. enable wireless 3. connect to a wireless AP 4. disable wireless by the kill switch Actual Results: The kernel hangs immediately. Expected Results: Wireless should detach from the AP and go into down state without crashing. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

21 Oct 21 Oct

14:23

New subject: [Bug 548265] Killswitch on some (most? all?) Asus EeePC models causes immediate kernel freeze

http://bugzilla.novell.com/show_bug.cgi?id=548265 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER- -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14 Dec 14 Dec

14:59

New subject: [Bug 548265] Killswitch on some (most? all?) Asus EeePC models causes immediate kernel freeze

http://bugzilla.novell.com/show_bug.cgi?id=548265 http://bugzilla.novell.com/show_bug.cgi?id=548265#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO CC| |jeffm@novell.com Info Provider| |nice@titanic.nyme.hu --- Comment #1 from Jeff Mahoney 2009-12-14 14:59:00 UTC --- Are you still able to reproduce this with a recent KOTD? In response to another bug reported against rt2860, I backported the driver from 2.6.32 after I saw it had a bunch of fixes. The problem here is that the driver is a "staging" driver. That means its quality is known to be pretty low and it's not yet ready to be incorporated into the "regular" kernel driver tree. We include the drivers because it's better to enable more hardware even if the driver isn't perfect. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Jan 5 Jan

12:24

New subject: [Bug 548265] Killswitch on some (most? all?) Asus EeePC models causes immediate kernel freeze

http://bugzilla.novell.com/show_bug.cgi?id=548265 http://bugzilla.novell.com/show_bug.cgi?id=548265#c2 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #2 from Tamás Németh 2010-01-05 12:24:18 UTC --- (In reply to comment #1)

...

Are you still able to reproduce this with a recent KOTD? In response to another bug reported against rt2860, I backported the driver from 2.6.32 after I saw it had a bunch of fixes.

No, I'm not able to reproduce this issue, because the kernel now crashes during AP association, making knetworkmanager's configuration corrupt on the ext4 filesystem. To sum it up my WiFi became absolutely unusable now. No connection is possible anymore. I can type some kernel call trace from tty10: [<c055e770>] skb_push+0x50/0x60 [<f87a3de8>] wlan_802_11_to_802_3_packet+0x48/0x70 [rt2760sta] [<f8772c59>] Indicate_Legacy_Packet+0xf9/0x250 [rt2760sta] [<f8798f99>] STAHandleRxDataFrame+0x1b9/0x530 [rt2760sta] [<f8799452>] STARxDoneInterruptHandle+0x142/0x1c0 [rt2760sta] [<f87b7340>] rx_done_tasklet+0x60/0xe0 [rt2760sta] [<c0255af9>] tasklet_hi_action+0xf9/0x110 [<c0256bd4>] __do_softirq+0xb4/0x200 [<c0256db5>] do_softirq+0x95/0xb0 [<c0256f55>] irq_exit+0x85/0xa0 [<c020602c>] do_IRQ+0x5c/0xe0 [<c0204670>] common_interrupt+0x30/0x40 [<f7e6e6f4>] acpi_idle_enter_simple+0x13f/0x181 [processor] [<c053da0e>] cpuidle_idle_call+0x8e/0x110 [<c0202a35>] cpu_idle+0xa5/0xf0 [<c05ee8c5>] rest_init+0x65/0x80 [<c08abcbb>] start_kernel+0x369/0x380 [<c08ab087>] i386_start_kernel+0x87/0x9f Code: 00 00 89 4c 24 14 8b 88 b0 00 00 00 89 54 24 0c 89 4c 24 10 8b 40 50 89 5c 24 04 c7 04 24 cc ce 76 c0 89 44 24 08 e8 3b 1f 0a 00 <0f> 0b eb fe b9 51 99 73 c0 eb ae 66 90 55 89 e5 53 89 cb 83 ec EIP: [<c055deb3>] skb_under_panic+0x63/0x70 SS:ESP 0068:c0877d1c ---[ end trace 783eb5ba732cbf69 ]--- Kernel panic - not syncing: Fatal exception in interrupt -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.