[Bug 490037] New: "pccardctl eject" hangs in state D
https://bugzilla.novell.com/show_bug.cgi?id=490037 Summary: "pccardctl eject" hangs in state D Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: Other Status: NEEDINFO Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jslaby@novell.com QAContact: qa@suse.de CC: gp@novell.com, seife@novell.com Blocks: 370872 Found By: --- The logs are at: https://bugzilla.novell.com/attachment.cgi?id=267094 Relevant part: pccardctl D 00000000 0 5359 5358 d2ef5efc 00000082 c0523c0c 00000000 c0585670 c0588300 c0588300 c0588300 cf922d80 cf922ff4 c1d90300 00000000 c1d90300 71d844b0 0000444d de2372c0 cf922ff4 c0523c00 f7929560 f7929564 cf922d80 f7929568 c0344b65 f7929568 Call Trace: [<c0344b65>] __mutex_lock_slowpath+0x60/0x9e [<c0344add>] mutex_lock+0xa/0xb [<f91fe642>] pcmcia_eject_card+0x1a/0x67 [pcmcia_core] [<f9200d53>] pccard_store_eject+0x1b/0x23 [pcmcia_core] [<c029e7b9>] dev_attr_store+0x24/0x29 [<c01d0c00>] sysfs_write_file+0xaf/0xdb [<c018fa60>] vfs_write+0x8b/0x13d [<c018fbb4>] sys_write+0x41/0x67 [<c0104c9b>] sysenter_do_call+0x12/0x2f [<ffffe430>] 0xffffe430 Gerald, please provide sysrq-d info from the kernel available at: http://labs.suse.cz/jslaby/bug-370872/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|370872 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |370872 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider| |jslaby@novell.com AssignedTo|bnc-team-screening@forge.pr |jslaby@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|jslaby@novell.com |gp@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 User gp@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490037#c1 --- Comment #1 from Gerald Pfeifer <gp@novell.com> 2009-03-30 18:10:28 MDT --- This is very strange. In two attempts (reboots) I have now failed to be able to log sysrq-d (nur sysrq-m). It twice worked after reboot, but after an attempt to suspend "echo d > /proc/sysrq-trigger" does not trigger anything, nor does sysrq-d via the keyboard. Any idea?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490037 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490037#c2 --- Comment #2 from Jiri Slaby <jslaby@novell.com> 2009-03-31 03:34:07 MDT --- (In reply to comment #1)
but after an attempt to suspend "echo d > /proc/sysrq-trigger" does not trigger anything, nor does sysrq-d via the keyboard. Any idea??
It depends on what issue you hit. Didn't you try to reproduce this with a nozomi card, so that it sleeps forever there (bug 490036)? Could you grab sysrq-t and look at the pccardctl process? Whether it is in mutex_lock_whatever function or somewhere else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com