All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jiang Liu <jiang.liu@huawei.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: PCI/e1000 BUG: unable to handle kernel paging request at 0ffff163
Date: Thu, 6 Sep 2012 17:05:22 +0800	[thread overview]
Message-ID: <20120906090522.GA25102@localhost> (raw)
In-Reply-To: <CAE9FiQVO6dj+rEP=phQD5VYEF-rak6UPYGMSV8ud0OyELo7Opg@mail.gmail.com>

On Wed, Sep 05, 2012 at 11:41:04AM -0700, Yinghai Lu wrote:
> On Tue, Sep 4, 2012 at 11:51 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Yinghai,
> >
> > There are many kernel paging errors showing up in tree:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-for-each-res-addon-v2
> >
> > The below summary shows that
> >
> > 1) it's a reliably reproducible bug
> > 2) all paging fault happens at address 0ffff163 and in some e1000 functions
> >
> > I'll try to bisect if the root cause is not obvious to you.  (Cannot
> > do so for now because there are 3 bisections on the way and I cannot
> > afford more..)
> 
> thanks, will check that...

Yinghai, I'm very sorry that it's a false report...

The root cause is memory corruption by the isdnloop driver:

==>     [    9.345694] isdnloop-ISDN-driver Rev 1.11.6.7
==>     [    9.347484] isdnloop: (loop0) virtual card added
        [    9.348444] bus: 'usb': driver_probe_device: matched device 1-1:2.0 with driver cdc_acm
        [    9.349773] bus: 'usb': really_probe: probing driver cdc_acm with device 1-1:2.0
        [    9.350967] cdc_acm 1-1:2.0: This device cannot do calls on its own. It is not a modem.
        [    9.353255] cdc_acm 1-1:2.0: ttyACM0: USB ACM device
        [    9.354137] BUG: unable to handle kernel paging request at 0ffff163
        [    9.355214] IP: [<0ffff163>] 0xffff162
        [    9.355869] *pde = 00000000

Which was recently fixed by

        commit 77f00f6324cb97cf1df6f9c4aaeea6ada23abdb2
        Author:     Wu Fengguang <fengguang.wu@intel.com>
        Commit:     David S. Miller <davem@davemloft.net>
        CommitDate: Fri Aug 3 16:53:22 2012 -0700

            isdnloop: fix and simplify isdnloop_init()
            
            Fix a buffer overflow bug by removing the revision and printk.

Thanks,
Fengguang

  parent reply	other threads:[~2012-09-06  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  6:51 PCI/e1000 BUG: unable to handle kernel paging request at 0ffff163 Fengguang Wu
2012-09-05 18:41 ` Yinghai Lu
2012-09-06  0:41   ` Fengguang Wu
2012-09-06  9:05   ` Fengguang Wu [this message]
2012-09-06 17:24     ` Yinghai Lu

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=20120906090522.GA25102@localhost \
    --to=fengguang.wu@intel.com \
    --cc=bhelgaas@google.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yinghai@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 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.