Displaying 2 results from an estimated 2 matches for "c0106b87".
2002 Nov 08
2
2.4.18 ext3 problems
...[<c0150b98>]
[<c0150a68>] [<c0150a68>] [<c0150a68>] [<c0150c79>] [<c0150f0b>]
[<c01567b9>]
[<c014ebad>] [<c014ec4c>] [<c014ecf3>] [<c014ec4c>] [<c0140287>]
[<c013ea38>]
[<c01382c6>] [<c01383a2>] [<c0106b87>]
Code: 0f 0b 83 c4 14 8b 54 24 28 8b 42 04 48 8b 4c 24 28 89 41 04
That finally caused the thread that was running to lock solid and the
machine had to be power-cycled.
Sorry I can't put the oops through ksymoops - opportunity lost.
The system is running stock 2.4.18 build patched for l...
2002 Dec 14
2
Nasty ext3 errors 2.4.18
...c>] ]
[KMSG:<4> [<c01516c2>] [<c0151727>] [<c0121b5f>] [<c011feae>]
[<c011ff0d>] [<c0140567>] ]
[KMSG:<4> [<c01518d1>] [<c01406bc>] [<c012cc3d>] [<c013796a>]
[<c012dae7>] [<c012de3a>] ]
[KMSG:<4> [<c0106b87>] ]
[KMSG:<4>]
[KMSG:<4>Code: 0f 0b 83 c4 14 8b 54 24 28 8b 42 04 48 8b 4c 24 28 89 41
04 ]
^^^
That's the final nail in the coffin as the process then locks solid (but
still has threads running which then run out of memory - total chaos
ensues) the box has to be powered off/on...