current errors
Any ideas as to the cause of the following errors in current. I have (2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card is an AGP TNT2 video card. Apr 17 23:07:42 telecast /kernel: unknown0: PNP at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 Apr 17 23:07:42 telecast /kernel: unknown1: PNP0200 at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 Apr 17 23:07:42 telecast /kernel: unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 Apr 17 23:07:42 telecast /kernel: unknown3: PNP0b00 at port 0x70-0x71 irq 8 on isa0 Apr 17 23:07:42 telecast /kernel: unknown: PNP0303 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown4: PNP0800 at port 0x61 on isa0 Apr 17 23:07:42 telecast /kernel: unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 Apr 17 23:07:42 telecast /kernel: unknown6: PNP0c01 at iomem 0-0x9,0xfffe-0x,0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x7ff on isa0 Apr 17 23:07:42 telecast /kernel: unknown7: PNP0c02 at iomem 0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xf on isa0 Apr 17 23:07:42 telecast /kernel: unknown: PNP0a03 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0f13 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0501 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0700 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0400 can't assign resources Apr 17 23:07:42 telecast /kernel: APIC_IO: Testing 8254 interrupt delivery Apr 17 23:07:42 telecast /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Apr 17 23:07:42 telecast /kernel: SMP: AP CPU #1 Launched! Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current errors
On Tue, 18 Apr 2000 13:37:21 -0400, Ted Sikora [EMAIL PROTECTED] said: Any ideas as to the cause of the following errors in current. Harmless. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current errors
Garrett Wollman wrote: On Tue, 18 Apr 2000 13:37:21 -0400, Ted Sikora [EMAIL PROTECTED] said: Any ideas as to the cause of the following errors in current. Harmless. Not totally harmless. PNPBIOS is causing a conflict, which is causing a kernel panic on my system. Since I haven't had a chance to track it down, I can't be more specific. More over, I don't think that device PCM should automaticly enable PNPBIOS. Bob Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current errors
In message [EMAIL PROTECTED] Ted Sikora writes: : Any ideas as to the cause of the following errors in current. I have : (2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card : is an AGP TNT2 video card. I don't see any error messages here :-). The problem is that PNPBIOS was turned on, which is trying to assign resources to devices. Trouble is PNP0303, PNP0a03, PNP0f13, PNP0501, PNP0700 and PNP0400 defined resources that were claimed previously by devices. There are bugs in PNPBIOS right now where it sorts these devices with the PNP ISA cards. Instead, it should sort them to the front of the list. However, once that done, then other problems with the device attachment system will be exposted (namely that these devices will appear one unit too high and you'll get messages about the 0th unit not being able to allocate them). You can fix that in many ways, but none of them satsifying. Once that's fixed, you'll discover that many of the PNP devices describe mobo devices that haven't traditionally had device drivers. After that, you'll be very close to being able to boot w/o this noise :-) People have said they are working on it. It is a complicated mess that's not easy to unwind. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current errors
Warner Losh wrote: In message [EMAIL PROTECTED] Bob Martin writes: : Not totally harmless. PNPBIOS is causing a conflict, which is causing a : kernel panic on my system. Since I haven't had a chance to track it : down, I can't be more specific. PNPBIOS isn't causing the conflict. It is merely allowing us to detect the conflict. PNPBIOS just reads a table from the BIOS of devices that are hard wired. Confict or not, my system boots and runs flawlessly without PNPBIOS. It kernel panics with it. (At the moment, it looks like PNPBIOS and SIO are both claiming the same modem...) Bob Martin -- "I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." -- Albert Einstein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
