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: Thu, 9 Apr 2009 23:01:09 -0400	[thread overview]
Message-ID: <18910.46709.707557.135033@stoffel.org> (raw)
In-Reply-To: <20090408232344.afed8103.zaitcev@redhat.com>


Ok, I've confirmed that it's usbmon under 2.6.29.1 on x86_64 which causes
complete system lockups when doing 'tcpdump host ##.##.##.##'.  I
compiled usbmon as a module, started a tcpdump and couldn't get a
crash. 

Loaded the module with tcpdump still going, no problems.  Stop and
restart tcpdump, bang!  Instant hang.  I'm now building 2.6.28 to see
if that works properly or not.  I suspect I might have to go back
farther, but I'm not sure.

Any suggestions of a known good state I should start bisection from?

Thanks,
John

  parent reply	other threads:[~2009-04-10  3:02 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
2009-04-17  3:00                 ` John Stoffel
2009-04-17 18:09                   ` Pete Zaitcev
2009-04-10  3:01           ` John Stoffel [this message]
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=18910.46709.707557.135033@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).