From: Gene Heskett <gene.heskett@verizon.net>
To: Valdis.Kletnieks@vt.edu, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
Date: Mon, 12 Jan 2004 01:47:36 -0500 [thread overview]
Message-ID: <200401120147.36032.gene.heskett@verizon.net> (raw)
In-Reply-To: <200401120611.i0C6BH7c003591@turing-police.cc.vt.edu>
On Monday 12 January 2004 01:11, Valdis.Kletnieks@vt.edu wrote:
>On Sun, 11 Jan 2004 21:42:59 PST, Andrew Morton said:
>> Gene Heskett <gene.heskett@verizon.net> wrote:
>> > hubble of about 4 or 5 months back. In any other kernel,
>> > switching to that window took about 12 seconds for the backdrop
>> > to be converted to 1600x1200x32 and drawn the first time and
>> > about 8 seconds for the next time. But with this 2.6.1-mm1
>> > kernel, that repeat window switch is so close to instant that I
>> > cannot see it being drawn.
>>
>> There are no significant fbdev patches in 2.6.1-mm1. There is a
>> DRM update.
>
>The 12 seconds coming and 8 seconds going, versus instant, sounds an
> *awful* lot like the virtual memory manager making better choices
> in -mm kernels, so the pages of pixmap are staying in memory rather
> than paging out.
>
>Other guess is that o21-sched.patch is DTRT, while the stock
> scheduler DTWT for his particular config.
>
>Gene: Can you tell what exactly your system is doing for the 12/8
> seconds? Is it CPU bound, or beating on the disk while paging
> in/out, or just sitting idle? Leaving a 'vmstat 1' running while
> you change backdrops should tell us something.
I can try that with the 2 kernels, but it will have to be after amanda
is done with her nightly tour, which will take another 2.5 hours. By
then I expect to be sleeping, or hope to be, its 1:30am here now.
Or maybe not, what do I do when "vmstat 1" prints its column headers and segfaults?:
---
[root@coyote linux-2.6]# vmstat 1
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
Segmentation fault
[root@coyote linux-2.6]#
---
cd'ing to /proc/1, and trying to "cat mem" gets me this:
---
[root@coyote 1]# cat mem
cat: mem: No such process
[root@coyote 1]#
---
Some of the other names there have content, but 'mem' seems to be
a truely empty filename, marked:
-rw------- 1 root root 0 Jan 12 01:32 mem
but apparently inacessable.
This actually sounds pretty serious, and I did have a hard lockup
in the night last night, had to use the reset button, but I think
that was a cpu overheat, I'd run the heat up cause the missus was
squawking about being cold.
I've rearranged things airwise and got the cpu down to below 70C.
These AMD DX-1600 thoroughbreds really are genuine coffee boilers.
I really should replace it with the cheapest barton cored one, but
this ones been running that hot for 30 months now. Running seti 24/7
of course doesn't help. :)
Do I need YANP42.6 (Yet Another New Program 4 2.6)?
Sorry, couldn't resist creating a new acronym. :)
--
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-01-12 6:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21 ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20 ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 23:04 ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
2004-01-09 22:43 ` Andrew Morton
2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
2004-01-10 4:04 ` Thomas Winischhofer
2004-01-12 2:58 ` Linus Torvalds
2004-01-12 4:53 ` Gene Heskett
2004-01-12 5:42 ` Andrew Morton
2004-01-12 6:11 ` Valdis.Kletnieks
2004-01-12 6:47 ` Gene Heskett [this message]
2004-01-12 7:05 ` Andrew Morton
2004-01-12 7:20 ` Gene Heskett
2004-01-12 12:38 ` Gene Heskett
2004-01-12 6:21 ` Gene Heskett
2004-01-12 6:34 ` Andrew Morton
2004-01-12 6:58 ` Gene Heskett
2004-01-12 7:03 ` Gene Heskett
2004-01-12 16:33 ` Dave Jones
2004-01-12 17:00 ` Gene Heskett
2004-01-12 17:04 ` Dave Jones
2004-01-12 8:58 ` Thomas Winischhofer
2004-01-12 14:32 ` Moritz Muehlenhoff
2004-01-12 10:36 ` Andrew Walrond
2004-01-13 19:04 ` Adrian Bunk
2004-01-14 0:35 ` Thomas Winischhofer
2004-01-15 11:32 ` Adrian Bunk
2004-01-15 11:42 ` Thomas Winischhofer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401120147.36032.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®