mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
	USB list <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.36-rc7: NULL pointer dereference in ehci_clear_tt_buffer_complete
Date: Sun, 24 Oct 2010 13:49:53 +0200	[thread overview]
Message-ID: <4CC41D61.7020303@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1010191049440.1786-100000@iolanthe.rowland.org>

Alan Stern wrote:
> Okay, here's a patch which definitely causes the problem to surface.  
> It contains some extra debugging printouts but you can ignore them.  Or 
> you can edit out the hunks that affect ehci-q.c.
> 
> Ideally, you would test this while forcing the card reader to run at
> full speed, by putting a USB-1.1 hub between the monitor and the card
> reader.  But if you don't have one available, don't worry -- the error
> message should still appear even though it won't lead to an oops.
> 
> And of course, when you run this along with the proposed fix, the error 
> message should go away.  :-)

Thanks, I will try it RSN, hopefully one of the next few days.
-- 
Stefan Richter
-=====-==-=- =-=- ==---
http://arcgraph.de/sr/

      reply	other threads:[~2010-10-24 11:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 20:56 Stefan Richter
2010-10-12 18:23 ` Alan Stern
2010-10-13 14:23 ` Alan Stern
2010-10-13 22:42   ` Stefan Richter
2010-10-14 14:25     ` Alan Stern
2010-10-16 19:44       ` Stefan Richter
2010-10-16 20:05         ` Alan Stern
2010-10-16 20:35           ` Stefan Richter
2010-10-17 13:50             ` Alan Stern
2010-10-19 14:54               ` Alan Stern
2010-10-24 11:49                 ` Stefan Richter [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=4CC41D61.7020303@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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®