On 16 July 2010 00:08, Matthew Garrett wrote:
> On Thu, Jul 15, 2010 at 08:00:23PM -0300, Henrique de Moraes Holschuh wrote:
>
>> Do you want to escalate this to Lenovo? I need a clear and consise
>> description of the problem and the boxes we know to be affected.
>
> Well, right now we're not do
On Fri, 16 Jul 2010 09:38:54 +0200
Jens Rutschmann wrote:
> Am 14.07.2010 16:33 schrieb Pedro Ribeiro:
> > Please consider this patch. Let me know if you would like me to change
> > anything or if you don't agree with it. It applies cleanly to 2.6.35-rc5.
> >
> > The Lenovo T400 and T500 have a
On 17 July 2010 02:27, Matthew Garrett wrote:
> On Fri, Jul 16, 2010 at 10:23:04PM -0300, Henrique de Moraes Holschuh wrote:
>
>> I'm confused. Is it the PCI reboot vector, or the ACPI reboot vector
>> that acts instantly? The bug reporters say that they use reboot=pci to
>> have instant reboot,
On Fri, Jul 16, 2010 at 10:23:04PM -0300, Henrique de Moraes Holschuh wrote:
> I'm confused. Is it the PCI reboot vector, or the ACPI reboot vector
> that acts instantly? The bug reporters say that they use reboot=pci to
> have instant reboot, in this thread...
The PCI one, since it's a functio
On Fri, 16 Jul 2010, Matthew Garrett wrote:
> 1) The ACPI reboot vector reboots these machines instantly, but the flag
> that indicates we should use it isn't set.
> 2) Windows takes 9 seconds to reboot on the same hardware.
>
> It just sounds like broken firmware.
I'm confused. Is it the PCI r
Ok.
1) The ACPI reboot vector reboots these machines instantly, but the flag
that indicates we should use it isn't set.
2) Windows takes 9 seconds to reboot on the same hardware.
It just sounds like broken firmware.
--
Matthew Garrett | mj...@srcf.ucam.org
Am 14.07.2010 16:33 schrieb Pedro Ribeiro:
> Please consider this patch. Let me know if you would like me to change
> anything or if you don't agree with it. It applies cleanly to 2.6.35-rc5.
>
> The Lenovo T400 and T500 have an annoying 9 second delay when
> rebooting, unless reboot=pci is passed
On Fri, 16 Jul 2010, Matthew Garrett wrote:
> On Thu, Jul 15, 2010 at 08:00:23PM -0300, Henrique de Moraes Holschuh wrote:
> > Do you want to escalate this to Lenovo? I need a clear and consise
> > description of the problem and the boxes we know to be affected.
>
> Well, right now we're not doin
On Thu, Jul 15, 2010 at 08:00:23PM -0300, Henrique de Moraes Holschuh wrote:
> Do you want to escalate this to Lenovo? I need a clear and consise
> description of the problem and the boxes we know to be affected.
Well, right now we're not doing precisely what Windows does. The other
possibility
On Thu, 15 Jul 2010, Matthew Garrett wrote:
> On Thu, Jul 15, 2010 at 07:31:49PM -0300, Henrique de Moraes Holschuh wrote:
> > Or maybe we should key into whatever OSI() the ACPI firmware asked, and try
> > first whatever shutdown path the highest version of Windows asked for by the
> > firmware wo
On 15:36 Wed 14 Jul , Matthew Garrett wrote:
> On Wed, Jul 14, 2010 at 03:33:08PM +0100, Pedro Ribeiro wrote:
> > The Lenovo T400 and T500 have an annoying 9 second delay when
> > rebooting, unless reboot=pci is passed to the kernel command line.
> > This delay happens from at least kernel 2
Please consider this patch. Let me know if you would like me to change
anything or if you don't agree with it. It applies cleanly to 2.6.35-rc5.
The Lenovo T400 and T500 have an annoying 9 second delay when
rebooting, unless reboot=pci is passed to the kernel command line.
This delay happens from
On 14 July 2010 15:36, Matthew Garrett wrote:
> On Wed, Jul 14, 2010 at 03:33:08PM +0100, Pedro Ribeiro wrote:
>> Please consider this patch. Let me know if you would like me to change
>> anything or if you don't agree with it. It applies cleanly to 2.6.35-rc5.
>>
>> The Lenovo T400 and T500 ha
On Thu, Jul 15, 2010 at 07:31:49PM -0300, Henrique de Moraes Holschuh wrote:
> Or maybe we should key into whatever OSI() the ACPI firmware asked, and try
> first whatever shutdown path the highest version of Windows asked for by the
> firmware would.
I've been tracing how Windows implements rebo
On Wed, 14 Jul 2010, Matthew Garrett wrote:
> There's two possibilities here:
>
> 1) Lenovo's firmware is broken and the 9-second delay is always going to
> be there. In that case we should try to use the ACPI reboot vector
> first.
Or maybe we should key into whatever OSI() the ACPI firmware a
On Wed, Jul 14, 2010 at 03:33:08PM +0100, Pedro Ribeiro wrote:
> Please consider this patch. Let me know if you would like me to change
> anything or if you don't agree with it. It applies cleanly to 2.6.35-rc5.
>
> The Lenovo T400 and T500 have an annoying 9 second delay when
> rebooting, unl
16 matches
Mail list logo
