Unable to reach some external web-pages with lynx

[jonlu]

Hello,

I'm having some problems with reaching some web-pages from bubba 2.

I ssh into the bubba and when I try to reach some pages (yle.fi and www.itsyourip.com for example) lynx reports - 'HTTP request sent; waiting for response." and then times out after about 30 seconds with unexpected network error.

Other pages like gmail and google (and this forum) works fine.

Any ideas what might block access?

[jonlu]

For the benefit of others, this was also caused by the 'silicone bug' .. I tried the solution suggested in this thread: http://forum.excito.net/viewtopic.php?t=1111

and it solved the problem.

Exactly what is this silicone bug?

[carl]

For the benefit of others, this was also caused by the 'silicone bug' .. I tried the solution suggested in this thread: http://forum.excito.net/viewtopic.php?t=1111

and it solved the problem.

Exactly what is this silicone bug?

We have identified that it is following bug; extract from the mpc8313 errata:

eTSEC 12: Tx IP and TCP/UDP checksum generation not supported for some Tx FCB offsets
Devices:
MPC8313E
Description:
If the Tx FCB (Frame Control Block) 32-byte offset is 0x19, 0x1A, 0x1B, 0x1C, 0x1D, 0x1E or
0x1F, IP and TCP/UDP header checksum generation do not function properly. The checksum value
may be inserted in the wrong location or not inserted at all.
Projected Impact:
IP and TCP/UDP header checksum generation is not supported in LINUX and other systems in
which headers are prepended to pre-aligned packet data, or where the alignment of the Tx FCB
cannot be controlled.
This behavior applies to pseudo-header checksum insertion as well as checksum generation.
Work Around:
Align Tx FCB to a 16- or 32-byte boundary.
If the alignment of TxFCB is not controllable, set TCTRL[TUCSEN] = 0 and
TCTRL[IPCSEN] = 0 to disable IP and TCP/UDP header checksum generation.
Projected Solution:
Plan to fix in revision 2 silicon.

/Carl

[jonlu]

Well, I asked for that now didn't I

It just sounded so drastic - 'the silicone bug' as if the chip itself was faulty.
Do you know if this bug will be patchable or does it require to replace the chip?