Author Topic: How Kernel Handles Pxa255 On 5600?  (Read 5650 times)

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« on: April 18, 2005, 09:03:03 am »
Hi everyone... i'm new here...
I own a poodle, and a couple of days ago i decided to install OpenZaurus on it.
Well, i must say it's really working good for me...
Now, let's get to the real question of the post:
since my poodle has a pxa255 processor, i'd like to know how the kernel that comes with the 3.5.3 distribution handles this fact... from the messages during the boot process it seems it recognizes my processor as a pxa250, but i know (from cat /proc/somewhat) that it's not...
is the kernel optimized also for the pxa255? or it just assumes all the poodles have the pxa250? is there a way to force the pxa255 detection? and is the cache errata workaround enabled as default in this kernel?
i googled around but couldn't find any answers to these questions... hope you can help!!
Thanks a lot for your time, and keep up the good work guys.... you ROCK!!
Bye
Marco

ced

  • Full Member
  • ***
  • Posts: 225
    • View Profile
    • http://
How Kernel Handles Pxa255 On 5600?
« Reply #1 on: April 19, 2005, 04:04:18 am »
yes... the kernel has the "cache bug errata enabled. so yes you don't get a full speed kernel for your pxa255.
In the previous release (3.5.2), I've asked Mickeyl to produce another kernel for the poodle and he told me it'll be available for OZ 3.5.3... I think Mickeyl has too much stuff to do... :-)

My OE setup is configured for an alpha kernel 2.6 and I don't really want to mess that up...
SL-5600, kernel 2.6.16 + GPE from .dev
Ethernet Socket LP-E
Viking 256M SD

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #2 on: April 19, 2005, 05:10:43 am »
hi ced!
well... i might be interested in recompiling the kernel... i'm used to it on my gentoo box, it can't be so different...
maybe you can point me out some place where i can find a guide to do it without spending too much time reinventing the wheel...
thanks again for your time...
Marco

Mickeyl

  • Hero Member
  • *****
  • Posts: 1495
    • View Profile
    • http://www.Vanille.de
How Kernel Handles Pxa255 On 5600?
« Reply #3 on: April 19, 2005, 08:53:45 am »
Quote
I've asked Mickeyl to produce another kernel for the poodle and he told me it'll be available for OZ 3.5.3... I think Mickeyl has too much stuff to do... :-)
No kidding. I didn't forget you though, I'll cook your kernel this week.
Cheers,

Michael 'Mickey' Lauer | Embedded Linux Freelancer | www.Vanille-Media.de
Consider donating, if you like the software I contribute to.

Mickeyl

  • Hero Member
  • *****
  • Posts: 1495
    • View Profile
    • http://www.Vanille.de
Cheers,

Michael 'Mickey' Lauer | Embedded Linux Freelancer | www.Vanille-Media.de
Consider donating, if you like the software I contribute to.

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #5 on: April 19, 2005, 09:21:32 am »
Thanks a lot mickeyl... saved me a lot of time...
I'll try it this evening and report how it goes...  
bye
Marco
« Last Edit: April 19, 2005, 09:21:55 am by ShaneFalco »

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #6 on: April 19, 2005, 04:00:40 pm »
I just flashed the new kernel...
it boots fine, seems pretty faster and more responsive...
sadly, when i plug in the wireless card the kernel dumps after the "Checking CFTABLE_ENTRY 0x01" line saying "unable to handle kernel paging request at virtual address 000x0160".
The system remains usable... but the card never shows up in the tray...
my wireless card is a Netgear MA701.
i'm thinking about what went wrong...

ps.
mickeyl, could you post the md5 of the new kernel? you never know...
if you haven't time, no problem...
« Last Edit: April 19, 2005, 04:02:55 pm by ShaneFalco »

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #7 on: April 19, 2005, 04:30:45 pm »
wow... i ran some tests, and it's about 50% faster in integer arithmetic...
using the tests in system info...
« Last Edit: April 19, 2005, 04:31:05 pm by ShaneFalco »

Mickeyl

  • Hero Member
  • *****
  • Posts: 1495
    • View Profile
    • http://www.Vanille.de
How Kernel Handles Pxa255 On 5600?
« Reply #8 on: April 19, 2005, 05:11:59 pm »
should be 287d0ac085086b7622eeba9eb33cfa6e
Cheers,

Michael 'Mickey' Lauer | Embedded Linux Freelancer | www.Vanille-Media.de
Consider donating, if you like the software I contribute to.

Greg2

  • Hero Member
  • *****
  • Posts: 790
    • View Profile
    • http://
How Kernel Handles Pxa255 On 5600?
« Reply #9 on: April 19, 2005, 05:17:32 pm »
@ 'anyone' that wants to test this kernel

Mickey's release note on the openzaurus-users mailing list:
Quote
FYI: I just uploaded a poodle zImage for those lucky folks with a PXA255
 model.
 Note: Although you could install this kernel also to the PXA250 models,
 we don"t recommend that and we will ignore all bug reports from you in
 that case. Running the PXA255 kernel on PXA250 is _not_ (repeat: NOT)
 supported.
 --
 Regards,
 
 Mickey.
@Mickey

Thanks for doing this. What things I've had a chance to check and use so far have worked very well on the 'PXA250' with this kernel. I will check out my wireless card tomorro... I don't have it with me now.

I will attach the Benchmarks before and after new kernel here.

Thanks again,

Greg

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #10 on: April 19, 2005, 05:54:22 pm »
Checked the md5, it matches... so it must be some kind of problem with the hostap driver i think...
i'll try to make some tests tomorrow...

beday00

  • Newbie
  • *
  • Posts: 9
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #11 on: April 20, 2005, 02:49:42 am »
I just flashed to the new kernel and I have experienced the same problem as ShaneFalco.  I am using a Linksys WCF12 and this the last part of the output from dmesg

hostap_cs_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen<jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: ignoring Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
Unable to handle kernel paging request at virtual address 000e0160
pgd = c1c54000
*pgd = alc53001, *pmd = a1c53001, *pte = 0000
Internal error: Oops: ffffffff
CPU: 0
... followed by what looks like a dump of some sort (if you need the rest let me know)

If I can do anything else to help let me know.
« Last Edit: April 20, 2005, 03:01:39 am by beday00 »

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #12 on: April 20, 2005, 05:39:54 pm »
made some other tests...
kernel dumps also when setting up a usb connection with a pc (in my case a gentoo box)...
ethernet seems up in the network config, but when you click ok it tries to restart the connection and there the kernel dumps with a similar error...
i'm too tired right now to check it out better, maybe i'll do that tomorrow...
good night!!

Greg2

  • Hero Member
  • *****
  • Posts: 790
    • View Profile
    • http://
How Kernel Handles Pxa255 On 5600?
« Reply #13 on: April 21, 2005, 10:06:36 am »
Just for the record and completeness of the thread my wireless card shows the same errors in dmesg as listed by ShaneFalco... but I'm using a PXA250 so that is not relevant here.

@ ShaneFalco

You might try from your terminal:

modprobe hostap

then insert your wireless card and post the readout of:

dmesg
cardctl ident
lsmod

You might also want to post this info on the openzaurus-users mailing list. Then maybe someone that knows more than I can be of some help to you and other poodle owners.

Greg

ShaneFalco

  • Newbie
  • *
  • Posts: 13
    • View Profile
How Kernel Handles Pxa255 On 5600?
« Reply #14 on: April 21, 2005, 12:22:11 pm »
hope this can help...

fresh boot, did modprobe hostap inserted the wireless card and here are the results:

dmesg:
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: ignoring Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
Unable to handle kernel paging request at virtual address 000e0160
pgd = c1008000
*pgd = a119c801, *pmd = a119c801, *pte = 00000000, *ppte = 00000000
Internal error: Oops: ffffffff
CPU: 0
pc : [<c39e57c8>]    lr : [<c00f2404>]    Tainted: P
sp : c1db97c0  ip : c1db978c  fp : c1db97e8
r10: c0dd1000  r9 : 00000000  r8 : c1db99f4
r7 : 000e00e0  r6 : 00000000  r5 : c39eb11c  r4 : c39eb108
r3 : 000e06a8  r2 : 000e0001  r1 : c01bffae  r0 : c0dd1000
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 197F  Table: A1008000  DAC: 00000015  PID:  0
Process cardmgr (pid: 687, stackpage=c1db9000)
Stack: (0xc1db97b0 to 0xc1dba000)
97a0:                                     c00f2404 c39e57c8 a0000013 ffffffff
97c0: 00000000 c10f2380 c1db9b68 00000000 c1db99f4 c39eb028 c1db97f0 c1db9bb0
97e0: c1db97ec c39e7c88 c39e5758 e59c1000 00019801 00000301 00000077 00050910
9800: 000493e0 00057e40 c1db9a00 002dc6c0 003567e0 000f4240 00000000 c0379800
9820: c1db9b94 00000080 00000001 c1db9a70 c1db9a40 c0114938 c0114600 c1db9a48
9840: c0113c18 c03700ff c1db9b94 c10f2280 c10f2280 00000000 00000000 00000000
9860: 00000000 c1db9a74 00000000 c011487c c1db0146 00000000 00000040 00000000
9880: c1db9bcc c1db9a94 c0116008 c01145e8 c1db9ac8 c1db9aa4 c0114834 c01142dc
98a0: c1db9aa8 00000000 c0379800 c1db9c74 00000080 00000001 c1db9afc c1db9acc
98c0: c0114938 c01146f0 c1db9ad4 00000000 000000ff c1db9b00 c032bb60 c1db9cc4
98e0: 00000001 00000000 00000001 c1db9cbc c1db9b00 0000007f 0000ffff 00020001
9900: 00000081 c01e2f04 00000000 00000000 000001d2 c01e2f00 c01e2ce8 c1db9b5c
9920: c1db9b30 c1db9b80 c1db9b38 c01aacd4 c01aa044 c1db9bdc 000028e7 c1db9b68
9940: ffffffb2 60000013 60000013 00000026 c10f23ac 00000000 c1db9b80 c1db9b6c
9960: c0030e00 00000000 00000000 00000021 00000021 00000021 c01a7dac c1db99c4
9980: 00000004 c032bb60 c1db9b00 00000000 00000000 c1db9c74 000d0000 00001000
99a0: c39d0000 00000000 00000000 c1db9a04 c1db99bc 771901c1 b5351eb5 063e363c
99c0: ffff7f46 00000005 00000010 c0379b72 00000000 c1db9a1c c1db9a14 c1db99e8
99e0: c0114320 c01a7dac c0379800 c1db9b94 00000000 00019801 00000301 00000077
9a00: 00050910 000493e0 00057e40 c1db9a00 002dc6c0 003567e0 000f4240 00000000
9a20: c0379800 c1db9b94 00000080 00000001 c1db9a70 c1db9a40 c0114938 c0114600
9a40: c1db9a48 c0113c18 c03700ff c1db9b94 c10f2280 c10f2280 00000000 00000000
9a60: 00000000 00000000 c1db9a74 00000000 c011487c c1db0146 00000000 00000040
9a80: 00000000 c1db9bcc c1db9a94 c0116008 c01145e8 c1db9ac8 c1db9aa4 c0114834
9aa0: c01142dc c1db9aa8 00000000 c0379800 c1db9c74 00000080 00000001 c1db9afc
9ac0: c1db9acc c0114938 c01146f0 c1db9ad4 00000000 000000ff c1db9b00 c032bb60
9ae0: c1db9cc4 00000001 00000000 00000001 c1db9cbc c1db9b00 0000007f 0000ffff
9b00: 00020001 00000081 c01e2f04 00000000 00000000 000001d2 c01e2f00 c01e2ce8
9b20: c1db9b5c c1db9b30 c1db9b80 c1db9b38 c01aacd4 c01aa044 c1db9bdc 000028e7
9b40: c1db9b68 ffffffb2 60000013 60000013 00000026 c10f23ac 00000000 c1db9b80
9b60: c1db9b6c c0030e00 00000000 c020d11b 00000110 00000000 00000070 4000101b
9b80: c0030d10 c1db99b4 c10f2380 c10f2280 00000000 00000000 c10f23ac c0238554
9ba0: 00000000 c1db9bcc c1db9bb4 c39e801c c39e78c8 c0379800 c10f2280 c10f22bc
9bc0: c1db9c40 c1db9bd0 c011b084 c39e7fac c002d35c ffffffd8 60000013 60000013
9be0: 00000028 00000000 c032ba60 c1db9c10 c1db9bfc c0030e24 c002d99c c020d130
9c00: c01e1b8c c1db9c30 c1db9c14 c0030cdc c0030d7c c1ef64e0 c39e7fa0 c39eb028
9c20: c10f2380 00000000 00000000 0001bf60 c032ba60 c1db9c8c c1db9c44 c39e77a4
9c40: c011ae44 c39eb028 00000002 0000660c c39e7fa0 0000002f 00000000 00000000
9c60: c1db9c90 c1db9c8c c10f2380 c011a284 00000210 c1ef64e0 c1f6ec60 c1db9cc4
9c80: c1db9cbc c1db9c90 c0118288 c39e771c c0000000 c1f6ec60 c050643c c032ba60
9ca0: 00000000 00000000 00000000 00000050 c1db9f80 c1db9cc0 c0118e68 c01180f8
9cc0: 80000000 74736f68 635f7061 00000073 00000000 00000000 00000000 00000000
9ce0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
9d00: 00000000 00000000 00000000 00000000 00000000 00000000 4005a328 00000000
9d20: 00000000 4005b200 00000000 00000000 00000000 00000000 00000000 4013a598
9d40: 00039048 00000013 000391cc 3331fb20 4012987f 000391d3 00000000 000391c8
9d60: 00000081 c01e2f04 c1c37860 00000000 00000081 c01e2f04 c0ead620 00000000
9d80: 000001d2 c01e2f00 c01e2ce8 c1db9dc8 c1db9d9c c004b1f0 c004ad38 c0c29480
9da0: c02413a8 c1db9dd0 c1db9db4 c012e168 c0048e68 c0ca2a60 ffffffe0 7fffffff
9dc0: 00000000 c1db9dfc c1db9dd4 c012d4fc c10f2280 00000062 c02ed700 c02ed700
9de0: 7fffffff c0ca2a60 c1db9e94 00000062 c1db9e10 c1db9e00 c012ddbc c002d99c
9e00: c0c29480 c1db9e50 c1db9e14 c01720d8 c012dd90 ffffffff c1db9e20 00000000
9e20: ffffffe0 c1db9e30 c1db9e54 00000000 c0c403a0 00000062 00000000 c1db8000
9e40: 00000000 c1db9e84 c1db9e54 c012ad14 c0171d40 000002af 00000000 c02743c0
9e60: a0b2f0bf 00001000 40015000 00000001 c10cf454 c1db9e90 c1db9e84 c004b410
9e80: c004aaa4 c1db9ea4 c1db9e94 c004b8f8 c004b3cc c02743c0 c1db9eb8 c1db9ea8
9ea0: c003e958 c004b8b4 00000000 c1db9f04 c1db9ebc c003edec c003e90c 00000001
9ec0: 00000001 40115000 40016000 c1009004 c1009004 00000001 40016000 40015000
9ee0: c1e78440 40016000 c1db8000 c1e78440 00000000 00000000 c1db9f24 c1db9f08
9f00: c003ef4c c003ec84 00001000 c0ead620 40015000 40015000 c1db9f48 c1db9f28
9f20: c004160c c0048f98 c0ead620 40015000 00000000 40015000 00000000 c1db9f84
9f40: c1db9f4c c0041ac4 c0041740 c1c37800 00001000 c1c37800 c001b6a0 c050643c
9f60: 00000003 0001bf60 ffffffe7 c1db8000 0001bf60 c1db9fa4 c1db9f84 c0061460
9f80: c011890c 00000002 00000001 00040838 00000036 c001d9e4 00000000 c1db9fa8
9fa0: c001d840 c0061270 00000002 c002362c 00000003 c050643c 0001bf60 00040838
9fc0: 00000002 00000001 00040838 00000000 00040838 00000000 0001bf60 bffff468
9fe0: 0001b1d0 bffff438 0000a400 400d8584 20000010 00000003 e59f1154 e5910000
Backtrace:
Function entered at [<c39e574c>] from [<c39e7c88>]
Function entered at [<c39e78bc>] from [<c39e801c>]
Function entered at [<c39e7fa0>] from [<c011b084>]
 r6 = C10F22BC  r5 = C10F2280  r4 = C0379800
Function entered at [<c011ae38>] from [<c39e77a4>]
Function entered at [<c39e7710>] from [<c0118288>]
 r6 = C1DB9CC4  r5 = C1F6EC60  r4 = C1EF64E0
Function entered at [<c01180ec>] from [<c0118e68>]
Function entered at [<c0118900>] from [<c0061460>]
Function entered at [<c0061264>] from [<c001d840>]
 r8 = C001D9E4  r7 = 00000036  r6 = 00040838  r5 = 00000001
 r4 = 00000002
Code: e28230df e3c37003 e2873d17 e2833008 (e5873080)

cardctl ident:
Socket 0:
  product info: "NETGEAR", "MA701 Wireless CF Card", ""
  manfid: 0xd601, 0x0002
  function: 6 (network)
Socket 1:
  no product info available

lsmod:
Module                  Size  Used by    Tainted: P  
hostap_cs              46484   0 (unused)
hostap                 97288   0 [hostap_cs]
rfcomm                 33488   0 (autoclean)
l2cap                  17028   2 (autoclean) [rfcomm]
bluez                  32616   1 (autoclean) [rfcomm l2cap]
sharp_mmcsd_m          26200   3
pxa_bi                 20028   0 (unused)
net_fd                 25012   0 (unused)
usbdcore               30424   0 [pxa_bi net_fd]