Did a reboot and picked up this new kernel that yum had installed for me. Failed miserably and caused a kernel panic after trying to umount 2 drives during boot. Anyone else got this? Any clues? Gone back to 2.6.11-1.35 smp for time being.

---

[font='courier,courier new']Did you remember to patch you LILO/GRUB/yaboot .confs accordingly?[/font]

---

Not sure if this is related, but 2.6.12-1.1398_FC4 was dead-locking on two of my machines, very unpredictable but max uptime was under 2 days before dead-lock. ..No clues to be found in the logs what so ever, just frozen solid and a forceful reset was the only way out. ...reverted back to 2.6.11-1.1369_FC4 which has had no issues to speak of here.

-dawg

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=2541&amp;prj=1&amp;trans=off" border="0">
Linux sex: unzip; strip; touch; finger; mount; fsck; more; yes; umount; sleep :o)

I got the same problem with 2.6.12-1.1372_FC3 SMP on my Intel P4 3.0GHHT box. I had to disable HT and force FC3 to boot with non-SMP kernel. I think it's some sort of race condition when initializing the kernel in SMP mode.

---

Thanks guys. Had a good search around and found reference to mkinitrd. Seems like the smp version does not work but can be fixed. Single proc version is fine. Here's a link.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163437

I might just wait for the next version rather than mess with this tbh.

Again thanks.
Regards.

---