Messages in this thread |  | | Date | Sat, 14 Sep 2002 15:36:19 +0200 | From | Jens Axboe <> | Subject | Re: 34-bk current ide problems - unexpected interrupt |
| |
On Fri, Sep 13 2002, Ed Tomlinson wrote: > On September 13, 2002 09:42 pm, Ed Tomlinson wrote: > > Hi, > > > > To check if the problem I am seeing is with the port to 2.5 I tried > > 2.4.20-pre5-ac4 and 2.4.20-pre5-ac6. Both booted correctly. > > > > Now to try 2.5.34+bk without Andrew's mm patch. If that fails what > > debugging info would help solve the unexpected interrupt problem? > > to summerize > > 2.4.20-pre5-ac4 works > 2.4.20-pre5-ac5 works > 2.5.34-mm1 works (without Jens ide port of pre5-ac4) > 2.5.34-mm2 fails with unexpected interrupt loop > 2.5.34-bk current fails with unexpected interrupt loop
Hmm, I just plopped in a 20267 here and it works perfectly:
PDC20267: IDE controller at PCI slot 00:0c.0 PDC20267: chipset revision 2 PDC20267: not 100% native mode: will probe irqs later PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:DMA hde: IBM-DTLA-307030, ATA DISK drive ide2 at 0xb400-0xb407,0xb002 on irq 16 hde: host protected area => 1 hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100) hde: hde1 hde2 < hde5 >
> Removing the printk from ide.c does _not_ cure the problem. The ide > setting between 2.4 and 2.5 were as identical as I can make them.
Can you please send me the config settings?
> Notice that 2.4 orders the boot differently. Wonder if this is significant?
That's expected.
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |