Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1507725
| From | Andrey Utkin <andrey_utkin@fastmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression) |
| Date | 2016-10-24 23:00 +0200 |
| Message-ID | <svUvE-4ir-15@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <slVjj-6IZ-3@gated-at.bofh.it> <slYTU-wK-63@gated-at.bofh.it> <sm1yq-29m-13@gated-at.bofh.it> <smfBo-2E2-3@gated-at.bofh.it> <svTge-3ya-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Oct 24, 2016 at 05:32:33PM -0200, Mauro Carvalho Chehab wrote: > Em Wed, 28 Sep 2016 07:21:44 +0200 > khalasa@piap.pl (Krzysztof HaĆasa) escreveu: > > > Andrey Utkin <andrey_utkin@fastmail.com> writes: > > > > > Lockup happens only on 6010. In provided log you can see that 6110 > > > passes just fine right before 6010. Also if 6010 PCI ID is removed from > > > solo6x10 driver's devices list, the freeze doesn't happen. > > > > Probably explains why I don't see lockups :-) > > > > I will have a look. > > Any news on this? Should the patch be applied or not? If not, are there > any other patch to fix this regression? Actual patch is Subject: [PATCH v2] media: solo6x10: fix lockup by avoiding delayed register write Message-Id: <20161022153436.12076-1-andrey.utkin@corp.bluecherry.net> Date: Sat, 22 Oct 2016 16:34:36 +0100
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression) Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2016-10-24 21:40 +0200 Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression) Andrey Utkin <andrey_utkin@fastmail.com> - 2016-10-24 23:00 +0200
csiph-web