On Tue, Jan 02, 2001 at 10:56:27AM -0800, Linus Torvalds wrote:
> Anyway, I suspect that the "fe"/"ff" values are specified by MS (no way to
> know, as the docs are obviously NDA'd), which means that it would be
> interesting to hear whether the problem is fixed by something like this:
>
> In the file arch/i386/kernel/pci-irq.c, around line 240, there's a
> function called pirq_via_get(). Right now it just does a
> "read_config_nybble()", and I'd ask you to add these two magic lines to
> the beginning of it:
>
> if ((pirq & 0xf0) == 0xf0)
> return pirq & 0xf;
>
> and please tell me if that changes/fixes the problem for you.
It seems to change the problem, but fixes it in most ways. I can
give you a dmesg output if you want one. That fixed the "confused
drive" errors and lets me boot, but now hdc and hdd are timing out
because of the reasons that they timed out in 2.2.
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 14
is what I get now. I haven't tried this yet, but I'm assuming a simple
re-addition of 'ide1=0x170,0x376,15' to the kernel options should put
ide1 back on irq 15 where it belongs (I haven't rebooted yet because I
was just so excited that this works. Geez your smart, Linus!)
> Oh, and could you pass me the output of /proc/pci while you're at it, so
> that I can match it up with your pirq table. That corrupted slot 4 entry
> still makes me go "Hmm..".
I've attached the output I got from doing cat /proc/pci from
2.4.0-prerelease. Because of a subtle configuration difference between
the two, there is a few I/O differences and output differences (because
of the jump in kernel versions) from 2.2.18pre21 (I really should
upgrade to 2.2.18).
Thanks,
-- | Evan Thompson | ICQ: 2233067 | | Freelance Computer Nerd | AIM: Evaner517 | | evaner@bigfoot.com | Yahoo!: evanat | | http://evaner.penguinpowered.com | MSN: evaner517 |
This archive was generated by hypermail 2b29 : Sun Jan 07 2001 - 21:00:14 EST