On Tue, 26 Feb 2008, Elias Oltmanns wrote:
> > You don't want, for example, to swap out other apps, swap in the
> > daemon, in order to handle a sudden acceleration.
>
> Quite. But with mlock this particular problem can be handled in user
> space just fine. The only reason I can see right now for
On Thu, 27 Sep 2007, Matthew Garrett wrote:
> The spec seems to imply that even if the drive hotswap bay and the
> battery bay are physically the same, they're logically distinct. 10.2.1
That holds true for thinkpads up to the T43, at least. I don't know about
the newer ones.
You get bay eject
On Tue, 07 Aug 2007, Robert Hancock wrote:
>> You *do* have to worry about it in any box you turn off daily. Desktop
>> HDs will croak fast in that scenario, laptop HDs less so, but still too
>> fast. A very good laptop HD can last about 20k emergency unloads (this
>> is a unit that can do about
On Tue, 07 Aug 2007, Tejun Heo wrote:
> Henrique de Moraes Holschuh wrote:
> >> approximately translates into "if you have too many boatmen on a ship,
> >> it goes to mountain". We also have a bunch of Toshiba laptops which
> >
> > Yeah, that
On Tue, 07 Aug 2007, Tejun Heo wrote:
> emergency unload. Emergency unload does shorten the lifespan of the
> disk but you don't have to worry too much about it. Disks are designed
> to withstand certain number of emergency unloads.
You *do* have to worry about it in any box you turn off daily.
On Tue, 07 Aug 2007, Tejun Heo wrote:
> Henrique de Moraes Holschuh wrote:
> > On Tue, 07 Aug 2007, Tejun Heo wrote:
> >> Michael Sedkowski wrote:
> >>>> Hmmm... If the problem only shows up on nx6325, it might be that ACPI is
> >>>> pulling unneces
On Tue, 07 Aug 2007, Tejun Heo wrote:
> Michael Sedkowski wrote:
> >> Hmmm... If the problem only shows up on nx6325, it might be that ACPI is
> >> pulling unnecessary stunt. Please apply the attached patch and report
> >> when the disk spins down and up.
> >
> > Disk spins down on "Pre-shutdown
On Mon, 06 Aug 2007, Michael Sedkowski wrote:
> Dnia 06-08-2007, Pn o godzinie 11:23 -0300, Henrique de Moraes Holschuh
> napisa??(a):
> > On Mon, 06 Aug 2007, Tejun Heo wrote:
> > > Cc'ing Henrique. Any ideas?
> >
> > Check if /etc/init.d/halt is calli
On Mon, 06 Aug 2007, Tejun Heo wrote:
> Cc'ing Henrique. Any ideas?
Check if /etc/init.d/halt is calling halt(8) with the -h flag. If it is,
remove that -h flag. Usually, there is a hddown variable that holds it, you
just need to get rid of it.
I don't know anything about a Sidux, though.
--
On Tue, 12 Jun 2007, Matthew Garrett wrote:
> On Tue, Jun 12, 2007 at 09:18:19AM -0300, Henrique de Moraes Holschuh wrote:
> > On Tue, 12 Jun 2007, Matthew Garrett wrote:
> > >
> > > On laptops, I suspect that we'll probably get an ACPI interrupt even if
>
On Tue, 12 Jun 2007, Matthew Garrett wrote:
> On Mon, Jun 11, 2007 at 08:59:46PM -0700, Arjan van de Ven wrote:
> > that's a temporary shortcoming; even with these power savings you can
> > do hotplug as long as you're willing to poll for it at a reasonable
> > interval and are willing to wait th
On Mon, 11 Jun 2007, Jeff Garzik wrote:
> >>on/off doesn't really make sense if the question is "do you favor power
> >>or do you favor performance"...
Actually, it does if you think of it as "do you need hotplug right now or
not?".
> >How about just making it a numeric scale with 0 meaning n
On Mon, 11 Jun 2007, Kristen Carlson Accardi wrote:
> Setting Effect
> --
> min_power ALPM is enabled, and link set to enter
> lowest power state (SLUMBER) when idle
> Hot plug not allowed.
>
> m
On Fri, 01 Jun 2007, Jeff Garzik wrote:
> IIRC, Debian was the one OS that really did need a shutdown utility
> update, as the message says :)
Actually, editing /etc/init.d/halt is enough. Find the hddown="-h" and
change it to hddown="".
--
"One disk to rule them all, One disk to find them.
On Sat, 19 May 2007, Tejun Heo wrote:
> > To fix this issue, halt(8) started issueing WIN_STANDBYNOW1 (0xE0) and
> > WIN_STANDBYNOW2 (0x94) ioctls before halt and poweroff, as that was more
> > reliable than "flush cache" and the effect was the same.
>
> One culprit there is that, according to the
On Mon, 16 Apr 2007, Chuck Ebbert wrote:
> It looks like there are two problems here:
>
> (1) Some notebooks power off and back on when restarting.
If it happens just under Linux, this is something that really needs to be
addressed post-haste. Maybe someone should open a bug in bugzilla to help
On Sat, 14 Apr 2007, Pavel Machek wrote:
> How common are notebooks that cut power to disks during reboot?
Not common at all. Given that it wears the electronics a lot, it must be
either a defect (of the kinds Brazilian law forces the manufacturer to
either fix or give you your money back).
Assu
On Thu, 22 Mar 2007, Vladislav Bolkhovitin wrote:
> Seems, there is another way of doing a bank spin up / spin down: doing
> it in two passes. On the first pass START_STOP will be issued with
> IMMED=1 on all devices, then on the second pass START_STOP will be
> issued with IMMED=0. So the devic
On Tue, 20 Mar 2007, Shem Multinymous wrote:
> >More like it is a "make sure we can actually eject, as we have been told
> >to". We might return an error instead, but if we do, we need a way to
> >force-eject (e.g. echo 2 >eject).
>
> Which stage are you referring to?
Stage 2, of course. It is
On Mon, 19 Mar 2007, Shem Multinymous wrote:
> Userspace wants to (non-force-)-unmount by itself after (1), so it can
> stop the eject process if the filesystems cannot be cleanly
> unmounted. So the force-unmount at (3) ends up being a redundant
> safety measure at best.
More like it is a "make
On Mon, 19 Mar 2007, Matthew Garrett wrote:
> > But you still have to deal with mounted filesystems, no matter if it a
> > cardbus or a cdrom. Wouldn't we need something like 'save removal'
> > triggered from userspace like you maybe know from 'the other' operating
> > system?
>
> Yes, there's a n
On Sun, 18 Mar 2007, Holger Macht wrote:
> It doesn't work, I've already tried. The bay driver only emits an event if
> you really try to remove the bay, but not on docking/undocking.
Ah, now I understand what you mean.
Looks like we really need the dock driver to sort of like act as a bus.
--
On Sun, 18 Mar 2007, Holger Macht wrote:
> those ThinkPads where it is needed. Afterwards it does the corresponding
> dock/undock request on ibm_acpi. And this works reliably good what I can
> see from the feedback I already got. But for this to work, userspace would
It should work with the generi
On Sun, 18 Mar 2007, Tejun Heo wrote:
> Kristen Carlson Accardi wrote:
> >> 1. It will handle all device types (ATAPI, PATA, SATA, batteries);
> >>
> >> 2. It will do the right thing on plug and unplug. This means telling the
> >> rest of the kernel to disable the device in the bay, for example.
24 matches
Mail list logo