Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

2016-04-06 Thread Bjørn Mork
Ben Hutchings writes: > On Wed, 2016-04-06 at 16:51 +0200, Bjørn Mork wrote: >> Antonis Christofides writes: >> >> > >> > Apr  5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel >> > paging request at eba40a800380 >> > Apr  5 13:32:47 thames kernel: [86003.994005] IP: []

Processed: Re: Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

2016-04-06 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #820176 [src:linux] 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device) Bug 820176 cloned as bug 820211 > retitle -2 [Regression] QuickPort XT USB3.0 in EHCI port is disconnected > during disk spin-up Bug #8202

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

2016-04-06 Thread Ben Hutchings
Control: clone -1 -2 Control: retitle -2 [Regression] QuickPort XT USB3.0 in EHCI port is disconnected during disk spin-up On Wed, 2016-04-06 at 16:51 +0200, Bjørn Mork wrote: > Antonis Christofides writes: > > > > > Apr  5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel >

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

2016-04-06 Thread Bjørn Mork
Antonis Christofides writes: > Apr 5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel > paging request at eba40a800380 > Apr 5 13:32:47 thames kernel: [86003.994005] IP: [] > kfree+0x76/0x220 .. > Apr 5 13:32:47 thames kernel: [86003.994679] Call Trace: > Apr 5 13:32:

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

2016-04-06 Thread Antonis Christofides
Package: src:linux Version: 3.16.7-ckt25-1 Severity: important Dear Maintainer, I bought a new USB hard disk dock and connected it, and the system mostly crashed. It actually wrote some stuff in the log, which I include below, and continued to work, then I tried to restart it and something went