public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: akpm@osdl.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.5-rc2-mm1 does not boot. 2.6.5-rc1-mm2 + small fix from axboe was fine
Date: Mon, 22 Mar 2004 11:16:17 +0100	[thread overview]
Message-ID: <405EBCF1.4010403@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0403211550430.28727@montezuma.fsmlabs.com>

Zwane Mwaikambo wrote:
> On Sun, 21 Mar 2004, Eric Valette wrote:
> 
>> System starts but hang just before giving hand to init, sometimes I see
>>
>> Mounted devfs on /dev <=== Hangs here
>> Freeing unused kernel memory: 216k freed
>>
>> Sometimes it goes a little bit further but hangs nearly at calling 
>> init...
>>
>> Is there something tagged __init that should not be? Or does some of the
>> new SCSI stuff breaks (swap on sda1, ...).
>>
>> Keyboard still gets interrupt (CAPS lock led), but nothing happens. Like
>> if there was a deadlock. No kdbg...
> 
> 
> initramfs-search-for-init.patch
> 
> That patch may be freeing initmem before you get to prepare_namespace()

After a sleep, I build up a clean 2.6.5-rc2-mm1, removed the two 
initramfs-* from the broken-out patches, and problem looks *quite* the same.

I managed to start init, but it fails somewhere in running scripts in 
rcS.d. I have :

README                S30checkfs.sh       S40networking
S01devfsd             S30etc-setserial    S41portmap
S02mountvirtfs        S30procps.sh        S45mountnfs.sh
S05bootlogd           S35devpts.sh        S46setserial
S05keymap.sh          S35mountall.sh      S48console-screen.sh
S09scsitools-pre.sh   S35mountkernfs      S50hwclock.sh
S10checkroot.sh       S38pppd-dns         S51ntpdate
S18hwclockfirst.sh    S39dns-clean        S55bootmisc.sh
S20dns-clean          S39ifupdown         S55urandom
S20module-init-tools  S39pppstatus-clean  S70nviboot
S20modutils           S40hostname.sh      S70xfree86-common
S22scsitools.sh       S40hotplug          S75sudo

I see *sometimes* the first devfsd message but almost nothing else. I 
think I also manage to partially initialize usbdevfs on /proc/bus/usb. 
It looks like due to an asynchronuous (irq) event, something deadlocks 
the machine.

-- 
    __
   /  `                   	Eric Valette
  /--   __  o _.          	6 rue Paul Le Flem
(___, / (_(_(__         	35740 Pace

Tel: +33 (0)2 99 85 26 76	Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr




  parent reply	other threads:[~2004-03-22 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 20:24 2.6.5-rc2-mm1 does not boot. 2.6.5-rc1-mm2 + small fix from axboe was fine Eric Valette
2004-03-21 20:51 ` Zwane Mwaikambo
2004-03-21 21:45   ` Eric Valette
2004-03-22 10:16   ` Eric Valette [this message]
2004-03-21 20:55 ` Zwane Mwaikambo
2004-03-21 21:22   ` Eric Valette
2004-03-21 21:48     ` Eric Valette
2004-03-21 22:08       ` Eric Valette
2004-03-21 22:39   ` Eric Valette
2004-03-22  5:49     ` Zwane Mwaikambo
2004-03-22 19:20       ` Luiz Fernando Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=405EBCF1.4010403@free.fr \
    --to=eric.valette@free.fr \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox