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 #2277: Wireless does not work with the
2.6.29 kernel (Openmoko Public Trac)
2. Re: Openmoko Bug #2135: write kernel crash message somewhere
where it can be retrieved after reboot? (Openmoko Public Trac)
3. Re: Openmoko Bug #2277: Wireless does not work with the
2.6.29 kernel (Openmoko Public Trac)
4. Re: Openmoko Bug #2277: Wireless does not work with the
2.6.29 kernel (Openmoko Public Trac)
5. Re: Openmoko Bug #2277: Wireless does not work with the
2.6.29 kernel (Openmoko Public Trac)
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
Reporter: arhuaco | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
---------------------+------------------------------------------------------
Comment(by lindi):
I just hit this bug again even though I had reverted
4836494d233cd34fe194ff2040d62e4109067d7.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Inspired by werner's poke.c I wrote a userland tool to dump the contents
of the ramconsole via /dev/mem -- http://iki.fi/lindi/openmoko/ramconsole-
dump.c
I then modified the ramconsole patch so that it does not need to print the
contents of the ramconsole on bootup. This fixes issues #3, #4, #5 and #6.
(#6 is fixed since now the policy to discard corrupted ramconsole header
is in userland and can be changed if somebody needs to recover partially
corrupted data manually).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
Reporter: arhuaco | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
---------------------+------------------------------------------------------
Comment(by budfive):
I just found a 100% reproducible trigger for a kernel oops (NULL
dereference in wmi_powermode_cmd). Hopefully this is related to all of the
crashes. Steps:
[load ar6000.ko or turn on the wifi via bind]
ifconfig eth0 up
ifconfig eth0 down
iwconfig eth0 power off
With stock shr-unstable and the stock kernel, ar6000 is compiled into the
kernel, so to turn on the wifi you need to
echo "s3c2440-sdi" > /sys/bus/platform/drivers/s3c2440-sdi/bind
If this crashes the driver for others, we should set the reproducible
flag.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
Reporter: arhuaco | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
---------------------+------------------------------------------------------
Comment(by budfive):
There appear to be multiple problems with the wifi driver. I'm attaching a
proposed patch to fix the kernel oops I just described (knjmokowifi hits
that case). Now, knjmokowifi still doesn't work, but gets into a state
where doing anything useful with iwconfig produces i/o errors, but no
oops.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
Reporter: arhuaco | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
---------------------+------------------------------------------------------
Comment(by budfive):
I figured out the bigger problem. Short version:
ifconfig eth0 down
ifconfig eth0 up
makes the driver unusable. Many programs that automatically set up the
network do this, and end up hosing the driver.
Long version:
In the current driver, there are several variables that define the
"readiness" of the driver. One of these is ar->arWmiReady. If this
variable is FALSE, no wireless calls succeed (iwconfig, iwlist, etc).
Currently, this variable is set to true only from ar6000_rx, NOT from
ar6000_open.
When ar6000_init is called (during the module load or the kernel boot if
ar6k is compiled-in), ar6000_rx ends up being called (not quite sure why)
and this allows the driver to work. ar6000_close (ifconfig eth0 down) sets
ar->arWmiReady to FALSE. However, a successive "ifconfig eth0 up" does NOT
reset the ar->arWmiReady variable, and the driver stays in an unusable
state. Reloading the kernel module allows the driver to work again.
ar6000_open needs to set up the variables to allow the driver to work. Is
the author of the driver still around?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
