From: "Michael Troß" <mtross@compu-shack.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPU Lockup with 2.4.21 and 2.4.22-pre
Date: 22 Jul 2003 14:55:05 +0200 [thread overview]
Message-ID: <1058878505.2232.122.camel@mtross2.csintern.de> (raw)
In-Reply-To: <0001F474@gwia.compu-shack.com>
Am Die, 2003-07-22 um 13.51 schrieb Udo A. Steinberg:
> Note that the fddi patch includes a patch you've previously sent me, which
> isn't present in the driver on your website.
As you might know, the Compu-Shack fddi products reached end-of-life
last year.
> If you need more information, let me know. Also if you have any tips or
> patches that would help in debugging the issue, I'm happy to try them.
As I can't locate the code sequence in my driver module, please check it
with your compiled kernel:
objdump -d vmlinux | grep -A 20 "7e f5" | grep csfddi
or module:
hexdump -e '32/1 "%02x " "\n"' csf.o | grep "7e f5 e9 e8"
Do you get a result like the code line from your oops, which eip is
referring to?
> MT> What makes you believe this? There is no matching code sequence like the
> MT> one from your dump in the driver, to be exact: in a driver compiled with
> MT> gcc 3.3 and kernel 2.4.21.
>
> The fact that the backtrace in the decoded oops looks like the lockup
> happened in the fddi driver led me to the conclusion that this may be
> the culprit.
But you got two different decoding results, didn't you ?!
> Regards,
> -Udo.
Regards,
Michael
next parent reply other threads:[~2003-07-22 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0001F474@gwia.compu-shack.com>
2003-07-22 12:55 ` Michael Troß [this message]
2003-07-22 14:24 ` CPU Lockup with 2.4.21 and 2.4.22-pre Udo A. Steinberg
[not found] <0001F49C@gwia.compu-shack.com>
2003-07-22 15:26 ` Michael Troß
2003-07-22 15:30 ` Udo A. Steinberg
[not found] <0001F3D0@gwia.compu-shack.com>
2003-07-22 10:24 ` Michael Troß
2003-07-22 11:51 ` Udo A. Steinberg
2003-07-21 14:12 Udo A. Steinberg
2003-07-21 14:17 ` Udo A. Steinberg
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=1058878505.2232.122.camel@mtross2.csintern.de \
--to=mtross@compu-shack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=us15@os.inf.tu-dresden.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.