public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Vanoni <vanonim@alice.it>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.41 & 2.6.18.7 OK,   2.6.19.5 NOT,   2.6.18.8 KERNEL PANIC
Date: Sun, 25 Feb 2007 17:05:58 +0100	[thread overview]
Message-ID: <45E1B3E6.60403@alice.it> (raw)
In-Reply-To: <20070224201902.a2a7b3da.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Sat, 24 Feb 2007 16:44:20 +0100 Mario Vanoni wrote:
> 
>> 2.6.18.7 vanilla & 2.6.16.41 vanilla:
>> /dev/hda CD/DVD
>> /dev/hda1 / IDE HD 160GB
>> /dev/hda2 swap
>> /dev/sda1 /xyz SATA HD 320GB
>> /dev/sda2 swap
>> /dev/sdb1 /zzz SATA HD 320GB
>> /dev/sdb2 swap
>> /dev/sdc1 /usb USB KEY 512MB

> For 2.6.19.*, does .config contain any CONFIG_ATA* entries?
> FYI, in 2.6.19, CONFIG_SCSI_SATA* config symbols were renamed to
> CONFIG_ATA*, so just using an oldconfig won't be sufficient
> for SATA support.

You are 100% right, I was lazy, thanks for the gentle blame.
2.6.19.5 vanilla works perfectly, 2.6.20.1 vanilla too!

>> ---
>> 2.6.18.8 vanilla: !!!
>> screen eating leftmost characters, then
>> kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(3,65)
>> POWER SWITCH ultima ratio
>> ---

Strange error, due to a partially corrupted MBR (?):
2.6.19.5 with incorrect .config, lilo, SATA missing
reboot with old 2.6.18.7, OK
2.6.18.8 with old .config from 2.6.18.6,
lilo objects not seeing /dev/sdb and /dev/sdc,
reboot and kernel panic,
reboot with 2.6.18.7, OK
2.6.18.8 make mrproper and rm -r /lib/modules/2.6.18.8
make bzImage etc., lilo: 2.6.18.8 works perfectly.

Many thanks and kind regards
Mario Vanoni

  reply	other threads:[~2007-02-25 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 15:44 2.6.16.41 & 2.6.18.7 OK, 2.6.19.5 NOT, 2.6.18.8 KERNEL PANIC Mario Vanoni
2007-02-25  4:19 ` Randy Dunlap
2007-02-25 16:05   ` Mario Vanoni [this message]
2007-02-25 23:44     ` Randy Dunlap

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=45E1B3E6.60403@alice.it \
    --to=vanonim@alice.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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