From: Valéry Raulet <Valery.Raulet@enib•fr>
To: "linuxppc-embedded@lists•linuxppc.org"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Boot failed with new 2.3.99 kernel !
Date: Tue, 25 Apr 2000 10:25:47 +0200 [thread overview]
Message-ID: <3905568B.22D4E45F@enib.fr> (raw)
Hi all,
the following part seems sticky for my board.
>>NIP; c0184da8 <prep_route_pci_interrupts+d0/3d0> <=====
Trace; 00000000 Before first symbol
Trace; c01850dc <prep_pcibios_fixup+34/188>
Trace; c017fa88 <pcibios_init+44/60>
Trace; c0195868 <pci_init+14/58>
Trace; c017e7a8 <do_basic_setup+20/190>
Trace; c00039fc <init+14/1a8>
Trace; c0008e30 <kernel_thread+2c/38>
>>NIP; c0184da8 <prep_route_pci_interrupts+d0/3d0> <=====
After having a close look to 'prep_pci.c', it seems that this test
'*ProcInfo &MOT_PROC2_BIT' in 'prep_route_pci_interrupts(void)' cause
troubles.
What happens ? Any ideas ?
--
Valéry RAULET
Ecole Nationale d'Ingénieurs de Brest
Parvis Blaise Pascal
Technopôle Brest-Iroise
29280 PLOUZANE
Site Web : http://www.enib.fr/~raulet
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-25 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-25 8:25 Valéry Raulet [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-24 15:24 Boot failed with new 2.3.99 kernel ! Valéry Raulet
2000-04-24 15:33 ` Pavel Roskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3905568B.22D4E45F@enib.fr \
--to=valery.raulet@enib$(echo .)fr \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox