linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Kirby <sim@hostway.ca>
To: linux-btrace@vger.kernel.org
Subject: Oops on blktrace
Date: Wed, 30 Dec 2009 01:41:02 +0000	[thread overview]
Message-ID: <20091230014102.GA7296@hostway.ca> (raw)

Hello,

I just experienced an Oops while running blktrace on a 2.6.30.9 kernel
(production system).  There was no camera handy and no serial console
or crash dump log, so all we could get remotely was a function backtrace
copied by hand:

  memset_c
  relay_open_buf
  relay_open
  do_blk_trace_setup
  blk_trace_setup
  disk_name | HEX/HEX
  blk_trace_ioctl
  find_get_page
  blkdev_ioctrl
  filemap_fault
  unlock_page
  __do_fault
  block_ioctl
  vfs_ioctl
  do_vfs_ioctl
  sys_ioctl
  system_call_fastpath

At the time I had just run "blktrace /dev/etherd/e10.1" (an AOE device),
having recently run "btrace -t /dev/etherd/e10.1" and similar with no
problem.  I've since tried to reproduce this crash to no avail.  Have
there been any similar experiences or related fixes since 2.6.30.9?

Cheers,

Simon-

                 reply	other threads:[~2009-12-30  1:41 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=20091230014102.GA7296@hostway.ca \
    --to=sim@hostway.ca \
    --cc=linux-btrace@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).