open bugzilla reports

Started by Andrew Morton on Feb 3, 2006 · 5 messages from 4 authors · Last reply Feb 5, 2006

open the first message on its own page

Message details and related content
This is a listing of the 263 bugzilla records which I felt worth keeping an
eye on.  It would be appreciated if the various maintenance teams could
take a look, close off any which are fixed and see if we can fix any which
aren't.

There's probably not a lot of point in replying to this email for any
particular bug: please do that within bugzilla and I can update this list
based upon any bugzilla updates.

If you do reply to this email, please trim the cc list to something
appropriate, thanks.


agp/drm/video/X
===============

[Bug 5163] x crashes at startup
	http://bugzilla.kernel.org/show_bug.cgi?id=5163

alsa
====

[Bug 5398] ES1988 Allegro-1 : No sound after boot
	http://bugzilla.kernel.org/show_bug.cgi?id=5398
[Bug 5420] SiS CMI onboard sound card not working
	http://bugzilla.kernel.org/show_bug.cgi?id=5420
[Bug 5523] Alsa Broken on 2.6.14
	http://bugzilla.kernel.org/show_bug.cgi?id=5523
[Bug 5568] opl3sa driver broken in 2.6.14
	http://bugzilla.kernel.org/show_bug.cgi?id=5568
[Bug 5824] EMU8000 does not depend on SB
	http://bugzilla.kernel.org/show_bug.cgi?id=5824
[Bug 5852] emu10k1 doesn't work
	http://bugzilla.kernel.org/show_bug.cgi?id=5852
[Bug 5126] No sound on Thinkpad X31 (Intel
	http://bugzilla.kernel.org/show_bug.cgi?id=5126
[Bug 5207] Sound system crashes when using the
	http://bugzilla.kernel.org/show_bug.cgi?id=5207
[Bug 5828] mplayer093 crash after update to

653 more lines

Message details and related content
On Fri, Feb 03, 2006 at 03:11:50PM -0800, Andrew Morton wrote:
serial
======

[Bug 5832] Enabling ACPI Plug and Play in kernels
	http://bugzilla.kernel.org/show_bug.cgi?id=5832
This seems to be misfiled.  Why do you think this is a serial bug?
It seems to be talking about parallel ports.
[Bug 5875] quad RS232 port card detected as 8,
	http://bugzilla.kernel.org/show_bug.cgi?id=5875
This seems to be because we have an explicit vendor/device ID listed
in 8250_pci for (according to this bug report) something which isn't
a serial device.  What I don't know is if these vendor/device IDs
also exist for something which is a serial device.  Hence, removing
them could cause more problems than keeping them.  Since it has no
effect other than causing extra ports to appear, this is low priority.
[Bug 5942] serial driver gives up and we get IRQ3
	http://bugzilla.kernel.org/show_bug.cgi?id=5942
No idea what's happening here.  No one else seems to be using IRQ3,
we've disabled the interrupt at the UART, yet we get a stuck IRQ3.
Don't think it's serial related, it just happens that closing the
serial port shows it.
[Bug 5958] CF bluetooth card oopses machine when
	http://bugzilla.kernel.org/show_bug.cgi?id=5958
This isn't a serial bug - it's a bluetooth ldisc bug.  I reported it
to the bluetooth folk back when it first got raised by Pavel.  However,
they seem to be completely disinterested in fixing it.

Unfortunately, there isn't a category for bt crap in bugzilla, otherwise
I'd reassign it.  Please kick the bt folk.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
Message details and related content
quoted
[Bug 5958] CF bluetooth card oopses machine when
	http://bugzilla.kernel.org/show_bug.cgi?id=5958
This isn't a serial bug - it's a bluetooth ldisc bug.  I reported it
to the bluetooth folk back when it first got raised by Pavel.  However,
they seem to be completely disinterested in fixing it.

Unfortunately, there isn't a category for bt crap in bugzilla, otherwise
I'd reassign it.  Please kick the bt folk.
Stick it under Drivers/Other if you want ...

M.
Message details and related content
On Sat, Feb 04, 2006 at 08:47:29AM -0800, Martin J. Bligh wrote:
quoted
quoted
[Bug 5958] CF bluetooth card oopses machine when
	http://bugzilla.kernel.org/show_bug.cgi?id=5958
This isn't a serial bug - it's a bluetooth ldisc bug.  I reported it
to the bluetooth folk back when it first got raised by Pavel.  However,
they seem to be completely disinterested in fixing it.

Unfortunately, there isn't a category for bt crap in bugzilla, otherwise
I'd reassign it.  Please kick the bt folk.
Stick it under Drivers/Other if you want ...
It _is_ under Networking/Other, yet akpm still thinks it's a serial
bug.  I'm not sure why though, I've fully explained why it isn't
a serial problem in the bug comments.

akpm is buggy and needs fixing.  Where do I file this bug? 8)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
Message details and related content
On So 04-02-06 23:14:26, Russell King wrote:
On Sat, Feb 04, 2006 at 08:47:29AM -0800, Martin J. Bligh wrote:
quoted
quoted
quoted
[Bug 5958] CF bluetooth card oopses machine when
	http://bugzilla.kernel.org/show_bug.cgi?id=5958
This isn't a serial bug - it's a bluetooth ldisc bug.  I reported it
to the bluetooth folk back when it first got raised by Pavel.  However,
they seem to be completely disinterested in fixing it.

Unfortunately, there isn't a category for bt crap in bugzilla, otherwise
I'd reassign it.  Please kick the bt folk.
Stick it under Drivers/Other if you want ...
It _is_ under Networking/Other, yet akpm still thinks it's a serial
bug.  I'm not sure why though, I've fully explained why it isn't
a serial problem in the bug comments.

akpm is buggy and needs fixing.  Where do I file this bug? 8)
It would be nice to create Networking/Bluetooth category, so there's
logical place to file such bugs under...
								Pavel
-- 
Thanks, Sharp!
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help