public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Len Brown <len.brown@intel.com>,
	linux-kernel@vger.kernel.org,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: Linux 2.6.23-rc4: BAD regression
Date: Wed, 29 Aug 2007 23:45:01 +0400	[thread overview]
Message-ID: <46D5CCBD.5050103@suse.de> (raw)
In-Reply-To: <200708292135.57584.daniel.ritz-ml@swissonline.ch>

If you could open a bugreport at bugzilla.kernel.org in ACPI category
and attach
dmesg and acpidump output, that would help a lot. (I hope :( )

Thanks,
Alex.

Daniel Ritz wrote:
> On Wednesday 29 August 2007 06:41:41 Alexey Starikovskiy wrote:
>   
>> Daniel,
>> Does this patch help you, or do we need to revert the whole thing?
>>
>>     
>
> yes, this does the trick. the fan goes on again. thanks.
> if you still need additional debug output or if you want me to test
> a different patch just let me know.
>
> rgds
> -daniel
>
>   
>> Sorry for the trouble,
>> Alex.
>> Daniel Ritz wrote:
>>     
>>> tried that one on my old toshiba tecra 8000 laptop, almost killing it.
>>> the fan doesn't work any more...type 'make' and see the box dying.
>>> luckily my CPU doesn't commit suicide...bisected it to that one:
>>>
>>> cd8c93a4e04dce8f00d1ef3a476aac8bd65ae40b is first bad commit
>>> commit cd8c93a4e04dce8f00d1ef3a476aac8bd65ae40b
>>> Author: Alexey Starikovskiy <astarikovskiy@suse.de>
>>> Date:   Fri Aug 3 17:52:48 2007 -0400
>>>
>>>     ACPI: EC: If ECDT is not found, look up EC in DSDT.
>>>
>>>     Some ASUS laptops access EC space from device _INI methods, but do not
>>>     provide ECDT for early EC setup. In order to make them function properly,
>>>     there is a need to find EC is DSDT before any _INI is called.
>>>
>>>     Similar functionality was turned on by acpi_fake_ecdt=1 command line
>>>     before. Now it is on all the time.
>>>
>>>     http://bugzilla.kernel.org/show_bug.cgi?id=8598
>>>
>>>     Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de>
>>>     Signed-off-by: Len Brown <len.brown@intel.com>
>>>   
>>>       
>
>
>   


  reply	other threads:[~2007-08-29 19:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 23:29 Linux 2.6.23-rc4: BAD regression Daniel Ritz
2007-08-28 23:42 ` Linus Torvalds
2007-08-29  4:41 ` Alexey Starikovskiy
2007-08-29 19:35   ` Daniel Ritz
2007-08-29 19:45     ` Alexey Starikovskiy [this message]
2007-08-29 20:55       ` Daniel Ritz
2007-08-29 23:21 ` Luca Tettamanti
2007-08-30 17:07   ` Daniel Ritz
2007-08-30 17:21     ` Linus Torvalds
2007-08-30 19:17       ` Luca
2007-08-31  5:05       ` [PATCH] ACPI: EC: Check if boot_ec was really found in DSDT Alexey Starikovskiy
2007-08-31  5:22         ` Linus Torvalds
2007-08-31  5:29           ` Alexey Starikovskiy
2007-08-31  5:34             ` Andrew Morton
2007-08-31  5:47               ` mail client to send patches Alexey Starikovskiy
2007-08-31  7:07               ` [PATCH] ACPI: EC: Check if boot_ec was really found in DSDT Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D5CCBD.5050103@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox