Re: Minor things: swi_net: unregistered isr number
Matthew N. Dodd wrote: On Thu, 25 Apr 2002, Peter Wemm wrote: This is well known. If we recieve an ARP frame before we sent one, then we print this. eg: a broadcast ARP packet will trigger it. dhclient etc use bpf etc so ARP isn't initialized at this point. We could just put this block of code from arp_rtrequest() into arp_init(). LIST_INIT(llinfo_arp); timeout(arptimer, (caddr_t)0, hz); register_netisr(NETISR_ARP, arpintr); I'm not sure why it should to be in arp_rtrequest() in the first place. You do not want the timer running and using cpu if you are not using ARP (eg: ppp only). Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Minor things: swi_net: unregistered isr number
On 25-Apr-2002 Jan Stocker wrote: My -current system gives me a swi_net: unregistered isr number: 18. too. I cant find any reply to this old subject. May anyone know where it comes from? It seems to trigger whenever there is traffic while the IP is 0.0.0.0, even for non-DHCP stuff. I'm not sure what is causing it. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Minor things: swi_net: unregistered isr number
John Baldwin wrote: On 25-Apr-2002 Jan Stocker wrote: My -current system gives me a swi_net: unregistered isr number: 18. too. I cant find any reply to this old subject. May anyone know where it comes from? It seems to trigger whenever there is traffic while the IP is 0.0.0.0, even for non-DHCP stuff. I'm not sure what is causing it. This is well known. If we recieve an ARP frame before we sent one, then we print this. eg: a broadcast ARP packet will trigger it. dhclient etc use bpf etc so ARP isn't initialized at this point. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Minor things: swi_net: unregistered isr number
John Baldwin wrote: On 25-Apr-2002 Jan Stocker wrote: My -current system gives me a swi_net: unregistered isr number: 18. too. I cant find any reply to this old subject. May anyone know where it comes from? It seems to trigger whenever there is traffic while the IP is 0.0.0.0, even for non-DHCP stuff. I'm not sure what is causing it. Protocol 18 is ARP. The message only happens when the network code is up, but before the ARP protocol handler is registered. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Minor things: swi_net: unregistered isr number
On Thu, 25 Apr 2002, Peter Wemm wrote: This is well known. If we recieve an ARP frame before we sent one, then we print this. eg: a broadcast ARP packet will trigger it. dhclient etc use bpf etc so ARP isn't initialized at this point. We could just put this block of code from arp_rtrequest() into arp_init(). LIST_INIT(llinfo_arp); timeout(arptimer, (caddr_t)0, hz); register_netisr(NETISR_ARP, arpintr); I'm not sure why it should to be in arp_rtrequest() in the first place. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Minor things: swi_net: unregistered isr number
If this might be of interest: kernel built 07.feb at boot time... | Doing initial network setup: hostname. * swi_net: unregistered isr number: 18. | xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 | options=3rxcsum,txcsum [...] This is (probably) the dhclient being run at this time, maybe. Should I be bothered by the following? unknown: IBM Enhanced (101/102-key) KC can't assign resources unknown: Microsoft PS/2 Mouse can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: LPT printer port can't assign resources unknown: Floppy Controller can't assign resources this is after all of these have been detected and assigned (sio0, sio1, etc) ata3: Generic ESDI/IDE/ATA controller at port 0x36e-0x36f,0x168-0x16f irq 10 o n isa0 Where did that come from, and why don't I know about it? I know about: ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 and -stable makes no claim I have a third ata controller... machine is ancient digital venturis 575 pc thanks barry bouwsma To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Minor things: swi_net: unregistered isr number
If this might be of interest: kernel built 07.feb at boot time... | Doing initial network setup: hostname. * swi_net: unregistered isr number: 18. | xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 | options=3rxcsum,txcsum [...] This is (probably) the dhclient being run at this time, maybe. Should I be bothered by the following? unknown: IBM Enhanced (101/102-key) KC can't assign resources unknown: Microsoft PS/2 Mouse can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: LPT printer port can't assign resources unknown: Floppy Controller can't assign resources this is after all of these have been detected and assigned (sio0, sio1, etc) ata3: Generic ESDI/IDE/ATA controller at port 0x36e-0x36f,0x168-0x16f irq 10 o n isa0 Where did that come from, and why don't I know about it? I know about: ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 and -stable makes no claim I have a third ata controller... machine is ancient digital venturis 575 pc thanks barry bouwsma To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
