Mailinglist Archive: opensuse-bugs (5235 mails)

[bugzilla_noreply@xxxxxxxxxx]

http://bugzilla.novell.com/show_bug.cgi?id=490037

User gp@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=490037#c3





--- Comment #3 from Gerald Pfeifer <gp@xxxxxxxxxx>  2009-04-01 14:29:28 MDT ---
(In reply to comment #2)
> > but after an attempt to suspend "echo d > /proc/sysrq-trigger" does
> > not trigger anything, nor does sysrq-d via the keyboard.  Any idea??

Found it!  After the failed suspend, the output of sysrq invocations is
no longer sent to /var/log/messages.  dmesg captured this properly, and
other message still go to /var/log/messages.  Should I report this as a
separate bug?

> 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)?

Yes, all my tests are with a nozomi card.

> Could you grab sysrq-t and look at the pccardctl process? Whether it
> is in mutex_lock_whatever function or somewhere else.

I'll attach the output of various sysrq invocations.

-- 
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.