Date: Wed, 10 Sep 2003 20:53:13 -0500 From: Jerry Lundy <jwlundy@swbell.net> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-mobile@freebsd.org Subject: Re: O2Micro insertion / removal undetected Message-ID: <3F5FD589.8050201@swbell.net> References: <3F5AA46F.5050901@swbell.net> <20030909.154555.78710221.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greetings. You are correct: the wireless card does not work. I can query it and set its parameters, but it fails to function otherwise. When I ping a wired host, I see repeated arp requests from the wireless client. The wireless client appears to be blind to the arp responses. Additionally, while attempting to ping from the wireless host, it shows a series of kernel level syslog messages: an0: device timeout an0: device timeout an0: discard frame w/o leading ethernet header (len 12 pkt len 12) an0: discard frame w/o leading ethernet header (len 12 pkt len 12) I've seen mention of interrupt routing problems before. Is this related to the "APIC PCI interrupt routing support" that is on the Must Resolve list for 5.2-RELEASE? Are there any workarounds? Thanks, Jerry Lundy M. Warner Losh wrote: > In message: <3F5AA46F.5050901@swbell.net> > Jerry Lundy <jwlundy@swbell.net> writes: > : From reading the list I get the impression that O2Micro devices have > : been difficult to support. I'm just about googled out. Am I missing > : something basic? > > Yes. Up until very recently, I've not had access to O2Micro > hardware. Now that I have that access, I've not had time to > investigate the issues with NEWCARD. > > It does sound like your issues might be related to interrupt routing. > Does the wi card actually work when you've included the wi card in the > socket at boot? > > Warner > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F5FD589.8050201>