From: Andrew Morton <akpm@osdl.org>
To: "Francisco Figueiredo Jr." <fxjrlists@yahoo.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.12 and 2.6.13 hangs for a while on boot
Date: Mon, 25 Jul 2005 14:45:58 -0700 [thread overview]
Message-ID: <20050725144558.03c0347c.akpm@osdl.org> (raw)
In-Reply-To: <20050719180521.8914.qmail@web60711.mail.yahoo.com>
"Francisco Figueiredo Jr." <fxjrlists@yahoo.com.br> wrote:
>
> I'm having little hangs while booting with kernels 2.6.12 and 2.6.13-rc1, rc2
> and rc3.
>
> It is strange that 2.6.12-rc1 booted ok without hangs.
>
> I saw a post of Alan Cox on rc-1 release notes:
>
> "Old ISA/VESA systems sometimes put tertiary IDE controllers at addresses
> 0x1e8, 0x168, 0x1e0 or 0x160. Linux thus probes these addresses on x86
> systems. Unfortunately some PCI systems now use these addresses for other
> purposes which leads to users seeing minute plus hangs during boot or even
> crashes."
>
> I thought this could be my problem, but it still hangs on boot.
>
> Hangs appears just before mounting filesystems message and before configuring
> system to use udev.
Are these hangs temporary or permanent? If they are temporary (ie: the
kernel recovers OK) then we should call them "stalls". Because a "hang" is
considered to be a permanent state.
Either way, we need to know where the kernel is stuck. Adding
`initcall_debug' to your kernel boot command may help.
And when the hang/stall occurs, hit the ALT-SSQRQ-P and ALT-SYSRQ-T key
combinations and send us the resulting traces.
Thanks.
next prev parent reply other threads:[~2005-07-25 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 18:05 Francisco Figueiredo Jr.
2005-07-25 21:45 ` Andrew Morton [this message]
2005-09-02 21:28 Andrew Burgess
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=20050725144558.03c0347c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=fxjrlists@yahoo.com.br \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®