sporadic kernel panic during boot (MPC8xx, FEC)

sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Hi there,

I am using the linux kernel from bitkeepers linuxppc_2_4_devel exported
as of -rv2.4.18 on a MPC855T based board.

>From time to time I see a kernel panic while booting. I suppose it
related to FEC (or MII) interrupts. The time the kernel panic occurs is
different every time.

Two examples:
==================================================================================
-------------------------------------------------------
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
IDE phys mem : fe000000...fe000200 (size 00000200)
hda: probing with STATUS(0x50) instead of ALTSTATUS(0x00)
hda: HITACHI_DK239A-65, ATA DISK drive
ide0 at 0xc2000000-0xc2000007,0xc2000106 on irq 2
hda: 12685680 sectors (6495 MB) w/512KiB Cache, CHS=13424/15/63
Partition check:
 hda: hda1 hda2
Oops: kernel access of bad area, sig: 11
NIP: C00AE7E8 XER: 00000000 LR: C0003984 SP: C01E9DC0 REGS: c01e9d10
TRAP: 0300    Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 000000D0, DSISR: 00000129
TASK = c01e8000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: F0000002 C01E9DC0 C01E8000 0000000A C01D5400 C01E9E30 C0122608
C01F6000
GPR08: 00000000 00000000 C0154018 00000001 24008022 100198C8 00FE3A00
007FFF83
GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00001032 001E9E20 00000000
C000298C
GPR24: C0003A28 00000140 C01E9E30 C01F6720 0000000A F0000000 C01D5400
FFF00E00
Call backtrace:
C0104CF0 C0003984 C0003A84 C000298C C00032A4 C0003440 C014FE9C
C014E740 C014E77C C0150608 C014D76C C01477C8 C0147810 C0002558
C0004D28
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
 <0>Rebooting in 180 seconds..
-------------------------------------------------------
C0104CF0 C0003984 C0003A84 C000298C C00032A4 C0003440 C014FE9C
C014E740 C014E77C C0150608 C014D76C C01477C8 C0147810 C0002558
C0004D28
0xc0104cf0 -- 0xc010461c + 0x06d4   vsnprintf
0xc0003984 -- 0xc00037f4 + 0x0190   ppc_irq_dispatch_handler
0xc0003a84 -- 0xc0003a28 + 0x005c   do_IRQ
0xc000298c -- 0xc000298c + 0x0000   ret_from_intercept
0xc00032a4 -- 0xc00031b0 + 0x00f4   setup_irq
0xc0003440 -- 0xc000339c + 0x00a4   request_8xxirq
0xc014fe9c -- 0xc014fc98 + 0x0204   fec_enet_init
0xc014e740 -- 0xc014e710 + 0x0030   network_probe
0xc014e77c -- 0xc014e76c + 0x0010   net_device_init
0xc0150608 -- 0xc015038c + 0x027c   net_dev_init
0xc014d76c -- 0xc014d754 + 0x0018   device_init
0xc01477c8 -- 0xc0147798 + 0x0030   do_initcalls
0xc0147810 -- 0xc01477e8 + 0x0028   do_basic_setup
0xc0002558 -- 0xc0002544 + 0x0014   init
0xc0004d28 -- 0xc0004cfc + 0x002c   kernel_thread

==================================================================================
...
eth0: FEC ENET Version 0.2, FEC irq 9, MII irq 10, addr
00:a0:33:00:37:e8
eth0: Phy @ 0x0, type LXT971 (0x001378e2)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 1024)
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
IP-Config: Complete:
      device=eth0, addr=192.168.11.225, mask=255.255.255.0,
gw=255.255.255.255,
     host=idif3, domain=, nis-domain=(none),
     bootserver=192.168.11.91, rootserver=192.168.11.91, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.11.91
eth0: status: link up, 100 Mbps Full Duplex, auto-negotiation complete.
Looking up port of RPC 100005/1 on 192.168.11.91
Oops: kernel access of bad area, sig: 11
NIP: C00F8510 XER: 00000000 LR: C00F84C4 SP: C01E9DB0 REGS: c01e9d00
TRAP: 0300    Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: C013C2C4, DSISR: 82000000
TASK = c01e8000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: C013C2A0 C01E9DB0 C01E8000 00000001 C01F68C0 00000000 C01E9E4C
C01F6000
GPR08: 00000038 00000001 000006E0 C013C2B4 24008022 100198C8 00FE3A00
007FFF83
GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00FDDD70 C010DDBC 00FA0740
C0150000
GPR24: C0140000 00FE5288 007FFEC0 C01E9E58 C01E9EA8 C0FF0E50 C01E9DC8
C01E9DC8
Call backtrace:
C00F84C4 C00F8358 C0070A48 C0070970 C014C838 C014C89C C014ABB8
C000242C C000255C C0004D28
Kernel panic: Attempted to kill init!
-------------------------------------------------------
Reading symbols from System.map
C00F84C4 C00F8358 C0070A48 C0070970 C014C838 C014C89C C014ABB8
C000242C C000255C C0004D28
0xc00f84c4 -- 0xc00f847c + 0x0048   rpc_call_setup
0xc00f8358 -- 0xc00f82d8 + 0x0080   rpc_call_sync
0xc0070a48 -- 0xc00709a4 + 0x00a4   nfs_gen_mount
0xc0070970 -- 0xc007095c + 0x0014   nfs_mount
0xc014c838 -- 0xc014c7cc + 0x006c   root_nfs_get_handle
0xc014c89c -- 0xc014c874 + 0x0028   nfs_root_data
0xc014abb8 -- 0xc014ab6c + 0x004c   mount_root
0xc000242c -- 0xc00023bc + 0x0070   prepare_namespace
0xc000255c -- 0xc0002544 + 0x0018   init
0xc0004d28 -- 0xc0004cfc + 0x002c   kernel_thread
==================================================================================

Any ideas?

Thanks,

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Christian Pellegrin]

On Thu, 11 Apr 2002, Steven Scholz wrote:

>
> Hi there,
>
> I am using the linux kernel from bitkeepers linuxppc_2_4_devel exported
> as of -rv2.4.18 on a MPC855T based board.
>

...

>
> Any ideas?
>
> Thanks,
>

not really sure this will help you, but I had similar problem (spurious
hangs during boot/insmod on 823 and 850 MPCs). The ppc mm for 8xx in 2.4
repository is broken, use that in 2.4-devel that works fine. AFA net
devices are concerned check that rx start is done in open and not in init
since linux doesn't like packets before a device is opened.

Bye!


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Christian Pellegrin wrote:

> not really sure this will help you, but I had similar problem (spurious
> hangs during boot/insmod on 823 and 850 MPCs). The ppc mm for 8xx in 2.4
> repository is broken, use that in 2.4-devel that works fine. AFA net
> devices are concerned check that rx start is done in open and not in init
> since linux doesn't like packets before a device is opened.

Thanks for your reply.

I got the kernel from the linuxppc_2_4_devel tree using

bk export ... -rv2.4.18

So I guess I do have a 2.4-devel. Right?

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Christian Pellegrin]

On Thu, 11 Apr 2002, Steven Scholz wrote:

>
> bk export ... -rv2.4.18
>
> So I guess I do have a 2.4-devel. Right?
>

bk pull to sync to the last version, but AFAIK it's 2.4-devel :-)

Bye!


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Tom Rini]

On Thu, Apr 11, 2002 at 09:23:11AM +0200, Steven Scholz wrote:
>
> Christian Pellegrin wrote:
>
> > not really sure this will help you, but I had similar problem (spurious
> > hangs during boot/insmod on 823 and 850 MPCs). The ppc mm for 8xx in 2.4
> > repository is broken, use that in 2.4-devel that works fine. AFA net
> > devices are concerned check that rx start is done in open and not in init
> > since linux doesn't like packets before a device is opened.
>
> Thanks for your reply.
>
> I got the kernel from the linuxppc_2_4_devel tree using
>
> bk export ... -rv2.4.18
>
> So I guess I do have a 2.4-devel. Right?

No.  -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Tom Rini wrote:
> > I got the kernel from the linuxppc_2_4_devel tree using
> >
> > bk export ... -rv2.4.18
> >
> > So I guess I do have a 2.4-devel. Right?
>
> No.  -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.

Well Tom,

I do a "bk pull" from http://ppc.bkserver.net/linuxppc_2_4_devel once in
a while.
And when I do a "bk export -r2.4.18 ..." I definetly get PPC stuff in
the resulting tree. Otherwise it would be easy to notice that there is
something strange!

Anyway, from noe on I try to remember not to use the tags but the
changeset to export the tree.

BTW does anyone know a good and easy way to get the changes from the
bitkeeper tree into a local CVS?
For now I "bk pull" then "bk export" and then "cvs import" and then
merge... :-(

Cheers,

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Wolfgang Grandegger]

On 04/11/2002 05:31 PM, Tom Rini wrote:

>On Thu, Apr 11, 2002 at 09:23:11AM +0200, Steven Scholz wrote:
>>
>> Christian Pellegrin wrote:
>>
>> > not really sure this will help you, but I had similar problem (spurious
>> > hangs during boot/insmod on 823 and 850 MPCs). The ppc mm for 8xx in 2.4
>> > repository is broken, use that in 2.4-devel that works fine. AFA net
>> > devices are concerned check that rx start is done in open and not in init
>> > since linux doesn't like packets before a device is opened.
>>
>> Thanks for your reply.
>>
>> I got the kernel from the linuxppc_2_4_devel tree using
>>
>> bk export ... -rv2.4.18
>>
>> So I guess I do have a 2.4-devel. Right?
>
>No.  -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.
>
You mean it's identical to linux-2.4.18.tar.gz from kernel.org?
[I'm just curious what I really get with the above command.]

Thanks,

Wolfgang.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Tom Rini]

On Thu, Apr 11, 2002 at 09:06:02PM +0200, Wolfgang Grandegger wrote:
> On 04/11/2002 05:31 PM, Tom Rini wrote:
>
> >On Thu, Apr 11, 2002 at 09:23:11AM +0200, Steven Scholz wrote:
> >>
> >> Christian Pellegrin wrote:
> >>
> >> > not really sure this will help you, but I had similar problem (spurious
> >> > hangs during boot/insmod on 823 and 850 MPCs). The ppc mm for 8xx in 2.4
> >> > repository is broken, use that in 2.4-devel that works fine. AFA net
> >> > devices are concerned check that rx start is done in open and not in init
> >> > since linux doesn't like packets before a device is opened.
> >>
> >> Thanks for your reply.
> >>
> >> I got the kernel from the linuxppc_2_4_devel tree using
> >>
> >> bk export ... -rv2.4.18
> >>
> >> So I guess I do have a 2.4-devel. Right?
> >
> >No.  -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.
> >
> You mean it's identical to linux-2.4.18.tar.gz from kernel.org?

Yes.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

> > >No.  -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.
> > You mean it's identical to linux-2.4.18.tar.gz from kernel.org?
> Yes.

Yes. Indeed. I just compared the two trees and got

/opt/linuxppc > dircmp -s devel_2_4_18 linux
2002-04-12 10:18       Comparison of devel_2_4_18 linux        Seite
1

different       ./fs/binfmt_elf.c
different       ./net/ipv4/udp.c


But I am still not sure if I understand what that means. Is there a
FAQ/README/HowTo about the LinuxPPC/Bitkeeper/Versionnumbering
somewhere?

Which ChangeSet or Tag stands for a stable PPC kernel?

Which ChangeSet equals (with regard to functionality) the official
linux-2.4.18 from kernel.org?

Does the ChangesSet 1.900 (which is shortly after Tag 2.4.18) contain
all the stuff that's in the offical kernel?

Thanks,

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Wolfgang Denk]

In message <3CB6A2FE.62FFB14E@imc-berlin.de> you wrote:
>
> But I am still not sure if I understand what that means. Is there a
> FAQ/README/HowTo about the LinuxPPC/Bitkeeper/Versionnumbering
> somewhere?

Good question!

> Which ChangeSet or Tag stands for a stable PPC kernel?

Define stable :-(

> Which ChangeSet equals (with regard to functionality) the official
> linux-2.4.18 from kernel.org?
>
> Does the ChangesSet 1.900 (which is shortly after Tag 2.4.18) contain
> all the stuff that's in the offical kernel?

Another "interesting" question: assuming I identif a certain state of
the tree with Changeset XXX today, how can I find  exactly  the  same
state  XXX  in  three  monbths,  when  the  changesets  may have been
renumbered?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"What people have been reduced to are  mere  3-D  representations  of
their own data."                                      - Arthur Miller

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Tom Rini]

On Fri, Apr 12, 2002 at 03:33:27PM +0200, Wolfgang Denk wrote:
> In message <3CB6A2FE.62FFB14E@imc-berlin.de> you wrote:
> >
> > But I am still not sure if I understand what that means. Is there a
> > FAQ/README/HowTo about the LinuxPPC/Bitkeeper/Versionnumbering
> > somewhere?
>
> Good question!

Without a real answer, unfortunatly.

> > Which ChangeSet or Tag stands for a stable PPC kernel?
>
> Define stable :-(

Well, whichever ChangeSet is the merge of someplace:/.../linux_2_4 into
someplace:/.../linuxppc_2_4 is the merge into linuxppc_2_4.

> > Which ChangeSet equals (with regard to functionality) the official
> > linux-2.4.18 from kernel.org?
> >
> > Does the ChangesSet 1.900 (which is shortly after Tag 2.4.18) contain
> > all the stuff that's in the offical kernel?
>
> Another "interesting" question: assuming I identif a certain state of
> the tree with Changeset XXX today, how can I find  exactly  the  same
> state  XXX  in  three  monbths,  when  the  changesets  may have been
> renumbered?

Well, ChangeSet 1.900 just happens to be after, but I don't recall the
exact changeset of the 2.4.18 merge.  As for the other question, I
forget the exact command (ask on the bk users list) bk each ChangeSet
has a unique key with it, that does not change, so you can later find
things based on the key.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Tom Rini wrote:

> > Define stable :-(
> Well, whichever ChangeSet is the merge of someplace:/.../linux_2_4 into
> someplace:/.../linuxppc_2_4 is the merge into linuxppc_2_4.

??? Excuse me? :-(
What did you say?

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Tom Rini]

On Fri, Apr 12, 2002 at 05:13:59PM +0200, Steven Scholz wrote:
>
> Tom Rini wrote:
>
> > > Define stable :-(
> > Well, whichever ChangeSet is the merge of someplace:/.../linux_2_4 into
> > someplace:/.../linuxppc_2_4 is the merge into linuxppc_2_4.
>
> ??? Excuse me? :-(
> What did you say?

Well, in the linuxppc_2_4 and linuxppc_2_4_devel trees (this doesn't
hold true for the Linus and Marcelo BK trees since they work differently):
ChangeSet@1.604, 2002-04-05 10:17:36-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linux_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4

ChangeSet@1.2.2.138, 2002-04-05 10:11:39-07:00, trini@opus.bloom.county
  patch-2.4.19-pre5-pre6
  TAG: v2.4.19-pre6


So 1.604 will get you 2.4.19-pre6 in the linuxppc_2_4 tree.

In the linuxppc_2_4_devel tree:
ChangeSet@1.900, 2002-02-26 17:37:17-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4_devel

ChangeSet@1.118.1.473, 2002-02-26 17:31:25-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linux_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4

ChangeSet@1.2.2.133, 2002-02-26 17:28:14-07:00, trini@opus.bloom.county
  The actual change in 2.4.18-rc4 got applied twice, revert.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Wolfgang Denk]

In message <20020412150803.GO759@opus.bloom.county> you wrote:
>
> > Another "interesting" question: assuming I identif a certain state of
> > the tree with Changeset XXX today, how can I find  exactly  the  same
> > state  XXX  in  three  monbths,  when  the  changesets  may have been
> > renumbered?
>
> Well, ChangeSet 1.900 just happens to be after, but I don't recall the
> exact changeset of the 2.4.18 merge.  As for the other question, I
> forget the exact command (ask on the bk users list) bk each ChangeSet
> has a unique key with it, that does not change, so you can later find
> things based on the key.

I know how to find the key:

	$ bk prs -d ':KEY:\n' -r1.900 ChangeSet
	======== ChangeSet 1.900 ========
	trini@opus.bloom.county|ChangeSet|20020227003717|01133


I _think_ I should be able to perform the reverse operation using "bk
key2rev", but I never understood how to use this command.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There's nothing  disgusting  about  it  [the  Companion].  It's  just
another life form, that's all. You get used to those things.
	-- McCoy, "Metamorphosis", stardate 3219.8

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Tom Rini]

On Fri, Apr 12, 2002 at 05:25:54PM +0200, Wolfgang Denk wrote:
> In message <20020412150803.GO759@opus.bloom.county> you wrote:
> >
> > > Another "interesting" question: assuming I identif a certain state of
> > > the tree with Changeset XXX today, how can I find  exactly  the  same
> > > state  XXX  in  three  monbths,  when  the  changesets  may have been
> > > renumbered?
> >
> > Well, ChangeSet 1.900 just happens to be after, but I don't recall the
> > exact changeset of the 2.4.18 merge.  As for the other question, I
> > forget the exact command (ask on the bk users list) bk each ChangeSet
> > has a unique key with it, that does not change, so you can later find
> > things based on the key.
>
> I know how to find the key:
>
> 	$ bk prs -d ':KEY:\n' -r1.900 ChangeSet
> 	======== ChangeSet 1.900 ========
> 	trini@opus.bloom.county|ChangeSet|20020227003717|01133
>
>
> I _think_ I should be able to perform the reverse operation using "bk
> key2rev", but I never understood how to use this command.

Okay, I think I just figured it out (the help page sucks..):
$ bk get ChangeSet
ChangeSet 1.944: 11970 lines
# escaped for bash's sake
$ echo trini@opus.bloom.county\|ChangeSet\|20020227003717\|01133 | bk key2rev ChangeSet
1.900

Or bk key2rev ChangeSet, and enter the keys

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Wolfgang Grandegger]

On 04/11/2002 09:07 AM, Steven Scholz wrote:

>Hi there,
>
>I am using the linux kernel from bitkeepers linuxppc_2_4_devel exported
>as of -rv2.4.18 on a MPC855T based board.
>
AFAIK, this relase tag applies ony to Linus's part of the tree.
The PPC part is somehow undefined and might be quite old.
I usually search "bk changes" for "v2.4.18" and then take a
change-set shortly afterwards e.g.:

  bk export -r1.900 <path>

Hope it helps,

Wolfgang.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Wolfgang,

> AFAIK, this relase tag applies ony to Linus's part of the tree.
> The PPC part is somehow undefined and might be quite old.
> I usually search "bk changes" for "v2.4.18" and then take a
> change-set shortly afterwards e.g.:
>
>   bk export -r1.900 <path>

Hmm. Yeah. Damn. You're right - of course.
I forgot about this.

Thanks a million!

Steven

BTW cs-1.900 seems not to have this kernal panic problem.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: sporadic kernel panic during boot (MPC8xx, FEC)

[Kári Davíðsson]

I have had this "random crashes" for linux 2.4.18-pre1 from
linuxppc-2_4_devel
for some time now, it was not to annoying, since so much other stuff has
been unstable for us. Theses crashses ware mostly during booting of the
kernel, i.e.
if the kernel made it through the boot it seemed to run stable. I
collected at one point some statistics and it crashed in 0.5% - 1% cases
of reboot.
I got 2.4.19-pre6 last weekend from the rsync source at mvista, merged
and compiled. Since
then I had the board in my "reboot loop" and rebooted some 6000 times.
Not one
single crash. So I am happy, and recomend to you to go get the latest
version from
linuxppc_2_4_devel (well I have version 2.4.19pre6 gotten from the rsync
source at
mvista last weekend).

Regards,

K.D.

> -----Original Message-----
> From: Steven Scholz [mailto:steven.scholz@imc-berlin.de]
> Sent: 11. apríl 2002 07:08
> To: LinuxPPC
> Subject: sporadic kernel panic during boot (MPC8xx, FEC)
>
>
>
> Hi there,
>
> I am using the linux kernel from bitkeepers
> linuxppc_2_4_devel exported
> as of -rv2.4.18 on a MPC855T based board.
>
> From time to time I see a kernel panic while booting. I suppose it
> related to FEC (or MII) interrupts. The time the kernel panic
> occurs is
> different every time.
>
> Two examples:
> ==============================================================
> ====================
> -------------------------------------------------------
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 50MHz system bus speed for PIO modes; override with
> idebus=xx
> IDE phys mem : fe000000...fe000200 (size 00000200)
> hda: probing with STATUS(0x50) instead of ALTSTATUS(0x00)
> hda: HITACHI_DK239A-65, ATA DISK drive
> ide0 at 0xc2000000-0xc2000007,0xc2000106 on irq 2
> hda: 12685680 sectors (6495 MB) w/512KiB Cache, CHS=13424/15/63
> Partition check:
>  hda: hda1 hda2
> Oops: kernel access of bad area, sig: 11
> NIP: C00AE7E8 XER: 00000000 LR: C0003984 SP: C01E9DC0 REGS: c01e9d10
> TRAP: 0300    Not tainted
> MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 000000D0, DSISR: 00000129
> TASK = c01e8000[1] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> GPR00: F0000002 C01E9DC0 C01E8000 0000000A C01D5400 C01E9E30 C0122608
> C01F6000
> GPR08: 00000000 00000000 C0154018 00000001 24008022 100198C8 00FE3A00
> 007FFF83
> GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00001032 001E9E20 00000000
> C000298C
> GPR24: C0003A28 00000140 C01E9E30 C01F6720 0000000A F0000000 C01D5400
> FFF00E00
> Call backtrace:
> C0104CF0 C0003984 C0003A84 C000298C C00032A4 C0003440 C014FE9C
> C014E740 C014E77C C0150608 C014D76C C01477C8 C0147810 C0002558
> C0004D28
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
>  <0>Rebooting in 180 seconds..
> -------------------------------------------------------
> C0104CF0 C0003984 C0003A84 C000298C C00032A4 C0003440 C014FE9C
> C014E740 C014E77C C0150608 C014D76C C01477C8 C0147810 C0002558
> C0004D28
> 0xc0104cf0 -- 0xc010461c + 0x06d4   vsnprintf
> 0xc0003984 -- 0xc00037f4 + 0x0190   ppc_irq_dispatch_handler
> 0xc0003a84 -- 0xc0003a28 + 0x005c   do_IRQ
> 0xc000298c -- 0xc000298c + 0x0000   ret_from_intercept
> 0xc00032a4 -- 0xc00031b0 + 0x00f4   setup_irq
> 0xc0003440 -- 0xc000339c + 0x00a4   request_8xxirq
> 0xc014fe9c -- 0xc014fc98 + 0x0204   fec_enet_init
> 0xc014e740 -- 0xc014e710 + 0x0030   network_probe
> 0xc014e77c -- 0xc014e76c + 0x0010   net_device_init
> 0xc0150608 -- 0xc015038c + 0x027c   net_dev_init
> 0xc014d76c -- 0xc014d754 + 0x0018   device_init
> 0xc01477c8 -- 0xc0147798 + 0x0030   do_initcalls
> 0xc0147810 -- 0xc01477e8 + 0x0028   do_basic_setup
> 0xc0002558 -- 0xc0002544 + 0x0014   init
> 0xc0004d28 -- 0xc0004cfc + 0x002c   kernel_thread
>
> ==============================================================
> ====================
> ...
> eth0: FEC ENET Version 0.2, FEC irq 9, MII irq 10, addr
> 00:a0:33:00:37:e8
> eth0: Phy @ 0x0, type LXT971 (0x001378e2)
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 1024 bind 1024)
> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> IP-Config: Complete:
>       device=eth0, addr=192.168.11.225, mask=255.255.255.0,
> gw=255.255.255.255,
>      host=idif3, domain=, nis-domain=(none),
>      bootserver=192.168.11.91, rootserver=192.168.11.91, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.11.91
> eth0: status: link up, 100 Mbps Full Duplex, auto-negotiation
> complete.
> Looking up port of RPC 100005/1 on 192.168.11.91
> Oops: kernel access of bad area, sig: 11
> NIP: C00F8510 XER: 00000000 LR: C00F84C4 SP: C01E9DB0 REGS: c01e9d00
> TRAP: 0300    Not tainted
> MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: C013C2C4, DSISR: 82000000
> TASK = c01e8000[1] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> GPR00: C013C2A0 C01E9DB0 C01E8000 00000001 C01F68C0 00000000 C01E9E4C
> C01F6000
> GPR08: 00000038 00000001 000006E0 C013C2B4 24008022 100198C8 00FE3A00
> 007FFF83
> GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00FDDD70 C010DDBC 00FA0740
> C0150000
> GPR24: C0140000 00FE5288 007FFEC0 C01E9E58 C01E9EA8 C0FF0E50 C01E9DC8
> C01E9DC8
> Call backtrace:
> C00F84C4 C00F8358 C0070A48 C0070970 C014C838 C014C89C C014ABB8
> C000242C C000255C C0004D28
> Kernel panic: Attempted to kill init!
> -------------------------------------------------------
> Reading symbols from System.map
> C00F84C4 C00F8358 C0070A48 C0070970 C014C838 C014C89C C014ABB8
> C000242C C000255C C0004D28
> 0xc00f84c4 -- 0xc00f847c + 0x0048   rpc_call_setup
> 0xc00f8358 -- 0xc00f82d8 + 0x0080   rpc_call_sync
> 0xc0070a48 -- 0xc00709a4 + 0x00a4   nfs_gen_mount
> 0xc0070970 -- 0xc007095c + 0x0014   nfs_mount
> 0xc014c838 -- 0xc014c7cc + 0x006c   root_nfs_get_handle
> 0xc014c89c -- 0xc014c874 + 0x0028   nfs_root_data
> 0xc014abb8 -- 0xc014ab6c + 0x004c   mount_root
> 0xc000242c -- 0xc00023bc + 0x0070   prepare_namespace
> 0xc000255c -- 0xc0002544 + 0x0018   init
> 0xc0004d28 -- 0xc0004cfc + 0x002c   kernel_thread
> ==============================================================
> ====================
>
> Any ideas?
>
> Thanks,
>
> Steven
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: sporadic kernel panic during boot (MPC8xx, FEC)

[Steven Scholz]

Kári,

> I have had this "random crashes" for linux 2.4.18-pre1 from
> linuxppc-2_4_devel for some time now...
> ...
> I got 2.4.19-pre6 last weekend from the rsync source at mvista, merged
> and compiled. Since
> then I had the board in my "reboot loop" and rebooted some 6000 times.
> Not one single crash...

Thanks. I just pulled cs-1.900.
It seems to work fine and solved at least one other problem for me! :o)

Thanks a lot,

Steven

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/