Hi, On Mon, Sep 14, 2009 at 04:31:17AM +0100, Ben Hutchings wrote: > On Sun, 2009-09-13 at 22:21 +0200, Patrick Schoenfeld wrote: > > Hi, > > > > Bastian, would you mind *explaining* why you think its justified to > > decrease the severity of this bug to normal? > > > > The bug effectively renders my WLAN useless. I consider that > > quiet having "major effect on the usability of a package without > > rendering it unusable to everyone". So - why do you think it > > doesn't and why do you think just downgrading with no explanation > > is reasonable? > > Since this is a hardware-specific bug, it has absolutely zero impact on > most users.
well, kernel bugs are most likely hardware-specific unless they affect components like filesystem drivers etc. According to the severity description it also does not need to impact other users. > It doesn't cause a crash or hang, It does cause a hang of the driver. It causes broken connections several times a day. It makes WLAN effectively unusuable on this system. Basically it forces me to use a kernel which is not part of the suite i'm using. And causing a crash or a hang every 10-30 minutes wouldn't be important. That would be grave. > and you have a simple workaround. Oh yeah, every 10-30 minutes I can force my system to connect to the WLAN again. Which takes about 30 seconds, because the driver needs to realize that something is wrong. Sometimes this isn't enough and I need to reload the module. This is not really practicable. OTOH I can of course not use the wireless driver and use a cable. If one considers that practicable ;-) > This doesn't even come close to being "important". I disagree, but its not worth to argue about this. For me its a blocker for the use of 2.6.30, so I hope it gets fixed regardless of the severity. Best Regards, Patrick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org