mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Stuart <dstuart@rogers.com>
Cc: David Stuart <dstuart@rogers.com>, linux-kernel@vger.kernel.org
Subject: Re: Problems with disk + network on 2.6.25.11-60.fc8
Date: Thu, 7 Aug 2008 11:36:04 +0100	[thread overview]
Message-ID: <20080807113604.70447431@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <489A5336.5080904@rogers.com>

> 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

      reply	other threads:[~2008-08-07 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 17:39 David Stuart
2008-08-04 17:42 ` Alan Cox
2008-08-04 20:31   ` David Stuart
2008-08-04 20:44     ` Alan Cox
2008-08-04 23:27       ` David Stuart
2008-08-04 23:13         ` Alan Cox
2008-08-04 23:58           ` David Stuart
2008-08-07  1:43             ` David Stuart
2008-08-07 10:36               ` Alan Cox [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080807113604.70447431@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dstuart@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®