From: "Andreas Lillebø Holm" <andreas@sqhead.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
linux-input <linux-input@vger.kernel.org>
Subject: Re: kernel Oops: 0003 on usbhid_submit_report
Date: Mon, 26 Aug 2013 18:16:11 +0200 [thread overview]
Message-ID: <7851429DDA1F498899F023F32CC33483@sqhead.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1308231447440.11021@pobox.suse.cz>
On Friday, August 23, 2013 at 2:49 PM, Jiri Kosina wrote:
> On Fri, 23 Aug 2013, Benjamin Tissoires wrote:
>
> > IIRC, Jiri fixed some paging requests with the two following patches:
> > http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-next&id=27ce405039bfe6d3f4143415c638f56a3df77dca
> > http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-next&id=bc197eedef1ae082ec662c64c3f4aa302821fb7a
> >
> > At least, these two patches are related to hid_output_report(). I
> > think they are scheduled for 3.12, so I can not find them in Linus'
> > tree.
> >
> > It would worth trying them :)
>
> All three reported oopses happened on page boundary exactly, so this
> pretty much looks like my implement() fix is the one.
>
> Andreas, could you please apply
>
> http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-next&id=27ce405039bfe6d3f4143415c638f56a3df77dca
>
> and report back whether it makes your problem go away?
Hi,
You are my hero Jiri :-) These two patches fixes the issues I was seeing and I can no longer reproduce them.
I have only tried them on one hardware platform yet; the one that I had failing: Atom Intel e6xx CPU with EG20T PCH platform controller. I have had approximately 300 boots in our test rigg now and no fails yet. Before was the failrate 1/25 boots.
I made the kernel based on 3.10.9 stable tag and applied them directly on there. I do recommend that these patches makes it way into the stable tree :-)
Thanks again :)
Best regards
Andreas Lillebø Holm
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-26 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9921350AD19C46EFA70EA181A0C1F7E9@sqhead.com>
2013-08-13 18:40 ` kernel Oops: 0003 on usbhid_submit_report Greg KH
2013-08-14 13:38 ` Andreas Lillebø Holm
2013-08-15 6:37 ` Greg KH
[not found] ` <20130815063736.GF25754-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-23 10:52 ` Andreas Lillebø Holm
[not found] ` <26E21BF00B944AB6B8F48B5E59B0442D-nr7O5T6ryCTQT0dZR+AlfA@public.gmane.org>
2013-08-23 12:32 ` Benjamin Tissoires
[not found] ` <CAN+gG=FJSMyQNHcq=0cO1srVpRb_83YihUH0WuAPTcKAJHhv4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-23 12:49 ` Jiri Kosina
2013-08-23 12:51 ` Andreas Lillebø Holm
2013-08-26 16:16 ` Andreas Lillebø Holm [this message]
[not found] ` <7851429DDA1F498899F023F32CC33483-nr7O5T6ryCTQT0dZR+AlfA@public.gmane.org>
2013-08-28 12:42 ` Jiri Kosina
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=7851429DDA1F498899F023F32CC33483@sqhead.com \
--to=andreas@sqhead.com \
--cc=benjamin.tissoires@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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