Date: Fri, 03 Aug 2001 21:30:22 -0700 From: Mike Smith <msmith@freebsd.org> To: lists <lists@security.za.net> Cc: Mike Smith <msmith@freebsd.org>, Warner Losh <imp@harmony.village.org>, freebsd-hackers@freebsd.org Subject: Re: NewCard / pccbb Message-ID: <200108040430.f744UMg01709@mass.dis.org> In-Reply-To: Your message of "Fri, 03 Aug 2001 14:49:27 %2B0200." <Pine.BSF.4.21.0108031449100.43318-100000@security.za.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, now I need your dmesg again, since it's been trimmed and I've lost it. I also need to know what slots you have things in. Please don't cut the $PIR output off this message when you reply. Note that your system is something of a pathalogical worst-case; no PCI recommended interrupts, all the 'major' interrupts available for each slot. It's not improbable that the table is wrong or buggy too. > Here we go, the output as requested: > > $PIR table at 0x2812f7c0 version 1.0 > PCI interrupt router at 0:3.8 vendor 0x1106 device 0x686 > PCI-only interrupts [ ] > entry bus slot device > 00: 00 00 01 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] > INTB 02 [ 3 4 5 7 9 10 11 12 14 15] > INTC 03 [ 3 4 5 7 9 10 11 12 14 15] > INTD 05 [ 3 4 5 7 9 10 11 12 14 15] > 01: 00 00 07 INTA fe [ 14 ] > INTB ff [ 15] > INTC 03 [ 3 4 5 7 9 10 11 12 14 15] > INTD 05 [ 3 4 5 7 9 10 11 12 14 15] > 02: 00 01 09 INTA 02 [ 3 4 5 7 9 10 11 12 14 15] > INTB 03 [ 3 4 5 7 9 10 11 12 14 15] > INTC 05 [ 3 4 5 7 9 10 11 12 14 15] > INTD 01 [ 3 4 5 7 9 10 11 12 14 15] > 03: 00 02 10 INTA 03 [ 3 4 5 7 9 10 11 12 14 15] > INTB 05 [ 3 4 5 7 9 10 11 12 14 15] > INTC 01 [ 3 4 5 7 9 10 11 12 14 15] > INTD 02 [ 3 4 5 7 9 10 11 12 14 15] > 04: 00 03 11 INTA 05 [ 3 4 5 7 9 10 11 12 14 15] > INTB 01 [ 3 4 5 7 9 10 11 12 14 15] > INTC 02 [ 3 4 5 7 9 10 11 12 14 15] > INTD 03 [ 3 4 5 7 9 10 11 12 14 15] > 05: 00 00 12 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] > INTB 00 [ ] > INTC 00 [ ] > INTD 00 [ ] > > > Thanks > > Andrew > On Fri, 3 Aug 2001, Mike Smith wrote: > > > > Tried the patch, interesting thing, for some reason or other its always > > > routing the IRQ to the same IRQ as the realtek network card I have in > > > here, and with the patch in (before nothing worked at all on the pccbb), > > > now if the network card is in slot0 it doesnt work, and the wavelan does, > > > if the wavelan comes first on the pcibus it doesnt work and the network > > > card does. For some reason it always seems to be trying to share an IRQ > > > between these 2, any reason for this? > > > > Yeah; that seems to be the way your system's interrupt routing is set up. > > > > Get http://people.freebsd.org/~msmith/pir.c, build and run it and let's > > look at the output. > > > > -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > > > > > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108040430.f744UMg01709>