mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: gregkh@suse.de, bunk@stusta.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz,
	pcihpd-discuss@lists.sourceforge.net,
	Neil Brown <neilb@cse.unsw.edu.au>,
	mmokrejs@ribosome.natur.cuni.cz,
	Dave Hansen <haveblue@us.ibm.com>, Nathan Scott <nathans@sgi.com>
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Wed, 8 Mar 2006 15:29:28 -0800	[thread overview]
Message-ID: <20060308152928.21afef81.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603081502350.32577@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> wrote:
>
> 
> 
> On Wed, 8 Mar 2006, Greg KH wrote:
> > 
> > None, as I am expecting 2.6.16 to be out any day now.
> 
> Sadly, until the FC5 problems re at least somewhat more understood, I 
> don't think that's going to happen.
> 
> Trying to chase down Andrew's "laptop from hell" has also delayed even 
> doing a -rc6, although that is imminent.
> 

Well..  That's a problem which only I can reproduce, and that only after
applying sched patches while performing strange acts upon small animals.
Plus I don't think we're close to fixing it.

More serious matters would be:

- The x86_64-goes-oom-due-to-bio-using-GFP_DMA bug.  I'll send the patch
  over today.

- The some-ati-timers-go-too-fast bug.  I'll sndn that patch today as
  well.

- Neil is sitting on a radi1 BIO leak fix which we need.

- It would be nice to get Martin MOKREJ
  <mmokrejs@ribosome.natur.cuni.cz>'s full 16GB recognised again.  Dave
  Hansen is working on that.

- http://bugzilla.kernel.org/show_bug.cgi?id=6180 seems to be a recent
  XFS regression.

- Matthew Grant <grantma@anathoth.gen.nz>'s "rt_sigsuspend() does not
  return EINTR on 2.6.16-rc2+" might be a new poll() bug, but that one's
  hard and I suspect we'll need the extra testers which 2.6.16 will give to
  be able to work out whether it's real and what the fix is.

- http://bugzilla.kernel.org/show_bug.cgi?id=6177 _looks_ like a serious
  TCP regression, but that happened between 2.6.14 and 2.6.15 and that's
  the only report I've seen.

Plus lots of other stuff, probably.

  parent reply	other threads:[~2006-03-08 23:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:35 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00   ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50   ` Greg KH
2006-03-08 23:03     ` Linus Torvalds
2006-03-08 23:18       ` Greg KH
2006-03-08 23:30         ` Linus Torvalds
2006-03-09 18:40           ` Tomasz Torcz
2006-03-09 19:49             ` Linus Torvalds
2006-03-09 20:10               ` Ben Collins
2006-03-09 20:24                 ` Linus Torvalds
2006-03-15 16:03                   ` Ben Collins
2006-03-09 20:52                 ` Lee Revell
2006-03-09 21:06                   ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47                     ` Lee Revell
2006-03-09 21:07                   ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37               ` Arjan van de Ven
2006-03-09 20:46                 ` Dave Jones
2006-03-09 21:15                   ` Arjan van de Ven
2006-03-08 23:29       ` Andrew Morton [this message]
2006-03-08 23:45         ` Dave Hansen
2006-03-08 23:52           ` Andrew Morton
2006-03-09 10:24         ` Martin MOKREJŠ
2006-03-08 23:05     ` Adrian Bunk
2006-03-08 23:18       ` Lee Revell
2006-03-08 23:23         ` Greg KH
2006-03-08 23:34           ` Lee Revell
2006-03-08 23:40             ` Greg KH
2006-03-09  0:03               ` Lee Revell
2006-03-08 23:21       ` Greg KH
2006-03-09  4:01 ` Kenji Kaneshige
2006-03-09  5:34   ` Greg KH
2006-03-09  5:11 ` Lee Revell

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=20060308152928.21afef81.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    --cc=nathans@sgi.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --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

Powered by JetHome