Bug 122597 - [iwi] Intel iwi fails after 3 - 4 hours of use"firmware stuck in state 4"
Summary: [iwi] Intel iwi fails after 3 - 4 hours of use"firmware stuck in state 4"
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Andrew Thompson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-09 15:30 UTC by Rick Sprague
Modified: 2018-05-28 19:44 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Sprague 2008-04-09 15:30:00 UTC
I've not had this problem under 6.x or WinXP.  I've seen other posts in newsgroups concerning this issue w/ no resolution other than "somebody should send a PR".

Typically it will take 4 hours and then I get the following:

Apr  9 01:56:12 inspiron_iwi0 kernel: iwi0: firmware stuck in state 4, resetting

Sometimes, it will only take 2.5-3 hours under heavy use.  I just don't know what triggers the failure.  I've been hobbling along w/ "netif restart"s

rc.conf:
-------
hostname=inspiron_iwi0.sprague.com
ifconfig_iwi0="WPA DHCP"
ifconfig_iwi0_alias0="inet 192.168.1.8 netmask 255.255.255.0"
ifconfig_iwi0_alias1="inet 10.0.2.15 netmask 255.255.255.0"

How-To-Repeat: Failure occurs after ~4 hours use, to 2.5-3hr under heavy use.
Comment 1 Andrew Thompson freebsd_committer 2008-04-09 19:08:06 UTC
> >Description:
> Typically it will take 4 hours and then I get the following:
> 
> Apr  9 01:56:12 inspiron_iwi0 kernel: iwi0: firmware stuck in state 4, resetting

Can you please try 'ifconfig iwi0 -bgscan' and see if the problem goes
away.


cheers,
Andrew
Comment 2 Volker Werth freebsd_committer 2008-04-09 20:08:38 UTC
State Changed
From-To: open->feedback


Note that submitter has been asked for feedback.
Comment 3 Andrew Thompson freebsd_committer 2008-04-10 17:41:18 UTC
State Changed
From-To: feedback->analyzed

Rick has reported that -bgscan removes the problem, grabbing PR. 


Comment 4 Andrew Thompson freebsd_committer 2008-04-10 17:41:18 UTC
Responsible Changed
From-To: freebsd-bugs->thompsa

Rick has reported that -bgscan removes the problem, grabbing PR.
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:40 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.