Hi,

The general consensus at work is - BIOSes are buggy and don't
necessarily reset the PCI bus correctly.

So either you can do your own PCI bus reset post-boot (and
re-enumerate all the PCI devices, including initialising their BARs)
or smack your vendor to fix their BIOSes. I can't really make any
further suggestions besides that.


Adrian

On 27 March 2013 11:34, Steffen Dettmer <steffen.dett...@nomadrail.com> wrote:
> Hi,
>
> some time ago there was a thread "Sparklan WPEA-121N AR9382 168c:abcd" about 
> the issue that the mentioned device was erroneously reported as device ID 
> 0xabcd. There were EEPROM issues assumed and BIOS issues reported that could 
> cause this effect (by resetting the PCI bus at system power on) and a 
> proposed workaround to add the wrong ID to the driver to make it load - it 
> had been reported working.
>
> I'm facing such a situation with embedded devices (I assume BIOS updates 
> probably are at least very difficult) and a WPEA-127N and would like to know 
> whether there were new findings and share mine in case they'd be of some 
> interest.
>
> Are there any news on that?
>
> Is the proposed workaround adding 0xabcd to the driver still best way of 
> handling this?
>
> On my board it happens /from time to time/ that the device reports 0xabcd - 
> but not always.
>
> I made 20 tests were I saw 4 such failures. All those failures appeared after 
> cold boot, but none after warm boot. After cold boot sometimes one of two 
> installed devices appeared with wrong device ID but other correctly, and at 
> other times both were working. Of course the number of tests is insufficient 
> to draw conclusions, I write it just in case it rings a bell.
>
> It is some Intel atom board running Linux (for example, Debian 7). Can I 
> provide information that could help (and if so, how do I get those)?
>
> Best regards,
> Steffen
>
> Some test results:
>
> root@nomad:~# lspci|grep -i ath
> 01:00.0 Ethernet controller: Atheros Communications Inc. Device abcd (rev 01)
> 07:00.0 Ethernet controller: Atheros Communications Inc. Device abcd (rev 01)
> root@nomad:~# grep '' 
> /sys/devices/pci0000:00/0000:00:1c.*/0000:0{1,7}:00.0/{vendor,device}
> /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/vendor:0x168c
> /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/device:0xabcd
> /sys/devices/pci0000:00/0000:00:1c.2/0000:07:00.0/vendor:0x168c
> /sys/devices/pci0000:00/0000:00:1c.2/0000:07:00.0/device:0xabcd
> root@nomad:~# reboot
> [ssh...]
> root@nomad:~# lspci|grep -i ath
> 01:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN 
> adaptor (rev 01)
> 07:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN 
> adaptor (rev 01)
> root@nomad:~# grep '' 
> /sys/devices/pci0000:00/0000:00:1c.*/0000:0{1,7}:00.0/{vendor,device}
> /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/vendor:0x168c
> /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/device:0x0030
> /sys/devices/pci0000:00/0000:00:1c.2/0000:07:00.0/vendor:0x168c
> /sys/devices/pci0000:00/0000:00:1c.2/0000:07:00.0/device:0x0030
>
>
> root@nomad:/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0# grep '' *
> broken_parity_status:0
> class:0x020000
> Binary file config matches
> consistent_dma_mask_bits:32
> device:0xabcd
> dma_mask_bits:32
> enable:0
> grep: firmware_node: Is a directory
> irq:10
> local_cpulist:0-31
> local_cpus:ffffffff
> modalias:pci:v0000168Cd0000ABCDsv00000000sd00000000bc02sc00i00
> grep: power: Is a directory
> grep: remove: Permission denied
> grep: rescan: Permission denied
> grep: reset: Permission denied
> resource:0x00000000fdfe0000 0x00000000fdffffff 0x0000000000140204
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x00000000fdfd0000 0x00000000fdfdffff 0x000000000004e200
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> resource:0x0000000000000000 0x0000000000000000 0x0000000000000000
> grep: resource0: Input/output error
> grep: rom: Invalid argument
> grep: subsystem: Is a directory
> subsystem_device:0x0000
> subsystem_vendor:0x0000
> uevent:PCI_CLASS=20000
> uevent:PCI_ID=168C:ABCD
> uevent:PCI_SUBSYS_ID=0000:0000
> uevent:PCI_SLOT_NAME=0000:01:00.0
> uevent:MODALIAS=pci:v0000168Cd0000ABCDsv00000000sd00000000bc02sc00i00
> vendor:0x168c
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to