Prev: mmu notifier calls in apply_to_page_range()
Next: Yet another 2.6.35 regression (AGP)? (resend)
From: Woody Suwalski on 9 Jul 2010 11:10
I have found one system, where 2.6.35 does not work (as tested with rc3
and rc4)
That Intel system has no problems in 2.6.33.x nor 2.6.34.0.

The problem seems to be in AGP - I can boot if I specify "agp=off" - but
of course only in text mode...
There seems to be a hard lock-up, so the only way to show the crash is
by picture 8-)

Since I do not build kernel on that machine, I did not do any bisect
tests, however if someone is interested in digging deeper, I can try...
Preferably a patch to try out ;-)

This bug seems to be different then
https://bugzilla.kernel.org/show_bug.cgi?id=16179

Should it be blamed on BIOS (the conflict indicated just before the crash)?

Thanks, Woody


From: Jesse Barnes on 9 Jul 2010 12:00
On Fri, 9 Jul 2010 10:21:56 -0400
Woody Suwalski <terraluna977(a)gmail.com> wrote:

> I have found one system, where 2.6.35 does not work (as tested with rc3
> and rc4)
> That Intel system has no problems in 2.6.33.x nor 2.6.34.0.
>
> The problem seems to be in AGP - I can boot if I specify "agp=off" - but
> of course only in text mode...
> There seems to be a hard lock-up, so the only way to show the crash is
> by picture 8-)
>
> Since I do not build kernel on that machine, I did not do any bisect
> tests, however if someone is interested in digging deeper, I can try...
> Preferably a patch to try out ;-)
>
> This bug seems to be different then
> https://bugzilla.kernel.org/show_bug.cgi?id=16179
>
> Should it be blamed on BIOS (the conflict indicated just before the crash)?

Well even if the BIOS is doing something bad, if we handled it in
earlier kernels we should handle it today. So this sounds like a
regression.

A bisect should help if it was working before, can you do that?

--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Woody Suwalski on 9 Jul 2010 12:30
Jesse Barnes wrote:
> On Fri, 9 Jul 2010 10:21:56 -0400
> Woody Suwalski<terraluna977(a)gmail.com> wrote:
>
>
>> I have found one system, where 2.6.35 does not work (as tested with rc3
>> and rc4)
>> That Intel system has no problems in 2.6.33.x nor 2.6.34.0.
>>
>> The problem seems to be in AGP - I can boot if I specify "agp=off" - but
>> of course only in text mode...
>> There seems to be a hard lock-up, so the only way to show the crash is
>> by picture 8-)
>>
>> Since I do not build kernel on that machine, I did not do any bisect
>> tests, however if someone is interested in digging deeper, I can try...
>> Preferably a patch to try out ;-)
>>
>> This bug seems to be different then
>> https://bugzilla.kernel.org/show_bug.cgi?id=16179
>>
>> Should it be blamed on BIOS (the conflict indicated just before the crash)?
>>
> Well even if the BIOS is doing something bad, if we handled it in
> earlier kernels we should handle it today. So this sounds like a
> regression.
>
> A bisect should help if it was working before, can you do that?
>
>
OK, I have never really done the brute-force bissecting, but there is
always first time...
Will try to do it over the weekend...

Unless U will be visiting Ottawa and want to do it yourself ;-)

Woody

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jesse Barnes on 9 Jul 2010 14:00
On Fri, 9 Jul 2010 12:27:43 -0400
Woody Suwalski <terraluna977(a)gmail.com> wrote:

> Jesse Barnes wrote:
> > On Fri, 9 Jul 2010 10:21:56 -0400
> > Woody Suwalski<terraluna977(a)gmail.com> wrote:
> >
> >
> >> I have found one system, where 2.6.35 does not work (as tested with rc3
> >> and rc4)
> >> That Intel system has no problems in 2.6.33.x nor 2.6.34.0.
> >>
> >> The problem seems to be in AGP - I can boot if I specify "agp=off" - but
> >> of course only in text mode...
> >> There seems to be a hard lock-up, so the only way to show the crash is
> >> by picture 8-)
> >>
> >> Since I do not build kernel on that machine, I did not do any bisect
> >> tests, however if someone is interested in digging deeper, I can try...
> >> Preferably a patch to try out ;-)
> >>
> >> This bug seems to be different then
> >> https://bugzilla.kernel.org/show_bug.cgi?id=16179
> >>
> >> Should it be blamed on BIOS (the conflict indicated just before the crash)?
> >>
> > Well even if the BIOS is doing something bad, if we handled it in
> > earlier kernels we should handle it today. So this sounds like a
> > regression.
> >
> > A bisect should help if it was working before, can you do that?
> >
> >
> OK, I have never really done the brute-force bissecting, but there is
> always first time...
> Will try to do it over the weekend...

Great, thanks.

> Unless U will be visiting Ottawa and want to do it yourself ;-)

Nope, no immediate plans. :)

--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Maciej Rutecki on 12 Jul 2010 11:30
On piątek, 9 lipca 2010 o 16:21:56 Woody Suwalski wrote:
> I have found one system, where 2.6.35 does not work (as tested with rc3
> and rc4)
> That Intel system has no problems in 2.6.33.x nor 2.6.34.0.
>
> The problem seems to be in AGP - I can boot if I specify "agp=off" - but
> of course only in text mode...
> There seems to be a hard lock-up, so the only way to show the crash is
> by picture 8-)
>
> Since I do not build kernel on that machine, I did not do any bisect
> tests, however if someone is interested in digging deeper, I can try...
> Preferably a patch to try out ;-)
>
> This bug seems to be different then
> https://bugzilla.kernel.org/show_bug.cgi?id=16179
>
> Should it be blamed on BIOS (the conflict indicated just before the crash)?
>
> Thanks, Woody

I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=16369
for your bug report, please add your address to the CC list in there, thanks!


--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: mmu notifier calls in apply_to_page_range()
Next: Yet another 2.6.35 regression (AGP)? (resend)