Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2333: Intermittent kernel oops when using
wifi (Openmoko Public Trac)
2. Re: Openmoko Bug #2333: Intermittent kernel oops when using
wifi (Openmoko Public Trac)
3. Re: Openmoko Bug #2333: Intermittent kernel oops when using
wifi (Openmoko Public Trac)
4. Re: Openmoko Bug #2333: Intermittent kernel oops when using
wifi (Openmoko Public Trac)
--- Begin Message ---
#2333: Intermittent kernel oops when using wifi
---------------------+------------------------------------------------------
Reporter: bt4 | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords: wlan oops
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Changes (by PaulFertser):
* cc: wer...@…, nicola....@… (added)
* status: new => in_testing
Comment:
Please try the attached patch.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2333#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2333: Intermittent kernel oops when using wifi
-----------------------------+----------------------------------------------
Reporter: bt4 | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: wlan oops
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Changes (by PaulFertser):
* component: unknown => System Software
Comment:
Also please do not forget to set Component to System Software when you
report bugs, i guess OM trac is not and will not be used for anything
else, so this is the only section we should pay attention to.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2333#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2333: Intermittent kernel oops when using wifi
-----------------------------+----------------------------------------------
Reporter: bt4 | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: wlan oops
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by bt4):
Thanks for the patch, however I'm still seeing the problem. Niko supplied
me with a replacement kernel module, which I tested using the method above
and it failed in exactly the same way. The dmesg output looks similar too.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2333#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2333: Intermittent kernel oops when using wifi
-----------------------------+----------------------------------------------
Reporter: bt4 | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: wlan oops
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by PaulFertser):
Are you really sure you used a kernel module with the patch and that dmesg
output is really identical?
Please, next time you do any testing,
1. #define DEBUG at the top of ar6000_drv.c (it might change the timing
tough, so if you can't reproduce with it, disable it back, i still hope
it's possible to reproduce it with this option, please try hard).
2. post dmesg
3. post kernel module binary you used (preferably the .o, not .ko file) so
i can locate (instead of guessing) the op that caused NULL pointer
dereference.
Also you might speed up the process a lot if you enable me to reproduce
the issue. Trace all calls to wpa_supplicant and try to reproduce with
wpa_cli (though it might be hard due to timing issues). Alternatively, i
can install nwa myself but i'm unsure i can reproduce your network
conditions so try to minimise the requirements (it's better to have a way
to reproduce it once in 10 times than having to find "an ap with weak
signal etc etc).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2333#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
