linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Kovid Goyal <kovid@theory.caltech.edu>
Cc: linux-ide@vger.kernel.org
Subject: Re: [2.6.18,19] SATA boot problems (ICH6/ICH6W)
Date: Wed, 20 Dec 2006 09:44:45 +0900	[thread overview]
Message-ID: <4588877D.1000400@gmail.com> (raw)
In-Reply-To: <200612111003.39928.kovid@theory.caltech.edu>

Kovid Goyal wrote:
> Hi,
> 
> I'm having problems booting from a SATA disk with 2.6.19.
> Grub loads fine, but when the kernel boots, it *sometimes* ends up with
> VFS: Cannot open root device "sda5" or unknown-block(0,0). 
> 
> This issue appears to be identical with the one reported in 
> http://lkml.org/lkml/2006/10/19/327 except that 2.6.19 did not fix it for me. 
> In fact, it made it worse. The timeouts reported in that thread are still 
> present and with 2.6.19 the fraction of unsuccessful boots has increased from 
> 30% to 80%. I often have to reboot my machine 3 times in a row before it 
> succeeds. I have tried both vanilla 2.6.19 and gentoo-sources-2.6.19-r1
> 
> To summarize: My machine stalls for nearly a minute on all boots and the root 
> filesystem fails to mount on 80% of the boots. This problem first manifested 
> itself when I switched to 2.6.18 and has become worse with 2.6.19. 
> 
> The controller:
> 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA 
> Controller (rev 03)
> 
> I don't know how to get the logs from an unsuccessful boot. Here is
> an extract from the logs of a successful boot (in which the timeout is 
> present):

Does goving back to 2.6.17 fix the problem?  Also, please report the
result of 'smartctl -d ata -a /dev/sdX' where sdX is the problematic drive.

-- 
tejun

  reply	other threads:[~2006-12-20  0:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 18:03 [2.6.18,19] SATA boot problems (ICH6/ICH6W) Kovid Goyal
2006-12-20  0:44 ` Tejun Heo [this message]
2006-12-20  2:00   ` Kovid Goyal
2006-12-20  2:13     ` Tejun Heo
2006-12-20  4:56       ` Kovid Goyal
2007-01-11 23:32       ` Kovid Goyal
2007-01-13  2:19         ` Tejun Heo
2006-12-20  3:29   ` Gary Hade
2006-12-20  3:53     ` Tejun Heo
2006-12-20  4:30       ` Tejun Heo
2006-12-21 17:10       ` Gary Hade
2007-01-30  1:55         ` Gary Hade
2007-01-30  7:32           ` Tejun Heo
2007-01-30 23:37             ` Gary Hade
2007-01-31  0:54               ` Jeff Garzik
2007-01-31 11:00                 ` Tejun Heo
2007-01-31 12:20                   ` Alan
2007-01-31 13:16                     ` Tejun Heo
2007-01-31 15:24                       ` Jeff Garzik
2007-01-31 15:30                         ` Mark Lord
2007-01-31 10:44               ` Tejun Heo
2007-01-31 10:47                 ` Jeff Garzik
2007-01-31 11:00                   ` Tejun Heo
2007-02-01  0:49                 ` Gary Hade
2007-02-17  0:34               ` Gary Hade
2007-02-21 12:40                 ` Tejun Heo
2007-02-22  0:41                   ` Gary Hade
2007-02-23  0:32                   ` Gary Hade
2007-01-23 21:49 ` danieljzhang

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=4588877D.1000400@gmail.com \
    --to=htejun@gmail.com \
    --cc=kovid@theory.caltech.edu \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).