Had to leave the house quickly today so this is not as complete as I
would like. The situation is as follows: I have a k6-500 on an ali1541
(from memory) ide chipset. All channels filled with 3 hds and 1 cdrom.
2 hds on the asme port at ata66, one at ata33 and the cdrom at whatever
it's on. ;) The system boots up normally and light use is just fine.
When I backup my laptop to it though I can repeatedly bring the system
down. The end result is an oops on the screen in soft_irq_timer that
came from cpu_idle. (I had no time to write it down). The following,
just before the oops was logged:
Apr 5 01:14:35 nessie kernel: Assertion failure in journal_add_journal_head() a
t fs/jbd/journal.c:1679: "(((&bh->b_count)->counter) > 0) || (bh->b_page && bh->
b_page->mapping)"
Apr 5 01:14:35 nessie kernel: ------------[ cut here ]------------
Apr 5 01:14:35 nessie kernel: kernel BUG at fs/jbd/journal.c:1679!
The backup was an rsync over the net.
There have been other problems with the system. It liked my promise
card in it even less (old driver variety) but nothing ever did get
logged.
If you need mroe info, please yell and I'll try to answer from memory
and I'll try to give oops details when I get home (please specify what
details you're most interested in so that I don't have to type it all
in if possible :).
Thanks.
--
Red herrings strewn hither and yon.
On Mon, Apr 05, 2004 at 08:59:51AM +1000, CaT wrote:
> Had to leave the house quickly today so this is not as complete as I
Back home now so I can type out the oops:
EIP: 0060:[<c011adac>] Not tainted
EFLAGS: 00010883 (2.6.5)
EIP is at cascade+0x20/0x4c
eax: d7735fcc ebx: d7735fcc ecx: 00000000 edx: c03e5f50
esi: x03960dc edi: c03957a0 ebp: c03e5f30 esp: c03e5f24
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=c03e4000 task=x0392960)
Stack: 00000000 c043d208 c03957a0 c03e5f58 c011b241 c03957a0 c0395fac 00000026
00000000 c043d208 0000000a c03e5f50 c03e5f50 c03e5f74 c0117c6f c043d208
00000000 00000000 c03e2a00 00000046 c03e5f8c c01083fd c03e4000 0009ff00
Call Trace:
[<c011b241>] run_timer_softirq+0x4d/0x124
[<c0117c6f>] do_softirq+0x4f/0x9c
[<c01083fd>] do_IRQ+0x101/0x114
[<c0106e48>] common_interrupt+0x18/0x20
[<c0104e7c>] default_idle+0x0/0x2c
[<c0104ea2>] default_idle+0x26/0x2c
[<c0104f1b>] cpu_idle+0x2b/0x3c
[<c010301c>] _stext+0x1c/0x20
[<c03e6644>] start_kernel+0x13c/0x140
Code: 0f 0b 72 01 29 92 31 c0 8b 1b 50 57 e8 8f fd ff ff 83 c4 08
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
That is all that I have on the screen. The mb is a Gigabyte 5ax v5.2 (f4
version of the bios). Full specs here:
http://tw.giga-byte.com/MotherBoard/Products/Products_GA-5AX%20(Rev%205.2).htm
Also I've attached the lspci, .config and /proc/interrupt outputs to the
file. Below is the rest of the initial msg.
If you need help from me just holler and I'll get to it ASAP.
> would like. The situation is as follows: I have a k6-500 on an ali1541
> (from memory) ide chipset. All channels filled with 3 hds and 1 cdrom.
> 2 hds on the asme port at ata66, one at ata33 and the cdrom at whatever
> it's on. ;) The system boots up normally and light use is just fine.
> When I backup my laptop to it though I can repeatedly bring the system
> down. The end result is an oops on the screen in soft_irq_timer that
> came from cpu_idle. (I had no time to write it down). The following,
> just before the oops was logged:
>
> Apr 5 01:14:35 nessie kernel: Assertion failure in journal_add_journal_head() a
> t fs/jbd/journal.c:1679: "(((&bh->b_count)->counter) > 0) || (bh->b_page && bh->
> b_page->mapping)"
> Apr 5 01:14:35 nessie kernel: ------------[ cut here ]------------
> Apr 5 01:14:35 nessie kernel: kernel BUG at fs/jbd/journal.c:1679!
>
> The backup was an rsync over the net.
>
> There have been other problems with the system. It liked my promise
> card in it even less (old driver variety) but nothing ever did get
> logged.
>
> If you need mroe info, please yell and I'll try to answer from memory
> and I'll try to give oops details when I get home (please specify what
> details you're most interested in so that I don't have to type it all
> in if possible :).
--
Red herrings strewn hither and yon.