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] [day] [month] [year] [list]
Date:	Fri, 13 Jul 2007 23:32:59 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Thomas Backlund <tmb@...driva.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: Problem with SiS Ide/Pata/Sata on 2.6.22-rc7-git4


Hi,

On Tuesday 10 July 2007, Thomas Backlund wrote:
> Alan Cox skrev:
> >> If you modprobe only sis5513
> >>   OR
> >> If you modprobe only sis5513 and then sata_sis/pata_sis:
> >>   - you get this:
> >>     (the hdb drive does not get detected/usable)
> > 
> > Don't mix old and new IDE like that. We allow both so you can use old SIS
> > and new Jmicron etc for example but there are some cases where trying to
> > load both old and new IDE support for the same chip will do strange
> > things.
> > 
> 
> But there is still a regression here compared to 2.6.17...
> 
> If you load only sis5513 on a 2.6.22 you still get:
> --- quote ---
> <6>SIS5513: chipset revision 1
> <6>SIS5513: not 100% native mode: will probe irqs later
> <6>SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
> <6>    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
> <6>    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
> <7>Probing IDE interface ide0...
> <4>hdb: QUANTUM FIREBALLlct15 07, ATA DISK drive
> <4>hdb: host side 80-wire cable detection failed, limiting max speed to 
> UDMA33
> <7>hdb: selected mode 0x42
> --- quote ---
> 
> wich does not happend on 2.6.17...

I'm a bit confused here.  Do you mean that the warning message
is not printed or that disk is not limited to UDMA33?

Could you send "hdb" part of 2.6.17 dmesg?

> The disk in question is ATA66 capable

Please send output of "hdparm --Istdout /dev/hdb" command.

This is probably one of the early ATA66 disks with the buggy device side
cable detection.  CONFIG_IDEDMA_IVB=y should help but I'm currently working
on adding automatic detection of such disks.

Thanks,
Bart
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ