From: Andrew Morton <akpm@osdl.org>
To: "Carlo E. Prelz" <fluido@fluido.as>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
Date: Sat, 21 Jan 2006 01:09:32 -0800 [thread overview]
Message-ID: <20060121010932.5d731f90.akpm@osdl.org> (raw)
In-Reply-To: <20060120123202.GA1138@epio.fluido.as>
"Carlo E. Prelz" <fluido@fluido.as> wrote:
>
> Best regards to all and everyone. I just purchased a new RS480 (Radeon
> XPress200)-based motherboard. It is a Sapphire Pure Performance
> PP-A9RS480. Mine is equipped with an Athlon64 3200+. I am attaching
> the output of lspci -v
>
> When booting with kernels from 2.6.15-rc1 up (tested with 2.6.15-rc1,
> 2.6.15-rc5, 2.6.15 and 2.6.16-rc1), the boot process freezes after
> displaying messages retated to registering io schedulers:
>
> ...
> ...
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
>
> There is no OOPS of any kind. The disk activity led remains on. With
> both 2.6.14 and 2.6.14.6, boot regularly continues with:
>
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> loop: loaded (max 8 devices)
> pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe@suse.de) and petero2@telia.com
> nbd: registered device at major 43
> ...
> ...
>
> I tried to enable all debug options in configure, but no new message
> appears.
>
> Important: I obtain the same result (frozen after "io scheduler cfq
> registered") when booting with a 100MB netinst debian sid bootdisk,
> downloaded last night. An older (9 month old) Ubuntu bootdisk boots
> perfectly. Both cd's are AMD64-specific.
>
Can you please add `initcall_debug' to the kernel boot command line?
That'll tell us which function got stuck.
next prev parent reply other threads:[~2006-01-21 9:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 12:32 Carlo E. Prelz
2006-01-21 9:09 ` Andrew Morton [this message]
2006-01-21 12:57 ` Carlo E. Prelz
2006-01-21 20:58 ` Andrew Morton
2006-01-21 21:28 ` Erwin Rol
2006-01-21 22:04 ` Dave Jones
2006-01-22 4:14 ` Kurt Wall
2006-01-22 7:40 ` Carlo E. Prelz
2006-01-22 7:55 ` Andrew Morton
2006-01-22 8:30 ` Carlo E. Prelz
2006-01-22 11:11 ` Carlo E. Prelz
2006-02-05 10:33 ` Carlo E. Prelz
2006-02-05 19:45 ` [linux-usb-devel] " David Brownell
2006-02-06 8:02 ` Carlo E. Prelz
2006-02-06 16:24 ` David Brownell
2006-02-06 16:50 ` Carlo E. Prelz
2006-02-06 17:31 ` David Brownell
2006-02-06 17:45 ` Carlo E. Prelz
2006-01-23 19:01 ` David Brownell
2006-01-23 21:47 ` Carlo E. Prelz
2006-01-24 4:42 ` Greg KH
2006-01-24 15:15 ` David Brownell
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=20060121010932.5d731f90.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=fluido@fluido.as \
--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
Powered by JetHome