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 #2265: kernel spams with useless messages
(fbcon_event_notify action, etc.) (Openmoko Public Trac)
2. Openmoko Bug #2269: Om2009 release (Openmoko Public Trac)
3. Re: Openmoko Bug #2265: kernel spams with useless messages
(fbcon_event_notify action, etc.) (Openmoko Public Trac)
4. Re: Openmoko Bug #2267: [wifi] kernel oops when starting
wpa_supplicant (Openmoko Public Trac)
5. Re: Openmoko Bug #2265: kernel spams with useless messages
(fbcon_event_notify action, etc.) (Openmoko Public Trac)
6. Re: Openmoko Bug #2265: kernel spams with useless messages
(fbcon_event_notify action, etc.) (Openmoko Public Trac)
7. Re: Openmoko Bug #2265: kernel spams with useless messages
(fbcon_event_notify action, etc.) (Openmoko Public Trac)
8. Re: Openmoko Bug #2267: [wifi] kernel oops when starting
wpa_supplicant (Openmoko Public Trac)
--- Begin Message ---
#2265: kernel spams with useless messages (fbcon_event_notify action, etc.)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by nicolas.dufresne):
JBT spam is already cleaned up. I'll fix fbcon.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2265#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2269: Om2009 release
--------------------+-------------------------------------------------------
Reporter: Nytowl | Owner: Nytowl
Type: task | Status: new
Priority: normal | Milestone: Om2009
Component: Distro | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
--------------------+-------------------------------------------------------
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2269>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2265: kernel spams with useless messages (fbcon_event_notify action, etc.)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Thanks. After these the only regular kernel messages I see are
{{{
03:09:33 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
03:09:33 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
03:09:33 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
03:24:33 Charging restarted..
03:34:57 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
03:34:58 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
03:34:58 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
03:49:57 Charging restarted..
04:00:39 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
04:00:39 INT1=0x80 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
04:00:39 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
04:15:39 Charging restarted..
04:25:40 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
04:25:40 INT1=0x80 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
04:25:40 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
04:40:40 Charging restarted..
04:49:43 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
04:49:43 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
04:49:43 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
05:04:43 Charging restarted..
05:14:43 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
05:14:43 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
05:14:43 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
05:29:43 Charging restarted..
05:39:36 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
05:39:36 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
05:39:36 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
05:54:36 Charging restarted..
06:05:54 INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
06:05:54 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
06:05:54 INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
}}
We probably don't want to get rid of "Charging restarted.." but what are
these interrupts?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2265#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2267: [wifi] kernel oops when starting wpa_supplicant
---------------------+------------------------------------------------------
Reporter: tilman2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: unknown | Version: unspecified
Severity: normal | Keywords: wpa_supplicant wlan oops
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Changes (by arhuaco):
* keywords: => wpa_supplicant wlan oops
* haspatch: 0 => 1
Comment:
Mwester, it seems like a good solution (until someone tell us otherwise).
Can I create a patch with your fix and add a Signed-off-by for you with
your email address?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2267#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2265: kernel spams with useless messages (fbcon_event_notify action, etc.)
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: positive | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by arhuaco):
* status: new => closed
* patchreview: => positive
* haspatch: 0 => 1
* resolution: => fixed
Comment:
Patch applied.
> We probably don't want to get rid of "Charging restarted.." but what
are these interrupts?
lindi: I'll open another bug with the information you just sent so that we
can receive feedback in case someone actually cares about the messages.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2265#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2265: kernel spams with useless messages (fbcon_event_notify action, etc.)
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: positive | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by arhuaco):
Oh. Check #2237. Shall we really remove those "INT1=0x00 INT2=0x00"...
messages? It seems in this case they were useful.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2265#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2265: kernel spams with useless messages (fbcon_event_notify action, etc.)
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: positive | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by nicolas.dufresne):
Note I have kept most of those traces, I've just moved them to proper log
level. If you set loglevel to 8, they will reapear. We could do the same
for the power management traces. Still I think they are counter intuitive
and may need some rework. As this chip is really central to our machine it
would be worth to have some string table to translate the information into
human readable containt ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2265#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2267: [wifi] kernel oops when starting wpa_supplicant
---------------------+------------------------------------------------------
Reporter: tilman2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: unknown | Version: unspecified
Severity: normal | Keywords: wpa_supplicant wlan oops
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by mwes...@…):
Replying to [comment:3 arhuaco]:
> Mwester, it seems like a good solution (until someone tell us
otherwise). Can I create a patch with your fix and add a Signed-off-by for
you with your email address?
Certainly; we can back it out if there is a "more correct" way to solve
this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2267#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
