Frugalware

Please read the http://frugalware.org/docs/bugs page if you are new to bugreporting!
Tasklist

FS#2243 - kernel panic during bootup

Attached to Project: Frugalware
Opened by Marcin Psiurski (mpsi) - Friday, 13 July 2007, 12:05 GMT+2
Last edited by Miklos Vajna (vmiklos) - Friday, 05 October 2007, 00:23 GMT+2
Task Type Bug Report
Category Base system
Status Closed
Assigned To No-one
Operating System x86_64 / i686
Severity Critical
Priority High
Reported Version -current
Due in Version 0.7
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

After upgrading to 2.6.22 kernel i get the following error during bootup:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

My machine is Thinkpad R52.
This task depends upon

Closed by  Miklos Vajna (vmiklos)
Friday, 05 October 2007, 00:23 GMT+2
Reason for closing:  Fixed
Additional comments about closing:  kernel-2.6.22-5
Comment by crazy (bugs) - Friday, 13 July 2007, 12:37 GMT+2
Yes is a known bug on some boxes. Guesssing you have an SATA/PATA controller ? Try boothing with ideX=noprobe ideY=noprobe ( where X,Y is your ide nr , e.g: disk 1 is ide0 and so on )

We are working on an fix for this already but will take some time while it need a big bisect to find the real bug .
At the moment I'm working on an workaround so you can switch IDE/PATA with ideX=noprobe.
Comment by Marcin Psiurski (mpsi) - Friday, 13 July 2007, 13:48 GMT+2
Attached is my output of lspci, lspci -nn -vvvxxx and dmesg on 2.6.2-fw3 kernel
   lspci (33.6 KiB)
   dmesg (20.8 KiB)
Comment by Priyank (priyank) - Friday, 13 July 2007, 14:48 GMT+2
I get the same problem on my Dell Inspiron 6400.
Comment by Priyank (priyank) - Friday, 13 July 2007, 14:58 GMT+2
Attached is my output of lspci and lspci -nn -vvvxxx
   lspci (2 KiB)
   lspci_1 (34.8 KiB)
Comment by Marcin Psiurski (mpsi) - Friday, 13 July 2007, 16:49 GMT+2
In the attached file is output of dmesg on 2.6.22-git2 kernel
   dmesg-1 (25.5 KiB)
Comment by Miklos Vajna (vmiklos) - Sunday, 29 July 2007, 14:22 GMT+2
a workaround for this has been added to

http://wiki.frugalware.org/KnownBugs-0.7pre2

till upstream does not fix this bug.

thanks
Comment by Miklos Vajna (vmiklos) - Friday, 28 September 2007, 22:10 GMT+2
do we have an idea about what can be fixed about this?

a trivial workaround is to add a note to the knownbugs-0.7 page, but i would prefer a cleaner solution if possible :s

Loading...