archive mirror
 help / color / mirror / Atom feed
From: Olivier Bornet <>
Subject: problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state)
Date: Wed, 23 Apr 2003 23:27:13 +0200	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]


I'm trying to install Debian on 4 RaQ550 with each 2 80GB disks. All
seems OK with 3 of RaQ, but with one, it crash when I put the two disks
in a RAID1 meta device. In fact, it as crash at about 6% before the 70GB
partition is fully synchronized.

The error message is:

Serverworks OSB4 in impossible state.
Disable UDMA or if you are using Seagate then try switching disk types
on this controller. Please report this event to
OSB4: continuing might cause disk corruption. 

I have also send the same email as this one to

After some search, it seems I must enable MWDMA for my disks. (ref: )

Here is the configuration : 2 IDE 80GB disks, one on hda, one on hdc.
The kernel is the stock 2.4.20, with cobalt patches. The cobalt patches
don't modify the drivers/ide/serverworks.c.

IDE part of lspci -v:

00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 92) (prog-if 8f [Master SecP SecO PriP PriO])
        Subsystem: Sun Microsystems Computer Corp.: Unknown device c000
        Flags: bus master, medium devsel, latency 64
        I/O ports at fcd8 [size=8]
        I/O ports at fcd4 [size=4]
        I/O ports at fcc8 [size=8]
        I/O ports at fcc4 [size=4]
        I/O ports at fcb0 [size=16]
        I/O ports at fcac [size=4]

/proc/ide/hda and /proc/ide/hdc say it's a ST380021A. (I have no
physical access to the system now...)

I have try to set the DMA of the disks with:
    hdparm -X66 -d 1 /dev/hda
    hdparm -X66 -d 1 /dev/hdc
but this has cause a direct hangup (with the same message "Serverworks
OSB4 in impossible state...."). Maybe I don't use correctly hdparm, as
this is my first attempt with it.

At this time, I have disabled the dma with:
    hdparm -d 0 /dev/hda
    hdparm -d 0 /dev/hdc
and the sync in in the way (but say we need about 6 hours to finish,
comparing to the unmodifed test giving about 1 hour).

So my questions are :

- what can I do ?
- may this problem come also with the others RaQ we have (as far as I
  know, they are the same, and they are ordered at the same time)
- is the system safe without dma ?

Thanks in advance for any help, or any pointer to a solution. (Of
course, I can apply a patch to the kernel if this may correct the

Olivier Bornet                 |      français :
Swiss Ice Hockey Results       |      english  :                |      deutsch  :         |      italiano :
Get my PGP-key at or at

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-04-23 21:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 21:27 Olivier Bornet [this message]
2003-04-23 22:21 ` problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Alan Cox
2003-04-23 23:29   ` Olivier Bornet
2003-04-24  8:00     ` Olivier Bornet
2003-04-24 21:51       ` problem with Serverworks CSB5 IDE Duncan Laurie
2003-04-24 23:52         ` Duncan Laurie
2003-04-25 11:00         ` Alan Cox
2003-04-25 16:39           ` Duncan Laurie
2003-04-25 15:42             ` Alan Cox
2003-04-25 18:52               ` Duncan Laurie
2003-04-25 18:02                 ` Alan Cox
2003-04-28 13:03                 ` Alan Cox
2003-04-24  0:02 ` problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Duncan Laurie
2003-04-24  7:55   ` Olivier Bornet

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:

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

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).