• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Kernel / Re: page allocation failure: order:2, mode:0x4020 on: November 02, 2012, 06:58:35 AM
Oops,

It happens indeed with the stock Debian kernel, just not as frequently.

N.
2  Linux Stuff / Kernel / Re: page allocation failure: order:2, mode:0x4020 on: October 28, 2012, 03:09:55 AM
Just to clarify, this doesn't happen with the Debian kernel

Linux version 2.6.32-5-kirkwood (Debian 2.6.32-46) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) )

coming from http://www.cyrius.com/debian/kirkwood/sheevaplug/

dd if=/dev/zero of=/dev/sda bs=1M
^C122886+0 records in
122886+0 records out
128855310336 bytes (129 GB) copied, 966.649 s, 133 MB/s


And not a single message.

Regards,
N.
3  Hardware and U-Boot firmware / Hardware / Re: External HD not recognized by sheevaplug on: October 27, 2012, 08:24:56 AM
I tried the 3.5.7 and my sata disk didnít show. Going back to 3.4.7 gave me my sata disk back. I run U-Boot 2011.12 on an esata sheevaplug.

regards,
N.
4  Linux Stuff / Kernel / page allocation failure: order:2, mode:0x4020 on: October 27, 2012, 07:41:38 AM
My console and log files are filled with this message. The process involved varies, but it always happens when the system is a little stressed.

I can easily reproduce it by running dd on a sata disk

root@plug:~# dd if=/dev/zero of=/dev/sdb bs=1M
^C3819+0 records in
3819+0 records out
4004511744 bytes (4.0 GB) copied, 37.636 s, 106 MB/s


The speed seems to be OK and top gives:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
 3419 root      20   0  4472 1608  496 R 66.4  0.3   0:24.32 dd

And the log reads:

plug kernel: dd: page allocation failure: order:2, mode:0x4020
plug kernel: [<c000d070>] (unwind_backtrace+0x0/0xe0) from [<c0083e84>] (warn_alloc_failed+0xf4/0x120)
plug kernel: [<c0083e84>] (warn_alloc_failed+0xf4/0x120) from [<c008613c>] (__alloc_pages_nodemask+0x544/0x65c)
plug kernel: [<c008613c>] (__alloc_pages_nodemask+0x544/0x65c) from [<c0086264>] (__get_free_pages+0x10/0x3c)
plug kernel: [<c0086264>] (__get_free_pages+0x10/0x3c) from [<c00af028>] (kmalloc_order_trace+0x20/0xd0)
plug kernel: [<c00af028>] (kmalloc_order_trace+0x20/0xd0) from [<c0373808>] (__alloc_skb+0x50/0xf0)
plug kernel: [<c0373808>] (__alloc_skb+0x50/0xf0) from [<c0373cdc>] (__netdev_alloc_skb+0x1c/0x44)
plug kernel: [<c0373cdc>] (__netdev_alloc_skb+0x1c/0x44) from [<c0304134>] (rxq_refill+0x1b8/0x1d8)
plug kernel: [<c0304134>] (rxq_refill+0x1b8/0x1d8) from [<c0304924>] (mv643xx_eth_poll+0x5d8/0x660)
plug kernel: [<c0304924>] (mv643xx_eth_poll+0x5d8/0x660) from [<c037cecc>] (net_rx_action+0x5c/0x204)
plug kernel: [<c037cecc>] (net_rx_action+0x5c/0x204) from [<c001b208>] (__do_softirq+0xf4/0x240)
plug kernel: [<c001b208>] (__do_softirq+0xf4/0x240) from [<c001b784>] (irq_exit+0x44/0x9c)
plug kernel: [<c001b784>] (irq_exit+0x44/0x9c) from [<c0009418>] (handle_IRQ+0x64/0x84)
plug kernel: [<c0009418>] (handle_IRQ+0x64/0x84) from [<c044c4d4>] (__irq_svc+0x34/0x98)
plug kernel: [<c044c4d4>] (__irq_svc+0x34/0x98) from [<c024e264>] (__copy_from_user+0x90/0x42c)
plug kernel: Mem-info:
plug kernel: Normal per-cpu:
plug kernel: CPU    0: hi:  186, btch:  31 usd:   5
plug kernel: active_anon:2649 inactive_anon:2688 isolated_anon:0
plug kernel: active_file:4439 inactive_file:112238 isolated_file:0
plug kernel: unevictable:0 dirty:10295 writeback:3201 unstable:0
plug kernel: free:967 slab_reclaimable:2602 slab_unreclaimable:879
plug kernel: mapped:2141 shmem:35 pagetables:150 bounce:0
plug kernel: Normal free:3868kB min:2884kB low:3604kB high:4324kB active_anon:10596kB inactive_anon:10752kB acti
ve_file:17756kB inactive_file:448952kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:520192kB mlocked:0kB dirty:
41180kB writeback:12804kB mapped:8564kB shmem:140kB slab_reclaimable:10408kB slab_unreclaimable:3516kB kernel_stack:544kB pageta
bles:600kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
plug kernel: lowmem_reserve[]: 0 0
plug kernel: Normal: 901*4kB 1*8kB 2*16kB 1*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 386
8kB
plug kernel: 116720 total pagecache pages
plug kernel: 0 pages in swap cache
plug kernel: Swap cache stats: add 0, delete 0, find 0/0
plug kernel: Free swap  = 526996kB
plug kernel: Total swap = 526996kB
plug kernel: 131072 pages of RAM
plug kernel: 1115 free pages
plug kernel: 2761 reserved pages
plug kernel: 3260 slab pages
plug kernel: 119397 pages shared
plug kernel: 0 pages swap cached


It happens with kernel 3.4.7 and 2.6.38.5, so it's old. Beside the fact that it annoys me because it fills the log, should I worry?

Rgds,
Nicolas
5  Linux Stuff / Kernel / Re: mmc support in 2.6.37 and 2.6.38 on: May 04, 2011, 10:17:24 AM
Here is my uboot env from the console. uboot version is Newit one (uboot-sata-090903.bin).

Code:
Marvell>> reset

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF120

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
serverip=10.10.0.2
ipaddr=10.10.0.1
cesvcid=ULULULULULULPPULULULULULDA
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:4C:23
run_diag=no
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
arcNumber=2678
bootargs_console=console=ttyS0,115200
bootargs_mtd=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
bootargs_mmc=root=/dev/mmcblk0p2
load_mmc=ext2load mmc 0:1 0x00800000 /uImage
bootcmd_mtd=setenv bootargs $(bootargs_console) $(bootargs_mtd); nand read.e 0x800000 0x100000 0x300000; bootm 0x800000
bootcmd_mmc=mmcinit; run load_mmc; setenv bootargs $(bootargs_console) $(bootargs_mmc); bootm 0x00800000
bootargs_usb=root=/dev/sda2 rootdelay=10
bootcmd_usb=setenv bootargs $(bootargs_console) $(bootargs_usb); usb start; ext2load usb 0:1 0x00800000 /uImage; bootm 0x00800000
bootcmd=run bootcmd_usb; run bootcmd_mmc;run bootcmd_mtd
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes

Environment size: 1883/131068 bytes

And Here is the fstab.

Code:
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/mmcblk0p2 during installation
UUID=2d32987a-81f5-4d9b-9e84-0585ffce1645 /               ext3    errors=remount-ro 0       1
# /boot was on /dev/mmcblk0p1 during installation
UUID=18da8739-d1c8-4b88-b60e-c25a58d9d4b0 /boot           ext2    defaults        0       2
# swap was on /dev/mmcblk0p5 during installation
UUID=c5c9015d-6d3b-42e8-bcfd-f382a19012e8 none            swap    sw              0       0
/dev/sda1       /media/usb0     auto    rw,user,noauto  0       0

Regards,
N.
6  Linux Stuff / Kernel / Re: mmc support in 2.6.37 and 2.6.38 on: May 04, 2011, 03:29:25 AM
Sorry, yes I'm speaking of the sheeva.with-linux kernels.

I get the following oops with 2.6.37 and 2.6.38, but not the previous ones:

Code:
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0  (driver?)
1f01            4096 mtdblock1  (driver?)
1f02          519168 mtdblock2  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c00355d4>] (unwind_backtrace+0x0/0xe0) from [<c0409378>] (panic+0x58/0x17c)
[<c0409378>] (panic+0x58/0x17c) from [<c0008d98>] (mount_block_root+0x1bc/0x1fc)
[<c0008d98>] (mount_block_root+0x1bc/0x1fc) from [<c0008f70>] (mount_root+0xa0/0xc0)
[<c0008f70>] (mount_root+0xa0/0xc0) from [<c00090f4>] (prepare_namespace+0x164/0x1b8)
[<c00090f4>] (prepare_namespace+0x164/0x1b8) from [<c00089f0>] (kernel_init+0x10c/0x14c)
[<c00089f0>] (kernel_init+0x10c/0x14c) from [<c0031494>] (kernel_thread_exit+0x0/0x8)

I just change a symlink in the /boot partition to switch kernels, so the remaining of the system is identical.

Regards,
N.
7  Linux Stuff / Kernel / mmc support in 2.6.37 and 2.6.38 on: May 03, 2011, 06:17:52 AM
I just tried the last kernel (2.6.35.13, 2.6.36.4, 2.6.37.6, 2.6.38.4 and 2.38.5).  The 2.6.37 and 2.6.38 fail to mount the root filesystem from mmcblk0p2 where the 2.6.35 and 2.6.36 succeed.

Is the mmc support deprecated?  I've my /boot on mmcblk0p1 (ext2) and the root on mmcblk0p2 (ext3). I thought it was a common setup.

Regards,
N.
8  Linux Stuff / Kernel / eSATA PM on 2.6.35.7 works on: October 12, 2010, 12:14:10 PM
I just find the time to try it and I can confirm that my eSATA PM is recognized now.

Thanks,
Nicolas
9  Linux Stuff / Kernel / Re: 2.6.35.4 new release on: August 29, 2010, 12:04:14 AM
Try 2.6.34.6.  They did a ata code reorg in 2.6.35 that seems to be causing some trouble, particularly with sata port multipliers.

Gwendal Grignou found the bug for the port multiplier bug.  The patch is on its way.
10  Linux Stuff / Kernel / Re: 2.6.35.3 new release on: August 25, 2010, 10:02:05 AM
2.6.35.3 like 2.6.35.2 doesn't recognize my port multiplier (sil3726). It's on the same esata sheeva plug.

If you're capable, you might want to peruse the changelogs on kernel.org, starting with 2.6.35 to see what changes have been made to the sata subsystem.  Maybe you'll run across something that could be the culprit.

I posted a message on lkml.  Marc Lord suggested to apply some patches (quite unrelated for my untrained eyes).  I still have to do that.  And there is a bugzilla entry as well: https://bugzilla.kernel.org/show_bug.cgi?id=17071


ok, i had a chance to look at some changes between 2.6.34.x and 2.6.35.x.  I reverted one commit and turned an option off in the config.

A new 2.6.35.3 testing kernel is in /sheeva/testing/ please test and report back...if it doesn't work i'd like you to "lsmod" so we can see which modules you've got loaded.

Quite a few changes have been made in the sata subsystem, although most of them are not too likely.


Sorry, I didn't find time before now to test your changes.  There is some progress, the failure message doesn't loop indefinitely now, but it still doesn't work :-(
11  Linux Stuff / Kernel / Re: 2.6.35.3 new release on: August 21, 2010, 02:42:16 AM
2.6.35.3 like 2.6.35.2 doesn't recognize my port multiplier (sil3726). It's on the same esata sheeva plug.  The console says:

ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
ata2.00: hard resetting link
ata2.01: hard resetting link
ata2.02: hard resetting link
ata2.03: hard resetting link
ata2.04: hard resetting link
ata2.05: hard resetting link
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2.15: hard resetting link
ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.00: hard resetting link
ata2.01: hard resetting link
ata2.02: hard resetting link
ata2.04: hard resetting link
ata2.05: hard resetting link
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)

ad nauseum.
12  Linux Stuff / Kernel / Re: 2.6.35.2 new release on: August 20, 2010, 09:41:41 AM
hmm, a regular esata plug, not a guruplug. Sorry for the vagueness.

N.
13  Linux Stuff / Kernel / Re: 2.6.35.2 new release on: August 19, 2010, 11:07:51 AM
This kernel doesn't support my port multiplier (sil3726). 2.6.34.4 does. I've not tested 2.6.35.1.

Single sata disk works.

It's a regular plug with the Feroceon 88FR131 [56251311] revision 1

N.
14  Hardware and U-Boot firmware / Hardware / Re: USB Hubs on: October 16, 2009, 09:15:09 AM
Just for info I have tried 3 different hubs to run software raid on the usb interface. I'm quite sure that I've stressed the hubs :-)

- trust 420A - 4 ports, powered: completely unreliable and on his way to the trash can;
- LaCie ? - 3 ports + mini usb device: reliable powered or not;
- Belkin F5U700 - 7 ports: reliable powered or not.

Tested on 2 "new" SheevaPlug.

N.
15  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 - fails on amd64 on: October 07, 2009, 09:20:29 AM
The installer fails reliably on amd64 (ubuntu jaunty)

openocd/openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory

investigating reveals:
:~/Desktop/sheevaplug-installer-v1.0/uboot/openocd$ ldd openocd
   linux-gate.so.1 =>  (0xf7f79000)
   libdl.so.2 => /lib32/libdl.so.2 (0xf7f52000)
   libftdi.so.1 => not found
   libusb-0.1.so.4 => /lib32/libusb-0.1.so.4 (0xf7f48000)
   libc.so.6 => /lib32/libc.so.6 (0xf7de5000)
   /lib/ld-linux.so.2 (0xf7f7a000)
:~$ sudo aptitude install libftdi
:~$ whereis libftdi.so.1
libftdi.so: /usr/lib/libftdi.so.1 /usr/lib64/libftdi.so.1
:~$ ldconfig -p|grep libftdi
   libftdi.so.1 (libc6,x86-64) => /usr/lib/libftdi.so.1

So libftdi is not included in the static openocd but I tested that a 32 bits version of jaunty do link libftdi.so.1 correctly.

Nicolas

Pages: [1]