Skip to contentSkip to conversation

kernel BUG at inode.c:654!

DISCUSSION Santiago Garcia Mantinan 2 participants 3 messages May 26, 2001 – May 28, 2001

lore
Share & tools
lore
#0 lore raw

Hi!

That's what my server, wich is running 2.4.5, was shouting when I pluged in my laptop at the console (ttyS0), all I could do was copy the output I was seeing on minicom to a file, after rebooting I saw that the kernel had left some of the logging on kern.log, so I'm attaching a file with both the stuff on the console and the ones on the log.

The machine is an intel pentium 166 with 48 megs of mem, it has an stock 2.4.5 kernel with netfilter patches for the irc NAT, even though this patches were working ok on 2.4.4 and don't seem to have anything to do with this problem, I'm recompiling an stock 2.4.5 now, just to be sure.

Well, I don't know what else to say, if I'm missing something you want to know, don't hesitate to ask.

Regards...

Signature · 1 line
Manty/BestiaTester -> http://manty.net
#1 lore raw
Quoted 8 lines · Santiago Garcia Mantinan

Hi!

That's what my server, wich is running 2.4.5, was shouting when I pluged in my laptop at the console (ttyS0), all I could do was copy the output I was seeing on minicom to a file, after rebooting I saw that the kernel had left some of the logging on kern.log, so I'm attaching a file with both the stuff on the console and the ones on the log.

Quoted 7 lines

The machine is an intel pentium 166 with 48 megs of mem, it has an stock 2.4.5 kernel with netfilter patches for the irc NAT, even though this patches were working ok on 2.4.4 and don't seem to have anything to do with this problem, I'm recompiling an stock 2.4.5 now, just to be sure.

Well, I don't know what else to say, if I'm missing something you want to know, don't hesitate to ask.

Lovely... It's one of the long lists and these asserts (lines 650 and 654) are exactly what would happen if it was corrupted at some place. OTOH, it may be for real - i.e. real inodes in wrong state getting on the list, rather than corrupted pointer.

#2 lore raw
Quoted 4 lines

Lovely... It's one of the long lists and these asserts (lines 650 and 654) are exactly what would happen if it was corrupted at some place. OTOH, it may be for real - i.e. real inodes in wrong state getting on the list, rather than corrupted pointer.

You were right, corrupted pointer.

It was due to general memory corruption caused by RAM problems, sorry, it happened just as I switched to 2.4.5 and I blamed it, it probably started failing now, after months without any problem, because of the high temperatures we are having this days.

Thanks for your help and sorry to have disturbed you all for not making a memtest before :-(

Regards...

Signature · 1 line
Manty/BestiaTester -> http://manty.net