All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2-mm1: Can't mount root
Date: 28 Jul 2003 23:44:04 -0500	[thread overview]
Message-ID: <1059453844.4786.37.camel@localhost> (raw)
In-Reply-To: <20030728193633.1b2bc9d8.akpm@osdl.org>

-test1-mm2. Hadn't tried any -bk? in between.

Won't have time to do much tonight or tomorrow before evening, but I'll
test what I can.

On Mon, 2003-07-28 at 21:36, Andrew Morton wrote:
> Shawn <core@enodev.com> wrote:
> >
> > OK, mucho more info (no wonder root=/dev/hde5 no worky):
> >         VP_IDE: (ide_setup_pci_device:) Could not enable device
> > 
> > Found out my on board via pci ide was not getting initialized under
> > -test2-mm1, so I went looking for driver/ide/pci/via82cxxx in the diffs.
> > I found this in the -test2 diff:
> > -                                    (((u >> i) & 7) < 8))) {
> > +                                    (((u >> i) & 7) < 6))) {
> > ...and reversing it did not change anything.
> > 
> > The only other diff I could think might matter to 
> > drivers/ide/setup-pci.c
> > -static unsigned long __init ide_get_or_set_dma_base (ide_hwif_t *hwif)
> > +static unsigned long ide_get_or_set_dma_base (ide_hwif_t *hwif)
> > ...which does not look like it should kill my via ide...
> > 
> 
> OK, looks like breakage at the PCI level: pci_enable_device_bars() is
> failing; something below pcibios_enable_device().
> 
> What was the most recent kernel which works?

  reply	other threads:[~2003-07-29  4:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 21:43 2.6.0-test2-mm1: Can't mount root Shawn
2003-07-28 21:47 ` Andrew Morton
2003-07-28 22:06   ` Shawn
2003-07-28 22:02     ` Andrew Morton
2003-07-28 22:39       ` Shawn
2003-07-29  2:04       ` Shawn
2003-07-29  2:36         ` Andrew Morton
2003-07-29  4:44           ` Shawn [this message]
2003-07-29  5:32           ` Shawn
2003-07-29  5:47             ` Andrew Morton
2003-07-29  6:14               ` Shawn

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=1059453844.4786.37.camel@localhost \
    --to=core@enodev.com \
    --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.