I had something similar. But your description isn't really helpfull. For example, what is the last message which you know to be correct _before_ the GPF error ?
In my case the error happened when init changed level to run-level 2. see bug #330592 Cheers, Ernest. On Monday 17 October 2005 23:44, Marcin Dębicki wrote: > I have a problem with 2.6.13.1 kernel with SELinux enabled. While I'm using > kernel with SELinux disabled (selinux=0) tverything works fine. Changing > only this one kernel parameter to 1 makes machine impossible to boot (only > general protection rip message repeating on a screen). > I don't know where it fails but I think it is while /dev is being populated > (using udev if it means something) or a few steps earlier while mounting > root fs or changing root. > I'll be thankful if anyone can help -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
