linux-kernel - Re: Problems with disk + network on 2.6.25.11-60.fc8

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:	Thu, 7 Aug 2008 11:36:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Stuart <dstuart@...ers.com>
Cc:	David Stuart <dstuart@...ers.com>, linux-kernel@...r.kernel.org
Subject: Re: Problems with disk + network on 2.6.25.11-60.fc8

> It occurs to me that you might be implying there is some "chip config" 
> that I can retrieve and give to you. Is there anything I can/should do 
> in order to give you more information, or is this pretty much out of my 
> hands at this point?

There are two things you can play with. One is the UDMA burst mode on the
chip which should be getting set, the other is PCI latencies (which the
BIOS should have set up but you can play with)

> Should I be filing a bug report for this?

Probably a good idea

Next things to try are

1.	edit drivers/ata/pata_pdc202xx_old.c
	after the line

	iowrite8(burst | 0x01, bmdma + 0x1f);

add

	printk(KERN_ERR "BURST was %02X\n", burst);

build/install/boot that kernel and see what it says.

The second (sledgehammer) approach would be to use setpci to set the
LATENCY_TIMER value on the pdc202xx_old and network card differently.

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