The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Timeout problems with ATA/SATA
Date: Tue, 19 Oct 2004 12:58:31 +0000	[thread overview]
Message-ID: <1098190711l.7834l.0l@werewolf.able.es> (raw)

Hi all...

I'm getting some proeblems and hangs with latest kernels.
I have two kind of problems, with ATA and with SATA-RAID.
SATA disks ata1-8 are part of a raid5 array exported via samba
(two promise controlers, 3 out of 4 ports used on each).
hde is an ATA disk for system root.

hde gives errors with 2.6.9 and -rc4-mm1. Also ata5 (SATA).
2.6.9-rc3-mm3 is working fine.

With 2.6.9-rc4-mm1, I get this messages:

Oct 18 19:31:54 nada kernel: Linux version 2.6.9-rc4-mm1 (root@nada.cps.unizar.es) (gcc version 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #1 SMP Thu Oct 14 23:57:32 CEST 2004
...
Oct 18 19:31:54 nada kernel: VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
Oct 18 19:31:54 nada kernel:     ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:DMA, hdf:pio
Oct 18 19:31:54 nada kernel:     ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:pio, hdh:DMA
Oct 18 19:31:54 nada kernel: Probing IDE interface ide2...
Oct 18 19:31:54 nada kernel: hde: Maxtor 6Y080L0, ATA DISK drive
Oct 18 19:31:54 nada kernel: ide2 at 0x1f0-0x1f7,0x3f6 on irq 14
...
Oct 18 19:31:54 nada kernel: ata5: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:407f
Oct 18 19:31:54 nada kernel: ata5: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48
Oct 18 19:31:54 nada kernel: ata5: dev 0 configured for UDMA/133
Oct 18 19:31:54 nada kernel: scsi4 : sata_promise
...
Oct 18 19:31:54 nada kernel:   Vendor: ATA       Model: Maxtor 7Y250M0    Rev: YAR5
Oct 18 19:31:54 nada kernel:   Type:   Direct-Access                      ANSI SCSI revision: 05
...
Oct 18 19:31:54 nada kernel:  sde: sde1
Oct 18 19:31:54 nada kernel: Attached scsi disk sde at scsi5, channel 0, id 0, lun 0
Oct 18 19:31:54 nada kernel: SCSI device sdf: 490234752 512-byte hdwr sectors (251000 MB)
Oct 18 19:31:54 nada kernel: SCSI device sdf: drive cache: write back
...
Oct 18 20:54:10 nada kernel: ata5: command timeout
Oct 18 20:54:30 nada kernel: hde: dma_timer_expiry: dma status == 0x24
Oct 18 20:54:40 nada kernel: hde: DMA interrupt recovery
Oct 18 20:54:40 nada kernel: hde: lost interrupt
<tons of similar messages>
...

With 2.6.9:
Oct 19 11:11:45 nada kernel: Linux version 2.6.9 (root@nada.cps.unizar.es) (gcc
...
Oct 19 13:07:03 nada kernel: ata5: command timeout
Oct 19 13:16:24 nada smb: smbd shutdown succeeded
Oct 19 13:16:24 nada nmbd[10910]: [2004/10/19 13:16:24, 0] nmbd/nmbd.c:terminate(54) 
Oct 19 13:16:24 nada nmbd[10910]:   Got SIGTERM: going down... 
Oct 19 13:16:24 nada smb: nmbd shutdown succeeded

Any ideas ?

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-rc4-mm1 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #4



             reply	other threads:[~2004-10-19 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 12:58 J.A. Magallon [this message]
2004-10-19 13:14 ` Timeout problems with ATA/SATA J.A. Magallon

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=1098190711l.7834l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --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