Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-11 Thread Berthold Cogel
Adrian Bunk schrieb:
> On Mon, Feb 05, 2007 at 10:28:34PM -0500, Len Brown wrote:
>>> On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
>> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
>> with linux-2.6.20-rc kernels. The system reboots instead.
>> I've checked linux-2.6.19.1 with an almost identical .config file
>> (differences because of new or changed options). For pre 2.6.20 kernels
>> shutdown works for my computer.
>> Try CONFIG_USB=n
> 
> CONFIG_USB_SUSPEND=n is most likely enough.
> 
> That's an unfixed 2.6.20-rc regression reported more than once, the 
> first time in December last year...
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=7945
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7828
> 
>> -Len
> 
> cu
> Adrian
> 

Hi!

CONFIG_USB_SUSPEND=n does the job. But the patch from
http://bugzilla.kernel.org/show_bug.cgi?id=7828#c29 works for my system
too (with CONFIG_USB_SUSPEND=y). The bugreport was made for an ACER
Travelmate 4001 WMLi, which is almost identical to my Acer Extensa 3002
WLMi.


Regards,
Berthold

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-11 Thread Berthold Cogel
Adrian Bunk schrieb:
 On Mon, Feb 05, 2007 at 10:28:34PM -0500, Len Brown wrote:
 On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
 with linux-2.6.20-rc kernels. The system reboots instead.
 I've checked linux-2.6.19.1 with an almost identical .config file
 (differences because of new or changed options). For pre 2.6.20 kernels
 shutdown works for my computer.
 Try CONFIG_USB=n
 
 CONFIG_USB_SUSPEND=n is most likely enough.
 
 That's an unfixed 2.6.20-rc regression reported more than once, the 
 first time in December last year...
 
 http://bugzilla.kernel.org/show_bug.cgi?id=7945
 
 http://bugzilla.kernel.org/show_bug.cgi?id=7828
 
 -Len
 
 cu
 Adrian
 

Hi!

CONFIG_USB_SUSPEND=n does the job. But the patch from
http://bugzilla.kernel.org/show_bug.cgi?id=7828#c29 works for my system
too (with CONFIG_USB_SUSPEND=y). The bugreport was made for an ACER
Travelmate 4001 WMLi, which is almost identical to my Acer Extensa 3002
WLMi.


Regards,
Berthold

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-05 Thread Adrian Bunk
On Mon, Feb 05, 2007 at 10:28:34PM -0500, Len Brown wrote:
> > On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
> 
> > > >> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> > > >> with linux-2.6.20-rc kernels. The system reboots instead.
> > > >> I've checked linux-2.6.19.1 with an almost identical .config file
> > > >> (differences because of new or changed options). For pre 2.6.20 kernels
> > > >> shutdown works for my computer.
> 
> Try CONFIG_USB=n

CONFIG_USB_SUSPEND=n is most likely enough.

That's an unfixed 2.6.20-rc regression reported more than once, the 
first time in December last year...

> http://bugzilla.kernel.org/show_bug.cgi?id=7945

http://bugzilla.kernel.org/show_bug.cgi?id=7828

> -Len

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-05 Thread Len Brown
> On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:

> > >> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> > >> with linux-2.6.20-rc kernels. The system reboots instead.
> > >> I've checked linux-2.6.19.1 with an almost identical .config file
> > >> (differences because of new or changed options). For pre 2.6.20 kernels
> > >> shutdown works for my computer.

Try CONFIG_USB=n

http://bugzilla.kernel.org/show_bug.cgi?id=7945

-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-05 Thread Len Brown
 On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:

   'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
   with linux-2.6.20-rc kernels. The system reboots instead.
   I've checked linux-2.6.19.1 with an almost identical .config file
   (differences because of new or changed options). For pre 2.6.20 kernels
   shutdown works for my computer.

Try CONFIG_USB=n

http://bugzilla.kernel.org/show_bug.cgi?id=7945

-Len
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-02-05 Thread Adrian Bunk
On Mon, Feb 05, 2007 at 10:28:34PM -0500, Len Brown wrote:
  On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
 
'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
with linux-2.6.20-rc kernels. The system reboots instead.
I've checked linux-2.6.19.1 with an almost identical .config file
(differences because of new or changed options). For pre 2.6.20 kernels
shutdown works for my computer.
 
 Try CONFIG_USB=n

CONFIG_USB_SUSPEND=n is most likely enough.

That's an unfixed 2.6.20-rc regression reported more than once, the 
first time in December last year...

 http://bugzilla.kernel.org/show_bug.cgi?id=7945

http://bugzilla.kernel.org/show_bug.cgi?id=7828

 -Len

cu
Adrian

-- 

   Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   Only a promise, Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-10 Thread Berthold Cogel
Alexey Starikovskiy schrieb:
> Berthold Cogel wrote:
>> 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.
>>
>>   
> Hi Berthold,
> 
> That is good news, but with ehci_hcd you basically disable the whole USB
> subsystem. Please try to locate more
> by turning off USB options in your kernel config, starting with USB
> suspend.
> Probably, USB maintainers could give you some more hints on there to look.
> 
> Regards,
>Alex.

Hello Alex!

How did you guess ...

It's USB_SUSPEND.


Regards,
Berthold
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-10 Thread Alexey Starikovskiy

Berthold Cogel wrote:

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.

  

Hi Berthold,

That is good news, but with ehci_hcd you basically disable the whole USB 
subsystem. Please try to locate more

by turning off USB options in your kernel config, starting with USB suspend.
Probably, USB maintainers could give you some more hints on there to look.

Regards,
   Alex.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-10 Thread Alexey Starikovskiy

Berthold Cogel wrote:

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.

  

Hi Berthold,

That is good news, but with ehci_hcd you basically disable the whole USB 
subsystem. Please try to locate more

by turning off USB options in your kernel config, starting with USB suspend.
Probably, USB maintainers could give you some more hints on there to look.

Regards,
   Alex.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-10 Thread Berthold Cogel
Alexey Starikovskiy schrieb:
 Berthold Cogel wrote:
 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.

   
 Hi Berthold,
 
 That is good news, but with ehci_hcd you basically disable the whole USB
 subsystem. Please try to locate more
 by turning off USB options in your kernel config, starting with USB
 suspend.
 Probably, USB maintainers could give you some more hints on there to look.
 
 Regards,
Alex.

Hello Alex!

How did you guess ...

It's USB_SUSPEND.


Regards,
Berthold
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-09 Thread Berthold Cogel
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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-09 Thread Berthold Cogel
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


-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-08 Thread Alexey Starikovskiy

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-08 Thread Alexey Starikovskiy

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.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-07 Thread Berthold Cogel
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



PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1035284k/1047424k available (1555k kernel code, 11592k reserved, 597k 
data, 168k init, 129920k highmem)
virtual kernel memory layout:
fixmap  : 0xfffaa000 - 0xf000   ( 340 kB)
pkmap   : 0xff80 - 0xffc0   (4096 kB)
vmalloc : 0xf880 - 0xff7fe000   ( 111 MB)
lowmem  : 0xc000 - 0xf800   ( 896 MB)
  .init : 0xc031e000 - 0xc0348000   ( 168 kB)
  .data : 0xc0284efd - 0xc031a3d0   ( 597 kB)
  .text : 0xc010 - 0xc0284efd   (1555 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3199.23 BogoMIPS (lpj=6398466)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9f9bf    0180 
 
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9f9bf   2040 0180 
 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) M processor 1.60GHz stepping 06
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0440)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd782, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
Boot video device is :01:00.0
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *6)
ACPI: PCI Interrupt Link [LNKB] (IRQs *10)
ACPI: PCI Interrupt Link [LNKC] (IRQs *6)
ACPI: PCI Interrupt Link [LNKD] (IRQs *6)
ACPI: PCI Interrupt Link [LNKE] (IRQs *10)
ACPI: PCI Interrupt Link [LNKF] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 6) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PFN1] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 9 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:04: ioport range 0x164e-0x164f has been reserved
PCI: Bridge: :00:01.0
  IO window: 3000-3fff
  MEM window: d010-d01f
  PREFETCH window: d800-dfff
PCI: Bus 3, cardbus bridge: :02:06.0
  IO window: 4000-40ff
  IO window: 4400-44ff
  PREFETCH window: 5000-53ff
  MEM window: 5800-5bff
PCI: Bridge: :00:1e.0
  IO window: 4000-4fff
  MEM window: d020-d05f
  PREFETCH window: 5000-55ff
PCI: Setting latency timer of device :00:1e.0 to 64
PCI: Enabling device :02:06.0 (0104 -> 0107)
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt :02:06.0[A] -> Link [LNKE] -> GSI 10 (level, low) -> 
IRQ 10
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag at 0x37 set to 0x1
highmem bounce pool size: 64 pages
io scheduler noop registered (default)
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt Link [LNKA] 

Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-07 Thread Berthold Cogel
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



PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1035284k/1047424k available (1555k kernel code, 11592k reserved, 597k 
data, 168k init, 129920k highmem)
virtual kernel memory layout:
fixmap  : 0xfffaa000 - 0xf000   ( 340 kB)
pkmap   : 0xff80 - 0xffc0   (4096 kB)
vmalloc : 0xf880 - 0xff7fe000   ( 111 MB)
lowmem  : 0xc000 - 0xf800   ( 896 MB)
  .init : 0xc031e000 - 0xc0348000   ( 168 kB)
  .data : 0xc0284efd - 0xc031a3d0   ( 597 kB)
  .text : 0xc010 - 0xc0284efd   (1555 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3199.23 BogoMIPS (lpj=6398466)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9f9bf    0180 
 
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9f9bf   2040 0180 
 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) M processor 1.60GHz stepping 06
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0440)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd782, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
Boot video device is :01:00.0
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *6)
ACPI: PCI Interrupt Link [LNKB] (IRQs *10)
ACPI: PCI Interrupt Link [LNKC] (IRQs *6)
ACPI: PCI Interrupt Link [LNKD] (IRQs *6)
ACPI: PCI Interrupt Link [LNKE] (IRQs *10)
ACPI: PCI Interrupt Link [LNKF] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 6) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PFN1] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 9 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try pci=routeirq.  If it helps, post a report
pnp: 00:04: ioport range 0x164e-0x164f has been reserved
PCI: Bridge: :00:01.0
  IO window: 3000-3fff
  MEM window: d010-d01f
  PREFETCH window: d800-dfff
PCI: Bus 3, cardbus bridge: :02:06.0
  IO window: 4000-40ff
  IO window: 4400-44ff
  PREFETCH window: 5000-53ff
  MEM window: 5800-5bff
PCI: Bridge: :00:1e.0
  IO window: 4000-4fff
  MEM window: d020-d05f
  PREFETCH window: 5000-55ff
PCI: Setting latency timer of device :00:1e.0 to 64
PCI: Enabling device :02:06.0 (0104 - 0107)
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt :02:06.0[A] - Link [LNKE] - GSI 10 (level, low) - 
IRQ 10
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag at 0x37 set to 0x1
highmem bounce pool size: 64 pages
io scheduler noop registered (default)
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 6
PCI: setting 

Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-06 Thread Alexey Starikovskiy

Berthold Cogel wrote:

Alexey Starikovskiy schrieb:
  

Berthold Cogel wrote:


Adrian Bunk schrieb:
 
  

On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:

   


Hello!
  
  

Hi Berthold!

   


'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
with linux-2.6.20-rc kernels. The system reboots instead.
I've checked linux-2.6.19.1 with an almost identical .config file
(differences because of new or changed options). For pre 2.6.20 kernels
shutdown works for my computer.
...
  
  

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.19

   


Regards,

Berthold Cogel
  
  

cu
Adrian




Hello Adrian,

I've attached the informations you requested.

In additon to the poweroff problem I see a lot of messages with
linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:

kernel: ACPI: EC: evaluating _Q80
kernel: ACPI: EC: evaluating _Q81
kernel: ACPI: EC: evaluating _Q09
kernel: ACPI: EC: evaluating _Q20

I'm running Debian testing/unstable with 'homemade' kernels. The laptop
is one of those using the Smart Battery System.


Berthold
  
  

Well, I see a lot of differences not related to ACPI...
20c3
Processor caps differ...
< CPU: After all inits, caps: afe9f9bf   0040
0180  
---


CPU: After all inits, caps: afe9f9bf   2040
  

0180  

Prefetch for PCMCIA differ
68,69c52,53
<   PREFETCH window: 5000-51ff
<   MEM window: 5400-55ff
---


  PREFETCH window: 5000-53ff
  MEM window: 5800-5bff
  

73c57
<   PREFETCH window: 5000-52ff
---


  PREFETCH window: 5000-55ff
  

This one is new as well...
168a156


Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
  

Berthold,
Could you please check if disabling PCMCIA changes situation?

Regards,
   Alex.






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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-06 Thread Alexey Starikovskiy

Berthold Cogel wrote:

Alexey Starikovskiy schrieb:
  

Berthold Cogel wrote:


Adrian Bunk schrieb:
 
  

On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:

   


Hello!
  
  

Hi Berthold!

   


'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
with linux-2.6.20-rc kernels. The system reboots instead.
I've checked linux-2.6.19.1 with an almost identical .config file
(differences because of new or changed options). For pre 2.6.20 kernels
shutdown works for my computer.
...
  
  

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.19

   


Regards,

Berthold Cogel
  
  

cu
Adrian




Hello Adrian,

I've attached the informations you requested.

In additon to the poweroff problem I see a lot of messages with
linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:

kernel: ACPI: EC: evaluating _Q80
kernel: ACPI: EC: evaluating _Q81
kernel: ACPI: EC: evaluating _Q09
kernel: ACPI: EC: evaluating _Q20

I'm running Debian testing/unstable with 'homemade' kernels. The laptop
is one of those using the Smart Battery System.


Berthold
  
  

Well, I see a lot of differences not related to ACPI...
20c3
Processor caps differ...
 CPU: After all inits, caps: afe9f9bf   0040
0180  
---


CPU: After all inits, caps: afe9f9bf   2040
  

0180  

Prefetch for PCMCIA differ
68,69c52,53
   PREFETCH window: 5000-51ff
   MEM window: 5400-55ff
---


  PREFETCH window: 5000-53ff
  MEM window: 5800-5bff
  

73c57
   PREFETCH window: 5000-52ff
---


  PREFETCH window: 5000-55ff
  

This one is new as well...
168a156


Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
  

Berthold,
Could you please check if disabling PCMCIA changes situation?

Regards,
   Alex.






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.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-05 Thread Berthold Cogel
Alexey Starikovskiy schrieb:
> Berthold Cogel wrote:
>> Adrian Bunk schrieb:
>>  
>>> On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:
>>>
>>>
 Hello!
   
>>> Hi Berthold!
>>>
>>>
 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
 with linux-2.6.20-rc kernels. The system reboots instead.
 I've checked linux-2.6.19.1 with an almost identical .config file
 (differences because of new or changed options). For pre 2.6.20 kernels
 shutdown works for my computer.
 ...
   
>>> Thanks for your report.
>>>
>>> Please send:
>>> - the .config for 2.6.20-rc2
>>> - the output of "dmesg -s 100" with 2.6.20-rc2
>>> - the output of "dmesg -s 100" with 2.6.19
>>>
>>>
 Regards,

 Berthold Cogel
   
>>> cu
>>> Adrian
>>>
>>> 
>>
>> Hello Adrian,
>>
>> I've attached the informations you requested.
>>
>> In additon to the poweroff problem I see a lot of messages with
>> linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:
>>
>> kernel: ACPI: EC: evaluating _Q80
>> kernel: ACPI: EC: evaluating _Q81
>> kernel: ACPI: EC: evaluating _Q09
>> kernel: ACPI: EC: evaluating _Q20
>>
>> I'm running Debian testing/unstable with 'homemade' kernels. The laptop
>> is one of those using the Smart Battery System.
>>
>>
>> Berthold
>>   
> Well, I see a lot of differences not related to ACPI...
> 20c3
> Processor caps differ...
> < CPU: After all inits, caps: afe9f9bf   0040
> 0180  
> ---
>> CPU: After all inits, caps: afe9f9bf   2040
> 0180  
> 
> Prefetch for PCMCIA differ
> 68,69c52,53
> <   PREFETCH window: 5000-51ff
> <   MEM window: 5400-55ff
> ---
>>   PREFETCH window: 5000-53ff
>>   MEM window: 5800-5bff
> 73c57
> <   PREFETCH window: 5000-52ff
> ---
>>   PREFETCH window: 5000-55ff
> 
> This one is new as well...
> 168a156
>> Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
> 
> Berthold,
> Could you please check if disabling PCMCIA changes situation?
> 
> Regards,
>Alex.
> 
> 
>

Hello Alex,

I still get the same diffs. Except the yenta part of course. And the
system is still rebooting.

Berthold
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-05 Thread Berthold Cogel
Alexey Starikovskiy schrieb:
 Berthold Cogel wrote:
 Adrian Bunk schrieb:
  
 On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:


 Hello!
   
 Hi Berthold!


 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
 with linux-2.6.20-rc kernels. The system reboots instead.
 I've checked linux-2.6.19.1 with an almost identical .config file
 (differences because of new or changed options). For pre 2.6.20 kernels
 shutdown works for my computer.
 ...
   
 Thanks for your report.

 Please send:
 - the .config for 2.6.20-rc2
 - the output of dmesg -s 100 with 2.6.20-rc2
 - the output of dmesg -s 100 with 2.6.19


 Regards,

 Berthold Cogel
   
 cu
 Adrian

 

 Hello Adrian,

 I've attached the informations you requested.

 In additon to the poweroff problem I see a lot of messages with
 linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:

 kernel: ACPI: EC: evaluating _Q80
 kernel: ACPI: EC: evaluating _Q81
 kernel: ACPI: EC: evaluating _Q09
 kernel: ACPI: EC: evaluating _Q20

 I'm running Debian testing/unstable with 'homemade' kernels. The laptop
 is one of those using the Smart Battery System.


 Berthold
   
 Well, I see a lot of differences not related to ACPI...
 20c3
 Processor caps differ...
  CPU: After all inits, caps: afe9f9bf   0040
 0180  
 ---
 CPU: After all inits, caps: afe9f9bf   2040
 0180  
 
 Prefetch for PCMCIA differ
 68,69c52,53
PREFETCH window: 5000-51ff
MEM window: 5400-55ff
 ---
   PREFETCH window: 5000-53ff
   MEM window: 5800-5bff
 73c57
PREFETCH window: 5000-52ff
 ---
   PREFETCH window: 5000-55ff
 
 This one is new as well...
 168a156
 Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
 
 Berthold,
 Could you please check if disabling PCMCIA changes situation?
 
 Regards,
Alex.
 
 


Hello Alex,

I still get the same diffs. Except the yenta part of course. And the
system is still rebooting.

Berthold
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-04 Thread Alexey Starikovskiy

Berthold Cogel wrote:

Adrian Bunk schrieb:
  

On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:



Hello!
  

Hi Berthold!



'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
with linux-2.6.20-rc kernels. The system reboots instead.
I've checked linux-2.6.19.1 with an almost identical .config file
(differences because of new or changed options). For pre 2.6.20 kernels
shutdown works for my computer.
...
  

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.19



Regards,

Berthold Cogel
  

cu
Adrian




Hello Adrian,

I've attached the informations you requested.

In additon to the poweroff problem I see a lot of messages with
linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:

kernel: ACPI: EC: evaluating _Q80
kernel: ACPI: EC: evaluating _Q81
kernel: ACPI: EC: evaluating _Q09
kernel: ACPI: EC: evaluating _Q20

I'm running Debian testing/unstable with 'homemade' kernels. The laptop
is one of those using the Smart Battery System.


Berthold
  

Well, I see a lot of differences not related to ACPI...
20c3
Processor caps differ...
< CPU: After all inits, caps: afe9f9bf   0040 
0180  

---
> CPU: After all inits, caps: afe9f9bf   2040 
0180  


Prefetch for PCMCIA differ
68,69c52,53
<   PREFETCH window: 5000-51ff
<   MEM window: 5400-55ff
---
>   PREFETCH window: 5000-53ff
>   MEM window: 5800-5bff
73c57
<   PREFETCH window: 5000-52ff
---
>   PREFETCH window: 5000-55ff

This one is new as well...
168a156
> Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06

Berthold,
Could you please check if disabling PCMCIA changes situation?

Regards,
   Alex.


1,18c1
< e entries: 4096 (order: 12, 16384 bytes)
< Console: colour VGA+ 80x25
< Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
< Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
< Memory: 1035160k/1047424k available (1690k kernel code, 11716k reserved, 575k data, 176k init, 129920k highmem)
< virtual kernel memory layout:
< fixmap  : 0xfffaa000 - 0xf000   ( 340 kB)
< pkmap   : 0xff80 - 0xffc0   (4096 kB)
< vmalloc : 0xf880 - 0xff7fe000   ( 111 MB)
< lowmem  : 0xc000 - 0xf800   ( 896 MB)
<   .init : 0xc033a000 - 0xc0366000   ( 176 kB)
<   .data : 0xc02a6982 - 0xc03368d0   ( 575 kB)
<   .text : 0xc010 - 0xc02a6982   (1690 kB)
< Checking if this processor honours the WP bit even in supervisor mode... Ok.
< Calibrating delay using timer specific routine.. 3199.22 BogoMIPS (lpj=6398450)
< Mount-cache hash table entries: 512
< CPU: After generic identify, caps: afe9f9bf    0180  
< CPU: L1 I cache: 32K, L1 D cache: 32K
---
> he: 32K
20c3
< CPU: After all inits, caps: afe9f9bf   0040 0180  
---
> CPU: After all inits, caps: afe9f9bf   2040 0180  
38d20
< PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
40a23,24
> PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
> Please report the result to linux-kernel to fix this permanently
68,69c52,53
<   PREFETCH window: 5000-51ff
<   MEM window: 5400-55ff
---
>   PREFETCH window: 5000-53ff
>   MEM window: 5800-5bff
73c57
<   PREFETCH window: 5000-52ff
---
>   PREFETCH window: 5000-55ff
110a95
> ACPI: EC: evaluating _Q80
117a103
> 
141c127
< device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: [EMAIL PROTECTED]
---
> device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED]
145a132
> input: AT Translated Set 2 keyboard as /class/input/input0
149,150c136
< Freeing unused kernel memory: 176k freed
< input: AT Translated Set 2 keyboard as /class/input/input0
---
> Freeing unused kernel memory: 168k freed
152c138,139
< Real Time Clock Driver v1.12ac
---
> ACPI: EC: evaluating _Q09
> ACPI: EC: evaluating _Q80
156d142
< input: PC Speaker as /class/input/input1
161a148,149
> ACPI: EC: evaluating _Q81
> input: PC Speaker as /class/input/input1
166d153
< ieee1394: Initialized config rom entry `ip1394'
168a156
> Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
172,174c160
< pcmcia: parent PCI bridge Memory window: 0x5000 - 0x52ff
< ACPI: PCI Interrupt :02:06.2[A] -> Link [LNKE] -> GSI 10 (level, low) -> IRQ 10
< ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10]  MMIO=[d020a000-d020a7ff]  Max Packet=[2048]  IR/IT contexts=[4/8]
---
> pcmcia: parent PCI bridge Memory window: 0x5000 - 0x55ff
177,178c163,164
< irda_init()
< NET: Registered protocol family 23
---
> ieee1394: Initialized config rom entry `ip1394'
> ACPI: PCI Interrupt :02:06.2[A] -> 

Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-04 Thread Alexey Starikovskiy

Berthold Cogel wrote:

Adrian Bunk schrieb:
  

On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:



Hello!
  

Hi Berthold!



'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
with linux-2.6.20-rc kernels. The system reboots instead.
I've checked linux-2.6.19.1 with an almost identical .config file
(differences because of new or changed options). For pre 2.6.20 kernels
shutdown works for my computer.
...
  

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.19



Regards,

Berthold Cogel
  

cu
Adrian




Hello Adrian,

I've attached the informations you requested.

In additon to the poweroff problem I see a lot of messages with
linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:

kernel: ACPI: EC: evaluating _Q80
kernel: ACPI: EC: evaluating _Q81
kernel: ACPI: EC: evaluating _Q09
kernel: ACPI: EC: evaluating _Q20

I'm running Debian testing/unstable with 'homemade' kernels. The laptop
is one of those using the Smart Battery System.


Berthold
  

Well, I see a lot of differences not related to ACPI...
20c3
Processor caps differ...
 CPU: After all inits, caps: afe9f9bf   0040 
0180  

---
 CPU: After all inits, caps: afe9f9bf   2040 
0180  


Prefetch for PCMCIA differ
68,69c52,53
   PREFETCH window: 5000-51ff
   MEM window: 5400-55ff
---
   PREFETCH window: 5000-53ff
   MEM window: 5800-5bff
73c57
   PREFETCH window: 5000-52ff
---
   PREFETCH window: 5000-55ff

This one is new as well...
168a156
 Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06

Berthold,
Could you please check if disabling PCMCIA changes situation?

Regards,
   Alex.


1,18c1
 e entries: 4096 (order: 12, 16384 bytes)
 Console: colour VGA+ 80x25
 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
 Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
 Memory: 1035160k/1047424k available (1690k kernel code, 11716k reserved, 575k data, 176k init, 129920k highmem)
 virtual kernel memory layout:
 fixmap  : 0xfffaa000 - 0xf000   ( 340 kB)
 pkmap   : 0xff80 - 0xffc0   (4096 kB)
 vmalloc : 0xf880 - 0xff7fe000   ( 111 MB)
 lowmem  : 0xc000 - 0xf800   ( 896 MB)
   .init : 0xc033a000 - 0xc0366000   ( 176 kB)
   .data : 0xc02a6982 - 0xc03368d0   ( 575 kB)
   .text : 0xc010 - 0xc02a6982   (1690 kB)
 Checking if this processor honours the WP bit even in supervisor mode... Ok.
 Calibrating delay using timer specific routine.. 3199.22 BogoMIPS (lpj=6398450)
 Mount-cache hash table entries: 512
 CPU: After generic identify, caps: afe9f9bf    0180  
 CPU: L1 I cache: 32K, L1 D cache: 32K
---
 he: 32K
20c3
 CPU: After all inits, caps: afe9f9bf   0040 0180  
---
 CPU: After all inits, caps: afe9f9bf   2040 0180  
38d20
 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
40a23,24
 PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
 Please report the result to linux-kernel to fix this permanently
68,69c52,53
   PREFETCH window: 5000-51ff
   MEM window: 5400-55ff
---
   PREFETCH window: 5000-53ff
   MEM window: 5800-5bff
73c57
   PREFETCH window: 5000-52ff
---
   PREFETCH window: 5000-55ff
110a95
 ACPI: EC: evaluating _Q80
117a103
 
141c127
 device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: [EMAIL PROTECTED]
---
 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED]
145a132
 input: AT Translated Set 2 keyboard as /class/input/input0
149,150c136
 Freeing unused kernel memory: 176k freed
 input: AT Translated Set 2 keyboard as /class/input/input0
---
 Freeing unused kernel memory: 168k freed
152c138,139
 Real Time Clock Driver v1.12ac
---
 ACPI: EC: evaluating _Q09
 ACPI: EC: evaluating _Q80
156d142
 input: PC Speaker as /class/input/input1
161a148,149
 ACPI: EC: evaluating _Q81
 input: PC Speaker as /class/input/input1
166d153
 ieee1394: Initialized config rom entry `ip1394'
168a156
 Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
172,174c160
 pcmcia: parent PCI bridge Memory window: 0x5000 - 0x52ff
 ACPI: PCI Interrupt :02:06.2[A] - Link [LNKE] - GSI 10 (level, low) - IRQ 10
 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10]  MMIO=[d020a000-d020a7ff]  Max Packet=[2048]  IR/IT contexts=[4/8]
---
 pcmcia: parent PCI bridge Memory window: 0x5000 - 0x55ff
177,178c163,164
 irda_init()
 NET: Registered protocol family 23
---
 ieee1394: Initialized config rom entry `ip1394'
 ACPI: PCI Interrupt :02:06.2[A] - Link [LNKE] - GSI 10 (level, low) - IRQ 10
188,189c174,175
 hdc: ATAPI 

Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-02 Thread Adrian Bunk
On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
> Adrian Bunk schrieb:
> > On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:
> > 
> >> Hello!
> > 
> > Hi Berthold!
> > 
> >> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> >> with linux-2.6.20-rc kernels. The system reboots instead.
> >> I've checked linux-2.6.19.1 with an almost identical .config file
> >> (differences because of new or changed options). For pre 2.6.20 kernels
> >> shutdown works for my computer.
> >> ...
> > 
> > Thanks for your report.
> > 
> > Please send:
> > - the .config for 2.6.20-rc2
> > - the output of "dmesg -s 100" with 2.6.20-rc2
> > - the output of "dmesg -s 100" with 2.6.19
> 
> Hello Adrian,

Hi Berthold,

> I've attached the informations you requested.

thanks for this information.

> In additon to the poweroff problem I see a lot of messages with
> linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:
> 
> kernel: ACPI: EC: evaluating _Q80
> kernel: ACPI: EC: evaluating _Q81
> kernel: ACPI: EC: evaluating _Q09
> kernel: ACPI: EC: evaluating _Q20
> 
> I'm running Debian testing/unstable with 'homemade' kernels. The laptop
> is one of those using the Smart Battery System.

The ACPI warnings might be harmless, but there's nothing obvious I see 
outside of ACPI that might be related to your problem (ACPI maintainers 
Cc'ed).

> Berthold

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2007-01-02 Thread Adrian Bunk
On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
 Adrian Bunk schrieb:
  On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:
  
  Hello!
  
  Hi Berthold!
  
  'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
  with linux-2.6.20-rc kernels. The system reboots instead.
  I've checked linux-2.6.19.1 with an almost identical .config file
  (differences because of new or changed options). For pre 2.6.20 kernels
  shutdown works for my computer.
  ...
  
  Thanks for your report.
  
  Please send:
  - the .config for 2.6.20-rc2
  - the output of dmesg -s 100 with 2.6.20-rc2
  - the output of dmesg -s 100 with 2.6.19
 
 Hello Adrian,

Hi Berthold,

 I've attached the informations you requested.

thanks for this information.

 In additon to the poweroff problem I see a lot of messages with
 linux-2.6.20-rc2 that I do not see with linux-2.6.20-rc1:
 
 kernel: ACPI: EC: evaluating _Q80
 kernel: ACPI: EC: evaluating _Q81
 kernel: ACPI: EC: evaluating _Q09
 kernel: ACPI: EC: evaluating _Q20
 
 I'm running Debian testing/unstable with 'homemade' kernels. The laptop
 is one of those using the Smart Battery System.

The ACPI warnings might be harmless, but there's nothing obvious I see 
outside of ACPI that might be related to your problem (ACPI maintainers 
Cc'ed).

 Berthold

cu
Adrian

-- 

   Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   Only a promise, Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2006-12-28 Thread Adrian Bunk
On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:

> Hello!

Hi Berthold!

> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> with linux-2.6.20-rc kernels. The system reboots instead.
> I've checked linux-2.6.19.1 with an almost identical .config file
> (differences because of new or changed options). For pre 2.6.20 kernels
> shutdown works for my computer.
>...

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.20-rc2
- the output of "dmesg -s 100" with 2.6.19

> Regards,
> 
> Berthold Cogel

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff

2006-12-28 Thread Adrian Bunk
On Tue, Dec 26, 2006 at 01:15:38AM +0100, Berthold Cogel wrote:

 Hello!

Hi Berthold!

 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
 with linux-2.6.20-rc kernels. The system reboots instead.
 I've checked linux-2.6.19.1 with an almost identical .config file
 (differences because of new or changed options). For pre 2.6.20 kernels
 shutdown works for my computer.
...

Thanks for your report.

Please send:
- the .config for 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.20-rc2
- the output of dmesg -s 100 with 2.6.19

 Regards,
 
 Berthold Cogel

cu
Adrian

-- 

   Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   Only a promise, Lao Er said.
   Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/