Re: 184.108.40.206 locking up hard on boot
From: Marcos Pinto
Date: Tue Apr 24 2007 - 15:11:23 EST
I can confirm that reverting commit
7639e962234c76031d1ddf436def7fd9602be560 fixes the problem. Also,
there seem to be plenty of other people reporting the same boot
Please consider reverting this patch in upstream.
Thank you for your time,
On 4/23/07, Marcos Pinto <markybob@xxxxxxxxx> wrote:
On 4/23/07, Jan Beulich <jbeulich@xxxxxxxxxx> 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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/