From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: ivo.g.dimitrov.75@gmail.com, khilman@kernel.org,
aaro.koskinen@iki.fi,
"kernel list" <linux-kernel@vger.kernel.org>,
sre@kernel.org, b-liu@ti.com, linux-usb@vger.kernel.org,
abcloriens@gmail.com, "Pali Rohár" <pali.rohar@gmail.com>,
linux-omap@vger.kernel.org, patrikbachan@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
serge@hallyn.com
Subject: Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Date: Fri, 27 Jan 2017 22:55:12 +0100 [thread overview]
Message-ID: <20170127215512.GG20571@amd> (raw)
In-Reply-To: <20170124145127.GC7403@atomide.com>
[-- Attachment #1.1: Type: text/plain, Size: 1929 bytes --]
Hi!
> > > Can I get the copy of the patch?
> > >
> > > http://www.spinics.net/lists/linux-usb/msg152542.html
> > >
> > > ...but it is html mangled with no obvious way to unmangle it.
>
> Bounced it to you. FYI, patchwork.kernel.org should have it too, the
> "mbox" option there works the best.
Thanks, applied. Problem did not reappear so far.
> > > > I was able to hit that only once so far, do you hit it
> > > > every time with your built-in g_ether .config?
> > >
> > > I get it "way too often", like once a day. I don't yet know how to hit
> > > it reliably :-(.
>
> OK, well let's hope the patch linked above fixes it. At some point the
> number of musb fixes should just start going down if I'm predicting right :)
Fingers crossed :-).
> Anyways, hitting these issues during late -rc cycle is too late. We
> really should have some n900 usability testing for core features with
> Linux next on at least weekly basis.
Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider
phone calls core feature of a phone. I'd very much like to get that to
work. Unfortunately, that means real-time audio, and a lot of
fun. Plus, as it is touchscreen device, it needs a GUI.
> I've noticed that testing with Linux next is way less effort than chasing
> bugs every -rc cycle when it's too late. For about past four months or so
> next has been usable for me with only occasional minor issues that get
> fixed within a day or two.
Well, I am carrying some patches... but maybe mainline is now good
enough to be useable without them?
No promises. I really should find more time for N900
development. Hmm. Or more developers. Where are all those Eudyptula
Challenge people when you need them?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Date: Fri, 27 Jan 2017 22:55:12 +0100 [thread overview]
Message-ID: <20170127215512.GG20571@amd> (raw)
In-Reply-To: <20170124145127.GC7403@atomide.com>
Hi!
> > > Can I get the copy of the patch?
> > >
> > > http://www.spinics.net/lists/linux-usb/msg152542.html
> > >
> > > ...but it is html mangled with no obvious way to unmangle it.
>
> Bounced it to you. FYI, patchwork.kernel.org should have it too, the
> "mbox" option there works the best.
Thanks, applied. Problem did not reappear so far.
> > > > I was able to hit that only once so far, do you hit it
> > > > every time with your built-in g_ether .config?
> > >
> > > I get it "way too often", like once a day. I don't yet know how to hit
> > > it reliably :-(.
>
> OK, well let's hope the patch linked above fixes it. At some point the
> number of musb fixes should just start going down if I'm predicting right :)
Fingers crossed :-).
> Anyways, hitting these issues during late -rc cycle is too late. We
> really should have some n900 usability testing for core features with
> Linux next on at least weekly basis.
Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider
phone calls core feature of a phone. I'd very much like to get that to
work. Unfortunately, that means real-time audio, and a lot of
fun. Plus, as it is touchscreen device, it needs a GUI.
> I've noticed that testing with Linux next is way less effort than chasing
> bugs every -rc cycle when it's too late. For about past four months or so
> next has been usable for me with only occasional minor issues that get
> fixed within a day or two.
Well, I am carrying some patches... but maybe mainline is now good
enough to be useable without them?
No promises. I really should find more time for N900
development. Hmm. Or more developers. Where are all those Eudyptula
Challenge people when you need them?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170127/a1c3359f/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
sre@kernel.org, "kernel list" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
b-liu@ti.com, linux-usb@vger.kernel.org
Subject: Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Date: Fri, 27 Jan 2017 22:55:12 +0100 [thread overview]
Message-ID: <20170127215512.GG20571@amd> (raw)
In-Reply-To: <20170124145127.GC7403@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
Hi!
> > > Can I get the copy of the patch?
> > >
> > > http://www.spinics.net/lists/linux-usb/msg152542.html
> > >
> > > ...but it is html mangled with no obvious way to unmangle it.
>
> Bounced it to you. FYI, patchwork.kernel.org should have it too, the
> "mbox" option there works the best.
Thanks, applied. Problem did not reappear so far.
> > > > I was able to hit that only once so far, do you hit it
> > > > every time with your built-in g_ether .config?
> > >
> > > I get it "way too often", like once a day. I don't yet know how to hit
> > > it reliably :-(.
>
> OK, well let's hope the patch linked above fixes it. At some point the
> number of musb fixes should just start going down if I'm predicting right :)
Fingers crossed :-).
> Anyways, hitting these issues during late -rc cycle is too late. We
> really should have some n900 usability testing for core features with
> Linux next on at least weekly basis.
Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider
phone calls core feature of a phone. I'd very much like to get that to
work. Unfortunately, that means real-time audio, and a lot of
fun. Plus, as it is touchscreen device, it needs a GUI.
> I've noticed that testing with Linux next is way less effort than chasing
> bugs every -rc cycle when it's too late. For about past four months or so
> next has been usable for me with only occasional minor issues that get
> fixed within a day or two.
Well, I am carrying some patches... but maybe mainline is now good
enough to be useable without them?
No promises. I really should find more time for N900
development. Hmm. Or more developers. Where are all those Eudyptula
Challenge people when you need them?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-01-27 21:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 22:25 v4.9 to v4.10 regression: oops when USB cable is plugged in Pavel Machek
2017-01-23 22:25 ` Pavel Machek
2017-01-23 22:25 ` Pavel Machek
2017-01-23 22:44 ` Tony Lindgren
2017-01-23 22:44 ` Tony Lindgren
2017-01-24 9:18 ` Pavel Machek
2017-01-24 9:18 ` Pavel Machek
2017-01-24 10:01 ` Pali Rohár
2017-01-24 10:01 ` Pali Rohár
2017-01-24 14:51 ` Tony Lindgren
2017-01-24 14:51 ` Tony Lindgren
2017-01-27 21:55 ` Pavel Machek [this message]
2017-01-27 21:55 ` Pavel Machek
2017-01-27 21:55 ` Pavel Machek
2017-01-27 23:48 ` Sebastian Reichel
2017-01-27 23:48 ` Sebastian Reichel
2017-02-03 7:59 ` Pavel Machek
2017-02-03 7:59 ` Pavel Machek
2017-02-03 16:30 ` Tony Lindgren
2017-02-03 16:30 ` Tony Lindgren
[not found] ` <20170203163048.GA3721-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-02-05 21:44 ` Pavel Machek
2017-02-05 21:44 ` Pavel Machek
2017-02-05 21:44 ` Pavel Machek
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=20170127215512.GG20571@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=b-liu@ti.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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 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.