Date: Thu, 08 Nov 2018 05:45:43 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 192641] [iwn] panic in AMPDU tx code "ni: no node" Message-ID: <bug-192641-21060-qVTC2J3sWe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192641-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-192641-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192641 gl00my@mail.ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gl00my@mail.ru --- Comment #2 from gl00my@mail.ru --- Hello! While working with iwfi drivers in Haiku (those drivers are ported from FreeBSD) i founded the bugs, that potentially is FreeBSD specific. iprowifi4965 and iprowifi3945 are affected. May be others. I will describe them on iprowifi4965 code. iwn_tx_done has KASSERT(data->ni != NULL, ("no node")) at beginning that is triggers in some situations. The situation can be: 1) hw interrupt is scheduled 2) iwn_hw_stop is called (and it disables/enables interrupss) node is destroyed here. 3) here we got scheduled (threaded) interrupt that is not actual anymore -> panic In fact, i was thinking it is Haiku specific bug, because of threaded inr handlers. But i found this bug report and it seems the same for me. To reproduce it on Haiku i run floodping to roater while reboot the system. But on FreeBSD i am not sure, what can couse iwn_hw_stop while sending packets... Hope it helps. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192641-21060-qVTC2J3sWe>