Adam Belay wrote: >On Wed, Aug 20, 2003 at 06:25:59PM -0500, Wes Janzen wrote: > > >>So sad... Ever since I started with kernel 2.5.69, the kernel has been >>properly reserving IRQ 5 for ISA, as set in my BIOS. >> >> > >The reserve IRQ feature in your BIOS should not effect the linux kernel. >It is strictly internal to your BIOS. Therefore if linux assigns >resources it probably won't reserve irq 5. This problem may be the >result of a change in the way linux assigns resources. > > Well, as odd as this may be, for versions 2.5.69 thru 2.6.0-test3-mm2, adjusting my BIOS changed how the IRQs were allocated. Apparently something was using that information, whether that is supposed to happen or not. In the BIOS I used the "set resources manually" to reserve 7 and 5 for ISA...and it made a difference with 2.5.69 thru 2.6.0-test3-mm2. I haven't tried setting it back to auto, but I suspect it has no effect anymore as you state. i.e., with my BIOS set to auto configure resources, 2.5.69 thru 2.6.0-test3-mm2 would allocate IRQ's in much the same way 2.6.0-test3-mm3 is right now even with my BIOS settings set manually ;-) Well, I can't say that for sure, because I can only tell how the IRQ's are allocated for my two PDC20269 cards, the PCI USB 2.0 card, and the 1 onboard IDE I have enabled on my MVP3... The screen scrolled too fast to figure out what the NIC is using and it's clearly locked since I can't scroll up. Seems odd it doesn't complain about the conflict and tries to share an interrupt with an ISA device... I know it complained at least with 2.5.69 when I tried loading the module before changing my BIOS settings. So, I'll give you those I know until I'm able to re-compile: IRQ DEVICE ___________________________ 5 PDC20269#1 7 Parport 9 OHCI HCD 10 EHCI HCD & PDC20269#2 14 VIA IDE#1 > > >>Unfortunately for me, it looks like 2.6.0-test3-mm3 is like 2.4.18 and >> >> > >In what kernel version did you first see this problem? > Well ;-) I thought I inferred 2.6.0-test3-mm3 well enough... I guess I left out the part about 2.5.69 thru 2.6.0-test3-mm2 working. I must have removed that part, sorry! >>ignores my BIOS settings, so it locks up trying to ativate my SB16 on >>boot (since IRQ 5 is used for IDE). Oddly it doesn't spit out any >>warnings, just locks up after "pnp: Device 00:01.03 activated". >> >> > >I'd imagine this is the result of the resource conflict, presumably with >your ide controller. More information would be needed. I'd like to see >/proc/interrupts, dmesg, and lspci -vv (when the sb driver is not loaded). > I tend to agree, that's always been the conflict before. The PCI devices use up all the IRQ's and then I can't get the SB16 on one it likes. I think it uses 10 or 12 in WinXP, but I'm not interested enough to confirm which. I know that the ALSA driver doesn't support those IRQs though. These are from 2.6.0-test3-mm2, I have to recompile because snd-sb16 isn't compiled as a module. With a K6-2 and GCC 3.3, that's going to take a little bit. Besides, once I attach my boot.msg log, this is going to be big. Concerning my boot log, because I have USB verbose enabled, the first part of the boot mesg has been deleted. You're probably more interested in those ACPI messages at the top... which are not there, but I've included it anyway. >cat /proc/interrupts: CPU0 0: 12297914 XT-PIC timer 1: 1773 XT-PIC i8042 2: 0 XT-PIC cascade 5: 11072 XT-PIC SoundBlaster 7: 2 XT-PIC parport0 8: 2 XT-PIC rtc 9: 29564 XT-PIC acpi, ohci-hcd, eth0 10: 72 XT-PIC ohci-hcd 11: 1495725 XT-PIC ide2, ide3, ehci_hcd, radeon@PCI:1:0:0 12: 1068 XT-PIC ide4, ide5 14: 13 XT-PIC ide0 NMI: 0 ERR: 0 >lspci -vv: rybBIT:/home/sprchkn # lspci -vv 00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 41) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Also, are you using acpi? If so, try the kernel parameter pci=noacpi and >also try disabling acpi completely. > Already tried pci=noacpi, I'll go first with the ALSA driver as a module and then pci=noacpi, then I'll disable ACPI, re-compile and post that too. > >Thanks, >Adam > Thanks, I'll send more when I have it. >- >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/ > > >