Re: [loongson-dev] Re: Lemote's kernel master branch not currently working on Xinghuo

2014-05-21 Thread David Kuehling
 Huacai == Huacai Chen chenhua...@gmail.com writes:

 master branch need a new version of PMON, you can use this one:
 http://dev.lemote.com/files/upload/lm/kernel/testing/pmon-A1101-4.0.1.bin

Same upgrade method as for Fuloong?  Googeling around I only find
chinese documentation for Xinghuo pmon upgrade, looks like a command
such as this should work [1]:

 load -rf bfc0 (usb0,0)/pmon-A1101-2.0.6.bin

Don't understand chinese, can you confirm that bfc0 is the correct
offset for the PMON firmware?  I hope PMON's flash is just plugged not
soldered into the mainboard, in case something goes wrong!?

cheers,

David

[1] http://bbs.lemote.com/archiver/?tid-71821.html
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F


pgpao4LbUKNaD.pgp
Description: PGP signature


Re: [loongson-dev] Re: Lemote's kernel master branch not currently working on Xinghuo

2014-05-21 Thread Huacai Chen
Yes, bfc0 is the correct offset. And PMON flash is plugged, not soldered.

On Wed, May 21, 2014 at 6:10 PM, David Kuehling dvdkh...@posteo.de wrote:
 Huacai == Huacai Chen chenhua...@gmail.com writes:

 master branch need a new version of PMON, you can use this one:
 http://dev.lemote.com/files/upload/lm/kernel/testing/pmon-A1101-4.0.1.bin

 Same upgrade method as for Fuloong?  Googeling around I only find
 chinese documentation for Xinghuo pmon upgrade, looks like a command
 such as this should work [1]:

  load -rf bfc0 (usb0,0)/pmon-A1101-2.0.6.bin

 Don't understand chinese, can you confirm that bfc0 is the correct
 offset for the PMON firmware?  I hope PMON's flash is just plugged not
 soldered into the mainboard, in case something goes wrong!?

 cheers,

 David

 [1] http://bbs.lemote.com/archiver/?tid-71821.html
 --
 GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
 Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F

-- 
You received this message because you are subscribed to the Google Groups 
loongson-dev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to loongson-dev+unsubscr...@googlegroups.com.
To post to this group, send email to loongson-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/loongson-dev.
For more options, visit https://groups.google.com/d/optout.


Re: [loongson-dev] Re: Lemote's kernel master branch not currently working on Xinghuo

2014-05-21 Thread David Kuehling
 Huacai == Huacai Chen chenhua...@gmail.com writes:

 master branch need a new version of PMON, you can use this one:
 http://dev.lemote.com/files/upload/lm/kernel/testing/pmon-A1101-4.0.1.bin

Sorry to be nitpicking, but I can't find any source code that
corresponds to recent PMON versions.  Last commit in pmon.git [1] is
From 2011, highest version tag is 1.6.1.  I also looked here [2] but
found nothing new, and upstream [3] is currently offline.  

Just my fault for not looking at the right spot?  Or did Lemote
eventually close-source their PMON development?  I'd really like to stay
with an open source BIOS for now.

cheers,

David

[1] http://dev.lemote.com/cgit/pmon.git
[2] http://dev.lemote.com/code/pmon
[3] http://www.pmon2000.com/
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F


pgpWLJQM8xkPu.pgp
Description: PGP signature


[loongson-dev] lemote's 3.15-rc5 kernel reports page allocation failure

2014-05-21 Thread David Kuehling
Hi,

compiling a Loongson3a kernel with CONFIG_SMP=y on lemote's official
kernel (branch master, 7a7d4e7770) shows error messages during boot up
and in kernel log:

[   24.253906] modprobe: page allocation failure: order:0, mode:0x2000d1
[   24.402343] CPU: 3 PID: 135 Comm: modprobe Not tainted 3.15.0-rc5-dk2+ #3
[..]
[   24.992187] Call Trace:
[   24.992187] [8020c378] show_stack+0x48/0x70
[   24.992187] [807e885c] dump_stack+0x70/0x90
[   24.992187] [802f8a88] warn_alloc_failed+0x110/0x134
[   24.992187] [802fb4f8] __alloc_pages_nodemask+0x750/0x864
[   24.992187] [80339ee8] new_slab+0xe0/0x348
[..]

I did not see these kinds of errors with same config and CONFIG_SMP
disabled.  This is still with the original PMON that came installed with
the Xinghuo.  I cross-compile all my kernels with with gcc 4.7.3.

Full output of dmesg attached below.

You can find the kernels in question, including kernel config here [1]
(-dk1: without SMP, -dk2: with SMP).  

Despite these errors, the system did not immediately crash.  However I
did not allow it to boot beyond the initrd for concerns about possibly
corrupting my system.

cheers,

David

[1] https://stech.muecke.pw/david/loongson/7a7d4e7770/
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F

[   24.042968] r8169 :04:00.0 eth0: jumbo features [frames: 9200 bytes, tx 
checksumming: ko]
[   24.253906] modprobe: page allocation failure: order:0, mode:0x2000d1
[   24.402343] CPU: 3 PID: 135 Comm: modprobe Not tainted 3.15.0-rc5-dk2+ #3
[   24.546875] Stack : 7000cce3  0008 
003d
[   24.546875]5000c000 804afd98  
8131
[   24.546875]8094e308 80a246b7 813111d0 
980179166900
[   24.546875]0087 0003  
812a12a0
[   24.546875] 807e4e28 98017f7177b8 

[   24.546875]980179166460 802885e4  
8094e308
[   24.546875]0003 0087  

[   24.546875] 98017f717700  
807e885c
[   24.546875]   

[   24.546875] 8020c378 002000d1 
807e885c
[   24.546875]...
[   24.992187] Call Trace:
[   24.992187] [8020c378] show_stack+0x48/0x70
[   24.992187] [807e885c] dump_stack+0x70/0x90
[   24.992187] [802f8a88] warn_alloc_failed+0x110/0x134
[   24.992187] [802fb4f8] __alloc_pages_nodemask+0x750/0x864
[   24.992187] [80339ee8] new_slab+0xe0/0x348
[   24.992187] [807e6bc8] __slab_alloc.constprop.49+0x240/0x3b8
[   24.992187] [8033d03c] __kmalloc+0x180/0x2c4
[   24.992187] [c009cf7c] sr_probe+0x230/0x728 [sr_mod]
[   24.992187] [80649380] driver_probe_device+0xdc/0x254
[   24.992187] [80649574] __driver_attach+0x7c/0xb4
[   24.992187] [8064767c] bus_for_each_dev+0x58/0xac
[   24.992187] [806489c4] bus_add_driver+0xf0/0x1f8
[   24.992187] [80649dc8] driver_register+0xac/0xfc
[   24.992187] [c00a8040] init_sr+0x40/0x74 [sr_mod]
[   24.992187] [80200518] do_one_initcall+0x88/0x140
[   24.992187] [802a82c4] load_module+0x1c48/0x1f34
[   24.992187] [802a870c] SyS_finit_module+0x70/0x94
[   24.992187] [802197a8] handle_sys+0x128/0x14c
[   24.992187] 
[   24.992187] Mem-Info:
[   24.992187] DMA per-cpu:
[   24.992187] CPU0: hi:0, btch:   1 usd:   0
[   24.992187] CPU1: hi:0, btch:   1 usd:   0
[   24.992187] CPU2: hi:0, btch:   1 usd:   0
[   24.992187] CPU3: hi:0, btch:   1 usd:   0
[   24.992187] DMA32 per-cpu:
[   24.992187] CPU0: hi:6, btch:   1 usd:   2
[   24.992187] CPU1: hi:6, btch:   1 usd:   5
[   24.992187] CPU2: hi:6, btch:   1 usd:   2
[   24.992187] CPU3: hi:6, btch:   1 usd:   5
[   24.992187] Normal per-cpu:
[   24.992187] CPU0: hi:   42, btch:   7 usd:  32
[   24.992187] CPU1: hi:   42, btch:   7 usd:  39
[   24.992187] CPU2: hi:   42, btch:   7 usd:  17
[   24.992187] CPU3: hi:   42, btch:   7 usd:  29
[   24.992187] active_anon:403 inactive_anon:9 isolated_anon:0
[   24.992187]  active_file:2782 inactive_file:84 isolated_file:0
[   24.992187]  unevictable:0 dirty:0 writeback:0 unstable:0
[   24.992187]  free:120334 slab_reclaimable:241 slab_unreclaimable:482
[   24.992187]  mapped:255 shmem:10 pagetables:67 bounce:0
[   24.992187]  free_cma:0
[   24.992187] DMA free:0kB min:0kB low:0kB high:0kB active_anon:0kB 
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB 
isolated(anon):0kB isolated(file):0kB present:14336kB managed:0kB mlocked:0kB 
dirty:0kB