Richmond writes:
> This occurs during shutdown. I've also noticed occasional delays "a stop
> job is running". These occur when I am using a desktop
> environment. Currently I am using gnome.
>
> kernel: traps: dconf worker[2353] general protection fault
> ip:7fe
This occurs during shutdown. I've also noticed occasional delays "a stop
job is running". These occur when I am using a desktop
environment. Currently I am using gnome.
kernel: traps: dconf worker[2353] general protection fault
ip:7fe4564ec4a6 sp:7fe448e31090 error:0 in
libc-2.31.
Hello,
I had recently a general protection fault on a Debian 8 server with
Xen (debian pacakge: 4.4.4lts4-0+deb8u1) on the vif50.1-q1-guest
kernel proces. I have copied the kernel log below in this mail for
reference. After this GPF the system was still responding but one domU
lost network
Hi all!
A few minutes ago I just experienced a horrible crash on one of my
computers with Debian Jessie:
---
Oct 31 17:17:32 ss01 kernel: [694807.832919] general protection fault:
[#1] SMP
Oct 31 17:17:32 ss01
n Wheezy since HP currently has only Squeeze
> builds.
>
> Cheers,
> Martin
I actually used the packages provided by HP for ubuntu/precise.
I just tried with the precise kernel and got the same hpasmlited general
protection fault :-(
Linux xenhost 3.2.0-47-generic #72-Ubuntu SMP Mon Jun 3
heers,
Martin
On 05.06.13 12:34, Bruno Voigt wrote:
Hi @all,
I have a problem with HP-Tools on Debian/Wheezy/amd64 running
under Xen-Hypervisor on a HP DL380 G7 system.
The hp-health package cannot be installed,
because the hpasmlited crashes with an general protection fault.
Has anyone s
Hi @all,
I have a problem with HP-Tools on Debian/Wheezy/amd64 running
under Xen-Hypervisor on a HP DL380 G7 system.
The hp-health package cannot be installed,
because the hpasmlited crashes with an general protection fault.
Has anyone solved / circumvented this problem ?
eg. some kernel
On Wed, Feb 23, 2011 at 10:36:52AM -1000, Joel Roth wrote:
> Hi,
>
> I'm running sid on amd64. My cupsd fails to start.
> >From /var/log/syslog:
>
> kernel: [209082.595638] cupsd[31022] general protection ip:7fc2be37f5e8
> sp:7fff3feb7058 error:0 in libc-2.11.2.so[7fc2be30+158000]
apt-get
Hi,
I'm running sid on amd64. My cupsd fails to start.
>From /var/log/syslog:
kernel: [209082.595638] cupsd[31022] general protection ip:7fc2be37f5e8
sp:7fff3feb7058 error:0 in libc-2.11.2.so[7fc2be30+158000]
Any ideas where I should go next?
If it's nothing obvious, I'll report a bug.
Update: this issue is now bug 500850 in openafs-modules-source. The
solution is to set the following in the kernel .config:
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=y
---
On Mon, 29 Sep 2008, Andrew Perrin wrote:
Using debian testing (lenny) and self-compiled 2.6.25 or 2.6.26 kernels, I
get the following GPF:
Sep 29 16:08:47 che kernel: general protection fault: [#1] SMP
...
Sep 29 16:08:47 che kernel: Call Trace:
Sep 29 16:08:47 che kernel
Andrew Perrin wrote:
> Using debian testing (lenny) and self-compiled 2.6.25 or 2.6.26 kernels,
> I get the following GPF:
[GPF trace snip]
> This does *not* happen using 2.6.24 compiled with essentially the same
> .config file. Using the latest openafs-modules-source: 1.4.7.dfsg1-5.
>
> Any adiv
Using debian testing (lenny) and self-compiled 2.6.25 or 2.6.26 kernels, I
get the following GPF:
Sep 29 16:08:47 che kernel: general protection fault: [#1] SMP
Sep 29 16:08:47 che kernel: Modules linked in: piix ide_cd_mod ide_core
pata_mpiix radeon drm openafs(P) rfcomm l2cap bluetooth
en up for 18 months.
Ian
-Original Message-
From: Ethan Benson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 19, 2001 5:55 PM
To: 'Debian Users'
Subject: Re: Strange logs - General Protection Fault
On Tue, Jun 19, 2001 at 12:57:42PM +1000, Ian Perry wrote:
> Hi all,
&g
On Tue, Jun 19, 2001 at 12:57:42PM +1000, Ian Perry wrote:
> Hi all,
>
> My first General Protection Fault since Windows 3 !!
> Can anyone shed some light on this ?
>
> It occurred right after an ISDN reconnect. The machine appeared to still be
> working !!! Named
Hi all,
My first General Protection Fault since Windows 3 !!
Can anyone shed some light on this ?
It occurred right after an ISDN reconnect. The machine appeared to still be
working !!! Named, Sendmail, POP, IMAP, Masquerading...
The machine is in a different state, so I had the operator there
salesman ?
>
> --
> From: Ron Rademaker[SMTP:[EMAIL PROTECTED]
> Sent: Monday, 24 April 2000 5:57 AM
> To: debian-user@lists.debian.org
> Subject: General Protection Fault
>
> How do I solve a General Protection Fault (Oops = 0002), I get it wh
TP:[EMAIL PROTECTED]
> Sent: Monday, 24 April 2000 5:57 AM
> To: debian-user@lists.debian.org
> Subject: General Protection Fault
>
> How do I solve a General Protection Fault (Oops = 0002), I get it when I
> boot with the rescue disk, when trying to install (right after mount
How do I solve a General Protection Fault (Oops = 0002), I get it when I
> boot with the rescue disk, when trying to install (right after mounting
> the root filesystem (RAM)) it gives the errors, and ends with: Aiee,
> killing the interrupt handler
> If you need more information, I wrote
Are you sure the K6 hasn't been over clocked by some bastard salesman ?
--
From: Ron Rademaker[SMTP:[EMAIL PROTECTED]
Sent: Monday, 24 April 2000 5:57 AM
To: debian-user@lists.debian.org
Subject: General Protection Fault
How do I solve a General Protection Fault
Ron Rademaker wrote:
> The system started giving general protection faults after I upgraded it
> (general protection faults both in linux as in windows) from a P166 with
> 32 M to a amd k6-2 533 with 128 M.
Hmmm. Sounds like bad RAM to me. Try the old 32M or RAM from a working
machine and see i
On Sun, Apr 23, 2000 at 07:57:27PM +0200, Ron Rademaker wrote:
> How do I solve a General Protection Fault (Oops = 0002), I get it when I
> boot with the rescue disk, when trying to install (right after mounting
> the root filesystem (RAM)) it gives the errors, and ends with: Aiee,
>
How do I solve a General Protection Fault (Oops = 0002), I get it when I
boot with the rescue disk, when trying to install (right after mounting
the root filesystem (RAM)) it gives the errors, and ends with: Aiee,
killing the interrupt handler
If you need more information, I wrote all the output
23 matches
Mail list logo
