Bug 151198

Summary: [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: unable to reset channel 11 (2462 MHz, flags 0x480), hal status 14"
Product: Base System Reporter: Poul-Henning Kamp <phk>
Component: wirelessAssignee: freebsd-wireless (Nobody) <wireless>
Status: Closed Feedback Timeout    
Severity: Affects Only Me CC: 0mp, lwhsu
Priority: Normal    
Version: 9.0-CURRENT   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Poul-Henning Kamp 2010-10-04 12:00:14 UTC 
	ath0: <Atheros 5416> mem 0xf2500000-0xf250ffff irq 16 at device 0.0 on pci2
	ath0: [ITHREAD]
	ath0: AR5418 mac 12.10 RF5133 phy 8.1

	if bgscan is enabled, connectivity will die when messages like

	ath0: ath_chan_set: unable to reset channel 11 (2462 MHz, flags 0x480), hal status 14
	ath0: ath_chan_set: unable to reset channel 13 (2472 MHz, flags 0x680), hal status 14
	ath0: ath_chan_set: unable to reset channel 10 (2457 MHz, flags 0x480), hal status 14
	ath0: ath_chan_set: unable to reset channel 12 (2467 MHz, flags 0x680), hal status 14
	ath0: ath_chan_set: unable to reset channel 11 (2462 MHz, flags 0x480), hal status 14
	ath0: ath_chan_set: unable to reset channel 13 (2472 MHz, flags 0x680), hal status 14
	ath0: ath_chan_set: unable to reset channel 10 (2457 MHz, flags 0x480), hal status 14

	appear in syslog.

	Disabling bgscan (ifconfig wlan0 -bgscan) removes symptoms.

Fix: tried, this to no avail:
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-10-06 20:40:06 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Adrian Chadd freebsd_committer freebsd_triage 2010-10-07 15:25:42 UTC 
Responsible Changed
From-To: freebsd-net->adrian

my turn!
Comment 3 Adrian Chadd freebsd_committer freebsd_triage 2011-04-09 04:12:21 UTC 
Responsible Changed
From-To: adrian->freebsd-wireless

bump to freebsd-wireless
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:49:37 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.
Comment 5 Mateusz Piotrowski freebsd_committer freebsd_triage 2021-02-08 11:01:37 UTC 
HAL has been removed from the ports tree in https://svnweb.freebsd.org/ports?view=revision&revision=564691. I'm closing this issue for now because of that.
Comment 6 Andriy Gapon freebsd_committer freebsd_triage 2021-02-08 14:07:55 UTC 
(In reply to Mateusz Piotrowski from comment #5)
What is the relevance of that hal to this problem with Atheros wireless driver?
(Not that I would insist on resurrecting this old bug.)
Comment 7 Li-Wen Hsu freebsd_committer freebsd_triage 2021-02-08 14:45:10 UTC 
(In reply to Andriy Gapon from comment #6)
I guess people are confused by hal port and ath_hal. However I think this ticket might be closed due to inactive for a long time.
Comment 8 Mateusz Piotrowski freebsd_committer freebsd_triage 2021-02-08 16:45:41 UTC 
(In reply to Andriy Gapon from comment #6)
I was considering that the hal in this context might not be sysutils/hal, but in the end I decided that it's probably the same thing. The goal was to close a seemingly stale PR. I'm sorry for the confusion.