I finally got back to this ThinkPad R51 stability problem and was able
to definitively assign blame to a defective (at least in this box)
memory module. Defective memory was suggested on list as a probable
cause, so thank you. I first used the "mem=1G" kernel boot parameter to
limit memory used
nstall
emacs24 because I have some confidence that the problem won't occur with
emacs24, just as it doesn't occur with my built emacs23. But I'll still
have the problem so I'm going to keep the native emacs23 for a bit
longer to see if I can come up with a more general solutio
:05 emacs23-x
seem to indicate some significant differences. Just for posterity, does
anyone have any insight into how one can build the identical Debian
binary to that installed?
Paul Ausbeck
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscr
I recently replaced the hard disk in my ThinkPad R51 with a solid state
drive and when I did so I installed Debian Wheezy LXDE updated with a
3.16 kernel as one of the boot options. I really am pleased with how the
system looks and acts except for a curious instability that occurs
increasingly
What is the difference between Microsoft insisting that Bret upgrade
from Debian 6 to 7 and other Debian users insisting that Bret upgrade
from Debian 6 to 7. Don't Debians know why they don't like Microsoft?
!systemd, !systemd, !systemd
On 8/2/2014 4:55 PM, Bret Busby wrote:
On 03/08/2014, J
with hyperthreading enabled. I'll delve more deeply into this as time
allows.
On 5/14/2014 4:05 PM, Henrique de Moraes Holschuh wrote:
On Wed, 14 May 2014, Paul Ausbeck wrote:
While examining the kernel log for another reason, I came across
evidence that acpi_idle, and not intel_idle, is bei
I have a newly built Wheezy 7.5 machine that I wanted to wake from S3
suspend using either a USB keyboard or mouse. This doesn't happen by
default, and after researching this topic a bit online, I was unable to
find a low complexity method for making it possible. Following some
study, I devised
I have two identical machines and one experienced a SSD failure. I
obtained a replacement SSD and cloned the drive out of the unaffected
machine using dd. Something like:
dd bs=4096 if=/dev/sdb of=saved.img
dd bs=4096 if=saved.img of=/dev/sdb
The cloned drive functions exactly like the origina
el products but heretofore unnoticed.
All experiments with 3.12 kernel.
On 5/14/2014 4:05 PM, Henrique de Moraes Holschuh wrote:
On Wed, 14 May 2014, Paul Ausbeck wrote:
While examining the kernel log for another reason, I came across
evidence that acpi_idle, and not intel_idle, is being used on my
I've got a desktop system with no ps/2 ports. I wanted to wake the
machine from S3 suspend using either the USB keyboard or mouse. After
researching this topic a bit online, I was unable to find a reasonably
simple solution. Following some study, I devised the following udev rule
for enabling t
While examining the kernel log for another reason, I came across
evidence that acpi_idle, and not intel_idle, is being used on my
dn2800mt system, see below. In fact, it seems that intel_idle cannot be
used. Is there some sort of binary blob involved here?
-
hdparm -t that's affected.
On 5/9/2014 2:56 PM, Henrique de Moraes Holschuh wrote:
On Fri, 09 May 2014, Paul Ausbeck wrote:
Henrique, thanks a lot for the detailed reply. I will look at the
stuff that you suggested, if only to learn about what I don't know.
FYI, the problem doesn'
t some point to pin down what
these log messages actually mean.
On 5/9/2014 12:30 PM, Henrique de Moraes Holschuh wrote:
On Thu, 08 May 2014, Paul Ausbeck wrote:
Next, I don't agree that this hyperthreading problem reeks of a
firmware issue. What it reeks of is a linux kernel issue. I'
0.34 MB/sec
/dev/sdc:
Timing cached reads: 1744 MB in 2.00 seconds = 872.13 MB/sec
Timing buffered disk reads: 96 MB in 3.00 seconds = 31.97 MB/sec
On 5/8/2014 6:44 AM, Henrique de Moraes Holschuh wrote:
On Mon, 05 May 2014, Paul Ausbeck wrote:
I've attached the contents of /proc/cp
xtpr pdcm movbe lahf_lm arat dtherm
bogomips: 3733.42
clflush size: 64
cache_alignment: 64
address sizes: 36 bits physical, 48 bits virtual
power management:
On 5/4/2014 5:12 PM, Henrique de Moraes Holschuh wrote:
On Sun, 04 May 2014, Paul Ausbeck wrote:
when I build a new system. Re
Running Wheezy 7.4, kernel 3.2.0-4-686-pae, also on Debian backports
kernel 3.12-0.bpo.1-686-pae
sudo hdparm -t /dev/sda
/dev/sda: # Hyperthreading enabled in bios
Timing buffered disk reads: 36 MB in 3.06 seconds = 11.77 MB/sec
# Apparently not correct
/dev/sda: # Hyperthreading disa
16 matches
Mail list logo
