Re: 2.6.38-rc3 regression on parisc: segfaults

[Meelis Roos]

> > I have been testing devel kernels on SMP L1000 successfully until 
> > 2.6.38-rc2-00324-g70d1f36 included. The testing means booting the new 
> > kernel and running aptitude to update to current debian unstable.
> > 
> > Now I tried 2.6.38-rc3 and got a crash from aptitude on 2 out of 2 
> > tries. Maybe aptitude was broken inbetween but it looks like a kernel 
> > bug. Retried 2.6.38-rc2-00324-g70d1f36 and that seemed to work fine so 
> > it's more likely a kernel problem.
> > 
> > What additional information can I provide?
> 
> Probably a bisection, if you could.  There have been no parisc patches
> between -rc2 and -rc3, so it's coming from outside the architecture.

The result is strange :(

6b28405395f7ec492ea69f541cc774adcb9e00ca is the first bad commit
commit 6b28405395f7ec492ea69f541cc774adcb9e00ca
Author: Axel KÃllhofer <AxelKoellhofer@xxxxxx>
Date:   Sat Jan 22 14:33:50 2011 -0600

    staging: r8712u: Add new device IDs

    This patch adds several new device ids to the r8712u staging driver.
    The new ids were retrieved from latest vendor driver (v2.6.6.0.20101111)
    downloadable from www.realtek.com.tw

    Signed-off-by: Axel Koellhofer <AxelKoellhofer@xxxxxx>
    Signed-off-by: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
    Cc: Stable <stable@xxxxxxxxxx> [2.6.37]
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>

:040000 040000 185c3d2c1e98cc99009bfb772ed0779410784110 f5aa903931116f28f803003f594fec3b2a29a6f6 M      drivers

Seems absolutely unrelated - I do not have staging enabled so so no 
CONFIG_R8712U either.

The "bad" bisects were clearly bad and failed quicky during aptitude 
list update but the good ones might have needed more stress... or it is 
some alignment-like problem. Will try again starting from these bad 
bisects to narrow it down, and stress seemingly good ones better.

-- 
Meelis Roos (mroos@xxxxxxxx)
--
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/