From: Fabio Coatti <cova@ferrara.linux.it>
To: Tejun Heo <htejun@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: SATA ICH5 not detected at boot, mm-kernels
Date: Mon, 6 Nov 2006 14:18:06 +0100 [thread overview]
Message-ID: <200611061418.07470.cova@ferrara.linux.it> (raw)
In-Reply-To: <454F2E0F.3010804@gmail.com>
Alle 13:43, lunedì 6 novembre 2006, Tejun Heo ha scritto:
> >> (320073 MB)
> >> Nov 5 13:26:37 kefk sdc: Write Protect is off
> >
> > And why doesn't -mm report the same conflict? I assume the .config is
> > the same?
>
> Also, please post full dmesg of both kernels.
Sure; now I'm far from the afflicted machine, but I'll post dmesg and .config
for all kernels (I've to use serial console debug for the non working one:
the non working drive,unfortunately, is needed to have machine up and
running :) .).
I'm pretty sure that the configs between 2.6.18-mm3 and 2.6.19-rcXmmY are the
same; I've compiled newer kernel using make oldconfig based on
working .config. But in the last days I've tweaked the configs trying to make
it work, so I'll start a fresh build to avoid any doubt. I'll do this as soon
as I'm again near the machine (I've no remote maintenance facility on this
machine)
--
Fabio "Cova" Coatti http://members.ferrara.linux.it/cova
Ferrara Linux Users Group http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646 BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.
next prev parent reply other threads:[~2006-11-06 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 14:36 SATA ICH5 not detected at boot, mm-kernels Fabio Coatti
2006-11-06 0:17 ` Andrew Morton
2006-11-06 12:43 ` Tejun Heo
2006-11-06 13:18 ` Fabio Coatti [this message]
2006-11-13 9:17 ` Fabio Coatti
2006-11-13 21:29 ` Andrew Morton
2006-11-14 21:52 ` Fabio Coatti
2006-11-14 22:45 ` Andrew Morton
2006-11-12 11:09 ` Fabio Coatti
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=200611061418.07470.cova@ferrara.linux.it \
--to=cova@ferrara.linux.it \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox