2.6.19-rc4: known unfixed regressions

2.6.19-rc4: known unfixed regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way possibly
involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : PCI: MMCONFIG breakage
References : http://lkml.org/lkml/2006/10/27/251
Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
Status     : unknown, both BIOS and Direct work


Subject    : x86_64: oprofile doesn't work
References : http://lkml.org/lkml/2006/10/27/3
Submitter  : Prakash Punnoor <prakash@punnoor.de>
Status     : unknown


Subject    : T43p/T60/X60s: lose ACPI events after suspend/resume
References : http://lkml.org/lkml/2006/10/10/39
             http://lkml.org/lkml/2006/10/4/425
             http://lkml.org/lkml/2006/10/16/262
             http://bugzilla.kernel.org/show_bug.cgi?id=7408
             http://lkml.org/lkml/2006/10/30/251
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
             "Michael S. Tsirkin" <mst@mellanox.co.il>
             Hugh Dickins <hugh@veritas.com>
Status     : unknown


Subject    : sata-via doesn't detect anymore disks attached to VIA vt6421
References : http://bugzilla.kernel.org/show_bug.cgi?id=7255
Submitter  : Thierry Vignaud <tvignaud@mandriva.com>
Status     : unknown


Subject    : unable to rip cd
References : http://lkml.org/lkml/2006/10/13/100
Submitter  : Alex Romosan <romosan@sycorax.lbl.gov>
Status     : unknown


Subject    : cpufreq not working on AMD K8
References : http://lkml.org/lkml/2006/10/10/114
Submitter  : Christian <christiand59@web.de>
Status     : unknown


Subject    : SMP kernel can not generate ISA irq properly
References : http://lkml.org/lkml/2006/10/22/15
Submitter  : Komuro <komurojun-mbn@nifty.com>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : Thomas will investigate


Subject    : USB net drivers: missing MII select's
References : http://lkml.org/lkml/2006/10/25/209
Submitter  : Randy Dunlap <randy.dunlap@oracle.com>
Caused-By  : Arnd Bergmann <arnd@arndb.de>
             commit c41286fd42f3545513f8de9f61028120b6d38e89
Handled-By : Randy Dunlap <randy.dunlap@oracle.com>
             David Brownell <david-b@pacbell.net>
Status     : patches are being discussed

Re: 2.6.19-rc4: known unfixed regressions

[Greg KH]

On Tue, Oct 31, 2006 at 08:56:54PM +0100, Adrian Bunk wrote:
> This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
> that are not yet fixed in Linus' tree.
> 
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you caused a breakage or I'm considering you in any other way possibly
> involved with one or more of these issues.
> 
> Due to the huge amount of recipients, please trim the Cc when answering.
> 
> 
> Subject    : PCI: MMCONFIG breakage
> References : http://lkml.org/lkml/2006/10/27/251
> Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
> Status     : unknown, both BIOS and Direct work

This seems to be now fixed by using the proper pci config accesses.

thanks,

greg k-h

Re: 2.6.19-rc4: known unfixed regressions

[Arjan van de Ven]

On Tue, 2006-10-31 at 20:56 +0100, Adrian Bunk wrote:
> This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
> that are not yet fixed in Linus' tree.
> 
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you caused a breakage or I'm considering you in any other way possibly
> involved with one or more of these issues.
> 
> Due to the huge amount of recipients, please trim the Cc when answering.
> 
> 
> Subject    : PCI: MMCONFIG breakage
> References : http://lkml.org/lkml/2006/10/27/251
> Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
> Status     : unknown, both BIOS and Direct work
> 


hmm I see nothing MMCONFIG related here much....

Linux 2.6.19-rc4: known unfixed regressions (v2)

[Adrian Bunk]

This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way possibly
involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : i386: more DWARFs and strange messages
References : http://lkml.org/lkml/2006/10/29/127
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
Status     : unknown


Subject    : PCI: MMCONFIG breakage
References : http://lkml.org/lkml/2006/10/27/251
Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
Status     : unknown, both BIOS and Direct work


Subject    : x86_64: oprofile doesn't work
References : http://lkml.org/lkml/2006/10/27/3
Submitter  : Prakash Punnoor <prakash@punnoor.de>
Status     : unknown


Subject    : sata-via doesn't detect anymore disks attached to VIA vt6421
References : http://bugzilla.kernel.org/show_bug.cgi?id=7255
Submitter  : Thierry Vignaud <tvignaud@mandriva.com>
Status     : unknown


Subject    : unable to rip cd
References : http://lkml.org/lkml/2006/10/13/100
Submitter  : Alex Romosan <romosan@sycorax.lbl.gov>
Status     : unknown


Subject    : cpufreq not working on AMD K8
References : http://lkml.org/lkml/2006/10/10/114
Submitter  : Christian <christiand59@web.de>
Status     : unknown


Subject    : SMP kernel can not generate ISA irq properly
References : http://lkml.org/lkml/2006/10/22/15
Submitter  : Komuro <komurojun-mbn@nifty.com>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : Thomas will investigate


Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
References : http://lkml.org/lkml/2006/10/31/333
Submitter  : Ernst Herzberg <earny@net4u.de>
Status     : problem is being debugged


Subject    : ThinkPad T43p/T60/X60s: lose ACPI events after suspend/resume
References : http://lkml.org/lkml/2006/10/10/39
             http://lkml.org/lkml/2006/10/4/425
             http://lkml.org/lkml/2006/10/16/262
             http://bugzilla.kernel.org/show_bug.cgi?id=7408
             http://lkml.org/lkml/2006/10/30/251
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
             "Michael S. Tsirkin" <mst@mellanox.co.il>
             Hugh Dickins <hugh@veritas.com>
Status     : problem is being debugged


Subject    : x86_64: NR_IRQ increase causes slowdown in lmbench's fork
References : http://lkml.org/lkml/2006/11/2/192
Submitter  : Tim Chen <tim.c.chen@linux.intel.com>
Caused-By  : Eric W. Biederman <ebiederm@xmission.com>
             commit 550f2299ac8ffaba943cf211380d3a8d3fa75301
Status     : problem is being debugged


Subject    : USB net drivers: missing MII select's
References : http://lkml.org/lkml/2006/10/25/209
Submitter  : Randy Dunlap <randy.dunlap@oracle.com>
Caused-By  : Arnd Bergmann <arnd@arndb.de>
             commit c41286fd42f3545513f8de9f61028120b6d38e89
Handled-By : Randy Dunlap <randy.dunlap@oracle.com>
             David Brownell <david-b@pacbell.net>
Status     : patches are being discussed

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Dave Jones]

On Fri, Nov 03, 2006 at 03:41:32AM +0100, Adrian Bunk wrote:
 > This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
 > that are not yet fixed in Linus' tree.
 > 
 > If you find your name in the Cc header, you are either submitter of one
 > of the bugs, maintainer of an affectected subsystem or driver, a patch
 > of you caused a breakage or I'm considering you in any other way possibly
 > involved with one or more of these issues.
 > 
 > Due to the huge amount of recipients, please trim the Cc when answering.
 > 
 > Subject    : cpufreq not working on AMD K8
 > References : http://lkml.org/lkml/2006/10/10/114
 > Submitter  : Christian <christiand59@web.de>
 > Status     : unknown

As Mark mentioned in his followup, powernow-k8 didn't change in .19 at all.
I'm suspecting an ACPI change meant that we no longer find the PST tables
correctly.

Christian, can you post the full dmesg's from the working/broken kernels.
It may be useful to enable CONFIG_ACPI_DEBUG too.

	Dave

-- 
http://www.codemonkey.org.uk

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Alexey Starikovskiy]

Could this be a problem?
--------------------
...
CONFIG_ACPI_PROCESSOR=m
...
CONFIG_X86_POWERNOW_K8=y
...

Regards,
	Alex.

Dave Jones wrote:
> On Fri, Nov 03, 2006 at 03:41:32AM +0100, Adrian Bunk wrote:
>  > This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
>  > that are not yet fixed in Linus' tree.
>  > 
>  > If you find your name in the Cc header, you are either submitter of one
>  > of the bugs, maintainer of an affectected subsystem or driver, a patch
>  > of you caused a breakage or I'm considering you in any other way possibly
>  > involved with one or more of these issues.
>  > 
>  > Due to the huge amount of recipients, please trim the Cc when answering.
>  > 
>  > Subject    : cpufreq not working on AMD K8
>  > References : http://lkml.org/lkml/2006/10/10/114
>  > Submitter  : Christian <christiand59@web.de>
>  > Status     : unknown
> 
> As Mark mentioned in his followup, powernow-k8 didn't change in .19 at all.
> I'm suspecting an ACPI change meant that we no longer find the PST tables
> correctly.
> 
> Christian, can you post the full dmesg's from the working/broken kernels.
> It may be useful to enable CONFIG_ACPI_DEBUG too.
> 
> 	Dave
> 

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Dave Jones]

On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
 > Could this be a problem?
 > --------------------
 > ...
 > CONFIG_ACPI_PROCESSOR=m
 > ...
 > CONFIG_X86_POWERNOW_K8=y

Hmm, possibly.  Christian, does it work again if you set them both to =y ?

	Dave

-- 
http://www.codemonkey.org.uk

2.6.19-rc4: known unfixed regressions (v3)

[Adrian Bunk]

This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way possibly
involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : ipath driver MCEs system on load when HT chip present
References : http://bugzilla.kernel.org/show_bug.cgi?id=7455
Submitter  : Bryan O'Sullivan <bos@serpentine.com>
Caused-By  : Eric W. Biederman <ebiederm@xmission.com>
Status     : unknown


Subject    : i386: more DWARFs and strange messages
References : http://lkml.org/lkml/2006/10/29/127
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
Status     : unknown


Subject    : x86_64: oprofile doesn't work
References : http://lkml.org/lkml/2006/10/27/3
Submitter  : Prakash Punnoor <prakash@punnoor.de>
Status     : unknown


Subject    : sata-via doesn't detect anymore disks attached to VIA vt6421
References : http://bugzilla.kernel.org/show_bug.cgi?id=7255
Submitter  : Thierry Vignaud <tvignaud@mandriva.com>
Status     : unknown


Subject    : unable to rip cd
References : http://lkml.org/lkml/2006/10/13/100
Submitter  : Alex Romosan <romosan@sycorax.lbl.gov>
Status     : unknown


Subject    : SMP kernel can not generate ISA irq properly
References : http://lkml.org/lkml/2006/10/22/15
Submitter  : Komuro <komurojun-mbn@nifty.com>
Status     : unknown


Subject    : nfs-kernel-server does not start
References : http://bugzilla.kernel.org/show_bug.cgi?id=7457
Submitter  : Elimar Riesebieter <riesebie@lxtec.de>
Status     : problem is being debugged


Subject    : ThinkPad T60/X60: lose ACPI events after suspend/resume
References : http://lkml.org/lkml/2006/10/10/39
             http://lkml.org/lkml/2006/10/4/425
             http://lkml.org/lkml/2006/10/16/262
             http://bugzilla.kernel.org/show_bug.cgi?id=7408
             http://lkml.org/lkml/2006/10/30/251
             http://lkml.org/lkml/2006/11/3/244
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
             "Michael S. Tsirkin" <mst@mellanox.co.il>
Status     : problem is being debugged


Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
References : http://lkml.org/lkml/2006/10/31/333
Submitter  : Ernst Herzberg <earny@net4u.de>
Status     : problem is being debugged


Subject    : x86_64: NR_IRQ increase causes 11.5% slowdown
                     in lmbench's fork benchmark
References : http://lkml.org/lkml/2006/11/2/192
Submitter  : Tim Chen <tim.c.chen@linux.intel.com>
Caused-By  : Eric W. Biederman <ebiederm@xmission.com>
             commit 550f2299ac8ffaba943cf211380d3a8d3fa75301
Handled-By : Eric W. Biederman <ebiederm@xmission.com>
             Andi Kleen <ak@suse.de>
Status     : problem is being debugged


Subject    : cpufreq not working on AMD K8
References : http://lkml.org/lkml/2006/10/10/114
             http://lkml.org/lkml/2006/11/3/26
Submitter  : Christian <christiand59@web.de>
Handled-By : Dave Jones <davej@redhat.com>
Status     : Dave is investigating


Subject    : PCI: MMCONFIG breakage
References : http://lkml.org/lkml/2006/10/27/251
Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
Status     : unknown, both BIOS and Direct work
             Greg said it should already be fixed

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Jeff Chua]

On 11/5/06, Adrian Bunk <bunk@stusta.de> wrote:

> Subject    : PCI: MMCONFIG breakage
> References : http://lkml.org/lkml/2006/10/27/251
> Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
> Status     : unknown, both BIOS and Direct work
>              Greg said it should already be fixed

Here's results with vanilla 2.6.19-rc4 (gcc version 3.4.5) ...

1) PCI access mode (Any) ... FAILED

2) PCI access mode (MMConfig) ... FAILED

3) PCI access mode (Direct) ... PASSED

4) PCI access mode (BIOS) ... PASSED

Looks like it's still having problem with Dell Optiplex GX620.

Thanks,
Jeff.

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Michael S. Tsirkin]

Quoting r. Adrian Bunk <bunk@stusta.de>:
> Subject    : ThinkPad T60/X60: lose ACPI events after suspend/resume
> References : http://lkml.org/lkml/2006/10/10/39
>              http://lkml.org/lkml/2006/10/4/425
>              http://lkml.org/lkml/2006/10/16/262
>              http://bugzilla.kernel.org/show_bug.cgi?id=7408
>              http://lkml.org/lkml/2006/10/30/251
>              http://lkml.org/lkml/2006/11/3/244
> Submitter  : Martin Lorenz <martin@lorenz.eu.org>
>              "Michael S. Tsirkin" <mst@mellanox.co.il>
> Status     : problem is being debugged

Add to that
http://lkml.org/lkml/2006/11/1/84
and a patch in
http://lkml.org/lkml/2006/11/1/294

I have been running f9dadfa71bc594df09044da61d1c72701121d802 which hs this patch
for several days now and this issue seem to be fixed.

I plan to re-test on -rc5 when that's out.

-- 
MST

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Adrian Bunk]

On Sun, Nov 05, 2006 at 03:26:07PM +0200, Michael S. Tsirkin wrote:
> Quoting r. Adrian Bunk <bunk@stusta.de>:
> > Subject    : ThinkPad T60/X60: lose ACPI events after suspend/resume
> > References : http://lkml.org/lkml/2006/10/10/39
> >              http://lkml.org/lkml/2006/10/4/425
> >              http://lkml.org/lkml/2006/10/16/262
> >              http://bugzilla.kernel.org/show_bug.cgi?id=7408
> >              http://lkml.org/lkml/2006/10/30/251
> >              http://lkml.org/lkml/2006/11/3/244
> > Submitter  : Martin Lorenz <martin@lorenz.eu.org>
> >              "Michael S. Tsirkin" <mst@mellanox.co.il>
> > Status     : problem is being debugged
> 
> Add to that
> http://lkml.org/lkml/2006/11/1/84
> and a patch in
> http://lkml.org/lkml/2006/11/1/294
> 
> I have been running f9dadfa71bc594df09044da61d1c72701121d802 which hs this patch
> for several days now and this issue seem to be fixed.
> 
> I plan to re-test on -rc5 when that's out.

Thanks for this information, unless you'll tell the opposite I'll assume 
your problems are fixed.

Martin, are your problems also fixed in the latest -git?

> MST

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

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Christian]

Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
> On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
>  > Could this be a problem?
>  > --------------------
>  > ...
>  > CONFIG_ACPI_PROCESSOR=m
>  > ...
>  > CONFIG_X86_POWERNOW_K8=y
>
> Hmm, possibly.  Christian, does it work again if you set them both to =y ?

Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it work 
again!

Nice catch ;-)

Thank you very much!
-Christian

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Dave Jones]

On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
 > Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
 > > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
 > >  > Could this be a problem?
 > >  > --------------------
 > >  > ...
 > >  > CONFIG_ACPI_PROCESSOR=m
 > >  > ...
 > >  > CONFIG_X86_POWERNOW_K8=y
 > >
 > > Hmm, possibly.  Christian, does it work again if you set them both to =y ?
 > 
 > Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it work 
 > again!

So, the reasoning behind this, is that we have this construct..

config X86_POWERNOW_K8_ACPI
    bool
    depends on X86_POWERNOW_K8 && ACPI_PROCESSOR
    depends on !(X86_POWERNOW_K8 = y && ACPI_PROCESSOR = m)
    default y


Which makes us use the ACPI stuff if it's there, otherwise not,
and in your case, it seems your system _needs_ this enabled
to make powernow work.

Thing is, this was there in 2.6.18 too, so strictly speaking,
we haven't regressed here, and you're getting exactly what you asked for.
The problem is that it's completely silent as to why it then fails.

I'm open to improvements, but I'm not sure what the right thing to do
here is.. opinions ?

	Dave

-- 
http://www.codemonkey.org.uk

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Adrian Bunk]

On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
> Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
> > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
> >  > Could this be a problem?
> >  > --------------------
> >  > ...
> >  > CONFIG_ACPI_PROCESSOR=m
> >  > ...
> >  > CONFIG_X86_POWERNOW_K8=y
> >
> > Hmm, possibly.  Christian, does it work again if you set them both to =y ?
> 
> Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it work 
> again!

You said 2.6.18 worked for you.

Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?

> Nice catch ;-)
> 
> Thank you very much!
> -Christian

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

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Christian]

Am Montag, 6. November 2006 07:00 schrieb Adrian Bunk:
> On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
> > Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
> > > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
> > >  > Could this be a problem?
> > >  > --------------------
> > >  > ...
> > >  > CONFIG_ACPI_PROCESSOR=m
> > >  > ...
> > >  > CONFIG_X86_POWERNOW_K8=y
> > >
> > > Hmm, possibly.  Christian, does it work again if you set them both to
> > > =y ?
> >
> > Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it
> > work again!
>
> You said 2.6.18 worked for you.
>
> Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
> CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?

It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it 
doesn't work anymore with CONFIG_ACPI_PROCESSOR=m.

user@ubuntu:~/Projekte/linux-2.6.18-rc7$ uname -a
Linux ubuntu.localnet 2.6.18-rc7 #2 SMP Wed Sep 13 11:28:41 CEST 2006 x86_64 
GNU/Linux

user@ubuntu:~/Projekte/linux-2.6.18-rc7$ lsmod | grep -Ei "processor|acpi|
power"
powernow_k8            16096  1
freq_table              6848  2 powernow_k8,cpufreq_stats
cpufreq_powersave       3584  0
asus_acpi              20644  0
processor              36872  2 powernow_k8,thermal


user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -i 
ACPI_PROCESSOR /boot/config-2.6.18-rc7
CONFIG_ACPI_PROCESSOR=m

user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y

+++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++

user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
grep -Ei "POWERNOW_K8" /boot/config-2.6.19-rc1
CONFIG_X86_POWERNOW_K8=y

user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -Ei "CPUFREQ|
CPU_FREQ" /boot/config-2.6.18-rc7
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
# CPUFreq processor drivers
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set

-Christian

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Dave Jones]

On Mon, Nov 06, 2006 at 04:43:13PM +0100, Christian wrote:

 > > Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
 > > CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?
 > 
 > It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it 
 > doesn't work anymore with CONFIG_ACPI_PROCESSOR=m.
 > 
 > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -i ACPI_PROCESSOR /boot/config-2.6.18-rc7
 > CONFIG_ACPI_PROCESSOR=m
 > 
 > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
 > grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7
 > CONFIG_X86_POWERNOW_K8=m
 > CONFIG_X86_POWERNOW_K8_ACPI=y
 > 
 > +++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++

I don't understand how this was allowed. Because when I try this
with a 2.6.18 tree..  (nothing changed between -rc7 and final for cpufreq)

<editted a .config to match your config>

$ grep ACPI_PROCESSOR .config
CONFIG_ACPI_PROCESSOR=m
$ grep POWERNOW_K8 .config
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_POWERNOW_K8_ACPI=y

and then after a make oldconfig the CONFIG_X86_POWERNOW_K8_ACPI is removed
as it isn't valid.

Did you edit your .config by hand ?

	Dave

-- 
http://www.codemonkey.org.uk

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Adrian Bunk]

On Mon, Nov 06, 2006 at 12:20:49PM -0500, Dave Jones wrote:
> On Mon, Nov 06, 2006 at 04:43:13PM +0100, Christian wrote:
> 
>  > > Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
>  > > CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?
>  > 
>  > It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it 
>  > doesn't work anymore with CONFIG_ACPI_PROCESSOR=m.
>  > 
>  > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -i ACPI_PROCESSOR /boot/config-2.6.18-rc7
>  > CONFIG_ACPI_PROCESSOR=m
>  > 
>  > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
>  > grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7
>  > CONFIG_X86_POWERNOW_K8=m
>  > CONFIG_X86_POWERNOW_K8_ACPI=y
>  > 
>  > +++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++
> 
> I don't understand how this was allowed. Because when I try this
> with a 2.6.18 tree..  (nothing changed between -rc7 and final for cpufreq)
> 
> <editted a .config to match your config>
> 
> $ grep ACPI_PROCESSOR .config
> CONFIG_ACPI_PROCESSOR=m
> $ grep POWERNOW_K8 .config
> CONFIG_X86_POWERNOW_K8=y
> CONFIG_X86_POWERNOW_K8_ACPI=y
> 
> and then after a make oldconfig the CONFIG_X86_POWERNOW_K8_ACPI is removed
> as it isn't valid.
> 
> Did you edit your .config by hand ?

Look closer, his linux-2.6.18-rc7 .config contains 
CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=m.

> 	Dave

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

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Adrian Bunk]

On Sun, Nov 05, 2006 at 03:04:48PM -0500, Dave Jones wrote:
> On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
>  > Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
>  > > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
>  > >  > Could this be a problem?
>  > >  > --------------------
>  > >  > ...
>  > >  > CONFIG_ACPI_PROCESSOR=m
>  > >  > ...
>  > >  > CONFIG_X86_POWERNOW_K8=y
>  > >
>  > > Hmm, possibly.  Christian, does it work again if you set them both to =y ?
>  > 
>  > Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it work 
>  > again!
> 
> So, the reasoning behind this, is that we have this construct..
> 
> config X86_POWERNOW_K8_ACPI
>     bool
>     depends on X86_POWERNOW_K8 && ACPI_PROCESSOR
>     depends on !(X86_POWERNOW_K8 = y && ACPI_PROCESSOR = m)
>     default y
> 
> 
> Which makes us use the ACPI stuff if it's there, otherwise not,
> and in your case, it seems your system _needs_ this enabled
> to make powernow work.
> 
> Thing is, this was there in 2.6.18 too, so strictly speaking,
> we haven't regressed here, and you're getting exactly what you asked for.
> The problem is that it's completely silent as to why it then fails.
> 
> I'm open to improvements, but I'm not sure what the right thing to do
> here is.. opinions ?

The extreme solution would be

config X86_POWERNOW_K8
        tristate "AMD Opteron/Athlon64 PowerNow!"
        select CPU_FREQ_TABLE
        depends ACPI_PROCESSOR

A medium solution might be

config X86_POWERNOW_K8
        tristate "AMD Opteron/Athlon64 PowerNow!"
        select CPU_FREQ_TABLE
	depends (ACPI_PROCESSOR || ACPI_PROCESSOR=n)

But in the end, the best solution depends on how many percent of the 
X86_POWERNOW_K8 users have Christian's problem of requiring 
ACPI_PROCESSOR. If there are only very few people with this problem, I'd 
say leave it as it is.

> 	Dave

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

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Adrian Bunk]

On Mon, Nov 06, 2006 at 04:43:13PM +0100, Christian wrote:
> Am Montag, 6. November 2006 07:00 schrieb Adrian Bunk:
> > On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
> > > Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
> > > > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
> > > >  > Could this be a problem?
> > > >  > --------------------
> > > >  > ...
> > > >  > CONFIG_ACPI_PROCESSOR=m
> > > >  > ...
> > > >  > CONFIG_X86_POWERNOW_K8=y
> > > >
> > > > Hmm, possibly.  Christian, does it work again if you set them both to
> > > > =y ?
> > >
> > > Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it
> > > work again!
> >
> > You said 2.6.18 worked for you.
> >
> > Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
> > CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?
> 
> It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it 
> doesn't work anymore with CONFIG_ACPI_PROCESSOR=m.
> 
> user@ubuntu:~/Projekte/linux-2.6.18-rc7$ uname -a
> Linux ubuntu.localnet 2.6.18-rc7 #2 SMP Wed Sep 13 11:28:41 CEST 2006 x86_64 
> GNU/Linux
> 
> user@ubuntu:~/Projekte/linux-2.6.18-rc7$ lsmod | grep -Ei "processor|acpi|
> power"
> powernow_k8            16096  1
> freq_table              6848  2 powernow_k8,cpufreq_stats
> cpufreq_powersave       3584  0
> asus_acpi              20644  0
> processor              36872  2 powernow_k8,thermal
> 
> 
> user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -i 
> ACPI_PROCESSOR /boot/config-2.6.18-rc7
> CONFIG_ACPI_PROCESSOR=m
> 
> user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
> grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7
> CONFIG_X86_POWERNOW_K8=m
> CONFIG_X86_POWERNOW_K8_ACPI=y
> 
> +++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++
> 
> user@ubuntu:~/Projekte/linux-2.6.18-rc7$ 
> grep -Ei "POWERNOW_K8" /boot/config-2.6.19-rc1
> CONFIG_X86_POWERNOW_K8=y
>....

It's gone because you changed CONFIG_X86_POWERNOW_K8 from m to y.

> -Christian

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

Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)

[Andi Kleen]

On Sunday 05 November 2006 10:30, Jeff Chua wrote:

> Here's results with vanilla 2.6.19-rc4 (gcc version 3.4.5) ...
> 
> 1) PCI access mode (Any) ... FAILED
> 
> 2) PCI access mode (MMConfig) ... FAILED

Full boot log please?

-Andi

Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

[Dave Jones]

On Mon, Nov 06, 2006 at 06:35:28PM +0100, Adrian Bunk wrote:
 
 > config X86_POWERNOW_K8
 >         tristate "AMD Opteron/Athlon64 PowerNow!"
 >         select CPU_FREQ_TABLE
 > 	depends (ACPI_PROCESSOR || ACPI_PROCESSOR=n)
 > 
 > But in the end, the best solution depends on how many percent of the 
 > X86_POWERNOW_K8 users have Christian's problem of requiring 
 > ACPI_PROCESSOR. If there are only very few people with this problem, I'd 
 > say leave it as it is.

Well, it's been this way for a while, and only recently this has come up.
There was a similar report for powernow-k7, which has a similar construct.

	Dave

-- 
http://www.codemonkey.org.uk

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Ernst Herzberg]

On Sunday 05 November 2006 07:48, Adrian Bunk wrote:
> ...
> Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
> References : http://lkml.org/lkml/2006/10/31/333
> Submitter  : Ernst Herzberg <earny@net4u.de>
> Status     : problem is being debugged

Update:

2.6.19-rc4-git11 does _not_ fix the problem.

But now it doesn't matter if Cardbus/PCMCIA is compiled in or not.

What also matters is a setting in the BIOS:

If i set instead of

Power -> 
   SpeedStep ->
      Mode for AC -    "Max Performance"
      Mode for Battery "Max Battery"

to

Power -> 
   SpeedStep ->
      Mode for AC -    "Max Battery"
      Mode for Battery "Max Performance" 

he _does_ boot from battery but also on AC...

Also the problem is now(?) not very reliable. Sometimes the boot is successful 
even on battery and then the laptop works without a glitch.
This makes it not easier to isolate the problem.

About the reverts of some patches: I'm not, lets say it carefull, an very   
experienced git user;-) 
What i get is:

# git-revert -n cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
First trying simple merge strategy to revert.
Simple revert fails; trying Automatic revert.
Auto-merging arch/i386/kernel/io_apic.c
merge: warning: conflicts during merge
ERROR: Merge conflict in arch/i386/kernel/io_apic.c
....


Is somewhere a howto-revert-patches-in-kernel-git-for-raw-beginners?

<earny>

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Len Brown]

On Monday 06 November 2006 21:17, Ernst Herzberg wrote:
> On Sunday 05 November 2006 07:48, Adrian Bunk wrote:
> > ...
> > Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
> > References : http://lkml.org/lkml/2006/10/31/333
> > Submitter  : Ernst Herzberg <earny@net4u.de>
> > Status     : problem is being debugged
> 
> Update:
> 
> 2.6.19-rc4-git11 does _not_ fix the problem.
> 
> But now it doesn't matter if Cardbus/PCMCIA is compiled in or not.
> 
> What also matters is a setting in the BIOS:
> 
> If i set instead of
> 
> Power -> 
>    SpeedStep ->
>       Mode for AC -    "Max Performance"
>       Mode for Battery "Max Battery"
> 
> to
> 
> Power -> 
>    SpeedStep ->
>       Mode for AC -    "Max Battery"
>       Mode for Battery "Max Performance" 
> 
> he _does_ boot from battery but also on AC...

so with the new settings it boots properly in either AC or battery mode with forced "lapic"?
Strange, one would expect this to refer to APM settings, but who knows...

Please test if booting with "processor.max_cstate=1" makes any difference

Please test if building with CONFIG_CPU_FREQ=n makes any difference.

Also, please make sure that booting with "apm=off" makes no difference --
there is a bug where the APM code is not currently disabled in ACPI mode,
and who knows what effect that may have...

> Also the problem is now(?) not very reliable. Sometimes the boot is successful 
> even on battery and then the laptop works without a glitch.
> This makes it not easier to isolate the problem.
> 

> Is somewhere a howto-revert-patches-in-kernel-git-for-raw-beginners?

Documentation/git-bisect.txt is what you want -- though if you can't
reliably reproduce the failure it may not easily lead you to the failure.

Also, it may be a good use of time to make darn sure that booting 2.6.18
with forced "lapic" when on battery does not fail.  ie. is this really
a regression -- of did forcing the lapic on this box never work reliably?

-Len

2.6.19-rc4: known unfixed regressions (v4)

[Adrian Bunk]

This email lists some known regressions in 2.6.19-rc compared to 2.6.18
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way possibly
involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
References : http://lkml.org/lkml/2006/10/31/333
Submitter  : Ernst Herzberg <earny@net4u.de>
Handled-By : Len Brown <len.brown@intel.com>
Status     : problem is being debugged


Subject    : ThinkPad T60: no screen after resume
References : http://mail.matrix.de/pipermail/linux-thinkpad/2006-November/037011.html
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
Status     : unknown


Subject    : ThinkPad T60: lose ACPI events after suspend/resume
References : http://lkml.org/lkml/2006/10/10/39
             http://bugzilla.kernel.org/show_bug.cgi?id=7408
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
Status     : problem might be fixed by
             commit f9dadfa71bc594df09044da61d1c72701121d802


Subject    : i386: more DWARFs and strange messages
References : http://lkml.org/lkml/2006/10/29/127
Submitter  : Martin Lorenz <martin@lorenz.eu.org>
Status     : should be fixed by
             commit 4b96b1a10cb00c867103b21f0f2a6c91b705db11


Subject    : BUG: scheduling while atomic: events/0/0x00000001/4, etc..
References : http://lkml.org/lkml/2006/11/2/209
Submitter  : Paolo Ornati <ornati@fastwebnet.it>
Status     : unknown


Subject    : sata-via doesn't detect anymore disks attached to VIA vt6421
References : http://bugzilla.kernel.org/show_bug.cgi?id=7255
Submitter  : Thierry Vignaud <tvignaud@mandriva.com>
Status     : unknown


Subject    : unable to rip cd
References : http://lkml.org/lkml/2006/10/13/100
Submitter  : Alex Romosan <romosan@sycorax.lbl.gov>
Status     : unknown


Subject    : x86_64: oprofile doesn't work
References : http://lkml.org/lkml/2006/10/27/3
Submitter  : Prakash Punnoor <prakash@punnoor.de>
Status     : unknown


Subject    : x86_64: NR_IRQ increase causes 11.5% slowdown
                     in lmbench's fork benchmark
References : http://lkml.org/lkml/2006/11/2/192
Submitter  : Tim Chen <tim.c.chen@linux.intel.com>
Caused-By  : Eric W. Biederman <ebiederm@xmission.com>
             commit 550f2299ac8ffaba943cf211380d3a8d3fa75301
Status     : unknown


Subject    : PCI: MMCONFIG breakage
References : http://lkml.org/lkml/2006/10/27/251
Submitter  : Jeff Chua <jeff.chua.linux@gmail.com>
Handled-By : Andi Kleen <ak@suse.de>
Status     : Andi is investigating, both BIOS and Direct work


Subject    : SMP kernel can not generate ISA irq properly
References : http://lkml.org/lkml/2006/10/22/15
Submitter  : Komuro <komurojun-mbn@nifty.com>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : Thomas is investigating


Subject    : ipath driver MCEs system on load when HT chip present
References : http://bugzilla.kernel.org/show_bug.cgi?id=7455
Submitter  : Bryan O'Sullivan <bos@serpentine.com>
Caused-By  : Eric W. Biederman <ebiederm@xmission.com>
Handled-By : Bryan O'Sullivan <bos@serpentine.com>
             Eric W. Biederman <ebiederm@xmission.com>
Status     : Bryan and Eric are working on fixing the ipath driver


Subject    : boot hang in the microcode driver
References : http://lkml.org/lkml/2006/11/6/117
Submitter  : Arjan van de Ven <arjan@linux.intel.com>
Caused-By  : Shaohua Li <shaohua.li@intel.com>
             commit a30a6a2cb0fdc2c9701d6ddfb21affeb8146c038
Handled-By : Arjan van de Ven <arjan@linux.intel.com>
Patch      : http://lkml.org/lkml/2006/11/6/117
Status     : workaround-patch available

Re: 2.6.19-rc4: known unfixed regressions (v3)

[Ernst Herzberg]

On Tuesday 07 November 2006 06:41, Len Brown wrote:
> On Monday 06 November 2006 21:17, Ernst Herzberg wrote:
> > On Sunday 05 November 2006 07:48, Adrian Bunk wrote:
> > > ...
> > > Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
> > > References : http://lkml.org/lkml/2006/10/31/333
> > > Submitter  : Ernst Herzberg <earny@net4u.de>
> > > Status     : problem is being debugged

First i made shure again that 2.6.18.2 works..... damn shure.

>
> Please test if booting with "processor.max_cstate=1" makes any
> difference

--> NO.

> Please test if building with CONFIG_CPU_FREQ=n makes any difference.

--> NO.

> Also, please make sure that booting with "apm=off" makes no difference
> -- there is a bug where the APM code is not currently disabled in ACPI
> mode, and who knows what effect that may have...

Ahem. All previous tests was done with CONFIG_APM=n. So i tested with 
CONFIG_APM=y. Does not help. It makes no difference booting with "apm=off" 
or not.

Another check:

The laptop muste be powered on on_battery to trigger the problem. If i 
disconnect AC at the grub-prompt the problem does _not_ occur.

The laptop has two batteries. The utraybay battery is nearly dead now, but 
it makes no difference if removed.

This problem is not very important for me, i just wondering why is only 
occurs if running on battery. I would be happy, if someone can explain 
this;-) 

The laptop itself is rock stable (if he boots), never seen any glitch or 
instability (with lapic). I don't know exactly when i started using lapic. 
Its a long time ago (last year?), i have read the message that i can 
enable this so i did. No problems until 2.6.19-rc1....

If nobody can reproduce this, i don't care about the problem. There is also 
a life without lapic:) But maybe it shows a problem anywhere else, timing 
or whatever, so i'm willing to test everything against.

So if someone is interesting to reproduce the problem, i repeat the 
conditions that must be met:

1.: Laptop must be powered on with AC removed (on battery)

2.: BIOS-Setting must be
  power --> Intel Speedstep --> Mode on Battery --> "Max Battery"

3.: Kernel command line must have "lapci"

4.: Kernel must be >= 2.6.19-rc1

dmidecode: (maybe that helps?)

# dmidecode 2.8
SMBIOS 2.33 present.
61 structures occupying 2127 bytes.
Table at 0x000E0010.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
	Vendor: IBM
	Version: 1RETDPWW (3.21 )
	Release Date: 06/02/2006
	Address: 0xDC000
	Runtime Size: 144 kB
	ROM Size: 1024 kB
	Characteristics:
		PCI is supported
		PC Card (PCMCIA) is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		3.5"/720 KB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		AGP is supported
		BIOS boot specification is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer: IBM
	Product Name: 183222G
	Version: ThinkPad R50p
	Serial Number: 99DR993
	UUID: 5532DC80-466C-11CB-B373-95CD80E5548B
	Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: IBM
	Product Name: 183222G
	Version: Not Available
	Serial Number: J1V9545B13X

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: IBM
	Type: Notebook
	Lock: Not Present
	Version: Not Available
	Serial Number: Not Available
	Asset Tag: No Asset Information
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown
	OEM Information: 0x00000000

Handle 0x0004, DMI type 126, 17 bytes
Inactive

Handle 0x0005, DMI type 126, 17 bytes
Inactive

Handle 0x0006, DMI type 4, 35 bytes
Processor Information
	Socket Designation: None
	Type: Central Processor
	Family: Pentium M
	Manufacturer: GenuineIntel
	ID: 95 06 00 00 BF F9 E9 A7
	Signature: Type 0, Family 6, Model 9, Stepping 5
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (Fast floating-point save and restore)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Pentium(R) M processor
	Voltage: 1.5 V
	External Clock: 400 MHz
	Max Speed: 1700 MHz
	Current Speed: 1700 MHz
	Status: Populated, Enabled
	Upgrade: None
	L1 Cache Handle: 0x000A
	L2 Cache Handle: 0x000B
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0007, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: None
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 1024 MB
	Maximum Total Memory Size: 2048 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		DIMM
		SDRAM
	Memory Module Voltage: 2.9 V
	Associated Memory Slots: 2
		0x0008
		0x0009
	Enabled Error Correcting Capabilities:
		None

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 1
	Bank Connections: 0 1
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 512 MB (Double-bank Connection)
	Enabled Size: 512 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 2
	Bank Connections: 2 3
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 512 MB (Double-bank Connection)
	Enabled Size: 512 MB (Double-bank Connection)
	Error Status: OK

Handle 0x000A, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L1 Cache
	Configuration: Enabled, Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 KB
	Maximum Size: 32 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Other
	Associativity: 8-way Set-associative

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L2 Cache
	Configuration: Enabled, Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 1024 KB
	Maximum Size: 1024 KB
	Supported SRAM Types:
		Burst
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

Handle 0x000C, DMI type 126, 9 bytes
Inactive

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Infrared
	External Connector Type: Infrared
	Port Type: Other

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Parallel
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: External Monitor
	External Connector Type: DB-15 female
	Port Type: Video Port

Handle 0x0010, DMI type 126, 9 bytes
Inactive

Handle 0x0011, DMI type 126, 9 bytes
Inactive

Handle 0x0012, DMI type 126, 9 bytes
Inactive

Handle 0x0013, DMI type 126, 9 bytes
Inactive

Handle 0x0014, DMI type 126, 9 bytes
Inactive

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Microphone Jack
	External Connector Type: Mini Jack (headphones)
	Port Type: Audio Port

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Headphone Jack
	External Connector Type: Mini Jack (headphones)
	Port Type: Audio Port

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: S-Video-Out
	External Connector Type: Other
	Port Type: Video Port

Handle 0x0018, DMI type 126, 9 bytes
Inactive

Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Modem
	External Connector Type: RJ-11
	Port Type: Modem Port

Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Ethernet
	External Connector Type: RJ-45
	Port Type: Network Port

Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 1
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x001C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 2
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x001D, DMI type 126, 9 bytes
Inactive

Handle 0x001E, DMI type 126, 9 bytes
Inactive

Handle 0x001F, DMI type 126, 9 bytes
Inactive

Handle 0x0020, DMI type 126, 9 bytes
Inactive

Handle 0x0021, DMI type 126, 9 bytes
Inactive

Handle 0x0022, DMI type 9, 13 bytes
System Slot Information
	Designation: CardBus Slot 1
	Type: 32-bit PC Card (PCMCIA)
	Current Usage: Available
	Length: Other
	ID: Adapter 0, Socket 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided
		PC Card-16 is supported
		Cardbus is supported
		Zoom Video is supported
		Modem ring resume is supported
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0023, DMI type 9, 13 bytes
System Slot Information
	Designation: CardBus Slot 2
	Type: 32-bit PC Card (PCMCIA)
	Current Usage: Available
	Length: Other
	ID: Adapter 1, Socket 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided
		PC Card-16 is supported
		Cardbus is supported
		Zoom Video is supported
		Modem ring resume is supported
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0024, DMI type 126, 13 bytes
Inactive

Handle 0x0025, DMI type 126, 13 bytes
Inactive

Handle 0x0026, DMI type 9, 13 bytes
System Slot Information
	Designation: Mini-PCI Slot 1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Other
	ID: 1
	Characteristics:
		5.0 V is provided
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x0027, DMI type 126, 13 bytes
Inactive

Handle 0x0028, DMI type 10, 6 bytes
On Board Device Information
	Type: Other
	Status: Enabled
	Description: IBM Embedded Security hardware

Handle 0x0029, DMI type 11, 5 bytes
OEM Strings
	String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04    ]-

Handle 0x002A, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 1
		enUS
	Currently Installed Language: enUS

Handle 0x002B, DMI type 15, 25 bytes
System Event Log
	Area Length: 0 bytes
	Header Start Offset: 0x0000
	Header Length: 16 bytes
	Data Start Offset: 0x0010
	Access Method: General-purpose non-volatile data functions
	Access Address: 0x0000
	Status: Invalid, Not Full
	Change Token: 0x00000004
	Header Format: Type 1
	Supported Log Type Descriptors: 1
	Descriptor 1: POST error
	Data Format 1: POST results bitmap

Handle 0x002C, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 1 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x002D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002C
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 1
	Bank Locator: Bank 0/1
	Type: DDR
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x002E, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002C
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 2
	Bank Locator: Bank 2/3
	Type: DDR
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x002F, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: OK
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x0030, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Array Handle: 0x002C
	Partition Width: 0

Handle 0x0031, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x002D
	Memory Array Mapped Address Handle: 0x0030
	Partition Row Position: 1

Handle 0x0032, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00020000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x002E
	Memory Array Mapped Address Handle: 0x0030
	Partition Row Position: 1

Handle 0x0033, DMI type 21, 7 bytes
Built-in Pointing Device
	Type: Track Point
	Interface: PS/2
	Buttons: 3

Handle 0x0034, DMI type 21, 7 bytes
Built-in Pointing Device
	Type: Touch Pad
	Interface: PS/2
	Buttons: 0

Handle 0x0035, DMI type 24, 5 bytes
Hardware Security
	Power-On Password Status: Disabled
	Keyboard Password Status: Disabled
	Administrator Password Status: Disabled
	Front Panel Reset Status: Unknown

Handle 0x0036, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0037, DMI type 131, 102 bytes
OEM-specific Type
	Header and Data:
		83 66 37 00 01 00 00 00 00 01 72 03 40 00 AE 80
		00 02 00 00 00 00 00 2A 00 40 2A 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 16 00 80 16 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00
	Strings:
		IBMCFGDATA

Handle 0x0038, DMI type 131, 17 bytes
OEM-specific Type
	Header and Data:
		83 11 38 00 01 02 03 FF FF 1F 00 00 00 00 00 02
		00
	Strings:
		BOOTINF 20h
		BOOTDEV 21h
		KEYPTRS 23h

Handle 0x0039, DMI type 132, 7 bytes
OEM-specific Type
	Header and Data:
		84 07 39 00 01 D8 36

Handle 0x003A, DMI type 133, 5 bytes
OEM-specific Type
	Header and Data:
		85 05 3A 00 01
	Strings:
		KHOIHGIUCCHHII

Handle 0x003B, DMI type 126, 13 bytes
Inactive

Handle 0x003C, DMI type 127, 4 bytes
End Of Table

------

Thx,

<earny>

Re: [linux-pm] 2.6.19-rc4: known unfixed regressions (v3)

[Adrian Bunk]

On Tue, Nov 07, 2006 at 09:05:36PM +0100, Ernst Herzberg wrote:
> On Tuesday 07 November 2006 06:41, Len Brown wrote:
> > On Monday 06 November 2006 21:17, Ernst Herzberg wrote:
> > > On Sunday 05 November 2006 07:48, Adrian Bunk wrote:
> > > > ...
> > > > Subject    : ThinkPad R50p: boot fail with (lapic && on_battery)
> > > > References : http://lkml.org/lkml/2006/10/31/333
> > > > Submitter  : Ernst Herzberg <earny@net4u.de>
> > > > Status     : problem is being debugged
> 
> First i made shure again that 2.6.18.2 works..... damn shure.
> 
> >
> > Please test if booting with "processor.max_cstate=1" makes any
> > difference
> 
> --> NO.
> 
> > Please test if building with CONFIG_CPU_FREQ=n makes any difference.
> 
> --> NO.
> 
> > Also, please make sure that booting with "apm=off" makes no difference
> > -- there is a bug where the APM code is not currently disabled in ACPI
> > mode, and who knows what effect that may have...
> 
> Ahem. All previous tests was done with CONFIG_APM=n. So i tested with 
> CONFIG_APM=y. Does not help. It makes no difference booting with "apm=off" 
> or not.
> 
> Another check:
> 
> The laptop muste be powered on on_battery to trigger the problem. If i 
> disconnect AC at the grub-prompt the problem does _not_ occur.
> 
> The laptop has two batteries. The utraybay battery is nearly dead now, but 
> it makes no difference if removed.
> 
> This problem is not very important for me, i just wondering why is only 
> occurs if running on battery. I would be happy, if someone can explain 
> this;-) 
> 
> The laptop itself is rock stable (if he boots), never seen any glitch or 
> instability (with lapic). I don't know exactly when i started using lapic. 
> Its a long time ago (last year?), i have read the message that i can 
> enable this so i did. No problems until 2.6.19-rc1....
> 
> If nobody can reproduce this, i don't care about the problem. There is also 
> a life without lapic:) But maybe it shows a problem anywhere else, timing 
> or whatever, so i'm willing to test everything against.


There's exactly the important point:
It's interesting to work out (e.g. by a successfull bisecting) _what_ 
broke it.

"OK, we understand what's going on, and it's a surprise that lapic ever 
worked for you." is a possible result.

But it's also possible that it's only one symptom of some serious 
problem - a buggy part of Andi's APIC cleanups has just been fixed, and 
Martin seems to run from one problem into the next on his ThinkPad, 
so getting your problem debugged might also help other people.


> So if someone is interesting to reproduce the problem, i repeat the 
> conditions that must be met:
> 
> 1.: Laptop must be powered on with AC removed (on battery)
> 
> 2.: BIOS-Setting must be
>   power --> Intel Speedstep --> Mode on Battery --> "Max Battery"
> 
> 3.: Kernel command line must have "lapci"
> 
> 4.: Kernel must be >= 2.6.19-rc1
> 
> dmidecode: (maybe that helps?)
> 
> # dmidecode 2.8
> SMBIOS 2.33 present.
> 61 structures occupying 2127 bytes.
> Table at 0x000E0010.
> 
> Handle 0x0000, DMI type 0, 20 bytes
> BIOS Information
> 	Vendor: IBM
> 	Version: 1RETDPWW (3.21 )
> 	Release Date: 06/02/2006
> 	Address: 0xDC000
> 	Runtime Size: 144 kB
> 	ROM Size: 1024 kB
> 	Characteristics:
> 		PCI is supported
> 		PC Card (PCMCIA) is supported
> 		PNP is supported
> 		APM is supported
> 		BIOS is upgradeable
> 		BIOS shadowing is allowed
> 		ESCD support is available
> 		Boot from CD is supported
> 		Selectable boot is supported
> 		EDD is supported
> 		3.5"/720 KB floppy services are supported (int 13h)
> 		Print screen service is supported (int 5h)
> 		8042 keyboard services are supported (int 9h)
> 		Serial services are supported (int 14h)
> 		Printer services are supported (int 17h)
> 		CGA/mono video services are supported (int 10h)
> 		ACPI is supported
> 		USB legacy is supported
> 		AGP is supported
> 		BIOS boot specification is supported
> 
> Handle 0x0001, DMI type 1, 25 bytes
> System Information
> 	Manufacturer: IBM
> 	Product Name: 183222G
> 	Version: ThinkPad R50p
> 	Serial Number: 99DR993
> 	UUID: 5532DC80-466C-11CB-B373-95CD80E5548B
> 	Wake-up Type: Power Switch
> 
> Handle 0x0002, DMI type 2, 8 bytes
> Base Board Information
> 	Manufacturer: IBM
> 	Product Name: 183222G
> 	Version: Not Available
> 	Serial Number: J1V9545B13X
> 
> Handle 0x0003, DMI type 3, 17 bytes
> Chassis Information
> 	Manufacturer: IBM
> 	Type: Notebook
> 	Lock: Not Present
> 	Version: Not Available
> 	Serial Number: Not Available
> 	Asset Tag: No Asset Information
> 	Boot-up State: Unknown
> 	Power Supply State: Unknown
> 	Thermal State: Unknown
> 	Security Status: Unknown
> 	OEM Information: 0x00000000
> 
> Handle 0x0004, DMI type 126, 17 bytes
> Inactive
> 
> Handle 0x0005, DMI type 126, 17 bytes
> Inactive
> 
> Handle 0x0006, DMI type 4, 35 bytes
> Processor Information
> 	Socket Designation: None
> 	Type: Central Processor
> 	Family: Pentium M
> 	Manufacturer: GenuineIntel
> 	ID: 95 06 00 00 BF F9 E9 A7
> 	Signature: Type 0, Family 6, Model 9, Stepping 5
> 	Flags:
> 		FPU (Floating-point unit on-chip)
> 		VME (Virtual mode extension)
> 		DE (Debugging extension)
> 		PSE (Page size extension)
> 		TSC (Time stamp counter)
> 		MSR (Model specific registers)
> 		MCE (Machine check exception)
> 		CX8 (CMPXCHG8 instruction supported)
> 		SEP (Fast system call)
> 		MTRR (Memory type range registers)
> 		PGE (Page global enable)
> 		MCA (Machine check architecture)
> 		CMOV (Conditional move instruction supported)
> 		PAT (Page attribute table)
> 		CLFSH (CLFLUSH instruction supported)
> 		DS (Debug store)
> 		ACPI (ACPI supported)
> 		MMX (MMX technology supported)
> 		FXSR (Fast floating-point save and restore)
> 		SSE (Streaming SIMD extensions)
> 		SSE2 (Streaming SIMD extensions 2)
> 		TM (Thermal monitor supported)
> 		PBE (Pending break enabled)
> 	Version: Intel(R) Pentium(R) M processor
> 	Voltage: 1.5 V
> 	External Clock: 400 MHz
> 	Max Speed: 1700 MHz
> 	Current Speed: 1700 MHz
> 	Status: Populated, Enabled
> 	Upgrade: None
> 	L1 Cache Handle: 0x000A
> 	L2 Cache Handle: 0x000B
> 	L3 Cache Handle: Not Provided
> 	Serial Number: Not Specified
> 	Asset Tag: Not Specified
> 	Part Number: Not Specified
> 
> Handle 0x0007, DMI type 5, 20 bytes
> Memory Controller Information
> 	Error Detecting Method: None
> 	Error Correcting Capabilities:
> 		None
> 	Supported Interleave: One-way Interleave
> 	Current Interleave: One-way Interleave
> 	Maximum Memory Module Size: 1024 MB
> 	Maximum Total Memory Size: 2048 MB
> 	Supported Speeds:
> 		Other
> 	Supported Memory Types:
> 		DIMM
> 		SDRAM
> 	Memory Module Voltage: 2.9 V
> 	Associated Memory Slots: 2
> 		0x0008
> 		0x0009
> 	Enabled Error Correcting Capabilities:
> 		None
> 
> Handle 0x0008, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM Slot 1
> 	Bank Connections: 0 1
> 	Current Speed: Unknown
> 	Type: DIMM SDRAM
> 	Installed Size: 512 MB (Double-bank Connection)
> 	Enabled Size: 512 MB (Double-bank Connection)
> 	Error Status: OK
> 
> Handle 0x0009, DMI type 6, 12 bytes
> Memory Module Information
> 	Socket Designation: DIMM Slot 2
> 	Bank Connections: 2 3
> 	Current Speed: Unknown
> 	Type: DIMM SDRAM
> 	Installed Size: 512 MB (Double-bank Connection)
> 	Enabled Size: 512 MB (Double-bank Connection)
> 	Error Status: OK
> 
> Handle 0x000A, DMI type 7, 19 bytes
> Cache Information
> 	Socket Designation: Internal L1 Cache
> 	Configuration: Enabled, Socketed, Level 1
> 	Operational Mode: Write Back
> 	Location: Internal
> 	Installed Size: 32 KB
> 	Maximum Size: 32 KB
> 	Supported SRAM Types:
> 		Synchronous
> 	Installed SRAM Type: Synchronous
> 	Speed: Unknown
> 	Error Correction Type: Unknown
> 	System Type: Other
> 	Associativity: 8-way Set-associative
> 
> Handle 0x000B, DMI type 7, 19 bytes
> Cache Information
> 	Socket Designation: Internal L2 Cache
> 	Configuration: Enabled, Socketed, Level 2
> 	Operational Mode: Write Back
> 	Location: Internal
> 	Installed Size: 1024 KB
> 	Maximum Size: 1024 KB
> 	Supported SRAM Types:
> 		Burst
> 	Installed SRAM Type: Burst
> 	Speed: Unknown
> 	Error Correction Type: Multi-bit ECC
> 	System Type: Unified
> 	Associativity: 8-way Set-associative
> 
> Handle 0x000C, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x000D, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Infrared
> 	External Connector Type: Infrared
> 	Port Type: Other
> 
> Handle 0x000E, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Parallel
> 	External Connector Type: DB-25 female
> 	Port Type: Parallel Port ECP/EPP
> 
> Handle 0x000F, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: External Monitor
> 	External Connector Type: DB-15 female
> 	Port Type: Video Port
> 
> Handle 0x0010, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0011, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0012, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0013, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0014, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0015, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Microphone Jack
> 	External Connector Type: Mini Jack (headphones)
> 	Port Type: Audio Port
> 
> Handle 0x0016, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Headphone Jack
> 	External Connector Type: Mini Jack (headphones)
> 	Port Type: Audio Port
> 
> Handle 0x0017, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: S-Video-Out
> 	External Connector Type: Other
> 	Port Type: Video Port
> 
> Handle 0x0018, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0019, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Modem
> 	External Connector Type: RJ-11
> 	Port Type: Modem Port
> 
> Handle 0x001A, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: Ethernet
> 	External Connector Type: RJ-45
> 	Port Type: Network Port
> 
> Handle 0x001B, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: USB 1
> 	External Connector Type: Access Bus (USB)
> 	Port Type: USB
> 
> Handle 0x001C, DMI type 8, 9 bytes
> Port Connector Information
> 	Internal Reference Designator: Not Available
> 	Internal Connector Type: None
> 	External Reference Designator: USB 2
> 	External Connector Type: Access Bus (USB)
> 	Port Type: USB
> 
> Handle 0x001D, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x001E, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x001F, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0020, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0021, DMI type 126, 9 bytes
> Inactive
> 
> Handle 0x0022, DMI type 9, 13 bytes
> System Slot Information
> 	Designation: CardBus Slot 1
> 	Type: 32-bit PC Card (PCMCIA)
> 	Current Usage: Available
> 	Length: Other
> 	ID: Adapter 0, Socket 0
> 	Characteristics:
> 		5.0 V is provided
> 		3.3 V is provided
> 		PC Card-16 is supported
> 		Cardbus is supported
> 		Zoom Video is supported
> 		Modem ring resume is supported
> 		PME signal is supported
> 		Hot-plug devices are supported
> 
> Handle 0x0023, DMI type 9, 13 bytes
> System Slot Information
> 	Designation: CardBus Slot 2
> 	Type: 32-bit PC Card (PCMCIA)
> 	Current Usage: Available
> 	Length: Other
> 	ID: Adapter 1, Socket 0
> 	Characteristics:
> 		5.0 V is provided
> 		3.3 V is provided
> 		PC Card-16 is supported
> 		Cardbus is supported
> 		Zoom Video is supported
> 		Modem ring resume is supported
> 		PME signal is supported
> 		Hot-plug devices are supported
> 
> Handle 0x0024, DMI type 126, 13 bytes
> Inactive
> 
> Handle 0x0025, DMI type 126, 13 bytes
> Inactive
> 
> Handle 0x0026, DMI type 9, 13 bytes
> System Slot Information
> 	Designation: Mini-PCI Slot 1
> 	Type: 32-bit PCI
> 	Current Usage: Available
> 	Length: Other
> 	ID: 1
> 	Characteristics:
> 		5.0 V is provided
> 		3.3 V is provided
> 		PME signal is supported
> 		SMBus signal is supported
> 
> Handle 0x0027, DMI type 126, 13 bytes
> Inactive
> 
> Handle 0x0028, DMI type 10, 6 bytes
> On Board Device Information
> 	Type: Other
> 	Status: Enabled
> 	Description: IBM Embedded Security hardware
> 
> Handle 0x0029, DMI type 11, 5 bytes
> OEM Strings
> 	String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04    ]-
> 
> Handle 0x002A, DMI type 13, 22 bytes
> BIOS Language Information
> 	Installable Languages: 1
> 		enUS
> 	Currently Installed Language: enUS
> 
> Handle 0x002B, DMI type 15, 25 bytes
> System Event Log
> 	Area Length: 0 bytes
> 	Header Start Offset: 0x0000
> 	Header Length: 16 bytes
> 	Data Start Offset: 0x0010
> 	Access Method: General-purpose non-volatile data functions
> 	Access Address: 0x0000
> 	Status: Invalid, Not Full
> 	Change Token: 0x00000004
> 	Header Format: Type 1
> 	Supported Log Type Descriptors: 1
> 	Descriptor 1: POST error
> 	Data Format 1: POST results bitmap
> 
> Handle 0x002C, DMI type 16, 15 bytes
> Physical Memory Array
> 	Location: System Board Or Motherboard
> 	Use: System Memory
> 	Error Correction Type: None
> 	Maximum Capacity: 1 GB
> 	Error Information Handle: Not Provided
> 	Number Of Devices: 2
> 
> Handle 0x002D, DMI type 17, 27 bytes
> Memory Device
> 	Array Handle: 0x002C
> 	Error Information Handle: No Error
> 	Total Width: 64 bits
> 	Data Width: 64 bits
> 	Size: 512 MB
> 	Form Factor: SODIMM
> 	Set: None
> 	Locator: DIMM 1
> 	Bank Locator: Bank 0/1
> 	Type: DDR
> 	Type Detail: Synchronous
> 	Speed: Unknown
> 	Manufacturer: Not Specified
> 	Serial Number: Not Specified
> 	Asset Tag: Not Specified
> 	Part Number: Not Specified
> 
> Handle 0x002E, DMI type 17, 27 bytes
> Memory Device
> 	Array Handle: 0x002C
> 	Error Information Handle: No Error
> 	Total Width: 64 bits
> 	Data Width: 64 bits
> 	Size: 512 MB
> 	Form Factor: SODIMM
> 	Set: None
> 	Locator: DIMM 2
> 	Bank Locator: Bank 2/3
> 	Type: DDR
> 	Type Detail: Synchronous
> 	Speed: Unknown
> 	Manufacturer: Not Specified
> 	Serial Number: Not Specified
> 	Asset Tag: Not Specified
> 	Part Number: Not Specified
> 
> Handle 0x002F, DMI type 18, 23 bytes
> 32-bit Memory Error Information
> 	Type: OK
> 	Granularity: Unknown
> 	Operation: Unknown
> 	Vendor Syndrome: Unknown
> 	Memory Array Address: Unknown
> 	Device Address: Unknown
> 	Resolution: Unknown
> 
> Handle 0x0030, DMI type 19, 15 bytes
> Memory Array Mapped Address
> 	Starting Address: 0x00000000000
> 	Ending Address: 0x0003FFFFFFF
> 	Range Size: 1 GB
> 	Physical Array Handle: 0x002C
> 	Partition Width: 0
> 
> Handle 0x0031, DMI type 20, 19 bytes
> Memory Device Mapped Address
> 	Starting Address: 0x00000000000
> 	Ending Address: 0x0001FFFFFFF
> 	Range Size: 512 MB
> 	Physical Device Handle: 0x002D
> 	Memory Array Mapped Address Handle: 0x0030
> 	Partition Row Position: 1
> 
> Handle 0x0032, DMI type 20, 19 bytes
> Memory Device Mapped Address
> 	Starting Address: 0x00020000000
> 	Ending Address: 0x0003FFFFFFF
> 	Range Size: 512 MB
> 	Physical Device Handle: 0x002E
> 	Memory Array Mapped Address Handle: 0x0030
> 	Partition Row Position: 1
> 
> Handle 0x0033, DMI type 21, 7 bytes
> Built-in Pointing Device
> 	Type: Track Point
> 	Interface: PS/2
> 	Buttons: 3
> 
> Handle 0x0034, DMI type 21, 7 bytes
> Built-in Pointing Device
> 	Type: Touch Pad
> 	Interface: PS/2
> 	Buttons: 0
> 
> Handle 0x0035, DMI type 24, 5 bytes
> Hardware Security
> 	Power-On Password Status: Disabled
> 	Keyboard Password Status: Disabled
> 	Administrator Password Status: Disabled
> 	Front Panel Reset Status: Unknown
> 
> Handle 0x0036, DMI type 32, 11 bytes
> System Boot Information
> 	Status: No errors detected
> 
> Handle 0x0037, DMI type 131, 102 bytes
> OEM-specific Type
> 	Header and Data:
> 		83 66 37 00 01 00 00 00 00 01 72 03 40 00 AE 80
> 		00 02 00 00 00 00 00 2A 00 40 2A 00 00 00 00 00
> 		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 		00 00 00 00 00 00 00 00 00 00 16 00 80 16 00 00
> 		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 		00 00 00 00 00 00
> 	Strings:
> 		IBMCFGDATA
> 
> Handle 0x0038, DMI type 131, 17 bytes
> OEM-specific Type
> 	Header and Data:
> 		83 11 38 00 01 02 03 FF FF 1F 00 00 00 00 00 02
> 		00
> 	Strings:
> 		BOOTINF 20h
> 		BOOTDEV 21h
> 		KEYPTRS 23h
> 
> Handle 0x0039, DMI type 132, 7 bytes
> OEM-specific Type
> 	Header and Data:
> 		84 07 39 00 01 D8 36
> 
> Handle 0x003A, DMI type 133, 5 bytes
> OEM-specific Type
> 	Header and Data:
> 		85 05 3A 00 01
> 	Strings:
> 		KHOIHGIUCCHHII
> 
> Handle 0x003B, DMI type 126, 13 bytes
> Inactive
> 
> Handle 0x003C, DMI type 127, 4 bytes
> End Of Table
> 
> ------
> 
> Thx,
> 
> <earny>

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