I think I have found a bug, I have taken a srceen dump of it.
________________________________________
F? din egen webmail p? http://solmail.sol.dk - gratis og med dig overalt!
Tr?t af virus? F? gratis beskyttelse her: http://antivirus.sol.dk
> I think I have found a bug, I have taken a srceen dump of it.
Mar 26 13:38:15 localhost kernel: CPU: 0
Mar 26 13:38:15 localhost kernel: ide-cd cdrom i810_audio ac97_codec
soundcore a
utofs 8139too mii iptable_filter
Mar 26 13:38:15 localhost kernel: invalid operand: 0000
Mar 26 13:38:15 localhost kernel: kernel BUG at page_alloc.c:145!
Mar 26 13:38:15 localhost kernel: ------------[ cut here ]------------
Mar 26 13:38:14 localhost kernel: swap_free: Bad swap file entry 0383304c
Mar 26 13:38:14 localhost kernel: swap_free: Bad swap file entry 050db024
I'd say you also have problems with your swap device ... I'd first make
sure your swap device is ok and then retry - however, the BUG is still
there, that is for sure ...
It'd also help to know your kernel version
I?aky P?rez-Gonz?lez -- Not speaking for Intel -- all opinions are my own
(and my fault)
On Wed, 26 Mar 2003, Perez-Gonzalez, Inaky wrote:
>
> Mar 26 13:38:15 localhost kernel: CPU: 0
> Mar 26 13:38:15 localhost kernel: ide-cd cdrom i810_audio ac97_codec
> soundcore a
> utofs 8139too mii iptable_filter
> Mar 26 13:38:15 localhost kernel: invalid operand: 0000
> Mar 26 13:38:15 localhost kernel: kernel BUG at page_alloc.c:145!
> Mar 26 13:38:15 localhost kernel: ------------[ cut here ]------------
> Mar 26 13:38:14 localhost kernel: swap_free: Bad swap file entry 0383304c
> Mar 26 13:38:14 localhost kernel: swap_free: Bad swap file entry 050db024
>
> I'd say you also have problems with your swap device ... I'd first make
> sure your swap device is ok and then retry -
No, those swap_free and swap_dup errors appear when a page table has been
corrupted, and we don't swap out page tables themselves, just the pages
they point to. There's no reason to suspect the swap device at all.
> however, the BUG is still there, that is for sure ...
>
> It'd also help to know your kernel version
The kernel version would help to identify the page_alloc.c:145 BUG.
But it's likely to correspond to freeing an impossible or already-freed
page, because of the corrupted page table (odd numbered corruption looks
like a valid page, even numbered corruption looks like a swap entry).
Sorry, I've no guess to make on what might be corrupting this memory.
Hugh