Re: [iPAQ] h3800 isolation bug?

Hmmm, that's interesting.. Unfortunatly the ipaq got rebooted last
night (actually battery drained..) so I will check these next time it
happens.

An interesting thought occurs to me with this bug that you mention.
Would having a battery monitoring applet docked and running possibly
cause this on the off occasion that the two happen at the same time?? I
am using matchbox as my window manager, and am running the three "mini"
apps that come with it, including miniapm wich reciently (from last
update) has been doing some weird output.

just more thoughts...

Christian, Andrew wrote:
> Check /proc/interrupts to see what parts of the h3800 are running. Take a look at the values, then push buttons, and see if the h3800_keyboard value changes. /proc/hal/light_sensor should toggle the h3800_adc value, as should touch the touchscreen (h3800_adc counts the number of ADC conversions; h3800_touchscreen counts the number of separate touch events).
>
> I re-wrote the interrupt handling code for the 3800 in version 2.4.18-rmk3-hh3. There is a known problem with that version if you "rmmod h3600_asic" while checking the battery level, but (in theory) that shouldn't be tickled when the screensaver kicks in.
>
> - Andrew
>
>
>
>>-----Original Message-----
>>From: creator@inreach.com [mailto:creator@inreach.com]
>>Sent: Thursday, April 18, 2002 8:00 PM
>>To: ipaq@handhelds.org
>>Subject: [iPAQ] h3800 isolation bug?
>>
>>
>>Hay all....
>>
>>Okay this is a weird one... I leave my ipaq (3870) alive
>>throught the
>>day. Occasionaly once the screensaver kicks in, I cannot get
>>the ipaq to
>>come back to life again untill I do a full reboot. Some of
>>the symptoms are:
>>
>>-pushing buttons will not wake the screen back up
>>-pushing suspend will not suspend/resume the device
>>-the charging indicator functions (flashing when on cradle)
>>-my network connectivity is not interrupted (I still am ssh'd
>>in and can
>>work on the system)
>>-when i try to stop/start x i get error messages (see below)
>>-when i cat /proc/hal/light_sensor, it hangs untill i issue a break
>>
>>It currently is in this state, so if you want any info from the
>>/proc/asic/registers or whatever, just yell.
>>
>>here is what happens when i try to stop and start the x server.
>>
>>sh-2.03# /etc/init.d/x stop
>>Killing X...
>>dd: writing to `/dev/fb0': No space left on device
>>301+0 records in
>>300+0 records out
>>sh-2.03# /etc/init.d/x start
>>Starting X...
>>iPAQ 3800
>>
>>Fatal server error:
>>LinuxInit: Cannot open /dev/tty0 (Input/output error)
>>
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X11 connection rejected because of wrong authentication.
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X11 connection rejected because of wrong authentication.
>>Gdk-ERROR **: X connection to familiar:10.0 broken (explicit kill or
>>server shutdown).
>>X11 connection rejected because of wrong authentication.
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X11 connection rejected because of wrong authentication.
>>X11 connection rejected because of wrong authentication.
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X11 connection rejected because of wrong authentication.
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>X connection to familiar:10.0 broken (explicit kill or server
>>shutdown).
>>sh-2.03#
>>
>>I am running the latest kernerl (2.4.18-rmk3-hh3) with a slightly
>>non-bleeding edge bootldr (2.18.24) (but have seen this on the newest
>>bootldr 2.18.38).
>>
>>Any ideas??
>>
>>Robert Stellhorn
>>creator@inreach.com
>>
>>_______________________________________________
>>Open Source Software for Compaq iPAQ Handhelds.
>>iPAQ mailing list
>>iPAQ@handhelds.org
>>http://handhelds.org/mailman/listinfo/ipaq
>>irc://irc.openprojects.net #ipaq
>>
>
Received on Fri Apr 19 15:34:01 2002