From: "Rüdiger Scholz" <r.scholz@bluehash.de>
To: Joel Soete <jsoe0708@tiscali.be>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Some 2.5-testing
Date: Thu, 19 Jun 2003 11:10:07 +0200 [thread overview]
Message-ID: <3EF17DEF.1050803@bluehash.de> (raw)
In-Reply-To: <3ED70CF1000076E9@ocpmta2.freegates.net>
Hi,
>Do you already try to rebuild and re-try a kernel without this support?
>
>Joel
>
>
this was also my thought, so recompiled kernel without md-support. I
just rebooted the machine with the new kernel.... Same problem at
another place:
----------------SNIP-----------
Keyboard initialization sequence failled
input: PS/2 keyboard port at 0xf0108000 (irq 69) found and attached
input: PS/2 mouse port at 0xf0108100 (irq 69) found and attached
HP SDC: HP SDC at 0xf0201000, IRQ 126 (NMI IRQ 125)
HP SDC: New style SDC
HP SDC: Revision: 1820-4784
HP SDC: TI SN76494 beeper present
HP SDC: OKI MSM-58321 BBRTC present
HP SDC: Spunking the self test register to force PUP on next
firmware reset.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
oprofile: using timer interrupt.
Badness in local_bh_enable at kernel/s1012503c>] [<101615dc>]
[<10124f10>]
[<1028ab94>] [<10494>]
<4> [<10210468>] [<10124b3c>] [<1018abf8>] [<10124cc8>]
ftirq.c:109
Kernel addresses on the stack:
[<10124ed8>] b1f0>] [<101070f8>] [<1028c0d8>] [<1028c20c>]
[<10128c68>] [<1020dd68>] [<101e493c>]
<4> [<10210468>] [<10124b3ck:
<4> [<10124ed8>] [<10105ab8>] [<101289a8>] [<1028a9d03b83c8>]
[<10399494>] [<10100284>]
[<10109c5c>]
Badnes [<101615dc>] [<10124f10>]
<4> [<1028ab94>] [<103b83c8>]> [<101e0f5c>] [<1012503c>]
[<101615dc>] [<10124f10>]
[1020dd48>] [<10210498>]
<4> [<10210468>] [<10124b3c>] c5c>]
<4>HP SDC: Transaction add failed: transaction already queuedl
addresses on the stack:
-----------------SNAP----------------
The interesting thing could this line: "oprofile: using timer
interrupt." I think in using the timer interrupt lies the problem.
Doesn't the md-stuff use also the timer-interrupt to measure the
throughput with various registers?
Rüdiger
next prev parent reply other threads:[~2003-06-19 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 16:06 [parisc-linux] Some 2.5-testing Rüdiger Scholz
2003-06-17 16:22 ` 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 [this message]
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=3EF17DEF.1050803@bluehash.de \
--to=r.scholz@bluehash.de \
--cc=jsoe0708@tiscali.be \
--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