From: Sean <knife@toaster.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-media@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Bugme-new] [Bug 14564] New: capture-example sleeping function called from invalid context at arch/x86/mm/fault.c
Date: Sat, 02 Jan 2010 17:56:56 -0800 [thread overview]
Message-ID: <4B3FF968.6000706@toaster.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1001021511320.9114-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Alan Stern wrote:
> In other words, I'm guessing that you're suffering from hardware memory
> errors. A possible way to test this is to modify the patch. In
> td_free() where it adds the line:
>
> + ohci_dbg(hc, "(%d %d) %p -> %p\n", hash, n, prev, *prev);
>
> instead add this code:
>
> + barrier();
> + ohci_dbg(hc, "(%d %d) %p -> %p [%p]\n", hash, n,
> + prev, *prev, td->td_hash);
>
> If we find that the value of *prev differs from the value of
> td->td_hash then we'll know for certain. (Or maybe the presence of the
> barrier() will cause the object code to change in a way that prevents
> the error from occurring.)
>
> Alan Stern
>
Hmm, I applied the changes and I did not see a place where *prev differs
from td->td_hash. I have run memtest86+ on this box and it has passed 16
times, so I do not suspect a hardware memory error. What do you think?
Attached is the latest dmesg output.
Sean
[-- Attachment #2: dmesg3.log.tar.gz --]
[-- Type: application/x-tar, Size: 36691 bytes --]
next prev parent reply other threads:[~2010-01-03 1:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14564-10286@http.bugzilla.kernel.org/>
2009-11-11 23:21 ` [Bugme-new] [Bug 14564] New: capture-example sleeping function called from invalid context at arch/x86/mm/fault.c Andrew Morton
2009-11-12 16:20 ` Alan Stern
2009-12-03 5:48 ` Sean
2009-12-03 21:03 ` Alan Stern
2009-12-16 23:30 ` Sean
2009-12-17 15:22 ` Alan Stern
2009-12-29 9:19 ` Sean
2009-12-29 19:48 ` Sean
2009-12-29 21:23 ` Alan Stern
2009-12-30 0:37 ` Sean
2009-12-30 3:22 ` Alan Stern
2010-01-02 9:00 ` Sean
2010-01-02 20:43 ` Alan Stern
2010-01-03 1:56 ` Sean [this message]
2010-01-03 17:35 ` Alan Stern
2010-01-03 23:47 ` Sean
2010-01-04 16:06 ` Alan Stern
2010-01-04 20:02 ` Sean
2010-01-04 20:48 ` Alan Stern
2010-01-04 22:24 ` Sean
2010-01-05 2:40 ` Alan Stern
2010-01-05 3:32 ` Sean
2010-01-05 15:11 ` Alan Stern
2010-01-05 20:05 ` Sean
2010-01-05 21:06 ` Alan Stern
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=4B3FF968.6000706@toaster.net \
--to=knife@toaster.net \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.