* Linux on Force Computers CPCI-3750
@ 2003-03-29 14:55 luca gambazzi
2003-03-29 15:43 ` Tom Rini
0 siblings, 1 reply; 9+ messages in thread
From: luca gambazzi @ 2003-03-29 14:55 UTC (permalink / raw)
To: linuxppc-embedded
Hi
As suggested, i've tried to compile the penguingppc.org linux kernel for
my CPCI-3750.
I've got still 2 problems:
with the 2.4 tree (stable and devel) the make znetboot.initrd return an
error here:
powerpc-linux-gcc -D__KERNEL__ -I/usr/local/src/linux-2.4-rsync/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer
-I/usr/local/src/linux-2.4-rsync/arch/ppc -fsigned-char -msoft-float
-pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -nostdinc
-iwithprefix include -DKBUILD_BASENAME=cputable -c -o cputable.o
cputable.c
cputable.c:179: `CPU_FTR_HAS_HIGH_BATS' undeclared here (not in a
function)
[...]
in the 2.5 tree the compile works fine, but when boots i've got this
error:
[...]
RAMDISK: Compressed image found at block 0
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C00154D4 LR: C000C9D0 SP: C0ACBD50 REGS: c0acbca0 TRAP: 0301 Not
tainted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000000, DSISR: 42000000
TASK = c0acc060[1] 'swapper' Last syscall: 6
GPR00: 00001032 C0ACBD50 C0ACC060 C01B7C0C C0ACBD58 00000000 C0ACBD68
0000000A
GPR08: FFFFFFFF C0ACBD64 00000000 00009032 2010C048
Call trace: [c008c528] [c008c788] [c0079660] [c00fd258] [c0048bd8]
[c0048af0] [c004723c] [c0047300] [c00077d4] [c000a544] [c01cba04
Kernel panic: Attempted to kill init!
i'm not a CS student,... just an electronic student. so i don't
understand what to do to resolve this error. I've used a working ramdisk
image from timesys.com, so the error is in my kernel.
i've tryed to incrase the ramdisk dimension (the ramdisk i use is 8192)
but still the same problem
can anybody give me an advice?
here can you find a boot log http://lsa1pc32.epfl.ch/~gamba/boot.txt
thanks a lot
luca gambazzi
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750
2003-03-29 14:55 Linux on Force Computers CPCI-3750 luca gambazzi
@ 2003-03-29 15:43 ` Tom Rini
2003-04-04 11:49 ` Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
0 siblings, 1 reply; 9+ messages in thread
From: Tom Rini @ 2003-03-29 15:43 UTC (permalink / raw)
To: luca gambazzi; +Cc: linuxppc-embedded
On Sat, Mar 29, 2003 at 03:55:41PM +0100, luca gambazzi wrote:
>
> Hi
>
> As suggested, i've tried to compile the penguingppc.org linux kernel for
> my CPCI-3750.
>
> I've got still 2 problems:
>
> with the 2.4 tree (stable and devel) the make znetboot.initrd return an
> error here:
>
> powerpc-linux-gcc -D__KERNEL__ -I/usr/local/src/linux-2.4-rsync/include
> -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
> -fno-common -fomit-frame-pointer
> -I/usr/local/src/linux-2.4-rsync/arch/ppc -fsigned-char -msoft-float
> -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -nostdinc
> -iwithprefix include -DKBUILD_BASENAME=cputable -c -o cputable.o
> cputable.c
> cputable.c:179: `CPU_FTR_HAS_HIGH_BATS' undeclared here (not in a
> function)
> [...]
This was just recently fixed. Please update your tree.
> in the 2.5 tree the compile works fine, but when boots i've got this
> error:
>
> [...]
> RAMDISK: Compressed image found at block 0
> Oops: kernel access of bad area, sig: 11 [#1]
> NIP: C00154D4 LR: C000C9D0 SP: C0ACBD50 REGS: c0acbca0 TRAP: 0301 Not
> tainted
> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 00000000, DSISR: 42000000
> TASK = c0acc060[1] 'swapper' Last syscall: 6
> GPR00: 00001032 C0ACBD50 C0ACC060 C01B7C0C C0ACBD58 00000000 C0ACBD68
> 0000000A
> GPR08: FFFFFFFF C0ACBD64 00000000 00009032 2010C048
> Call trace: [c008c528] [c008c788] [c0079660] [c00fd258] [c0048bd8]
> [c0048af0] [c004723c] [c0047300] [c00077d4] [c000a544] [c01cba04
> Kernel panic: Attempted to kill init!
>
> i'm not a CS student,... just an electronic student. so i don't
> understand what to do to resolve this error. I've used a working ramdisk
> image from timesys.com, so the error is in my kernel.
>
> i've tryed to incrase the ramdisk dimension (the ramdisk i use is 8192)
> but still the same problem
>
> can anybody give me an advice?
> here can you find a boot log http://lsa1pc32.epfl.ch/~gamba/boot.txt
> thanks a lot
Can you please put the .config you used up? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-03-29 15:43 ` Tom Rini
@ 2003-04-04 11:49 ` luca gambazzi
2003-04-04 21:00 ` Tom Rini
2003-04-04 21:11 ` Matt Porter
0 siblings, 2 replies; 9+ messages in thread
From: luca gambazzi @ 2003-04-04 11:49 UTC (permalink / raw)
To: linuxppc-embedded
Hi
i'm still trying to bild a running linux kernel for a Force Computers
CPCI-3750.
I've got one more error, the ethernet card doesn't work.
is a Digital DS21143 Tulip
i've installed the kernel drivers (i've tried with 2.4 and 2.5
penguinppc kernel tree), and the drivers found in
http://sourceforge.net/projects/tulip, but the error is always the same.
NETDEV WATCHDOG: eth0: transmit timed out
here can you find a bootlog (kernelboot.txt), the tcpdump on my pc, and
the .config file I used in this case (config_2_5_66.txt)
http://lsa1pc32.epfl.ch/~gamba/robox/
Maybe somebody has experence with this kind of error and can help me.
Thanks a lot
Luca Gambazzi
PS Tom: I don't find the .config file who caused the crash I've posted
last week, i'll search in my pc, sorry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-04-04 11:49 ` Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
@ 2003-04-04 21:00 ` Tom Rini
2003-04-04 21:11 ` Matt Porter
1 sibling, 0 replies; 9+ messages in thread
From: Tom Rini @ 2003-04-04 21:00 UTC (permalink / raw)
To: luca gambazzi; +Cc: linuxppc-embedded
On Fri, Apr 04, 2003 at 01:49:13PM +0200, luca gambazzi wrote:
> Hi
>
> i'm still trying to bild a running linux kernel for a Force Computers
> CPCI-3750.
>
> I've got one more error, the ethernet card doesn't work.
> is a Digital DS21143 Tulip
>
> i've installed the kernel drivers (i've tried with 2.4 and 2.5
> penguinppc kernel tree), and the drivers found in
> http://sourceforge.net/projects/tulip, but the error is always the same.
>
> NETDEV WATCHDOG: eth0: transmit timed out
>
> here can you find a bootlog (kernelboot.txt), the tcpdump on my pc, and
> the .config file I used in this case (config_2_5_66.txt)
Don't use CONFIG_TULIP, use CONFIG_DE4X5 and poke the upstream authors
abotu this issue.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-04-04 11:49 ` Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
2003-04-04 21:00 ` Tom Rini
@ 2003-04-04 21:11 ` Matt Porter
1 sibling, 0 replies; 9+ messages in thread
From: Matt Porter @ 2003-04-04 21:11 UTC (permalink / raw)
To: luca gambazzi; +Cc: linuxppc-embedded
On Fri, Apr 04, 2003 at 01:49:13PM +0200, luca gambazzi wrote:
>
> Hi
>
> i'm still trying to bild a running linux kernel for a Force Computers
> CPCI-3750.
>
> I've got one more error, the ethernet card doesn't work.
> is a Digital DS21143 Tulip
>
> i've installed the kernel drivers (i've tried with 2.4 and 2.5
> penguinppc kernel tree), and the drivers found in
> http://sourceforge.net/projects/tulip, but the error is always the same.
>
> NETDEV WATCHDOG: eth0: transmit timed out
Assuming you are booting with the pcore kernel, are you sure that
the pci interrupt routing for the 3750 is identical to the 6750?
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
@ 2003-04-09 9:22 luca gambazzi
2003-04-09 15:02 ` Matt Porter
2003-04-09 15:22 ` Matt Porter
0 siblings, 2 replies; 9+ messages in thread
From: luca gambazzi @ 2003-04-09 9:22 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-embedded
Hi Matt
I'm booting with the pcore kernel.
the pcore_find_bridges function in pcore_pci.c recognize my card as a
6750, but the 3750 uses a 21150 bridge and not a 21154.
Do you know where can i find documentation to solve this problem?
and where I have to modify?
here you can find the bios log, maybe you can find an answer.
http://lsa1pc32.epfl.ch/~gamba/robox/
Thanks a lot
luca
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-04-09 9:22 luca gambazzi
@ 2003-04-09 15:02 ` Matt Porter
2003-04-09 15:22 ` Matt Porter
1 sibling, 0 replies; 9+ messages in thread
From: Matt Porter @ 2003-04-09 15:02 UTC (permalink / raw)
To: luca gambazzi; +Cc: Matt Porter, linuxppc-embedded
On Wed, Apr 09, 2003 at 11:22:49AM +0200, luca gambazzi wrote:
> I'm booting with the pcore kernel.
>
> the pcore_find_bridges function in pcore_pci.c recognize my card as a
> 6750, but the 3750 uses a 21150 bridge and not a 21154.
That makes sense. When I did the port I had a 6750 and 680. They
are very similar but Force is too stupid to provide a method to
uniquely identify a board at runtime. So, you see the kludge where
anything booting a pcore kernel that has an MPC106 is a 6750 and
if it has a MPC107 then it must be a 680.
> Do you know where can i find documentation to solve this problem?
> and where I have to modify?
Talk to Force. You need the 3750 manual. I suspect that it has
different interrupt routing than the 6750. Right now, you are
picking up the pcore_6750_map_irq table which has irq 10 for the
on-board tulip. More than likely it's routed to a different input
on the 3750. You would create a pcore_3750_map_irq, and provide
some way to uniquely identify that you are on a 3750 and have the
kernel use that map_irq function.
> here you can find the bios log, maybe you can find an answer.
> http://lsa1pc32.epfl.ch/~gamba/robox/
Definitely looks like pci interrupt routing is incorrect. tulip
driver isn't getting interrupts. One warning, once you get
3750 docs...don't trust them, they are often incorrect. :)
When you get this working, please post a patch so it can be
incorporated. Good luck.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-04-09 9:22 luca gambazzi
2003-04-09 15:02 ` Matt Porter
@ 2003-04-09 15:22 ` Matt Porter
2003-04-11 10:40 ` luca gambazzi
1 sibling, 1 reply; 9+ messages in thread
From: Matt Porter @ 2003-04-09 15:22 UTC (permalink / raw)
To: luca gambazzi; +Cc: Matt Porter, linuxppc-embedded
On Wed, Apr 09, 2003 at 11:22:49AM +0200, luca gambazzi wrote:
> Hi Matt
>
> I'm booting with the pcore kernel.
>
> the pcore_find_bridges function in pcore_pci.c recognize my card as a
> 6750, but the 3750 uses a 21150 bridge and not a 21154.
>
> Do you know where can i find documentation to solve this problem?
> and where I have to modify?
Oh, I should have mentioned the shotgun alternative to waiting on docs
from Force. Assume that the 3750 uses cascade irqs 9-12 for all pci
interrupts just like the 6750. Try changing the 6750 tulip map_irq
entry to be 9,11,12 and see if any work.
BTW, saw your list of devices in the /proc/pci dump. Looks like a
fun project. :)
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Linux on Force Computers CPCI-3750 eth drivers
2003-04-09 15:22 ` Matt Porter
@ 2003-04-11 10:40 ` luca gambazzi
0 siblings, 0 replies; 9+ messages in thread
From: luca gambazzi @ 2003-04-11 10:40 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-embedded
hi matt
as you said the problem was on the eth card irq,... the irq is 9.
i prepear a patch and i'll send you in next days.
happy weekend
luca
On Wed, 2003-04-09 at 17:22, Matt Porter wrote:
> On Wed, Apr 09, 2003 at 11:22:49AM +0200, luca gambazzi wrote:
> > Hi Matt
> >
> > I'm booting with the pcore kernel.
> >
> > the pcore_find_bridges function in pcore_pci.c recognize my card as a
> > 6750, but the 3750 uses a 21150 bridge and not a 21154.
> >
> > Do you know where can i find documentation to solve this problem?
> > and where I have to modify?
>
> Oh, I should have mentioned the shotgun alternative to waiting on docs
> from Force. Assume that the 3750 uses cascade irqs 9-12 for all pci
> interrupts just like the 6750. Try changing the 6750 tulip map_irq
> entry to be 9,11,12 and see if any work.
>
> BTW, saw your list of devices in the /proc/pci dump. Looks like a
> fun project. :)
>
> Regards,
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2003-04-11 10:40 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-29 14:55 Linux on Force Computers CPCI-3750 luca gambazzi
2003-03-29 15:43 ` Tom Rini
2003-04-04 11:49 ` Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
2003-04-04 21:00 ` Tom Rini
2003-04-04 21:11 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 9:22 luca gambazzi
2003-04-09 15:02 ` Matt Porter
2003-04-09 15:22 ` Matt Porter
2003-04-11 10:40 ` luca gambazzi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).