https://bugzilla.novell.com/show_bug.cgi?id=332048#c8
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |reisenweber@web.de
--- Comment #8 from Jeff Mahoney 2007-10-16 11:55:42 MST ---
Ok, thanks. Comment #5 provides most of the needed information.
There are actually two bugs here. The first is the panic here:
[<c0123c0c>] panic+0x48/0xf8
[<dcf4cac1>] ahc_search_qinfifo+0x2b0/0x775 [aic7xxx]
[<dcf4d98e>] ahc_freezedevq+0x7f/0x8f [aic7xxx]
[<dcf4fbe5>] ahc_handle_seqint+0x1a1/0x23e0 [aic7xxx]
[<c016fc81>] do_sync_read+0xc7/0x10a
[<dcf0689c>] scsi_end_request+0xa1/0xab [scsi_mod]
[<c01341b9>] autoremove_wake_function+0x0/0x33
[<dcf5aff0>] ahc_linux_isr+0x184/0x1b0 [aic7xxx]
[<c014f2c7>] handle_IRQ_event+0x23/0x51
[<c01506c9>] handle_level_irq+0xb9/0xc8
[<c0107479>] do_IRQ+0x79/0x90
[<c0105e73>] common_interrupt+0x23/0x30
[<c02c0000>] unix_ioctl+0x75/0x95
There's a panic in ahc_search_qinfifo. Unfortunately, there are 4 panic cases
in that function, so it would be useful to narrow that down.
The second is here:
BUG: scheduling while atomic: beagled/ox10010000/4560
[<c02c362e>] __sched_text_start+0x5e/0x7c5
[<c011f2fc>] __cond_resched+0x18/0x29
[<c02c3dfb>] cond_resched+0x26/0x31
[<c0136c19>] down_read+0x08/0x17
[<c012eb07>] __blocking_notifier_call_chain+0x1q/0x47
[<c01ebc38>] bit_cursor+0x0/0x498
[<c012eb4b>] blocking_notifier_call_chain+0x17/0x1a <--- Problem.
[<c01eac73>] fbcon_blank+0x17/0x1e7
The first call trace shows we're in interrupt context (do_IRQ), and any
schedule() while in interrupt context is forbidden. The BUG: message is from
schedule(). This code needs to not be blocking in interrupt context.
Incidentally, that's why the machine is still up after panicking. The panic()
call expects to terminate system execution, but then execution is scheduled
away from the panic context.
So, what I need from you now is the panic message itself. It will probably be
easier to come up with a fix for the scheduling in interrupt context portion of
the bug first so that the panic message doesn't scroll off the screen.
--
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.