Date: Thu, 28 Jun 2001 23:20:19 -0700 (PDT) From: Alan Larson <larson@w6yx.stanford.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/28506: problems with wi0 driver Message-ID: <200106290620.f5T6KJq95473@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 28506 >Category: kern >Synopsis: problems with wi0 driver >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 28 23:30:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Alan Larson >Release: 4.3-release >Organization: >Environment: FreeBSD 4.3-RELEASE ... >Description: Using an HP Omnibook 6000, the wi0 device doesn't work. It gets many errors of the form: wi0: tx buffer allocation failed wi0: xmit failed wi0: device timeout sometimes also wi0: mgmt. buffer allocation failed building test systems, with extra print messages in the driver, I find that the calls to wi_alloc_nicmem are failing, returning EIO. This comes from wi_seek in wi_alloc_nicmem, which is returning ETIMEDOUT. This is because the CSR_READ_2 of offreg is returning WI_OFF_ERR (0x4000) and continuing to return that, so the loop never gets a non-error reply. Tracing back further, we find that this occurs when the value of 'id' is 0, as returned by the read of WI_ALLOC_FID back in wi_alloc_nicmem. If we get a 0 for id, which we apparently get when we call wi_alloc_nicmem from wi_init, the wi_seek will fail. I have no idea why this happens. Bizarrely, when I first tried using this machine, I had the same problem for several tries of loading the system, then eventually, all the parameters got sorted out, and it worked -- until the hard disk stopped working... (It spins, seeks, sounds fine, but won't read.) The relaoded system now cannot talk to the wireless card. The card works just fine in the same system running windows 2000. The card is loaded with the current firmware. PLEASE HELP. IF I CAN'T FIX THIS, I HAVE TO USE WIN2K -- CLEARLY A TERRIBLE FATE. >How-To-Repeat: Boot the computer, and after setting the encryption parameters (necessary), do an ifconfig wi0 <address> .. and you will start getting errors. If that isn't enough, try using the interface. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106290620.f5T6KJq95473>