Opened 6 days ago
Last modified 44 hours ago
#19289 assigned bug
Iprowifi4965 connection instability
| Reported by: | piusbird | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Network/iprowifi4965 | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
On build hrev58399, I get wifi disconnects when making http requests in beos native applications. Sometimes i get dumped into kdebug with complaints about mbufs and null pointers.
The hardware is a 2007 era Thinkpad T61 The 802.11n variant Crash cannot be replicated on wired Ethernet.
I can provide any other info you need. I'm lurking in IRC.. If you want to ping.
Device Info:
device Network controller [2|80|0]
vendor 8086: Intel Corporation device 4230: PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
---
Syslog
KERN: [net/iprowifi4965/0] ieee80211_ref_node (ht_send_action_ba_addba:3060) 0xffffffff812e0000<4c:19:5d:6f:5c:0e> refcnt 4 DAEMON 'DHCP': /dev/net/iprowifi4965/0: Timeout shift: 4000 msecs (try 4) DAEMON 'DHCP': /dev/net/iprowifi4965/0: Send DHCP_DISCOVER to 255.255.255.255:67 DAEMON 'DHCP': /dev/net/iprowifi4965/0: Received DHCP_OFFER from 192.168.1.1 DAEMON 'DHCP': /dev/net/iprowifi4965/0: Send DHCP_REQUEST for 192.168.1.181 to 255.255.255.255:67 DAEMON 'DHCP': /dev/net/iprowifi4965/0: Received DHCP_ACK from 192.168.1.1 DAEMON 'DHCP': /dev/net/iprowifi4965/0: DHCP status = No error KERN: [net/iprowifi4965/0] ieee80211_ref_node (ht_send_action_ba_addba:3060) 0xffffffff812e0000<4c:19:5d:6f:5c:0e> refcnt 4 KERN: [net/iprowifi4965/0] ieee80211_ref_node (ht_send_action_ba_addba:3060) 0xffffffff812e0000<4c:19:5d:6f:5c:0e> refcnt 4
Attachments (3)
Change History (12)
comment:1 by , 6 days ago
| Component: | - General → Drivers/Network/iprowifi4965 |
|---|---|
| Owner: | changed from to |
comment:2 by , 6 days ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 6 days ago
Syslog i can give you now.. Because of my palsy taking photos is quite difficult. So i'll have to figure out a way
comment:4 by , 6 days ago
I do see the controller panics in there, which may be related at least. The kernel panic may be related, or it may not be...
comment:5 by , 2 days ago
That's the best i can do for screenshots. If you need another go let me know and I'll get a friend to take one.
comment:6 by , 45 hours ago
Unfortunately it's too blurry to read.
Maybe you can just transcribe the message in the first line of the KDL ("PANIC: ...")?
Is this a regression or did it happen on older builds too?
Please attach a full syslog and screenshots of the KDLs.