Skip to contentSkip to conversation

Why can't I build a running Kernel?

DISCUSSION Reg Clemens 4 participants 8 messages Feb 8, 2007 – Feb 13, 2007

lore
Share & tools
lore
#0 lore raw

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors.
Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

Signature · 2 lines
                                        Reg.Clemens
                                        [email protected]
#1 lore raw

Reg Clemens napsal(a):

Quoted 23 lines

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors. Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

Quoted 6 lines

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

Re-enable sata/scsi/usb/whatever is your root behind stuff back again? What does your .config look like?

regards,

Signature · 4 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
#2 lore raw

2007/2/9, Jiri Slaby <[email protected]>:

Quoted 32 lines

Reg Clemens napsal(a):

Quoted 30 lines

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors.
Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

I have the same problem with 2.6.19 and later. The previous kernel with same .config works, but it's not true for 2.6.19 and 2.6.30.

Quoted 5 lines

Re-enable sata/scsi/usb/whatever is your root behind stuff back again? What does
your .config look like?

regards,

I selected everything about ATA to <*> or <M>, and made initrd for the newly-built kernel, still unable to boot.

The .config was attached, I have kdb-4.4 patched.

Thanks and Regards,
albcamus <[email protected]>

#3 lore raw

albcamus napsal(a):

Quoted 43 lines

2007/2/9, Jiri Slaby <[email protected]>:

Quoted 32 lines

Reg Clemens napsal(a):

Quoted 30 lines

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors.
Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

I have the same problem with 2.6.19 and later. The previous kernel with same .config works, but it's not true for 2.6.19 and 2.6.30.

Quoted 4 lines

Re-enable sata/scsi/usb/whatever is your root behind stuff back again? What does
your .config look like?

Quoted 6 lines
Quoted 1 line

regards,

I selected everything about ATA to <*> or <M>, and made initrd for the newly-built kernel, still unable to boot.

The .config was attached, I have kdb-4.4 patched.

Config seems to be fine. Please post
lspci -vvvxx

and lines from your boot loader.

regards,

Signature · 4 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
#4 lore raw

2007/2/12, Jiri Slaby <[email protected]>:

Quoted 2 lines

Config seems to be fine. Please post
lspci -vvvxx

Attached.

Quoted 3 lines

and lines from your boot loader.

title Fedora Core (2.6.20)

	root (hd0,1)
	kernel /vmlinuz-2.6.20 ro root=LABEL=/ vga=0x31B
	initrd /initrd-2.6.20.img

And I have the SATA device /dev/sda3 labeled as '/'.

Quoted 2 lines

regards,
--

Thanks and regards,
albcamus<[email protected]>

#5 lore raw

albcamus napsal(a):

Quoted 10 lines

2007/2/12, Jiri Slaby <[email protected]>:

Quoted 2 lines

and lines from your boot loader.

title Fedora Core (2.6.20)

    root (hd0,1)
    kernel /vmlinuz-2.6.20 ro root=LABEL=/ vga=0x31B
    initrd /initrd-2.6.20.img

And I have the SATA device /dev/sda3 labeled as '/'.

I would try to disable piix from old ATA tree (which was superseded by libata ata_piix). This is what've changed since 2.6.19 times -- you probably may turn the whole 'ATA/ATAPI/MFM/RLL support' off. Another problem may lie in your initrd, what distro do you use/what type of initrd do you have -- it would be reasonable to look into it, what (which modules) does it contain and load.

reagrds,

Signature · 4 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
#6 lore raw
In reply to albcamus

I have the same problem with 2.6.20.
My host is dell PE850: pemtiumD 2.8G X1, MEM 1G X4, SATA 73G X1.

Quoted 52 lines · albcamus

2007/2/9, Jiri Slaby <[email protected]>:

Quoted 32 lines

Reg Clemens napsal(a):

Quoted 30 lines

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors.
Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

I have the same problem with 2.6.19 and later. The previous kernel with same .config works, but it's not true for 2.6.19 and 2.6.30.

Quoted 5 lines

Re-enable sata/scsi/usb/whatever is your root behind stuff back again? What does
your .config look like?

regards,

I selected everything about ATA to <*> or <M>, and made initrd for the newly-built kernel, still unable to boot.

The .config was attached, I have kdb-4.4 patched.

Thanks and Regards,
albcamus <[email protected]>

#7 lore raw

In addition....
This problem is not appear on another PC host with the same hardware(CPU,HD) except MEM is 2G. OS is origin RHEL4 without updates.

Quoted 63 lines · Tony.Ho

I have the same problem with 2.6.20.
My host is dell PE850: pemtiumD 2.8G X1, MEM 1G X4, SATA 73G X1.

Quoted 45 lines · albcamus

2007/2/9, Jiri Slaby <[email protected]>:

Quoted 32 lines

Reg Clemens napsal(a):

Quoted 30 lines

Why can't I build a running Kernel?
I have in the past, but since some time in the 2.6.19 series, I have got the following series of errors.
Same thing now with 2.6.20.

I build with:

make xconfig

changing only the Processor type to Pentium4,
then I

make bzImage
make modules
make modules_install
make install

Fine everything builds, no errors.
I then try booting, and I get 4 or 5 lines and then

Unable to access resume device (/dev/sda5)
mount: could not find filesystem '/dev/root' < 4 more lines with setuproot and switchroot >

and then

    Kernel panic - not syncing: Attempting to kill init!

Sigh.
What has changed, what do I need to do to get this thing to boot?

I have the same problem with 2.6.19 and later. The previous kernel with same .config works, but it's not true for 2.6.19 and 2.6.30.

Quoted 5 lines

Re-enable sata/scsi/usb/whatever is your root behind stuff back again? What does
your .config look like?

regards,

Quoted 7 lines

I selected everything about ATA to <*> or <M>, and made initrd for the newly-built kernel, still unable to boot.

The .config was attached, I have kdb-4.4 patched.

Thanks and Regards,
albcamus <[email protected]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/