lkml.org 
[lkml]   [2008]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.28-rc2-git1: spitz still won't boot
    On Mon, Nov 03, 2008 at 11:40:35AM +0100, Pavel Machek wrote:
    > > On Friday, 31 of October 2008, Pavel Machek wrote:
    > > > Hi!
    > > >
    > > > ...unfortunately, 2.6.27 contains the 'reset floating' bug, and from
    > > > the point 'reset floating' is fixed, to 2.6.28-rc1, tree will not
    > > > compile, so bisect is quite hard to do. Any ideas?
    > >
    > > Is this a regression from .27?
    >
    > Yes, it is (*).
    > Pavel
    > (*) Okay, so 2.6.27 does not boot due to the 'reset floating' bug.

    I wouldn't say that was a bug. That was by design of Dmitry, which
    I'm far from happy with. If an output is being used to drive a
    reset line, you always want to actively drive it to the inactive
    state for noise immunity reasons.

    > 'reset floating' is fixed in 2.6.28-rc1, and compilation of spitz
    > is fixed in 2.6.28-rc2, but it still will not boot.

    Compilation errors are only going to get worse as ARM continues to
    diversify. We're entirely reliant on sfr's linux-next project to
    find build errors prior to merging, and it is unfortunate that this
    time around, sfr was on vacation on the run up to the merge window.
    Hence, there was very little build coverage of the changes that
    went in during this last merge window. I spent most of the merge
    window fixing up all the shitty patches that people had submitted up
    until that point that either broke compilation or had runtime
    problems.

    > So yes, some new spitz-breaking bug got introduced. But no, 2.6.27
    > will not boot due to other bug. 2.6.26 boots.

    If 2.6.27 doesn't boot even with the reset fixes applied, there's a hell
    of a lot of changes that could be the culpret (and I don't remember much
    that happened before this last merge window.) The only thing I can
    suggest is to bisect with the reset fixes on top.

    This is precisely where we're let down by not having a Zaurus maintainer
    who knows the Zaurus issues inside out, and regularly puts effort into
    building and testing kernels for these platforms. That's a hint for
    anyone who's reading this.

    --
    Russell King
    Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
    maintainer of:


    \
     
     \ /
      Last update: 2008-11-03 12:09    [W:2.173 / U:0.200 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site