lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 13 Apr 2008 00:19:39 -0400
From:	Rich West <Rich.West@...mo.com>
To:	Tejun Heo <htejun@...il.com>
CC:	Jeff Garzik <jeff@...zik.org>,
	Wander Winkelhorst <w.winkelhorst@...il.com>,
	linux-kernel@...r.kernel.org,
	Linux IDE mailing list <linux-ide@...r.kernel.org>
Subject: Re: sata_via

Tejun Heo wrote:
> Jeff Garzik wrote:
>> Rich West wrote:
>>> I was only curious as to what turning off power management support 
>>> would buy with regard to the sata timeout issue.
>>
>>
>> ACPI is not only power management.  It is all the information your 
>> hardware conveys to your OS, about the setup and workings of your 
>> hardware.
>>
>> Without ACPI, non-PM things like SMP, laptop dock/undock, and many 
>> other gadgets fail to function (or are configured sub-optimally).
>>
>> ACPI sets up interrupt routing, and Linux history is _loaded_ with 
>> _years_ of problem reports that appear as timeouts, only to be 
>> resolved as ACPI interrupt bugs (aka BIOS bugs, since ACPI tables 
>> come from BIOS).
>
> Also, please give a shot at the sacred "irqpoll".

I've had bad luck in the past (with other machiens) when adding 
"irqpoll" in that it had locked up the entire machine (not this one, but 
others) after a very short period of time.  My only attempt at using it, 
though, was to try to address an X server related issue, but this is a 
non-user machine, so X isn't necessary, and, hence, it's at runlevel 3 
all of the time.

So far, noapic and acpi=off seem to be working.. The system has been up 
8 days without any problems.. previously, a problem with the SATA drive 
(details of which were part of the first few messages in this thread) 
would surface anywhere between 15 minutes and 5-7 days after a reboot.

However, since I started this email, I tried firing up X (with noapci 
and acpi=off both set), the machine locks up entirely.

-Rich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists