I understand this bug existed not much prior to the present kernel version from what I read on the [email protected] mailing list so this bug was carried into this kernel version from at least one earlier version. On Sat, 25 Jan 2014, Paul Gevers wrote:
> On 24-01-14 22:24, Jude DaShiell wrote: > > jude@d-216-36-20-9:~$ uname -a > > Linux d-216-36-20-9 3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 > > GNU/Linux > > I am fully guessing here, but my hypothesis is that the bug is caused by > the "new" kernel version scheme, which dropped the patch version, ie. > 3.12 i.s.o 3.12.0. I don't know where this would come into play though. > > Paul > > > jude <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
