Re: sleep/fan problem bisected to 73201dbec64aebf6b0dca855b523f437972dc7bb
Jake Edge wrote: > > Hi Peter, > > I have been having a problem on my laptop (HP Compaq 2510p) over the > last two months with >= 3.7 kernels. After the first resume, it turns > on the fan and leaves it running at top speed no matter what the system > is doing. > The output of "sensors" is interesting ... for "temp6" in > "acpitz-virtual-0" it sits at +100C (near the +110C critical level) > when things have gone bad (just in Fedora or my kernels >=3.7, not in > the bisect, cuz those don't come back from the sleep) ... in the "good" > case, it normally sits around 30, but goes as high as 50 (and sometimes > reports 0 for a try or two -- frozen motherboard! :) ... > > thoughts on this? Other info you need or things I should be trying? This is known, see https://lkml.org/lkml/2012/12/4/428 for more details. > thanks, > > jake Regards, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: regression in linux 3.7 - fan speed at 100% after suspend/resume at 100%
Michael Grosshaeuser wrote: > Zhang Rui intel.com> writes: > >> >> Hi, Roberto, >> >> please attach the acpidump output. >> >> On Tue, 2012-12-04 at 13:57 +0100, Roberto Oppedisano wrote: >> > Hello, >> > with recent kernels after a suspend/resume cycle on my laptop (HP >> > 6730b) the fans stays at full speed. >> does the fan keep running at full speed after resume? >> >> please attach the output of "grep . /sys/class/thermal/*/*" before >> suspend and when the fan is running at full speed. >> please attach the same stuff in a good kernel. >> >> thanks, >> rui >> > > Hi, > > any update for this bug? This also breaks on my HP 2510p. Also on HP Mini 5102. > Best regards, > Michael Best regards, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata_nv issues with MCP51 SATA controller
Hello, I get a similar, if not identical, problem with an ASUS A8N SLI nforce4 based motherboard. The PC (with a seagate SATA-2 120 GB HDD) ran fine for two years , last Christmas windows xp (I didn't change either hardware or drivers) started crashing and the filesystem got corrupted beyond repair within 8 hours after every installation. The system log contained entries about bad sectors and, based on the seagate diagnosis tool, I returned the system to the supplier. According to the retail shop, neither the disk nor the system had any problems, so I was coerced to pay for a replacement disk. The replacement HDD (seagate again, 120 GB) ran fine until a month ago (this time the system is connected to a UPS), when the same problem occurred! I moved the disk to a linux system with the promise tx2plus controller (the one I'm typing this from), found bad sectors, formatted it and everything works fine for at least 6 hours of continuous disk writes and reads in this system. If I return the disk to the nforce4 system, it becomes corrupted within some hours of disk access, no matter whether linux or windows is installed, regardless of NCQ settings, drivers and cables. The symptoms are the same in both cases: the system crashes, then runs for some hours, then the controller stops completely responding (ata1: exception Emask 0x10 SAct 0x0 SErr 0x181 action 0x2 frozen is the first error message), the disk access LED blinks continuously, linux 2.6.18 (opensuse 10.2) throws lots of error messages similar to the ones you mention above, linux says that the device is dead and the system becomes unusable (no disk access). After a reboot, the filesystem is fine for some time, afterwards similar error messages appear, seek errors appear and the filesystem becomes completely destroyed. The positive part of this ordeal is that the linux SATA error handling works fine and linux recovered the first time, without access to the drive of course, while windows crashed badly and I was unable to find out what was happening in the beginning. I cannot say with certainty that this is a hardware error or damage, seagate technical support insists that their HDD is at fault, which is obviously wrong, the PC is (after the second incident) connected to a UPS and was checked by the service at the shop, and the most weird thing I cannot explain is that the system ran fine for 8 months after I changed the disk, even though the disk wasn't damaged! Either the motherboard is damaged or faulty (how can you explain that it ran fine for 8 months after I changed the disk?) or there is some very weird interaction with the HDD and the SATA controller, which isn't unlikely, considering the problems reported about combinations of nforce4 and maxtor HDDs, yet still doesn't explain the 2 year and 8 month period of normal operation. I'm going to contact the service again and see how this comes out. - 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: Loud "pop" coming from hard drive on reboot
On Sunday 15 April 2007 19:07, emisca wrote: > I can confirm this, I have a Seagate Momentus 5400.3 sata disk, and it > spins off, respin up and again off when I halt my notebook. > I had before this disk an IBM/Hitachi one, and it doesn't have this > behaviour. > > Take a look at this bug report: > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/67810 > > There are some references and some patches against 2.6.20 kernel. This > bug is confirmed there. > > Bye > I had the same problem with 2 WD disks on a desktop machine for 2 years, until I activated ACPI S3 (suspend to RAM) in the BIOS. According to this bug report (https://bugzilla.novell.com/show_bug.cgi?id=229210) the problem may be due to bad interaction between libata and the shutdown command. Tejun Heo, whom I thank for his support, has already proposed a patch to fix this. From the description there, it looks like it may also fix the reboot problem this thread is about. Regards - 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.21-rc1 and 2.6.21-rc2 kwin dies silently
On Wednesday 28 February 2007 17:19, Sid Boyce wrote: > openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to > require a password to unlock, but it asks for password. When the screen > unlocks, kwin is gone with no errors logged in /var/log/kdm or > /var/log/messages. No problems with 2.6.20. > > Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2. > Regards > Sid. This is the linux kernel mailing list. Perhaps you should post your problem to the opensuse mailing list. Regards - 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/
ata command timeout
Hello,
I have been running 2.6.18 for two months and the last couple of days these
error messages have appeared in my logs
(sata_promise kernel module, sda:SATA sdb:PATA disks):
ata1: command timeout
Feb 17 22:23:14 linux kernel: ata1: no sense translation for status: 0x40
Feb 17 22:23:14 linux kernel: ata1: translated ATA stat/err 0x40/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Feb 17 22:23:14 linux kernel: ata1: status=0x40 { DriveReady }
Feb 17 22:23:14 linux kernel: sd 0:0:0:0: SCSI error: return code = 0x0802
Feb 17 22:23:14 linux kernel: sda: Current: sense key: Aborted Command
Feb 17 22:23:14 linux kernel: Additional sense: No additional sense
information
Feb 17 22:23:14 linux kernel: end_request: I/O error, dev sda, sector
145179585
Feb 17 22:23:14 linux kernel: Buffer I/O error on device sda2, logical block
2787300
Feb 17 22:23:14 linux kernel: lost page write due to I/O error on sda2
and
ata1: command timeout
Feb 19 20:39:31 linux kernel: ata1: no sense translation for status: 0x40
Feb 19 20:39:31 linux kernel: ata1: translated ATA stat/err 0x40/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Feb 19 20:39:31 linux kernel: ata1: status=0x40 { DriveReady }
Feb 19 20:39:31 linux kernel: sd 0:0:0:0: SCSI error: return code = 0x0802
Feb 19 20:39:31 linux kernel: sda: Current: sense key: Aborted Command
Feb 19 20:39:31 linux kernel: Additional sense: No additional sense
information
Feb 19 20:39:31 linux kernel: end_request: I/O error, dev sda, sector 89553479
without any other ill-effects that I know of(I did smart tests on the drive;
all passed successfully).
I have read that hddtemp may be the cause of this (I am running version 0.3)
so is there any reason
to worry and prepare for a HDD replacement?
Kind regards.
-
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/
