Bug#546213: severity of 546213 is normal
On Fri, Sep 25, 2009 at 04:19:52AM -0400, Andres Salomon wrote: On Fri, 25 Sep 2009 10:12:06 +0200 Patrick Schoenfeld schoenf...@debian.org wrote: On Thu, Sep 24, 2009 at 11:01:45PM -0400, Andres Salomon wrote: This sounds an awful lot like a firmware bug, as well (for which we don't have the source code for). Perhaps you could try downgrading your firmware-iwlwifi package and let us know whether that fixes the issue? It sounds like the driver itself is doing the right thing by detecting a firmware problem and reloading. Hmm. No, I haven't yet considered this. The thing is: The driver and the firmware work flawless in 2.6.29, so I guess that this might be a firmware problem, but more likely the driver changed since then and doesn't work with the firmware anymore. But AFAICT there were new release.. So you've verified that you were using the same version of firmware-iwlwifi with 2.6.29 and 2.6.30 then, yes? I thought so, but currently I don't have a working kernel image (as I reinstalled for some other reasons a while ago) for 2.6.29 to verify that my memory is correct. However I found that bug #548749, which suggests that it might be a firmware bug nevertheless, so I'll give *that* a try. Should have tried that first. 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
Bug#546213: severity of 546213 is normal
On Thu, Sep 24, 2009 at 11:01:45PM -0400, Andres Salomon wrote: This sounds an awful lot like a firmware bug, as well (for which we don't have the source code for). Perhaps you could try downgrading your firmware-iwlwifi package and let us know whether that fixes the issue? It sounds like the driver itself is doing the right thing by detecting a firmware problem and reloading. Hmm. No, I haven't yet considered this. The thing is: The driver and the firmware work flawless in 2.6.29, so I guess that this might be a firmware problem, but more likely the driver changed since then and doesn't work with the firmware anymore. But AFAICT there were new release.. Regards, Patrick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546213: severity of 546213 is normal
On Fri, 25 Sep 2009 10:12:06 +0200 Patrick Schoenfeld schoenf...@debian.org wrote: On Thu, Sep 24, 2009 at 11:01:45PM -0400, Andres Salomon wrote: This sounds an awful lot like a firmware bug, as well (for which we don't have the source code for). Perhaps you could try downgrading your firmware-iwlwifi package and let us know whether that fixes the issue? It sounds like the driver itself is doing the right thing by detecting a firmware problem and reloading. Hmm. No, I haven't yet considered this. The thing is: The driver and the firmware work flawless in 2.6.29, so I guess that this might be a firmware problem, but more likely the driver changed since then and doesn't work with the firmware anymore. But AFAICT there were new release.. So you've verified that you were using the same version of firmware-iwlwifi with 2.6.29 and 2.6.30 then, yes? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546213: severity of 546213 is normal
On Mon, 14 Sep 2009 10:33:21 +0200 Patrick Schoenfeld schoenf...@debian.org wrote: 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. This sounds an awful lot like a firmware bug, as well (for which we don't have the source code for). Perhaps you could try downgrading your firmware-iwlwifi package and let us know whether that fixes the issue? It sounds like the driver itself is doing the right thing by detecting a firmware problem and reloading. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546213: severity of 546213 is normal
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
Bug#546213: severity of 546213 is normal
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? 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
Bug#546213: severity of 546213 is normal
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. It doesn't cause a crash or hang, and you have a simple workaround. This doesn't even come close to being important. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
