public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: 2.6.22-git17 boot failure
Date: Mon, 23 Jul 2007 01:27:37 +0100	[thread overview]
Message-ID: <46A3F5F9.2040501@blueyonder.co.uk> (raw)

Tilman Schmidt: wrote
 > On my test machine with a Pentium D 940 processor, Intel DQ965GF
 > mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
 > to come up because it cannot find the disk drives. Same issue
 > with a clone of the 'linus' git tree. Anything known?
I don't know if this is any indication.
I have no SATA drives, but I noticed booting 2.6.22-git16 x86_64 I got 
error messages with "sata slow in responding" also "EH timeout" and my 
IDE drive /dev/sda1 giving ext3 errors, ending in a  filesystem not 
clean prompt. Did fsck.ext3 using openSUSE 10.3Alpha3 DVD, that fixed a 
string of wrong inode errors. Booted an earlier kernel and turned off 
loading the sata_nv module, then 2.6.22-git16 and later 2.6.22-git17 
booted without problems, so I put it down to a motherboard problem with 
the SATA.
Regards
Sid.

-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks



             reply	other threads:[~2007-07-23  0:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23  0:27 Sid Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-22 23:47 2.6.22-git17 boot failure Tilman Schmidt
2007-07-23  0:31 ` Gabriel C
2007-07-23  0:52 ` Tilman Schmidt
2007-07-23  8:51   ` Jeremy Fitzhardinge
2007-07-23 10:25     ` Tilman Schmidt
2007-07-23 14:51       ` Jeremy Fitzhardinge
2007-07-23 19:42         ` Tilman Schmidt
2007-07-23 20:32           ` Jeremy Fitzhardinge
2007-07-23 23:02             ` Tilman Schmidt
2007-07-24  0:14               ` Jeremy Fitzhardinge
2007-07-24  8:51                 ` Tilman Schmidt
2007-07-24  8:59                   ` Jeremy Fitzhardinge
2007-07-24  9:10                 ` Andi Kleen
2007-07-24  9:56                   ` Olaf Hering
2007-07-24 10:36                     ` Tilman Schmidt
2007-07-24 13:45                       ` Olaf Hering
2007-07-24 15:45                         ` Jeremy Fitzhardinge
2007-07-24 15:47                           ` Andi Kleen
2007-07-24 18:08                     ` Tilman Schmidt
2007-07-24 19:02                       ` Jeremy Fitzhardinge
2007-07-24 19:12                         ` Andi Kleen
2007-07-24 19:15                           ` Jeremy Fitzhardinge
2007-07-24 20:48                           ` Tilman Schmidt
2007-07-24 21:20                             ` Jeremy Fitzhardinge
2007-07-24  3:46               ` Jeremy Fitzhardinge
2007-07-23  9:25   ` Andi Kleen

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=46A3F5F9.2040501@blueyonder.co.uk \
    --to=g3vbv@blueyonder.co.uk \
    --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