PANIC: double fault, RIP: 0010:acpi_idle_do_entry+0x15/0x30

131719] RIP: 0010:acpi_idle_do_entry+0x15/0x30 <4>[ 99.131725] Code: 66 90 fa 66 0f 1f 44 00 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 0f b6 47 08 3c 01 74 11 3c 02 74 12 8b 57 04 ec <48> 8b 15 d8 e2 f0 00 ed c3 e9 0d fc ff ff eb ab 90 90 90 90 90 90 <4>[ 99.131727] RSP: 0018: EFLAGS: 00010093 <4>[ 99.131730] RAX: RBX: RCX: <4>[ 99.131731] RDX: RSI: RDI: <4>[ 99.131733] RBP: R08: R09: 0006 <4>[ 99.131734] R10: fffdf701 R11: fffdf7018000 R12: <4>[ 99.131735] R13: R14: 9305 R15: Panic#1 Part1 <4>[ 99.131738] FS: () GS:9d740eac() knlGS: <4>[ 99.131740] CS: 0010 DS: ES: CR0: 80050033 <4>[ 99.131741] CR2: fff8 CR3: 00040181 CR4: 003406e0 <4>[ 99.131743] Call Trace: <0>[ 99.131745] Kernel panic - not syncing: Machine halted. <4>[ 99.131749] CPU: 3 PID: 0 Comm: swapper/3 Tainted: GE 5.0.0-trunk-amd64 #1 Debian 5.0.2-1~exp1 <4>[ 99.131751] Hardware name: Micro-Star International Co., Ltd. MS-7A34/B350 PC MATE (MS-7A34), BIOS A.J0 01/23/2019 <4>[ 99.131752] Call Trace: <4>[ 99.131756] <#DF> <4>[ 99.131763] dump_stack+0x5c/0x80 <4>[ 99.131770] panic+0x101/0x2a7 <4>[ 99.131775] df_debug+0x29/0x36 <4>[ 99.131779] do_double_fault+0xa7/0x120 <4>[ 99.131782] double_fault+0x1e/0x30 <4>[ 99.131786] RIP: 0010:acpi_idle_do_entry+0x15/0x30 <4>[ 99.131788] Code: 66 90 fa 66 0f 1f 44 00 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 0f b6 47 08 3c 01 74 11 3c 02 74 12 8b 57 04 ec <48> 8b 15 d8 e2 f0 00 ed c3 e9 0d fc ff ff eb ab 90 90 90 90 90 90 <4>[ 99.131790] RSP: 0018: EFLAGS: 00010093 <4>[ 99.131792] RAX: RBX: RCX: <4>[ 99.131794] RDX: RSI: RDI: <4>[ 99.131795] RBP: R08: R09: 0006 <4>[ 99.131797] R10: fffdf701 R11: fffdf7018000 R12: <4>[ 99.131798] R13: R14: 9305 R15: <4>[ 99.131802] <0>[ 99.131904] Kernel Offset: 0x2500 from 0x8100 (relocation range: 0x8000-0xbfff) Does this look like a kernel bug or am I experiencing a hardware problem? -- Frederik Himpe

cachefs: kernel BUG at fs/cachefiles/namei.c:197

t;48> 8b 40 d8 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f [2967555.389714] RIP [] kthread_data+0xc/0x20 [2967555.389715] RSP [2967555.389716] CR2: ffd8 [2967555.389718] ---[ end trace 80e48067b39ab6d8 ]--- [2967555.451116] Fixing recursive fault but reboot is needed!

cachefs: kernel BUG at fs/cachefiles/namei.c:197

t;48> 8b 40 d8 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f [2967555.389714] RIP [] kthread_data+0xc/0x20 [2967555.389715] RSP [2967555.389716] CR2: ffd8 [2967555.389718] ---[ end trace 80e48067b39ab6d8 ]--- [2967555.451116] Fixing recursive fault but reboot is needed! -- Frederik Himpe

Re: 3.5.0: BUG: Bad page state in process Compositor pfn:16834f

On za, 2016-04-16 at 16:29 -0400, Michal Hocko wrote: > On Sat 16-04-16 18:37:53, Frederik Himpe wrote: > > > >  > > Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state > > in process Compositor  pfn:16834f > > Apr 16 20:21

Re: 3.5.0: BUG: Bad page state in process Compositor pfn:16834f

On za, 2016-04-16 at 16:29 -0400, Michal Hocko wrote: > On Sat 16-04-16 18:37:53, Frederik Himpe wrote: > > > >  > > Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state > > in process Compositor  pfn:16834f > > Apr 16 20:21

3.5.0: BUG: Bad page state in process Compositor pfn:16834f

With Linux 3.5.0 I suddenly had Firefox which suddenly seemed to get stuck, and then I tried to kill it. I also noticed that the ps aux command was hanging. Then I found this in my kernel logs: Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state in process Compositor pfn:16834f

3.5.0: BUG: Bad page state in process Compositor pfn:16834f

With Linux 3.5.0 I suddenly had Firefox which suddenly seemed to get stuck, and then I tried to kill it. I also noticed that the ps aux command was hanging. Then I found this in my kernel logs: Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state in process Compositor pfn:16834f

Crash when resuming system (related to USB?) with 4.4

D 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 003 Device 004: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 003 Device 003: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 002: ID 0424:5434 Standard Microsystems Corp. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- Frederik Himpe <fhi...@vub.ac.be> Vrije Universiteit Brussel

Crash when resuming system (related to USB?) with 4.4

D 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 003 Device 004: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 003 Device 003: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 002: ID 0424:5434 Standard Microsystems Corp. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- Frederik Himpe Vrije Universiteit Brussel

Re: stable regression: tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -19

On za, 2013-12-14 at 09:24 -0200, Mauro Carvalho Chehab wrote: > Em Fri, 13 Dec 2013 22:19:39 +0100 > Frederik Himpe escreveu: > > > [My excuses for multiposting, it seems gmane does not permit posting to all > > the relevant lists] > > > > Since upgrading my

Re: stable regression: tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -19

On za, 2013-12-14 at 09:24 -0200, Mauro Carvalho Chehab wrote: Em Fri, 13 Dec 2013 22:19:39 +0100 Frederik Himpe fhi...@telenet.be escreveu: [My excuses for multiposting, it seems gmane does not permit posting to all the relevant lists] Since upgrading my system from Linux 3.12

stable regression: tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -19

to tda18271. Could this be the culprit? -- Frederik Himpe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

stable regression: tda18271_read_regs: [1-0060|M] ERROR: i2c_transfer returned: -19

to tda18271. Could this be the culprit? -- Frederik Himpe -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] pci: do not try to assign irq 255

s with MSI interrupts only > > (like the xhci device on certain HP laptops) work properly. > > > > Cc: Frederik Himpe > > Cc: Oliver Neukum > > Cc: David Haerdeman > > Cc: linux-...@vger.kernel.org > > Cc: linux-...@vger.kernel.org > > Signed-off-

Re: [PATCH] pci: do not try to assign irq 255

) work properly. Cc: Frederik Himpe fhi...@vub.ac.be Cc: Oliver Neukum oneu...@suse.de Cc: David Haerdeman da...@hardeman.nu Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org Signed-off-by: Hannes Reinecke h...@suse.de diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c

xhci module fails when booting in UEFI mode

the same problem on a HP Probook system: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072918 -- Frederik Himpe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.

xhci module fails when booting in UEFI mode

the same problem on a HP Probook system: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072918 -- Frederik Himpe -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org

Re: 3.7-rc2: corrupted image on Radeon HD 7800 after restarting X

On Mon, 2012-10-29 at 11:40 +0100, Michel Dänzer wrote: > On Fre, 2012-10-26 at 19:15 +0000, Frederik Himpe wrote: > > When I restart my display manager (GDM) from tty0, I get a corrupted > > image where parts of the X display before I restarted GDM become visible > > on b

Re: 3.7-rc2: corrupted image on Radeon HD 7800 after restarting X

On Mon, 2012-10-29 at 11:40 +0100, Michel Dänzer wrote: On Fre, 2012-10-26 at 19:15 +, Frederik Himpe wrote: When I restart my display manager (GDM) from tty0, I get a corrupted image where parts of the X display before I restarted GDM become visible on both the newly started X

Re: 2.6.24 regression: pan hanging unkilleable and un-straceable

On ma, 2008-01-28 at 12:46 +1100, Nick Piggin wrote: > On Sunday 27 January 2008 00:29, Frederik Himpe wrote: > > On di, 2008-01-22 at 16:25 +1100, Nick Piggin wrote: > > > > > On Tuesday 22 January 2008 07:58, Frederik Himpe wrote: > > > > > > With

Re: 2.6.24 regression: pan hanging unkilleable and un-straceable

On ma, 2008-01-28 at 12:46 +1100, Nick Piggin wrote: On Sunday 27 January 2008 00:29, Frederik Himpe wrote: On di, 2008-01-22 at 16:25 +1100, Nick Piggin wrote: On Tuesday 22 January 2008 07:58, Frederik Himpe wrote: With Linux 2.6.24-rc8 I often have the problem that the pan usenet

Udev coldplugging loads 8139too driver instead of 8139cp

Linux 2.6.24 kernel gives the following messages when udev coldplugging loads the driver for my NIC: 8139too :00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip 8139too :00:0b.0: Use the "8139cp" driver for improved performance and stability. ACPI: PCI Interrupt Link [LNK1]

Re: 2.6.24 regression: pan hanging unkilleable and un-straceable

On ma, 2008-01-28 at 12:46 +1100, Nick Piggin wrote: > On Sunday 27 January 2008 00:29, Frederik Himpe wrote: > > On di, 2008-01-22 at 16:25 +1100, Nick Piggin wrote: > > > > > On Tuesday 22 January 2008 07:58, Frederik Himpe wrote: > > > > > > With

Udev coldplugging loads 8139too driver instead of 8139cp

-Enable- DSel=0 DScale=0 PME- Kernel driver in use: 8139too Kernel modules: 8139cp, 8139too Why does not udev coldpluggin first try to load 8139cp instead of 8139too? -- Frederik Himpe [EMAIL PROTECTED] -- To unsubscribe from this list: send the line unsubscribe linux-kernel

Re: 2.6.24 regression: pan hanging unkilleable and un-straceable

On ma, 2008-01-28 at 12:46 +1100, Nick Piggin wrote: On Sunday 27 January 2008 00:29, Frederik Himpe wrote: On di, 2008-01-22 at 16:25 +1100, Nick Piggin wrote: On Tuesday 22 January 2008 07:58, Frederik Himpe wrote: With Linux 2.6.24-rc8 I often have the problem that the pan usenet

Re: 2.6.24 regression: pan hanging unkilleable and un-straceable

On di, 2008-01-22 at 16:25 +1100, Nick Piggin wrote: > > > On Tuesday 22 January 2008 07:58, Frederik Himpe wrote: > > > > With Linux 2.6.24-rc8 I often have the problem that the pan usenet > > > > reader starts using 100% of CPU time after some time. When t

2.6.24 regression: pan hanging unkilleable and un-straceable

kernel: [system_call+126/131] system_call+0x7e/0x83 What could be causing this problem? -- Frederik Himpe <[EMAIL PROTECTED]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http:/

2.6.24 regression: pan hanging unkilleable and un-straceable

kernel: [system_call+126/131] system_call+0x7e/0x83 What could be causing this problem? -- Frederik Himpe [EMAIL PROTECTED] -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org

Re: [PATCH v2] Fix hardware IRQ time accounting problem.

h into one for neatness. I can confirm this patch fixed the problem for me. Thank you! -- Frederik Himpe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-i

Re: [PATCH v2] Fix hardware IRQ time accounting problem.

confirm this patch fixed the problem for me. Thank you! -- Frederik Himpe -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org

Re: 2.6.24-rc3-git3: usb hardware interrupts using 25% of CPU time

On Thu, 29 Nov 2007 00:02:01 +0100, Rafael J. Wysocki wrote: > On Wednesday, 28 of November 2007, Frederik Himpe wrote: >> I installed Linux 2.6.24-rc3-git3 on a PPC based Apple Powerbook G4 >> system. Now with top I see that over 20% of CPU time is used by >> hardwar

2.6.24-rc3-git3: usb hardware interrupts using 25% of CPU time

:24:0f.0 Ethernet controller [0200]: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) [106b:0032] (rev 80) Full dmesg, .config and lsmod output can be found on http://artipc10.vub.ac.be/linux-2.6.24-rc3-git3/ -- Frederik Himpe - To unsubscribe from this list: send the line "unsubscribe

2.6.24-rc3-git3: usb hardware interrupts using 25% of CPU time

:24:0f.0 Ethernet controller [0200]: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) [106b:0032] (rev 80) Full dmesg, .config and lsmod output can be found on http://artipc10.vub.ac.be/linux-2.6.24-rc3-git3/ -- Frederik Himpe - To unsubscribe from this list: send the line unsubscribe linux

Re: 2.6.24-rc3-git3: usb hardware interrupts using 25% of CPU time

On Thu, 29 Nov 2007 00:02:01 +0100, Rafael J. Wysocki wrote: On Wednesday, 28 of November 2007, Frederik Himpe wrote: I installed Linux 2.6.24-rc3-git3 on a PPC based Apple Powerbook G4 system. Now with top I see that over 20% of CPU time is used by hardware interrupts. Looking at /proc

ne2k-pci 0000:05:00.0: no I/O resource at PCI BAR #0

, lspci -nn and lspic -vvv output. Is this a hardware problem, or is something going wrong in the kernel? -- Frederik Himpe Linux version 2.6.23.1-desktop-1mdv ([EMAIL PROTECTED]) (gcc version 4.2.2 20070909 (prerelease) (4.2.2-0.RC.1mdv2008.0)) #1 SMP Wed Oct 31 19:41:36 CET 2007 Command

ne2k-pci 0000:05:00.0: no I/O resource at PCI BAR #0

motherboard. -- Frederik Himpe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

ne2k-pci 0000:05:00.0: no I/O resource at PCI BAR #0

motherboard. -- Frederik Himpe - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

ne2k-pci 0000:05:00.0: no I/O resource at PCI BAR #0

, lspci -nn and lspic -vvv output. Is this a hardware problem, or is something going wrong in the kernel? -- Frederik Himpe Linux version 2.6.23.1-desktop-1mdv ([EMAIL PROTECTED]) (gcc version 4.2.2 20070909 (prerelease) (4.2.2-0.RC.1mdv2008.0)) #1 SMP Wed Oct 31 19:41:36 CET 2007 Command

Re: CFS + Rhythmbox audio skipping

On Fri, 24 Aug 2007 16:57:43 +0200, Ingo Molnar wrote: > * Frederik Himpe <[EMAIL PROTECTED]> wrote: > >> Some time ago, it was already discussed here that Rhythmbox would >> easily cause audio skipping when running with the CFS scheduler >> (http:// bhhdoa.org.au

CFS + Rhythmbox audio skipping

somebody give some more details about what Rhythmbox is doing wrong, either here, either in the bug ticket? -- Frederik Himpe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.

CFS + Rhythmbox audio skipping

somebody give some more details about what Rhythmbox is doing wrong, either here, either in the bug ticket? -- Frederik Himpe - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org

Re: CFS + Rhythmbox audio skipping

On Fri, 24 Aug 2007 16:57:43 +0200, Ingo Molnar wrote: * Frederik Himpe [EMAIL PROTECTED] wrote: Some time ago, it was already discussed here that Rhythmbox would easily cause audio skipping when running with the CFS scheduler (http:// bhhdoa.org.au/pipermail/ck/2007-June/007886.html

Re: pata_ali exceptions (timeout)

easier to check. I have attached the output of lspci -nn. -- Frederik Himpe 00:00.0 Host bridge [0600]: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] [1002:cab2] (rev 02) 00:01.0 PCI bridge [0604]: ATI Technologies Inc PCI Bridge [IGP 340M] [1002:7010] 00:06.0 Multimedia audio controller

Re: pata_ali exceptions (timeout)

the output of lspci -nn. -- Frederik Himpe 00:00.0 Host bridge [0600]: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] [1002:cab2] (rev 02) 00:01.0 PCI bridge [0604]: ATI Technologies Inc PCI Bridge [IGP 340M] [1002:7010] 00:06.0 Multimedia audio controller [0401]: ALi Corporation M5451 PCI

pata_ali exceptions (timeout)

this is the same problem as discussed earlier in these threads? http://lkml.org/lkml/2006/6/20/309 http://www.opensubscriber.com/message/linux-ide%40vger.kernel.org/7326463.html -- Frederik Himpe Linux version 2.6.22-5mdv ([EMAIL PROTECTED]) (gcc version 4.2.1 20070802 (prerelease) (4.2.1

pata_ali exceptions (timeout)

this is the same problem as discussed earlier in these threads? http://lkml.org/lkml/2006/6/20/309 http://www.opensubscriber.com/message/linux-ide%40vger.kernel.org/7326463.html -- Frederik Himpe Linux version 2.6.22-5mdv ([EMAIL PROTECTED]) (gcc version 4.2.1 20070802 (prerelease) (4.2.1

Re: [2.6.22-rc6] NForce4 soft and hard resetting ports and exceptions

On Tue, 26 Jun 2007 17:45:22 +, Frederik Himpe wrote: > I tried Linux 2.6.22-rc6 on my machine with an Asus A8N-SlI Deluxe > motherboard (NForce 4 chipset). > > When booting, the system hangs for a long time, but it continues after a > long wait. I found these kind of err

[2.6.22-rc6] NForce4 soft and hard resetting ports and exceptions

0xc201a59c ATA: abnormal status 0xD0 on port 0xc201a59c ata2.00: revalidation failed (errno=-2) [...] With Linux 2.6.21 this did not happen. config, dmesg and lspci can be found here: http://artipc10.vub.ac.be/kernelbug/ -- Frederik Himpe - To unsubscribe from this list: send the line

[2.6.22-rc6] NForce4 soft and hard resetting ports and exceptions

0xc201a59c ATA: abnormal status 0xD0 on port 0xc201a59c ata2.00: revalidation failed (errno=-2) [...] With Linux 2.6.21 this did not happen. config, dmesg and lspci can be found here: http://artipc10.vub.ac.be/kernelbug/ -- Frederik Himpe - To unsubscribe from this list: send the line

Re: [2.6.22-rc6] NForce4 soft and hard resetting ports and exceptions

On Tue, 26 Jun 2007 17:45:22 +, Frederik Himpe wrote: I tried Linux 2.6.22-rc6 on my machine with an Asus A8N-SlI Deluxe motherboard (NForce 4 chipset). When booting, the system hangs for a long time, but it continues after a long wait. I found these kind of errors in the logs