Fwd: kernel 3.2rc4 hangs if I use allyesconfig

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



should have gone to list..



---------- Forwarded message ----------
From: rajaneesh acharya <rajaneeshacharya@xxxxxxxxxxxxxx>
Date: Sat, Dec 10, 2011 at 2:48 AM
Subject: Re: kernel 3.2rc4 hangs if I use allyesconfig
To: Jim Cromie <jim.cromie@xxxxxxxxx>


Hi Jim,

allmodconfig and config borrowed from debian distro works fine

Regards
Rajaneesh



as Srivatsa Bhat bhat pointed out, -rc4 probably has the bug fixed later
whereas sufficiently old kernels dont. (before it was introduced)


----- Original Message -----
From: Jim Cromie <jim.cromie@xxxxxxxxx>
To: rajaneesh acharya <rajaneeshacharya@xxxxxxxxxxxxxx>
Sent: Sat, 10 Dec 2011 12:31:32 +0530 (IST)
Subject: Re: kernel 3.2rc4 hangs if I use allyesconfig

On Fri, Dec 9, 2011 at 11:14 PM, rajaneesh acharya
<rajaneeshacharya@xxxxxxxxxxxxxx> wrote:
> Hi Mulyadi,
>
>  Please find the screenshot...There are no debug messages being thrown out...
>
> Ran this from qemu with command
>
> qemu-system-x86_64 -kernel /boot/vmlinuz-3.2.0 -initrd initramfs.gz
>
>
>
> Regards
> Rajaneesh
>

have you  tried allmodconfig,
or a config borrowed from a distro build ?


>
> ----- Original Message -----
> From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
> To: rajaneesh acharya <rajaneeshacharya@xxxxxxxxxxxxxx>
> Cc: kernelnewbies@xxxxxxxxxxxxxxxxx
> Sent: Sat, 10 Dec 2011 10:44:40 +0530 (IST)
> Subject: Re: kernel 3.2rc4 hangs if I use allyesconfig
>
> On 09/12/2011, rajaneesh acharya <rajaneeshacharya@xxxxxxxxxxxxxx> wrote:
>> Hi
>>
>>   I created a kernel using the target as allyesconfig. The machine fails to
>> bootup (just hangs with 100% cpu utilization) with message "Booting the
>> kernel"
>> If I use the config from a distro and create the kernel image, it boots
>> fine..
>
> Hi Rajanesh
>
> Could you post at least 20 lines of boot messages up to the time it
> hangs? The clue is quite too few IMHO.
>
> AFAIK, it already passed the decompressing of kernel image, so at
> least we know there is little chance kernel image got corrupted.
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

Attachment: Screenshot-QEMU-1.png
Description: PNG image

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux