Prev: vmscan: convert direct reclaim tracepoint to DEFINE_EVENT
Next: [PATCH 3/7] ACPI: Register EC io ports in /proc/ioports
From: Pedro Ribeiro on 16 Jul 2010 07:10
On 16 July 2010 00:08, Matthew Garrett <mjg59(a)srcf.ucam.org> 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 doing precisely what Windows does. The other
> possibility is that when the keyboard controller write triggers some SMM
> code, it makes an assumption about some piece of hardware state that
> isn't true and loops for a while to see if it changes. If we knew what
> that was then we could ensure that we're performing the same state
> change on our way down to reboot.
>
> One thing that would be worth checking is whether performing the
> keyboard controller writes from userspace with a minimal kernel and
> init=/bin/bash shows the 9-second pause or not - and then, ideally, see
> whether the same is also true under DOS.
>
> --
> Matthew Garrett | mjg59(a)srcf.ucam.org
>

I'm available to try and test whatever you want on my machine .

Regards,
Pedro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Pedro Ribeiro on 23 Jul 2010 15:00
On 17 July 2010 02:27, Matthew Garrett <mjg59(a)srcf.ucam.org> 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, in this thread...
>
> The PCI one, since it's a function of the chipset. The ACPI one would
> act instantly (it's the PCI one, in this case) but it's marked as
> unsupported. However, the PCI one is poorly standardised - Windows never
> uses it, different chips have subtly different requirements and so on.
>
> --
> Matthew Garrett | mjg59(a)srcf.ucam.org
>

So what should be done then? This is not the most annoying of bugs,
but still a bug.

Regards,
Pedro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: vmscan: convert direct reclaim tracepoint to DEFINE_EVENT
Next: [PATCH 3/7] ACPI: Register EC io ports in /proc/ioports