I can confirm that reverting commit
7639e962234c76031d1ddf436def7fd9602be560 fixes the problem. Also,
there seem to be plenty of other people reporting the same boot
locking:
http://groups.google.com/group/fa.linux.kernel/msg/cc0453677be44a9e
http://bbs.archlinux.org/viewtopic.php?pid=245313
http://bugs.archlinux.org/task/6845
http://www.usenetlinux.com/archive/topic.php/t-757515.html
Please consider reverting this patch in upstream.
Thank you for your time,
Marcos
On 4/23/07, Marcos Pinto <[email protected]> wrote:
On 4/23/07, Jan Beulich <[email protected]> wrote:
> Given that all of the reports are in cases when the adjustment is *not*
> being done (and only a message is being printed), I can only assume that
> the breakage results from the adding of PCI_BASE_ADDRESS_SPACE_IO
> into the resource flags. I considered this unconditional setting of the flags
> odd already in the original code, and added this extra flag only for
> consistency reasons (because the settings reported by X indicated that
> this was missing). Perhaps the adjustment (original and the added
> extra flag) shouldn't be done if IORESOURCE_IO wasn't already set.
> Perhaps one of those seeing the issue could try out returning from the
> function right after that printk(), without any adjustment to the flags.
>
> Jan
>
>
-
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/
[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]
