mirror of https://lore.kernel.org/lkml/
 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: Fri, 10 Apr 2009 11:18:35 -0400	[thread overview]
Message-ID: <18911.25419.893747.465556@stoffel.org> (raw)
In-Reply-To: <20090410002435.52794220.zaitcev@redhat.com>


Pete> On Thu, 9 Apr 2009 23:01:09 -0400, "John Stoffel" <john@stoffel.org> wrote:
>> Any suggestions of a known good state I should start bisection from?

Pete> No suggestions, sorry. The part of usbmon that peeks at DMA-ed
Pete> data wasn't touched since December 2006. It worked fine since
Pete> then, your oops is the first. So, I don't expect bisection to
Pete> help.  At best you're going to find the commit where uvcvideo
Pete> was merged.

I guess my next step would be to unload that module and see if the
crash happens while I have usbmon loaded.

Pete> The right way forward is to deduce what's going on, IMHO. Maybe
Pete> usbmon is trying to take an address in the GART aperture and
Pete> convert it into a struct page. Or the direction in URB
Pete> mismatches endpoint.  Or any number of other things.

I do have the Radeon driver installed, with DRI, etc.  

Pete> I'm working on it, but I'm not done with puzzling out the dmesg
Pete> you sent me, sorry again.

Let me know if you want me to put in debugging messages or try for
more netconsole output.  I built a bunch of kernels last night, but
ran out of reboot time (learning git...) to test them.  I figured I'd
go back to 2.6.26 and see if I had the problem there.  If not, it's a
good start for bisection.

I'll keep poking at this, though tax time is starting to fill my time
right now too.  :]

John


      reply	other threads:[~2009-04-10 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  3:03 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
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 [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=18911.25419.893747.465556@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

all inboxes | Powered by JetHome®