I am having a sudden problem getting Fedora and Knoppix to boot. I have limited experience and don’t have any idea how to even start fixing this since I only know how to fix things from a terminal window. I apologize for the long post, but I want to try to include everything:

I have been running Fedora 8 (64-bit) on my computer now for two months or so. I have not really had any problems until now. Fedora is the only operating system on the machine. I allow it to update every time there are available updates. I have successfully shut-down and restarted at least three times since the last updates and software changes.

Last night, I was using the computer and it froze for the first time ever under Linux – twice. The first time was shortly after logging into my account before I had a chance to open anything and the second time was after I was working. In both cases I tried everything I could and waited, but ended up pressing the physical power button on the computer box to restart. Both times it restarted without problems or errors that I could see. I then used my machine for a few hours with no more trouble. When I shut down, I put it in hibernate (which I’ve done before with no issues though I usually do a full shut-down).

This morning, I have been unable to restart. Fedora tries to start and then I get strange screens. One line during the first boot read:
BUG: soft lockup-CPI#0 stuck for 11s! [udevd:618]
(with other stuff below, though this does not return and I didn’t write it all down)

I tried to boot a few more times with no success.

During the boot-up everything seemed OK. I got the “Welcome to Fedora” line and then the start-up began. Instead of the usual list of processes and [OK]s, I got a horrible-looking screen that shows something like:


R10: ### R11: ### R12: ###
R13: ### R14: ### R15: ###
FS: ### (0000) GS: ### kn1GS: ###
CS: 0010 DS: 0000 ES: 0000 CR0: ###
CR2: ### CR3: ### CR4: ###
DR0: ### DR1: ### DR2: ###
DR3: ### DR6: ### DR7: ###
Process udevd (pid: 584, threadinfo ###, task ###)
Stack: ### ### ### ###
### ### ### ###
### ### ### ###
Call Trace:
[<###>] new_inode+0x4e/0x7f (six more lines like the above with different names)

Code: # # # # # # # # # # # # # # # # # # # #
RIP [<###>] __list_add+0x27/0x5b
RSP <###>


(Note: I’m using ### to denote lots of hex code that takes too long to type and changes with each boot-up anyway, I can upload photos to my website later if helpful.)


It should also be noted that the pid (process id?) and the processes/errors references change at every boot-up – so I can’t trace it to one particular process.

Occasionally, this screen is followed by another full of lines in the format of the one below, though this is not always the case:

[<###>] dput+0xf1/0xfb

I think this is just a longer “Call Trace” sequence where it hangs up, but the screens go by so fast, I’m not sure.

After trying this a few times, I then opted to boot from an older version of Fedora 8 (2.6.23.14-115.fc8 instead of 2.6.23.15-137.fc8) that was listed under my GRUB boot options. This failed quickly. I get this:


.
Decompressing Linux…done.
Booting the kernel.

Bad page state in process ‘swapper’
page:### flags:### mapping:### mapcount:-### count:0 (Not tainted)
Trying to fix it up, but a reboot is needed
Backtrace:
Bad page state in process ‘swapper’
page:### flags:### mapping:### mapcount:-### count:0 (Tainted: G B )
Trying to fix it up, but a reboot is needed
Backtrace:
Bad page state in process ‘swapper’
page:### flags:### mapping:### mapcount:-### count:0 (Tainted: G B )
Trying to fix it up, but a reboot is needed
Backtrace:
powernow-k8: BIOS error – no PSB or ACPI _PSS objects
crc error
Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


I couldn’t find anyone else with the same problem posted anywhere online, so I tried to rescue the system with the Fedora install DVD. It didn’t seem to work.

I get a screen that says:

Running anaconda 11.3.0.50, the Fedora rescue mode – please wait…
Python: Modules/gcmodule.c:241: update_refs: Assertion ‘gc->gc.gc_refs == (-3)’ failed.
Install exited abnormally [1/1]
Sending termination signals…done
Sending kill signals…done
Disabling swap…
Unmounting filesystems…
/mnt/runtime done
disabling /dev/loop0
/proc/bus/usb done
/proc done
/dev/pts done
/sys done
/tmp/ramfs done
/selinux done
you may safely reboot your system


I didn’t expect this to help after I saw that it failed. I was hopeful and rebooted. I got:

.
Decompressing Linux…done.
Booting the kernel.

Bad page state in process ‘swapper’
Page:### flags:### mapping:### mapcount:-### count:0 (Not tainted)
Trying to fix it up, but a reboot is needed
Backtrace:
(and then my usual starting messages)


The bottom left of the screen says “Kernel alive” as always.

I then usually get that RBP:###, R10:### etc page as before (again with ever different numbers, pids and processes)


Unsure what else to try, I put in my Knoppix CD and rebooted. I’ve used the same Knoppix CD on this machine before (before and after Fedora was installed) and it has never failed me before.

Unfortunately, with Knoppix I only get the penguin and a line that says:
kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(1,3)

I then tried to load Knoppix in “failsafe” mode, but that ended the same way, though I also got this:


ata8: SATA link down (SStatus 0 SControl 300)
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
EISA: Probing bus 0 at eisa.0
Cannot allocate resource for EISA slot 4
Cannot allocate resource for EISA slot 5
Cannot allocate resource for EISA slot 6
Cannot allocate resource for EISA slot 7
Cannot allocate resource for EISA slot 8
EISA: Detected 0 cards.
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 15
Using IPI No-Shortcut mode
Time: tsc clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
input: PS/2 Generic Mouse as /class/input/input1
RAMDISK: Compressed image found at block 0
crc error
No filesystem could mount root, tried: reiserfs ext3 ext2 msdos vfat iso9660 ….
Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(1,3)


Ocassionally (twice so far) everything seems to load, though there are lots of [FAILED] messages during the Fedora boot that go by too fast for me to catch. The GUI fails (this is OK at this point) and I get the text log-in screen which brings my spirits up. During the first time this happened, I could not log on with either my user account or the root account. A message flashed too quickly for me to read after each attempt. During the second occurrence, the screen looked like this:


Fedora release 8 (Werewolf)
Kernel 2.6.23.15-137.fc8 on an x86_64

localhost login: modprobe: FATAL: Error inserting ipv6 (/lib/modules/2.6.23.15-137.fc8/kernel/net/ipv6/ipv6.ko): Key was rejected by service

I hit enter for a fresh login prompt and I tried to log in – but it wouldn’t let me as before.


I’m running out of ideas. Perhaps this is a sudden hardware failure? (If so, what failed?)


I’m open to any suggestions or ideas!


I have a home-built computer:
- Fedora 8 64-bit updated as of 18 February 2008 (2.6.23.15-137.fc8)
- MSI K8N Neo4 Platinum motherboard with AMD-64 processor
(I can provide more specs if helpful, but all hardware was working fine until this morning.)

since you have a home-built computer I would check to make sure all cables are well seated - has one worked itself lose

are the knoppix disks in good shape - do they work on another computer

what dose memtest86 say

let me know if you get it fixed

It certainly sounds like a hardware problem. My initial thought was a BIOS issue. have you gone into your BIOS? Is everything kosher?

If the bios looks good, then it's probably an issue with the motherboard and/or RAM. Can you run a memtest (you may have to download the memtest86+ iso & run from CD)?

If memory checks out ok, it's probably your motherboard. I say this as opposed to hard drive as knoppix doesn't care if you even have a hard drive.

At this point, it's still marginally possible that your BIOS is corrupted & fudging things up. It won't hurt to update it. If that doesn't work, you'll need to start replacing parts until you find the problem.

I'd check grounding issues and the mobo first. Pull the mobo - with everything attached - out of the case & see if your machine will boot knoppix (obviously be careful, be sure the mobo is sitting on something non-metallic, unplug the PS from the wall while you're unscrewing things, don't touch anything while it's on... of course you know all this because you built this machine, but...). If it boots, then it's a grounding problem. If it doesn't then continue removing bits. To boot, you need a [crappy] graphics card, a tiny bit of memory, a CPU, a mobo, and a CDROM. pull out all but one stick of memory, swap graphics cards, swap CPUs, remove all hard drives, remove all USB/Firewire, remove all PCI cards, etc. etc. etc.

I've had a similar situation, can't recall the exact errors, but for me it turned out to be a broken floppy drive. I third the notion of rechecking all your hardware, especially if Knoppix no longer loads.

Thank you everyone for your prompt replies.

I had checked the BIOS and everything was good (including the memory check there) - that that's why I couldn't see what could have failed.

The MEMTEST86 did show some errors after a few tests (it was fine for the early tests) - there were severe problems after some time, in fact. I thought I had run the test before, but apparently didn't let it run long enough to catch any errors?

The last time I had memory go bad, the BIOS didn't count it correctly and the resulting problems where not so terrible.
I feel a bit silly now!

I have the bad stick out and I'm happy to say I'm responding on my own computer (though I do miss the extra RAM). I'll be checking on the warranty and hopefully be back to full speed in a few days.

Thanks again to everyone!

Even the best of us will overlook something simple

Yea, like I was slimming down my kernel last night. I have a 1GB built-in nic, so I unchecked the 10-100 drivers right? Makes sense?

In reality the driver is under 10-100 in built-in section. I recompiled and it couldn't find NIC. Took me some headscratching to realize what was going on and I also felt silly

Happens to all of us...

-Viz