Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
On Fri 2017-02-03 08:30:48, Tony Lindgren wrote: > * Pavel Machek[170203 00:00]: > > Hi! > > > > > On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > > > > 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. > > > > > > Talking about testing - kernelci's n900 is broken? > > > > > > https://kernelci.org/boot/omap3-n900/ > > > > The N900 regressions are now more of "audio mixers no longer work" > > than "it fails to boot" kind -- thus difficult to test automatically, > > I'm afraid. > > Talking about audio testing, next now has commit 9834ffd1ecc3 > ("ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches"), > care to check if that also fixes the n900 audio glitch issues you > reported earlier? Yes, audio was choppy when I tried to use n900 as an mp3 player. Hmm. I re-checked v4.9, and it seems to work ok now. I'll speak up if it re-appears. Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
* Pavel Machek[170203 00:00]: > Hi! > > > On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > > > 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. > > > > Talking about testing - kernelci's n900 is broken? > > > > https://kernelci.org/boot/omap3-n900/ > > The N900 regressions are now more of "audio mixers no longer work" > than "it fails to boot" kind -- thus difficult to test automatically, > I'm afraid. Talking about audio testing, next now has commit 9834ffd1ecc3 ("ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches"), care to check if that also fixes the n900 audio glitch issues you reported earlier? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Hi! > On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > > 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. > > Talking about testing - kernelci's n900 is broken? > > https://kernelci.org/boot/omap3-n900/ The N900 regressions are now more of "audio mixers no longer work" than "it fails to boot" kind -- thus difficult to test automatically, I'm afraid. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Hi, On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > 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. Talking about testing - kernelci's n900 is broken? https://kernelci.org/boot/omap3-n900/ -- Sebastian signature.asc Description: PGP signature
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
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 signature.asc Description: Digital signature
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
* Pali Rohár[170124 02:02]: > On Tuesday 24 January 2017 10:18:17 Pavel Machek wrote: > > Hi! > > On Mon 2017-01-23 14:44:54, Tony Lindgren wrote: > > > * Pavel Machek [170123 14:26]: > > > > [25392.239837] Unhandled fault: external abort on non-linefetch > > > > (0x1028) at 0xfa0ab060 > > > > [25392.239868] pgd = c0004000 > > > > [25392.239898] [fa0ab060] *pgd=48011452(bad) > > > > [25392.239929] Internal error: : 1028 [#1] ARM > > > > [25392.239929] Modules linked in: > > > > [25392.239959] CPU: 0 PID: 24322 Comm: kworker/0:1 Not tainted > > > > 4.10.0-rc5-142127-g41f2839-dirty #222 > > > > [25392.239990] Hardware name: Nokia RX-51 board > > > > [25392.240020] Workqueue: events musb_irq_work > > > > [25392.240051] task: cd44d5c0 task.stack: cd308000 > > > > [25392.240051] PC is at musb_default_readb+0x0/0xc > > > > [25392.240081] LR is at musb_irq_work+0x1c/0x1b0 > > > > > > OK I'm pretty sure the patch I posted few days ago fixes > > > this. Can you please test patch "[PATCH] usb: musb: Fix > > > external abort on non-linefetch for musb_irq_work()"? > > > > 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. > Another place when caller of pm_runtime_get_sync forgot to check return > value? This is not first time I see this problem related to Nokia N900! No that's a completely missing pm_runtime_get on this one that's the most likely cause. > In past I already suggested to use gcc attribute for pm_runtime_get_sync > to issue warning when caller does not check return value. Yeah that would be nice, needs all the missing use cases fixed first though.. > > > 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 :) 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. 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. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
On Tuesday 24 January 2017 10:18:17 Pavel Machek wrote: > Hi! > On Mon 2017-01-23 14:44:54, Tony Lindgren wrote: > > * Pavel Machek[170123 14:26]: > > > [25392.239837] Unhandled fault: external abort on non-linefetch (0x1028) > > > at 0xfa0ab060 > > > [25392.239868] pgd = c0004000 > > > [25392.239898] [fa0ab060] *pgd=48011452(bad) > > > [25392.239929] Internal error: : 1028 [#1] ARM > > > [25392.239929] Modules linked in: > > > [25392.239959] CPU: 0 PID: 24322 Comm: kworker/0:1 Not tainted > > > 4.10.0-rc5-142127-g41f2839-dirty #222 > > > [25392.239990] Hardware name: Nokia RX-51 board > > > [25392.240020] Workqueue: events musb_irq_work > > > [25392.240051] task: cd44d5c0 task.stack: cd308000 > > > [25392.240051] PC is at musb_default_readb+0x0/0xc > > > [25392.240081] LR is at musb_irq_work+0x1c/0x1b0 > > > > OK I'm pretty sure the patch I posted few days ago fixes > > this. Can you please test patch "[PATCH] usb: musb: Fix > > external abort on non-linefetch for musb_irq_work()"? > > 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. Another place when caller of pm_runtime_get_sync forgot to check return value? This is not first time I see this problem related to Nokia N900! In past I already suggested to use gcc attribute for pm_runtime_get_sync to issue warning when caller does not check return value. > > 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 :-(. -- Pali Rohár pali.ro...@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
Hi! On Mon 2017-01-23 14:44:54, Tony Lindgren wrote: > * Pavel Machek[170123 14:26]: > > [25392.239837] Unhandled fault: external abort on non-linefetch (0x1028) at > > 0xfa0ab060 > > [25392.239868] pgd = c0004000 > > [25392.239898] [fa0ab060] *pgd=48011452(bad) > > [25392.239929] Internal error: : 1028 [#1] ARM > > [25392.239929] Modules linked in: > > [25392.239959] CPU: 0 PID: 24322 Comm: kworker/0:1 Not tainted > > 4.10.0-rc5-142127-g41f2839-dirty #222 > > [25392.239990] Hardware name: Nokia RX-51 board > > [25392.240020] Workqueue: events musb_irq_work > > [25392.240051] task: cd44d5c0 task.stack: cd308000 > > [25392.240051] PC is at musb_default_readb+0x0/0xc > > [25392.240081] LR is at musb_irq_work+0x1c/0x1b0 > > OK I'm pretty sure the patch I posted few days ago fixes > this. Can you please test patch "[PATCH] usb: musb: Fix > external abort on non-linefetch for musb_irq_work()"? 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. > 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 :-(. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.
* Pavel Machek[170123 14:26]: > [25392.239837] Unhandled fault: external abort on non-linefetch (0x1028) at > 0xfa0ab060 > [25392.239868] pgd = c0004000 > [25392.239898] [fa0ab060] *pgd=48011452(bad) > [25392.239929] Internal error: : 1028 [#1] ARM > [25392.239929] Modules linked in: > [25392.239959] CPU: 0 PID: 24322 Comm: kworker/0:1 Not tainted > 4.10.0-rc5-142127-g41f2839-dirty #222 > [25392.239990] Hardware name: Nokia RX-51 board > [25392.240020] Workqueue: events musb_irq_work > [25392.240051] task: cd44d5c0 task.stack: cd308000 > [25392.240051] PC is at musb_default_readb+0x0/0xc > [25392.240081] LR is at musb_irq_work+0x1c/0x1b0 OK I'm pretty sure the patch I posted few days ago fixes this. Can you please test patch "[PATCH] usb: musb: Fix external abort on non-linefetch for musb_irq_work()"? I was able to hit that only once so far, do you hit it every time with your built-in g_ether .config? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html