Re: Linux 4.16 Kernel Boot Crash

2018-04-05 Thread Hans Verkuil
On 05/04/18 11:57, Mauro Carvalho Chehab wrote: > Em Wed, 4 Apr 2018 16:26:22 +0300 > Jaak Ristioja escreveu: > >> Hello, all! >> >> I experience the same issue with a Lenovo ThinkPad T440p (LENOVO >> 20AN006VMS/20AN006VMS, BIOS GLET90WW (2.44 ) 09/13/2017). I tried to >> bisect v4.15..v4.16 but

Re: Linux 4.16 Kernel Boot Crash

2018-04-05 Thread Mauro Carvalho Chehab
Em Thu, 5 Apr 2018 06:57:13 -0300 Mauro Carvalho Chehab escreveu: > Em Wed, 4 Apr 2018 16:26:22 +0300 > Jaak Ristioja escreveu: > > > Hello, all! > > > > I experience the same issue with a Lenovo ThinkPad T440p (LENOVO > > 20AN006VMS/20AN006VMS, BIOS GLET90WW (2.44 ) 09/13/2017). I tried to >

Re: Linux 4.16 Kernel Boot Crash

2018-04-05 Thread Mauro Carvalho Chehab
Em Wed, 4 Apr 2018 16:26:22 +0300 Jaak Ristioja escreveu: > Hello, all! > > I experience the same issue with a Lenovo ThinkPad T440p (LENOVO > 20AN006VMS/20AN006VMS, BIOS GLET90WW (2.44 ) 09/13/2017). I tried to > bisect v4.15..v4.16 but failed. > > Best regards, > J The real problem here is t

Re: Linux 4.16 Kernel Boot Crash

2018-04-04 Thread Mauro Carvalho Chehab
Em Wed, 4 Apr 2018 16:26:22 +0300 Jaak Ristioja escreveu: > Hello, all! > > I experience the same issue with a Lenovo ThinkPad T440p (LENOVO > 20AN006VMS/20AN006VMS, BIOS GLET90WW (2.44 ) 09/13/2017). I tried to > bisect v4.15..v4.16 but failed. Could you post the complete dmesg? I also need th

Re: Linux 4.16 Kernel Boot Crash

2018-04-04 Thread Peter Geis
Good Afternoon, I have been digging into this issue further, and the problem is definitely with the media driver. Rebuilt the kernel with media drivers compiled in vice modular and the kernel boots without issue. The core dump states the crash occurred at drivers/media/v4l2-core/v4l2-dev.c,

Re: Linux 4.16 Kernel Boot Crash

2018-04-04 Thread Jani Nikula
On Tue, 03 Apr 2018, Peter Geis wrote: > Good Evening, > > I have been trying to use the 4.16 kernel source since 4.16-rc3. > Every time it booted it crashed upon loading the video drivers. > Now with the 4.16 release, it is still occurring, so I felt it prudent > to notify someone. > > The machi