> Thanks for posting the dmesg. In looking through it, the only thing I noticed
> was the following:
>
> [   25.844834]        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 
> mBm)
> [   25.844844]        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 
> mBm)
> [   25.845455] cfg80211: Calling CRDA for country: US
> [   26.115780] name_count maxed, losing inode data: dev=00:06, inode=13081
> [   26.115885] name_count maxed, losing inode data: dev=00:06, inode=13081
> [   26.115944] name_count maxed, losing inode data: dev=00:06, inode=13081
>
> There are a lot of those "name_count maxed" messages. Is this a problem with
> your disk?

  Thanks for looking so closely -- although it's a little bit like if
you go to the doctor for a flue remedy and (s|)he tells you you got
tuberculosis :-). I think it's harmless. It comes from within auditsc.c.
I've turned on everything in the kernel config that smelled like "more 
verbosity" and I think (hope ?) it's harmless.

So as far as I understand both the early kernel as well as lspci think
that the mmio area of the Broadcom chip is located at 57100000 only ssb
gets the wrong address. It gets set in ssbioremap via pci_iomap. So my 
guess is that the pci_dev passed to that function is not properly set
up. I'll add more debug output into the module when i find the time
and post the results.

Sebastian
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to