* 2.6.19-rc4: known unfixed regressions
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
@ 2006-10-31 19:56 ` Adrian Bunk
2006-10-31 20:11 ` Greg KH
2006-10-31 20:12 ` Arjan van de Ven
2006-11-03 2:41 ` Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
` (2 subsequent siblings)
3 siblings, 2 replies; 30+ messages in thread
From: Adrian Bunk @ 2006-10-31 19:56 UTC (permalink / raw)
To: Linus Torvalds, Andrew Morton
Cc: Linux Kernel Mailing List, Jeff Chua, gregkh, linux-pci,
Prakash Punnoor, phil.el, oprofile-list, ak, discuss,
Martin Lorenz, Michael S. Tsirkin, Hugh Dickins, len.brown,
linux-acpi, pavel, linux-pm, Thierry Vignaud, jgarzik, linux-ide,
Alex Romosan, Jens Axboe, Christian, davej, cpufreq, Komuro,
Thomas Gleixner, Randy Dunlap, Arnd Bergmann,
David Brownell <david-b>
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
@ 2006-10-31 20:11 ` Greg KH
2006-10-31 20:12 ` Arjan van de Ven
1 sibling, 0 replies; 30+ messages in thread
From: Greg KH @ 2006-10-31 20:11 UTC (permalink / raw)
To: Adrian Bunk
Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List,
Jeff Chua, linux-pci, Prakash Punnoor, phil.el, oprofile-list, ak,
discuss, Martin Lorenz, Michael S. Tsirkin, Hugh Dickins,
len.brown, linux-acpi, pavel, linux-pm, Thierry Vignaud, jgarzik,
linux-ide, Alex Romosan, Jens Axboe, Christian, davej, cpufreq,
Komuro, Thomas Gleixner, Randy Dunlap, Arn
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
2006-10-31 20:11 ` Greg KH
@ 2006-10-31 20:12 ` Arjan van de Ven
1 sibling, 0 replies; 30+ messages in thread
From: Arjan van de Ven @ 2006-10-31 20:12 UTC (permalink / raw)
To: Adrian Bunk
Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List,
Jeff Chua, gregkh, linux-pci, Prakash Punnoor, phil.el,
oprofile-list, ak, discuss, Martin Lorenz, Michael S. Tsirkin,
Hugh Dickins, len.brown, linux-acpi, pavel, linux-pm,
Thierry Vignaud, jgarzik, linux-ide, Alex Romosan, Jens Axboe,
Christian, davej, cpufreq, Komuro, Thomas Gleixner, Randy Dunlap
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....
^ permalink raw reply [flat|nested] 30+ messages in thread
* Linux 2.6.19-rc4: known unfixed regressions (v2)
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
@ 2006-11-03 2:41 ` Adrian Bunk
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
2006-11-07 13:30 ` 2.6.19-rc4: known unfixed regressions (v4) Adrian Bunk
3 siblings, 0 replies; 30+ messages in thread
From: Adrian Bunk @ 2006-11-03 2:41 UTC (permalink / raw)
Cc: Randy Dunlap, len.brown, Thierry Vignaud, davej, Ernst Herzberg,
cpufreq, Alex Romosan, Linux Kernel Mailing List, linux-ide,
oprofile-list, Jens Axboe, Hugh Dickins, Thomas Gleixner,
linux-usb-devel, discuss, linux-pm, Michael S. Tsirkin, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, ak, linux-acpi, mingo,
Arnd Bergmann, Eric W. Biederman
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* 2.6.19-rc4: known unfixed regressions (v3)
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
2006-11-03 2:41 ` Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
@ 2006-11-05 6:48 ` Adrian Bunk
2006-11-05 9:30 ` Jeff Chua
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 13:30 ` 2.6.19-rc4: known unfixed regressions (v4) Adrian Bunk
3 siblings, 2 replies; 30+ messages in thread
From: Adrian Bunk @ 2006-11-05 6:48 UTC (permalink / raw)
To: Linus Torvalds, Andrew Morton
Cc: len.brown, Komuro, linux-pm, Ernst Herzberg, Christian,
Alex Romosan, openib-general, ak, linux-ide, oprofile-list,
Jens Axboe, linux-pci, Elimar Riesebieter, discuss,
Thierry Vignaud, Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Linux Kernel Mailing List, linux-acpi, mingo, nfs,
Eric W. Biederman, cpufreq, Michael S. Tsirkin, Bryan
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
@ 2006-11-05 9:30 ` Jeff Chua
2006-11-06 17:47 ` [discuss] " Andi Kleen
2006-11-07 2:17 ` Ernst Herzberg
1 sibling, 1 reply; 30+ messages in thread
From: Jeff Chua @ 2006-11-05 9:30 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general, ak, linux-ide,
Linus Torvalds, oprofile-list, Jens Axboe, linux-pci,
Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen, phil.el,
gregkh, neilb, Linux Kernel Mailing List, linux-acpi, mingo, nfs,
Eric W. Biederman, cpufreq, Michael S. Tsirkin
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.
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-05 9:30 ` Jeff Chua
@ 2006-11-06 17:47 ` Andi Kleen
0 siblings, 0 replies; 30+ messages in thread
From: Andi Kleen @ 2006-11-06 17:47 UTC (permalink / raw)
To: discuss
Cc: Andrew Morton, len.brown, Thierry Vignaud, Ernst Herzberg,
Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, linux-pci, Elimar Riesebieter,
linux-pm, Komuro, Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Adrian Bunk, linux-acpi, mingo, nfs, Eric W. Biederman, cpufreq
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
@ 2006-11-06 22:40 Jeff Chua
2006-11-07 15:50 ` Aaron Durbin
0 siblings, 1 reply; 30+ messages in thread
From: Jeff Chua @ 2006-11-06 22:40 UTC (permalink / raw)
To: Andi Kleen
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, linux-pci, Elimar Riesebieter, discuss,
Thierry Vignaud, Tim Chen, phil.el, gregkh, neilb, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman, cpufreq, Michael
On 11/7/06, Andi Kleen <ak@suse.de> 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?
1) booting with MMConfig ...
Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #1 SMP PREEMPT Sun Nov 5 17:18:48 SGT 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000df686c00 (usable)
BIOS-e820: 00000000df686c00 - 00000000df688c00 (ACPI NVS)
BIOS-e820: 00000000df688c00 - 00000000df68ac00 (ACPI data)
BIOS-e820: 00000000df68ac00 - 00000000e0000000 (reserved)
BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
2678MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000fe710
Entering add_active_range(0, 0, 915078) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 915078
early_node_map[1] active PFN ranges
0: 0 -> 915078
On node 0 totalpages: 915078
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 5357 pages used for memmap
HighMem zone: 680345 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v002 DELL ) @ 0x000feb00
ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd253
ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd34b
ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @ 0xfffd6996
ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd43f
ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4b1
ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4d9
ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd540
ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd57e
ACPI: SSDT (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309) @ 0xdf686c40
ACPI: SSDT (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309) @ 0xdf687049
ACPI: SSDT (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309) @ 0xdf687452
ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at e1000000 (gap: e0000000:10000000)
Detected 2992.724 MHz processor.
Built 1 zonelists. Total pages: 907929
Kernel command line: BOOT_IMAGE=(hd0,1)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 testing_only="this is got to be good. Now I can send in a very long line just like 2.4 and need not worry about the line being too long. What a great way to start a great year!!! Cool!"
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
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: 3625948k/3660312k available (2402k kernel code, 33292k reserved, 848k data, 200k init, 2742808k highmem)
virtual kernel memory layout:
fixmap : 0xfff4f000 - 0xfffff000 ( 704 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc0433000 - 0xc0465000 ( 200 kB)
.data : 0xc0358928 - 0xc042cab4 ( 848 kB)
.text : 0xc0100000 - 0xc0358928 (2402 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Using HPET for base-timer
Calibrating delay using timer specific routine.. 5990.52 BogoMIPS (lpj=11981048)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
CPU0: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5985.35 BogoMIPS (lpj=11970701)
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
monitor/mwait feature present.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
CPU1: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
Total of 2 processors activated (11975.87 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=327
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:00:02.0
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH6 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 10 devices
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 0 of device 0000:00:02.0
PCI: Cannot allocate resource region 3 of device 0000:00:02.0
PCI: Cannot allocate resource region 0 of device 0000:00:02.1
PCI: Cannot allocate resource region 0 of device 0000:00:1d.7
PCI: Cannot allocate resource region 2 of device 0000:00:1e.2
PCI: Cannot allocate resource region 3 of device 0000:00:1e.2
PCI: Cannot allocate resource region 0 of device 0000:02:00.0
NET: Registered protocol family 23
pnp: 00:01: ioport range 0x800-0x85f could not be reserved
pnp: 00:01: ioport range 0xc00-0xc7f has been reserved
pnp: 00:01: ioport range 0x860-0x8ff could not be reserved
pnp: 00:09: ioport range 0x100-0x1fe has been reserved
pnp: 00:09: ioport range 0x200-0x277 has been reserved
pnp: 00:09: ioport range 0x280-0x2e7 has been reserved
pnp: 00:09: ioport range 0x2f0-0x2f7 has been reserved
pnp: 00:09: ioport range 0x300-0x377 has been reserved
pnp: 00:09: ioport range 0x380-0x3bb has been reserved
pnp: 00:09: ioport range 0x3c0-0x3e7 could not be reserved
pnp: 00:09: ioport range 0x3f6-0x3f7 has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Failed to allocate mem resource #8:100000@e1000000 for 0000:00:1c.0
PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.0
PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.1
PCI: Failed to allocate mem resource #3:40000@e1000000 for 0000:00:02.0
PCI: Failed to allocate mem resource #0:400@e1000000 for 0000:00:1d.7
PCI: Failed to allocate mem resource #2:200@e1000000 for 0000:00:1e.2
PCI: Failed to allocate mem resource #3:100@e1000000 for 0000:00:1e.2
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Failed to allocate mem resource #0:10000@0 for 0000:02:00.0
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 262144 (order: 9, 3145728 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Simple Boot Flag at 0x7a set to 0x1
apm: disabled - APM is not SMP safe.
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:01.0:pcie00]
Allocate Port Service[0000:00:01.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
Allocate Port Service[0000:00:1c.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
Allocate Port Service[0000:00:1c.1:pcie03]
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
acpiphp_glue: can't get bus number, assuming 0
acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
Evaluate _OSC Set fails. Status = 0x0005
Evaluate _OSC Set fails. Status = 0x0005
pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.0
pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
Evaluate _OSC Set fails. Status = 0x0005
Evaluate _OSC Set fails. Status = 0x0005
pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.1
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [VBTN]
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x3
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x4
ibm_acpi: ec object not found
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 945G Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xe0000000
[drm] Initialized drm 1.0.1 20051102
RAMDISK driver initialized: 16 RAM disks of 20480K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 3.6.10)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: HL-DT-ST DVD+/-RW GWA4164B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006)
megasas: 00.00.03.05 Mon Oct 02 11:21:32 PDT 2006
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00ac6
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18
scsi0 : ata_piix
ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 8
ata1.01: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
ata1.01: ata1: dev 1 multi count 8
ata1.00: configured for UDMA/133
ata1.01: configured for UDMA/133
scsi1 : ata_piix
ata2: port is slow to respond, please be patient (Status 0xff)
ata2: port failed to respond (30 secs, Status 0xff)
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: reset failed, giving up
scsi 0:0:0:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
sd 0:0:0:0: Attached scsi disk sda
scsi 0:0:1:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
sdb:
sd 0:0:1:0: Attached scsi disk sdb
usbmon: debugfs is not available
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 19
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16
ehci_hcd: probe of 0000:00:1d.7 failed with error -16
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000ff80
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 22 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000ff40
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 22, io base 0x0000ff20
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 3-1: new low speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
usb 3-2: new low speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Dell Dell USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-1
input: USB Optical Mouse as /class/input/input1
input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.2-2
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
EDAC MC: Ver: 2.0.1 Nov 5 2006
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Starting balanced_irq
Using IPI No-Shortcut mode
Time: tsc clocksource has been installed.
ACPI: (supports S0 S1 S3 S4 S5)
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 200k freed
Adding 7823644k swap on /dev/sda3. Priority:-1 extents:1 across:7823644k
tg3.c:v3.67 (October 18, 2006)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
tg3: Cannot find proper PCI device base address, aborting.
ACPI: PCI interrupt for device 0000:02:00.0 disabled
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
2) booting with "Direct" ...
Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #5 SMP PREEMPT Sun Nov 5 17:24:04 SGT 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000df686c00 (usable)
BIOS-e820: 00000000df686c00 - 00000000df688c00 (ACPI NVS)
BIOS-e820: 00000000df688c00 - 00000000df68ac00 (ACPI data)
BIOS-e820: 00000000df68ac00 - 00000000e0000000 (reserved)
BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
2678MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000fe710
Entering add_active_range(0, 0, 915078) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 915078
early_node_map[1] active PFN ranges
0: 0 -> 915078
On node 0 totalpages: 915078
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 5357 pages used for memmap
HighMem zone: 680345 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP @ 0x000feb00/0x0024 (v002 DELL )
ACPI: XSDT @ 0x000fd253/0x0074 (v001 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: FACP @ 0x000fd34b/0x00F4 (v003 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: DSDT @ 0xfffd2b0e/0x3D69 (v001 DELL dt_ex 0x00001000 INTL 0x20050309)
ACPI: FACS @ 0xdf686c00/0x0040
ACPI: SSDT @ 0xfffd6996/0x00AA (v001 DELL st_ex 0x00001000 INTL 0x20050309)
ACPI: APIC @ 0x000fd43f/0x0072 (v001 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: BOOT @ 0x000fd4b1/0x0028 (v001 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: ASF! @ 0x000fd4d9/0x0067 (v016 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: MCFG @ 0x000fd540/0x003E (v001 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: HPET @ 0x000fd57e/0x0038 (v001 DELL GX620 0x00000007 ASL 0x00000061)
ACPI: SSDT @ 0xdf686c40/0x0175 (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309)
ACPI: SSDT @ 0xdf687049/0x0175 (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309)
ACPI: SSDT @ 0xdf687452/0x0140 (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309)
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at e1000000 (gap: e0000000:10000000)
Detected 2992.778 MHz processor.
Built 1 zonelists. Total pages: 907929
Kernel command line: BOOT_IMAGE=(hd0,1)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 testing_only="this is got to be good. Now I can send in a very long line just like 2.4 and need not worry about the line being too long. What a great way to start a great year!!! Cool!"
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
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: 3625956k/3660312k available (2399k kernel code, 33284k reserved, 847k data, 200k init, 2742808k highmem)
virtual kernel memory layout:
fixmap : 0xfff50000 - 0xfffff000 ( 700 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc0431000 - 0xc0463000 ( 200 kB)
.data : 0xc0357d28 - 0xc042bab4 ( 847 kB)
.text : 0xc0100000 - 0xc0357d28 (2399 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Using HPET for base-timer
Calibrating delay using timer specific routine.. 5990.58 BogoMIPS (lpj=11981166)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20061011
CPU0: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5985.36 BogoMIPS (lpj=11970720)
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
monitor/mwait feature present.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
CPU1: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
Total of 2 processors activated (11975.94 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=317
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb898, last bus=4
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:00:02.0
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH6 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 10 devices
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
NET: Registered protocol family 23
pnp: 00:01: ioport range 0x800-0x85f could not be reserved
pnp: 00:01: ioport range 0xc00-0xc7f has been reserved
pnp: 00:01: ioport range 0x860-0x8ff could not be reserved
pnp: 00:09: ioport range 0x100-0x1fe has been reserved
pnp: 00:09: ioport range 0x200-0x277 has been reserved
pnp: 00:09: ioport range 0x280-0x2e7 has been reserved
pnp: 00:09: ioport range 0x2f0-0x2f7 has been reserved
pnp: 00:09: ioport range 0x300-0x377 has been reserved
pnp: 00:09: ioport range 0x380-0x3bb has been reserved
pnp: 00:09: ioport range 0x3c0-0x3e7 could not be reserved
pnp: 00:09: ioport range 0x3f6-0x3f7 has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: fe900000-fe9fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: fe800000-fe8fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: fe700000-fe7fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 262144 (order: 9, 3145728 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Simple Boot Flag at 0x7a set to 0x1
apm: disabled - APM is not SMP safe.
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:01.0:pcie00]
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
acpiphp_glue: can't get bus number, assuming 0
acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
Evaluate _OSC Set fails. Status = 0x0005
Evaluate _OSC Set fails. Status = 0x0005
pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.0
pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
Evaluate _OSC Set fails. Status = 0x0005
Evaluate _OSC Set fails. Status = 0x0005
pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.1
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [VBTN]
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
ACPI: Getting cpuindex for acpiid 0x3
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
ACPI: Getting cpuindex for acpiid 0x4
ibm_acpi: ec object not found
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 945G Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xe0000000
[drm] Initialized drm 1.0.1 20051102
RAMDISK driver initialized: 16 RAM disks of 20480K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 3.6.10)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: HL-DT-ST DVD+/-RW GWA4164B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006)
megasas: 00.00.03.05 Mon Oct 02 11:21:32 PDT 2006
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00ac6
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18
scsi0 : ata_piix
ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 8
ata1.01: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
ata1.01: ata1: dev 1 multi count 8
ata1.00: configured for UDMA/133
ata1.01: configured for UDMA/133
scsi1 : ata_piix
ata2: port is slow to respond, please be patient (Status 0xff)
ata2: port failed to respond (30 secs, Status 0xff)
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: reset failed, giving up
scsi 0:0:0:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
sd 0:0:0:0: Attached scsi disk sda
scsi 0:0:1:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
sdb:
sd 0:0:1:0: Attached scsi disk sdb
usbmon: debugfs is not available
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80800
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000ff80
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 22 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000ff40
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 22, io base 0x0000ff20
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 4-1: new low speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usb 4-2: new low speed USB device using uhci_hcd and address 3
usb 4-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Dell Dell USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-1
input: USB Optical Mouse as /class/input/input1
input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.2-2
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
EDAC MC: Ver: 2.0.1 Nov 5 2006
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Starting balanced_irq
Using IPI No-Shortcut mode
Time: tsc clocksource has been installed.
ACPI: (supports S0 S1 S3 S4 S5)
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 200k freed
Adding 7823644k swap on /dev/sda3. Priority:-1 extents:1 across:7823644k
tg3.c:v3.67 (October 18, 2006)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:13:72:7b:2a:f0
eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
3) diff of (1) and (2). Note I've also patched acpi with
(acpi-test-20061011-2.6.19-rc3.diff.bz2), but with or without that patch,
tg3 still fails.
1c1
< Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #1 SMP PREEMPT Sun Nov 5 17:18:48 SGT 2006
---
> Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #5 SMP PREEMPT Sun Nov 5 17:24:04 SGT 2006
33,45c33,46
< ACPI: RSDP (v002 DELL ) @ 0x000feb00
< ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd253
< ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd34b
< ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @ 0xfffd6996
< ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd43f
< ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4b1
< ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4d9
< ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd540
< ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd57e
< ACPI: SSDT (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309) @ 0xdf686c40
< ACPI: SSDT (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309) @ 0xdf687049
< ACPI: SSDT (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309) @ 0xdf687452
< ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @ 0x00000000
---
> ACPI: RSDP @ 0x000feb00/0x0024 (v002 DELL )
> ACPI: XSDT @ 0x000fd253/0x0074 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: FACP @ 0x000fd34b/0x00F4 (v003 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: DSDT @ 0xfffd2b0e/0x3D69 (v001 DELL dt_ex 0x00001000 INTL 0x20050309)
> ACPI: FACS @ 0xdf686c00/0x0040
> ACPI: SSDT @ 0xfffd6996/0x00AA (v001 DELL st_ex 0x00001000 INTL 0x20050309)
> ACPI: APIC @ 0x000fd43f/0x0072 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: BOOT @ 0x000fd4b1/0x0028 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: ASF! @ 0x000fd4d9/0x0067 (v016 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: MCFG @ 0x000fd540/0x003E (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: HPET @ 0x000fd57e/0x0038 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: SSDT @ 0xdf686c40/0x0175 (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309)
> ACPI: SSDT @ 0xdf687049/0x0175 (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309)
> ACPI: SSDT @ 0xdf687452/0x0140 (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309)
66c67
< Detected 2992.724 MHz processor.
---
> Detected 2992.778 MHz processor.
78c79
< Memory: 3625948k/3660312k available (2402k kernel code, 33292k reserved, 848k data, 200k init, 2742808k highmem)
---
> Memory: 3625956k/3660312k available (2399k kernel code, 33284k reserved, 847k data, 200k init, 2742808k highmem)
80c81
< fixmap : 0xfff4f000 - 0xfffff000 ( 704 kB)
---
> fixmap : 0xfff50000 - 0xfffff000 ( 700 kB)
84,86c85,87
< .init : 0xc0433000 - 0xc0465000 ( 200 kB)
< .data : 0xc0358928 - 0xc042cab4 ( 848 kB)
< .text : 0xc0100000 - 0xc0358928 (2402 kB)
---
> .init : 0xc0431000 - 0xc0463000 ( 200 kB)
> .data : 0xc0357d28 - 0xc042bab4 ( 847 kB)
> .text : 0xc0100000 - 0xc0357d28 (2399 kB)
89c90
< Calibrating delay using timer specific routine.. 5990.52 BogoMIPS (lpj=11981048)
---
> Calibrating delay using timer specific routine.. 5990.58 BogoMIPS (lpj=11981166)
102c103
< ACPI: Core revision 20060707
---
> ACPI: Core revision 20061011
107c108
< Calibrating delay using timer specific routine.. 5985.35 BogoMIPS (lpj=11970701)
---
> Calibrating delay using timer specific routine.. 5985.36 BogoMIPS (lpj=11970720)
116c117
< Total of 2 processors activated (11975.87 BogoMIPS).
---
> Total of 2 processors activated (11975.94 BogoMIPS).
121c122
< migration_cost=327
---
> migration_cost=317
124c125
< PCI: Using MMCONFIG
---
> PCI: PCI BIOS revision 2.10 entry at 0xfb898, last bus=4
158,167d158
< PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0
< PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
< PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
< PCI: Cannot allocate resource region 0 of device 0000:00:02.0
< PCI: Cannot allocate resource region 3 of device 0000:00:02.0
< PCI: Cannot allocate resource region 0 of device 0000:00:02.1
< PCI: Cannot allocate resource region 0 of device 0000:00:1d.7
< PCI: Cannot allocate resource region 2 of device 0000:00:1e.2
< PCI: Cannot allocate resource region 3 of device 0000:00:1e.2
< PCI: Cannot allocate resource region 0 of device 0000:02:00.0
181,187d171
< PCI: Failed to allocate mem resource #8:100000@e1000000 for 0000:00:1c.0
< PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.0
< PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.1
< PCI: Failed to allocate mem resource #3:40000@e1000000 for 0000:00:02.0
< PCI: Failed to allocate mem resource #0:400@e1000000 for 0000:00:1d.7
< PCI: Failed to allocate mem resource #2:200@e1000000 for 0000:00:1e.2
< PCI: Failed to allocate mem resource #3:100@e1000000 for 0000:00:1e.2
190c174
< MEM window: disabled.
---
> MEM window: fe900000-fe9fffff
192d175
< PCI: Failed to allocate mem resource #0:10000@0 for 0000:02:00.0
195c178
< MEM window: disabled.
---
> MEM window: fe800000-fe8fffff
199c182
< MEM window: disabled.
---
> MEM window: fe700000-fe7fffff
229d211
< Allocate Port Service[0000:00:01.0:pcie03]
234d215
< Allocate Port Service[0000:00:1c.0:pcie03]
239d219
< Allocate Port Service[0000:00:1c.1:pcie03]
255c235
< ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
---
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
257c237
< ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
---
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
333,335c313,322
< ACPI: PCI interrupt for device 0000:00:1d.7 disabled
< ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16
< ehci_hcd: probe of 0000:00:1d.7 failed with error -16
---
> PCI: Setting latency timer of device 0000:00:1d.7 to 64
> ehci_hcd 0000:00:1d.7: EHCI Host Controller
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:1d.7: debug port 1
> PCI: cache line size of 128 is not supported by device 0000:00:1d.7
> ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80800
> ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 8 ports detected
340c327
< uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
---
> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
342,344c329,331
< usb usb1: configuration #1 chosen from 1 choice
< hub 1-0:1.0: USB hub found
< hub 1-0:1.0: 2 ports detected
---
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
348c335
< uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
---
> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
350,352c337,339
< usb usb2: configuration #1 chosen from 1 choice
< hub 2-0:1.0: USB hub found
< hub 2-0:1.0: 2 ports detected
---
> usb usb3: configuration #1 chosen from 1 choice
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 2 ports detected
356c343
< uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
---
> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
358,360c345,347
< usb usb3: configuration #1 chosen from 1 choice
< hub 3-0:1.0: USB hub found
< hub 3-0:1.0: 2 ports detected
---
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
364c351
< uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
---
> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
366,372c353,359
< usb usb4: configuration #1 chosen from 1 choice
< hub 4-0:1.0: USB hub found
< hub 4-0:1.0: 2 ports detected
< usb 3-1: new low speed USB device using uhci_hcd and address 2
< usb 3-1: configuration #1 chosen from 1 choice
< usb 3-2: new low speed USB device using uhci_hcd and address 3
< usb 3-2: configuration #1 chosen from 1 choice
---
> usb usb5: configuration #1 chosen from 1 choice
> hub 5-0:1.0: USB hub found
> hub 5-0:1.0: 2 ports detected
> usb 4-1: new low speed USB device using uhci_hcd and address 2
> usb 4-1: configuration #1 chosen from 1 choice
> usb 4-2: new low speed USB device using uhci_hcd and address 3
> usb 4-2: configuration #1 chosen from 1 choice
398,399c385,388
< tg3: Cannot find proper PCI device base address, aborting.
< ACPI: PCI interrupt for device 0000:02:00.0 disabled
---
> PCI: Setting latency timer of device 0000:02:00.0 to 64
> eth0: Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:13:72:7b:2a:f0
> eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth0: dma_rwctrl[76180000] dma_mask[64-bit]
401a391,392
> tg3: eth0: Link is up at 100 Mbps, full duplex.
> tg3: eth0: Flow control is on for TX and on for RX.
Thanks,
Jeff
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
2006-11-05 9:30 ` Jeff Chua
@ 2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 5:41 ` Len Brown
1 sibling, 1 reply; 30+ messages in thread
From: Ernst Herzberg @ 2006-11-07 2:17 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Christian,
Alex Romosan, openib-general, ak, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, linux-pci, Elimar Riesebieter, discuss,
Thierry Vignaud, Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Linux Kernel Mailing List, linux-acpi, mingo, nfs,
Eric W. Biederman, cpufreq
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>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 2:17 ` Ernst Herzberg
@ 2006-11-07 5:41 ` Len Brown
2006-11-07 20:05 ` Ernst Herzberg
0 siblings, 1 reply; 30+ messages in thread
From: Len Brown @ 2006-11-07 5:41 UTC (permalink / raw)
To: linux-pm
Cc: Andrew Morton, jgarzik, Thierry Vignaud, discuss, Ernst Herzberg,
Linux Kernel Mailing List, Alex Romosan, openib-general,
Christian, linux-ide, Linus Torvalds, oprofile-list, Jens Axboe,
Martin Lorenz, Bryan O'Sullivan, Elimar Riesebieter, linux-pm,
Komuro, Jeff Chua, phil.el, gregkh, ak, Adrian Bunk, linux-acpi,
mingo, nfs, Eric W. Biederman, cpufreq
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* 2.6.19-rc4: known unfixed regressions (v4)
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
` (2 preceding siblings ...)
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
@ 2006-11-07 13:30 ` Adrian Bunk
3 siblings, 0 replies; 30+ messages in thread
From: Adrian Bunk @ 2006-11-07 13:30 UTC (permalink / raw)
To: Linus Torvalds, Andrew Morton
Cc: Linux Kernel Mailing List, Ernst Herzberg, Len Brown, mingo,
Martin Lorenz, pavel, linux-pm, linux-acpi, Paolo Ornati,
Thierry Vignaud, jgarzik, linux-ide, Alex Romosan, Jens Axboe,
Prakash Punnoor, phil.el, oprofile-list, ak, discuss, Tim Chen,
Eric W. Biederman, Jeff Chua, gregkh, linux-pci, Komuro,
Thomas Gleixner, Bryan O'Sullivan, openib-general, Arja
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
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-06 22:40 [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3) Jeff Chua
@ 2006-11-07 15:50 ` Aaron Durbin
0 siblings, 0 replies; 30+ messages in thread
From: Aaron Durbin @ 2006-11-07 15:50 UTC (permalink / raw)
To: Jeff Chua
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general, Andi Kleen, linux-ide,
Linus Torvalds, oprofile-list, Jens Axboe, Martin Lorenz,
linux-pci, Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman
Jeff,
Could please you post a dump of /proc/iomem for both the kernel that
works for you and the kernel that fails to allocate the PCI resources?
-Aaron
On 11/6/06, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>
>
> On 11/7/06, Andi Kleen <ak@suse.de> 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?
>
>
>
> 1) booting with MMConfig ...
>
> Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #1 SMP PREEMPT Sun Nov 5 17:18:48 SGT 2006
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 00000000df686c00 (usable)
> BIOS-e820: 00000000df686c00 - 00000000df688c00 (ACPI NVS)
> BIOS-e820: 00000000df688c00 - 00000000df68ac00 (ACPI data)
> BIOS-e820: 00000000df68ac00 - 00000000e0000000 (reserved)
> BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
> BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
> BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
> BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
> 2678MB HIGHMEM available.
> 896MB LOWMEM available.
> found SMP MP-table at 000fe710
> Entering add_active_range(0, 0, 915078) 0 entries of 256 used
> Zone PFN ranges:
> DMA 0 -> 4096
> Normal 4096 -> 229376
> HighMem 229376 -> 915078
> early_node_map[1] active PFN ranges
> 0: 0 -> 915078
> On node 0 totalpages: 915078
> DMA zone: 32 pages used for memmap
> DMA zone: 0 pages reserved
> DMA zone: 4064 pages, LIFO batch:0
> Normal zone: 1760 pages used for memmap
> Normal zone: 223520 pages, LIFO batch:31
> HighMem zone: 5357 pages used for memmap
> HighMem zone: 680345 pages, LIFO batch:31
> DMI 2.3 present.
> ACPI: RSDP (v002 DELL ) @ 0x000feb00
> ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd253
> ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd34b
> ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @ 0xfffd6996
> ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd43f
> ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4b1
> ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4d9
> ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd540
> ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd57e
> ACPI: SSDT (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309) @ 0xdf686c40
> ACPI: SSDT (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309) @ 0xdf687049
> ACPI: SSDT (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309) @ 0xdf687452
> ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @ 0x00000000
> ACPI: PM-Timer IO Port: 0x808
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> Processor #0 15:4 APIC version 20
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> Processor #1 15:4 APIC version 20
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
> ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
> ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ9 used by override.
> Enabling APIC mode: Flat. Using 1 I/O APICs
> ACPI: HPET id: 0x8086a201 base: 0xfed00000
> Using ACPI (MADT) for SMP configuration information
> Allocating PCI resources starting at e1000000 (gap: e0000000:10000000)
> Detected 2992.724 MHz processor.
> Built 1 zonelists. Total pages: 907929
> Kernel command line: BOOT_IMAGE=(hd0,1)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 testing_only="this is got to be good. Now I can send in a very long line just like 2.4 and need not worry about the line being too long. What a great way to start a great year!!! Cool!"
> mapped APIC to ffffd000 (fee00000)
> mapped IOAPIC to ffffc000 (fec00000)
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> 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: 3625948k/3660312k available (2402k kernel code, 33292k reserved, 848k data, 200k init, 2742808k highmem)
> virtual kernel memory layout:
> fixmap : 0xfff4f000 - 0xfffff000 ( 704 kB)
> pkmap : 0xff800000 - 0xffc00000 (4096 kB)
> vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
> lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
> .init : 0xc0433000 - 0xc0465000 ( 200 kB)
> .data : 0xc0358928 - 0xc042cab4 ( 848 kB)
> .text : 0xc0100000 - 0xc0358928 (2402 kB)
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> Using HPET for base-timer
> Calibrating delay using timer specific routine.. 5990.52 BogoMIPS (lpj=11981048)
> Mount-cache hash table entries: 512
> CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
> monitor/mwait feature present.
> using mwait in idle threads.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
> Compat vDSO mapped to ffffe000.
> Checking 'hlt' instruction... OK.
> SMP alternatives: switching to UP code
> ACPI: Core revision 20060707
> CPU0: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
> SMP alternatives: switching to SMP code
> Booting processor 1/1 eip 3000
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 5985.35 BogoMIPS (lpj=11970701)
> CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
> monitor/mwait feature present.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
> CPU1: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
> Total of 2 processors activated (11975.87 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization across 2 CPUs: passed.
> Brought up 2 CPUs
> migration_cost=327
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: Using MMCONFIG
> Setting up standard PCI resources
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
> Boot video device is 0000:00:02.0
> PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
> PCI quirk: region 0880-08bf claimed by ICH6 GPIO
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> PCI: Transparent bridge - 0000:00:1e.0
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI4._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI3._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 15)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI init
> pnp: PnP ACPI: found 10 devices
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
> PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0
> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
> PCI: Cannot allocate resource region 0 of device 0000:00:02.0
> PCI: Cannot allocate resource region 3 of device 0000:00:02.0
> PCI: Cannot allocate resource region 0 of device 0000:00:02.1
> PCI: Cannot allocate resource region 0 of device 0000:00:1d.7
> PCI: Cannot allocate resource region 2 of device 0000:00:1e.2
> PCI: Cannot allocate resource region 3 of device 0000:00:1e.2
> PCI: Cannot allocate resource region 0 of device 0000:02:00.0
> NET: Registered protocol family 23
> pnp: 00:01: ioport range 0x800-0x85f could not be reserved
> pnp: 00:01: ioport range 0xc00-0xc7f has been reserved
> pnp: 00:01: ioport range 0x860-0x8ff could not be reserved
> pnp: 00:09: ioport range 0x100-0x1fe has been reserved
> pnp: 00:09: ioport range 0x200-0x277 has been reserved
> pnp: 00:09: ioport range 0x280-0x2e7 has been reserved
> pnp: 00:09: ioport range 0x2f0-0x2f7 has been reserved
> pnp: 00:09: ioport range 0x300-0x377 has been reserved
> pnp: 00:09: ioport range 0x380-0x3bb has been reserved
> pnp: 00:09: ioport range 0x3c0-0x3e7 could not be reserved
> pnp: 00:09: ioport range 0x3f6-0x3f7 has been reserved
> PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
> PCI: Failed to allocate mem resource #8:100000@e1000000 for 0000:00:1c.0
> PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.0
> PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.1
> PCI: Failed to allocate mem resource #3:40000@e1000000 for 0000:00:02.0
> PCI: Failed to allocate mem resource #0:400@e1000000 for 0000:00:1d.7
> PCI: Failed to allocate mem resource #2:200@e1000000 for 0000:00:1e.2
> PCI: Failed to allocate mem resource #3:100@e1000000 for 0000:00:1e.2
> PCI: Bridge: 0000:00:01.0
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
> PCI: Failed to allocate mem resource #0:10000@0 for 0000:02:00.0
> PCI: Bridge: 0000:00:1c.0
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1c.1
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1e.0
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
> ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:01.0 to 64
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.1 to 64
> PCI: Setting latency timer of device 0000:00:1e.0 to 64
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> TCP established hash table entries: 262144 (order: 9, 3145728 bytes)
> TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
> TCP: Hash tables configured (established 262144 bind 65536)
> TCP reno registered
> Simple Boot Flag at 0x7a set to 0x1
> apm: disabled - APM is not SMP safe.
> highmem bounce pool size: 64 pages
> Total HugeTLB memory allocated, 0
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> PCI: Setting latency timer of device 0000:00:01.0 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:01.0:pcie00]
> Allocate Port Service[0000:00:01.0:pcie03]
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:1c.0:pcie00]
> Allocate Port Service[0000:00:1c.0:pcie02]
> Allocate Port Service[0000:00:1c.0:pcie03]
> PCI: Setting latency timer of device 0000:00:1c.1 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:1c.1:pcie00]
> Allocate Port Service[0000:00:1c.1:pcie02]
> Allocate Port Service[0000:00:1c.1:pcie03]
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> acpiphp_glue: can't get bus number, assuming 0
> acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
> pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.0
> pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.1
> pciehp: PCI Express Hot Plug Controller Driver version: 0.4
> ACPI: Power Button (FF) [PWRF]
> ACPI: Power Button (CM) [VBTN]
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
> ACPI: Getting cpuindex for acpiid 0x3
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
> ACPI: Getting cpuindex for acpiid 0x4
> ibm_acpi: ec object not found
> Real Time Clock Driver v1.12ac
> Linux agpgart interface v0.101 (c) Dave Jones
> agpgart: Detected an Intel 945G Chipset.
> agpgart: Detected 7932K stolen memory.
> agpgart: AGP aperture is 256M @ 0xe0000000
> [drm] Initialized drm 1.0.1 20051102
> RAMDISK driver initialized: 16 RAM disks of 20480K size 1024 blocksize
> loop: loaded (max 8 devices)
> HP CISS Driver (v 3.6.10)
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> ICH7: IDE controller at PCI slot 0000:00:1f.1
> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
> ICH7: chipset revision 1
> ICH7: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
> Probing IDE interface ide0...
> hda: HL-DT-ST DVD+/-RW GWA4164B, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
> megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006)
> megasas: 00.00.03.05 Mon Oct 02 11:21:32 PDT 2006
> libata version 2.00 loaded.
> ata_piix 0000:00:1f.2: version 2.00ac6
> ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
> ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:00:1f.2 to 64
> ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18
> ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18
> scsi0 : ata_piix
> ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
> ata1.00: ata1: dev 0 multi count 8
> ata1.01: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
> ata1.01: ata1: dev 1 multi count 8
> ata1.00: configured for UDMA/133
> ata1.01: configured for UDMA/133
> scsi1 : ata_piix
> ata2: port is slow to respond, please be patient (Status 0xff)
> ata2: port failed to respond (30 secs, Status 0xff)
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: softreset failed, retrying in 5 secs
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: softreset failed, retrying in 5 secs
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: reset failed, giving up
> scsi 0:0:0:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
> SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
> SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
> sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
> sd 0:0:0:0: Attached scsi disk sda
> scsi 0:0:1:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
> SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
> sdb:
> sd 0:0:1:0: Attached scsi disk sdb
> usbmon: debugfs is not available
> ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 19
> ACPI: PCI interrupt for device 0000:00:1d.7 disabled
> ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16
> ehci_hcd: probe of 0000:00:1d.7 failed with error -16
> USB Universal Host Controller Interface driver v3.0
> ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:00:1d.0 to 64
> uhci_hcd 0000:00:1d.0: UHCI Host Controller
> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
> uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000ff80
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 22 (level, low) -> IRQ 20
> PCI: Setting latency timer of device 0000:00:1d.1 to 64
> uhci_hcd 0000:00:1d.1: UHCI Host Controller
> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
> uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
> PCI: Setting latency timer of device 0000:00:1d.2 to 64
> uhci_hcd 0000:00:1d.2: UHCI Host Controller
> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000ff40
> usb usb3: configuration #1 chosen from 1 choice
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 22
> PCI: Setting latency timer of device 0000:00:1d.3 to 64
> uhci_hcd 0000:00:1d.3: UHCI Host Controller
> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
> uhci_hcd 0000:00:1d.3: irq 22, io base 0x0000ff20
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
> usb 3-1: new low speed USB device using uhci_hcd and address 2
> usb 3-1: configuration #1 chosen from 1 choice
> usb 3-2: new low speed USB device using uhci_hcd and address 3
> usb 3-2: configuration #1 chosen from 1 choice
> usbcore: registered new interface driver hiddev
> input: Dell Dell USB Keyboard as /class/input/input0
> input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-1
> input: USB Optical Mouse as /class/input/input1
> input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.2-2
> usbcore: registered new interface driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
> mice: PS/2 mouse device common for all mice
> device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
> EDAC MC: Ver: 2.0.1 Nov 5 2006
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Starting balanced_irq
> Using IPI No-Shortcut mode
> Time: tsc clocksource has been installed.
> ACPI: (supports S0 S1 S3 S4 S5)
> VFS: Mounted root (reiserfs filesystem) readonly.
> Freeing unused kernel memory: 200k freed
> Adding 7823644k swap on /dev/sda3. Priority:-1 extents:1 across:7823644k
> tg3.c:v3.67 (October 18, 2006)
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> tg3: Cannot find proper PCI device base address, aborting.
> ACPI: PCI interrupt for device 0000:02:00.0 disabled
> ip_tables: (C) 2000-2006 Netfilter Core Team
> ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
>
>
>
> 2) booting with "Direct" ...
>
> Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #5 SMP PREEMPT Sun Nov 5 17:24:04 SGT 2006
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 00000000df686c00 (usable)
> BIOS-e820: 00000000df686c00 - 00000000df688c00 (ACPI NVS)
> BIOS-e820: 00000000df688c00 - 00000000df68ac00 (ACPI data)
> BIOS-e820: 00000000df68ac00 - 00000000e0000000 (reserved)
> BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
> BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
> BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
> BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
> 2678MB HIGHMEM available.
> 896MB LOWMEM available.
> found SMP MP-table at 000fe710
> Entering add_active_range(0, 0, 915078) 0 entries of 256 used
> Zone PFN ranges:
> DMA 0 -> 4096
> Normal 4096 -> 229376
> HighMem 229376 -> 915078
> early_node_map[1] active PFN ranges
> 0: 0 -> 915078
> On node 0 totalpages: 915078
> DMA zone: 32 pages used for memmap
> DMA zone: 0 pages reserved
> DMA zone: 4064 pages, LIFO batch:0
> Normal zone: 1760 pages used for memmap
> Normal zone: 223520 pages, LIFO batch:31
> HighMem zone: 5357 pages used for memmap
> HighMem zone: 680345 pages, LIFO batch:31
> DMI 2.3 present.
> ACPI: RSDP @ 0x000feb00/0x0024 (v002 DELL )
> ACPI: XSDT @ 0x000fd253/0x0074 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: FACP @ 0x000fd34b/0x00F4 (v003 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: DSDT @ 0xfffd2b0e/0x3D69 (v001 DELL dt_ex 0x00001000 INTL 0x20050309)
> ACPI: FACS @ 0xdf686c00/0x0040
> ACPI: SSDT @ 0xfffd6996/0x00AA (v001 DELL st_ex 0x00001000 INTL 0x20050309)
> ACPI: APIC @ 0x000fd43f/0x0072 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: BOOT @ 0x000fd4b1/0x0028 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: ASF! @ 0x000fd4d9/0x0067 (v016 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: MCFG @ 0x000fd540/0x003E (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: HPET @ 0x000fd57e/0x0038 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> ACPI: SSDT @ 0xdf686c40/0x0175 (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309)
> ACPI: SSDT @ 0xdf687049/0x0175 (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309)
> ACPI: SSDT @ 0xdf687452/0x0140 (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309)
> ACPI: PM-Timer IO Port: 0x808
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> Processor #0 15:4 APIC version 20
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> Processor #1 15:4 APIC version 20
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
> ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
> ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ9 used by override.
> Enabling APIC mode: Flat. Using 1 I/O APICs
> ACPI: HPET id: 0x8086a201 base: 0xfed00000
> Using ACPI (MADT) for SMP configuration information
> Allocating PCI resources starting at e1000000 (gap: e0000000:10000000)
> Detected 2992.778 MHz processor.
> Built 1 zonelists. Total pages: 907929
> Kernel command line: BOOT_IMAGE=(hd0,1)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 testing_only="this is got to be good. Now I can send in a very long line just like 2.4 and need not worry about the line being too long. What a great way to start a great year!!! Cool!"
> mapped APIC to ffffd000 (fee00000)
> mapped IOAPIC to ffffc000 (fec00000)
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> 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: 3625956k/3660312k available (2399k kernel code, 33284k reserved, 847k data, 200k init, 2742808k highmem)
> virtual kernel memory layout:
> fixmap : 0xfff50000 - 0xfffff000 ( 700 kB)
> pkmap : 0xff800000 - 0xffc00000 (4096 kB)
> vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
> lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
> .init : 0xc0431000 - 0xc0463000 ( 200 kB)
> .data : 0xc0357d28 - 0xc042bab4 ( 847 kB)
> .text : 0xc0100000 - 0xc0357d28 (2399 kB)
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> Using HPET for base-timer
> Calibrating delay using timer specific routine.. 5990.58 BogoMIPS (lpj=11981166)
> Mount-cache hash table entries: 512
> CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
> monitor/mwait feature present.
> using mwait in idle threads.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
> Compat vDSO mapped to ffffe000.
> Checking 'hlt' instruction... OK.
> SMP alternatives: switching to UP code
> ACPI: Core revision 20061011
> CPU0: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
> SMP alternatives: switching to SMP code
> Booting processor 1/1 eip 3000
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 5985.36 BogoMIPS (lpj=11970720)
> CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000001
> monitor/mwait feature present.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000001
> CPU1: Intel(R) Pentium(R) D CPU 3.00GHz stepping 07
> Total of 2 processors activated (11975.94 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization across 2 CPUs: passed.
> Brought up 2 CPUs
> migration_cost=317
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: PCI BIOS revision 2.10 entry at 0xfb898, last bus=4
> Setting up standard PCI resources
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
> Boot video device is 0000:00:02.0
> PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
> PCI quirk: region 0880-08bf claimed by ICH6 GPIO
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> PCI: Transparent bridge - 0000:00:1e.0
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI4._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI3._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
> ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 15)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI init
> pnp: PnP ACPI: found 10 devices
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
> NET: Registered protocol family 23
> pnp: 00:01: ioport range 0x800-0x85f could not be reserved
> pnp: 00:01: ioport range 0xc00-0xc7f has been reserved
> pnp: 00:01: ioport range 0x860-0x8ff could not be reserved
> pnp: 00:09: ioport range 0x100-0x1fe has been reserved
> pnp: 00:09: ioport range 0x200-0x277 has been reserved
> pnp: 00:09: ioport range 0x280-0x2e7 has been reserved
> pnp: 00:09: ioport range 0x2f0-0x2f7 has been reserved
> pnp: 00:09: ioport range 0x300-0x377 has been reserved
> pnp: 00:09: ioport range 0x380-0x3bb has been reserved
> pnp: 00:09: ioport range 0x3c0-0x3e7 could not be reserved
> pnp: 00:09: ioport range 0x3f6-0x3f7 has been reserved
> PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
> PCI: Bridge: 0000:00:01.0
> IO window: disabled.
> MEM window: fe900000-fe9fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1c.0
> IO window: disabled.
> MEM window: fe800000-fe8fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1c.1
> IO window: disabled.
> MEM window: fe700000-fe7fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1e.0
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
> ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:01.0 to 64
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.1 to 64
> PCI: Setting latency timer of device 0000:00:1e.0 to 64
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> TCP established hash table entries: 262144 (order: 9, 3145728 bytes)
> TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
> TCP: Hash tables configured (established 262144 bind 65536)
> TCP reno registered
> Simple Boot Flag at 0x7a set to 0x1
> apm: disabled - APM is not SMP safe.
> highmem bounce pool size: 64 pages
> Total HugeTLB memory allocated, 0
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> PCI: Setting latency timer of device 0000:00:01.0 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:01.0:pcie00]
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:1c.0:pcie00]
> Allocate Port Service[0000:00:1c.0:pcie02]
> PCI: Setting latency timer of device 0000:00:1c.1 to 64
> assign_interrupt_mode Found MSI capability
> Allocate Port Service[0000:00:1c.1:pcie00]
> Allocate Port Service[0000:00:1c.1:pcie02]
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> acpiphp_glue: can't get bus number, assuming 0
> acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
> pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.0
> pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
> Evaluate _OSC Set fails. Status = 0x0005
> Evaluate _OSC Set fails. Status = 0x0005
> pciehp: Cannot get control of hotplug hardware for pci 0000:00:1c.1
> pciehp: PCI Express Hot Plug Controller Driver version: 0.4
> ACPI: Power Button (FF) [PWRF]
> ACPI: Power Button (CM) [VBTN]
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
> ACPI: Getting cpuindex for acpiid 0x3
> ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
> ACPI: Getting cpuindex for acpiid 0x4
> ibm_acpi: ec object not found
> Real Time Clock Driver v1.12ac
> Linux agpgart interface v0.101 (c) Dave Jones
> agpgart: Detected an Intel 945G Chipset.
> agpgart: Detected 7932K stolen memory.
> agpgart: AGP aperture is 256M @ 0xe0000000
> [drm] Initialized drm 1.0.1 20051102
> RAMDISK driver initialized: 16 RAM disks of 20480K size 1024 blocksize
> loop: loaded (max 8 devices)
> HP CISS Driver (v 3.6.10)
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> ICH7: IDE controller at PCI slot 0000:00:1f.1
> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
> ICH7: chipset revision 1
> ICH7: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
> Probing IDE interface ide0...
> hda: HL-DT-ST DVD+/-RW GWA4164B, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
> megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006)
> megasas: 00.00.03.05 Mon Oct 02 11:21:32 PDT 2006
> libata version 2.00 loaded.
> ata_piix 0000:00:1f.2: version 2.00ac6
> ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
> ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:00:1f.2 to 64
> ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18
> ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18
> scsi0 : ata_piix
> ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
> ata1.00: ata1: dev 0 multi count 8
> ata1.01: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32)
> ata1.01: ata1: dev 1 multi count 8
> ata1.00: configured for UDMA/133
> ata1.01: configured for UDMA/133
> scsi1 : ata_piix
> ata2: port is slow to respond, please be patient (Status 0xff)
> ata2: port failed to respond (30 secs, Status 0xff)
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: softreset failed, retrying in 5 secs
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: softreset failed, retrying in 5 secs
> ata2: SRST failed (status 0xFF)
> ata2: SRST failed (err_mask=0x100)
> ata2: reset failed, giving up
> scsi 0:0:0:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
> SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
> SCSI device sda: 488281250 512-byte hdwr sectors (250000 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
> sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
> sd 0:0:0:0: Attached scsi disk sda
> scsi 0:0:1:0: Direct-Access ATA WDC WD2500JS-75N 10.0 PQ: 0 ANSI: 5
> SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 488281250 512-byte hdwr sectors (250000 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
> sdb:
> sd 0:0:1:0: Attached scsi disk sdb
> usbmon: debugfs is not available
> ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:00:1d.7 to 64
> ehci_hcd 0000:00:1d.7: EHCI Host Controller
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:1d.7: debug port 1
> PCI: cache line size of 128 is not supported by device 0000:00:1d.7
> ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80800
> ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 8 ports detected
> USB Universal Host Controller Interface driver v3.0
> ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:00:1d.0 to 64
> uhci_hcd 0000:00:1d.0: UHCI Host Controller
> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
> uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000ff80
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 22 (level, low) -> IRQ 20
> PCI: Setting latency timer of device 0000:00:1d.1 to 64
> uhci_hcd 0000:00:1d.1: UHCI Host Controller
> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60
> usb usb3: configuration #1 chosen from 1 choice
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
> PCI: Setting latency timer of device 0000:00:1d.2 to 64
> uhci_hcd 0000:00:1d.2: UHCI Host Controller
> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
> uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000ff40
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 22
> PCI: Setting latency timer of device 0000:00:1d.3 to 64
> uhci_hcd 0000:00:1d.3: UHCI Host Controller
> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> uhci_hcd 0000:00:1d.3: irq 22, io base 0x0000ff20
> usb usb5: configuration #1 chosen from 1 choice
> hub 5-0:1.0: USB hub found
> hub 5-0:1.0: 2 ports detected
> usb 4-1: new low speed USB device using uhci_hcd and address 2
> usb 4-1: configuration #1 chosen from 1 choice
> usb 4-2: new low speed USB device using uhci_hcd and address 3
> usb 4-2: configuration #1 chosen from 1 choice
> usbcore: registered new interface driver hiddev
> input: Dell Dell USB Keyboard as /class/input/input0
> input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-1
> input: USB Optical Mouse as /class/input/input1
> input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.2-2
> usbcore: registered new interface driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
> mice: PS/2 mouse device common for all mice
> device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
> EDAC MC: Ver: 2.0.1 Nov 5 2006
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Starting balanced_irq
> Using IPI No-Shortcut mode
> Time: tsc clocksource has been installed.
> ACPI: (supports S0 S1 S3 S4 S5)
> VFS: Mounted root (reiserfs filesystem) readonly.
> Freeing unused kernel memory: 200k freed
> Adding 7823644k swap on /dev/sda3. Priority:-1 extents:1 across:7823644k
> tg3.c:v3.67 (October 18, 2006)
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:02:00.0 to 64
> eth0: Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:13:72:7b:2a:f0
> eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth0: dma_rwctrl[76180000] dma_mask[64-bit]
> ip_tables: (C) 2000-2006 Netfilter Core Team
> ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
> tg3: eth0: Link is up at 100 Mbps, full duplex.
> tg3: eth0: Flow control is on for TX and on for RX.
>
>
>
>
> 3) diff of (1) and (2). Note I've also patched acpi with
> (acpi-test-20061011-2.6.19-rc3.diff.bz2), but with or without that patch,
> tg3 still fails.
>
> 1c1
> < Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #1 SMP PREEMPT Sun Nov 5 17:18:48 SGT 2006
> ---
> > Linux version 2.6.19-rc4 (root@indiana.corp.fedex.com) (gcc version 3.4.5) #5 SMP PREEMPT Sun Nov 5 17:24:04 SGT 2006
> 33,45c33,46
> < ACPI: RSDP (v002 DELL ) @ 0x000feb00
> < ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd253
> < ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd34b
> < ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @ 0xfffd6996
> < ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd43f
> < ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4b1
> < ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd4d9
> < ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd540
> < ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x000fd57e
> < ACPI: SSDT (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309) @ 0xdf686c40
> < ACPI: SSDT (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309) @ 0xdf687049
> < ACPI: SSDT (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309) @ 0xdf687452
> < ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @ 0x00000000
> ---
> > ACPI: RSDP @ 0x000feb00/0x0024 (v002 DELL )
> > ACPI: XSDT @ 0x000fd253/0x0074 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: FACP @ 0x000fd34b/0x00F4 (v003 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: DSDT @ 0xfffd2b0e/0x3D69 (v001 DELL dt_ex 0x00001000 INTL 0x20050309)
> > ACPI: FACS @ 0xdf686c00/0x0040
> > ACPI: SSDT @ 0xfffd6996/0x00AA (v001 DELL st_ex 0x00001000 INTL 0x20050309)
> > ACPI: APIC @ 0x000fd43f/0x0072 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: BOOT @ 0x000fd4b1/0x0028 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: ASF! @ 0x000fd4d9/0x0067 (v016 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: MCFG @ 0x000fd540/0x003E (v001 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: HPET @ 0x000fd57e/0x0038 (v001 DELL GX620 0x00000007 ASL 0x00000061)
> > ACPI: SSDT @ 0xdf686c40/0x0175 (v001 DpgPmm Cpu0Ist 0x00000011 INTL 0x20050309)
> > ACPI: SSDT @ 0xdf687049/0x0175 (v001 DpgPmm Cpu1Ist 0x00000011 INTL 0x20050309)
> > ACPI: SSDT @ 0xdf687452/0x0140 (v001 DpgPmm CpuPm 0x00000010 INTL 0x20050309)
> 66c67
> < Detected 2992.724 MHz processor.
> ---
> > Detected 2992.778 MHz processor.
> 78c79
> < Memory: 3625948k/3660312k available (2402k kernel code, 33292k reserved, 848k data, 200k init, 2742808k highmem)
> ---
> > Memory: 3625956k/3660312k available (2399k kernel code, 33284k reserved, 847k data, 200k init, 2742808k highmem)
> 80c81
> < fixmap : 0xfff4f000 - 0xfffff000 ( 704 kB)
> ---
> > fixmap : 0xfff50000 - 0xfffff000 ( 700 kB)
> 84,86c85,87
> < .init : 0xc0433000 - 0xc0465000 ( 200 kB)
> < .data : 0xc0358928 - 0xc042cab4 ( 848 kB)
> < .text : 0xc0100000 - 0xc0358928 (2402 kB)
> ---
> > .init : 0xc0431000 - 0xc0463000 ( 200 kB)
> > .data : 0xc0357d28 - 0xc042bab4 ( 847 kB)
> > .text : 0xc0100000 - 0xc0357d28 (2399 kB)
> 89c90
> < Calibrating delay using timer specific routine.. 5990.52 BogoMIPS (lpj=11981048)
> ---
> > Calibrating delay using timer specific routine.. 5990.58 BogoMIPS (lpj=11981166)
> 102c103
> < ACPI: Core revision 20060707
> ---
> > ACPI: Core revision 20061011
> 107c108
> < Calibrating delay using timer specific routine.. 5985.35 BogoMIPS (lpj=11970701)
> ---
> > Calibrating delay using timer specific routine.. 5985.36 BogoMIPS (lpj=11970720)
> 116c117
> < Total of 2 processors activated (11975.87 BogoMIPS).
> ---
> > Total of 2 processors activated (11975.94 BogoMIPS).
> 121c122
> < migration_cost=327
> ---
> > migration_cost=317
> 124c125
> < PCI: Using MMCONFIG
> ---
> > PCI: PCI BIOS revision 2.10 entry at 0xfb898, last bus=4
> 158,167d158
> < PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0
> < PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
> < PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
> < PCI: Cannot allocate resource region 0 of device 0000:00:02.0
> < PCI: Cannot allocate resource region 3 of device 0000:00:02.0
> < PCI: Cannot allocate resource region 0 of device 0000:00:02.1
> < PCI: Cannot allocate resource region 0 of device 0000:00:1d.7
> < PCI: Cannot allocate resource region 2 of device 0000:00:1e.2
> < PCI: Cannot allocate resource region 3 of device 0000:00:1e.2
> < PCI: Cannot allocate resource region 0 of device 0000:02:00.0
> 181,187d171
> < PCI: Failed to allocate mem resource #8:100000@e1000000 for 0000:00:1c.0
> < PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.0
> < PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.1
> < PCI: Failed to allocate mem resource #3:40000@e1000000 for 0000:00:02.0
> < PCI: Failed to allocate mem resource #0:400@e1000000 for 0000:00:1d.7
> < PCI: Failed to allocate mem resource #2:200@e1000000 for 0000:00:1e.2
> < PCI: Failed to allocate mem resource #3:100@e1000000 for 0000:00:1e.2
> 190c174
> < MEM window: disabled.
> ---
> > MEM window: fe900000-fe9fffff
> 192d175
> < PCI: Failed to allocate mem resource #0:10000@0 for 0000:02:00.0
> 195c178
> < MEM window: disabled.
> ---
> > MEM window: fe800000-fe8fffff
> 199c182
> < MEM window: disabled.
> ---
> > MEM window: fe700000-fe7fffff
> 229d211
> < Allocate Port Service[0000:00:01.0:pcie03]
> 234d215
> < Allocate Port Service[0000:00:1c.0:pcie03]
> 239d219
> < Allocate Port Service[0000:00:1c.1:pcie03]
> 255c235
> < ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
> ---
> > ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
> 257c237
> < ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
> ---
> > ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20061011]
> 333,335c313,322
> < ACPI: PCI interrupt for device 0000:00:1d.7 disabled
> < ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16
> < ehci_hcd: probe of 0000:00:1d.7 failed with error -16
> ---
> > PCI: Setting latency timer of device 0000:00:1d.7 to 64
> > ehci_hcd 0000:00:1d.7: EHCI Host Controller
> > ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> > ehci_hcd 0000:00:1d.7: debug port 1
> > PCI: cache line size of 128 is not supported by device 0000:00:1d.7
> > ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80800
> > ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> > usb usb1: configuration #1 chosen from 1 choice
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 8 ports detected
> 340c327
> < uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
> ---
> > uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
> 342,344c329,331
> < usb usb1: configuration #1 chosen from 1 choice
> < hub 1-0:1.0: USB hub found
> < hub 1-0:1.0: 2 ports detected
> ---
> > usb usb2: configuration #1 chosen from 1 choice
> > hub 2-0:1.0: USB hub found
> > hub 2-0:1.0: 2 ports detected
> 348c335
> < uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
> ---
> > uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> 350,352c337,339
> < usb usb2: configuration #1 chosen from 1 choice
> < hub 2-0:1.0: USB hub found
> < hub 2-0:1.0: 2 ports detected
> ---
> > usb usb3: configuration #1 chosen from 1 choice
> > hub 3-0:1.0: USB hub found
> > hub 3-0:1.0: 2 ports detected
> 356c343
> < uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
> ---
> > uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
> 358,360c345,347
> < usb usb3: configuration #1 chosen from 1 choice
> < hub 3-0:1.0: USB hub found
> < hub 3-0:1.0: 2 ports detected
> ---
> > usb usb4: configuration #1 chosen from 1 choice
> > hub 4-0:1.0: USB hub found
> > hub 4-0:1.0: 2 ports detected
> 364c351
> < uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
> ---
> > uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> 366,372c353,359
> < usb usb4: configuration #1 chosen from 1 choice
> < hub 4-0:1.0: USB hub found
> < hub 4-0:1.0: 2 ports detected
> < usb 3-1: new low speed USB device using uhci_hcd and address 2
> < usb 3-1: configuration #1 chosen from 1 choice
> < usb 3-2: new low speed USB device using uhci_hcd and address 3
> < usb 3-2: configuration #1 chosen from 1 choice
> ---
> > usb usb5: configuration #1 chosen from 1 choice
> > hub 5-0:1.0: USB hub found
> > hub 5-0:1.0: 2 ports detected
> > usb 4-1: new low speed USB device using uhci_hcd and address 2
> > usb 4-1: configuration #1 chosen from 1 choice
> > usb 4-2: new low speed USB device using uhci_hcd and address 3
> > usb 4-2: configuration #1 chosen from 1 choice
> 398,399c385,388
> < tg3: Cannot find proper PCI device base address, aborting.
> < ACPI: PCI interrupt for device 0000:02:00.0 disabled
> ---
> > PCI: Setting latency timer of device 0000:02:00.0 to 64
> > eth0: Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:13:72:7b:2a:f0
> > eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> > eth0: dma_rwctrl[76180000] dma_mask[64-bit]
> 401a391,392
> > tg3: eth0: Link is up at 100 Mbps, full duplex.
> > tg3: eth0: Flow control is on for TX and on for RX.
>
>
>
>
> Thanks,
> Jeff
>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
@ 2006-11-07 16:56 Jeff Chua
0 siblings, 0 replies; 30+ messages in thread
From: Jeff Chua @ 2006-11-07 16:56 UTC (permalink / raw)
To: Aaron Durbin
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general, Andi Kleen, linux-ide,
Linus Torvalds, oprofile-list, Jens Axboe, Martin Lorenz,
linux-pci, Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman
On 11/7/06, Aaron Durbin <adurbin@google.com> wrote:
> Could please you post a dump of /proc/iomem for both the kernel that
> works for you and the kernel that fails to allocate the PCI resources?
1) this works ...
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc800-000cffff : Adapter ROM
000f0000-000fffff : System ROM
00100000-df686bff : System RAM
00100000-00357d27 : Kernel code
00357d28-0042bab3 : Kernel data
df686c00-df688bff : ACPI Non-volatile Storage
df688c00-df68abff : ACPI Tables
df68ac00-dfffffff : reserved
e0000000-efffffff : 0000:00:02.0
f0000000-f3ffffff : reserved
fe700000-fe7fffff : PCI Bus #03
fe800000-fe8fffff : PCI Bus #02
fe8f0000-fe8fffff : 0000:02:00.0
fe8f0000-fe8fffff : tg3
fe900000-fe9fffff : PCI Bus #01
feabf900-feabf9ff : 0000:00:1e.2
feabfa00-feabfbff : 0000:00:1e.2
feac0000-feafffff : 0000:00:02.0
feb00000-feb7ffff : 0000:00:02.0
feb80000-febfffff : 0000:00:02.1
fed00000-fed003ff : HPET 0
fed20000-fed9ffff : reserved
fee00000-feefffff : reserved
ffa80800-ffa80bff : 0000:00:1d.7
ffa80800-ffa80bff : ehci_hcd
ffb00000-ffffffff : reserved
2) this fails ...
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc800-000cffff : Adapter ROM
000f0000-000fffff : System ROM
00100000-df686bff : System RAM
00100000-00358927 : Kernel code
00358928-0042cab3 : Kernel data
df686c00-df688bff : ACPI Non-volatile Storage
df688c00-df68abff : ACPI Tables
df68ac00-dfffffff : reserved
e0000000-efffffff : 0000:00:02.0
f0000000-ffffffff : PCI MMCONFIG 0
fed00000-fed003ff : HPET 0
Thanks,
Jeff
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
@ 2006-11-07 16:57 Jeff Chua
2006-11-07 17:11 ` Aaron Durbin
2006-11-07 17:11 ` Matthew Wilcox
0 siblings, 2 replies; 30+ messages in thread
From: Jeff Chua @ 2006-11-07 16:57 UTC (permalink / raw)
To: Aaron Durbin
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general, Andi Kleen, linux-ide,
Linus Torvalds, oprofile-list, Jens Axboe, Martin Lorenz,
linux-pci, Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman
On 11/7/06, Aaron Durbin <adurbin@google.com> wrote:
> Could please you post a dump of /proc/iomem for both the kernel that
> works for you and the kernel that fails to allocate the PCI resources?
1) this works ...
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc800-000cffff : Adapter ROM
000f0000-000fffff : System ROM
00100000-df686bff : System RAM
00100000-00357d27 : Kernel code
00357d28-0042bab3 : Kernel data
df686c00-df688bff : ACPI Non-volatile Storage
df688c00-df68abff : ACPI Tables
df68ac00-dfffffff : reserved
e0000000-efffffff : 0000:00:02.0
f0000000-f3ffffff : reserved
fe700000-fe7fffff : PCI Bus #03
fe800000-fe8fffff : PCI Bus #02
fe8f0000-fe8fffff : 0000:02:00.0
fe8f0000-fe8fffff : tg3
fe900000-fe9fffff : PCI Bus #01
feabf900-feabf9ff : 0000:00:1e.2
feabfa00-feabfbff : 0000:00:1e.2
feac0000-feafffff : 0000:00:02.0
feb00000-feb7ffff : 0000:00:02.0
feb80000-febfffff : 0000:00:02.1
fed00000-fed003ff : HPET 0
fed20000-fed9ffff : reserved
fee00000-feefffff : reserved
ffa80800-ffa80bff : 0000:00:1d.7
ffa80800-ffa80bff : ehci_hcd
ffb00000-ffffffff : reserved
2) this fails ...
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc800-000cffff : Adapter ROM
000f0000-000fffff : System ROM
00100000-df686bff : System RAM
00100000-00358927 : Kernel code
00358928-0042cab3 : Kernel data
df686c00-df688bff : ACPI Non-volatile Storage
df688c00-df68abff : ACPI Tables
df68ac00-dfffffff : reserved
e0000000-efffffff : 0000:00:02.0
f0000000-ffffffff : PCI MMCONFIG 0
fed00000-fed003ff : HPET 0
Thanks,
Jeff
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 16:57 Jeff Chua
@ 2006-11-07 17:11 ` Aaron Durbin
2006-11-07 17:11 ` Matthew Wilcox
1 sibling, 0 replies; 30+ messages in thread
From: Aaron Durbin @ 2006-11-07 17:11 UTC (permalink / raw)
To: Jeff Chua
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Christian, Alex Romosan, openib-general, Andi Kleen, linux-ide,
Linus Torvalds, oprofile-list, Jens Axboe, Martin Lorenz,
linux-pci, Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman
On 11/7/06, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>
> On 11/7/06, Aaron Durbin <adurbin@google.com> wrote:
>
> > Could please you post a dump of /proc/iomem for both the kernel that
> > works for you and the kernel that fails to allocate the PCI resources?
>
>
>
> 1) this works ...
>
> 00000000-0009ffff : System RAM
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000cc800-000cffff : Adapter ROM
> 000f0000-000fffff : System ROM
> 00100000-df686bff : System RAM
> 00100000-00357d27 : Kernel code
> 00357d28-0042bab3 : Kernel data
> df686c00-df688bff : ACPI Non-volatile Storage
> df688c00-df68abff : ACPI Tables
> df68ac00-dfffffff : reserved
> e0000000-efffffff : 0000:00:02.0
> f0000000-f3ffffff : reserved
> fe700000-fe7fffff : PCI Bus #03
> fe800000-fe8fffff : PCI Bus #02
> fe8f0000-fe8fffff : 0000:02:00.0
> fe8f0000-fe8fffff : tg3
> fe900000-fe9fffff : PCI Bus #01
> feabf900-feabf9ff : 0000:00:1e.2
> feabfa00-feabfbff : 0000:00:1e.2
> feac0000-feafffff : 0000:00:02.0
> feb00000-feb7ffff : 0000:00:02.0
> feb80000-febfffff : 0000:00:02.1
> fed00000-fed003ff : HPET 0
> fed20000-fed9ffff : reserved
> fee00000-feefffff : reserved
> ffa80800-ffa80bff : 0000:00:1d.7
> ffa80800-ffa80bff : ehci_hcd
> ffb00000-ffffffff : reserved
>
>
>
> 2) this fails ...
>
> 00000000-0009ffff : System RAM
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000cc800-000cffff : Adapter ROM
> 000f0000-000fffff : System ROM
> 00100000-df686bff : System RAM
> 00100000-00358927 : Kernel code
> 00358928-0042cab3 : Kernel data
> df686c00-df688bff : ACPI Non-volatile Storage
> df688c00-df68abff : ACPI Tables
> df68ac00-dfffffff : reserved
> e0000000-efffffff : 0000:00:02.0
> f0000000-ffffffff : PCI MMCONFIG 0
> fed00000-fed003ff : HPET 0
>
Ok. Jeff I have patch in there that reserves the MMCONFIG space,
however it is marked as reserved during resource insertion. For some
reason your MMCONFIG space is being reported as very large, thus
reserving the range f0000000-ffffffff. That is why your PCI devices
are bombing out on resource allocation. It looks like the MMCONFIG
region should be:
f0000000-f3ffffff. This range is marked as reserved in your e820 map,
however the MMCONFIG parsing is thinking it is 256MB.
This is not the right answer, but you could patch up your kernel to
fix it to the correct size for a temporary fix. I am going to see if
I can parse any other information from your logs and see if I can come
up w/ a better solution.
I just wanted to point you and others in the right direction.
-Aaron
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 16:57 Jeff Chua
2006-11-07 17:11 ` Aaron Durbin
@ 2006-11-07 17:11 ` Matthew Wilcox
2006-11-07 17:49 ` Eric W. Biederman
` (2 more replies)
1 sibling, 3 replies; 30+ messages in thread
From: Matthew Wilcox @ 2006-11-07 17:11 UTC (permalink / raw)
To: Jeff Chua
Cc: Andrew Morton, len.brown, Komuro, linux-pm, Ernst Herzberg,
Aaron Durbin, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, Martin Lorenz, linux-pci,
Elimar Riesebieter, discuss, Thierry Vignaud, Tim Chen, phil.el,
gregkh, Andi Kleen, Christian, Adrian Bunk, linux-acpi, mingo,
nfs, Eric
On Wed, Nov 08, 2006 at 12:57:03AM +0800, Jeff Chua wrote:
> 2) this fails ...
>
> e0000000-efffffff : 0000:00:02.0
> f0000000-ffffffff : PCI MMCONFIG 0
> fed00000-fed003ff : HPET 0
Heh, no kidding ...
num_buses = pci_mmcfg_config[i].end_bus_number -
pci_mmcfg_config[i].start_bus_number + 1;
res->start = pci_mmcfg_config[i].base_address;
res->end = res->start + (num_buses << 20) - 1;
res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
insert_resource(&iomem_resource, res);
So if we have 256 busses assigned, then we request 256MB and, well,
there's no room for anyone else. This code was added by Andi in commit
de09bddb9d6f96785be470c832b881e6d72d589f
Hopefully he'll have a good idea how to restrict it. Given your "working"
resource map, it seems like it should be limited to 16MB (and thus 16 busses).
But how to figure that out?
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 17:11 ` Matthew Wilcox
@ 2006-11-07 17:49 ` Eric W. Biederman
2006-11-07 17:50 ` Aaron Durbin
2006-11-08 7:39 ` Andi Kleen
2 siblings, 0 replies; 30+ messages in thread
From: Eric W. Biederman @ 2006-11-07 17:49 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general,
Andi Kleen, linux-ide, Linus Torvalds, oprofile-list, Jens Axboe,
Adrian Bunk, linux-pci, Elimar Riesebieter, discuss, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb, Christian,
Linux Kernel Mailing List, linux-acpi, mingo, nfs
Matthew Wilcox <matthew@wil.cx> writes:
> On Wed, Nov 08, 2006 at 12:57:03AM +0800, Jeff Chua wrote:
>> 2) this fails ...
>>
>> e0000000-efffffff : 0000:00:02.0
>> f0000000-ffffffff : PCI MMCONFIG 0
>> fed00000-fed003ff : HPET 0
>
> Heh, no kidding ...
>
> num_buses = pci_mmcfg_config[i].end_bus_number -
> pci_mmcfg_config[i].start_bus_number + 1;
> res->start = pci_mmcfg_config[i].base_address;
> res->end = res->start + (num_buses << 20) - 1;
> res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> insert_resource(&iomem_resource, res);
>
> So if we have 256 busses assigned, then we request 256MB and, well,
> there's no room for anyone else. This code was added by Andi in commit
> de09bddb9d6f96785be470c832b881e6d72d589f
>
> Hopefully he'll have a good idea how to restrict it. Given your "working"
> resource map, it seems like it should be limited to 16MB (and thus 16 busses).
> But how to figure that out?
Sounds like you need to find the current maximum bus number in use.
A little more sophisticated would look at where the next reserved region begins.
ACPI might have some of that information as well. Although I'm not certain
where we you are coming from.
If you don't have to worry about device hotplug getting the current maximum bus
number should be all you need.
Eric
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 17:11 ` Matthew Wilcox
2006-11-07 17:49 ` Eric W. Biederman
@ 2006-11-07 17:50 ` Aaron Durbin
2006-11-07 17:56 ` Matthew Wilcox
2006-11-08 15:14 ` Andi Kleen
2006-11-08 7:39 ` Andi Kleen
2 siblings, 2 replies; 30+ messages in thread
From: Aaron Durbin @ 2006-11-07 17:50 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, linux-pci, Elimar Riesebieter, discuss,
Komuro, Jeff Chua, Tim Chen, phil.el, cpufreq, gregkh, neilb,
Adrian Bunk, linux-acpi, mingo, nfs, Eric
On 11/7/06, Matthew Wilcox <matthew@wil.cx> wrote:
> On Wed, Nov 08, 2006 at 12:57:03AM +0800, Jeff Chua wrote:
> > 2) this fails ...
> >
> > e0000000-efffffff : 0000:00:02.0
> > f0000000-ffffffff : PCI MMCONFIG 0
> > fed00000-fed003ff : HPET 0
>
> Heh, no kidding ...
>
> num_buses = pci_mmcfg_config[i].end_bus_number -
> pci_mmcfg_config[i].start_bus_number + 1;
> res->start = pci_mmcfg_config[i].base_address;
> res->end = res->start + (num_buses << 20) - 1;
> res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> insert_resource(&iomem_resource, res);
>
> So if we have 256 busses assigned, then we request 256MB and, well,
> there's no room for anyone else. This code was added by Andi in commit
> de09bddb9d6f96785be470c832b881e6d72d589f
>
> Hopefully he'll have a good idea how to restrict it. Given your "working"
> resource map, it seems like it should be limited to 16MB (and thus 16 busses).
> But how to figure that out?
>
Maybe Andi can shed some light on the reasoning for not checking e820
to see if the entire MMCONFIG region is reported as reserved in the
e820 map. I can patch up the pci_mmcfg_insert_resource to verify if
the region that is exported by ACPI is reserved in e820 and printk an
error message if it is not and skip the resource insertion.
Does that seem like a good avenue to pursue?
-Aaron
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 17:50 ` Aaron Durbin
@ 2006-11-07 17:56 ` Matthew Wilcox
2006-11-08 15:14 ` Andi Kleen
1 sibling, 0 replies; 30+ messages in thread
From: Matthew Wilcox @ 2006-11-07 17:56 UTC (permalink / raw)
To: Aaron Durbin
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, Linus Torvalds,
oprofile-list, Jens Axboe, linux-pci, Elimar Riesebieter, discuss,
Komuro, Jeff Chua, Tim Chen, phil.el, cpufreq, gregkh, neilb,
Adrian Bunk, linux-acpi, mingo, nfs, Eric
On Tue, Nov 07, 2006 at 09:50:54AM -0800, Aaron Durbin wrote:
> Maybe Andi can shed some light on the reasoning for not checking e820
> to see if the entire MMCONFIG region is reported as reserved in the
> e820 map. I can patch up the pci_mmcfg_insert_resource to verify if
> the region that is exported by ACPI is reserved in e820 and printk an
> error message if it is not and skip the resource insertion.
>
> Does that seem like a good avenue to pursue?
Sounds much better than Eric's idea of maximum bus number currently in
use (which was also my first thought).
But rather than skipping the resource insertion, I believe you should
limit its size to the largest multiple of 1MB that will fit within the
reserved region.
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 5:41 ` Len Brown
@ 2006-11-07 20:05 ` Ernst Herzberg
0 siblings, 0 replies; 30+ messages in thread
From: Ernst Herzberg @ 2006-11-07 20:05 UTC (permalink / raw)
To: Len Brown
Cc: Andrew Morton, Thierry Vignaud, discuss,
Linux Kernel Mailing List, Alex Romosan, openib-general, ak,
linux-ide, Linus Torvalds, oprofile-list, Jens Axboe,
Martin Lorenz, Bryan O'Sullivan, Elimar Riesebieter, linux-pm,
Michael S. Tsirkin, Komuro, Jeff Chua, phil.el, gregkh, linux-pm,
neilb, Adrian Bunk, linux-acpi, mingo, nfs, Eric W. Biederman,
cpu
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>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 17:11 ` Matthew Wilcox
2006-11-07 17:49 ` Eric W. Biederman
2006-11-07 17:50 ` Aaron Durbin
@ 2006-11-08 7:39 ` Andi Kleen
2006-11-08 12:22 ` Matthew Wilcox
2 siblings, 1 reply; 30+ messages in thread
From: Andi Kleen @ 2006-11-08 7:39 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general, neilb,
linux-ide, Linus Torvalds, oprofile-list, Jens Axboe, linux-pci,
Elimar Riesebieter, discuss, Komuro, Jeff Chua, Tim Chen, phil.el,
gregkh, Linux Kernel Mailing List, Christian, Adrian Bunk,
linux-acpi, mingo, nfs, Eric
On Tuesday 07 November 2006 18:11, Matthew Wilcox wrote:
> On Wed, Nov 08, 2006 at 12:57:03AM +0800, Jeff Chua wrote:
> > 2) this fails ...
> >
> > e0000000-efffffff : 0000:00:02.0
> > f0000000-ffffffff : PCI MMCONFIG 0
> > fed00000-fed003ff : HPET 0
>
> Heh, no kidding ...
>
> num_buses = pci_mmcfg_config[i].end_bus_number -
> pci_mmcfg_config[i].start_bus_number + 1;
> res->start = pci_mmcfg_config[i].base_address;
> res->end = res->start + (num_buses << 20) - 1;
> res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> insert_resource(&iomem_resource, res);
>
> So if we have 256 busses assigned, then we request 256MB and, well,
> there's no room for anyone else. This code was added by Andi in commit
> de09bddb9d6f96785be470c832b881e6d72d589f
>
> Hopefully he'll have a good idea how to restrict it. Given your "working"
> resource map, it seems like it should be limited to 16MB (and thus 16
> busses). But how to figure that out?
ACPI knows the number of busses.
Just need to get the information there, which is a ordering issue
(normally MCFG initialization is before this is known I think)
Len, ACPI folks, any ideas how to fix this cleanly?
-Andi
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 7:39 ` Andi Kleen
@ 2006-11-08 12:22 ` Matthew Wilcox
2006-11-08 16:05 ` Linus Torvalds
0 siblings, 1 reply; 30+ messages in thread
From: Matthew Wilcox @ 2006-11-08 12:22 UTC (permalink / raw)
To: Andi Kleen
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general, neilb,
linux-ide, Linus Torvalds, oprofile-list, Jens Axboe, linux-pci,
Elimar Riesebieter, discuss, Komuro, Jeff Chua, Tim Chen, phil.el,
gregkh, Linux Kernel Mailing List, Christian, Adrian Bunk,
linux-acpi, mingo, nfs, Eric
On Wed, Nov 08, 2006 at 08:39:44AM +0100, Andi Kleen wrote:
> ACPI knows the number of busses.
But what if the number of busses increases later, eg by hotplugging
a card with a PCI-PCI bridge on it? Or does it know the number of
busses which can be supported by this machine's MMCONFIG region?
If so, why isn't this information reported in the MCFG table properly
instead of claiming to support 0-255?
> Just need to get the information there, which is a ordering issue
> (normally MCFG initialization is before this is known I think)
>
> Len, ACPI folks, any ideas how to fix this cleanly?
>
> -Andi
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-07 17:50 ` Aaron Durbin
2006-11-07 17:56 ` Matthew Wilcox
@ 2006-11-08 15:14 ` Andi Kleen
1 sibling, 0 replies; 30+ messages in thread
From: Andi Kleen @ 2006-11-08 15:14 UTC (permalink / raw)
To: discuss
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general, neilb,
linux-ide, Linus Torvalds, oprofile-list, Jens Axboe, linux-pci,
Elimar Riesebieter, linux-pm, Komuro, Jeff Chua, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Christian,
Adrian Bunk, linux-acpi, mingo, nfs
> I can patch up the pci_mmcfg_insert_resource to verify if
> the region that is exported by ACPI is reserved in e820 and printk an
> error message if it is not and skip the resource insertion.
It probably should get its information from pci_mcfg_init()
and only reserve what is used there instead of adding duplicate
e820 checking code somewhere else.
Or perhaps only reserve when the bus is discovered?
-Andi
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 12:22 ` Matthew Wilcox
@ 2006-11-08 16:05 ` Linus Torvalds
2006-11-08 17:38 ` Eric W. Biederman
0 siblings, 1 reply; 30+ messages in thread
From: Linus Torvalds @ 2006-11-08 16:05 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Andrew Morton, len.brown, Thierry Vignaud, linux-pm,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, oprofile-list, Jens Axboe,
Martin Lorenz, linux-pci, Elimar Riesebieter, discuss, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, Andi Kleen, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman
On Wed, 8 Nov 2006, Matthew Wilcox wrote:
>
> On Wed, Nov 08, 2006 at 08:39:44AM +0100, Andi Kleen wrote:
> > ACPI knows the number of busses.
>
> But what if the number of busses increases later, eg by hotplugging
> a card with a PCI-PCI bridge on it? Or does it know the number of
> busses which can be supported by this machine's MMCONFIG region?
ACPI will give the maximum number.
However, in this case, the correct thing to do (always _has_ been) is to
not use ACPI for _anything_, but just read the base and the size of the
MMCONFIG region from the hardware itself.
Anyway, I do not consider this a regression. MMCONFIG has _never_ worked
reliably. It has always been a case of "we can make it work on some
machines by making it break on others".
Linus
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 16:05 ` Linus Torvalds
@ 2006-11-08 17:38 ` Eric W. Biederman
2006-11-08 18:52 ` Linus Torvalds
0 siblings, 1 reply; 30+ messages in thread
From: Eric W. Biederman @ 2006-11-08 17:38 UTC (permalink / raw)
To: Linus Torvalds
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general,
Andi Kleen, linux-ide, oprofile-list, Jens Axboe, Adrian Bunk,
linux-pci, Elimar Riesebieter, discuss, linux-pm, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Linux Kernel Mailing List, linux-acpi, mingo, nfs, cpufreq
Linus Torvalds <torvalds@osdl.org> writes:
> On Wed, 8 Nov 2006, Matthew Wilcox wrote:
>>
>> On Wed, Nov 08, 2006 at 08:39:44AM +0100, Andi Kleen wrote:
>> > ACPI knows the number of busses.
>>
>> But what if the number of busses increases later, eg by hotplugging
>> a card with a PCI-PCI bridge on it? Or does it know the number of
>> busses which can be supported by this machine's MMCONFIG region?
>
> ACPI will give the maximum number.
>
> However, in this case, the correct thing to do (always _has_ been) is to
> not use ACPI for _anything_, but just read the base and the size of the
> MMCONFIG region from the hardware itself.
>
> Anyway, I do not consider this a regression. MMCONFIG has _never_ worked
> reliably. It has always been a case of "we can make it work on some
> machines by making it break on others".
The implementations I have seen, I believe have all been on bridges and
the maximum size is actually generated from the bus number below the bridge.
Eric
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 17:38 ` Eric W. Biederman
@ 2006-11-08 18:52 ` Linus Torvalds
2006-11-08 19:10 ` Aaron Durbin
2006-11-08 19:24 ` Eric W. Biederman
0 siblings, 2 replies; 30+ messages in thread
From: Linus Torvalds @ 2006-11-08 18:52 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general,
Andi Kleen, linux-ide, oprofile-list, Jens Axboe, Adrian Bunk,
linux-pci, Elimar Riesebieter, discuss, linux-pm, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Linux Kernel Mailing List, linux-acpi, mingo, nfs, cpufreq
On Wed, 8 Nov 2006, Eric W. Biederman wrote:
>
> The implementations I have seen, I believe have all been on bridges and
> the maximum size is actually generated from the bus number below the bridge.
Hmm. It might be possible to first set up the MMCONFIG thing for the
minimum range, then read the bus numbers from the host bridge on that bus,
and then expand the mmconfig range if necessary.
Because pretty much ANYTHING is better than trusting the BIOS tables.
That said, I'd really be a _lot_ more confident about it if we were to be
able to read the values from the hardware itself some way. There's
obviously a chicken-and-egg issue on mmcfg configuration, but it's one
that the BIOS startup code also has, so I assume that there is a solution
to that somewhere.
Linus
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 18:52 ` Linus Torvalds
@ 2006-11-08 19:10 ` Aaron Durbin
2006-11-08 19:25 ` Linus Torvalds
2006-11-08 19:24 ` Eric W. Biederman
1 sibling, 1 reply; 30+ messages in thread
From: Aaron Durbin @ 2006-11-08 19:10 UTC (permalink / raw)
To: Linus Torvalds
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, oprofile-list, Jens Axboe,
linux-pci, Elimar Riesebieter, discuss, linux-pm, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman, cpufre
On 11/8/06, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Wed, 8 Nov 2006, Eric W. Biederman wrote:
> >
> > The implementations I have seen, I believe have all been on bridges and
> > the maximum size is actually generated from the bus number below the bridge.
>
> Hmm. It might be possible to first set up the MMCONFIG thing for the
> minimum range, then read the bus numbers from the host bridge on that bus,
> and then expand the mmconfig range if necessary.
>
> Because pretty much ANYTHING is better than trusting the BIOS tables.
>
> That said, I'd really be a _lot_ more confident about it if we were to be
> able to read the values from the hardware itself some way. There's
> obviously a chicken-and-egg issue on mmcfg configuration, but it's one
> that the BIOS startup code also has, so I assume that there is a solution
> to that somewhere.
>
I agree that the orignal patch was stupid in relying on the MCFG table reported
in ACPI, however, like you said, without the actual knowledge of the MCFG
region being pulled out of the hardware even the e820 check is not valid. It is
close, but not entirely correct. For instance, if the MCFG region is being
reported in ACPI land as 256 buses and the e820 has a reservation at the
MCFG base address of 18MB that does not necessarily mean the MCFG region allows
for PCI config access on 18 buses. It could be that it only allows 16 buses w/
another piece of hardware on that last 2MB.
So what is the proper scenario? One needs to know the actual upper limit of
MCFG region. Otherwise when detecting unreachable devices one could be poking
something else in the process of trying to discover these unreachable devices.
I am open to ideas and am willing to rework some of the code, but I do like the
idea of having the region being reported in the resource table.
-Aaron
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 18:52 ` Linus Torvalds
2006-11-08 19:10 ` Aaron Durbin
@ 2006-11-08 19:24 ` Eric W. Biederman
2006-11-10 6:52 ` Andi Kleen
1 sibling, 1 reply; 30+ messages in thread
From: Eric W. Biederman @ 2006-11-08 19:24 UTC (permalink / raw)
To: Linus Torvalds
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general,
Andi Kleen, linux-ide, oprofile-list, Jens Axboe, Adrian Bunk,
linux-pci, Elimar Riesebieter, discuss, linux-pm, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb,
Linux Kernel Mailing List, linux-acpi, mingo, nfs, cpufreq
Linus Torvalds <torvalds@osdl.org> writes:
> On Wed, 8 Nov 2006, Eric W. Biederman wrote:
>>
>> The implementations I have seen, I believe have all been on bridges and
>> the maximum size is actually generated from the bus number below the bridge.
>
> Hmm. It might be possible to first set up the MMCONFIG thing for the
> minimum range, then read the bus numbers from the host bridge on that bus,
> and then expand the mmconfig range if necessary.
>
> Because pretty much ANYTHING is better than trusting the BIOS tables.
>
> That said, I'd really be a _lot_ more confident about it if we were to be
> able to read the values from the hardware itself some way. There's
> obviously a chicken-and-egg issue on mmcfg configuration, but it's one
> that the BIOS startup code also has, so I assume that there is a solution
> to that somewhere.
cfc and cf8 still work on x86. So you can start with the old path
and then when you know mmconfig works you can upgrade.
In fact mmconfig doesn't necessary allow access to the entire pci domain.
On AMD systems currently you will get all of the subordinate busses but
the cpus themselves will not show up in the mmconfig space.
So we should have the infrastructure to only use mmconfig for some set
of busses. If that interface is well described we can probably
bootstrap sanely, only enabling what we know exists and like wise
only reserving what we know is used.
For chipsets I know that there is quite a bit of information publicly
available. For intel chipsets I believe those are registers they
make available in their public docs. For things like the Nvidia
chipset the knowledge should be in the publicly available linuxbios
code base.
Hopefully that is enough of a pointer to get people going. I might
have enough time to write the patch but I don't have enough time to
maintain it until mmconfig becomes boring.
Eric
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 19:10 ` Aaron Durbin
@ 2006-11-08 19:25 ` Linus Torvalds
0 siblings, 0 replies; 30+ messages in thread
From: Linus Torvalds @ 2006-11-08 19:25 UTC (permalink / raw)
To: Aaron Durbin
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Christian, Alex Romosan, openib-general,
Linux Kernel Mailing List, linux-ide, oprofile-list, Jens Axboe,
linux-pci, Elimar Riesebieter, discuss, linux-pm, Komuro,
Jeff Chua, Tim Chen, phil.el, gregkh, neilb, Adrian Bunk,
linux-acpi, mingo, nfs, Eric W. Biederman, cpufre
On Wed, 8 Nov 2006, Aaron Durbin wrote:
>
> For instance, if the MCFG region is being reported in ACPI land as 256
> buses and the e820 has a reservation at the MCFG base address of 18MB
> that does not necessarily mean the MCFG region allows for PCI config
> access on 18 buses. It could be that it only allows 16 buses w/ another
> piece of hardware on that last 2MB.
Oh, I agree. You'd _hope_ that the BIOS reports that as a separate region,
and we could use that as a hint, but it's never going to be fool-proof.
It's just much much better to try to figure out what the hardware itself
thinks it is doing, rather than relying on a firmware engineer filling out
the table to match what he _thinks_ the hardware is doing (or, more
accurately, randomly scribbling values until Windows boots, at which point
it's not his problem any more, and people ship the crap).
Some misguided people used to think that we shouldn't do our own PCI
probing, but use ACPI instead. This is the same thing, except on a smaller
scale. MAYBE the scale ends up being so small that we can figure out some
reliable way without actually asking the hardware itself, but I kind of
doubt it. Especially judging by the current situation.
> So what is the proper scenario? One needs to know the actual upper limit of
> MCFG region. Otherwise when detecting unreachable devices one could be poking
> something else in the process of trying to discover these unreachable devices.
> I am open to ideas and am willing to rework some of the code, but I do like
> the idea of having the region being reported in the resource table.
Absolutely. I'd _love_ to have the region reported in the resource table.
It's just that right now it doesn't seem practical, since the downsides
are bigger than the upsides (and the upsides aren't _that_ big, since we
require the thing to be marked reserved in the e820 tables anyway, so the
resource tables do know about it, about as well as they currently can).
In the absense of a way to actually ask the hardware, we could perhaps
modify the thing so that it does request the regions in the resource
table, but _only_ if the e820 entries aren't there (ie the "config type 1
didn't even work" case).
Alternatively, we might choose to request just the known smallest region,
because that should be relatively "safer". It's better than not reporting
the regions at all, and while it's not perfect, it at least shouldn't have
huge potential downsides from getting the size totally wrong...
Hmm?
Linus
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
2006-11-08 19:24 ` Eric W. Biederman
@ 2006-11-10 6:52 ` Andi Kleen
0 siblings, 0 replies; 30+ messages in thread
From: Andi Kleen @ 2006-11-10 6:52 UTC (permalink / raw)
To: discuss
Cc: Andrew Morton, len.brown, Thierry Vignaud, Matthew Wilcox,
Ernst Herzberg, Aaron Durbin, Alex Romosan, openib-general, neilb,
linux-ide, Linus Torvalds, oprofile-list, Jens Axboe, linux-pci,
Elimar Riesebieter, linux-pm, Komuro, Jeff Chua, Tim Chen,
phil.el, gregkh, Linux Kernel Mailing List, Christian,
Adrian Bunk, linux-acpi, mingo, nfs
> So we should have the infrastructure to only use mmconfig for some set
> of busses. If that interface is well described we can probably
> bootstrap sanely, only enabling what we know exists and like wise
> only reserving what we know is used.
Unfortunately there is a chicken and egg problem on those few broken
systems (like some x86 Macs) where only mcfg works. Without mcfg you
won't be able to probe the bus. Ok you could trust ACPI when it says
it's there, but I'm not sure Linus would like that.
Still perhaps I guess only reserving when the bus is probed is probably
a good idea. In most cases we only probe a small number of busses
because ACPI tells us the number.
This basically means pci_mcfg_init() should be split up.
-Andi
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2006-11-10 6:52 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
2006-10-31 20:11 ` Greg KH
2006-10-31 20:12 ` Arjan van de Ven
2006-11-03 2:41 ` Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
2006-11-05 9:30 ` Jeff Chua
2006-11-06 17:47 ` [discuss] " Andi Kleen
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 5:41 ` Len Brown
2006-11-07 20:05 ` Ernst Herzberg
2006-11-07 13:30 ` 2.6.19-rc4: known unfixed regressions (v4) Adrian Bunk
2006-11-06 22:40 [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3) Jeff Chua
2006-11-07 15:50 ` Aaron Durbin
-- strict thread matches above, loose matches on Subject: below --
2006-11-07 16:56 Jeff Chua
2006-11-07 16:57 Jeff Chua
2006-11-07 17:11 ` Aaron Durbin
2006-11-07 17:11 ` Matthew Wilcox
2006-11-07 17:49 ` Eric W. Biederman
2006-11-07 17:50 ` Aaron Durbin
2006-11-07 17:56 ` Matthew Wilcox
2006-11-08 15:14 ` Andi Kleen
2006-11-08 7:39 ` Andi Kleen
2006-11-08 12:22 ` Matthew Wilcox
2006-11-08 16:05 ` Linus Torvalds
2006-11-08 17:38 ` Eric W. Biederman
2006-11-08 18:52 ` Linus Torvalds
2006-11-08 19:10 ` Aaron Durbin
2006-11-08 19:25 ` Linus Torvalds
2006-11-08 19:24 ` Eric W. Biederman
2006-11-10 6:52 ` Andi Kleen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).