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 #2262: backlight brightness of 11 unusable
after blank/unblank (Openmoko Public Trac)
2. Re: Openmoko Bug #2255: xf86-video-glamo/703acea13: xrandr -o
1; xrandr -o 3 causes distortion (Openmoko Public Trac)
3. Re: Openmoko Bug #2255: xf86-video-glamo/703acea13: xrandr -o
1; xrandr -o 3 causes distortion (Openmoko Public Trac)
4. Re: Openmoko Bug #2255: xf86-video-glamo/703acea13: xrandr -o
1; xrandr -o 3 causes distortion (Openmoko Public Trac)
5. Re: Openmoko Bug #2252: andy-tracking: battery/capacity:
Timer expired (Openmoko Public Trac)
6. Re: Openmoko Bug #2252: andy-tracking: battery/capacity:
Timer expired (Openmoko Public Trac)
7. Re: Openmoko Bug #2274: Kernel regression: white screen of
death reappeared with 2.6.29 (Openmoko Public Trac)
8. Openmoko Bug #2275: power_supply battery: driver failed to
report X property (Openmoko Public Trac)
--- Begin Message ---
#2262: backlight brightness of 11 unusable after blank/unblank
--------------------------------+-------------------------------------------
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: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by lindi):
Thanks a lot. I tested with andy-tracking b4136a36f31a65d0 and can confirm
that the bug does not occur anymore.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2262#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2255: xf86-video-glamo/703acea13: xrandr -o 1; xrandr -o 3 causes distortion
------------------------+---------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: closed
Priority: high | Milestone: stable-kernel-2009.1
Component: unknown | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
------------------------+---------------------------------------------------
Comment(by lindi):
I can still hit this bug with andy-tracking b4136a36f31a65d0 from today.
Is there some extra information I should provide?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2255#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2255: xf86-video-glamo/703acea13: xrandr -o 1; xrandr -o 3 causes distortion
------------------------+---------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: closed
Priority: high | Milestone: stable-kernel-2009.1
Component: unknown | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
------------------------+---------------------------------------------------
Comment(by arhuaco):
Did you try this before running Xorg?
echo 0 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0
/glamo-fb.0/xglamo_hack
It can also be disabled in the .config.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2255#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2255: xf86-video-glamo/703acea13: xrandr -o 1; xrandr -o 3 causes distortion
------------------------+---------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: closed
Priority: high | Milestone: stable-kernel-2009.1
Component: unknown | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 1
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
------------------------+---------------------------------------------------
Comment(by lindi):
No sorry, I forgot that. I added
echo 0 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0
/glamo-fb.0/xglamo_hack
to /etc/init.d/xdm and now I can do not hit this bug anymore with
b4136a36f31a65d0, thanks a lot!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2255#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2252: andy-tracking: battery/capacity: Timer expired
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I do not see this anymore with b4136a36f31a65d0 from 2009-04-25. Please
close the bug.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2252#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2252: andy-tracking: battery/capacity: Timer expired
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by arhuaco):
* status: new => closed
* resolution: => fixed
Comment:
Not present with recent kernel. Closed.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2252#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2274: Kernel regression: white screen of death reappeared with 2.6.29
-----------------------------+----------------------------------------------
Reporter: CyrusDreams | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone: stable-kernel-2009.1
Component: System Software | Version: GTA02v5
Severity: critical | Keywords: WSoD white screen suspend
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I just hit this with andy-tracking b4136a36f31a65d0 after resume. SD card
access seems to work during WSOD and suspend/resume seems to bring the
display back to a usable state. Here's some version number information:
kernel: Linux ginger 2.6.29-GTA02_lindi-andy-tracking-mokodev #1 PREEMPT
Sat Apr 25 15:56:52 EEST 2009 armv4tl GNU/Linux
kernel cmdline: rootfstype=jffs2 root=/dev/mtdblock6
console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot mtdparts
=physmap-
flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 mem=127M panic=10
u-boot: U-Boot 1.3.2+gitr46+dc633f4be2527f844158aa5085c278b0c3039d3f (Aug
8 2008 - 03:58:49)
xserver-xorg-core: 2:1.5.99.902-1
xf86-video-glamo: 703acea13
distro: debian gnu/linux unstable
hardware revision: 24420350
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2274#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2275: power_supply battery: driver failed to report X property
---------------------+------------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: minor | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Even when I leave my phone idle on the desk my kernel logs are filled with
warnings like
{{{
[57265.375000] power_supply battery: driver failed to report `voltage_now'
property
[57283.530000] power_supply battery: driver failed to report `voltage_now'
property
[57290.390000] HDQ responds again
[57948.315000] HDQ error: 1
[57948.330000] HDQ responds again
[57948.450000] power_supply battery: driver failed to report `temp'
property
[58302.695000] HDQ error: 1
[58302.695000] power_supply battery: driver failed to report `voltage_now'
property
[58303.535000] power_supply battery: driver failed to report `voltage_now'
property
[58327.710000] HDQ responds again
[58909.870000] HDQ error: 1
[58909.885000] HDQ responds again
[59264.240000] HDQ error: 1
[59264.255000] HDQ responds again
[59264.285000] power_supply battery: driver failed to report
`time_to_full_now' property
[59441.340000] HDQ error: 1
[59441.355000] HDQ responds again
[59820.810000] HDQ error: 1
[59820.825000] HDQ responds again
[60048.480000] HDQ error: 1
[60048.495000] HDQ responds again
[60048.675000] power_supply battery: driver failed to report `charge_full'
property
[60073.550000] power_supply battery: driver failed to report `charge_full'
property
[60529.275000] HDQ error: 1
[60529.295000] HDQ responds again
[60529.370000] power_supply battery: driver failed to report
`time_to_empty_now' property
[61085.810000] HDQ error: 1
[61085.825000] HDQ responds again
[61389.675000] HDQ error: 1
[61389.675000] power_supply battery: driver failed to report `voltage_now'
property
[61393.540000] power_supply battery: driver failed to report `voltage_now'
property
[61414.690000] HDQ responds again
[63084.780000] HDQ error: 1
[63084.795000] HDQ responds again
[63084.870000] power_supply battery: driver failed to report
`time_to_empty_now' property
[63944.870000] HDQ error: 1
[63944.885000] HDQ responds again
[63945.115000] power_supply battery: driver failed to report `health'
property
[64805.350000] HDQ error: 1
[64805.365000] HDQ responds again
[64906.370000] HDQ error: 1
[64906.385000] HDQ responds again
[64906.630000] power_supply battery: driver failed to report `current_now'
property
[65032.905000] HDQ error: 1
[65032.925000] HDQ responds again
[65033.105000] power_supply battery: driver failed to report `charge_full'
property
[65053.550000] power_supply battery: driver failed to report `charge_full'
property
[65058.255000] HDQ error: 1
[65058.270000] HDQ responds again
[65058.390000] power_supply battery: driver failed to report `temp'
property
[65311.115000] HDQ error: 1
[65311.130000] HDQ responds again
[65311.375000] power_supply battery: driver failed to report `current_now'
property
[65323.545000] power_supply battery: driver failed to report `current_now'
property
[65640.095000] HDQ error: 1
[65640.110000] HDQ responds again
}}}
Is this a bug that should be fixed or are these messages just too verbose?
I am using andy-tracking b4136a36f31a65d0 from Apr 25.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2275>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
