Bug 198670 - Log if there is an invalid ID with ath(4) at bootup preventing driver from attaching
Summary: Log if there is an invalid ID with ath(4) at bootup preventing driver from at...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-17 22:21 UTC by cmb
Modified: 2015-03-17 22:21 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cmb 2015-03-17 22:21:10 UTC 
Opening at Adrian's request. 

If an ath(4) card doesn't get its initial power on config from EEPROM, the driver doesn't attach. This is usually some power up reset bug in how the BIOS sets up the PCI bus. The PC Engines APU appears to do this at times, seemingly only with an older BIOS rev that was buggy in that regard. 

from Adrian: "I'll go see if I can at least have the driver explain why that's an invalid id at boot up"