On Wed, 2013-03-20 at 20:57 +0100, Volker Armin Hemmann wrote:
> you might just hit a thrashing situation. Linux is very bad when it
> comes to abusing swap in case of an emergency.
>
> But it also sounds like overheating or a power problem. Power problems
> might be caused by the PSU - but it cou
Oom Killer is Not instant, can take a long time or get stuck or kills
something vital.
...
Am 21.03.2013 07:52 schrieb "Carlos Hendson" :
> On Thu, 2013-03-21 at 06:45 +0100, Volker Armin Hemmann wrote:
> > You got your answer. 8gig and no swap is NOT ENOUGHT.
>
> It's a strong indicator, which is
On Thu, 2013-03-21 at 06:45 +0100, Volker Armin Hemmann wrote:
> You got your answer. 8gig and no swap is NOT ENOUGHT.
It's a strong indicator, which is going to be corrected.
I am slightly confused by the resulting behaviour however. I was of the
impression oomkiller would start to kill process
On Wed, 2013-03-20 at 16:27 -0500, Paul Hartman wrote:
>
> I had a virtual server that kept crashing/rebooting during compiles of
> large packages such as php. It ended up being because it was running
> out of memory. Added another 1GB of swap space and it has been happy
> ever since.
Thanks Pau
You got your answer. 8gig and no swap is NOT ENOUGHT.
Am 20.03.2013 22:51 schrieb "Carlos Hendson" :
> On Wed, 2013-03-20 at 20:57 +0100, Volker Armin Hemmann wrote:
> > you might just hit a thrashing situation. Linux is very bad when it
> > comes to abusing swap in case of an emergency.
> >
> > B
On Wed, 2013-03-20 at 20:57 +0100, Volker Armin Hemmann wrote:
> you might just hit a thrashing situation. Linux is very bad when it
> comes to abusing swap in case of an emergency.
>
> But it also sounds like overheating or a power problem. Power problems
> might be caused by the PSU - but it cou
On Wed, 2013-03-20 at 08:17 +, Mick wrote:
> Stating the obvious, it seems that the kernel is struggling and indeed
> you may
> have come across some nasty kernel bug. However, it could well be
> that it is
> not related to the kernel you're running, or your kernel config. It
> could be
>
On Wed, 2013-03-20 at 18:43 +0100, Daniel Wagener wrote:
> "Frozen" means there is no Hard Drive Activity going on right?
> And there is no other indication, that you are just running out of
> memory?
I can't categorically state if there was drive activity. I was so
fixated on regaining control
On Tue, Mar 19, 2013 at 11:42 PM, Carlos Hendson wrote:
> For last few weeks or so, I've been getting intermittent hard lock-ups
> during the emerge of various packages. It appears the more compile
> intensive the package, the more likely the lock-up. These lock-ups have
> occurred under kernels
Am 20.03.2013 05:42, schrieb Carlos Hendson:
> Hello,
>
> For last few weeks or so, I've been getting intermittent hard lock-ups
> during the emerge of various packages. It appears the more compile
> intensive the package, the more likely the lock-up. These lock-ups have
> occurred under kernels
On Wed, 20 Mar 2013 05:42:28 +0100
Carlos Hendson wrote:
> Hello,
>
> For last few weeks or so, I've been getting intermittent hard lock-ups
> during the emerge of various packages. It appears the more compile
> intensive the package, the more likely the lock-up. These lock-ups have
> occurred
On Wed, 20 Mar 2013 08:17:11 +, Mick wrote:
> Stating the obvious, it seems that the kernel is struggling and indeed
> you may have come across some nasty kernel bug. However, it could well
> be that it is not related to the kernel you're running, or your kernel
> config. It could be a probl
On Wednesday 20 Mar 2013 04:42:28 Carlos Hendson wrote:
> Hello,
>
> For last few weeks or so, I've been getting intermittent hard lock-ups
> during the emerge of various packages. It appears the more compile
> intensive the package, the more likely the lock-up. These lock-ups have
> occurred un
Hello,
For last few weeks or so, I've been getting intermittent hard lock-ups
during the emerge of various packages. It appears the more compile
intensive the package, the more likely the lock-up. These lock-ups have
occurred under kernels 3.4.9 and 3.7.10 with gcc 4.5.4 and 4.6.3.
Once the mac
On Monday 06 February 2006 21:07, Marco Calviani wrote:
> Hi,
>
> > yupp, kernel waits for some time outs, if you did not set unmaskirq with
> > hdparm, this may make your laptop pretty unresponsive.
>
> do you mean that i have to set the umaskirq option also for cdrom? I
> had it set with hdparm o
Hi,
> Substituting the power supply cured all the issues, but I don't know how
> it can be done on a laptop.
thanks for sharing your experience.
Regards,
MC
--
gentoo-user@gentoo.org mailing list
Hi,
> yupp, kernel waits for some time outs, if you did not set unmaskirq with
> hdparm, this may make your laptop pretty unresponsive.
do you mean that i have to set the umaskirq option also for cdrom? I
had it set with hdparm only for my primary hd, that is /dev/hda.
Regards,
MC
--
gento
On Friday 03 February 2006 14:36, Marco Calviani wrote:
> Hi list,
>i'm a Travelmate 8005 laptop user, running an updated gentoo box.
> I'm routinely experiencing system freezes 1 or 2 times every two days,
> without an apparent cause; everything stops, starting from mouse to
> keyboard, so tha
The system logs of the system does not suggest anything particular
except for this:
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_c
Hi list,
i'm a Travelmate 8005 laptop user, running an updated gentoo box.
I'm routinely experiencing system freezes 1 or 2 times every two days,
without an apparent cause; everything stops, starting from mouse to
keyboard, so that it is impossible to restart the system.
The system logs of the
20 matches
Mail list logo
