linux-kernel - Re: [PATCH] ALSA: hda-intel - Disable MSI support by default

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]

Message-ID: <455B6F20.6050503@garzik.org>
Date:	Wed, 15 Nov 2006 14:48:48 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Stephen.Clark@...lark.us
CC:	Linus Torvalds <torvalds@...l.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Takashi Iwai <tiwai@...e.de>,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ALSA: hda-intel - Disable MSI support by default

Stephen Clark wrote:
> Also, I find it disturbing that we are forcing users to have know about 
> all these
> magic options that have to be put on the kernel boot line. My hard drive 
> on my
> new laptop would only run at 1.2mbs until I found out I had to use 
> combined_mode=libata
> and build a new ramdisk that included ata_piix.

That's what happens when two drivers want to drive the same hardware. 
The "slow and safe" default is the only proven-stable option, with the 
proven-stable PATA driver.  The other two options (drivers/ide for 
PATA+SATA -> leads to SATA locksup) and (libata for PATA -> ok but 
breaks existing configs, and less field time) are considered less safe.

Combined mode is ugly no matter how you look at it.  Just turn it off in 
BIOS (or pressure system vendor for this ability if BIOS lacks it, e.g. 
some Dell servers)

And throw some annoyance at Intel for creating such a headache.

	Jeff

-
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/