If you spot this bug again, could you please:
* check whether eth0 is still visible with ifconfig -a
* check whether the Marvell 8xxx is still visible with lsusb
* dmesg dmesg.out and attach it to the bug. Dextrose enables
libertas debug in /etc/rc.local to help diagnose this bug.
* dmesg dmesg.out and attach it to the bug. Dextrose enables
libertas debug in /etc/rc.local to help diagnose this bug.
took me 10 minutes after it came good to work out dmesg so this is a bit later
than the event:
[0.00] Linux version 2.6.31_xo1-20100701.1605.1.olpc.a8f1b26
attached file dmesg___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
El Wed, 25-08-2010 a las 20:45 +1000, fors...@ozonline.com.au escribió:
* dmesg dmesg.out and attach it to the bug. Dextrose enables
libertas debug in /etc/rc.local to help diagnose this bug.
took me 10 minutes after it came good to work out dmesg so this is a bit
later than the
That's odd, debug does not seem to be on.
Is this really os373py? What's in /etc/rc.local?
Still getting my head round this stuff. I presume [xx.xx] is the timestamp in
seconds. The log activity dmesg captures the first 16 seconds after startup,
dmesg in terminal shows [xx.xx]=1 aprox.
Bernie
Sorry, on closer inspection its not locked up, it just looks like its locked up
because it is doing something else for a long time.
Can be replicated 100%. Shut the lid for a while, 5 minutes is not long enough
1.5 hours is. Resume from sleep. The Wifi shows it is connected at 100%
