#9744 HIGH Not Tri: XO-1.5 WLAN errors after multiple suspend/resumes
Zarro Boogs per Child
bugtracker at laptop.org
Wed Nov 25 01:13:49 EST 2009
#9744: XO-1.5 WLAN errors after multiple suspend/resumes
--------------------------------+-------------------------------------------
Reporter: wad | Owner: mbletsas
Type: defect | Status: new
Priority: high | Milestone: Not Triaged
Component: wireless | Version: Development build as of this date
Resolution: | Keywords: XO-1.5 WLAN
Next_action: diagnose | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
--------------------------------+-------------------------------------------
Description changed by cjb:
Old description:
> On an XO-1.5 B3 prototype (#17), running Q3A16 and os45, I had a reboot
> instead of a resume.
>
> The laptop was modified with the XO1.5 WLAN SR ECO:
>
> http://wiki.laptop.org/go/XO1.5_WLAN_SR_ECO
>
> The laptop was set to autowack by adding:
>
> 50 autowack-delay
>
> autowack-on
>
> to the olpc.fth file.
>
> It was associated with an access point.
>
> From the terminal activity, I enabled EC wakeup events using:
>
> sudo sh
>
> echo EC > /proc/acpi/wakeup
>
> I then started a script (dosr) running:
>
> for i in seq 1 100000; do echo $i; sleep 1; echo mem >
> /sys/power/state; done;
>
> After twenty cycles, I stopped it and checked the interface using
> iwconfig and ping the gateway just fine.
>
> I restarted it, and after ten or so cycles I noticed that the WLAN LED
> was flashing very quickly. I stopped, and when I typed iwconfig it took
> many second to respond. This happened repeatedly.
>
> This is easy to reproduce.
New description:
On an XO-1.5 B3 prototype (#17), running Q3A16 and os45, I had WLAN errors
after multiple suspend/resumes.
The laptop was modified with the XO1.5 WLAN SR ECO:
http://wiki.laptop.org/go/XO1.5_WLAN_SR_ECO
The laptop was set to autowack by adding:
50 autowack-delay
autowack-on
to the olpc.fth file.
It was associated with an access point.
From the terminal activity, I enabled EC wakeup events using:
sudo sh
echo EC > /proc/acpi/wakeup
I then started a script (dosr) running:
for i in seq 1 100000; do echo $i; sleep 1; echo mem >
/sys/power/state; done;
After twenty cycles, I stopped it and checked the interface using iwconfig
and ping the gateway just fine.
I restarted it, and after ten or so cycles I noticed that the WLAN LED was
flashing very quickly. I stopped, and when I typed iwconfig it took many
second to respond. This happened repeatedly.
This is easy to reproduce.
--
--
Ticket URL: <http://dev.laptop.org/ticket/9744#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list