Jeff Garzik wrote:
> Tejun Heo wrote:
>> Arjan van de Ven wrote:
>>> I'd be interested in finding out how to best test this; if the bios is
>>> really broken I'd love to add a test to the Linux-ready Firmware
>>> Developer Kit for this, so that BIOS developers can make sure future
>>> bioses do not
Tejun Heo wrote:
Arjan van de Ven wrote:
I'd be interested in finding out how to best test this; if the bios is
really broken I'd love to add a test to the Linux-ready Firmware
Developer Kit for this, so that BIOS developers can make sure future
bioses do not suffer from this bug...
As reporte
Arjan van de Ven wrote:
> I'd be interested in finding out how to best test this; if the bios is
> really broken I'd love to add a test to the Linux-ready Firmware
> Developer Kit for this, so that BIOS developers can make sure future
> bioses do not suffer from this bug...
As reported, this is al
14 Oca 2007 Paz 20:06 tarihinde, Arjan van de Ven şunları yazmıştı:
> Hi,
Hi,
> I'd be interested in finding out how to best test this; if the bios is
> really broken I'd love to add a test to the Linux-ready Firmware
> Developer Kit for this, so that BIOS developers can make sure future
> biose
On Sun, 2007-01-14 at 19:59 +0200, Faik Uygur wrote:
> 14 Oca 2007 Paz 03:23 tarihinde, Robert Hancock şunları yazmıştı:
> >> [...]
> >> > Since you're getting to this point I think this has to be some kind of
> > BIOS interaction causing this. The only thing that happens after the
> > "Entering
14 Oca 2007 Paz 03:23 tarihinde, Robert Hancock şunları yazmıştı:
>> [...]
>> > Since you're getting to this point I think this has to be some kind of
> BIOS interaction causing this. The only thing that happens after the
> "Entering sleep state" is that the kernel writes to some ACPI registers
>
14 Oca 2007 Paz 05:18 tarihinde şunları yazmıştınız:
>> [...]
> > Since you're getting to this point I think this has to be some kind of
> > BIOS interaction causing this. The only thing that happens after the
> > "Entering sleep state" is that the kernel writes to some ACPI registers
> > to tell t
Robert Hancock wrote:
Faik Uygur wrote:
What happens when you try to shutdown?
Does not shutdown and freezes.
Hand copied last messages seen on console:
Synchronizing SCSI cache for disk sda:
ACPI: PCI Interrupt for device :06:08.0 disabled
Power down.
acpi_power_off called
hwsleep-02
Faik Uygur wrote:
What happens when you try to shutdown?
Does not shutdown and freezes.
Hand copied last messages seen on console:
Synchronizing SCSI cache for disk sda:
ACPI: PCI Interrupt for device :06:08.0 disabled
Power down.
acpi_power_off called
hwsleep-0285 [01] enter_sleep_sta
Hello Tejun,
13 Oca 2007 Cts 03:12 tarihinde şunları yazmıştınız:
> If possible, please post dmesg of shutting down.
I have taken more detailed dmesg outputs of three configs with ATA_DEBUG and
ATA_VERBOSE_DEBUG defined. You can find them at this address:
http://cekirdek.pardus.org.tr/~faik/t
13 Oca 2007 Cts 03:12 tarihinde, Tejun Heo şunları yazmıştı:
> Hello,
Hello,
Thanks for the response.
> [...]
> Does everything else work okay?
> Can you access devices attached to
> ahci?
Yes. While the machine is on, there seems to be no problem at all. Everything
works great.
> What
Hello,
Faik Uygur wrote:
> We have a Sony PCG-6H1M laptop. It started failing to poweroff with our
> switch
> from 2.6.16 stable series kernels to 2.6.18 stable series. Rebooting works.
>
> While searching for the cause, I have found these reported bug reports in the
> kernel bugzilla which ma
12 matches
Mail list logo
