linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Berthold Cogel <cogel@rrz.uni-koeln.de>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff
Date: Wed, 10 Jan 2007 01:53:50 +0100	[thread overview]
Message-ID: <45A4391E.7080805@rrz.uni-koeln.de> (raw)
In-Reply-To: <45A29C09.8050901@linux.intel.com>

Alexey Starikovskiy schrieb:
> Berthold Cogel wrote:
>> Alexey Starikovskiy schrieb:
>>
>>  
>>>> Hello Alex,
>>>>
>>>> I still get the same diffs. Except the yenta part of course. And the
>>>> system is still rebooting.
>>>>
>>>> Berthold
>>>>         
>>> Good, yenta is cleared :) Could you replace /drivers/acpi/ec.c with the
>>> version from 2.6.19.x and try again?
>>>
>>> Regards,
>>>    Alex.
>>>     
>>
>> Hi Alex!
>>
>> I did what you suggested. First I replaced ec.c in linux-2.6.20-rc2 (see
>> attached dmesg-2.6.20-rc2.ec.txt) with the version from linux-2.6.19.1
>> and in a second step I also replaced i2c_ec.c and i2c_ec.h
>> (dmesg-2.6.20-rc2.i2c_ec.txt).
>>
>> In both cases the only result I can see is the absence of the 'ACPI: EC:
>> evaluating' messages in the logs. The system is still rebooting instead
>> of doing a clean shutdown.
>>
>> Regards,
>> Berthold
>>
>>   
> Excellent, ACPI printing of queries is cleared as well :)
> There are two ways to debug further... git-bisect and unloading modules
> before shutdown (or not loading them)...
> While second is easier and could isolate a module, the first could be
> way more productive:
> http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
> 
> 
> Thanks in advance,
>    Alex.
> 

Hi Alex!

I will have to set up git first for the bisect way. So I decided to give
the second way a try.

The module in question is ehci_hcd. After blacklisting it, 'shutdown -h
now' worked fine.

Here is the output of lspci for the system:

acer01:~# lspci
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV
Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV
Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV
Processor to I/O Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV
Processor to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2
EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility
Radeon 9600 M10]
02:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG
Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394
Host Controller
02:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
FlashMedia Controller


Regards,
Berthold



  reply	other threads:[~2007-01-10  0:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26  0:15 Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff Berthold Cogel
2006-12-28 22:16 ` Adrian Bunk
2007-01-01 23:41   ` Berthold Cogel
2007-01-02 19:07     ` Adrian Bunk
2007-02-06  3:28       ` Len Brown
2007-02-06  3:46         ` Adrian Bunk
2007-02-11 22:01           ` Berthold Cogel
2007-01-04 19:07     ` Alexey Starikovskiy
2007-01-06  0:09       ` Berthold Cogel
2007-01-06  8:52         ` Alexey Starikovskiy
2007-01-07 18:37           ` Berthold Cogel
2007-01-08 19:31             ` Alexey Starikovskiy
2007-01-10  0:53               ` Berthold Cogel [this message]
2007-01-10 11:51                 ` Alexey Starikovskiy
2007-01-11  0:45                   ` Berthold Cogel

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=45A4391E.7080805@rrz.uni-koeln.de \
    --to=cogel@rrz.uni-koeln.de \
    --cc=alexey.y.starikovskiy@linux.intel.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).