linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob_Tracy)
To: linux-kernel@vger.kernel.org
Cc: acme@conectiva.com.br
Subject: 2.5.38: oops with kernel LLC support enabled
Date: Wed, 25 Sep 2002 10:49:20 -0500 (CDT)	[thread overview]
Message-ID: <m17uEPg-0005khC@gherkin.frus.com> (raw)

Firstly, a big thanks to Ingo for kksymoops...  2.5.38 panics right
out of the chute with no way to save the oops output, so it's REALLY
nice to have it decoded on the screen!!  Manual transcription of the
oops output follows below.

What was I trying to do with LLC support?  I have an old JetDirect
interface in a LJ-III that speaks DLC/LLC only, and wanted to try to
use it with Linux.  (It should go without saying that NT and Win2K
can talk to it just fine :-)).  Both machines in a sample set of two
panic the same way...  One is a desktop with the NIC driver built-in.
The other (that produced the oops output below) is a Dell Latitude CPxJ
with a modular Xircom Tulip cardbus driver.

I guess I should mention that I haven't tried this with a 2.4 kernel.

 Unable to handle kernel NULL pointer dereference at virtual address 00000000
  printing eip:
 c0245da5
 *pde = 00000000
 Oops: 0000
 kernel
 CPU:    0
 EIP:    0060:[<c0245da5>]	Not tainted
 EFLAGS: 00010202
 EIP is at llc_sap_find [kernel] 0x25
 eax: c7fae000   ebx: c02e8e28   ecx: 000000aa   edx: 00000000
 esi: 00000000   edi: 00000000   ebp: 00000000   esp: c7faffa8
 ds: 0068   es: 0068   ss: 0068
 Process swapper (pid: 1, threadinfo=c7fae000 task=c7fac040)
 Stack: c02e8e28 000000aa 00000000 c0242141 000000aa c02e8e28 00000000 c02df8e1
        c01f0ca0 00000000 000000aa c02d0712 c7fae000 c0105093 c0105060 00000000
        00000000 00000000 c01054e5 00000000 00000000 00000000
 Call Trace: [<c0242141>] llc_sap_open [kernel] 0x11
 [<c01f0ca0>] snap_indicate [kernel] 0x0
 [<c0105093>] init [kernel] 0x33
 [<c0105060>] init [kernel] 0x0
 [<c01054e5>] kernel_thread_helper [kernel] 0x5
 
 
 Code: 8b 02 0f 18 00 81 fa 04 69 33 c0 74 08 38 4a f8 8d 72 a0 75
  <0>Kernel panic: Aiee, killing interrupt handler!
 In interrupt handler - not syncing
 
 
-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

             reply	other threads:[~2002-09-25 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 15:49 Bob_Tracy [this message]
2002-09-25 19:10 ` 2.5.38: oops with kernel LLC support enabled Arnaldo Carvalho de Melo

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=m17uEPg-0005khC@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=acme@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).