Re: 2.6.20.7 locking up hard on boot

[Len Brown]

On Saturday 21 April 2007 06:54, Marcos Pinto wrote:
> It took me several hours, but I just got done combing things over with
> bisect as Greg requested.  This is what git spit out as the problem
> patch in the end:
> 
> 7639e962234c76031d1ddf436def7fd9602be560 is first bad commit
> commit 7639e962234c76031d1ddf436def7fd9602be560
> Author: Jan Beulich <jbeulich@xxxxxxxxxx>
> Date:   Tue Mar 13 14:04:11 2007 -0400
> 
>     adjust legacy IDE resource setting (v2)
> 
>     adjust legacy IDE resource setting (v2)
> 
>     The change to force legacy mode IDE channels' resources to fixed non-zero
>     values confuses (at least some versions of) X, because the values reported
>     by the kernel and those readable from PCI config space aren't consistent
>     anymore.  Therefore, this patch arranges for the respective BARs to also
>     get updated if possible.
> 
>     Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
>     Acked-by: Alan Cox <alan@xxxxxxxxxx>
>     Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
>     Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
>     Cc: Chuck Ebbert <cebbert@xxxxxxxxxx>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
> 
> :040000 040000 d4ee6822208dc3e205bfc92fd30121e7894e63a9
> 5155044aa75f0d2671e7f5081f5b2999f24034bd M      drivers
> bisect run success
> 

Looks like others are seeing failures due to this patch also:
http://bugzilla.kernel.org/show_bug.cgi?id=7562

-Len

-
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/