Re: Reporting result of pci=assign-busses to lkml


Hi Russ,

in case you are still wondering about this...

There is a good explanation of the original reasoning here:
   http://lists.opensuse.org/opensuse-bugs/2007-02/msg00149.html

And there are plans to remove the message here
   http://www.uwsg.iu.edu/hypermail/linux/kernel/0707.3/2879.html

I am still seeing the warning in 2.6.23-rc3, but it makes no difference
if I specify pci=assign-busses ... everything seems fine either way.

Cheers,
Mathis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Reporting result of pci=assign-busses to lkml
  - From: "Russ Dill" <[email protected]>

Prev by Date: Re: [PATCH 18/25][V3] turn priviled operations into macros in entry.S
Next by Date: Re: [2.6 patch] UML: "extern inline" -> "static inline"
Previous by thread: Reporting result of pci=assign-busses to lkml
Next by thread: 2.6.23-rc2-mm2 -- INFO: inconsistent lock state -- "modprobe -r ipw2200"
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]