All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [BUG] unable to handle kernel paging request at virtual address 0800000e
Date: Mon, 09 Apr 2007 16:48:01 -0400	[thread overview]
Message-ID: <461AA681.50605@redhat.com> (raw)
In-Reply-To: <4616CBF4.8020205@m3y3r.de>

Thomas Meyer wrote:
> dmesg output:
> 
> pktcdvd: pkt_get_last_written failed
> BUG: unable to handle kernel paging request at virtual address 0800000e
<SNIP>
> EFLAGS: 00010203   (2.6.21-rc6 #295)
<SNIP>
> cdrom: This disc doesn't have any tracks I recognize!
> 
> This happens while calling command pktsetup.
> 

Well that's very strange.

long do_sys_open(int dfd, const char __user *filename, int flags, int mode)
{
        char *tmp = getname(filename);
        int fd = PTR_ERR(tmp);

        if (!IS_ERR(tmp)) {
                fd = get_unused_fd();
                if (fd >= 0) {
============>           struct file *f = do_filp_open(dfd, tmp, flags, mode);
                        if (IS_ERR(f)) {
                                put_unused_fd(fd);
                                fd = PTR_ERR(f);
                        } else {
                                fsnotify_open(f->f_path.dentry);
                                fd_install(fd, f);
                        }
                }
                putname(tmp);
        }

do_filp_open has returned 0x8000002

Isn't that a SCSI error of some kind?

IAC we have tried to do fsnotify_open(f->f_path.dentry) with that result...

  reply	other threads:[~2007-04-09 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 22:38 [BUG] unable to handle kernel paging request at virtual address 0800000e Thomas Meyer
2007-04-09 20:48 ` Chuck Ebbert [this message]
2007-04-13 19:45 ` Joe Kappus

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=461AA681.50605@redhat.com \
    --to=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=thomas@m3y3r.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.