linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: "John Stoffel" <john@stoffel.org>,
	Jarek Poplawski <jarkao2@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: usb_mon oops Re: tcpdump crashes 2.6.29.1 (and 2.6.29-rc5)
Date: Tue, 14 Apr 2009 09:38:47 -0400	[thread overview]
Message-ID: <18916.37351.872568.757026@stoffel.org> (raw)
In-Reply-To: <20090413174105.b03a1f19.zaitcev@redhat.com>

>>>>> "Pete" == Pete Zaitcev <zaitcev@redhat.com> writes:

Pete> On Thu, 9 Apr 2009 09:59:31 -0400, "John Stoffel" <john@stoffel.org> wrote:
>> Here's a dmesg of bootup:

>> [    0.000000] Linux version 2.6.29.1 (john@sail) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #24 SMP PREEMPT Tue Apr 7 11:30:52 EDT 2009
>> [    0.000999] Checking aperture...
>> [    0.000999] No AGP bridge found
>> [    0.000999] Node 0: aperture @ 20000000 size 32 MB
>> [    0.000999] Aperture pointing to e820 RAM. Ignoring.
>> [    0.000999] Your BIOS doesn't leave a aperture memory hole
>> [    0.000999] Please enable the IOMMU option in the BIOS setup
>> [    0.000999] This costs you 64 MB of RAM
>> [    0.000999] Mapping aperture over 65536 KB of RAM @ 20000000

>> [ 1396.271782] BUG: unable to handle kernel paging request at ffff880020a15cc0

Pete> So 20a15000 is in the aperture. Oh well, I screwed up. I meant
Pete> to check for this back in 2006 but forgot, and miraclously it
Pete> worked until now.

Pete> Here's the problem:

Pete> 	pg = phys_to_page(dma_addr);
Pete> 	map = kmap_atomic(pg, KM_IRQ0);
Pete> 	offset = mon_copy_to_buff(rp, offset, map + page_off, step_len);
Pete> 	kunmap_atomic(map, KM_IRQ0);

Pete> Obviously we don't want the page that's overlayed by the
Pete> aperture, but the page where IOMMU is pointing.

Thanks for finding this!  I was working on getting 2.6.25 built and
running, but it hates my Forcedeth ethernet ports and won't bring them
up, which complicated testing immensely.  It's tough when your home
directory is on NFS and the network is down...

I'm happy to test any patches you have.

Thanks,
John


  reply	other threads:[~2009-04-14 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  3:03 tcpdump crashes 2.6.29.1 (and 2.6.29-rc5) John Stoffel
2009-04-07 12:00 ` usb_mon oops " Jarek Poplawski
2009-04-07 15:25   ` John Stoffel
2009-04-07 18:52     ` John Stoffel
2009-04-07 19:04     ` Pete Zaitcev
2009-04-08 13:20       ` John Stoffel
2009-04-09  5:23         ` Pete Zaitcev
2009-04-09 13:59           ` John Stoffel
2009-04-13 23:41             ` Pete Zaitcev
2009-04-14 13:38               ` John Stoffel [this message]
2009-04-17  3:00                 ` John Stoffel
2009-04-17 18:09                   ` Pete Zaitcev
2009-04-10  3:01           ` John Stoffel
2009-04-10  6:24             ` Pete Zaitcev
2009-04-10 15:18               ` John Stoffel

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=18916.37351.872568.757026@stoffel.org \
    --to=john@stoffel.org \
    --cc=jarkao2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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).