FS#9795 - Kernel panic on 2.6.23-2.6.24

Attached to Project: Arch Linux
Opened by Teo Mrnjavac (teo) - Sunday, 09 March 2008, 12:27 GMT
Last edited by Aaron Griffin (phrakture) - Sunday, 09 November 2008, 05:28 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tobias Powalowski (tpowa)
Aaron Griffin (phrakture)
Architecture x86_64
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I tried to install Arch64 on a Dell XPS M1530 with the following configurations:
* FTP install from 2007.11-4
* Local install from 2007.11-4
* FTP install from 2007.8-2
* Local install from 2007.8-2

Partition layouts tried:
---
sda1 /boot ext2
sda5 / reiserfs or ext3
sda6 /home reiserfs
sda7 swap
---
sda1 / reiserfs
sda5 /home reiserfs
sda6 swap
---
I tried with traditional /dev/sdX# and persistent by-uuid naming.

I tried with kernels 2.6.23, 2.6.24 and 2.6.24-ice (PKGBUILD from AUR).

I tried different mkinitcpio.conf configurations, mainly with or without pata and scsi hooks and with or without ata_generic and ahci modules.

I tried booting from the LiveCD with root=/dev/sda#.

The result is always the same:
After a successful and straightforward install, on the first boot GRUB loads normally the initramfs. udev runs normally and all the hardware is detected. Initramfs runs the filesystem module and detects reiserfs (or ext3). When initramfs finishes and kinit takes over I get some usual and ok ReiserFS (or ext3) mumbo jumbo, in the style "found reiserfs format 3.6 with standard journal; ordered data mode; journal parameters; using r5 hash to sort names", and then
kinit: Mounted root (reiserfs filesystem) readonly.
sh: root=/dev/sda5 [or sda5 or by-uuid]: No such file or directory
Kernel panic - not syncing: Attempted to kill init!


Additional info:
* package version(s):
Various kernel versions from 2.6.23 to 2.6.24-3 including -ice patchset

* config and/or log files etc.
Virtually any sane menu.lst and mkinitcpio.conf configurations one can imagine.


Steps to reproduce:
Not sure if this applies to some system other than the Dell XPS M1530. All I did was to install Arch64 with a dozen different partition layouts and mkinitcpio configurations.

I attach the kernel log from the LiveCD, the one that boots.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Sunday, 09 November 2008, 05:28 GMT
Reason for closing:  Deferred
Comment by Teo Mrnjavac (teo) - Sunday, 09 March 2008, 13:21 GMT
Update: I confirm that the problem persists on the same machine with 2007.8-2 i686 and kernel 2.6.22.
Here are some of the various menu.lst, fstab and mkinitcpio.conf I tried: http://pastebin.com/f377b3e1c
Comment by Glenn Matthys (RedShift) - Sunday, 09 March 2008, 20:10 GMT
I vote to increase the severity of this issue. Someone else on IRC is having exactly the same problem. Two unrelated people having exactly the same problem is just too weird, there are probably others out there too.

What puzzles me is this:

sh: root=/dev/sda5 [or sda5 or by-uuid]: No such file or directory

What is that sh doing there? Where is this message originating from? Is it from the initcpio? But control has already been passed to kinit...?
Comment by Teo Mrnjavac (teo) - Sunday, 09 March 2008, 23:43 GMT
After three days of blood and tears I manager to perform a successful bootable install, I installed offline form 2007.8-2 x86_64, all the packages from core - that was the only way. I can only conclude there are missing deps in core.
Comment by daaku (daaku) - Sunday, 09 March 2008, 23:51 GMT
I had the same issue, but it was resolved when I chose to install ALL base packages instead of selectively choosing them. There's a missing dependancy for some package!
Comment by Tobias Powalowski (tpowa) - Monday, 10 March 2008, 06:28 GMT
hm guys, if you deselect packages from base you need to know what you are doing.
We state clearly install base and then go on.
Comment by Glenn Matthys (RedShift) - Tuesday, 07 October 2008, 05:23 GMT
Base or no base, there's still a missing dep.
Comment by Aaron Griffin (phrakture) - Tuesday, 07 October 2008, 05:24 GMT
The bug appears to be usage of init=/bin/sh
See  FS#8832 

Loading...