Re: Bug#404143: Fans unreliable under load, permanent memory leak
Hi *, this is indeed a severe issue which requires all our attention and care to solve or circumvent in order for nobodies boxes to get any harm, you know how expensive these laptops are. I basically see 3 solutions/workarounds: 1. the brutal one: deactivate ACPI in 2.6.18, have the bios keep control of the fans - better a noisy laptop until I upgrade the kernel than a fried box. 2. port 2.6.19 ACPI - noop because way too much work, unless someone "crazy enough" to accomplish this task. 3. go for 2.6.19 Documenting arbitrary breakage in the release notes is not a solution, just consider how well manuals are usually read (if at all). Users will end with damaged hardware and blame us for it. We released woody with disabled ide dma due to somewhat similar issues (boxes hanging), so disabling ACPI in 2.6.18 and going for a 2.6.19 based 4.0r1 ASAP seems the best thing to me personally, but this is of course up for discussion. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
debian-kernel@lists.debian.org
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > forwarded 404216 > http://marc.theaimsgroup.com/?l=linux-sparc&m=116690324132632&w=2 Bug#404216: linux-image-2.6.18-3-sparc64: Ooops during boot on Netra X1 in function isa_dev_get_resource Noted your statement that Bug has been forwarded to http://marc.theaimsgroup.com/?l=linux-sparc&m=116690324132632&w=2. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400488: no fans after S3 sleep on many laptops
Hi Riku! You wrote: > > With the kernel from linux-image-2.6.18-2-686, fans for my laptop > > (HP nc6120) don't work anymore after an S3 suspend/resume cycle. > > Did this work with older kernels? Yes, it worked fine with kernels prior to 2.6.17. > > I can very well imagine that you guys don't want to include these > > patches in the default etch kernel at this time > > There is quite a few patches in that bugreport, and atleast some of them > seem to cause regressions. If you can provide a patch agains debian's > kernel version, and you are confident it will not break anyone elses > system, the patch will be much more likely considered. Well, I've been running I kernel with the patches from the upstream bug report and the other ralated issue #5534 (upstream), #404143 (debian), and that seems to work perfectly here. The patches are: - http://bugzilla.kernel.org/attachment.cgi?id=9255&action=view - http://bugzilla.kernel.org/attachment.cgi?id=9337&action=view - http://bugzilla.kernel.org/attachment.cgi?id=8951&action=view - http://bugzilla.kernel.org/attachment.cgi?id=8952&action=view The last of those seems to have been superseded by http://bugzilla.kernel.org/attachment.cgi?id=9746&action=view (see http://bugzilla.kernel.org/show_bug.cgi?id=5534). I'm not at all a kernel expert, and I really can't say anything about the stability of these pacthes, except that they work for me. Greetings, Bas. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: no fans after S3 sleep on many laptops
Processing commands for [EMAIL PROTECTED]: > retitle 400488 no fans after S3 sleep on several HP laptop models Bug#400488: no fans after S3 sleep on many laptops Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400488: no fans after S3 sleep on many laptops
retitle 400488 no fans after S3 sleep on several HP laptop models thanks Hi, > With the kernel from linux-image-2.6.18-2-686, fans for my laptop > (HP nc6120) don't work anymore after an S3 suspend/resume cycle. Did this work with older kernels? > I can very well imagine that you guys don't want to include these > patches in the default etch kernel at this time There is quite a few patches in that bugreport, and atleast some of them seem to cause regressions. If you can provide a patch agains debian's kernel version, and you are confident it will not break anyone elses system, the patch will be much more likely considered. Updating title since the kernel.org bugreport does not mention any non-HP laptops affected. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404143: Fans unreliable under load, permanent memory leak
On Sat, Dec 23, 2006 at 11:50:40AM +0100, Andreas Barth wrote: > * Sven Luther ([EMAIL PROTECTED]) [061222 05:42]: > > On Fri, Dec 22, 2006 at 12:53:09PM +0100, Marc 'HE' Brockschmidt wrote: > > > maximilian attems <[EMAIL PROTECTED]> writes: > > > > On Fri, Dec 22, 2006 at 11:28:29AM +0100, Marc 'HE' Brockschmidt wrote: > > > >> Fix it or document it, I don't care. But the current state is not > > > >> releasable. > > > > we are not talking about "a" patch. > > > > what you need is an backport of the 2.6.19 acpi release to 2.6.18. > > > > > > Read again what I wrote. I will not allow Debian to release with a > > > Kernel that may damage hardware without even a notice in the release > > > notes. If you are not able to fix it, note that you have provided a > > > broken kernel. > > > > Cool, let's delay etch a couple of weeks and move to a (now released) 2.6.19 > > kernel, to solve this issue. > > Sven, stop this! Why ? /me guesses that even though debian is about free software, there are many who feel that freedom of speach is to be banned. Do you also follow that line of thought ? Was it not enough that some people felt that i should be burned on the stack for having send mails while i was not at my best ? Really, this kind of behavior is disgusting. > I can remember well how you promised that moving to > 2.6.18 will magically solve almost all of our issues - 6 (or more) > release critical bugs against 2.6.18 don't show that this has worked so > well. Please try helping us on solutions rather then breaking things > again. I did not promise anything such. I simply stated at that time, that there where many RC issues which where already fixed in the 2.6.18 tree, and which would be a pain to backport to the 2.6.17 tree. Quite a different thing, don't you think ? I personally will need to maintain 2.6.19+ backports to etch, because there is no sane way to get Efika support in 2.6.18 without lot of work. > Please try to look at it from another perspective: > > Consider you have bought such a laptop, and you install Debian. You have > even read the release notes first. Everything works well. Until one > day you notice your laptop gets too warm, and eventually even breaks > because of this. On deeper research, you notice that this issue was > well-known to Debian, but they refused to deal with it at all. How would > you feel as a user? I think this is an unacceptable perspective. Bah. hardware which can be broken by software is broken. That said, if in fact this is not a bug of the bios as was first mentioned here, but that the linux support is not able to cope with some not usual but legal features of acpi, then it is another matter. But you should *NEVER* try to stop discussion about the subject, or bash on someone for writing a single sentence as i did. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#400488: no fans after S3 sleep on many laptops
Processing commands for [EMAIL PROTECTED]: > severity 400488 critical Bug#400488: no fans after S3 sleep on many laptops Severity set to `critical' from `important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400488: no fans after S3 sleep on many laptops
severity 400488 critical thanks Bastian Blank wrote: > > With the kernel from linux-image-2.6.18-2-686, fans for my laptop > > (HP nc6120) don't work anymore after an S3 suspend/resume cycle. This > > causes the system to spontaneously shutdown under load causing data > > loss (or posibly it might even break the hardware), ergo the grave > > severity. > > It does not fail for everyone, so grave is not appropriate. Indeed, critial is more appropriate, as this bug causes data loss and hardware damage. IMO, the sitation is similar to bug #404143: like Andi said there: > Consider you have bought such a laptop, and you install Debian. You have > even read the release notes first. Everything works well. Until one > day you notice your laptop gets too warm, and eventually even breaks > because of this. On deeper research, you notice that this issue was > well-known to Debian, but they refused to deal with it at all. How would > you feel as a user? I think this is an unacceptable perspective. I can very well imagine that you guys don't want to include these patches in the default etch kernel at this time, but please document it in the release notes, make the kernel refuse to run on this hardware, or make the user aware of the problem in some other way. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404198: Repeated XFree86 crashes related to a kernel bug according to dmesg :: dmesg files
Jean-Alex wrote: > XFree86 has crashed 4 time since this morning and my concern is fastly > growing. > > Last dmesg extract below and older ones in the attached file. > > Some interesting point : this time it's kdeinit, and for what I saw, > especially kicker, who crashed in the first place, before the Xserver > eventually crashed too in a matter of seconds... > > last dmesg output : > -- > > kernel BUG at vmscan.c:433! > invalid operand: > CPU:0 > EIP:0010:[]Tainted: P ^^ You're running a proprietary, closed-source driver; probably the binary driver by ATI. Does the kernel crash w/o the ATI driver as well? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404143: Fans unreliable under load, permanent memory leak
* Sven Luther ([EMAIL PROTECTED]) [061222 05:42]: > On Fri, Dec 22, 2006 at 12:53:09PM +0100, Marc 'HE' Brockschmidt wrote: > > maximilian attems <[EMAIL PROTECTED]> writes: > > > On Fri, Dec 22, 2006 at 11:28:29AM +0100, Marc 'HE' Brockschmidt wrote: > > >> Fix it or document it, I don't care. But the current state is not > > >> releasable. > > > we are not talking about "a" patch. > > > what you need is an backport of the 2.6.19 acpi release to 2.6.18. > > > > Read again what I wrote. I will not allow Debian to release with a > > Kernel that may damage hardware without even a notice in the release > > notes. If you are not able to fix it, note that you have provided a > > broken kernel. > > Cool, let's delay etch a couple of weeks and move to a (now released) 2.6.19 > kernel, to solve this issue. Sven, stop this! I can remember well how you promised that moving to 2.6.18 will magically solve almost all of our issues - 6 (or more) release critical bugs against 2.6.18 don't show that this has worked so well. Please try helping us on solutions rather then breaking things again. Please try to look at it from another perspective: Consider you have bought such a laptop, and you install Debian. You have even read the release notes first. Everything works well. Until one day you notice your laptop gets too warm, and eventually even breaks because of this. On deeper research, you notice that this issue was well-known to Debian, but they refused to deal with it at all. How would you feel as a user? I think this is an unacceptable perspective. Ok, what can we do? 1. ignore the problem, 2. document it in the release notes and README.Debian of the kernel, 3. prevent the kernel running on such buggy laptops [is this possible?], 4. backport ACPI from 2.6.19, or use 2.6.19, 5. isolate a smaller fix and apply it. I personally consider options 1 and 4 to be unacceptable. Option 5 would be the best, but I have yet to see that this is possible (or rather, someone knowledgeable enough has time to do it). So, we should at least document it inside of the release notes, and README.Debian, and, if possible without being to invasive, get some check inside the kernel to print a big warning on bootup, or even refuse to work until some special parameter is used. How does this proposal sound to the kernel team? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402823: linux-image-2.6.18-3-686: Can't access /dev/rtc
* Michael Richters wrote: > On Fri, Dec 22, 2006 at 03:23:44PM +0100, Norbert Tretkowski wrote: > > * Michael Richters wrote: > > > I have a Dell PowerEdge 860, and the current stock Debian > > > kernels cannot access /dev/rtc: > > > > > > [EMAIL PROTECTED]:~] > > > # hwclock --show > > > select() to /dev/rtc to wait for clock tick timed out > > > > > > This same error occurs when the system is booting. > > > > Could you please retry the above command using the --directisa > > option? > > That works: > > [EMAIL PROTECTED]:~] > # hwclock --directisa --show > Fri Dec 22 09:52:27 2006 -0.565819 seconds Okay... as a temporary workaround, add the --directisa option to $HWCLOCKPARS in /etc/init.d/hwclock.sh. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
