lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 13 Feb 2007 12:20:35 +0800
From:	"Tony.Ho" <linux@...center.cn>
To:	albcamus <albcamus@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Why can't I build a running Kernel?

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.


Tony.Ho wrote:
> I have the same problem with 2.6.20.
> My host is dell PE850: pemtiumD 2.8G X1,  MEM  1G X4,  SATA  73G X1.
>
> albcamus wrote:
>> 2007/2/9, Jiri Slaby <jirislaby@...il.com>:
>>> Reg Clemens napsal(a):
>>> > 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.
>>
>>
>>
>>
>>> 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 <albcamus@...il.com>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ