On Feb 15, 2011, at 3:16 AM, Sridhar Dhanapalan wrote:
> Is there a chance that it's related to
> http://wiki.laptop.org/go/XO1.5_WLAN_ESD_protection
Given the production dates of those laptops, that is almost
certainly the problem.
Swapping out the WLAN card will fix it.
Regards,
wad
___
On Tue, Feb 15, 2011 at 07:16:18PM +1100, Sridhar Dhanapalan wrote:
> Is there a chance that it's related to
> http://wiki.laptop.org/go/XO1.5_WLAN_ESD_protection
>
> or is that out of the question?
I don't know. I expect Martin will know. The serial number range you
reported is ISO week 19 of
On 15 February 2011 17:56, James Cameron wrote:
> On Tue, Feb 15, 2011 at 03:48:24PM +1100, Sridhar Dhanapalan wrote:
>> After upgrading the Q3A50 one to Q3A62, I get slightly different
>> output from the WLAN test:
>>
>> SDHCI: Error: ISR = 8000 ESR = 1 Command Timeout,
>> Command reg: 50a Mo
On Tue, Feb 15, 2011 at 03:48:24PM +1100, Sridhar Dhanapalan wrote:
> After upgrading the Q3A50 one to Q3A62, I get slightly different
> output from the WLAN test:
>
> SDHCI: Error: ISR = 8000 ESR = 1 Command Timeout,
> Command reg: 50a Mode reg: 0 Arg reg: 0
> Recent commands (decimal): 0 5
On Mon, Feb 14, 2011 at 09:39:33PM -0800, Hal Murray wrote:
> 7500 isn't very many packets.
Good point. It isn't the packet loss that I'm looking for, (there will
always be some, and even more when flooding), but rather complaints of
SDHCI problems from the kernel, to match against the complaints
> I don't see any problems in Linux. Following James' advice, I associated
> with an AP and pinged the gateway for a few hours. Over ~7500 pings, I had
> 1% packet loss and no errors in /ver/log/dmesg.
7500 isn't very many packets.
Try ping -f. (f for flood, need to be root)
It takes me 13 se
On 15 February 2011 15:25, James Cameron wrote:
> On Tue, Feb 15, 2011 at 02:37:21PM +1100, Sridhar Dhanapalan wrote:
>> Possibly related to this, we have at least 20x XO-1.5s that have
>> completely dead WLAN. The OpenFirmware wireless test fails
>> immediately.
>
> In what way does the test fail
On Tue, Feb 15, 2011 at 02:37:21PM +1100, Sridhar Dhanapalan wrote:
> Possibly related to this, we have at least 20x XO-1.5s that have
> completely dead WLAN. The OpenFirmware wireless test fails
> immediately.
In what way does the test fail?
What version of OpenFirmware was used to test with?
>
On 15 February 2011 14:27, Sridhar Dhanapalan wrote:
> On 12 February 2011 01:39, Martin Langhoff wrote:
>> On Fri, Feb 11, 2011 at 2:54 AM, James Cameron wrote:
>>> I'm quite familiar with that part of the SDHCI implementation in the
>>> firmware.
>>
>> And practical experience in the field bac
On 12 February 2011 01:39, Martin Langhoff wrote:
> On Fri, Feb 11, 2011 at 2:54 AM, James Cameron wrote:
>> I'm quite familiar with that part of the SDHCI implementation in the
>> firmware.
>
> And practical experience in the field backs James' and Chris' notes
> and recommendations :-)
>
> The
On Fri, Feb 11, 2011 at 2:54 AM, James Cameron wrote:
> I'm quite familiar with that part of the SDHCI implementation in the
> firmware.
And practical experience in the field backs James' and Chris' notes
and recommendations :-)
The wlan card is acting up. Maybe I can add a suggestion to test it
On Fri, Feb 11, 2011 at 04:16:52PM +1100, Sridhar Dhanapalan wrote:
> I am seeing NANDblaster (nb-secure) fail after some time (from my
> tests, anywhere between 30 minutes to an hour).
I'm aware you have a workaround, (use another unit), but I'll address the
problem further:
> The text was scrol
On 11 February 2011 16:58, Sridhar Dhanapalan wrote:
> On 11 February 2011 16:31, Chris Ball wrote:
>> Hi,
>>
>> > I am seeing NANDblaster (nb-secure) fail after some time (from my
>> > tests, anywhere between 30 minutes to an hour).
>> >
>> > The text was scrolling very fast (screenshots
On 11 February 2011 16:31, Chris Ball wrote:
> Hi,
>
> > I am seeing NANDblaster (nb-secure) fail after some time (from my
> > tests, anywhere between 30 minutes to an hour).
> >
> > The text was scrolling very fast (screenshots attached), but I
> > think it was:
> >
> > SDHCI: Err
Hi,
> SDHCI is that not the mmc controller? Don't think data is
> directly using it, power management kicking in maybe?
The wifi card, which is serving the image to the other machines, is
an SDIO card.
- Chris.
--
Chris Ball
One Laptop Per Child
On Fri, 2011-02-11 at 16:16 +1100, Sridhar Dhanapalan wrote:
> I am seeing NANDblaster (nb-secure) fail after some time (from my
> tests, anywhere between 30 minutes to an hour).
>
> The text was scrolling very fast (screenshots attached), but I think it was:
>
> SDHCI: Error: ISR = 8000 ESR =
Hi,
> I am seeing NANDblaster (nb-secure) fail after some time (from my
> tests, anywhere between 30 minutes to an hour).
>
> The text was scrolling very fast (screenshots attached), but I
> think it was:
>
> SDHCI: Error: ISR = 8000 ESR = 3 Command CRC, Command Timeout,
On 11 February 2011 16:16, Sridhar Dhanapalan wrote:
> I am seeing NANDblaster (nb-secure) fail after some time (from my
> tests, anywhere between 30 minutes to an hour).
>
> The text was scrolling very fast (screenshots attached), but I think it was:
>
> SDHCI: Error: ISR = 8000 ESR = 3 Command
I am seeing NANDblaster (nb-secure) fail after some time (from my
tests, anywhere between 30 minutes to an hour).
The text was scrolling very fast (screenshots attached), but I think it was:
SDHCI: Error: ISR = 8000 ESR = 3 Command CRC, Command Timeout,
Command reg: 341a Mode reg: 0 Arg reg:
19 matches
Mail list logo
