It seems Allen Pulsifer wrote:
> According to the DPTA-3x spec from IBM, if the drive has fully entered
> Standby mode, it can take up to 31 seconds for it to spin back up.
> (See sections 3.3.6.1 and 13.0). Other drive models may take even
> longer, and even after the drive is back up, it ma
]
> Cc: Richard Seaman Jr.; [EMAIL PROTECTED]
> Subject: Re: ATA driver problem?? (lost disk contact)
>
>
> It seems Dave J. Boers wrote:
> > On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> > > There is no way to see if the disk was in suspend mode, you can
On Sat, Dec 18, 1999 at 11:20:51PM +0100, Martin Blapp wrote:
>
> Sorry,
>
> I found a rather easy workaround. Disable DMA for
> the disks in the BIOS ... But I still wonder why
> enable/disable ATA DMA in kernel has no effect for
> this crash. Why does only the BIOS disable help ?
Purely a wil
It seems Martin Blapp wrote:
>
> Sorry,
>
> I found a rather easy workaround. Disable DMA for
> the disks in the BIOS ... But I still wonder why
> enable/disable ATA DMA in kernel has no effect for
> this crash. Why does only the BIOS disable help ?
No idea, I have to study AMD's southbridge fi
Sorry,
I found a rather easy workaround. Disable DMA for
the disks in the BIOS ... But I still wonder why
enable/disable ATA DMA in kernel has no effect for
this crash. Why does only the BIOS disable help ?
ata-pci0: at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq
It seems Dave J. Boers wrote:
> On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> > There is no way to see if the disk was in suspend mode, you can
> > give it a command and se how long it takes before it comes back :)
> >
> > The problem here is that it takes the command and OK's
On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> There is no way to see if the disk was in suspend mode, you can
> give it a command and se how long it takes before it comes back :)
>
> The problem here is that it takes the command and OK's it, but it
> takes the spinuptime + over
It seems Richard Seaman, Jr. wrote:
> On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote:
>
> > Because the wd driver has a 10 secs timeout, and ata has 5 secs.
> > I think the easiest way to "solve" this is to increase the
> > timeout to 10-15 secs, as little as I want to do that...
It seems Martin Blapp wrote:
> I've bought two new 16GB ATA disks and am not able to boot
> anymore since wd0 has been retired:
>
> Fresh current from today:
>
> [...]
> ad0: ad_timeout: lost disk contact
> ata0: resetting devices
>
> and after it hangs forever.
>
> I tried IDE_DELAY=1 and
hi,
I've bought two new 16GB ATA disks and am not able to boot
anymore since wd0 has been retired:
Fresh current from today:
[...]
ad0: ad_timeout: lost disk contact
ata0: resetting devices
and after it hangs forever.
I tried IDE_DELAY=1 and 15000 but it did not change anything.
Break i
On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote:
> Because the wd driver has a 10 secs timeout, and ata has 5 secs.
> I think the easiest way to "solve" this is to increase the
> timeout to 10-15 secs, as little as I want to do that...
I don't really understand disk drivers, so if
It seems Richard Seaman, Jr. wrote:
>
> > Yup, sounds like the problem some are seing, now I wonder why I
> > havn't seen it on any of the IBM disks I've access to, hmm...
> >
> > It apparantly can't be disabled, but I'll try to figure out if
> > I can detect when the drive is in this mode, or p
On Fri, Dec 17, 1999 at 08:22:03AM +0100, Soren Schmidt wrote:
> Yup, sounds like the problem some are seing, now I wonder why I
> havn't seen it on any of the IBM disks I've access to, hmm...
>
> It apparantly can't be disabled, but I'll try to figure out if
> I can detect when the drive is in
In message <[EMAIL PROTECTED]>, Soren Schmidt writes:
>It seems Richard Seaman, Jr. wrote:
>
>Yup, sounds like the problem some are seing, now I wonder why I
>havn't seen it on any of the IBM disks I've access to, hmm...
>
>It apparantly can't be disabled, but I'll try to figure out if
>I can dete
It seems Richard Seaman, Jr. wrote:
Yup, sounds like the problem some are seing, now I wonder why I
havn't seen it on any of the IBM disks I've access to, hmm...
It apparantly can't be disabled, but I'll try to figure out if
I can detect when the drive is in this mode, or put it in
standby mode
On Thu, Dec 16, 1999 at 04:50:55PM -0600, Richard Seaman, Jr. wrote:
> Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf
> If a command is received during spin down of ADM, the drive quits the spin down
> and tries to complete the command as soon as possible.
> In case the sp
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
> There is this thing with the IBM's doing some headcleaning stuff once
> a day/week, but I've never seen any of my IBM's do that (I got plenty
> of them). I'll try to get more info on that from IBM...
Check http://www.storage.ibm.co
It seems Dave J. Boers wrote:
> On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
> > Uhm, that wont be new WD drives, as they are exactly the same as
> > IBM drives give or take the label :)
>
> Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
> the same har
On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
> Uhm, that wont be new WD drives, as they are exactly the same as
> IBM drives give or take the label :)
Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
the same hardware?
My disk:
ad0: ATA-4 disk at at
It seems Dave J. Boers wrote:
> On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
>
> > Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact -
>resetting
> > Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
>
> > Dec 16 07:01:24 test /kernel:
On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
> Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting
> Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
> Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk contact
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
> It seems Dave J. Boers wrote:
> >
> > I am still having "disc contact lost messages" regularly too. I've been
> > posting about them on several occasions some time ago. I haven't been able
> > to pinn it down, however. IF they occu
hi, there!
On Thu, 16 Dec 1999, Dave J. Boers wrote:
> I am still having "disc contact lost messages" regularly too.
[...]
> There are two important aspects of the problem:
>
> 1. The problem does not always occur: it's unpredictable
> 2. When it occurs, I can actually hear the disk spinnin
hi, there!
On Thu, 16 Dec 1999, Dave J. Boers wrote:
> Could you tell met the exact time on which these messages occurred?
> Anywhere near 10:15 or 9:15 ?
nope. the time is unpredictable.
sometimes it can work more than a day without spilling out those messages
/fjoe
To Unsubscribe: send m
On Thu, Dec 16, 1999 at 03:29:30PM +0600, Max Khon wrote:
> hi, there!
> same here, dmesg output:
>
> ata_command: timeout waiting for interrupt
> Mounting root from ufs:/dev/ad0s2a
> ata0-master: ad_timeout: lost disk contact - resetting
> ata0: resetting devices .. done
> ata0-master: ad_timeo
It seems Devin Butterfield wrote:
> That's interesting...In my case it is quite easily reproduced (very
> predictable). All I have to do is reboot and then run sysinstall and
> when it probes the devices the disks time out. So far I have not been
> able to get this behavior at any other time.
>
>
On Thu, Dec 16, 1999 at 09:36:42AM +0100, Soren Schmidt wrote:
> One more thing, do you have SMART enabled in your BIOS ??, if so
> turn it off, and see if that changes anything...
I don't recall having it enabled; but I will check to make sure as soon as
I get home from work (which is still some
Hi,
"Dave J. Boers" wrote:
>
> On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote:
> > It seems Devin Butterfield wrote:
> > > I just recently compiled a kernel with the new ATA driver and have
> > > discovered a problem: if I run sysinstall, right when it says "probing
> > > devices,
It seems Soren Schmidt wrote:
> It seems Dave J. Boers wrote:
> >
> > I am still having "disc contact lost messages" regularly too. I've been
> > posting about them on several occasions some time ago. I haven't been able
> > to pinn it down, however. IF they occur, they occur somewhere between 9
It seems Dave J. Boers wrote:
>
> I am still having "disc contact lost messages" regularly too. I've been
> posting about them on several occasions some time ago. I haven't been able
> to pinn it down, however. IF they occur, they occur somewhere between 9:15
> and 9:20 a.m. OR p.m. But they don
On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote:
> It seems Devin Butterfield wrote:
> > I just recently compiled a kernel with the new ATA driver and have
> > discovered a problem: if I run sysinstall, right when it says "probing
> > devices, please wait (this can be a while)" error
It seems Devin Butterfield wrote:
> Hi,
>
> I just recently compiled a kernel with the new ATA driver and have
> discovered a problem: if I run sysinstall, right when it says "probing
> devices, please wait (this can be a while)" error messages saying...
[snip]
> and after printing these messages
Hi,
I just recently compiled a kernel with the new ATA driver and have
discovered a problem: if I run sysinstall, right when it says "probing
devices, please wait (this can be a while)" error messages saying...
Dec 15 21:20:05 dbm /kernel: ata0-slave: ad_timeout: lost disk contact -
resetting
De
33 matches
Mail list logo
