Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-05 Thread Lukas Wunner
On Tue, Jul 05, 2016 at 11:00:21AM +0800, AceLan Kao wrote: > These are logs from my machine. > > *** Before plug-in the USB key > > u@u-XPS-13-9xxx:~$ sudo lspci - -s 00:1c.0 > 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) (prog-if 00 > [Normal decode]) [...] > L

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread AceLan Kao
Hi, These are logs from my machine. *** Before plug-in the USB key u@u-XPS-13-9xxx:~$ sudo lspci - -s 00:1c.0 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- Fa

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Mathias Nyman
On 04.07.2016 18:21, Lukas Wunner wrote: On Mon, Jul 04, 2016 at 06:04:42PM +0300, Mathias Nyman wrote: On 04.07.2016 17:25, Rafael J. Wysocki wrote: On Mon, Jul 4, 2016 at 4:26 PM, Mathias Nyman wrote: AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging a USB 3.1 key v

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Lukas Wunner
On Mon, Jul 04, 2016 at 06:04:42PM +0300, Mathias Nyman wrote: > On 04.07.2016 17:25, Rafael J. Wysocki wrote: > > On Mon, Jul 4, 2016 at 4:26 PM, Mathias Nyman > > wrote: > > > AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging > > > a USB 3.1 key via thunderbolt port. > >

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Mathias Nyman
On 04.07.2016 17:25, Rafael J. Wysocki wrote: On Mon, Jul 4, 2016 at 4:26 PM, Mathias Nyman wrote: Hi AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging a USB 3.1 key via thunderbolt port. Allocating memory fails after this, always pointing to NULL pointer or page reque

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Rafael J. Wysocki
On Mon, Jul 4, 2016 at 4:26 PM, Mathias Nyman wrote: > Hi > > AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging > a USB 3.1 key via thunderbolt port. > > Allocating memory fails after this, always pointing to NULL pointer or > page request failing in get_freepointer() calle

kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Mathias Nyman
Hi AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging a USB 3.1 key via thunderbolt port. Allocating memory fails after this, always pointing to NULL pointer or page request failing in get_freepointer() called by kmalloc/kmem_cache_alloc. Unplugging a usb type-c device fr

unable to handle paging request, arm, at aio/tcp code, only 3.6

2012-11-18 Thread Lluís Batlle i Rossell
Hello, in a Sheevaplug, if I run the kernels 3.6.3 or 3.6.6, they crash in less than 48h. Kernel 3.5.3 runs perfect, as most previous kernels I've been running. Can anyone suggest what change can be the cause of that? Or how could I debug this to fix it? Here is the panic: unable to handle kern

Re: unable to handle paging request in worker_thread on apm resume

2005-03-23 Thread Andrew Morton
"J. Bruce Fields" <[EMAIL PROTECTED]> wrote: > > > Have you added any code which does schedule_work()? > > Hm, I don't think so. But of course I have some nfsv4 patches, and the > nfsv4 nfsd code does use schedule_delayed_work(). It's possible the > cleanup is wrong, and that bringing nfsd up

Re: unable to handle paging request in worker_thread on apm resume

2005-03-23 Thread J. Bruce Fields
On Wed, Mar 23, 2005 at 02:33:44AM -0800, Andrew Morton wrote: > Seems that there's a `struct work_struct' which is still registered but its > memory has been freed. It's likely that CONFIG_DEBUG_PAGEALLOC caught this. > > Either that, or some module got unloaded without flushing its workqueue. >

Re: unable to handle paging request in worker_thread on apm resume

2005-03-23 Thread Andrew Morton
"J. Bruce Fields" <[EMAIL PROTECTED]> wrote: > > I got the following after an apm resume on a thinkpad X31, with > 2.6.12-rc1 plus some (hopefully unrelated) NFS patches. Any ideas? > > --Bruce Fields > > > Mar 21 18:22:44 puzzle apmd[1815]: Suspending now > Mar 21 22:37:36 puzzle kernel: P

unable to handle paging request in worker_thread on apm resume

2005-03-21 Thread J. Bruce Fields
I got the following after an apm resume on a thinkpad X31, with 2.6.12-rc1 plus some (hopefully unrelated) NFS patches. Any ideas? --Bruce Fields Mar 21 18:22:44 puzzle apmd[1815]: Suspending now Mar 21 22:37:36 puzzle kernel: PCI: Setting latency timer of device :00:1d.0 to 64 Mar 21 22:3

Re: "unable to handle paging request..."

2000-11-17 Thread aprasad
but EVERY TIME shut my machine down, I always get the following message, just after >the line "stopping all md devices": I also used to get the same messages on my celeron machine, but after i disabled the support of RAID in kernel, it started working nicely. I don't know the reason. regards, Ani

"unable to handle paging request..."

2000-11-17 Thread Sebastien . Rigaud
Hello, I found that it's possible to submit you error messages and ask for help... I've installed Red Hat 6.2 on an AMD300, without problem. Everything works fine (Oracle server, Java developments...), but EVERY TIME I shut my machine down, I always get the following message, just after the line "