From: Jon Smirl <jonsmirl@gmail.com>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: current linus bk, error mounting root
Date: Thu, 10 Mar 2005 13:40:54 -0500 [thread overview]
Message-ID: <9e4733910503101040b815916@mail.gmail.com> (raw)
In-Reply-To: <20050310162918.GD2578@suse.de>
I see:
Loading libata.ko module
Loading ata_piix.ko module
ACPI: PCI interupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 169
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 169
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA0 irq 169
then raid autorun, one of the raid partitions is on /dev/sda
No panic on ata_piix load.
The panix is on killing init, it is the standard panix from not having
a root device.
I just built it in instead as a module, I'll try that next and see if
says anything different.
- Hide quoted text -
On Thu, 10 Mar 2005 17:29:19 +0100, Jens Axboe <axboe@suse.de> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <axboe@suse.de> wrote:
> > > what are the major/minor numbers of /dev/root?
> >
> >
> > If I boot on a working system it is 8,5
>
> I see no /dev/sda detected in your system from the dmesg. Ahh this is
> where it panics on loading ata_piix I suppose, can't you capture that
> panic with the serial console as well?
>
> --
> Jens Axboe
>
>
- Hide quoted text -
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-10 18:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:03 current linus bk, error mounting root Jon Smirl
2005-03-09 17:16 ` Jeff Garzik
2005-03-09 18:23 ` Jon Smirl
2005-03-09 20:28 ` Jeff Garzik
2005-03-09 20:31 ` Jeff Garzik
2005-03-09 20:51 ` Jon Smirl
2005-03-09 21:09 ` Jens Axboe
2005-03-10 1:16 ` Jon Smirl
2005-03-10 7:50 ` Jens Axboe
2005-03-10 14:58 ` Jon Smirl
2005-03-10 15:31 ` Jens Axboe
2005-03-10 15:45 ` Jon Smirl
2005-03-10 15:48 ` Jens Axboe
2005-03-10 15:59 ` Jon Smirl
2005-03-10 16:01 ` Jens Axboe
2005-03-10 16:18 ` Jon Smirl
2005-03-10 16:29 ` Jens Axboe
2005-03-10 18:40 ` Jon Smirl [this message]
2005-03-10 18:52 ` Jon Smirl
2005-03-11 3:11 ` Matt Mackall
2005-03-11 3:18 ` Jon Smirl
2005-03-15 15:39 ` Jon Smirl
2005-03-15 15:47 ` Jens Axboe
2005-03-09 20:34 ` Steven Cole
[not found] ` <20050321154131.30616ed0.akpm@osdl.org>
[not found] ` <9e473391050321155735fc506d@mail.gmail.com>
2005-03-22 0:19 ` Andrew Morton
2005-03-22 0:38 ` Greg KH
2005-03-22 0:43 ` Andrew Morton
2005-03-22 0:49 ` Greg KH
2005-03-22 0:57 ` Jon Smirl
2005-03-22 4:02 ` Greg KH
2005-03-22 1:13 ` Jon Smirl
2005-03-22 0:53 ` Jon Smirl
2005-03-22 4:03 ` Greg KH
2005-03-22 0:47 ` Jon Smirl
2005-03-22 1:14 ` Kyle Moffett
2005-03-22 4:02 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 13:15 Alexander E. Patrakov
2005-03-12 19:56 ` Jon Smirl
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=9e4733910503101040b815916@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--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