From: Pete Zaitcev <zaitcev@redhat.com>
To: David <david@unsolicited.net>
Cc: Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dbrownell@users.sourceforge.net, leonidv11@gmail.com,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
zaitcev@redhat.com
Subject: Re: USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down
Date: Mon, 25 May 2009 18:48:43 -0600 [thread overview]
Message-ID: <20090525184843.33c93006.zaitcev@redhat.com> (raw)
In-Reply-To: <4A1A8E53.9060108@unsolicited.net>
On Mon, 25 May 2009 13:25:55 +0100, David <david@unsolicited.net> wrote:
> >> I wonder if CONFIG_HAVE_DMA_API_DEBUG does it (enabled with a select
> >> in arch/x86/Kconfig). Strange that it started happening now.
> >>
> > That is enabled. I'll switch it off and give it another go.
> >
> While CONFIG_HAVE_DMA_API_DEBUG was set, DMA_API_DEBUG was not, so I
> guess there's nothing I can do to test?
I suppose so. I misunderstood how this worked. I guessed that the
DMA API debugging was the culprit because its introduction coincided
with the recent onset of this oops.
Although usbmon does essentially illegal tricks to look at data
already mapped for DMA, the code used to work for a few releases.
Bisecting may help. I cannot be sure of it though, and it's
going to take a lot of reboots.
Unfortunately, although I have an Opteron, the issue does not
occur here, so I'm at a loss for the moment. But I'll have to
tackle it somehow. Not sure how though. Any suggestions are welcome.
-- Pete
next prev parent reply other threads:[~2009-05-26 0:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 21:32 USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down David
2009-05-22 21:45 ` David
2009-05-23 8:25 ` Pekka Enberg
2009-05-23 15:15 ` Alan Stern
2009-05-23 18:20 ` David
2009-05-23 19:22 ` David
2009-05-23 21:02 ` Alan Stern
2009-05-24 0:15 ` David
2009-05-24 0:54 ` hermann pitton
2009-05-24 8:35 ` David
2009-05-24 14:33 ` Alan Stern
2009-05-24 15:28 ` David
2009-05-25 2:10 ` Alan Stern
2009-05-25 2:39 ` Pete Zaitcev
2009-05-25 9:00 ` David
2009-05-25 12:25 ` David
2009-05-26 0:48 ` Pete Zaitcev [this message]
2009-05-26 14:08 ` Alan Stern
2009-05-26 18:42 ` David
2009-05-26 19:01 ` Pete Zaitcev
2009-05-24 15:16 ` Alan Stern
2009-05-25 15:23 ` Alan Stern
2009-05-25 17:32 ` David
2009-05-25 18:44 ` David
2009-05-25 21:12 ` Alan Stern
2009-05-26 20:57 ` Alan Stern
2009-05-27 18:42 ` David
2009-05-27 20:20 ` Alan Stern
2009-05-27 21:28 ` David
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=20090525184843.33c93006.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@unsolicited.net \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=leonidv11@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--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