Re: promise controller resource alloc problems with ~2.6.8

From: CaT
Date: Tue Oct 12 2004 - 07:54:43 EST


On Sun, Oct 10, 2004 at 10:00:32AM -0700, Linus Torvalds wrote:
> which has a "insert_resource()" in it. That "insert_resource()" should be
> a "request_resource()" (and for you it won't matter, but other people will
> likely want to additionally apply Shaohua's patch to put in ACPI resources
> last).
>
> Hope this clears it all up. Knock wood.

Well with all the fun and the mind bendiness of the results of my
earlier tests I thought that there might be a slim chance that something
got buggered up with the lifetime of patching that particular kernel
tree got on my system and since rc4 was out I decided to start afresh.

I untarred 2.6.5, patched to 2.6.9-rc4, turned on the PCI debugging as
per request, compiled and rebooted. End result?

PDC20267: IDE controller at PCI slot 0000:00:0d.0
IRQ for 0000:00:0d.0:0 -> PIRQ 60, mask 0ef8, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:0d.0
PDC20267: chipset revision 2
PDC20267: 100% native mode on irq 11
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x1080-0x1087, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x1088-0x108f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: IC35L060AVV207-0, ATA DISK drive
ide2 at 0x10f0-0x10f7,0x1802 on irq 11
Probing IDE interface ide3...
hdh: ST3200822A, ATA DISK drive
ide3 at 0x10f8-0x10ff,0x1806 on irq 11

It worked!

Now thinking that I may have just right royally buggered up I compiled
rc3 again, starting from a totally fresh tree like I did with rc4 and
the problem was still there. No promise card. (phew... kinda)

So basically, something got fixed between rc3 and rc4. Personally, I
call shenanigans.

--
Red herrings strewn hither and yon.
-
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/