Strange OOM problem (swap empty)

Last night one of our testbed fileservers went OOM for unknown reasons. (The log is attached.) Its a moderately complex setup - 2 dual-core Opteron chips with 8G of (matched) ram under Xen. The file array (which was doing heavy writes from this node using rsync) is an external multi-connected s

Re: PROBLEM: system clock slow on Athlon AMD64 since 2.6.21

On 6/9/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote: According to your system description it seems that you have a Targa Visionary laptop with a VIA chipset and a Mobile Athlon64. If so, then you probably have the same problem I reported some time ago: see

Re: Back to the future.

We used it (with great success) to replace bad UPSs on single-PSU database servers under (light) load. No need for scheduled downtime, etc. The whole point of hibernation (or suspend to disk, or whatever you call it) is that the system goes to a zero-power state and then can be brought back to it

Re: 2.4.6-ac5 and VIA Athlon chipsets

Will this fix (or get closer to fixing) the K7-optimization crashes? (I'm still hoping its something that isn't getting initialized correctly, rather than just a bug. BurnK7/BurnMMX work fine, memtest86 and the MMX memtest work, windows seems to be using the full memory bandwidth, etc.) On Thu,

Re: Controversy over dynamic linking -- how to end the panic

In-Reply-To: <[EMAIL PROTECTED]> On Thu, 21 Jun 2001, Alan Cox did have cause to say: > An application is clearly not a derivative work in the general case, and they > are linked with glibc which is LGPL and gives the users the choice and right > to run non-free apps. IANAL, and this may be a

Re: rsync hangs on RedHat 2.4.2 or stock 2.4.4

On Tue, 12 Jun 2001, David S. Miller did have cause to say: > Look everyone, it was determined to be a deadlock because of some > interaction between how rsync sets up it's communication channels > with the ssh subprocess, readas: userland bug. we're not using ssh. :( --- -BEGIN GEEK CO

Re: rsync hangs on RedHat 2.4.2 or stock 2.4.4

On Tue, 12 Jun 2001, Rasmus Andersen did have cause to say: > On Tue, Jun 12, 2001 at 02:59:12PM +0100, Jeremy Sanders wrote: > > I'm getting numerous rsync (v2.4.6) problems under Linux 2.4.2 (RedHat > > 7.1) or stock 2.4.4 on several machines. rsync often hangs copying files > > I could swear

Re: Break 2.4 VM in five easy steps

On Tue, 05 Jun 2001, Derek Glidden did have cause to say: > > The swapoff algorithms in 2.2 and 2.4 are basically identical. > > The problem *appears* worse in 2.4 because it uses lots > > more swap. > > I disagree with the terminology you're using. It *is* worse in 2.4, > period. If it only *

Re: [PATCH] fbdev logo (fwd)

Ditto - I'd like at least an option of the "incorrect" logo. I can (sorta) see not having it as the default. But perhaps under the 'experimental drivers' tag, have an option of "Politically incorrect framebuffer logo". (If there isn't a huge outcry against it, I may work up a patch - been meani

Re: [PATCH] Single user linux

On Wed, 25 Apr 2001, Ronald Bultje did have cause to say: > Who says it needs to compile? Who says it needs software installed? Who > says it needs to run the software itself? My current project (and I'm just waiting for nfs and wvlan_cs to stabalize on ARM before putting the final touches on it

Re: [PATCH] Single user linux

On Tue, 24 Apr 2001, Aaron Lehmann did have cause to say: > On Wed, Apr 25, 2001 at 10:07:48AM +1000, Daniel Stone wrote: > > What real value does it have, apart from the geek "look at me, I'm using > > bash" value? > > I don't really want to get into it at the moment, but imagine hacking > netf

Re: Athlon problem report summary

> I wrote a set of programs to tune the MMX code. Arjan I suspect did similar > when he reoptimised the code for the newer Athlon. Simple stuff like Alan - your proggy ran (no output) for about 5 seconds or so, then exited. Arjan - from yours, I get the results below. Either way, no OOPs, no er

Re: Athlon problem report summary

On Sat, 21 Apr 2001, Alan Cox did have cause to say: > K7 optimisation basically enabled the MMX copy/clear code which adds 30-40% > performance to those functions. It also materially ups the maximum memory > bandwidth the processor will use which may be where the fun starts. Not to be slow/dull

Re: Athlon problem report summary

On Sat, 21 Apr 2001, Alan Cox did have cause to say: > > Addendum to 1. So far everyone (at least on LKML) who has had the > > crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or > > kk266r, IIRC) mobo. > > Not quite all. Many have but I have other reports. Oddness. Is it a

Re: Athlon problem report summary

Addendum to 1. So far everyone (at least on LKML) who has had the crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or kk266r, IIRC) mobo. Have we gotten any fix, other than not using K7 optimizations? I'm willing to keep trying new patches, if necessary. (And for that matte

Re: RFC: pageable kernel-segments

On Tue, 17 Apr 2001, Oliver Neukum did have cause to say: > > load/init/etc. Hardware setup tends to only happen once..) > > No they can't. Modules can't be finegrained enough to do this without wasting > more memory due to fragmentation than you'd gain. Actually, don't they do this -already-

Re: Bug in serial.c

On Thu, 19 Apr 2001, Marc Karasek did have cause to say: > 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the > terminal but when you get to a point of entering data (login, configuration > scripts, etc) the terminal does not accept any input. Most gettys and such take a

Re: Your response is requested

(Sending to LKML just so nobody else flips out) OK it wasn't just us. Lemme reassure the admins I just forwarded it to ;) It seems to list the hostname of whoever receives it (neat trick). On Tue, 17 Apr 2001, Dave Zarzycki did have cause to say: > On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:

Re: RFC: pageable kernel-segments

On Tue, 17 Apr 2001, Heusden, Folkert van did have cause to say: > I would think is usable (for example) for my 8MB ram laptop. > Anyone any thoughts on this? I'm not a kernel hacker, but I've got some thoughts on this: 1> Modules (with the autoloader) can do that for anything not necessary to

Re: Athlon runtime problems

> Can the folks who are seeing crashes running athlon optimised kernels all mail > me > - CPU model/stepping vendor_id : AuthenticAMD cpu family : 6 model : 4 model name : AMD Athlon(tm) Processor stepping: 2 cpu MHz : 1202.743 (/proc/cpuinfo attached

Re: Problem with k7 optimizations in 2.4.x?

Blew sky high. Booted stock 2.4.3-ac3, K7 optimizations, init=/bin/sh. First time it went fine for quite some time (10-15 mins, find / -print, etc) and then locked up hard on "open". Second time, it oops'd before hardlocking (which I copied out by hand.) The oops and decode are attached. On Fr

Re: Problem with k7 optimizations in 2.4.x?

On the iwill mobo? (I haven't heard of this problem on other motherboards.) I'll grab the latest -ac today and give it a try this evening. (Just for reference, the system is the Iwill kk266, 1.2G tbird, 512M pc133, ata66 drive - everything has AMD-approved stickers and nothing is overclocked.)

Re: Problem with k7 optimizations in 2.4.x?

Several of us on the list had the same/similar problems. AFAIK the only fix at this point is to run w/ no more than K6 optimizations. Check the archives for -> Only 10 MB/sec with via 82c686b (towards the end of the thread) -> thunderbird 1.2G + kk266 + 2.4.x oops It seems to be something wierd

Re: All processes hung under 2.4.3

Althought I was unable to do any debugging, I found the same thing earlier today. Syslog showed everything normal (uptimed reports, MARK, etc) and ctrl-sysrq worked, but it had frozen hard. I was using xlock, and it was stopped in the middle of an opengl saver. I had suspected it was related to

thunderbird 1.2G + kk266 + 2.4.x oops and crash

Long and short is I have a new mobo/cpu/ram (see below) that runs great under Win98 and passes memtest86 (3 extended runs as pc133/cas2, 3 standard runs as pc100/cas3) but oops's almost immediately under Linux 2.4.x (2.4.2 and 2.4.1 at the least.) With a few rare exceptions (usually kupdated) all