Re: 2.6.25-mm1: Failing to probe IDE interface

From: Mel Gorman
Date: Tue Apr 29 2008 - 13:06:52 EST


On (29/04/08 16:49), Mel Gorman didst pronounce:
> On (29/04/08 10:43), Mel Gorman didst pronounce:
> > On (28/04/08 20:44), Bartlomiej Zolnierkiewicz didst pronounce:
> > >
> > > Hi,
> > >
> > > On Monday 28 April 2008, Mel Gorman wrote:
> > > > An old T21 is failing to boot and the relevant message appears to be
> > > >
> > > > [ 1.929536] Probing IDE interface ide0...
> > > > [ 36.939317] ide0: Wait for ready failed before probe !
> > > > [ 37.502676] ide0: DISABLED, NO IRQ
> > > > [ 37.506356] ide0: failed to initialize IDE interface
> > > >
> > > > The owner of ide-mm-ide-add-struct-ide_io_ports-take-2.patch with the
> > > > "DISABLED, NO IRQ" message is cc'd. I've attached the config, full boot log
> > > > and lspci -v for the machine in question. I'll start reverting some of the
> > > > these patches to see if ide-mm-ide-add-struct-ide_io_ports-take-2.patch
> > > > is really the culprit.
> > >
> > > Please try reverting ide-fix-hwif-s-initialization.patch first - it has
> > > already been dropped from IDE tree because people were reporting problems
> > > similar to the one encountered by you.
> > >
> >
> > Thanks.
> >
> > I reverted this patch and ide-mm-ide-make-ide_hwifs-static.patch (for compile
> > breakage reasons). It's better but still fails to find the IDE device.
>
> Interestingly, bisection firmly blames this patch and QEMU boots with the two
> patches reverted but fails with them applied so that patch does cause problems.
> The failure on the laptop must be depending on some follow-on patch. I tried
> a hatchet-job revert of the IDE patches between IDE-START and IDE-END in
> the series file and it similarly fails to probe the IDE devices. So either
> I made a mess of the reverts (strong possibility) or there is more than one
> problem patch.
>

The third patch that needed reverting was
gregkh-pci-pci-clean-up-resource-alignment-management.patch (owners added
to cc). The relevant hint in the a diff between a broken and working bootlog was;

system 00:09: ioport range 0x15e0-0x15ef has been reserved
+ PCI: bogus alignment of resource 7 [100:1ff] (flags 100) of 0000:00:02.0
+ PCI: bogus alignment of resource 8 [100:1ff] (flags 100) of 0000:00:02.0
+ PCI: bogus alignment of resource 9 [4000000:7ffffff] (flags 1200) of 0000:00:02.0
+ PCI: bogus alignment of resource 10 [4000000:7ffffff] (flags 200) of 0000:00:02.0
+ PCI: bogus alignment of resource 7 [100:1ff] (flags 100) of 0000:00:02.1
+ PCI: bogus alignment of resource 8 [100:1ff] (flags 100) of 0000:00:02.1
+ PCI: bogus alignment of resource 9 [4000000:7ffffff] (flags 1200) of 0000:00:02.1
+ PCI: bogus alignment of resource 10 [4000000:7ffffff] (flags 200) of 0000:00:02.1

With the resource alignment patch and the two IDE patches reverted, the
laptop is able to boot.

--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/