From: Rodney Gordon II <meff@pobox.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck list <ck@vds.kolivas.org>, linux list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.16-ck1
Date: Thu, 23 Mar 2006 06:00:18 -0600 [thread overview]
Message-ID: <20060323120018.GA10050@spherenet.spherevision.org> (raw)
In-Reply-To: <cone.1143114017.303805.31285.501@kolivas.org>
On Thu, Mar 23, 2006 at 10:40:17PM +1100, Con Kolivas wrote:
> Rodney Gordon II writes:
>
> >Good job Con, on your patches.. As far as the kernel in general, I'd
> >like to post some warnings:
>
> Thanks.
>
> >Adaptive readahead: I had probs with this before, and I still do.. On
> >a desktop if you have odd problems (nothing responding for SECONDS,
> >very slow disk I/O during heavy I/O, etc..) disable it.
>
> I was concerned about that myself which is why the only reason I included
> it was because it came in a configurable form where you could choose to
> enable it, and the default was off, and the config option even said
> suitable to _servers_, not desktops.
Yea, just thought I would try it again sighting the improvements in
the ? docs in menuconfig, was just disappointed again.
> >The new Yukon2 "sky2" driver: This one really pissed me off. It had me
> >thinking apache2 AND my linksys router we're on the brink. For some
> >unknown reason at least for me, in FF it would only half-load some
> >pages, including ones on localhost AND my router (10.1.1.1) ... I
> >dunno what the hell is up with this one. I have to stay with the
> >syskonnect.com sk98lin patch, which.. doesn't work with 2.6.16 so I am
> >back to 2.6.15 at the moment.
> >
> >nVidia drivers: Broken. I posted a ftbfs bug on the debian bts, here
> >is a current patch that works against the current release:
> >http://bugs.debian.org/cgi-bin/bugreport.cgi/nvidia-kernel-source_1.0.8178-2.diff?bug=357992;msg=15;att=1
>
> Luckily none of these are my fault.
Yep, just warnings in general.
> >All in all, my experience sucked for the first time on this kernel.
>
> /me does the "not my fault" look.
LOL, I know, just warnings in general like I have said.
> >Good luck with this new one..
>
> Heh. No new one in the works just yet, but I'm actually not planning on
> changing anything. Turn adaptive readahead off, and you're left with out of
> kernel tree, or worse, binary driver problems.
Turned it off, disk probs are gone.
Meant to say "Good luck with this new mainline one.."
Your patches are great.. Thus, why I started this post with "Good
job Con, on your patches.." ;)
-r
--
Rodney "meff" Gordon II -*- meff@pobox.com
Systems Administrator / Coder Geek -*- Open yourself to OpenSource
next prev parent reply other threads:[~2006-03-23 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 10:45 2.6.16-ck1 Con Kolivas
[not found] ` <3aa654a40603200300r28034d9di86ed58107d245f08@mail.gmail.com>
2006-03-20 11:39 ` [ck] 2.6.16-ck1 Hugo Vanwoerkom
2006-03-23 11:31 ` Rodney Gordon II
2006-03-23 11:40 ` Con Kolivas
2006-03-23 12:00 ` Rodney Gordon II [this message]
2006-03-23 12:37 ` Matt Heler
2006-03-23 13:14 ` Wu Fengguang
2006-03-23 13:21 ` Rodney Gordon II
[not found] ` <dvv0ob$nql$1@sea.gmane.org>
2006-03-23 22:31 ` Stephen Hassard
2006-03-24 6:58 ` 2.6.16-ck1 Edouard Gomez
2006-03-25 18:03 ` [ck] 2.6.16-ck1 Rodney Gordon II
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=20060323120018.GA10050@spherenet.spherevision.org \
--to=meff@pobox.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.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
Powered by JetHome