[EMAIL PROTECTED] wrote:
>Ulrich Kunitz wrote:
>
>
>>This is the address of the invalid code. It's a pity that they
>>don't write out a normal kernel oops, which would give us much
>>more information. Look into /proc/modules and /boot/System.map*
>>to check where it is. If it is in zd1211 you ca
Ulrich Kunitz wrote:
> This is the address of the invalid code. It's a pity that they
> don't write out a normal kernel oops, which would give us much
> more information. Look into /proc/modules and /boot/System.map*
> to check where it is. If it is in zd1211 you can uses
> nm -n -g zd1211.ko to fi
Guennadi Liakhovetski wrote:
> are you planning on submitting your improvements / bugfixes for 2.6.18 or
> are they only going into the wireless tree for after-2.6.18?
Fixes are going into 2.6.18, improvements are going into
wireless-2.6.git to be merged into 2.6.19. We have been sending patches
Ulrich, Daniel,
are you planning on submitting your improvements / bugfixes for 2.6.18 or
are they only going into the wireless tree for after-2.6.18?
Thanks
Guennadi
---
Guennadi Liakhovetski
-
Using Tomcat but need to do
On 06-08-12 20:58 Maxime wrote:
>
> I connected a computer using a usb dongle (0ace:1215) to my access point
> (WPA/PSK), and the system hit a BUG over night.
> Let me know what I can do to help,
>
> Max
>
> if (!test_and_set_bit(0, &work->pending)) {
> BUG_ON(timer_pe
On 06-08-12 22:48 Patrick Simmons wrote:
> Thanks for your help, Ulrich.
>
> Would an unaligned memory access look like just an array indexing?
> Perhaps something like this? (version r83)
>
> zd1205.c:108:#define getSeq(pWlanHdr)
> (((u16)pWlanHdr->SeqCtrl[1] << 4) + (u16)(
