Upgraded from v262 to the latest (v413) and got:

hijack(12): memory violation at pc=0x020045a0, lr=0x02004548 (bad address=0x464c4587, code 2)
pc : [<020045a0>] lr : [<02004548>]
sp : bffffe80 ip : bffffea0 fp : bffffe9c
r10: 020006c8 r9 : 00000000 r8 : 0202f010
r7 : 0203ff30 r6 : 464c457f r5 : 0203ff20 r4 : 00000010
r3 : 00001069 r2 : 00000010 r1 : 00001068 r0 : 464c457f
Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0F3D17D Table: C0F3D17D DAC: 00000015
Function entered at [<02004578>] from [<02004548>]
r7 = 00000000 r6 = 020000C0 r5 = 0203FF20 r4 = 464C457F
Function entered at [<020044a0>] from [<020009c0>]
r5 = BFFFFF74 r4 = 00000001
Function entered at [<020006c8>] from [<02000b64>]
Function entered at [<02000a88>] from [<02000104>]
r10 = 00000000 r8 = 00000000 r7 = 00000000 r6 = 00000000
r5 = 00000000 r4 = 00000000

Machine runs, but network is unusable. Maybe one or two pings will get through with > 1000 ms latency, but nothing much more.

Rolled over to the v410/ext3 build, and the same thing. About to go back to v262. Anyone have any ideas?

All of those numbers look like nonsense -- none of the addresses are valid for kernel space.

Which means.. you probably tried upgrading your player's DRAM.

Post a full boot log for us, please. It will likely contain further clues as to what is wrong with your player.

Cheers

Player has not been modified at all - no dram upgrades, no nothing. It's as it came from the manufacturing line. No errors under older (~ v300) kernels. I will post a full boot log for you soon. I think the network problem may not have been related to the oops. I will advise.

Oh, I know why none of the addresses were in kernel space.. it was not the kernel that crashed (oops'd).

It's something that is being run in user space.

You already mentioned ext3 in passing.. what other add-on software is in this player?

Cheers

I am not actually running ext3, but might at some stage. Hence trying out that kernel. I'm actually using my own compile of your v291 tree which has worked pretty good for a long time. I wonder which app is causing it? I'm running a telnetd, and empacman. Did the hijack ioctl extensions change slightly in newer versions? Btw, network problem was indeed something else.

Process of elimination

Try disabling things until it stops happening AND post a boot log (click)