public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.6.13-rc6: aic7xxx testers please..
Date: Sun, 07 Aug 2005 16:38:49 -0400	[thread overview]
Message-ID: <1123447130.12766.35.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.58.0508071136020.3258@g5.osdl.org>

On Sun, 2005-08-07 at 11:47 -0700, Linus Torvalds wrote:
> James and gang found the aic7xxx slowdown that happened after 2.6.12, and 
> we'd like to get particular testing that it's fixed, so if you have a 
> relevant machine, please do test this.
> 
> There are other fixes too, a number of them reverting (at least for now)  
> patches that people had problems with. In general, anybody who has
> reported regressions since 2.6.12, please re-test with -rc6 and report
> back (even if, or perhaps _particularly_ if, no change to the regression).

It looks like CONFIG_4KSTACKS has gone away (IOW 8K stacks are no longer
an option).  But now I get this ominous warning when I compile
ndiswrapper:

*** WARNING: Kernel seems to have 4K size stack option (CONFIG_4KSTACKS)
removed; many Windows drivers will need at least 8K size stacks. You
should read wiki about 4K size stack issue. Don't complain about crashes
until you resolve this

As ndiswrapper seems to be the only option for many wireless chipsets,
this certainly looks like it will lead to regressions.

Why was this option removed?  It's pretty clear that lots of out of tree
drivers still require it.

Lee




  parent reply	other threads:[~2005-08-07 20:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 18:47 Linux-2.6.13-rc6: aic7xxx testers please Linus Torvalds
2005-08-07 20:23 ` Heikki Orsila
2005-08-07 20:38 ` Lee Revell [this message]
2005-08-07 20:50   ` Linus Torvalds
2005-08-07 20:52     ` Lee Revell
2005-08-07 21:14 ` Dumitru Ciobarcianu
2005-08-08 14:17   ` Theodore Ts'o
2005-08-07 22:12 ` [2.6 patch] fix drivers/s390/net/ compilation Adrian Bunk
2005-08-08  8:31   ` Martin Schwidefsky
2005-08-08 12:59 ` Linux-2.6.13-rc6: aic7xxx testers please John Stoffel
2005-08-08 15:08 ` Danny ter Haar
2005-08-08 17:54 ` Jesper Juhl
2005-08-09 19:35   ` John Stoffel
2005-08-09 19:58     ` James Bottomley
2005-08-09 20:12       ` John Stoffel
2005-08-10  0:50         ` James Bottomley
2005-08-10 15:28           ` John Stoffel
2005-08-10 15:46             ` James Bottomley
2005-08-10 16:27               ` John Stoffel
2005-08-11  2:30                 ` John Stoffel
2005-08-11  6:34 ` Philipp Matthias Hahn
2005-08-11  6:42 ` Philipp Matthias Hahn
2005-08-11  9:54   ` Johannes Stezenbach
2005-08-11 12:37   ` hunold
2005-08-11 14:51     ` Gene Heskett
2005-08-11 15:38       ` cx88 teletext not yet implemented -was- " Michael Krufky
2005-08-11 21:53         ` Gene Heskett
2005-08-11 15:30     ` Philipp Matthias Hahn
     [not found]     ` <20050815071723.GB8524@titan.lahn.de>
     [not found]       ` <20050815215855.GB5860@linuxtv.org>
     [not found]         ` <E1E4vSG-0005r7-KG@allen.werkleitz.de>
2005-08-24  6:59           ` [PATCH] saa7146_i2c device model integration Philipp Matthias Hahn
2005-08-31 12:14             ` Johannes Stezenbach

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=1123447130.12766.35.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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