mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.5.65 RCU oops.
Date: Fri, 21 Mar 2003 17:50:11 +0000	[thread overview]
Message-ID: <20030321175011.GB15652@suse.de> (raw)

hand transcribed oops (top bit missing from screen unfortunatly,
and box locked up solid).

Call trace:
 d_callback
 d_callback
 rcu_do_batch
 rcu_process_callbacks
 timer_interrupt
 tasklet_action
 do_softirq
 do_IRQ
 common_interrupt
 acpi_processor_idle
 default_idle
 cpu_idle
 _stext

Code: 0f 0b 2e 06 d6 de 54 c0 e9 d7 fe ff ff 8b 55 08 8b 5a 34 e9

Judging by the Code: line, it hit a BUG() somewhere, but the
rest of the code line looks like gibberish. Worst still, an
objdump -D of the vmlinux doesn't have the corresponding 
bytes in that order.  kernel text corruption ?

		Dave


                 reply	other threads:[~2003-03-21 17:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030321175011.GB15652@suse.de \
    --to=davej@codemonkey.org.uk \
    --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
all inboxes | Powered by JetHome®