Hi everybody.
Sorry to re-post this issue but nobody replied and I don't think me and S.
Biggs are the only one experiencing this issue.
I'm experiencing the same problem Stephen has (described below). I was looking
for a solution on the
web but I'd say unsuccessfully. I couldn't found any reply to his
complaint (the one posted by S. Biggs is in fact the only one I've found
around).
Here's my pcidump -v output related to the wireless AP:
5:4:0: Ralink RT2561S
0x0000: Vendor ID: 1814 Product ID: 0301
0x0004: Command: 0107 Status ID: 0410
0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
0x000c: BIST: 00 Header Type: 00 Latency Timer: 42 Cache Line Size: 10
0x0010: BAR mem 32bit addr: 0xf8510000
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000601
0x002c: Subsystem Vendor ID: 1432 Product ID: 7128
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 05 Min Gnt: 00 Max Lat: 00
0x0040: Capability 0x01: Power Management
Everything's running on OpenBSD 4.8 RELEASE.
Thanks in advance, any tip/direction is more than welcome.
On Tue, 2010-11-30 at 03:33 +0000, Stephen Biggs wrote:
> Running 4.8 patch/stable with all updated, apm disable via config, upgraded
> from
> 4.7 patch/stable.
>
> Any time ral0 is initialized (in hostap mode) using, say, sh /etc/netstart,
> the
> following message is shown on the console:
> ral0: timeout waiting for BBP
>
> The code shows that when this happens, the device initialization is aborted
> and
> EIO error is returned, making 4.8 patch/stable useless for running the box as
> a
> wireless access point using ral.
>
> This may ordinarily point to hardware failing except for two things:
> 1. checking the code shows that the busy bit is actually cleared because no
> "cannot read from BBP" message is seen, only a 0 is returned from the version
> flash read. My guess is that some firmware is being loaded wrong onto the
> hardware in 4.8?
> ...and
> 2. ral0 initializes just fine without the timeout using either my previous 4.7
> kernel, or the -current kernel which I am running now.
>
> The relevant parts of dmesg (relevant imho; if there is more that is needed,
> please advise) are:
> ral0 at pci0 dev 14 function 0 "Ralink RT2561S" rev 0x00: irq 3, address
> 00:24:1
> d:39:f6:84
> ral0: MAC/BBP RT2561C, RF RT2527
>
> Also, pcidump -v shows for this device:
> 0:14:0: Ralink RT2561S
> 0x0000: Vendor ID: 1814 Product ID: 0301
> 0x0004: Command: 0017 Status ID: 0410
> 0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
> 0x000c: BIST: 00 Header Type: 00 Latency Timer: 20 Cache Line Size: 08
> 0x0010: BAR mem 32bit addr: 0xe3800000
> 0x0014: BAR empty (00000000)
> 0x0018: BAR empty (00000000)
> 0x001c: BAR empty (00000000)
> 0x0020: BAR empty (00000000)
> 0x0024: BAR empty (00000000)
> 0x0028: Cardbus CIS: 00000601
> 0x002c: Subsystem Vendor ID: 1458 Product ID: e934
> 0x0030: Expansion ROM Base Address: 00000000
> 0x0038: 00000000
> 0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00
> 0x0040: Capability 0x01: Power Management
>
> I don't know what to do next here. I am understandably very apprehensive about
> running a -current kernel on top of a 4.8 stable userland. I don't want to be
> running -current at all.
>
> I was thinking about posting a bug using sendbug but that seems a bit
> pointless
> considering that I am right now running the -current kernel.
>
> The best case scenario would be for whomever knows what causes the -current
> kernel to work in this instance to post what relevant changes there are (or a
> patch?) or better yet, post a patch to the errata so I can go back to a 4.8
> stable kernel with the patch.
>
> What is interesting about this is that I can't find any other mention of this
> problem anywhere else on the Internet. I would have thought that a lot of
> people would be running ral0 as an access point and would have found this.
>
> If this is only local to me, I would sure appreciate any advice on how to
> track
> this down.
