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
2010/6/9 Toralf Förster :
> Hi,
>
> Matthew Garrett wrote at 16:11:03
>> On Mon, Jun 07, 2010 at 11:22:21AM +0200, Toralf Förster wrote:
>> > Since some kernel version (IIRC since 2.6.31) it is necessary to boot the
>> > linux kernel with that option to prevent an extra 9 seconds delay during
>> >
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
