From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: david.ronis@mcgill.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with 2.6.13.[0-2]
Date: Thu, 29 Sep 2005 12:29:20 +0200 [thread overview]
Message-ID: <58cb370e050929032935a87c72@mail.gmail.com> (raw)
In-Reply-To: <17206.60255.403692.773279@montroll.lan>
On 9/25/05, David Ronis <ronis@ronispc.chem.mcgill.ca> wrote:
>
> I recently tried upgrading from 2.6.12.6 to 2.6.13.[0-2] on an HP
> pavilion zv5000 (a P4 with hyper-threading) running slackware-current.
> The configuration and build went fine and the new kernel boots;
> however, things run very very slowly. As far as I can tell, what is
> slow are process involving any disk IO. For example, the part of the
> boot where ldconfig is run seems to take 2-3 times as long as do
> things like remaking the X font caches, loading programs etc.
>
> This vaguely reminds me of my initial experience with this laptop,
> where I hadn't turned on CONFIG_BLK_DEV_ATIIXP, although it is now
> (see below). If I reboot with the old kernel, things run as before.
According to this page http://web.purplefrog.com/~thoth/zv5000/
this laptop uses nForce3 chipset so you should turn on AMD/nForce
IDE driver (CONFIG_BLK_DEV_AMD74XX). Does it help?
Bartlomiej
next prev parent reply other threads:[~2005-09-29 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 18:24 problem with 2.6.13.[0-2] David Ronis
[not found] ` <20050926005531.90DF42E0018@asmx1.McGill.CA>
2005-09-27 2:34 ` David Ronis
2005-09-29 10:29 ` Bartlomiej Zolnierkiewicz [this message]
2005-09-29 21:34 ` David Ronis
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 2:55 Parag Warudkar
2005-09-29 1:37 ` David Ronis
2005-09-29 6:20 ` Jean Delvare
2005-09-29 21:26 ` David Ronis
2005-09-29 4:13 kernel-stuff
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=58cb370e050929032935a87c72@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=david.ronis@mcgill.ca \
--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