b43: Debugging PHY TX errors

b43: Debugging PHY TX errors

[Michael Buesch]

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

I hacked up some scripts for debugging of the PHY transmission
errors. It consists of two parts. One patch that has to be applied
to the kernel driver (latest wireless-testing!) and one firmware
binary patcher script (for latest supported firmware only!)

Both are included in the attached tarball. Extract the tarball.

So you first have to apply the included "b43-kernel-patch.patch" to
the kernel driver and recompile your kernel.
Then you have to patch your firmware by doing:

cd phyerr-patcher-001
bash ./patch-phyerr-logger.sh /lib/firmware/b43/ucode5.fw

You might have to adjust the path to your firmware.
On successful patching, the script will exit with a nice smilie: :)


So when running the modified driver with the patched firmware, it should
dump the shared memory every time a PHY error occurs.
More state dumps can be added to the kernel driver. The firmware is halted
while the phyerr logger function is running, so state should be consistent.

WARNING: This patch might kill your cat, or at least disturb your wireless
connectivity. Only use it for debugging the PHY transmission errors.

Note that these scripts require a complete compiler toolchain, including
flex and bison, on your machine, as it will compile the assembler and
disassembler tools.

-- 
Greetings Michael.

[-- Attachment #2: phyerr-patcher-001.tar.bz2 --]
[-- Type: application/x-tbz, Size: 58586 bytes --]

Re: b43: Debugging PHY TX errors

[Stefanik Gábor]

On Thu, Jul 24, 2008 at 1:30 PM, Michael Buesch <mb@bu3sch.de> wrote:
> I hacked up some scripts for debugging of the PHY transmission
> errors. It consists of two parts. One patch that has to be applied
> to the kernel driver (latest wireless-testing!) and one firmware
> binary patcher script (for latest supported firmware only!)
>
> Both are included in the attached tarball. Extract the tarball.
>
> So you first have to apply the included "b43-kernel-patch.patch" to
> the kernel driver and recompile your kernel.
> Then you have to patch your firmware by doing:
>
> cd phyerr-patcher-001
> bash ./patch-phyerr-logger.sh /lib/firmware/b43/ucode5.fw
>
> You might have to adjust the path to your firmware.
> On successful patching, the script will exit with a nice smilie: :)
>
>
> So when running the modified driver with the patched firmware, it sho=
uld
> dump the shared memory every time a PHY error occurs.
> More state dumps can be added to the kernel driver. The firmware is h=
alted
> while the phyerr logger function is running, so state should be consi=
stent.
>
> WARNING: This patch might kill your cat, or at least disturb your wir=
eless
> connectivity. Only use it for debugging the PHY transmission errors.
>
> Note that these scripts require a complete compiler toolchain, includ=
ing
> flex and bison, on your machine, as it will compile the assembler and
> disassembler tools.
>
> --
> Greetings Michael.

Please add this functionality to the open-source firmware too.

--G=E1bor

--=20
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: b43: Debugging PHY TX errors

[Michael Buesch]

On Thursday 24 July 2008 17:06:39 Stefanik G=E1bor wrote:
> Please add this functionality to the open-source firmware too.

No this is very intrusive.
The hacked firmware restarts itself on a PHY error. We don't want this =
in
a production environment, because as I said it will disturb your
connectivity (a PHY error every few minutes with vanilla firmware will =
not).

I also forgot to say that the patcher currently only works for ucode5.f=
w.
So if your device uses another firmware and you really want to debug
a PHY error, I can port the patcher to your version. Just poke me.

--=20
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html