* RE: boot failure on lite5200b board
From: tnt @ 2006-02-23 10:08 UTC (permalink / raw)
To: #LI JIANGGAN#; +Cc: #WONG CHEE KHIN#, linuxppc-embedded
In-Reply-To: <84A109BF918D934CB46ACF33BCE187C002D54D7A@mail02.student.main.ntu.edu. sg>
> Thank you José María and Andrey for your advices, however the problem
> remains. I've tried setting the console (though I remember that our
> previous lite5200 board was working fine on kernel 2.4 without setting the
> console); meantime,
In 2.4 you didn't need to set the console. On 2.6 we don't use the
standard ttyS0 naming for the PSC because it causes conflict when another
serial card was inserted (in a pcmcia slot for ex.).
> I've set the booting image to 0x500000; I have also
> tried using the kernel image come together with the BSP, it's always the
> same error.
> Load address: 0x100000
In the log you sent, you still use a low load address ...
> Sylvain, I've actually using your kernel source, the compiled image is
> around 700k (compared to the 1.4M image from the BSP), but it doesn't
> solve the problem. So I presume that the problem is lying somewhere else.
Do you have a hardware debugger to see where it's stopping ?
I'm at work right now, but I'll have a look when I get home.
Sylvain
^ permalink raw reply
* Re: [PATCH] ppc32: handle Book E debug exceptions on kernel stack
From: Josh Boyer @ 2006-02-23 10:54 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-embedded, Paul Mackerras, David Gibson
In-Reply-To: <Pine.LNX.4.44.0602222217220.28948-100000@gate.crashing.org>
On Wed, 2006-02-22 at 22:19 -0600, Kumar Gala wrote:
> On Tue, 14 Feb 2006, Dale Farnsworth wrote:
>
> > From: Dale Farnsworth <dale@farnsworth.org>
> >
> > On PPC Book E processsors, we currently handle debug
> > exceptions on the critical exception stack (debug stack
> > for E200). This causes problems with the kgdb single
> > step handler, which calls smp_processor_id() and spin_lock(),
> > which reference current_thread_info(), which only works when
> > we are on the kernel stack.
> >
> > We address this by switching to the kernel stack early while
> > handling debug exceptions. Note that the entry values of r10
> > and r11 are still saved on the critical exception (or debug) stack.
> >
> > Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
> >
>
> Paul,
>
> We were wondering if you or David remember why a specific critical
> exception stack was added in the 40x port from 2.4 to 2.6?
I think Matt did that. And if I remember correctly, it was to avoid
corruption if you were in the middle of handling a normal interrupt and
a critical interrupt came in.
josh
^ permalink raw reply
* please pull powerpc-merge.git
From: Paul Mackerras @ 2006-02-23 12:05 UTC (permalink / raw)
To: torvalds; +Cc: linuxppc-dev
Linus,
Please do a pull from
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc-merge.git
There are 15 commits there: fixes for various bugs and a performance
regression, plus a defconfig update.
Thanks,
Paul.
Alan Curry:
powerpc: fix altivec_unavailable_exception Oopses
Anton Blanchard:
powerpc: Fix runlatch performance issues
powerpc64: remove broken/bitrotted HMT support
Haren Myneni:
powerpc: Trivial fix to set the proper timeout value for kdump
Kelly Daly:
powerpc: disable OProfile for iSeries
Kumar Gala:
powerpc: Enable coherency for all pages on 83xx to fix PCI data corruption
Michael Ellerman:
powerpc: Initialise hvlpevent_queue.lock correctly
powerpc: Only calculate htab_size in one place for kexec
Michal Ostrowski:
Fix race condition in hvc console.
Olaf Hering:
powerpc: change compat shmget size arg to signed
ppc: fix adb breakage in xmon
Olof Johansson:
powerpc: Update {g5,pseries,ppc64}_defconfig
R Sharada:
powerpc64: fix spinlock recursion in native_hpte_clear
Segher Boessenkool:
powerpc: Fix some MPIC + HT APIC buglets
powerpc: Don't re-assign PCI resources on Maple
arch/powerpc/configs/g5_defconfig | 174 ++++++++++--------------
arch/powerpc/configs/ppc64_defconfig | 173 ++++++++++--------------
arch/powerpc/configs/pseries_defconfig | 127 ++++++-----------
arch/powerpc/kernel/crash.c | 4 -
arch/powerpc/kernel/head_32.S | 1
arch/powerpc/kernel/head_64.S | 109 +--------------
arch/powerpc/kernel/machine_kexec_64.c | 10 -
arch/powerpc/kernel/process.c | 32 ++++
arch/powerpc/kernel/prom_init.c | 38 -----
arch/powerpc/kernel/sys_ppc32.c | 2
arch/powerpc/mm/hash_native_64.c | 7 +
arch/powerpc/mm/hash_utils_64.c | 3
arch/powerpc/oprofile/Kconfig | 1
arch/powerpc/platforms/iseries/lpevents.c | 2
arch/powerpc/platforms/iseries/setup.c | 1
arch/powerpc/platforms/maple/pci.c | 4 -
arch/powerpc/platforms/pseries/Kconfig | 7 -
arch/powerpc/sysdev/mpic.c | 9 +
arch/ppc/kernel/head.S | 1
arch/ppc/xmon/adb.c | 212 -----------------------------
arch/ppc/xmon/start.c | 169 -----------------------
arch/ppc/xmon/xmon.c | 108 ---------------
drivers/char/hvc_console.c | 8 +
include/asm-powerpc/cputable.h | 9 +
include/asm-powerpc/mmu.h | 1
include/asm-powerpc/reg.h | 33 -----
include/asm-powerpc/thread_info.h | 4 -
27 files changed, 275 insertions(+), 974 deletions(-)
delete mode 100644 arch/ppc/xmon/adb.c
^ permalink raw reply
* Re: [PATCH] ppc32: handle Book E debug exceptions on kernel stack
From: Dale Farnsworth @ 2006-02-23 14:23 UTC (permalink / raw)
To: Josh Boyer; +Cc: David Gibson, Paul Mackerras, linuxppc-embedded
In-Reply-To: <1140692043.2892.1.camel@yoda.jdub.homelinux.org>
On Thu, Feb 23, 2006 at 10:54:02AM +0000, Josh Boyer wrote:
> On Wed, 2006-02-22 at 22:19 -0600, Kumar Gala wrote:
> > On Tue, 14 Feb 2006, Dale Farnsworth wrote:
> >
> > > From: Dale Farnsworth <dale@farnsworth.org>
> > >
> > > On PPC Book E processsors, we currently handle debug
> > > exceptions on the critical exception stack (debug stack
> > > for E200). This causes problems with the kgdb single
> > > step handler, which calls smp_processor_id() and spin_lock(),
> > > which reference current_thread_info(), which only works when
> > > we are on the kernel stack.
> > >
> > > We address this by switching to the kernel stack early while
> > > handling debug exceptions. Note that the entry values of r10
> > > and r11 are still saved on the critical exception (or debug) stack.
> > >
> > > Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
> >
> > Paul,
> >
> > We were wondering if you or David remember why a specific critical
> > exception stack was added in the 40x port from 2.4 to 2.6?
>
> I think Matt did that. And if I remember correctly, it was to avoid
> corruption if you were in the middle of handling a normal interrupt and
> a critical interrupt came in.
Thanks Josh, Matt was one of the "we" who were wondering. If indeed
you are remembering correctly, then I think we're safe to use the
normal kernel stack rather than the critical exception stack.
-Dale
^ permalink raw reply
* Re: boot failure on lite5200b board
From: Marty @ GMail @ 2006-02-23 17:10 UTC (permalink / raw)
To: tnt, lijianggan, linuxppc-embedded
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+IEZyb206IFN5bHZhaW4gTXVuYXV0IFttYWls
dG86dG50QDI0NnROdC5jb21dCj4gU2VudDogVGh1IDIvMjMvMjAwNiAxNTozOAo+IFRvOiAjTEkg
SklBTkdHQU4jCj4gQ2M6IGxpbnV4cHBjLWVtYmVkZGVkQG96bGFicy5vcmcKPiBTdWJqZWN0OiBS
ZTogYm9vdCBmYWlsdXJlIG9uIGxpdGU1MjAwYiBib2FyZAo+Cj4gI0xJIEpJQU5HR0FOIyB3cm90
ZToKPiA+IEhlbGxvIGFsbCwKPiA+Cj4gPiBGb3IgbXkgZW5kLW9mLXN0dWR5IHByb2plY3QsIEkg
YW0gd29ya2luZyBvbiBhbiBlbWJlZGRlZCBzeXN0ZW0gd2l0aAo+ID4gcmVmZXJlbmNlIG9mIGZy
ZWVzY2FsZSdzIGxpdGU1MjAwYiByZWZlcmVuY2UgYm9hcmQuIEkgd2FzIHRyeWluZyB0byBib290
Cj4gPiBMaW51eCAyLjYuMTUgb24gdGhlIGJvYXJkICh3aXRoIHRoZSBmZWMgYW5kIGJlc3Rjb21t
IGNvcnJlY3RlZCkuIGhvd2V2ZXIKPiA+IHRoZSBib290aW5nIHdhcyBzdHVjayBhdCB0aGUgZm9s
bG93aW5nIHN0YWdlOgo+Cj4gSW4gYWRkaXRpb24gdG8gd2hhdCBoYXMgYWxyZWFkeSBiZWVuIHNh
aWQgKHVzZSBhIGhpZ2hlciBhZGRyZXNzIGZvciB0aGUKPiBpbWFnZSBhbmQgZG9uJ3QgZm9yZ2V0
IGNvbnNvbGU9dHR5UFNDMCBpbiBrZXJuZWwgY29tbWFuZCBsaW5lKSwgbWFrZQo+IHN1cmUgeW91
IHVzZSB0aGUga2VybmVsIGZyb20gbXkgZ2l0IHRyZWUsIGl0IGNvbnRhaW5zIGEgZmV3IHBhdGNo
ZXMgZnJvbQo+IEpvaG4gUmlnYnkgdG8gYWRkIHN1cHBvcnQgZm9yIHRoZSBsaXRlNTIwMGIuCj4K
PiBQbGVhc2UgcmVwb3J0IGlmIGl0IHdvcmtzLCBJJ3ZlIG5vdCBiZWVuIGFibGUgdG8gdGVzdCB0
aG9zZSBteXNlbGYgc2luY2UKPiBpJ20gc3RpbGwgb24gbGl0ZTUyMDAuCj4KPgo+IAlTeWx2YWlu
CgoKClRoZSBwcm9ibGVtIG1pZ2h0IGJlIGluIHRoZSBVLUJvb3QgZW52aXJvbm1lbnQgdmFyaWFi
bGVzClNlZSBtaW5lIGJlbG93LgoKTk9URToKdGhhdCB0aGUgYm9vdF9jbWQgZXhlY3V0ZXMgdGhl
IGNvbW1hbmQgcnVuIG5ldF9uZnMgYW5kCnRoYXQgdGhlIG5ldF9uZnMgdGZ0cCdzIHRoZSBrZXJu
ZWwsIHRoZW4gZXhlY3V0cyB0aGUgcnVuIHNldGNvbnNvbGUKbmZzYXJncyBhZGRpcCBiZWZvcmUg
aXQgYm9vdHMgdGhlIGtlcm5lbAoKSG9wZSB0aGF0IGhlbHBzCgpNYXJ0aW4KCgoKClUtQm9vdCAx
LjEuNCAoRmViIDIyIDIwMDYgLSAxNDo0MjowNSkKCkNQVTogICBNUEM1MjAwIHYyLjIgYXQgNDYy
IE1IegogICAgICAgQnVzIDEzMiBNSHosIElQQiAxMzIgTUh6LCBQQ0kgMzMgTUh6CkJvYXJkOiBG
cmVlc2NhbGUgTVBDNTIwMCAoTGl0ZTUyMDBCKQpJMkM6ICAgODUga0h6LCByZWFkeQpEUkFNOiAg
MjU2IE1CCkZMQVNIOiAzMiBNQgpQQ0k6ICAgQnVzIERldiBWZW5JZCBEZXZJZCBDbGFzcyBJbnQK
ICAgICAgICAwMCAgMWEgIDEwNTcgIDU4MDkgIDA2ODAgIDAwCkluOiAgICBzZXJpYWwKT3V0OiAg
IHNlcmlhbApFcnI6ICAgc2VyaWFsCk5ldDogICBGRUMgRVRIRVJORVQKSURFOiAgIEJ1cyAwOiBP
SwogIERldmljZSAwOiBub3QgYXZhaWxhYmxlCiAgRGV2aWNlIDE6IG5vdCBhdmFpbGFibGUKClR5
cGUgInJ1biBmbGFzaF9uZnMiIHRvIG1vdW50IHJvb3QgZmlsZXN5c3RlbSBvdmVyIE5GUwoKSGl0
IGFueSBrZXkgdG8gc3RvcCBhdXRvYm9vdDogIDAKPT4gcHJpbnRlbnYKYm9vdGNtZD1ydW4gbmV0
X25mcwpib290ZGVsYXk9NQpiYXVkcmF0ZT0xMTUyMDAKcHJlYm9vdD1lY2hvO2VjaG8gVHlwZSAi
cnVuIGZsYXNoX25mcyIgdG8gbW91bnQgcm9vdCBmaWxlc3lzdGVtIG92ZXIgTkZTO2VjaG8KYmF1
ZHJhdGU9MTE1MjAwCm5ldGRldj1ldGgwCmFkZGlwPXNldGVudiBib290YXJncyAkKGJvb3Rhcmdz
KQppcD0kKGlwYWRkcik6JChzZXJ2ZXJpcCk6JChnYXRld2F5aXApOiQobmV0bWFzayk6JChob3N0
bmFtZSk6JChuZXRkZXYpOm9mZgpwYW5pNWV0aGFjdD1GRUMgRVRIRVJORVQKc2VydmVyaXA9MTky
LjE2OC4xMDAuMzMKZ2F0ZXdheWlwPTE5Mi4xNjguMTAwLjEKbmV0bWFzaz0yNTUuMjU1LjI1NS4w
CnJvb3RwYXRoPS9vcHQvZWxkay9wcGNfNnh4CmlwYWRkcj0xOTIuMTY4LjEwMC4yOQpyYW1hcmdz
PXNldGVudiBib290YXJncyByb290PS9kZXYvcmFtIHJ3Cm5ldF9uZnM9dGZ0cCAyMDAwMDAgJChi
b290ZmlsZSk7cnVuIHNldGNvbnNvbGUgbmZzYXJncyBhZGRpcDtib290bQpzZXRjb25zb2xlPXNl
dGVudiBib290YXJncyAkKGNvbnNvbGUpCm5mc2FyZ3M9c2V0ZW52IGJvb3RhcmdzICQoYm9vdGFy
Z3MpIHJvb3Q9L2Rldi9uZnMgcncKbmZzcm9vdD0kKHNlcnZlcmlwKTokKHJvb3QpYm9vdGZpbGU9
TVBDNTIwMC91SW1hZ2UKaG9zdG5hbWU9d2VlZHdoYWNrZXIKYm9vdGRlbGF5PTUKY29uc29sZT1j
b25zb2xlPXR0eVBTQzAsMTE1MjAwbjggY29uc29sZT10dHkxCmZsYXNoX25mcz1ydW4gc2V0Y29u
c29sZSBuZnNhcmdzIGFkZGlwO2Jvb3RtCmF1dG9sb2FkPW5vCmV0aGFkZHI9MDA6MDQ6OWY6MDA6
Mjc6MzUKc3RkaW49c2VyaWFsCnN0ZG91dD1zZXJpYWwKc3RkZXJyPXNlcmlhbAoKRW52aXJvbm1l
bnQgc2l6ZTogODY4LzY1NTMyIGJ5dGVzCj0+IGJvb3QKVXNpbmcgRkVDIEVUSEVSTkVUIGRldmlj
ZQpURlRQIGZyb20gc2VydmVyIDE5Mi4xNjguMTAwLjMzOyBvdXIgSVAgYWRkcmVzcyBpcyAxOTIu
MTY4LjEwMC4yOQpGaWxlbmFtZSAnTVBDNTIwMC91SW1hZ2UnLgpMb2FkIGFkZHJlc3M6IDB4MjAw
MDAwCkxvYWRpbmc6ICMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjCiAgICAgICAgICMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCiAgICAgICAgICMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIwpk
b25lCkJ5dGVzIHRyYW5zZmVycmVkID0gOTg2NDcyIChmMGQ2OCBoZXgpCiMjIEJvb3RpbmcgaW1h
Z2UgYXQgMDAyMDAwMDAgLi4uCiAgIEltYWdlIE5hbWU6ICAgTGludXgtMi42LjE2LXJjMS1nYWY0
Zjc1ZmQtZGlydHkKICAgSW1hZ2UgVHlwZTogICBQb3dlclBDIExpbnV4IEtlcm5lbCBJbWFnZSAo
Z3ppcCBjb21wcmVzc2VkKQogICBEYXRhIFNpemU6ICAgIDk4NjQwOCBCeXRlcyA9IDk2My4zIGtC
CiAgIExvYWQgQWRkcmVzczogMDAwMDAwMDAKICAgRW50cnkgUG9pbnQ6ICAwMDAwMDAwMAogICBW
ZXJpZnlpbmcgQ2hlY2tzdW0gLi4uIE9LCiAgIFVuY29tcHJlc3NpbmcgS2VybmVsIEltYWdlIC4u
LiBPSwppZCBtYWNoKCk6IGRvbmUKTU1VOmVudGVyCk1NVTpodyBpbml0Ck1NVTptYXBpbgpNTVU6
c2V0aW8KTU1VOmV4aXQKc2V0dXBfYXJjaDogZW50ZXIKc2V0dXBfYXJjaDogYm9vdG1lbQphcmNo
OiBleGl0CkxpbnV4IHZlcnNpb24gMi42LjE2LXJjMS1nYWY0Zjc1ZmQtZGlydHkgKHdlZGVwb2hs
QHVidW50dSkgKGdjYwp2ZXJzaW9uIDQuMC4wICg2QnVpbHQgMSB6b25lbGlzdHMKS2VybmVsIGNv
bW1hbmQgbGluZTogY29uc29sZT10dHlQU0MwLDExNTIwMG44IGNvbnNvbGU9dHR5MQpyb290PS9k
ZXYvbmZzIHJ3IG5mc3hQSUQgaGFzaCB0YWJsZSBlbnRyaWVzOiAyMDQ4IChvcmRlcjogMTEsIDMy
NzY4CmJ5dGVzKQpDb25zb2xlOiBjb2xvdXIgZHVtbXkgZGV2aWNlIDgweDI1CkRlbnRyeSBjYWNo
ZSBoYXNoIHRhYmxlIGVudHJpZXM6IDY1NTM2IChvcmRlcjogNiwgMjYyMTQ0IGJ5dGVzKQpJbm9k
ZS1jYWNoZSBoYXNoIHRhYmxlIGVudHJpZXM6IDMyNzY4IChvcmRlcjogNSwgMTMxMDcyIGJ5dGVz
KQpNZW1vcnk6IDI1NzUzNmsgYXZhaWxhYmxlICgxNTA0ayBrZXJuZWwgY29kZSwgNDk2ayBkYXRh
LCA5NmsgaW5pdCwgMGsgaGlnaG1lbSkKTW91bnQtY2FjaGUgaGFzaCB0YWJsZSBlbnRyaWVzOiA1
MTIKTkVUOiBSZWdpc3RlcmVkIHByb3RvY29sIGZhbWlseSAxNgoKUENJOiBQcm9iaW5nIFBDSSBo
YXJkd2FyZQppbyBzY2hlZHVsZXIgbm9vcCByZWdpc3RlcmVkCmlvIHNjaGVkdWxlciBhbnRpY2lw
YXRvcnkgcmVnaXN0ZXJlZCAoZGVmYXVsdCkKaW8gc2NoZWR1bGVyIGRlYWRsaW5lIHJlZ2lzdGVy
ZWQKaW8gc2NoZWR1bGVyIGNmcSByZWdpc3RlcmVkClNlcmlhbDogTVBDNTJ4eCBQU0MgZHJpdmVy
CnR0eVBTQzAgYXQgTU1JTyAweGYwMDAyMDAwIChpcnEgPSA0MCkgaXMgYSBNUEM1Mnh4IFBTQwpS
QU1ESVNLIGRyaXZlciBpbml0aWFsaXplZDogMTYgUkFNIGRpc2tzIG9mIDQwOTZLIHNpemUgMTAy
NCBibG9ja3NpemUKbWljZTogUFMvMiBtb3VzZSBkZXZpY2UgY29tbW9uIGZvciBhbGwgbWljZQpO
RVQ6IFJlZ2lzdGVyZWQgcHJvdG9jb2wgZmFtaWx5IDIK
^ permalink raw reply
* Re: yaboot 1.3.14 release candidate 1
From: David Woodhouse @ 2006-02-23 17:21 UTC (permalink / raw)
To: Paul Nasrat; +Cc: linuxppc-dev list
In-Reply-To: <1139538538.3638.14.camel@enki.eridu>
On Thu, 2006-02-09 at 21:28 -0500, Paul Nasrat wrote:
> Amiga partition support (Sven Luther),
Does this still have an off-by-one bug in the partition numbering which
coincidentally matches a similar bug in the Pegasos OpenFirmware? If so,
we should fix it before any proper release.
--
dwmw2
^ permalink raw reply
* Re: yaboot 1.3.14 release candidate 1
From: David Woodhouse @ 2006-02-23 17:22 UTC (permalink / raw)
To: Paul Nasrat; +Cc: linuxppc-dev list
In-Reply-To: <1140021795.2824.12.camel@enki.eridu>
On Wed, 2006-02-15 at 11:43 -0500, Paul Nasrat wrote:
> No, thanks for passing this on to me it looks sane, I'll test a little
> then probably commit. Currently I've been doing this on macs with an
> ofboot script checking 64-bit, but this is probably better.
... and will work on CHRP for 32 vs. 64, which we can't do in
bootinfo.txt because of problems with the IBM firmware.
--
dwmw2
^ permalink raw reply
* RE: Gianfar is slower than fcc_enet on MPC8541 ???
From: Laurent Lagrange @ 2006-02-23 17:28 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <000701c6389b$49e30960$5201a8c0@GEG2400>
Hi everybody,
Sorry to reply so late. I was out of office.
I tried the below Andy's idea. It works fine.
It is my TCP clients which now slow the traffic.
But I don't know why the default timeouts are so high.
If the traffic is high, the timeout does not fire.
If the traffic is low, the timeout seems too long (???).
Thanks all for your ideas and works.
Best regards
Laurent
> De la part de Andy Fleming
> Envoye : mar. 14 fevrier 2006 18:37
> A : Laurent Lagrange
> Cc : linuxppc-embedded@ozlabs.org
> Objet : Re: Gianfar is slower than fcc_enet on MPC8541 ???
>
> My guess is that you are measuring latency. By default, interrupt
> coalescing is on, and used to be set to very poor default
> values. In drivers/net/gianfar.h, change the defaults to look like this:
>
> #define DEFAULT_TX_COALESCE 1
> #define DEFAULT_TXCOUNT 16
> #define DEFAULT_TXTIME 4
>
> #define DEFAULT_RX_COALESCE 1
> #define DEFAULT_RXCOUNT 16
> #define DEFAULT_RXTIME 4
>
> The problem was that the timeout was quite long, so a small number of
> packets would have to wait a whole millisecond (or more!) to get
> processed. While it wouldn't affect bandwidth tests, which send many
> packets, it would affect a simple test like ping.
>
> If you don't feel like recompiling the kernel, you can use ethtool to
> change the timeout values.
^ permalink raw reply
* Re: Gianfar is slower than fcc_enet on MPC8541 ???
From: Andy Fleming @ 2006-02-23 20:08 UTC (permalink / raw)
To: Laurent Lagrange; +Cc: linuxppc-embedded
In-Reply-To: <000001c6389e$980f0ff0$5201a8c0@GEG2400>
On Feb 23, 2006, at 11:28, Laurent Lagrange wrote:
> Hi everybody,
>
> I tried the below Andy's idea. It works fine.
> It is my TCP clients which now slow the traffic.
>
> But I don't know why the default timeouts are so high.
> If the traffic is high, the timeout does not fire.
> If the traffic is low, the timeout seems too long (???).
The answer there is simple: stupidity! :) I just didn't carefully
test the values for performance when I chose them. I probably also
did the math wrong, because I was more concerned about seeing if it
worked at all. It's also possible it got set that way to see a
measurable difference to prove it was working, and then got left as
the default. Rest assured, there was not a deliberate reason. We
submitted a patch once this performance issue was discovered.
^ permalink raw reply
* Fix for CFI Flash Driver bug in 2.4 Kernel
From: Matsen, Dean (WA26) @ 2006-02-23 21:33 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 4070 bytes --]
All,
This patch applies to 2.4.22 from Monta Vista. We started seeing a
kernel panic due to the really SLOOOOW 29LV641MH-120 flash parts.
Interestingly, the same part with 90mS access time (29LV641MH-120) are
about 10 times faster erasing and programming.
Turns out there are two problems in the driver code:
1- the timeout is calculated incorrectly, based on HZ/100, which is zero
on my system 'cuz "HZ" is equal to 100
2- when the timeout occurs, the code erroneously releases a spinlock
twice.
I have not checked to see if there is a similar problem in the 2.6
kernel
Regards,
Dean Matsen
Software Architect
Alerton Honeywell
dean.matsen@honeywell.com
Patch follows:
------------------------------------------------------------------------
----------------------
diff --unified --recursive
ppc-linux-kernel.org/drivers/mtd/chips/cfi_cmdset_0002.c
ppc-linux-kernel/drivers/mtd/chips/cfi_cmdset_0002.c
--- ppc-linux-kernel.org/drivers/mtd/chips/cfi_cmdset_0002.c Sat
Jul 12 01:08:17 2003
+++ ppc-linux-kernel/drivers/mtd/chips/cfi_cmdset_0002.c Thu Feb 23
12:50:34 2006
@@ -10,6 +10,15 @@
*
* $Id: cfi_cmdset_0002.c,v 1.1.1.1 2003/07/12 08:08:17 dean Exp $
*
+ * - 2006/02/23 : Dean Matsen (dean.matsen@honeywell.com) Fixed write
+ * timeout bug: timeout was based on HZ/1000 before (which is equal
to
+ * zero in my system), also the exit path unlocked the spinlock
twice.
+ * Increased timeout from 1mS to 100mS, because new 100K write
flashes
+ * such as 29LV641MH say "TBD" in the data sheet for worst case
programming
+ * time. Problem was detected due to the really slow 29LV641MH-120
part,
+ * which erases and programs 10 times slower than any other flash
we've
+ * ever encountered (including the 29LV641MH-90, which is in the same
+ * 100K write family of parts!).
*/
#include <linux/module.h>
@@ -511,7 +520,7 @@
or tells us why it failed. */
dq6 = CMD(1<<6);
dq5 = CMD(1<<5);
- timeo = jiffies + (HZ/1000); /* setting timeout to 1ms for now */
+ timeo = jiffies + (HZ/10); /* setting timeout to 100ms for now */
oldstatus = cfi_read(map, adr);
status = cfi_read(map, adr);
@@ -532,10 +541,10 @@
}
if( (status & dq6) != (oldstatus & dq6) ) {
- /* The erasing didn't stop?? */
+ /* The writing didn't stop?? */
if( (status & dq5) == dq5 ) {
/* When DQ5 raises, we must check once again
- if DQ6 is toggling. If not, the erase has been
+ if DQ6 is toggling. If not, the write has been
completed OK. If not, reset chip. */
oldstatus = cfi_read(map, adr);
status = cfi_read(map, adr);
@@ -543,7 +552,7 @@
if ( (oldstatus & 0x00FF) == (status & 0x00FF) ) {
printk(KERN_WARNING "Warning: DQ5 raised while
program operation was in progress, however operation completed OK\n" );
} else {
- /* DQ5 is active so we can do a reset and stop
the erase */
+ /* DQ5 is active so we can do a reset and stop
the write */
cfi_write(map, CMD(0xF0), chip->start);
printk(KERN_WARNING "Internal flash device
timeout occurred or write operation was performed while flash was
programming.\n" );
}
@@ -554,7 +563,7 @@
wake_up(&chip->wq);
cfi_spin_unlock(chip->mutex);
DISABLE_VPP(map);
- ret = -EIO;
+ return -EIO;
}
}
------------------------------------------------------------------------
-----------------------------------
[-- Attachment #2: Type: text/html, Size: 18299 bytes --]
^ permalink raw reply
* Looping SPIMISO and SPIMOSI pins
From: dibacco @ 2006-02-23 21:54 UTC (permalink / raw)
To: linuxppc-embedded
What could happen if I loop SPIMISO and SPIMOSI on my board expansion con=
nector? I think I should receive the messages I send on the SPI bus. SPI =
is
full duplex?
Best regards,
Antonio.
^ permalink raw reply
* Re: PowerPC: Sleeping function called from invalid context at emulate_instruction()
From: Paul Mackerras @ 2006-02-23 22:57 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev list, Linux Kernel, Michael Buesch
In-Reply-To: <7A04DCF5-C5CF-46E2-A133-A7743BD83B17@kernel.crashing.org>
Kumar Gala writes:
> Last time this was brought up we left it wondering why you had made
> program_check_exception() run with interrupts disabled. Any further
> ideas on that one?
I think it was so that if we are entering the kernel debugger, we do
so on the same cpu that the exception was generated on. This should
fix it.
Paul.
diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
index 7509aa6..98660ae 100644
--- a/arch/powerpc/kernel/traps.c
+++ b/arch/powerpc/kernel/traps.c
@@ -814,6 +814,8 @@ void __kprobes program_check_exception(s
return;
}
+ local_irq_enable();
+
/* Try to emulate it if we should. */
if (reason & (REASON_ILLEGAL | REASON_PRIVILEGED)) {
switch (emulate_instruction(regs)) {
^ permalink raw reply related
* parsing of some early cmdline options
From: Kumar Gala @ 2006-02-23 23:02 UTC (permalink / raw)
To: Benjamin Herrenschmidt, Paul Mackerras; +Cc: linuxppc-dev
Guys,
I noticed that we have code in arch/powerpc/kernel/prom_init.c to handle
parsing iommu=, mem=, and crashkernel=.
The problem I have is that we only use/build prom_init.c on MULTIPLATFORM
(coming from true OF).
Any ideas on how to handle this for the !MULTIPLATFORM cases. I'm most
concerned about mem=.
- kumar
^ permalink raw reply
* Re: [PATCH] change compat shmget size arg to signed
From: Stephen Rothwell @ 2006-02-23 23:16 UTC (permalink / raw)
To: Olaf Herring; +Cc: ppc64-dev, ppc-dev
Hi Olaf,
> change second arg (the 'size') to signed to handle a size of -1.
> ltp test shmget02 fails. This patch fixes it.
> Oddly, we see the failure only on a POWER4 LPAR with 4.6G ram.
>
> Signed-off-by: Olaf Hering <olh at suse.de>
>
> arch/powerpc/kernel/sys_ppc32.c | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6.16-rc4-olh/arch/powerpc/kernel/sys_ppc32.c
> ===================================================================
> --- linux-2.6.16-rc4-olh.orig/arch/powerpc/kernel/sys_ppc32.c
> +++ linux-2.6.16-rc4-olh/arch/powerpc/kernel/sys_ppc32.c
> @@ -429,7 +429,7 @@ long compat_sys_ipc(u32 call, u32 first,
> return sys_shmdt(compat_ptr(ptr));
> case SHMGET:
> /* sign extend key_t */
> - return sys_shmget((int)first, second, third);
> + return sys_shmget((int)first, (int)second, third);
> case SHMCTL:
> /* sign extend shmid */
> return compat_sys_shmctl((int)first, second, compat_ptr(ptr));
Does the ltp test fail on a standard kernel(where SHMMAX is 0x2000000), or
only on a SLES kernel (where SHMMAX is ULONG_MAX)?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
^ permalink raw reply
* Re: parsing of some early cmdline options
From: Benjamin Herrenschmidt @ 2006-02-23 23:19 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.44.0602231658210.16092-100000@gate.crashing.org>
On Thu, 2006-02-23 at 17:02 -0600, Kumar Gala wrote:
> Guys,
>
> I noticed that we have code in arch/powerpc/kernel/prom_init.c to handle
> parsing iommu=, mem=, and crashkernel=.
>
> The problem I have is that we only use/build prom_init.c on MULTIPLATFORM
> (coming from true OF).
MULTIPLATFORM is here to die (or rather be always there, with
ARCH=powerpc we really want to NOT reproduce the old single platform
crap) , but yes, prom_init.c is supposed to only be run on real OFs...
I suppose we woul have to deal with those in early_init_devtree() for
machines that didn't go through prom_init()....
> Any ideas on how to handle this for the !MULTIPLATFORM cases. I'm most
> concerned about mem=.
^ permalink raw reply
* ibook1 hangs during boot, atyfb broken
From: Olaf Hering @ 2006-02-23 23:24 UTC (permalink / raw)
To: linuxppc-dev
My iBook1 did not work with recent kernels (2.6.15+), 2.6.13 was always ok.
Today I did some more testing, with 2.6.16-rc4-git3.
If I boot with 'quiet panic=1 root=/dev/blah', it will hang in 75% of the boots
before displaying the penguin.
Adding video=atyfb:off did fix it, tried it a few times. Then I removed
the quiet and video= option, and it did boot again. Then I reverted the
atyfb to 2.6.15 status and did a reboot loop.
Unfortunately, after 13 reboots with just 'panic=1 root=/x' it was stuck, after
time_init: processor frequency = 300MHz.
"panic=1 root=/dev/blah video=atyfb:off" works better, 27 reboots and
still going.
^ permalink raw reply
* Re: [PATCH] change compat shmget size arg to signed
From: Olaf Hering @ 2006-02-23 23:27 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: ppc64-dev, ppc-dev
In-Reply-To: <20060224101644.548b0c24.sfr@canb.auug.org.au>
On Fri, Feb 24, Stephen Rothwell wrote:
> Does the ltp test fail on a standard kernel(where SHMMAX is 0x2000000), or
> only on a SLES kernel (where SHMMAX is ULONG_MAX)?
It fails with SLES9 and SLES10. SLES9 has 0x2000000 as default.
^ permalink raw reply
* Re: parsing of some early cmdline options
From: Michael Ellerman @ 2006-02-23 23:40 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <1140736753.8264.55.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Fri, 24 Feb 2006 10:19, Benjamin Herrenschmidt wrote:
> On Thu, 2006-02-23 at 17:02 -0600, Kumar Gala wrote:
> > Guys,
> >
> > I noticed that we have code in arch/powerpc/kernel/prom_init.c to handle
> > parsing iommu=, mem=, and crashkernel=.
> >
> > The problem I have is that we only use/build prom_init.c on MULTIPLATFORM
> > (coming from true OF).
> > Any ideas on how to handle this for the !MULTIPLATFORM cases. I'm most
> > concerned about mem=.
mem= is a bit tricky because you need to know about it really early, otherwise
your bootloader might violate the limit. But we could certainly check for it
again in prom.c. And you can always just set /chosen/linux,memory-limit.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [PATCH] ppc32: handle Book E debug exceptions on kernel stack
From: David Gibson @ 2006-02-23 23:49 UTC (permalink / raw)
To: Kumar Gala; +Cc: Paul Mackerras, linuxppc-embedded
In-Reply-To: <Pine.LNX.4.44.0602222217220.28948-100000@gate.crashing.org>
On Wed, Feb 22, 2006 at 10:19:54PM -0600, Kumar Gala wrote:
> On Tue, 14 Feb 2006, Dale Farnsworth wrote:
>
> > From: Dale Farnsworth <dale@farnsworth.org>
> >
> > On PPC Book E processsors, we currently handle debug
> > exceptions on the critical exception stack (debug stack
> > for E200). This causes problems with the kgdb single
> > step handler, which calls smp_processor_id() and spin_lock(),
> > which reference current_thread_info(), which only works when
> > we are on the kernel stack.
> >
> > We address this by switching to the kernel stack early while
> > handling debug exceptions. Note that the entry values of r10
> > and r11 are still saved on the critical exception (or debug) stack.
> >
> > Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
> >
>
> Paul,
>
> We were wondering if you or David remember why a specific critical
> exception stack was added in the 40x port from 2.4 to 2.6?
I don't, in any detail. But did it have to do with a possible race
with a critical exception in just the wrong part of the normal
exception exit path. ISTR BenH was worried about something in that
area.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
^ permalink raw reply
* Re: [PATCH] change compat shmget size arg to signed
From: Stephen Rothwell @ 2006-02-24 0:12 UTC (permalink / raw)
To: Olaf Hering; +Cc: linuxppc64-dev, linuxppc-dev
In-Reply-To: <20060223232717.GB29454@suse.de>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Fri, 24 Feb 2006 00:27:17 +0100 Olaf Hering <olh@suse.de> wrote:
>
> On Fri, Feb 24, Stephen Rothwell wrote:
>
> > Does the ltp test fail on a standard kernel(where SHMMAX is 0x2000000), or
> > only on a SLES kernel (where SHMMAX is ULONG_MAX)?
>
> It fails with SLES9 and SLES10. SLES9 has 0x2000000 as default.
So what was shm_ctlmax set to when the test was run.
I am trying to figure out why this test:
if (size < SHMMIN || size > shm_ctlmax)
return -EINVAL;
Doesn't return -EINVAL for size == 0xffffffff if shm_ctlmax is 0x2000000?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: please pull powerpc-merge.git
From: Paul Mackerras @ 2006-02-24 0:19 UTC (permalink / raw)
To: torvalds; +Cc: linuxppc-dev
In-Reply-To: <17405.42237.285728.981952@cargo.ozlabs.ibm.com>
Linus,
Please hold off from pulling powerpc-merge.git for now, if you haven't
already done the pull. Stephen Rothwell has just convinced me that a
1-line change from Olaf Hering is in fact wrong, so I'll pull that
change out. If you have pulled I'll just do a reverting commit. (The
commit in question is 847db200a647058f6af883da3474b867617b7273.)
Paul.
^ permalink raw reply
* please pull powerpc-merge.git
From: Paul Mackerras @ 2006-02-24 2:36 UTC (permalink / raw)
To: torvalds; +Cc: linuxppc-dev
Linus,
I have pulled out the problematic commit, so please do a pull from
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc-merge.git
There are 14 commits there: fixes for various bugs and a performance
regression, plus a defconfig update.
Thanks,
Paul.
Alan Curry:
powerpc: fix altivec_unavailable_exception Oopses
Anton Blanchard:
powerpc: Fix runlatch performance issues
powerpc64: remove broken/bitrotted HMT support
Haren Myneni:
powerpc: Trivial fix to set the proper timeout value for kdump
Kelly Daly:
powerpc: disable OProfile for iSeries
Kumar Gala:
powerpc: Enable coherency for all pages on 83xx to fix PCI data corruption
Michael Ellerman:
powerpc: Initialise hvlpevent_queue.lock correctly
powerpc: Only calculate htab_size in one place for kexec
Michal Ostrowski:
Fix race condition in hvc console.
Olaf Hering:
ppc: fix adb breakage in xmon
Olof Johansson:
powerpc: Update {g5,pseries,ppc64}_defconfig
R Sharada:
powerpc64: fix spinlock recursion in native_hpte_clear
Segher Boessenkool:
powerpc: Fix some MPIC + HT APIC buglets
powerpc: Don't re-assign PCI resources on Maple
arch/powerpc/configs/g5_defconfig | 174 ++++++++++--------------
arch/powerpc/configs/ppc64_defconfig | 173 ++++++++++--------------
arch/powerpc/configs/pseries_defconfig | 127 ++++++-----------
arch/powerpc/kernel/crash.c | 4 -
arch/powerpc/kernel/head_32.S | 1
arch/powerpc/kernel/head_64.S | 109 +--------------
arch/powerpc/kernel/machine_kexec_64.c | 10 -
arch/powerpc/kernel/process.c | 32 ++++
arch/powerpc/kernel/prom_init.c | 38 -----
arch/powerpc/mm/hash_native_64.c | 7 +
arch/powerpc/mm/hash_utils_64.c | 3
arch/powerpc/oprofile/Kconfig | 1
arch/powerpc/platforms/iseries/lpevents.c | 2
arch/powerpc/platforms/iseries/setup.c | 1
arch/powerpc/platforms/maple/pci.c | 4 -
arch/powerpc/platforms/pseries/Kconfig | 7 -
arch/powerpc/sysdev/mpic.c | 9 +
arch/ppc/kernel/head.S | 1
arch/ppc/xmon/adb.c | 212 -----------------------------
arch/ppc/xmon/start.c | 169 -----------------------
arch/ppc/xmon/xmon.c | 108 ---------------
drivers/char/hvc_console.c | 8 +
include/asm-powerpc/cputable.h | 9 +
include/asm-powerpc/mmu.h | 1
include/asm-powerpc/reg.h | 33 -----
include/asm-powerpc/thread_info.h | 4 -
26 files changed, 274 insertions(+), 973 deletions(-)
delete mode 100644 arch/ppc/xmon/adb.c
^ permalink raw reply
* RE: boot failure on lite5200b board
From: #LI JIANGGAN# @ 2006-02-24 3:31 UTC (permalink / raw)
To: John Rigby; +Cc: linuxppc-embedded
In-Reply-To: <4b73d43f0602230818w63423513n817d9ec7eb580d2c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 8800 bytes --]
I have actually tried both kernel with both console configurations. It gave the same output, thus I presume that the problem lies somewhere else. I attached the log to this email.
the board is Lite5200B Version 1.0. Which .config file do you want?
Sylvain, we have ordered a debugging set but we are still waiting for delivery, the leaking time is said to be one month, tant pis. And the log I attached here are booting from a higher address (0x500000).
My current u-boot args:
Autostarting. Press any key to abort..
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
autoload=no
ethact=FEC ETHERNET
flshroot=root=/dev/mtdblock2 rw
ethaddr=00:01:9F:00:27:2F
preboot=echo; echo Autostarting. Press any key to abort..; echo
bootdelay=5
hostname=icecube
bootfile=MPC5200/uImage
nv=nfsroot root=/dev/nfs rw nfsroot=10.190.3.113:/opt/eldk/rootfs
ip=ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
nfsroot=root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
bootcmd=run net_nfs
filesize=546
fileaddr=500000
netmask=255.255.240.0
ipaddr=10.190.3.144
serverip=10.190.3.103
setconsole=setenv bootargs console=ttyPSC0, 115200n8 console=tty1
rootfs=root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
bootargs=env bootargs root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
flash_nfs=run setconsole nfsargs addip;bootm
net_nfs=tftp 500000 MPC5200/uImage;run setconsole nfsargs addip;bootm
nfsargs=setenv bootargs env bootargs root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::offroot=/dev/nfs rw
addip=setenv bootargs env bootargs root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
ramargs=setenv bootargs root=/dev/ram rw
console=console=ttyS0,115200n8 console=tty1
stdin=serial
stdout=serial
stderr=serial
Environment size: 1472/65532 bytes
=>
USING Sylvain's KERNEL:
U-Boot 1.1.3 (Feb 6 2006 - 09:56:46)
CPU: MPC5200 v2.2 at 462 MHz
Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
Board: Freescale MPC5200 (Lite5200B)
I2C: 85 kHz, ready
DRAM: 256 MB
FLASH: 32 MB
PCI: Bus Dev VenId DevId Class Int
00 1a 1057 5809 0680 00
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
IDE: Bus 0: OK
Device 0: not available
Device 1: not available
Autostarting. Press any key to abort..
Hit any key to stop autoboot: 0
Using FEC ETHERNET device
TFTP from server 10.190.3.103; our IP address is 10.190.3.144
Filename 'MPC5200/uImage'.
Load address: 0x500000
Loading: #################################################################
################################################################
done
Bytes transferred = 658114 (a0ac2 hex)
## Booting image at 00500000 ...
Image Name: Linux-2.6.16-rc1
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 658050 Bytes = 642.6 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
arch: exit
USING KERNEL FROM Freescale:
U-Boot 1.1.3 (Feb 6 2006 - 09:56:46)
CPU: MPC5200 v2.2 at 462 MHz
Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
Board: Freescale MPC5200 (Lite5200B)
I2C: 85 kHz, ready
DRAM: 256 MB
FLASH: 32 MB
PCI: Bus Dev VenId DevId Class Int
00 1a 1057 5809 0680 00
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
IDE: Bus 0: OK
Device 0: not available
Device 1: not available
Autostarting. Press any key to abort..
Hit any key to stop autoboot: 0
Using FEC ETHERNET device
TFTP from server 10.190.3.103; our IP address is 10.190.3.144
Filename 'MPC5200/uImage'.
Load address: 0x500000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
###################################
done
Bytes transferred = 1510143 (170aff hex)
## Booting image at 00500000 ...
Image Name: Linux-2.6.11.7
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1510079 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
ocp: exit
arch: exit
-----Original Message-----
From: John Rigby [mailto:jcrigby@gmail.com]
Sent: Fri 2/24/2006 0:18
To: #LI JIANGGAN#
Subject: Re: boot failure on lite5200b board
If you are using Sylvain's kernel you need to set console=ttyPSC0. If you are
using a kernel from Freescale then you need to set console=ttyS0.
Also what rev of the board do you have?
On 2/23/06, #LI JIANGGAN# <lijianggan@pmail.ntu.edu.sg> wrote:
>
>
> Thank you José María and Andrey for your advices, however the problem
> remains. I've tried setting the console (though I remember that our previous
> lite5200 board was working fine on kernel 2.4 without setting the console);
> meantime, I've set the booting image to 0x500000; I have also tried using
> the kernel image come together with the BSP, it's always the same error.
>
> Sylvain, I've actually using your kernel source, the compiled image is
> around 700k (compared to the 1.4M image from the BSP), but it doesn't solve
> the problem. So I presume that the problem is lying somewhere else.
>
> A SNAPSHOT OF THE BOOTING MESSAGES:
>
>
> U-Boot 1.1.3 (Feb 6 2006 - 09:56:46)
>
> CPU: MPC5200 v2.2 at 462 MHz
> Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
> Board: Freescale MPC5200 (Lite5200B)
> I2C: 85 kHz, ready
> DRAM: 256 MB
> FLASH: 32 MB
> PCI: Bus Dev VenId DevId Class Int
> 00 1a 1057 5809 0680 00
> In: serial
> Out: serial
> Err: serial
> Net: FEC ETHERNET
> IDE: Bus 0: OK
> Device 0: not available
> Device 1: not available
>
> Autostarting. Press any key to abort..
>
> Hit any key to stop autoboot: 0
> Using FEC ETHERNET device
> TFTP from server 10.190.3.103; our IP address is 10.190.3.144
> Filename 'MPC5200/uImage'.
> Load address: 0x100000
> Loading:
> #################################################################
>
> ################################################################
> done
> Bytes transferred = 658114 (a0ac2 hex)
> ## Booting image at 00100000 ...
> Image Name: Linux-2.6.16-rc1
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 658050 Bytes = 642.6 kB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
> id mach(): done
> MMU:enter
> MMU:hw init
> MMU:mapin
> MMU:setio
> MMU:exit
> setup_arch: enter
> setup_arch: bootmem
> arch: exit
>
>
> I am wondering whether it's a kernel problem or more likely to be a problem
> lying with the U-boot. It seems to hang when executing setup_arch()
> function, or maybe there is sth else behind the wall?
>
> Regards,
> Jianggan LI
>
>
>
>
> -----Original Message-----
> From: Sylvain Munaut [mailto:tnt@246tNt.com]
> Sent: Thu 2/23/2006 15:38
> To: #LI JIANGGAN#
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: boot failure on lite5200b board
>
> #LI JIANGGAN# wrote:
> > Hello all,
> >
> > For my end-of-study project, I am working on an embedded system with
> > reference of freescale's lite5200b reference board. I was trying to boot
> > Linux 2.6.15 on the board (with the fec and bestcomm corrected). however
> > the booting was stuck at the following stage:
>
> In addition to what has already been said (use a higher address for the
> image and don't forget console=ttyPSC0 in kernel command line), make
> sure you use the kernel from my git tree, it contains a few patches from
> John Rigby to add support for the lite5200b.
>
> Please report if it works, I've not been able to test those myself since
> i'm still on lite5200.
>
>
> Sylvain
>
>
>
>
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
[-- Attachment #2: Type: text/html, Size: 12521 bytes --]
^ permalink raw reply
* Re: ibook1 hangs during boot, atyfb broken
From: Benjamin Herrenschmidt @ 2006-02-24 3:48 UTC (permalink / raw)
To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060223232423.GA29454@suse.de>
On Fri, 2006-02-24 at 00:24 +0100, Olaf Hering wrote:
> My iBook1 did not work with recent kernels (2.6.15+), 2.6.13 was always ok.
> Today I did some more testing, with 2.6.16-rc4-git3.
> If I boot with 'quiet panic=1 root=/dev/blah', it will hang in 75% of the boots
> before displaying the penguin.
> Adding video=atyfb:off did fix it, tried it a few times. Then I removed
> the quiet and video= option, and it did boot again. Then I reverted the
> atyfb to 2.6.15 status and did a reboot loop.
> Unfortunately, after 13 reboots with just 'panic=1 root=/x' it was stuck, after
> time_init: processor frequency = 300MHz.
It boots with video=atyfb:noaccel ?
I suggest you report that to the linux-fbdev mailing list. That problem
seems to happen with some wallstreet powerbooks too, there is definitely
something broken there...
Ben.
^ permalink raw reply
* UTOPIA support for MPC885 with 2.6.15 kernel
From: Pelton, Dave @ 2006-02-24 5:54 UTC (permalink / raw)
To: linuxppc-embedded
Hello,
I am currently working with a MPC885ADS board running a 2.6.15 kernel
build. I have been attempting to get the UTOPIA interface working, but
I have not been able to find kernel code (or patches) to do this. =20
The closest I have found so far is the MPC860/862 ATM driver on
SourceForge. Unfortunately this driver was written for the 2.4 kernel,
and does not include MPHY support for ESAR mode. I have been able to
get this code to compile and run on my kernel, and now I am digging into
the ESAR/MPHY support stuff. =20
I was wondering if anyone else has already done anything along these
lines (either a ESAR/MPHY driver or MPC855 UTOPIA support on the 2.6
kernel), as I would prefer to build on existing code rather than gluing
this stuff together myself.
- Thanks,
David Pelton.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox