public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Henrik Persson <root@fulhack.info>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Dominik Brodowski <linux@brodo.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.13
Date: Wed, 31 Aug 2005 19:29:38 -0700	[thread overview]
Message-ID: <20050901022938.GA27209@kroah.com> (raw)
In-Reply-To: <4314E07F.2080807@fulhack.info>

On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
> Linus Torvalds wrote:
> > There it is. 
> > 
> > The most painful part of 2.6.13 is likely to be the fact that we made x86
> > use the generic PCI bus setup code for assigning unassigned resources.  
> > That uncovered rather a lot of nasty small details, but should also mean
> > that a lot of laptops in particular should be able to discover PCI devices
> > behind bridges that the BIOS hasn't set up.
> > 
> > We've hopefully fixed up all the problems that the longish -rc series
> > showed, and it shouldn't be that painful, but if you have device problems,
> > please make a report that at a minimum contains the unified diff of the
> > output of "lspci -vvx" running on 2.6.12 vs 2.6.13. That might give us
> > some clues.
> 
> Well. 2.6.13 won't boot if I have my Netgear WG511 in the cardbus slot.
> It boots just fine if it isn't inserted, though. If I insert it later
> on, the computer will freeze and won't respond, just like it does on boot.
> 
> 2.6.12.5 works just fine, and I just did make oldconfig and used the
> defaults (except for the hardware monitoring).
> 
> Suggestions, anyone?

Can you try the patch posted to lkml at:
	http://marc.theaimsgroup.com/?l=linux-kernel&m=112541348008047&w=2
from Ivan to see if that helps this?

thanks,

greg k-h

  reply	other threads:[~2005-09-01  2:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  0:17 Linux 2.6.13 Linus Torvalds
2005-08-29  0:43 ` Jesper Juhl
2005-08-29  3:05   ` Linus Torvalds
2005-08-29 10:57 ` Steven Rostedt
2005-08-29 12:17   ` Nigel Cunningham
2005-08-29 12:25     ` Jörn Engel
2005-08-29 12:28       ` Nigel Cunningham
2005-08-29 14:25     ` Antonino A. Daplas
2005-08-29 14:42       ` Steven Rostedt
2005-08-29 14:50       ` Linus Torvalds
2005-08-29 15:44         ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes Steven Rostedt
2005-08-29 18:04         ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes. [take2] Steven Rostedt
2005-08-29 12:19 ` Linux 2.6.13 Nigel Cunningham
2005-08-29 14:22   ` Roland Dreier
2005-09-01  6:24     ` reboot vs poweroff (was: Linux 2.6.13) Meelis Roos
2005-09-01  6:48       ` Nigel Cunningham
2005-09-01  7:33         ` Meelis Roos
2005-09-01 12:32           ` Pierre Ossman
2005-09-01 12:48             ` Nigel Cunningham
2005-09-01 15:15               ` Eric W. Biederman
2005-09-01 15:19                 ` reboot vs poweroff Pierre Ossman
2005-09-01 17:00                   ` Eric W. Biederman
2005-09-01 18:19                     ` Pierre Ossman
2005-09-01 18:23                       ` Eric W. Biederman
2005-09-01 21:11                         ` Nigel Cunningham
2005-09-02  4:46                           ` Eric W. Biederman
2005-09-01 20:22                     ` Pavel Machek
2005-09-02  4:26                       ` Eric W. Biederman
2005-09-01 21:09                 ` reboot vs poweroff (was: Linux 2.6.13) Nigel Cunningham
2005-08-29 18:23 ` Oops in 2.6.13 (was Linux 2.6.13 ) Masoud Sharbiani
2005-08-29 20:13   ` Lee Revell
2005-08-30  3:47     ` Masoud Sharbiani
2005-08-30 22:41 ` Linux 2.6.13 Henrik Persson
2005-09-01  2:29   ` Greg KH [this message]
2005-09-03  9:22     ` Henrik Persson
2005-08-31 12:42 ` Alexandre Buisse
  -- strict thread matches above, loose matches on Subject: below --
2005-08-29  2:34 Jerome Pinot
2005-08-29  3:27 ` Linus Torvalds
2005-08-29 23:57 Ricardo Galli
2005-09-03 16:16 ` Alexey Dobriyan

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=20050901022938.GA27209@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=root@fulhack.info \
    --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