linux-kernel - rt2500pci: false alarm (was rt2500pci_bbp_read: Error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <81b0412b0808191208y6bef9187nc57fa74c08a92d54@mail.gmail.com>
Date:	Tue, 19 Aug 2008 21:08:50 +0200
From:	"Alex Riesen" <raa.lkml@...il.com>
To:	"Ivo van Doorn" <ivdoorn@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: rt2500pci: false alarm (was rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed)

2008/8/19 Alex Riesen <raa.lkml@...il.com>:
> 2008/8/19 Ivo van Doorn <ivdoorn@...il.com>:
>>> The rt2500 driver in 2.6.27-rc3 (v2.6.27-rc3-552-g3c3a15a) constantly
>>> produces a lot of this messages in log (slowdown quite noticable):
>>>
>>>     kernel: phy0 -> rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed.
>
> It surely did, but I honestly don't remember what with. I'll try to bisect.
>

Ok, it _is_ the hardware. Precisely: it is a dusty box in a dark humid corner.
I reseated the card and suddenly everything started working.

I'm really sorry. The error description was actually a very good
hint at the problem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/