Re: 2.6.20-rc2: known unfixed regressions (v2)

[Ismail Dönmez]

31 Ara 2006 Paz 02:47 tarihinde, Adrian Bunk şunları yazmıştı: 
[...]
> Subject: ALSA: No sound in KDE with intel hda
> References : http://lkml.org/lkml/2006/12/30/73
> Submitter  : Ismail Dönmez <[EMAIL PROTECTED]>
> Status : unknown

Just tried with 2.6.18.6 and aRts still have no sound, there must be something 
else broken on my side.

Thanks,
ismail

-- 
2 + 2 = 5 for very large values of 2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Fri, Dec 29, 2006 at 10:21:36PM -0300, Horst H. von Brand wrote:
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
> 
> [...]
> 
> > Subject: BUG at fs/buffer.c:1235 when using gdb
> > References : http://lkml.org/lkml/2006/12/17/134
> > Submitter  : Andrew J. Barr <[EMAIL PROTECTED]>
> > Fixed-By   : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> > Commit : 8701ea957dd2a7c309e17c8dcde3a64b92d8aec0
> > Status : fixed in -rc2
> 
> This I see in Fedora rawhide i686 2.6.19-1.2891.fc7 (BZ'd at
> 

2.6.19-1.2891.fc7 is based on 2.6.20-rc1-git5, and it's therefore 
expected that it contains this bug.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Horst H. von Brand]

Adrian Bunk <[EMAIL PROTECTED]> wrote:

[...]

> Subject: BUG at fs/buffer.c:1235 when using gdb
> References : http://lkml.org/lkml/2006/12/17/134
> Submitter  : Andrew J. Barr <[EMAIL PROTECTED]>
> Fixed-By   : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> Commit : 8701ea957dd2a7c309e17c8dcde3a64b92d8aec0
> Status : fixed in -rc2

This I see in Fedora rawhide i686 2.6.19-1.2891.fc7 (BZ'd at

-- 
Dr. Horst H. von Brand   User #22616 counter.li.org
Departamento de InformaticaFono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile   Fax:  +56 32 2797513
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Daniel Barkalow]

On Fri, 29 Dec 2006, Adrian Bunk wrote:

> On Fri, Dec 29, 2006 at 01:14:13PM -0500, Daniel Barkalow wrote:
> 
> > There's also http://lkml.org/lkml/2006/12/21/47; the included patch break 
> > my nVidia devices and probably all PCIX devices, so it's not right, but 
> > something has to be done to fix ATI. My guess is a quirk to say that 
> > pci_intx doesn't work on certain devices and should just be skipped, but 
> > I'm not sure if it's just in combination with MSI or not.
> 
> This:
> - does not seem to be a regression and
> - missing MSI support is not such a big problem.
> 
> Considering how many problems patches in this area tend to cause on 
> different hardware, I'm even inclined to say that such patches should 
> only be added during the 2 weeks merge window before -rc1.

(I was only talking about the first issue/patch as being a regression, 
obviously, and forgot that there was more to the email I cited.)

Ah, okay. I somehow missed that all of the devices that were reported 
to break with the MSI change in mainline doesn't support MSI in mainline. 
Actually, I wouldn't be surprised if this issue applied to audio on ATI 
SB450 and later, which (I think) use the hda_intel driver, which supports 
MSI (although I guess it's still defaulting to disabled). If this is true, 
it would be a regression since 2.6.19.

The addition of a quirk to not use pci_intx with MSI on ATI PCI devices 
should be safe (until 2.6.20-rc1, this was the usual kernel behavior), but 
is clearly not critical if mainline doesn't use MSI with any such devices 
anyway.

-Daniel
*This .sig left intentionally blank*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Fri, Dec 29, 2006 at 01:07:10PM -0500, Ben Collins wrote:
> On Thu, 2006-12-28 at 23:39 +0100, Adrian Bunk wrote:
> > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> > 
> > If you find your name in the Cc header, you are either submitter of one
> > of the bugs, maintainer of an affectected subsystem or driver, a patch
> > of you caused a breakage or I'm considering you in any other way possibly
> > involved with one or more of these issues.
> > 
> > Due to the huge amount of recipients, please trim the Cc when answering.
> 
> > Subject: i386: Oops in __find_get_block()
> > References : http://lkml.org/lkml/2006/12/16/138
> > Submitter  : Ben Collins <[EMAIL PROTECTED]>
> >  Daniel Holbach <[EMAIL PROTECTED]>
> > Status : unknown
> 
> I believe this is the same bug as I've seen reported about gdb. I'd have
> to find the thread/information regarding it. Not sure if it was fixed
> already.

Subject: BUG at fs/buffer.c:1235 when using gdb
References : http://lkml.org/lkml/2006/12/17/134
Submitter  : Andrew J. Barr <[EMAIL PROTECTED]>
Fixed-By   : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Commit : 8701ea957dd2a7c309e17c8dcde3a64b92d8aec0
Status : fixed in -rc2

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Fri, Dec 29, 2006 at 01:14:13PM -0500, Daniel Barkalow wrote:

> There's also http://lkml.org/lkml/2006/12/21/47; the included patch break 
> my nVidia devices and probably all PCIX devices, so it's not right, but 
> something has to be done to fix ATI. My guess is a quirk to say that 
> pci_intx doesn't work on certain devices and should just be skipped, but 
> I'm not sure if it's just in combination with MSI or not.

This:
- does not seem to be a regression and
- missing MSI support is not such a big problem.

Considering how many problems patches in this area tend to cause on 
different hardware, I'm even inclined to say that such patches should 
only be added during the 2 weeks merge window before -rc1.

>   -Daniel

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Daniel Barkalow]

There's also http://lkml.org/lkml/2006/12/21/47; the included patch break 
my nVidia devices and probably all PCIX devices, so it's not right, but 
something has to be done to fix ATI. My guess is a quirk to say that 
pci_intx doesn't work on certain devices and should just be skipped, but 
I'm not sure if it's just in combination with MSI or not.

-Daniel
*This .sig left intentionally blank*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Ben Collins]

On Thu, 2006-12-28 at 23:39 +0100, Adrian Bunk wrote:
> This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> 
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you caused a breakage or I'm considering you in any other way possibly
> involved with one or more of these issues.
> 
> Due to the huge amount of recipients, please trim the Cc when answering.

> Subject: i386: Oops in __find_get_block()
> References : http://lkml.org/lkml/2006/12/16/138
> Submitter  : Ben Collins <[EMAIL PROTECTED]>
>  Daniel Holbach <[EMAIL PROTECTED]>
> Status : unknown

I believe this is the same bug as I've seen reported about gdb. I'd have
to find the thread/information regarding it. Not sure if it was fixed
already.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Thu, Dec 28, 2006 at 08:51:06PM -0800, David Miller wrote:
> From: "Horst H. von Brand" <[EMAIL PROTECTED]>
> Date: Thu, 28 Dec 2006 22:36:02 -0300
> 
> > Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> > 
> > Add that on SPARC64 boot fails due to missing /dev/root. Vanilla 2.6.19 and
> > 2.6.19.1 work fine, before 2.6.20-rc1 it broke. I checked the initrds for
> > both versions, the only difference "diff -Nur" finds between the unpacked
> > initrds are the modules themselves (obviously).
> 
> Did you report this will all relevant details on [EMAIL PROTECTED]
> so that the sparc64 maintainers can analyze the problem?
> 
> I didn't see the report there else I would be looking into it.
>...

I did copy the email to both sparclinux and you when I asked Horst 
whether it's still present in the latest kernel, and therefore his 
answer that it does the day before yesterday should have reached you.

The thread is "Re: 2.6.19 (current from git) on SPARC64: Can't mount /".

Is there anything I can improve to catch your intention?
Is "reply with fullquote + question + adding Cc's" somehow suboptimal?

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Thu, Dec 28, 2006 at 10:36:02PM -0300, Horst H. von Brand wrote:
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> 
> Add that on SPARC64 boot fails due to missing /dev/root. Vanilla 2.6.19 and
> 2.6.19.1 work fine, before 2.6.20-rc1 it broke. I checked the initrds for
> both versions, the only difference "diff -Nur" finds between the unpacked
> initrds are the modules themselves (obviously).

Sorry, I knew about this and somehow forgot to add it to my list.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[David Miller]

From: "Horst H. von Brand" <[EMAIL PROTECTED]>
Date: Thu, 28 Dec 2006 22:36:02 -0300

> Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> 
> Add that on SPARC64 boot fails due to missing /dev/root. Vanilla 2.6.19 and
> 2.6.19.1 work fine, before 2.6.20-rc1 it broke. I checked the initrds for
> both versions, the only difference "diff -Nur" finds between the unpacked
> initrds are the modules themselves (obviously).

Did you report this will all relevant details on [EMAIL PROTECTED]
so that the sparc64 maintainers can analyze the problem?

I didn't see the report there else I would be looking into it.

Please don't report sparc64 bugs here, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Horst H. von Brand]

Adrian Bunk <[EMAIL PROTECTED]> wrote:
> This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.

Add that on SPARC64 boot fails due to missing /dev/root. Vanilla 2.6.19 and
2.6.19.1 work fine, before 2.6.20-rc1 it broke. I checked the initrds for
both versions, the only difference "diff -Nur" finds between the unpacked
initrds are the modules themselves (obviously).
-- 
Dr. Horst H. von Brand   User #22616 counter.li.org
Departamento de InformaticaFono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile   Fax:  +56 32 2797513
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Greg KH]

On Thu, Dec 28, 2006 at 03:17:53PM -0800, Linus Torvalds wrote:
> 
> 
> On Fri, 29 Dec 2006, Adrian Bunk wrote:
> > 
> > In Linus' tree, it currently only depends on EXPERIMENTAL.
> > 
> > It seems commit 009af1ff78bfc30b9a27807dd0207fc32848218a wasn't intended 
> > for Linus?
> 
> I think we should just remove it.
> 
> It's broken.
> 
> Nobody cares.

I agree, that's why I thought I had added a patch in the last PCI queue
to you to just disable the config option and was going to rip out the
code entirely for the next release.  I'll make sure to add the config
option patch to the next round of PCI patches to you.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Linus Torvalds]

On Fri, 29 Dec 2006, Adrian Bunk wrote:
> 
> In Linus' tree, it currently only depends on EXPERIMENTAL.
> 
> It seems commit 009af1ff78bfc30b9a27807dd0207fc32848218a wasn't intended 
> for Linus?

I think we should just remove it.

It's broken.

Nobody cares.

If people want to do concurrent stuff at bootup, it should be the _other_ 
buses (like USB, IDE or SCSI or anything like that, that actually has 
operations that can delay) that end up asynchronous. And I think we could 
have some generic functionality for the drivers themselves to do their 
probing in parallel. But I think the PCI one was just a mistake.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Adrian Bunk]

On Thu, Dec 28, 2006 at 02:57:06PM -0800, Greg KH wrote:
> On Thu, Dec 28, 2006 at 11:39:09PM +0100, Adrian Bunk wrote:
> > 
> > Subject: PCI_MULTITHREAD_PROBE breakage
> > References : http://lkml.org/lkml/2006/12/12/21
> > Submitter  : Ben Castricum <[EMAIL PROTECTED]>
> > Caused-By  : Greg Kroah-Hartman <[EMAIL PROTECTED]>
> >  commit 009af1ff78bfc30b9a27807dd0207fc32848218a
> > Status : known to break many drivers; revert?
> 
> PCI_MULTITHREAD_PROBE is now only able to be enabled if you also enable
> CONFIG_BROKEN, so this can be removed from your list.

In Linus' tree, it currently only depends on EXPERIMENTAL.

It seems commit 009af1ff78bfc30b9a27807dd0207fc32848218a wasn't intended 
for Linus?

> thanks,
> 
> greg k-h

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.20-rc2: known unfixed regressions

[Greg KH]

On Thu, Dec 28, 2006 at 11:39:09PM +0100, Adrian Bunk wrote:
> 
> Subject: PCI_MULTITHREAD_PROBE breakage
> References : http://lkml.org/lkml/2006/12/12/21
> Submitter  : Ben Castricum <[EMAIL PROTECTED]>
> Caused-By  : Greg Kroah-Hartman <[EMAIL PROTECTED]>
>  commit 009af1ff78bfc30b9a27807dd0207fc32848218a
> Status : known to break many drivers; revert?

PCI_MULTITHREAD_PROBE is now only able to be enabled if you also enable
CONFIG_BROKEN, so this can be removed from your list.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/