From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Andre Hessling <ahessling@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.15 sometimes only detects one of two SATA drives and panics
Date: Thu, 12 Jan 2006 21:02:09 +1300 [thread overview]
Message-ID: <43C60D01.5080808@reub.net> (raw)
In-Reply-To: <20060111234011.451c5c36.akpm@osdl.org>
On 12/01/2006 8:40 p.m., Andrew Morton wrote:
> Andre Hessling <ahessling@gmx.de> wrote:
>> Hello!
>>
>> I recently upgraded from 2.6.14 to 2.6.15 vanilla and I encountered some
>> random kernel panics on boot so far.
>>
>> The panic is:
>> "Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)"
>
> Reuben, do you think this is the same as the bug you're seeing?
Hard to be sure, on this one I'm not convinced. With mine, both controllers are
recognised but display timeout messages which are not shown by the sequences
reported below.
The hardware here is similar to mine though, mine is:
00:1f.2 SATA controller: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA
Controller (rev 03) (prog-if 01 [AHCI 1.0]
with 3x SATAs on raid-1 over reiserfs (although mine is a genuine Intel board).
>> My config hasn't changed since 2.6.14 and I never encountered such an
>> error under 2.6.14.
>>
>> My system configuration: I have two SATA drives, /dev/sdb7 is the root
>> partition using reiserfs.
>> SATA, SCSI and reiserfs are compiled into the kernel.
Ditto.
>> My kernel command line is just: root=/dev/sdb7
>>
>> lspci -v gives for the SATA controller:
>>
>> 0000:00:1f.2 IDE interface: Intel Corp. 82801FB/FW (ICH6/ICH6W) SATA
>> Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
>> Subsystem: Micro-Star International Co., Ltd.: Unknown device
>> 7091
>> Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
>> I/O ports at e400 [size=8]
>> I/O ports at e500 [size=4]
>> I/O ports at e600 [size=8]
>> I/O ports at e700 [size=4]
>> I/O ports at e800 [size=16]
>> Capabilities: [70] Power Management version 2
>>
>>
>> Sometimes the kernel boots without an error and sometimes it just
My problem is also somewhat intermittent but fairly common, which makes it more
difficult to track down than a completely reproduceable bug.
>> panics. I found out (using a camera, since I can't log the sys messages
>> at this time) that there is one big difference between booting the
>> kernel with and without a panic.
Andre: serial console is your friend ;)
reuben
next prev parent reply other threads:[~2006-01-12 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 18:14 Kernel 2.6.15 sometimes only detects one of two SATA drives and panics Andre Hessling
2006-01-11 18:29 ` Lee Revell
2006-01-11 18:35 ` Andre Hessling
2006-01-12 7:40 ` Andrew Morton
2006-01-12 8:02 ` Reuben Farrelly [this message]
2006-01-12 12:53 ` Andre Hessling
2006-01-12 7:49 ` YOSHIFUJI Hideaki / 吉藤英明
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=43C60D01.5080808@reub.net \
--to=reuben-lkml@reub.net \
--cc=ahessling@gmx.de \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.