On Fri, May 18, 2007 at 03:16:45AM -0400, Rob Landley wrote:
> Because the controller's far more likely to go than the moving parts...
Having redundant everything would be preferable. But cables do
sometimes fail. Not sure about the controllers, but if the controller
went you might loose the
On Fri, 18 May 2007 03:16:45 -0400
Rob Landley <[EMAIL PROTECTED]> wrote:
> On Thursday 17 May 2007 11:04 am, Lennart Sorensen wrote:
> > On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
> > > Actually, in my limited experience, SAS is marginally less crappy than
>
On Thursday 17 May 2007 11:04 am, Lennart Sorensen wrote:
> On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
> > Actually, in my limited experience, SAS is marginally less crappy than
SATA,
> > and has a higher MTBF, probably because the manufacturers try to cut less
>
On Thursday 17 May 2007 11:04 am, Lennart Sorensen wrote:
On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
Actually, in my limited experience, SAS is marginally less crappy than
SATA,
and has a higher MTBF, probably because the manufacturers try to cut less
On Fri, 18 May 2007 03:16:45 -0400
Rob Landley [EMAIL PROTECTED] wrote:
On Thursday 17 May 2007 11:04 am, Lennart Sorensen wrote:
On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
Actually, in my limited experience, SAS is marginally less crappy than
SATA,
On Fri, May 18, 2007 at 03:16:45AM -0400, Rob Landley wrote:
Because the controller's far more likely to go than the moving parts...
Having redundant everything would be preferable. But cables do
sometimes fail. Not sure about the controllers, but if the controller
went you might loose the
On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
> Actually, in my limited experience, SAS is marginally less crappy than SATA,
> and has a higher MTBF, probably because the manufacturers try to cut less
> corners. But if one can get high-quality SATA drives (where?!),
Rob Landley wrote:
>> Yeap, definitely a bug in the kernel and we're trying to fix it. Just
>> for the record, we have _always_ issued FLUSH CACHE, so there hasn't
>> been and won't be any data loss problem. The data loss problem was
>> mentioned as why we can't do things completely inside
Rob Landley wrote:
>> Distros should update their shutdown(8) to do the followings.
>> Check whether /sys/modules/libata/parameters/spindown_compat exists. If it
>> does, write 0 to it. For each libata harddisk
>> Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop exists. If it
>>
Rob Landley wrote:
Distros should update their shutdown(8) to do the followings.
Check whether /sys/modules/libata/parameters/spindown_compat exists. If it
does, write 0 to it. For each libata harddisk
Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop exists. If it
doesn't,
Rob Landley wrote:
Yeap, definitely a bug in the kernel and we're trying to fix it. Just
for the record, we have _always_ issued FLUSH CACHE, so there hasn't
been and won't be any data loss problem. The data loss problem was
mentioned as why we can't do things completely inside kernel
On Thu, May 17, 2007 at 12:39:47AM -0300, Henrique de Moraes Holschuh wrote:
Actually, in my limited experience, SAS is marginally less crappy than SATA,
and has a higher MTBF, probably because the manufacturers try to cut less
corners. But if one can get high-quality SATA drives (where?!), I
On Wed, 16 May 2007, Rob Landley wrote:
> > But you need to detect if the kernel has proper SCSI device shutdown
> > support, because if it does not, you have to do a cache flush and spindown
> > on shutdown(8) if you can...
>
> Or (and this is just a thought), you could upgrade your kernel so it
On Wednesday 16 May 2007 8:58 pm, Henrique de Moraes Holschuh wrote:
> On Wed, 16 May 2007, Rob Landley wrote:
> > Ok, so the change is to get shutdown to _stop_ doing something stupid
> > (spinning down the disk without first flushing the cache), and the correct
> > thing for shutdown to do is
On Wed, 16 May 2007, Rob Landley wrote:
> Ok, so the change is to get shutdown to _stop_ doing something stupid
> (spinning down the disk without first flushing the cache), and the correct
> thing for shutdown to do is keep its' mitts off the thing and let the kernel
> power down the darn
On Wednesday 16 May 2007 9:49 am, Francesco Pretto wrote:
> 2007/5/16, Stephen Clark <[EMAIL PROTECTED]>:
> > >On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
> > >
> > >I'm confused. Could someone please explain?
> > >
> > I agree. This didn't happen when I was just using the ide driver, why
>
On Wednesday 16 May 2007 7:41 am, Tejun Heo wrote:
> Hello,
>
> Rob Landley wrote:
> > Um, hang on. So libata can't reliably turn the system off without data
loss
> > and potential damage to hardware unless userspace goes through a special
song
> > and dance? And this is _not_ considered a
On Wednesday 16 May 2007 5:15 am, Francesco Pretto wrote:
> - everyone else:
> // continue to do nothing :-)
> reboot();
That would be cool, but the impression I got from
http://linux-ata.org/shutdown.html was that shutdown commands were supposed
to _add_ quiescing of drives in order to avoid
2007/5/16, Stephen Clark <[EMAIL PROTECTED]>:
>On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
>
>I'm confused. Could someone please explain?
>
I agree. This didn't happen when I was just using the ide driver, why
can't libata work as well
as the old ide driver.
Read my reply to that post.
Rob Landley wrote:
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
> Francesco Pretto wrote:
> > 2007/5/4, Tejun Heo <[EMAIL PROTECTED]>:
> >> Yeap, the third iteration of the patch just got submitted.
> >>
> >>
Hello,
Rob Landley wrote:
> Um, hang on. So libata can't reliably turn the system off without data loss
> and potential damage to hardware unless userspace goes through a special song
> and dance? And this is _not_ considered a defect in the kernel?
Yeap, definitely a bug in the kernel and
Francesco Pretto wrote:
> For what i understood, there were a misunderstanding caused by the
> wrong assumption that shutdown(8) implementations were issuing
> STANDBYNOW on all hard disk devices on the system (indistinctly from
> the interface, old-ide/libata/scsi). The fact is that sysvinit and
Dave Jones wrote:
> There's a typo..
>
> "Check whether /sys/modules/libata/parameters/spindown_compat exists. If it
> does, write 0 to it."
>
> should be /sys/module/libata/parameters/spindown_compat
Right, thanks.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe
2007/5/16, Rob Landley <[EMAIL PROTECTED]>:
(Is there any other piece of hardware that needs userspace to quiesce it just
so the _off_switch_ can take effect? Yes, I read both the gmane thread and
the linux-ata.org link. I used to maintain the busybox halt/reboot/poweroff
commands, although I
2007/5/16, Rob Landley [EMAIL PROTECTED]:
(Is there any other piece of hardware that needs userspace to quiesce it just
so the _off_switch_ can take effect? Yes, I read both the gmane thread and
the linux-ata.org link. I used to maintain the busybox halt/reboot/poweroff
commands, although I
Francesco Pretto wrote:
For what i understood, there were a misunderstanding caused by the
wrong assumption that shutdown(8) implementations were issuing
STANDBYNOW on all hard disk devices on the system (indistinctly from
the interface, old-ide/libata/scsi). The fact is that sysvinit and
Dave Jones wrote:
There's a typo..
Check whether /sys/modules/libata/parameters/spindown_compat exists. If it
does, write 0 to it.
should be /sys/module/libata/parameters/spindown_compat
Right, thanks.
--
tejun
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
Hello,
Rob Landley wrote:
Um, hang on. So libata can't reliably turn the system off without data loss
and potential damage to hardware unless userspace goes through a special song
and dance? And this is _not_ considered a defect in the kernel?
Yeap, definitely a bug in the kernel and
Rob Landley wrote:
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
Francesco Pretto wrote:
2007/5/4, Tejun Heo [EMAIL PROTECTED]:
Yeap, the third iteration of the patch just got submitted.
2007/5/16, Stephen Clark [EMAIL PROTECTED]:
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
I'm confused. Could someone please explain?
I agree. This didn't happen when I was just using the ide driver, why
can't libata work as well
as the old ide driver.
Read my reply to that post. To
On Wednesday 16 May 2007 5:15 am, Francesco Pretto wrote:
- everyone else:
// continue to do nothing :-)
reboot();
That would be cool, but the impression I got from
http://linux-ata.org/shutdown.html was that shutdown commands were supposed
to _add_ quiescing of drives in order to avoid
On Wednesday 16 May 2007 7:41 am, Tejun Heo wrote:
Hello,
Rob Landley wrote:
Um, hang on. So libata can't reliably turn the system off without data
loss
and potential damage to hardware unless userspace goes through a special
song
and dance? And this is _not_ considered a defect in
On Wednesday 16 May 2007 9:49 am, Francesco Pretto wrote:
2007/5/16, Stephen Clark [EMAIL PROTECTED]:
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
I'm confused. Could someone please explain?
I agree. This didn't happen when I was just using the ide driver, why
can't libata
On Wed, 16 May 2007, Rob Landley wrote:
Ok, so the change is to get shutdown to _stop_ doing something stupid
(spinning down the disk without first flushing the cache), and the correct
thing for shutdown to do is keep its' mitts off the thing and let the kernel
power down the darn hardware?
On Wednesday 16 May 2007 8:58 pm, Henrique de Moraes Holschuh wrote:
On Wed, 16 May 2007, Rob Landley wrote:
Ok, so the change is to get shutdown to _stop_ doing something stupid
(spinning down the disk without first flushing the cache), and the correct
thing for shutdown to do is keep
On Wed, 16 May 2007, Rob Landley wrote:
But you need to detect if the kernel has proper SCSI device shutdown
support, because if it does not, you have to do a cache flush and spindown
on shutdown(8) if you can...
Or (and this is just a thought), you could upgrade your kernel so it
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
> On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
> > Francesco Pretto wrote:
> > > 2007/5/4, Tejun Heo <[EMAIL PROTECTED]>:
> > >> Yeap, the third iteration of the patch just got submitted.
> > >>
> > >>
On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
> Francesco Pretto wrote:
> > 2007/5/4, Tejun Heo <[EMAIL PROTECTED]>:
> >> Yeap, the third iteration of the patch just got submitted.
> >>
> >> http://thread.gmane.org/gmane.linux.ide/18485
> >>
> >> Unfortunately, there doesn't
Hello, Henrique.
Henrique de Moraes Holschuh wrote:
> On Mon, 14 May 2007, Francesco Pretto wrote:
>> Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
>> Smoorenburg, dev of sysvinit.
>
> For all Debian sysvinit issues, please send email to
> [EMAIL PROTECTED] (added to CC).
>
On Mon, 14 May 2007, Francesco Pretto wrote:
> Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
> Smoorenburg, dev of sysvinit.
For all Debian sysvinit issues, please send email to
[EMAIL PROTECTED] (added to CC).
For the Debian sysvinit crew: Guys, have a look at
Francesco Pretto wrote:
> 2007/5/14, Tejun Heo <[EMAIL PROTECTED]>
>>
>> Okay, the patch made upstream and webpage posted.
>>
>> http://linux-ata.org/shutdown.html
>>
>> --
>> tejun
>>
>
> Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
> Smoorenburg, dev of sysvinit.
>
> [1]
Francesco Pretto wrote:
2007/5/14, Tejun Heo [EMAIL PROTECTED]
Okay, the patch made upstream and webpage posted.
http://linux-ata.org/shutdown.html
--
tejun
Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
Smoorenburg, dev of sysvinit.
[1]
On Mon, 14 May 2007, Francesco Pretto wrote:
Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
Smoorenburg, dev of sysvinit.
For all Debian sysvinit issues, please send email to
[EMAIL PROTECTED] (added to CC).
For the Debian sysvinit crew: Guys, have a look at
Hello, Henrique.
Henrique de Moraes Holschuh wrote:
On Mon, 14 May 2007, Francesco Pretto wrote:
Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
Smoorenburg, dev of sysvinit.
For all Debian sysvinit issues, please send email to
[EMAIL PROTECTED] (added to CC).
For the
On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
Francesco Pretto wrote:
2007/5/4, Tejun Heo [EMAIL PROTECTED]:
Yeap, the third iteration of the patch just got submitted.
http://thread.gmane.org/gmane.linux.ide/18485
Unfortunately, there doesn't seem to be an easy
On Tuesday 15 May 2007 5:08 pm, Dave Jones wrote:
On Mon, May 14, 2007 at 07:32:43PM +0200, Tejun Heo wrote:
Francesco Pretto wrote:
2007/5/4, Tejun Heo [EMAIL PROTECTED]:
Yeap, the third iteration of the patch just got submitted.
http://thread.gmane.org/gmane.linux.ide/18485
2007/5/14, Tejun Heo <[EMAIL PROTECTED]>
Okay, the patch made upstream and webpage posted.
http://linux-ata.org/shutdown.html
--
tejun
Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
Smoorenburg, dev of sysvinit.
[1] https://bugs.launchpad.net/upstart/+bug/114683
[2]
Francesco Pretto wrote:
> 2007/5/4, Tejun Heo <[EMAIL PROTECTED]>:
>> Yeap, the third iteration of the patch just got submitted.
>>
>> http://thread.gmane.org/gmane.linux.ide/18485
>>
>> Unfortunately, there doesn't seem to be an easy way out. We'll need
>> userland shutdown(8) update.
>>
>> --
Francesco Pretto wrote:
2007/5/4, Tejun Heo [EMAIL PROTECTED]:
Yeap, the third iteration of the patch just got submitted.
http://thread.gmane.org/gmane.linux.ide/18485
Unfortunately, there doesn't seem to be an easy way out. We'll need
userland shutdown(8) update.
--
tejun
Ok, i
2007/5/14, Tejun Heo [EMAIL PROTECTED]
Okay, the patch made upstream and webpage posted.
http://linux-ata.org/shutdown.html
--
tejun
Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
Smoorenburg, dev of sysvinit.
[1] https://bugs.launchpad.net/upstart/+bug/114683
[2]
Francesco Pretto wrote:
> Ok, i can't understand if the patch will be included in 2.6.22 (i
> didn't see it in the Andrew Morton merge plan). However, if you can
> confirm the inclusion, i can send bug reports for ubuntu and gentoo. I
> can even send an email to Miquel van Smoorenburg, who should
2007/5/4, Tejun Heo <[EMAIL PROTECTED]>:
Yeap, the third iteration of the patch just got submitted.
http://thread.gmane.org/gmane.linux.ide/18485
Unfortunately, there doesn't seem to be an easy way out. We'll need
userland shutdown(8) update.
--
tejun
Ok, i can't understand if the patch
2007/5/4, Tejun Heo [EMAIL PROTECTED]:
Yeap, the third iteration of the patch just got submitted.
http://thread.gmane.org/gmane.linux.ide/18485
Unfortunately, there doesn't seem to be an easy way out. We'll need
userland shutdown(8) update.
--
tejun
Ok, i can't understand if the patch
Francesco Pretto wrote:
Ok, i can't understand if the patch will be included in 2.6.22 (i
didn't see it in the Andrew Morton merge plan). However, if you can
confirm the inclusion, i can send bug reports for ubuntu and gentoo. I
can even send an email to Miquel van Smoorenburg, who should be
Phillip Susi wrote:
> Did anything ever come of this? We still have users complaining about
> this. Does this patch resolve the issue? I can't seem to load it up
> right now; the site says it is down for maintenance.
Yeap, the third iteration of the patch just got submitted.
Did anything ever come of this? We still have users complaining about
this. Does this patch resolve the issue? I can't seem to load it up
right now; the site says it is down for maintenance.
Francesco Pretto wrote:
2007/2/22, Robert Hancock <[EMAIL PROTECTED]>:
I believe it runs on
Did anything ever come of this? We still have users complaining about
this. Does this patch resolve the issue? I can't seem to load it up
right now; the site says it is down for maintenance.
Francesco Pretto wrote:
2007/2/22, Robert Hancock [EMAIL PROTECTED]:
I believe it runs on
Phillip Susi wrote:
Did anything ever come of this? We still have users complaining about
this. Does this patch resolve the issue? I can't seem to load it up
right now; the site says it is down for maintenance.
Yeap, the third iteration of the patch just got submitted.
Francesco Pretto wrote:
2007/2/22, Robert Hancock <[EMAIL PROTECTED]>:
I believe it runs on suspend, but we don't run that code on normal
shutdown, do we?
Tejun Heo had a patch for sd that could (optionally) trigger a START
STOP UNIT command to spin the disk down after synchronizing the cache
Francesco Pretto wrote:
2007/2/22, Robert Hancock [EMAIL PROTECTED]:
I believe it runs on suspend, but we don't run that code on normal
shutdown, do we?
Tejun Heo had a patch for sd that could (optionally) trigger a START
STOP UNIT command to spin the disk down after synchronizing the cache
2007/2/22, Robert Hancock <[EMAIL PROTECTED]>:
I believe it runs on suspend, but we don't run that code on normal
shutdown, do we?
Tejun Heo had a patch for sd that could (optionally) trigger a START
STOP UNIT command to spin the disk down after synchronizing the cache
before shutdown, but I
2007/2/22, Robert Hancock [EMAIL PROTECTED]:
I believe it runs on suspend, but we don't run that code on normal
shutdown, do we?
Tejun Heo had a patch for sd that could (optionally) trigger a START
STOP UNIT command to spin the disk down after synchronizing the cache
before shutdown, but I
Rolf Offermanns wrote:
I hear the same strange noise on poweroff (2.6.20 vanilla). This is what I
get on my system with ATA_DEBUG and ATA_VERBOSE_DEBUG both defined. The
system will *not* poweroff with "halt -f" so there was no noise!
md: stopping all md devices.
Synchronizing SCSI cache for
2007/2/22, Alan <[EMAIL PROTECTED]>:
The following will generate a vast amount of debug of which only the end
matters.
For some reason, related to my current distro, i didn't used init=/bin/sh .
The full, bloated, log is here http://www.webalice.it/ceztko/log1
(taken from launch of
Alan wrote:
>> However, i'm not still sure i enabled as much debugging info as i
>> could in the kernel configuration. If you need more, please point me
>> to precise configuration options.
>
> You grabbed a lot of junk but you did grab this line
>
> [17179682.56] Synchronizing SCSI cache
Francesco Pretto wrote:
Yes, windows XP could handle better the power button pressed event
(causing the hd not to go to emergency parking, even when forced
shut-down, most of the times). But regarding a normal shut-down cycle,
isn't this a regression? You don't solve a regression adding a
> However, i'm not still sure i enabled as much debugging info as i
> could in the kernel configuration. If you need more, please point me
> to precise configuration options.
You grabbed a lot of junk but you did grab this line
[17179682.56] Synchronizing SCSI cache for disk sda:
Which
2007/2/22, Robert Hancock <[EMAIL PROTECTED]>:
And yes, this is something we need to deal with. I don't think that
disks that use contact start-stop heads care so much, but disks that use
load-unload heads (like most laptop drives, it seems) generally quote a
much lower cycle lifetime for
2007/2/22, Robert Hancock [EMAIL PROTECTED]:
And yes, this is something we need to deal with. I don't think that
disks that use contact start-stop heads care so much, but disks that use
load-unload heads (like most laptop drives, it seems) generally quote a
much lower cycle lifetime for
However, i'm not still sure i enabled as much debugging info as i
could in the kernel configuration. If you need more, please point me
to precise configuration options.
You grabbed a lot of junk but you did grab this line
[17179682.56] Synchronizing SCSI cache for disk sda:
Which means
Francesco Pretto wrote:
Yes, windows XP could handle better the power button pressed event
(causing the hd not to go to emergency parking, even when forced
shut-down, most of the times). But regarding a normal shut-down cycle,
isn't this a regression? You don't solve a regression adding a
Alan wrote:
However, i'm not still sure i enabled as much debugging info as i
could in the kernel configuration. If you need more, please point me
to precise configuration options.
You grabbed a lot of junk but you did grab this line
[17179682.56] Synchronizing SCSI cache for disk
2007/2/22, Alan [EMAIL PROTECTED]:
The following will generate a vast amount of debug of which only the end
matters.
For some reason, related to my current distro, i didn't used init=/bin/sh .
The full, bloated, log is here http://www.webalice.it/ceztko/log1
(taken from launch of poweroff).
Rolf Offermanns wrote:
I hear the same strange noise on poweroff (2.6.20 vanilla). This is what I
get on my system with ATA_DEBUG and ATA_VERBOSE_DEBUG both defined. The
system will *not* poweroff with halt -f so there was no noise!
md: stopping all md devices.
Synchronizing SCSI cache for disk
Robert Hancock wrote:
> Robert Hancock wrote:
>> Alan wrote:
>>> Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
>>> turn on all the ATA debug and shutdown, the code should issue a cache
>>> flush followed by a standbynow1 command for each disk.
>>>
>>> Alan
>>
>> I
Robert Hancock wrote:
Alan wrote:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
I believe it runs on suspend, but we don't run that
Alan wrote:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
I believe it runs on suspend, but we don't run that code on normal
shutdown,
(I'm sorry if the thread breaks, i'm not subscribed)
2007/2/21, Alan <[EMAIL PROTECTED]>:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi, we are a couple of users suffering both the same problem: a weird
hard disk noise emitted when shutting down, immediately after the main
power is cut from the pc/notebook. We believe that the noise is a
symptom of an emergency head parking, usually performed on the drives
when the the power
Hi, we are a couple of users suffering both the same problem: a weird
hard disk noise emitted when shutting down, immediately after the main
power is cut from the pc/notebook. We believe that the noise is a
symptom of an emergency head parking, usually performed on the drives
when the the power
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
(I'm sorry if the thread breaks, i'm not subscribed)
2007/2/21, Alan [EMAIL PROTECTED]:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
Alan wrote:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
I believe it runs on suspend, but we don't run that code on normal
shutdown,
Robert Hancock wrote:
Alan wrote:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
I believe it runs on suspend, but we don't run that
Robert Hancock wrote:
Robert Hancock wrote:
Alan wrote:
Stick some printk calls in drivers/ata/libata-eh.c in ata_eh_suspend, or
turn on all the ATA debug and shutdown, the code should issue a cache
flush followed by a standbynow1 command for each disk.
Alan
I believe it runs on suspend,
86 matches
Mail list logo
