mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ian <brooke@jump.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panic with mounting CD in 2.6.0test8
Date: Tue, 21 Oct 2003 11:15:36 -0700	[thread overview]
Message-ID: <20031021111536.50b0a6cc.rddunlap@osdl.org> (raw)
In-Reply-To: <3F95227C.6080601@jump.net>

On Tue, 21 Oct 2003 07:11:40 -0500 Ian <brooke@jump.net> wrote:

| -----BEGIN PGP SIGNED MESSAGE-----
| Hash: SHA1
| 
| I'm getting a kernel panic in running 2.6.0test8 which I just compiled
| today.
| After chatting this up with #Kernelnewbies, erikm told me to post here.
| 
| http://www.gastronomicon.org/im003116.jpg
| 
| Attempt to mount a particular CD, which I'm thinking is just an ordinary
| data CD.
| It could be a VCD, but then I would suspect it would play on my DVD player.
| Windows sees it as a data disk with one big AVI file on it.
| Anyway, I was impressed by the magical symbol lookups in the crash dump,
| but I really just want to mount my CD.
| 
| I am not subscribed to this list, so please CC me on any correspondence.
| I will gladly help debug this.

So you can open/explore the CD in Windows?

The call stack could have scrolled off of the top of the screen.
If not, then cdrom_start_read() called cdrom_start_packet_command(),
but there's not enough info to see what went haywire in
cdrom_start_packet_command() or whether that latter function
called cdrom_start_read_continuation() which then erred or if
it called something which fumbled.  So if you can get more/better
info (from kernel log or serial console etc.), that would be very
helpful.

--
~Randy

      parent reply	other threads:[~2003-10-21 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 12:11 Ian
2003-10-21 12:55 ` Jens Axboe
2003-10-21 18:15 ` Randy.Dunlap [this message]

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=20031021111536.50b0a6cc.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=brooke@jump.net \
    --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

Powered by JetHome