F11 for the X01- shutdown

James Cameron quozl at laptop.org
Thu Jul 30 01:43:59 UTC 2009


On Wed, Jul 29, 2009 at 10:10:48AM -0700, Yioryos Asprobounitis wrote:
> Given that in my hands the shutdowns are happening usually very soon
> after boot, eg as soon as/while the xo is connecting to the wifi, I
> would guess that the problem stems from there.

I agree, that matches my shutdowns as well ... usually very soon after
boot, within a minute of associating with an access point.

I've got /var/log/messages being saved in /home/olpc/log/messages, and
here is the time sequence of messages when these uncommanded shutdowns
occur:

Jul 30 01:29:29 localhost NetworkManager: <info>  (eth0): device state change: 7 -> 8 (reason 0)
Jul 30 01:29:30 localhost NetworkManager: <info>  Policy set 'Auto quozl.linux.org.au' (eth0) as default for routing and DNS.
Jul 30 01:29:30 localhost NetworkManager: <info>  Activation (eth0) successful, device activated.
Jul 30 01:29:30 localhost NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jul 30 01:30:23 localhost init: tty4 main process (1755) killed by TERM signal
Jul 30 01:30:23 localhost init: tty5 main process (1756) killed by TERM signal
Jul 30 01:30:23 localhost init: tty2 main process (1757) killed by TERM signal

As you can see, roughly 50 seconds elapsed from when the access point
association completed and init decided to kill all the tty processes.

-- 
James Cameron
http://quozl.linux.org.au/




More information about the Fedora-olpc-list mailing list