Bug#859779: BUG: unable to handle kernel paging request at 6f697468

2017-04-07 Thread Leo Weppelman
Package: linux-source-3.16 Version: 3.16.7-ckt20-1+deb8u4 Severity: important Tags: upstream Dear Maintainer, We are running this system under KVM. The KVM host is running: 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 The client is running: 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt20-1+deb

Bug#859779: BUG: unable to handle kernel paging request at 6f697468

2017-04-07 Thread Ben Hutchings
Control: tag -1 moreinfo On Fri, 2017-04-07 at 13:47 +0200, Leo Weppelman wrote: > Package: linux-source-3.16 > Version: 3.16.7-ckt20-1+deb8u4 > Severity: important > Tags: upstream > > Dear Maintainer, > > We are running this system under KVM. The KVM host is running: >   3.16.0-4-amd64 #1 SMP

Bug#859779: BUG: unable to handle kernel paging request at 6f697468

2017-05-17 Thread leo weppelman
Just to add a data point: I upgraded 60 clients (to: linux-image-3.16.0-4-amd64 3.16.39-1+deb8u2) and they are running OK for 2 weeks now. So things are looking good! Leo. On Fri, Apr 7, 2017 at 7:03 PM, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Fri, 2017-04-07 at 13:47 +0200, Le

Bug#859779: BUG: unable to handle kernel paging request at 6f697468

2017-05-24 Thread leo weppelman
I got 2 kernel panics today, from one of them I have a stack trace. To me it looks quite simular :-( Both the host and the client are now on: 3.16.0-4-amd64 #1 Debian 3.16.39-1+deb8u2 So unfortunately, I am back where I started :-( The backtrace: general protection fault: [#1] SMP [1908184.65