From: "Rüdiger Scholz" <r.scholz@bluehash.de>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Some 2.5-testing
Date: Tue, 17 Jun 2003 18:06:44 +0200 [thread overview]
Message-ID: <3EEF3C94.3080300@bluehash.de> (raw)
Hi there,
I tried to get a running 2.5.70 kernel on my 715/100, but booting
results in an endless loop with the following error:
Badness in local_bh_enable at kernel/softirq.c:109
Kernel addresses on the stack:
[<10123d54>] [<10105884>] [<10127610>] [<10285e0c>]
[<102868c4>] [<10285828>] [<10287360>] [<1012b6ac>]
[<10287624>] [<1012782c>] [<101275c8>] [<10175800>]
[<10107000>] [<101876ac>] [<1010a068>] [<10285828>]
[<1028e468>] [<103951b8>] [<10123d54>] [<1028f904>]
[<1039541c>] [<10100278>] [<10109c5c>]
Only way to stop it, is to pull the plug...
Does anyone know a solution?
Another thing: During compile I get this warning several times:
"Warning: long unsigned int format, time_t arg (arg XX)" (But perhaps
this warning is solved with the fixes jejb uploaded currently)
Some more informations:
Kernel was generated via make distclean, make oldconfig, make vmlinux.
During compile I get this warning several times: "Warnung: long
unsigned int format, time_t arg (arg XX)"
OS: Debian testing with gcc-3.3 and glibc-2.3.16
HW: HP 715/100 with serial console and HIL-adaptor box (but no mouse
or keyboard is connected to the adaptor)
Debug: System.map and complete bootlog is here:
http://rscholz.bluehash.de/parisc/
TIA,
Ruediger
next reply other threads:[~2003-06-17 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 16:06 Rüdiger Scholz [this message]
2003-06-17 16:22 ` [parisc-linux] Some 2.5-testing John David Anglin
2003-06-19 3:59 ` Rüdiger Scholz
2003-06-19 8:55 ` Joel Soete
2003-06-19 9:10 ` Rüdiger Scholz
2003-06-19 10:16 ` Joel Soete
2003-06-19 11:40 ` Matthew Wilcox
2003-06-19 13:02 ` James Bottomley
2003-06-19 18:49 ` Rüdiger Scholz
2003-06-19 19:56 ` Matthew Wilcox
2003-06-19 23:28 ` Helge Deller
2003-06-22 10:04 ` Rüdiger Scholz
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=3EEF3C94.3080300@bluehash.de \
--to=r.scholz@bluehash.de \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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