netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-20  4:51 David Witbrodt
  2008-08-20  5:21 ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-20  4:51 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Yinghai Lu, linux-kernel, Paul E. McKenney, Peter Zijlstra,
	Thomas Gleixner, H. Peter Anvin, netdev



> > $ dmesg | grep -i hpet
> > ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
> > ACPI: HPET id: 0x10b9a201 base: 0xfed00000
> > hpet clockevent registered
> > hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
> > hpet0: 4 32-bit timers, 14318180 Hz
> > hpet_resources: 0xfed00000 is busy
> 
> btw., you might also want to look into drivers/char/hpet.c and 
> instrument that a bit. In particular the ioremap()s done there will show 
> exactly how the hpet is mapped.

Well, I exhausted about 80% of the list of experiments I put together
on Saturday, but I still can't make a 2.6.2[67] kernel boot without
"hpet=disable" or reverting commits 3def3d6d... and 1e934dda...

I spent so many hours on this today...  My head is spinning, and I'm
afraid springs and smoke will start emanating from my hard drive soon
from all the recompiling and rebooting!

I need to warn you all:  I discovered today, for the first time, that
I am not the first user to report this bug.  This guy got bit by it
back in May, at version 2.6.26-rc2:

[blog] http://ciaranm.wordpress.com/tag/f-i90hd/
[LKML] http://www.uwsg.indiana.edu/hypermail/linux/kernel/0805.2/0746.html

He has different hardware from mine, so when 2.6.26 starts hitting the 
distros you may see a flood of complaints -- and I came to LKML partly
with the purpose of providing a bug fix patch (or, less preferably, a
reversion patch) for Debian, my distro of choice.

I am not giving up.  I _did_ look at drivers/char/hpet.c as requested,
but since this code did not change before and after 3def3d6d..., I
was not sure what to look for that would be harmful.  The same turned out
to be true about the "connection" I found between HPET and the calls
of insert_resource(), though this could actually be affected if my latest
hypothesis pans out.  (All of my ideas have failed so far, though, so it
will not surprise me if my new idea fails as well.)

I found another item in arch/x86/kernel/acpi/boot.c -- which I suspect
_is_ a bug -- but which had no effect on my lockup issue when I "fixed" 
it.  I will let a guru decide if I have found anything important:

===== BEGIN DIFF ==========================
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 2cdc9de..d5a9d9d 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -669,7 +669,7 @@ static int __init acpi_parse_hpet(struct acpi_table_header *table)
 
     memset(hpet_res, 0, sizeof(*hpet_res));
     hpet_res->name = (void *)&hpet_res[1];
-    hpet_res->flags = IORESOURCE_MEM;
+    hpet_res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
     snprintf((char *)hpet_res->name, HPET_RESOURCE_NAME_SIZE, "HPET %u",
          hpet_tbl->sequence);
===== END DIFF ==========================

The dynamically-allocated structure that hpet_res points to eventually gets
added to the resource tree by 

static __init int hpet_insert_resource(void);

which calls insert_resource().  My thought is that we are supposed to be 
marking the memory region as unavailable, so that nothing else will touch 
it later, right?


Anyway, what happened in 3def3d6d to cause the regression?  I have a new 
hypothesis to test, but I'm too tired to continue right now -- so I'll hit 
it again tomorrow before I go to work:

Up until now, I have focused on the fact that request_resource() was 
replaced by insert_resource().  I did not pay attention to another aspect 
of that commit -- the large change in the order of execution of where the
kernel memory regions are added to the resource list.

The original (2.6.25) approach, which works on my machine, is to identify 
RAM resources as they are added to the resource list, then tack on the 
kernel memory regions to the (proper) resource as it is added to the tree:

  for (...) {
    [...]
    if (e820.map[i].type == E820_RAM) {
        request_resource(res, code_resource);
        request_resource(res, data_resource);
        request_resource(res, bss_resource);
    [...]
    }
    insert_resource(&iomem_resource, res);
  }

The problem commit moves those 3 request_resource() calls out of
e820_reserve_resources() [arch/x86/kernel/e820{,_64}.c] and into
setup_arch() [arch/x86/kernel/setup{,_64}.c].  The original code
would have this happen when setup_arch() directly callse
820_reserve_resources(), but the commit moved those lines into 
setup_arch() itself, and they run sooner now than before...
potentially affecting any resources added afterward.

I don't see what effect this reordering could possibly have, since
insert_resource() ignores the IORESOURCE_BUSY flag.  But that
commit changed SOMETHING... and the two most obvious changes are 
the {request,insert}_resource() switch, and the repositioning of 
the request_resource() calls for {code,data,bss}_resource.


I did a LOT of testing of insert_resource() last weekend, and it
completely checked out:  it was only called about a dozen times,
and it always inserted the resource without returning errors or
accessing code paths for special cases.  That function is not
broken internally, though its proper functioning might have
unintended side effects I have not understood yet.

I had the idea of setting up a side-by-side test -- taking the
two versions of e820_reserve_resources() from before and after
3def3d6d, renaming them, and writing a tiny replacement of
e820_reserve_resources() which would call both versions... with
the idea that I could recurse the resulting trees and compare 
their contents for differences.

While reading drivers/char/hpet.c and looking at the functions
used there, I discovered request_region(), and realized that it
would be difficult to compare the entire iomem_resource tree to
a dummy tree only containing resources added by insert_resource()
and request_resource().  It might be simpler to have my tiny
e820_reserve_resources() replacement add each resource to 3 trees
-- the real iomem_resource tree, and 2 dummy trees -- which could
then be compared for differences just before the kernel locks up.


Thanks,
Dave W.

/* head hits pillow */

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  4:51 David Witbrodt
@ 2008-08-20  5:21 ` Yinghai Lu
  2008-08-20  7:51   ` Bill Fink
  0 siblings, 1 reply; 41+ messages in thread
From: Yinghai Lu @ 2008-08-20  5:21 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, linux-kernel, Paul E. McKenney, Peter Zijlstra,
	Thomas Gleixner, H. Peter Anvin, netdev

On Tue, Aug 19, 2008 at 9:51 PM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
>
>> > $ dmesg | grep -i hpet
>> > ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
>> > ACPI: HPET id: 0x10b9a201 base: 0xfed00000
>> > hpet clockevent registered
>> > hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
>> > hpet0: 4 32-bit timers, 14318180 Hz
>> > hpet_resources: 0xfed00000 is busy
>>
>> btw., you might also want to look into drivers/char/hpet.c and
>> instrument that a bit. In particular the ioremap()s done there will show
>> exactly how the hpet is mapped.
>
> Well, I exhausted about 80% of the list of experiments I put together
> on Saturday, but I still can't make a 2.6.2[67] kernel boot without
> "hpet=disable" or reverting commits 3def3d6d... and 1e934dda...
>
> I spent so many hours on this today...  My head is spinning, and I'm
> afraid springs and smoke will start emanating from my hard drive soon
> from all the recompiling and rebooting!
>
> I need to warn you all:  I discovered today, for the first time, that
> I am not the first user to report this bug.  This guy got bit by it
> back in May, at version 2.6.26-rc2:
>
> [blog] http://ciaranm.wordpress.com/tag/f-i90hd/
> [LKML] http://www.uwsg.indiana.edu/hypermail/linux/kernel/0805.2/0746.html
>
> He has different hardware from mine, so when 2.6.26 starts hitting the
> distros you may see a flood of complaints -- and I came to LKML partly
> with the purpose of providing a bug fix patch (or, less preferably, a
> reversion patch) for Debian, my distro of choice.
>
> I am not giving up.  I _did_ look at drivers/char/hpet.c as requested,
> but since this code did not change before and after 3def3d6d..., I
> was not sure what to look for that would be harmful.  The same turned out
> to be true about the "connection" I found between HPET and the calls
> of insert_resource(), though this could actually be affected if my latest
> hypothesis pans out.  (All of my ideas have failed so far, though, so it
> will not surprise me if my new idea fails as well.)
>
> I found another item in arch/x86/kernel/acpi/boot.c -- which I suspect
> _is_ a bug -- but which had no effect on my lockup issue when I "fixed"
> it.  I will let a guru decide if I have found anything important:
>
> ===== BEGIN DIFF ==========================
> diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
> index 2cdc9de..d5a9d9d 100644
> --- a/arch/x86/kernel/acpi/boot.c
> +++ b/arch/x86/kernel/acpi/boot.c
> @@ -669,7 +669,7 @@ static int __init acpi_parse_hpet(struct acpi_table_header *table)
>
>     memset(hpet_res, 0, sizeof(*hpet_res));
>     hpet_res->name = (void *)&hpet_res[1];
> -    hpet_res->flags = IORESOURCE_MEM;
> +    hpet_res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
>     snprintf((char *)hpet_res->name, HPET_RESOURCE_NAME_SIZE, "HPET %u",
>          hpet_tbl->sequence);
> ===== END DIFF ==========================
>
> The dynamically-allocated structure that hpet_res points to eventually gets
> added to the resource tree by
>
> static __init int hpet_insert_resource(void);
>
> which calls insert_resource().  My thought is that we are supposed to be
> marking the memory region as unavailable, so that nothing else will touch
> it later, right?
>
>
> Anyway, what happened in 3def3d6d to cause the regression?  I have a new
> hypothesis to test, but I'm too tired to continue right now -- so I'll hit
> it again tomorrow before I go to work:
>
> Up until now, I have focused on the fact that request_resource() was
> replaced by insert_resource().  I did not pay attention to another aspect
> of that commit -- the large change in the order of execution of where the
> kernel memory regions are added to the resource list.
>
> The original (2.6.25) approach, which works on my machine, is to identify
> RAM resources as they are added to the resource list, then tack on the
> kernel memory regions to the (proper) resource as it is added to the tree:
>
>  for (...) {
>    [...]
>    if (e820.map[i].type == E820_RAM) {
>        request_resource(res, code_resource);
>        request_resource(res, data_resource);
>        request_resource(res, bss_resource);
>    [...]
>    }
>    insert_resource(&iomem_resource, res);
>  }
>
> The problem commit moves those 3 request_resource() calls out of
> e820_reserve_resources() [arch/x86/kernel/e820{,_64}.c] and into
> setup_arch() [arch/x86/kernel/setup{,_64}.c].  The original code
> would have this happen when setup_arch() directly callse
> 820_reserve_resources(), but the commit moved those lines into
> setup_arch() itself, and they run sooner now than before...
> potentially affecting any resources added afterward.
>
> I don't see what effect this reordering could possibly have, since
> insert_resource() ignores the IORESOURCE_BUSY flag.  But that
> commit changed SOMETHING... and the two most obvious changes are
> the {request,insert}_resource() switch, and the repositioning of
> the request_resource() calls for {code,data,bss}_resource.
>
>
> I did a LOT of testing of insert_resource() last weekend, and it
> completely checked out:  it was only called about a dozen times,
> and it always inserted the resource without returning errors or
> accessing code paths for special cases.  That function is not
> broken internally, though its proper functioning might have
> unintended side effects I have not understood yet.
>
> I had the idea of setting up a side-by-side test -- taking the
> two versions of e820_reserve_resources() from before and after
> 3def3d6d, renaming them, and writing a tiny replacement of
> e820_reserve_resources() which would call both versions... with
> the idea that I could recurse the resulting trees and compare
> their contents for differences.
>
> While reading drivers/char/hpet.c and looking at the functions
> used there, I discovered request_region(), and realized that it
> would be difficult to compare the entire iomem_resource tree to
> a dummy tree only containing resources added by insert_resource()
> and request_resource().  It might be simpler to have my tiny
> e820_reserve_resources() replacement add each resource to 3 trees
> -- the real iomem_resource tree, and 2 dummy trees -- which could
> then be compared for differences just before the kernel locks up.
>

with reverting patch that change insert_resource to request_resource...
2.6.26 or 2.6.27-rcX still hange somewhere.

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  5:21 ` Yinghai Lu
@ 2008-08-20  7:51   ` Bill Fink
  2008-08-20  8:02     ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: Bill Fink @ 2008-08-20  7:51 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: David Witbrodt, Ingo Molnar, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev

On Tue, 19 Aug 2008, Yinghai Lu wrote:

> On Tue, Aug 19, 2008 at 9:51 PM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
> > While reading drivers/char/hpet.c and looking at the functions
> > used there, I discovered request_region(), and realized that it
> > would be difficult to compare the entire iomem_resource tree to
> > a dummy tree only containing resources added by insert_resource()
> > and request_resource().  It might be simpler to have my tiny
> > e820_reserve_resources() replacement add each resource to 3 trees
> > -- the real iomem_resource tree, and 2 dummy trees -- which could
> > then be compared for differences just before the kernel locks up.
> 
> with reverting patch that change insert_resource to request_resource...
> 2.6.26 or 2.6.27-rcX still hange somewhere.

This is true if he reverted just the 3def3d6d... commit, but if he
also reverts the similar, and immediately following, 1e934dda...
commit, then his 2.6.26 kernel runs fine.

						-Bill

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  7:51   ` Bill Fink
@ 2008-08-20  8:02     ` Yinghai Lu
  2008-08-20  9:15       ` Ingo Molnar
  0 siblings, 1 reply; 41+ messages in thread
From: Yinghai Lu @ 2008-08-20  8:02 UTC (permalink / raw)
  To: Bill Fink
  Cc: David Witbrodt, Ingo Molnar, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev

On Wed, Aug 20, 2008 at 12:51 AM, Bill Fink <billfink@mindspring.com> wrote:
> On Tue, 19 Aug 2008, Yinghai Lu wrote:
>
>> On Tue, Aug 19, 2008 at 9:51 PM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>> > While reading drivers/char/hpet.c and looking at the functions
>> > used there, I discovered request_region(), and realized that it
>> > would be difficult to compare the entire iomem_resource tree to
>> > a dummy tree only containing resources added by insert_resource()
>> > and request_resource().  It might be simpler to have my tiny
>> > e820_reserve_resources() replacement add each resource to 3 trees
>> > -- the real iomem_resource tree, and 2 dummy trees -- which could
>> > then be compared for differences just before the kernel locks up.
>>
>> with reverting patch that change insert_resource to request_resource...
>> 2.6.26 or 2.6.27-rcX still hange somewhere.
>
> This is true if he reverted just the 3def3d6d... commit, but if he
> also reverts the similar, and immediately following, 1e934dda...
> commit, then his 2.6.26 kernel runs fine.

interesting,

David, can you try only comment out

late_initcall(lapic_insert_resource);

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  8:02     ` Yinghai Lu
@ 2008-08-20  9:15       ` Ingo Molnar
  2008-08-20  9:31         ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: Ingo Molnar @ 2008-08-20  9:15 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Bill Fink, David Witbrodt, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev


* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

> > This is true if he reverted just the 3def3d6d... commit, but if he 
> > also reverts the similar, and immediately following, 1e934dda... 
> > commit, then his 2.6.26 kernel runs fine.
> 
> interesting,
> 
> David, can you try only comment out
> 
> late_initcall(lapic_insert_resource);

i.e. the patch below?

what's your theory, what could be the reason for David's lockups?

	Ingo

--------------->
Index: linux/arch/x86/kernel/apic_32.c
===================================================================
--- linux.orig/arch/x86/kernel/apic_32.c
+++ linux/arch/x86/kernel/apic_32.c
@@ -1740,4 +1740,4 @@ static int __init lapic_insert_resource(
  * need call insert after e820_reserve_resources()
  * that is using request_resource
  */
-late_initcall(lapic_insert_resource);
+//late_initcall(lapic_insert_resource);
Index: linux/arch/x86/kernel/apic_64.c
===================================================================
--- linux.orig/arch/x86/kernel/apic_64.c
+++ linux/arch/x86/kernel/apic_64.c
@@ -1614,4 +1614,4 @@ static int __init lapic_insert_resource(
  * need call insert after e820_reserve_resources()
  * that is using request_resource
  */
-late_initcall(lapic_insert_resource);
+//late_initcall(lapic_insert_resource);


^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  9:15       ` Ingo Molnar
@ 2008-08-20  9:31         ` Yinghai Lu
  2008-08-20  9:36           ` Ingo Molnar
  0 siblings, 1 reply; 41+ messages in thread
From: Yinghai Lu @ 2008-08-20  9:31 UTC (permalink / raw)
  To: Ingo Molnar, Vivek Goyal
  Cc: Bill Fink, David Witbrodt, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev

On Wed, Aug 20, 2008 at 2:15 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>
>> > This is true if he reverted just the 3def3d6d... commit, but if he
>> > also reverts the similar, and immediately following, 1e934dda...
>> > commit, then his 2.6.26 kernel runs fine.
>>
>> interesting,
>>
>> David, can you try only comment out
>>
>> late_initcall(lapic_insert_resource);
>
> i.e. the patch below?
>
> what's your theory, what could be the reason for David's lockups?

could be insert_resource related.
1. revert patch that change back insert_resource doesn't work
2. insert_resource for lapic address moved to late after ....

need to add debug printout for insert_resource/request_resource to
make sure thing going well

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20  9:31         ` Yinghai Lu
@ 2008-08-20  9:36           ` Ingo Molnar
  0 siblings, 0 replies; 41+ messages in thread
From: Ingo Molnar @ 2008-08-20  9:36 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Vivek Goyal, Bill Fink, David Witbrodt, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev


* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

> On Wed, Aug 20, 2008 at 2:15 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> >
> >> > This is true if he reverted just the 3def3d6d... commit, but if he
> >> > also reverts the similar, and immediately following, 1e934dda...
> >> > commit, then his 2.6.26 kernel runs fine.
> >>
> >> interesting,
> >>
> >> David, can you try only comment out
> >>
> >> late_initcall(lapic_insert_resource);
> >
> > i.e. the patch below?
> >
> > what's your theory, what could be the reason for David's lockups?
> 
> could be insert_resource related.
> 1. revert patch that change back insert_resource doesn't work
> 2. insert_resource for lapic address moved to late after ....
> 
> need to add debug printout for insert_resource/request_resource to 
> make sure thing going well

but what can happen if it does not "go well"? The resource list is 
basically there to make sure we dont overlap resources. But is there a 
real danger here for any overlap?

And insert_resource() differs from request_resource() in that 
insert_resource() allows "complete overlap". David has done printks of 
all resources in this thread - can you see anything suspicious in there?

and what's the connection to your e820 patches?

	Ingo

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-20 14:08 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-20 14:08 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, linux-kernel, Paul E. McKenney, Peter Zijlstra,
	Thomas Gleixner, H. Peter Anvin, netdev



> > This is true if he reverted just the 3def3d6d... commit, but if he
> > also reverts the similar, and immediately following, 1e934dda...
> > commit, then his 2.6.26 kernel runs fine.
> 
> interesting,
> 
> David, can you try only comment out
> 
> late_initcall(lapic_insert_resource);

Results with v2.6.27-rc3:  hangs in the same way, at the same place;
works with "hpet=disable".


I wondered whether changes since before v2.6.26-rc1 might interfere
with your intention here, so I checked out 1e934dda... and tried
again.

Results with 1e934dda...:  hangs, just like above.


Bill is right:  reverting the changes in 3def3d6d alone will not work 
on my hardware unless I also revert 1e934dda.

I have not (yet) attempted to bring those reverts forward to v2.6.27*
because I have been trying to identify the breakage that 3def3d6d
causes (and because I don't know the right git-fu to apply to my branch
to apply the post-v2.6.26 commits :(  ).


The other user who reported problems said that reverting3def3d6d alone
worked for him.  (I have asked him for more info on his blog, hoping he 
can tell us more... if there is more for him to tell.)  His kernel was 
NOT hanging in the same place as mine:

- mine hangs in inet_init(), after a series of calls that ends with
the hang at synchronize_rcu().

- his hangs (somewhere) inide_scan_pcibus().
[http://www.uwsg.indiana.edu/hypermail/linux/kernel/0805.2/1082.html]

He has a bug report (http://marc.info/?l=linux-kernel&m=121107133101187&w=2)
which lists his hardware as "Abit F-190HD motherboard with a Q6600 CPU".

My hardware -- 2 machines with the same regression -- is quite different:

"fileserver":  ECS AMD690GM-M2 mboard with AMD Athlon X2 4850e
"webserver":  ECS AMD690GM-M2 mboard with AMD Athlon 64 X2 3600+


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-20 14:32 David Witbrodt
  2008-08-20 14:49 ` Ingo Molnar
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-20 14:32 UTC (permalink / raw)
  To: Ingo Molnar, Yinghai Lu
  Cc: Bill Fink, linux-kernel, Paul E. McKenney, Peter Zijlstra,
	Thomas Gleixner, H. Peter Anvin, netdev



> > > This is true if he reverted just the 3def3d6d... commit, but if he 
> > > also reverts the similar, and immediately following, 1e934dda... 
> > > commit, then his 2.6.26 kernel runs fine.
> > 
> > interesting,
> > 
> > David, can you try only comment out
> > 
> > late_initcall(lapic_insert_resource);
> 
> i.e. the patch below?
> 
> what's your theory, what could be the reason for David's lockups?
> 
>     Ingo
> 
> --------------->
> Index: linux/arch/x86/kernel/apic_32.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/apic_32.c
> +++ linux/arch/x86/kernel/apic_32.c
> @@ -1740,4 +1740,4 @@ static int __init lapic_insert_resource(
>   * need call insert after e820_reserve_resources()
>   * that is using request_resource
>   */
> -late_initcall(lapic_insert_resource);
> +//late_initcall(lapic_insert_resource);
> Index: linux/arch/x86/kernel/apic_64.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/apic_64.c
> +++ linux/arch/x86/kernel/apic_64.c
> @@ -1614,4 +1614,4 @@ static int __init lapic_insert_resource(
>   * need call insert after e820_reserve_resources()
>   * that is using request_resource
>   */
> -late_initcall(lapic_insert_resource);
> +//late_initcall(lapic_insert_resource);


Brain Damage Alert:  I have only been experimenting with files for
64-bit architecture -- like e820_64.c, e820_64.h, setup_64.c, apic_64.c
-- and not their 32-bit counterparts.  The 3def3d6d commit only touched
64-bit files (before they merged with the 32-bit versions later).

I'm sure that is correct, but can you folks verify that?  A file like
apic_32.c (in Ingo's patch above) cannot affect me if I am running a
64-bit architecture, right?

Running this sanity check:
$ make  arch/x86/kernel/apic_32.o

just gives me loads of errors, presumably because of my .config settings:
============
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_X86_64_SMP=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_RESOURCES_64BIT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
[...]
============

Sorry for my confusion,
Dave W.

PS:  Why didn't anyone tell me for 2 weeks that I was breaking standard
operating procedure by changing the subject line frequently?  Now I'm
in trouble with the bosses, you bums!  ;)

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20 14:32 David Witbrodt
@ 2008-08-20 14:49 ` Ingo Molnar
  0 siblings, 0 replies; 41+ messages in thread
From: Ingo Molnar @ 2008-08-20 14:49 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Bill Fink, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev


* David Witbrodt <dawitbro@sbcglobal.net> wrote:

> I'm sure that is correct, but can you folks verify that?  A file like 
> apic_32.c (in Ingo's patch above) cannot affect me if I am running a 
> 64-bit architecture, right?

correct - i just commented out from both 32-bit and the 64-bit side to 
have a complete patch. (if someone else who runs a 32-bit kernel picks 
it up for experimentation it will do a similar thing)

	Ingo

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-20 16:44 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-20 16:44 UTC (permalink / raw)
  To: Ingo Molnar, Yinghai Lu
  Cc: Vivek Goyal, Bill Fink, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev



> > >> > This is true if he reverted just the 3def3d6d... commit, but if he
> > >> > also reverts the similar, and immediately following, 1e934dda...
> > >> > commit, then his 2.6.26 kernel runs fine.
> > >>
> > >> interesting,
> > >>
> > >> David, can you try only comment out
> > >>
> > >> late_initcall(lapic_insert_resource);
> > >
> > > i.e. the patch below?
> > >
> > > what's your theory, what could be the reason for David's lockups?
> > 
> > could be insert_resource related.
> > 1. revert patch that change back insert_resource doesn't work
> > 2. insert_resource for lapic address moved to late after ....
> > 
> > need to add debug printout for insert_resource/request_resource to 
> > make sure thing going well
> 
> but what can happen if it does not "go well"? The resource list is 
> basically there to make sure we dont overlap resources. But is there a 
> real danger here for any overlap?
> 
> And insert_resource() differs from request_resource() in that 
> insert_resource() allows "complete overlap". David has done printks of 
> all resources in this thread - can you see anything suspicious in there?


Clarification:  the resource-related outputs I have posted here so far
have been either from kernels without the regression (2.6.25 series, or
the v2.6.26 kernel with 2 reverts) or kernels _with_ the regression but
made to boot with "hpet=disable".  Those outputs were 'cat /proc/iomem'.

Any other output I have posted here, involving insertion of printk's to
see diagnostic data just before the lockups, has not included resource-
related information.  This is for two reasons:

1.  It is hard to fit the entire contents of the iomem_resource tree on
the little 80x25 VGA screen!

2.  The data I do get has to be hand-transcribed, decreasing the 
reliability a lot.

3.  It results mostly from my own personal experiments, trying to
understand what the kernel code is doing and what it is supposed to be
doing.  You folks already know those things, so I assumed that most of
the data I produced would be irrelevant -- and when I asked if anyone
wanted to see it, there were no replies.


I fought on Monday with the idea of producing the equivalent of
'cat /proc/iomem', but on a hanging kernel just before it hangs.  The
output format suffered as I tried to squeeze it all on one 80x25
screen, but I _did_ succeed:

===== BEGIN OUTPUT ===================
Number of resources handled by insert_resource(): 12
       0-ffffffffffffffff       PCI mem        0-9f3ff               System RAM
   9f400-9ffff                 reserved    f0000-fffff                 reserved
  100000-77fdffff            System RAM   200000-56ff31             kernel code
  56ff32-6d8fff             kernel data   76a000-7ac907              kernel bss
77fe0000-77fe2fff          ACPI non-vol 77fe3000-77feffff           ACPI Tables
77ff0000-77ffffff              reserved 78000000-7fffffff             pnp 00:0d
80000000-800003ff          0000:00:14.0 d8000000-dfffffff          PCI Bus 0000
d8000000-dfffffff          0000:01:05.0 e0000000-efffffff              reserved
fdc00000-fdcfffff          PCI Bus 0000 fdcff000-fcdff0ff          0000:02:05.0
fdd00000-fdefffff          PCI Bus 0000 fdd00000-fddfffff          0000:01:05.0
fdee0000-fdeeffff          0000:01:05.0 fdefc000-fdefffff          0000:01:05.2
fdf00000-fdffffff          PCI Bus 0000 fdf00000-fdf1ffff          0000:02:05.0
fe020000-fe023fff          0000:00:14.2 fe029000-fe0290ff          0000:00:13.5
fe02a000-fe02afff          0000:00:13.4 fe02b000-fe02bfff          0000:00:13.3
fe02c000-fe02cfff          0000:00:13.2 fe02d000-fe02dfff          0000:00:13.1
fe02e000-fe02efff          0000:00:13.0 fe02f000-fe02feff          0000:00:12.0
fec00000-ffffffff              reserved
===== END OUTPUT ===================

Please beware that my recursion follows 'struct resource *' children first,
then siblings only after the entire child subtree is exhausted.

The only resource names that I see truncated are the "PCI Bus 0000" entries,
but those can be matched with the 'cat /proc/iomem' data I posted earlier;
the address ranges are similar to those of a working kernel:

===== v2.6.25 NON-REGRESSION KERNEL OUTPUT =====
$ cat /proc/iomem
00000000-0009f3ff : System RAM
0009f400-0009ffff : reserved
000f0000-000fffff : reserved
00100000-77fdffff : System RAM
  00200000-0056ca21 : Kernel code
  0056ca22-006ce3d7 : Kernel data
  00753000-0079a3c7 : Kernel bss
77fe0000-77fe2fff : ACPI Non-volatile Storage
77fe3000-77feffff : ACPI Tables
77ff0000-77ffffff : reserved
78000000-7fffffff : pnp 00:0d
d8000000-dfffffff : PCI Bus #01
  d8000000-dfffffff : 0000:01:05.0
    d8000000-d8ffffff : uvesafb
e0000000-efffffff : PCI MMCONFIG 0
  e0000000-efffffff : reserved
fdc00000-fdcfffff : PCI Bus #02
  fdcff000-fdcff0ff : 0000:02:05.0
    fdcff000-fdcff0ff : r8169
fdd00000-fdefffff : PCI Bus #01
  fdd00000-fddfffff : 0000:01:05.0
  fdee0000-fdeeffff : 0000:01:05.0
  fdefc000-fdefffff : 0000:01:05.2
    fdefc000-fdefffff : ICH HD audio
fdf00000-fdffffff : PCI Bus #02
fe020000-fe023fff : 0000:00:14.2
  fe020000-fe023fff : ICH HD audio
fe029000-fe0290ff : 0000:00:13.5
  fe029000-fe0290ff : ehci_hcd
fe02a000-fe02afff : 0000:00:13.4
  fe02a000-fe02afff : ohci_hcd
fe02b000-fe02bfff : 0000:00:13.3
  fe02b000-fe02bfff : ohci_hcd
fe02c000-fe02cfff : 0000:00:13.2
  fe02c000-fe02cfff : ohci_hcd
fe02d000-fe02dfff : 0000:00:13.1
  fe02d000-fe02dfff : ohci_hcd
fe02e000-fe02efff : 0000:00:13.0
  fe02e000-fe02efff : ohci_hcd
fe02f000-fe02f3ff : 0000:00:12.0
  fe02f000-fe02f3ff : ahci
fec00000-fec00fff : IOAPIC 0
  fec00000-fec00fff : pnp 00:0d
fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0
fee00000-fee00fff : Local APIC
fff80000-fffeffff : pnp 00:0d
ffff0000-ffffffff : pnp 00:0d
===============================================

I see now that much is missing in the hanging kernel's output.  It may be
hanging before all the resources are added.

[I have a dual core CPU.  If the missing things are already supposed to be 
there at this point, when inet_init() is running, could one core be hung 
while the other core runs inet_init() until it hits synchronize_rcu()?  
I'm sure my question is silly:  I don't even know whether a SMP kernel 
boots in SMP mode, or when it switches to SMP if it doesn't start that 
way!]


The screenful of 80x25 output above was produced with the following code:
=========================================================================
diff --git a/kernel/resource.c b/kernel/resource.c
index f5b518e..d2c62d6 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -375,11 +375,16 @@ EXPORT_SYMBOL(allocate_resource);
  * resource is inserted and the conflicting resources become children of
  * the new resource.
  */
+
+extern unsigned dw_count;
+
 int insert_resource(struct resource *parent, struct resource *new)
 {
     int result;
     struct resource *first, *next;
 
+    static unsigned int num_calls = 0;
+
     write_lock(&resource_lock);
 
     for (;; parent = first) {
@@ -394,16 +399,19 @@ int insert_resource(struct resource *parent, struct resource *new)
 
         if ((first->start > new->start) || (first->end < new->end))
             break;
+
         if ((first->start == new->start) && (first->end == new->end))
             break;
     }
 
     for (next = first; ; next = next->sibling) {
         /* Partial overlap? Bad, and unfixable */
-        if (next->start < new->start || next->end > new->end)
+            if (next->start < new->start || next->end > new->end)
             goto out;
+
         if (!next->sibling)
             break;
+
         if (next->sibling->start > new->end)
             break;
     }
@@ -429,6 +437,9 @@ int insert_resource(struct resource *parent, struct resource *new)
 
  out:
     write_unlock(&resource_lock);
+
+    dw_count = ++num_calls;
+
     return result;
 }
 
diff --git a/net/core/dev.c b/net/core/dev.c
index 600bb23..b6f57c2 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -127,6 +127,8 @@
 #include <linux/jhash.h>
 #include <linux/random.h>
 
+#include <linux/ioport.h>
+
 #include "net-sysfs.h"
 
 /*
@@ -4304,9 +4306,29 @@ void free_netdev(struct net_device *dev)
     put_device(&dev->dev);
 }
 
+unsigned dw_count;
+
+void dw_print_res (struct resource *r)
+{
+        printk ("%9llx-%-16llx%14.12s", r->start, r->end, r->name);
+}
+
+void dw_recurse_res (struct resource *r)
+{
+        if (!r) return;
+
+    dw_print_res (r);
+    dw_recurse_res (r->child);
+    dw_recurse_res (r->sibling);
+}
+
 /* Synchronize with packet receive processing. */
 void synchronize_net(void)
 {
     might_sleep();
+
+    printk ("Number of resources handled by insert_resource(): %u\n", dw_count);
+    dw_recurse_res (&iomem_resource);
+
     synchronize_rcu();
 }
=========================================================================


HTH,
Dave W.

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-20 17:42 David Witbrodt
  2008-08-20 17:58 ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-20 17:42 UTC (permalink / raw)
  To: Ingo Molnar, Yinghai Lu
  Cc: Vivek Goyal, Bill Fink, linux-kernel, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev


*** FINALLY FOUND THE EXACT PROBLEM ***

I woke up this morning with a new idea.  I wish I had thought of this
TWO WEEKS AGO!

Commit 3def3d6d essentially involves 2 different changes:

1.  request_resource () is replaced by insert_resource()

2.  code to add {code,data,bss}_resource to the iomem_resource tree
is moved out of e820_reserve_resources() and into setup_arch()
directly.  [The actual call of e820_reserve_resources() is also
located in setup_arch().]


Since this is 2 separate changes, I went back to 700efc1b, just
before the commit introducing the regression (3def3d6d).

When I applied change #2 alone, and GOT A WORKING KERNEL!
===== BEGIN DIFF ================
diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
index a8694a3..e452bea 100644
--- a/arch/x86/kernel/e820_64.c
+++ b/arch/x86/kernel/e820_64.c
@@ -229,8 +229,7 @@ unsigned long __init e820_end_of_ram(void)
 /*
  * Mark e820 reserved areas as busy for the resource manager.
  */
-void __init e820_reserve_resources(struct resource *code_resource,
-        struct resource *data_resource, struct resource *bss_resource)
+void __init e820_reserve_resources(void)
 {
     int i;
     for (i = 0; i < e820.nr_map; i++) {
@@ -246,20 +245,6 @@ void __init e820_reserve_resources(struct resource *code_resource,
         res->end = res->start + e820.map[i].size - 1;
         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
         request_resource(&iomem_resource, res);
-        if (e820.map[i].type == E820_RAM) {
-            /*
-             * We don't know which RAM region contains kernel data,
-             * so we try it repeatedly and let the resource manager
-             * test it.
-             */
-            request_resource(res, code_resource);
-            request_resource(res, data_resource);
-            request_resource(res, bss_resource);
-#ifdef CONFIG_KEXEC
-            if (crashk_res.start != crashk_res.end)
-                request_resource(res, &crashk_res);
-#endif
-        }
     }
 }
 
diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c
index 187f084..a0584ac 100644
--- a/arch/x86/kernel/setup_64.c
+++ b/arch/x86/kernel/setup_64.c
@@ -322,6 +322,11 @@ void __init setup_arch(char **cmdline_p)
 
     finish_e820_parsing();
 
+    /* after parse_early_param, so could debug it */
+    insert_resource(&iomem_resource, &code_resource);
+    insert_resource(&iomem_resource, &data_resource);
+    insert_resource(&iomem_resource, &bss_resource);
+
     early_gart_iommu_check();
 
     e820_register_active_regions(0, 0, -1UL);
@@ -454,7 +459,7 @@ void __init setup_arch(char **cmdline_p)
     /*
      * We trust e820 completely. No explicit ROM probing in memory.
      */
-    e820_reserve_resources(&code_resource, &data_resource, &bss_resource);
+    e820_reserve_resources();
     e820_mark_nosave_regions();
 
     /* request I/O space for devices used on all i[345]86 PCs */
diff --git a/include/asm-x86/e820_64.h b/include/asm-x86/e820_64.h
index 9e06c6e..ef653a4 100644
--- a/include/asm-x86/e820_64.h
+++ b/include/asm-x86/e820_64.h
@@ -23,8 +23,7 @@ extern void update_memory_range(u64 start, u64 size, unsigned old_type,
 extern void setup_memory_region(void);
 extern void contig_e820_setup(void); 
 extern unsigned long e820_end_of_ram(void);
-extern void e820_reserve_resources(struct resource *code_resource,
-        struct resource *data_resource, struct resource *bss_resource);
+extern void e820_reserve_resources(void);
 extern void e820_mark_nosave_regions(void);
 extern int e820_any_mapped(unsigned long start, unsigned long end, unsigned type);
 extern int e820_all_mapped(unsigned long start, unsigned long end, unsigned type);
===== END DIFF ================


As a separate experiment, I started over with a clean version of
700efc1b, then introduced the change from request_resource() to
insert_resource():
===== BEGIN DIFF ================
diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
index a8694a3..988195d 100644
--- a/arch/x86/kernel/e820_64.c
+++ b/arch/x86/kernel/e820_64.c
@@ -245,7 +245,7 @@ void __init e820_reserve_resources(struct resource *code_resource,
         res->start = e820.map[i].addr;
         res->end = res->start + e820.map[i].size - 1;
         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
-        request_resource(&iomem_resource, res);
+        insert_resource(&iomem_resource, res);
         if (e820.map[i].type == E820_RAM) {
             /*
              * We don't know which RAM region contains kernel data,
===== END DIFF ================

The kernel produced from the change HANGS!


I am very late for work, but just couldn't leave home until I posted
these results.  My conclusion is that, somehow, the reordering of
adding {code,data,bss}_resource to the iomem_resource tree is doing
funky things to certain people's machines!


HTH!!!
Dave W.

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20 17:42 David Witbrodt
@ 2008-08-20 17:58 ` Yinghai Lu
  2008-08-21  2:02   ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: Yinghai Lu @ 2008-08-20 17:58 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Wed, Aug 20, 2008 at 10:42 AM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
> *** FINALLY FOUND THE EXACT PROBLEM ***
>
> I woke up this morning with a new idea.  I wish I had thought of this
> TWO WEEKS AGO!
>
> Commit 3def3d6d essentially involves 2 different changes:
>
> 1.  request_resource () is replaced by insert_resource()
>
> 2.  code to add {code,data,bss}_resource to the iomem_resource tree
> is moved out of e820_reserve_resources() and into setup_arch()
> directly.  [The actual call of e820_reserve_resources() is also
> located in setup_arch().]
>
>
> Since this is 2 separate changes, I went back to 700efc1b, just
> before the commit introducing the regression (3def3d6d).
>
> When I applied change #2 alone, and GOT A WORKING KERNEL!
> ===== BEGIN DIFF ================
> diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
> index a8694a3..e452bea 100644
> --- a/arch/x86/kernel/e820_64.c
> +++ b/arch/x86/kernel/e820_64.c
> @@ -229,8 +229,7 @@ unsigned long __init e820_end_of_ram(void)
>  /*
>  * Mark e820 reserved areas as busy for the resource manager.
>  */
> -void __init e820_reserve_resources(struct resource *code_resource,
> -        struct resource *data_resource, struct resource *bss_resource)
> +void __init e820_reserve_resources(void)
>  {
>     int i;
>     for (i = 0; i < e820.nr_map; i++) {
> @@ -246,20 +245,6 @@ void __init e820_reserve_resources(struct resource *code_resource,
>         res->end = res->start + e820.map[i].size - 1;
>         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
>         request_resource(&iomem_resource, res);
> -        if (e820.map[i].type == E820_RAM) {
> -            /*
> -             * We don't know which RAM region contains kernel data,
> -             * so we try it repeatedly and let the resource manager
> -             * test it.
> -             */
> -            request_resource(res, code_resource);
> -            request_resource(res, data_resource);
> -            request_resource(res, bss_resource);
> -#ifdef CONFIG_KEXEC
> -            if (crashk_res.start != crashk_res.end)
> -                request_resource(res, &crashk_res);
> -#endif
> -        }
>     }
>  }
>
> diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c
> index 187f084..a0584ac 100644
> --- a/arch/x86/kernel/setup_64.c
> +++ b/arch/x86/kernel/setup_64.c
> @@ -322,6 +322,11 @@ void __init setup_arch(char **cmdline_p)
>
>     finish_e820_parsing();
>
> +    /* after parse_early_param, so could debug it */
> +    insert_resource(&iomem_resource, &code_resource);
> +    insert_resource(&iomem_resource, &data_resource);
> +    insert_resource(&iomem_resource, &bss_resource);
> +
>     early_gart_iommu_check();
>
>     e820_register_active_regions(0, 0, -1UL);
> @@ -454,7 +459,7 @@ void __init setup_arch(char **cmdline_p)
>     /*
>      * We trust e820 completely. No explicit ROM probing in memory.
>      */
> -    e820_reserve_resources(&code_resource, &data_resource, &bss_resource);
> +    e820_reserve_resources();
>     e820_mark_nosave_regions();
>
>     /* request I/O space for devices used on all i[345]86 PCs */
> diff --git a/include/asm-x86/e820_64.h b/include/asm-x86/e820_64.h
> index 9e06c6e..ef653a4 100644
> --- a/include/asm-x86/e820_64.h
> +++ b/include/asm-x86/e820_64.h
> @@ -23,8 +23,7 @@ extern void update_memory_range(u64 start, u64 size, unsigned old_type,
>  extern void setup_memory_region(void);
>  extern void contig_e820_setup(void);
>  extern unsigned long e820_end_of_ram(void);
> -extern void e820_reserve_resources(struct resource *code_resource,
> -        struct resource *data_resource, struct resource *bss_resource);
> +extern void e820_reserve_resources(void);
>  extern void e820_mark_nosave_regions(void);
>  extern int e820_any_mapped(unsigned long start, unsigned long end, unsigned type);
>  extern int e820_all_mapped(unsigned long start, unsigned long end, unsigned type);
> ===== END DIFF ================
>
>
> As a separate experiment, I started over with a clean version of
> 700efc1b, then introduced the change from request_resource() to
> insert_resource():
> ===== BEGIN DIFF ================
> diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
> index a8694a3..988195d 100644
> --- a/arch/x86/kernel/e820_64.c
> +++ b/arch/x86/kernel/e820_64.c
> @@ -245,7 +245,7 @@ void __init e820_reserve_resources(struct resource *code_resource,
>         res->start = e820.map[i].addr;
>         res->end = res->start + e820.map[i].size - 1;
>         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> -        request_resource(&iomem_resource, res);
> +        insert_resource(&iomem_resource, res);
>         if (e820.map[i].type == E820_RAM) {
>             /*
>              * We don't know which RAM region contains kernel data,
> ===== END DIFF ================
>
> The kernel produced from the change HANGS!

because code/data/bss/crashk is inserted at first

in e820_reserve_resource if you call request_resource instead of
insert_resource. the entries from e820 tables that has conflict to
entries already added will not show in
resource list /proc/iomem.

please send out /proc/iomem when it happens to boot.

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-20 17:58 ` Yinghai Lu
@ 2008-08-21  2:02   ` Yinghai Lu
  0 siblings, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-21  2:02 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]

please apply attached patch to see if insert_resource/request resource
works on your conf

YH

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: insert_resource_debug.patch --]
[-- Type: text/x-patch; name=insert_resource_debug.patch, Size: 2227 bytes --]

Index: linux-2.6/kernel/resource.c
===================================================================
--- linux-2.6.orig/kernel/resource.c
+++ linux-2.6/kernel/resource.c
@@ -201,6 +201,7 @@ int request_resource(struct resource *ro
 	write_lock(&resource_lock);
 	conflict = __request_resource(root, new);
 	write_unlock(&resource_lock);
+	printk(KERN_DEBUG "request_resource: root: (%s) [%llx, %llx], new: (%s) [%llx, %llx] conflict %d\n", root->name, root->start, root->end, new->name, new->start, new->end, !!conflict);
 	return conflict ? -EBUSY : 0;
 }
 
@@ -382,16 +383,20 @@ int insert_resource(struct resource *par
 
 	write_lock(&resource_lock);
 
+	printk(KERN_DEBUG "insert_resource: parent: (%s) [%llx, %llx], new: (%s) [%llx, %llx]\n", parent->name, parent->start, parent->end, new->name, new->start, new->end);
 	for (;; parent = first) {
 	 	result = 0;
 		first = __request_resource(parent, new);
-		if (!first)
+		if (!first) {
+			printk(KERN_DEBUG "    insert_resource: good with request direct parent: (%s) [%llx, %llx], new: (%s) [%llx, %llx]\n", parent->name, parent->start, parent->end, new->name, new->start, new->end);
 			goto out;
+		}
 
 		result = -EBUSY;
 		if (first == parent)
 			goto out;
 
+		printk(KERN_DEBUG "  insert_resource: first: (%s) [%llx, %llx], new: (%s) [%llx, %llx]\n", first->name, first->start, first->end, new->name, new->start, new->end);
 		if ((first->start > new->start) || (first->end < new->end))
 			break;
 		if ((first->start == new->start) && (first->end == new->end))
@@ -413,10 +418,13 @@ int insert_resource(struct resource *par
 	new->parent = parent;
 	new->sibling = next->sibling;
 	new->child = first;
+	printk(KERN_DEBUG "  insert_resource: direct parent: (%s) [%llx, %llx], new: (%s) [%llx, %llx]\n", parent->name, parent->start, parent->end, new->name, new->start, new->end);
 
 	next->sibling = NULL;
-	for (next = first; next; next = next->sibling)
+	for (next = first; next; next = next->sibling) {
 		next->parent = new;
+		printk(KERN_DEBUG "    insert_resource: child: (%s) [%llx, %llx], new: (%s) [%llx, %llx]\n", next->name, next->start, next->end, new->name, new->start, new->end);
+	}
 
 	if (parent->child == first) {
 		parent->child = new;

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-21  2:48 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-21  2:48 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev




> > As a separate experiment, I started over with a clean version of
> > 700efc1b, then introduced the change from request_resource() to
> > insert_resource():
> > ===== BEGIN DIFF ================
> > diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
> > index a8694a3..988195d 100644
> > --- a/arch/x86/kernel/e820_64.c
> > +++ b/arch/x86/kernel/e820_64.c
> > @@ -245,7 +245,7 @@ void __init e820_reserve_resources(struct resource 
> *code_resource,
> >         res->start = e820.map[i].addr;
> >         res->end = res->start + e820.map[i].size - 1;
> >         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> > -        request_resource(&iomem_resource, res);
> > +        insert_resource(&iomem_resource, res);
> >         if (e820.map[i].type == E820_RAM) {
> >             /*
> >              * We don't know which RAM region contains kernel data,
> > ===== END DIFF ================
> >
> > The kernel produced from the change HANGS!
> 
> because code/data/bss/crashk is inserted at first
> 
> in e820_reserve_resource if you call request_resource instead of
> insert_resource. the entries from e820 tables that has conflict to
> entries already added will not show in
> resource list /proc/iomem.

Ahh, what an error I made!  I made at least 3 errors in that post, and
now that I am home from work I can try to correct them.


> please send out /proc/iomem when it happens to boot.

OK, this was my first error.  My first experiment -- leave 
request_resource() alone, and move the additions of the kernel memory
regions to setup_arch() -- produced a booting kernel.  When that
happened, I was already late for work... so I produced the output
of 'cat /proc/iomem' from that kernel and moved on to my second test

I simply forgot to include the output in my message because I was
rushing to get out of the house!  Here it is:

==============================
00000000-0009f3ff : System RAM
0009f400-0009ffff : reserved
000f0000-000fffff : reserved
00200000-005570e1 : Kernel code
005570e2-006b4397 : Kernel data
00736000-0077d387 : Kernel bss
77fe0000-77fe2fff : ACPI Non-volatile Storage
77fe3000-77feffff : ACPI Tables
77ff0000-77ffffff : reserved
78000000-7fffffff : pnp 00:0d
d8000000-dfffffff : PCI Bus #01
  d8000000-dfffffff : 0000:01:05.0
    d8000000-d8ffffff : uvesafb
e0000000-efffffff : PCI MMCONFIG 0
  e0000000-efffffff : reserved
fdc00000-fdcfffff : PCI Bus #02
  fdcff000-fdcff0ff : 0000:02:05.0
    fdcff000-fdcff0ff : r8169
fdd00000-fdefffff : PCI Bus #01
  fdd00000-fddfffff : 0000:01:05.0
  fdee0000-fdeeffff : 0000:01:05.0
  fdefc000-fdefffff : 0000:01:05.2
    fdefc000-fdefffff : ICH HD audio
fdf00000-fdffffff : PCI Bus #02
fe020000-fe023fff : 0000:00:14.2
  fe020000-fe023fff : ICH HD audio
fe029000-fe0290ff : 0000:00:13.5
  fe029000-fe0290ff : ehci_hcd
fe02a000-fe02afff : 0000:00:13.4
  fe02a000-fe02afff : ohci_hcd
fe02b000-fe02bfff : 0000:00:13.3
  fe02b000-fe02bfff : ohci_hcd
fe02c000-fe02cfff : 0000:00:13.2
  fe02c000-fe02cfff : ohci_hcd
fe02d000-fe02dfff : 0000:00:13.1
  fe02d000-fe02dfff : ohci_hcd
fe02e000-fe02efff : 0000:00:13.0
  fe02e000-fe02efff : ohci_hcd
fe02f000-fe02f3ff : 0000:00:12.0
  fe02f000-fe02f3ff : ahci
fec00000-fec00fff : IOAPIC 0
  fec00000-fec00fff : pnp 00:0d
fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0
fee00000-fee00fff : Local APIC
fff80000-fffeffff : pnp 00:0d
ffff0000-ffffffff : pnp 00:0d
==============================


My second (huge) error was to carry out my second experiment incorrectly.
When I replaced request_resource() with insert_resource(), I positioned
it before the code that added the kernel memory regions to the resource
for the system RAM region containing them.

I actually intended the second experiment to be different, but only
realized it when Yinghai corrected me (above).  Here is the diff for
the _actual_ experiment I intended:
===== BEGIN DIFF ================
diff --git a/arch/x86/kernel/e820_64.c b/arch/x86/kernel/e820_64.c
index a8694a3..f2498ae 100644
--- a/arch/x86/kernel/e820_64.c
+++ b/arch/x86/kernel/e820_64.c
@@ -245,7 +245,6 @@ void __init e820_reserve_resources(struct resource *code_resource,
         res->start = e820.map[i].addr;
         res->end = res->start + e820.map[i].size - 1;
         res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
-        request_resource(&iomem_resource, res);
         if (e820.map[i].type == E820_RAM) {
             /*
              * We don't know which RAM region contains kernel data,
@@ -260,6 +259,7 @@ void __init e820_reserve_resources(struct resource *code_resource,
                 request_resource(res, &crashk_res);
 #endif
         }
+        insert_resource(&iomem_resource, res);
     }
 }
===== END DIFF ================

This change produces a kernel that hangs.  The difference between the
results of the two experiments was what I was trying to show.  We now
know that:

- moving the code that adds {code,data,bss}_resource to the iomem_resource
tree out of e820_reserve_resources() and into setup_arch() is NOT what
caused my problem.

- the change from using request_resource() to insert_resource() seems
to be to blame.

My purpose in those experiments was to try to present a sort of "proof",
like a mathematical proof.  But my understanding of the code is fairly
shallow, so my "proof" might not mean very much.  I was hoping to 
provide useful data here, but only kernel developers can assess whether
or not this information is useful.


My third error was my "conclusion":

> My conclusion is that, somehow, the reordering of adding 
> {code,data,bss}_resource to the iomem_resource tree is doing funky 
> things to certain people's machines!

I meant to say just the opposite:  reordering the place where adding the
kernel memory resources to the iomem_resource tree is NOT the problem;
somehow the change to insert_resource() is the problem.

My apologies to all here:  I was racing to finish up, post my results,
and get to work... and completely botched the second experiment and the
message describing them!


Dave W.

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-21  4:07 David Witbrodt
  2008-08-21  6:42 ` Yinghai Lu
  2008-08-21  7:04 ` Ilpo Järvinen
  0 siblings, 2 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-21  4:07 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> please apply attached patch to see if insert_resource/request resource
> works on your conf

Yinghai,

Please advise me on how you would like me to handle 2.6.27 kernels.
If I use your patch on 2.6.27-rc3, the message scroll off the 80x25 
screen before I can see them... and then the kernel hangs.  I can run 
the kernel with "hpet=disable", but I'm not sure you want that.  If
you _do_ want that, just let me know.

As an alternative, I can alter your patch to use a log level of
something lower, like KERN_WARNING.  Then I could see the messages
from your patch if I set a "loglevel=4" boot parameter, even on a
kernel that hangs.  The normal messages should disappear, only
leaving the messages from your patch.


In the meantime, here is what I _did_ do to test your patch:

==================================
$ git checkout -f v2.6.27-rc3
HEAD is now at 30a2f3c... Linux 2.6.27-rc3

$ git apply --verbose --check ../yh_insert_resource_debug.patch 
Checking patch kernel/resource.c...

$ git apply --verbose ../yh_insert_resource_debug.patch 
Checking patch kernel/resource.c...
Applied patch kernel/resource.c cleanly.

$ git status
# Not currently on any branch.
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#
#    modified:   kernel/resource.c
#
no changes added to commit (use "git add" and/or "git commit -a")
==================================

This kernel boots and hangs, and I cannot see your patch messages.  But
I am sure they are there.  (See below.)


To see your patch messages without altering the patch, I checked out
an older revision that will boot.  Also, I just realized why I never get
the earliest boot log messages from 'dmesg':  the standard value of 
CONFIG_LOG_BUF_SHIFT is 15 (32 KB), which is too small to capture all
of my early boot messages.

In view of these things, I checked out the last kernel that will run for
me without hanging,

$ git checkout -f 700efc1b

and set CONFIG_LOG_BUF_SHIFT=18.  Your patch messages show up nicely this
way:
==================================
$ uname -r
2.6.25.test

$ dmesg
Linux version 2.6.25.test (dawitbro@fileserver) (gcc version 4.3.1 (Debian 4.3.1-2) ) #1 SMP Wed Aug 20 23:31:39 EDT 2008
Command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
 BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000077fe0000 (usable)
 BIOS-e820: 0000000077fe0000 - 0000000077fe3000 (ACPI NVS)
 BIOS-e820: 0000000077fe3000 - 0000000077ff0000 (ACPI data)
 BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
end_pfn_map = 1048576
DMI 2.5 present.
ACPI: RSDP 000F7B80, 0024 (r2 RS690 )
ACPI: RSDT 77FE3040, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: FACP 77FE30C0, 0074 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: DSDT 77FE3180, 4B0B (r1 RS690  AWRDACPI     1000 MSFT  3000000)
ACPI: FACS 77FE0000, 0040
ACPI: SSDT 77FE7DC0, 028A (r1 PTLTD  POWERNOW        1  LTP        1)
ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
ACPI: MCFG 77FE8140, 003C (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: APIC 77FE7D00, 0068 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
No NUMA configuration found
Faking a node at 0000000000000000-0000000077fe0000
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
Bootmem setup node 0 0000000000000000-0000000077fe0000
  NODE_DATA [000000000000c000 - 0000000000012fff]
  bootmap [0000000000013000 -  0000000000021fff] pages f
early res: 0 [0-fff] BIOS data page
early res: 1 [6000-7fff] SMP_TRAMPOLINE
early res: 2 [200000-7b5387] TEXT DATA BSS
early res: 3 [9f000-aefff] EBDA
early res: 4 [8000-bfff] PGTABLE
 [ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
 [ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
 [ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
 [ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
 [ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
 [ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
 [ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
 [ffffe20000e00000-ffffe20000ffffff] PMD ->ffff810002e00000 on node 0
 [ffffe20001000000-ffffe200011fffff] PMD ->ffff810003200000 on node 0
 [ffffe20001200000-ffffe200013fffff] PMD ->ffff810003600000 on node 0
 [ffffe20001400000-ffffe200015fffff] PMD ->ffff810003a00000 on node 0
 [ffffe20001600000-ffffe200017fffff] PMD ->ffff810003e00000 on node 0
 [ffffe20001800000-ffffe200019fffff] PMD ->ffff810004200000 on node 0
 [ffffe20001a00000-ffffe20001bfffff] PMD ->ffff810004600000 on node 0
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0:        0 ->      159
    0:      256 ->   491488
On node 0 totalpages: 491391
  DMA zone: 56 pages used for memmap
  DMA zone: 1486 pages reserved
  DMA zone: 2457 pages, LIFO batch:0
  DMA32 zone: 6663 pages used for memmap
  DMA32 zone: 480729 pages, LIFO batch:31
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
ATI board detected. Disabling timer routing over 8254.
Detected use of extended apic ids on hypertransport bus
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, 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 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x10b9a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [0, 9f3ff] conflict 0
request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel code) [200000, 557241] conflict 1
request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel data) [557242, 6b4397] conflict 1
request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel bss) [736000, 7b5387] conflict 1
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [9f400, 9ffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [f0000, fffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [100000, 77fdffff] conflict 0
request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel code) [200000, 557241] conflict 0
request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel data) [557242, 6b4397] conflict 0
request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel bss) [736000, 7b5387] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI Non-volatile Storage) [77fe0000, 77fe2fff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI Tables) [77fe3000, 77feffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [77ff0000, 77ffffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [e0000000, efffffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [fec00000, ffffffff] conflict 1
request_resource: root: (PCI IO) [0, ffff], new: (dma1) [0, 1f] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (pic1) [20, 21] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (timer0) [40, 43] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (timer1) [50, 53] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (keyboard) [60, 6f] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (dma page reg) [80, 8f] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (pic2) [a0, a1] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (dma2) [c0, df] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (fpu) [f0, ff] conflict 0
Allocating PCI resources starting at 80000000 (gap: 78000000:68000000)
PERCPU: Allocating 33672 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 483186
Policy zone: DMA32
Kernel command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
Marking TSC unstable due to TSCs unsynchronized
time.c: Detected 2499.726 MHz processor.
request_resource: root: (PCI IO) [0, ffff], new: (vga+) [3c0, 3df] conflict 0
Console: colour VGA+ 80x25
console [tty0] enabled
Checking aperture...
Node 0: aperture @ 2ecc000000 size 32 MB
Aperture beyond 4GB. Ignoring.
No AGP bridge found
Memory: 1930748k/1965952k available (3420k kernel code, 34816k reserved, 1396k data, 388k init)
CPA: page pool initialized 1 of 1 pages preallocated
SLUB: Genslabs=13, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
hpet clockevent registered
Calibrating delay using timer specific routine.. 5121.43 BogoMIPS (lpj=8531901)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Freeing SMP alternatives: 30k freed
ACPI: Core revision 20070126
Using local APIC timer interrupts.
APIC timer calibration result 12498622
Detected 12.498 MHz APIC timer.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5001.83 BogoMIPS (lpj=8332542)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
AMD Processor model unknown stepping 02
Brought up 2 CPUs
net_namespace: 408 bytes
NET: Registered protocol family 16
No dock devices found.
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:14.4
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
 00:0d: mem resource (0xfed00000-0xfed000ff) overlaps 0000:00:14.0 BAR 1 (0xfed00000-0xfed003ff), disabling
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 3.00 loaded.
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
request_resource: root: (PCI IO) [0, ffff], new: (PCI Bus #01) [e000, efff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus #01) [fdd00000, fdefffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus #01) [d8000000, dfffffff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (PCI Bus #02) [d000, dfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus #02) [fdc00000, fdcfffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus #02) [fdf00000, fdffffff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [ff00, ff07] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fe00, fe03] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fd00, fd07] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fc00, fc03] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fb00, fb0f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:12.0) [fe02f000, fe02f3ff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.0) [fe02e000, fe02efff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.1) [fe02d000, fe02dfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.2) [fe02c000, fe02cfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.3) [fe02b000, fe02bfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.4) [fe02a000, fe02afff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.5) [fe029000, fe0290ff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.0) [fa00, fa0f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:14.0) [fed00000, fed003ff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [1f0, 1f7] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [3f6, 3f6] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [170, 177] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [376, 376] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [f900, f90f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:14.2) [fe020000, fe023fff] conflict 0
request_resource: root: (PCI Bus #01) [d8000000, dfffffff], new: (0000:01:05.0) [d8000000, dfffffff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdee0000, fdeeffff] conflict 0
request_resource: root: (PCI Bus #01) [e000, efff], new: (0000:01:05.0) [ee00, eeff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdd00000, fddfffff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.2) [fdefc000, fdefffff] conflict 0
request_resource: root: (PCI Bus #02) [d000, dfff], new: (0000:02:05.0) [de00, deff] conflict 0
request_resource: root: (PCI Bus #02) [fdc00000, fdcfffff], new: (0000:02:05.0) [fdcff000, fdcff0ff] conflict 0
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 32-bit timers, 14318180 Hz
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
system 00:01: ioport range 0x4100-0x411f has been reserved
system 00:01: ioport range 0x228-0x22f has been reserved
system 00:01: ioport range 0x40b-0x40b has been reserved
system 00:01: ioport range 0x4d6-0x4d6 has been reserved
system 00:01: ioport range 0xc00-0xc01 has been reserved
system 00:01: ioport range 0xc14-0xc14 has been reserved
system 00:01: ioport range 0xc50-0xc52 has been reserved
system 00:01: ioport range 0xc6c-0xc6d has been reserved
system 00:01: ioport range 0xc6f-0xc6f has been reserved
system 00:01: ioport range 0xcd0-0xcd1 has been reserved
system 00:01: ioport range 0xcd2-0xcd3 has been reserved
system 00:01: ioport range 0xcd4-0xcdf has been reserved
system 00:01: ioport range 0x4000-0x40fe has been reserved
system 00:01: ioport range 0x4210-0x4217 has been reserved
system 00:01: ioport range 0xb10-0xb1f has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x220-0x225 has been reserved
system 00:07: ioport range 0xb00-0xb0f has been reserved
system 00:0c: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0d: iomem range 0xf0000-0xfffff could not be reserved
system 00:0d: iomem range 0x77fe0000-0x77ffffff could not be reserved
system 00:0d: iomem range 0xffff0000-0xffffffff has been reserved
system 00:0d: iomem range 0x0-0x9ffff could not be reserved
system 00:0d: iomem range 0x100000-0x77fdffff could not be reserved
system 00:0d: iomem range 0x78000000-0x7fffffff has been reserved
system 00:0d: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:0d: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:0d: iomem range 0xfff80000-0xfffeffff has been reserved
PCI: Bridge: 0000:00:01.0
  IO window: e000-efff
  MEM window: 0xfdd00000-0xfdefffff
  PREFETCH window: 0x00000000d8000000-0x00000000dfffffff
PCI: Bridge: 0000:00:14.4
  IO window: d000-dfff
  MEM window: 0xfdc00000-0xfdcfffff
  PREFETCH window: 0x00000000fdf00000-0x00000000fdffffff
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:05.0: Boot video device
uvesafb: (C) 1988-2005, ATI Technologies Inc. RS69001.00, RS69001.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. RS69001.00, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x56
uvesafb: framebuffer at 0xd8000000, mapped to 0xffffc20010980000, using 16384k, total 16384k
fb0: VESA VGA frame buffer device
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
ACPI: PNP0C0B:00 is registered as cooling_device0
ACPI: Fan [FAN] (on)
ACPI: ACPI0007:00 is registered as cooling_device1
ACPI: ACPI0007:01 is registered as cooling_device2
ACPI: LNXTHERM:01 is registered as thermal_zone0
ACPI: Thermal Zone [THRM] (24 C)
hpet_resources: 0xfed00000 is busy
Linux agpgart interface v0.103
loop: module loaded
r8169 Gigabit Ethernet driver 2.2LK loaded
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 22 (level, low) -> IRQ 22
eth0: RTL8169sc/8110sc at 0xffffc2000032e000, 00:1b:b9:f4:88:d0, XID 18000000 IRQ 22
Uniform Multi-Platform E-IDE driver
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SB600_PATA: IDE controller (0x1002:0x438c rev 0x00) at  PCI slot 0000:00:14.1
ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 16
SB600_PATA: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf900-0xf907, BIOS settings: hda:DMA, hdb:DMA
Probing IDE interface ide0...
hda: Maxtor 6H500R0, ATA DISK drive
hdb: SAMSUNG DVD-ROM SD-616E, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63
hda: cache flushes supported
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 >
hdb: ATAPI 48X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.20
Driver 'sd' needs updating - please use bus_type methods
ahci 0000:00:12.0: version 3.0
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 16 (level, low) -> IRQ 16
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 16
ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 16
ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 16
ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 16
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: configured for UDMA/133
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
ACPI: PCI Interrupt 0000:00:13.5[D] -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 19, io mem 0xfe029000
ehci_hcd 0000:00:13.5: 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: 10 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 16, io mem 0xfe02e000
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:13.1[B] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 17, io mem 0xfe02d000
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:13.2[C] -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 18, io mem 0xfe02c000
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:13.3[B] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 17, io mem 0xfe02b000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.4[C] -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 18, io mem 0xfe02a000
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
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
i2c /dev entries driver
piix4_smbus 0000:00:14.0: Found 0000:00:14.0 device
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31 16:40:16 2008 UTC).
ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
ACPI: PCI Interrupt 0000:01:05.2[B] -> GSI 19 (level, low) -> IRQ 19
ALSA device list:
  #0: HDA ATI SB at 0xfe020000 irq 16
  #1: HDA ATI HDMI at 0xfdefc000 irq 19
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
powernow-k8: Found 1 AMD Processor model unknown processors (2 cpu cores) (version 2.20.00)
powernow-k8:    0 : fid 0x11 (2500 MHz), vid 0xc
powernow-k8:    1 : fid 0x10 (2400 MHz), vid 0xd
powernow-k8:    2 : fid 0xe (2200 MHz), vid 0xf
powernow-k8:    3 : fid 0xc (2000 MHz), vid 0x11
powernow-k8:    4 : fid 0xa (1800 MHz), vid 0x13
powernow-k8:    5 : fid 0x2 (1000 MHz), vid 0x16
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) [fed00000, fed003ff]
  insert_resource: first: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) [fed00000, fed003ff]
  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) [fed00000, fed003ff]
    insert_resource: child: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) [fed00000, fed003ff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
  insert_resource: first: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) [fec00000, fec00fff]
  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
    insert_resource: child: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) [fec00000, fec00fff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
  insert_resource: first: (reserved) [e0000000, efffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
    insert_resource: child: (reserved) [e0000000, efffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
input: AT Translated Set 2 keyboard as /class/input/input3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 388k freed
input: PC Speaker as /class/input/input4
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Adding 1951888k swap on /dev/hda2.  Priority:-1 extents:1 across:1951888k
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
r8169: eth0: link up
NET: Registered protocol family 10
Clocksource tsc unstable (delta = -87569023 ns)
warning: `ntpd' uses 32-bit capabilities (legacy support in use)
eth0: no IPv6 routers present
==================================

Just let me know how you would like me to handle a crashing kernel, if
this output is not sufficient.  I don't think all of your patch
messages would fit on one screen, though, even if I made the 
KERN_WARNING change that would allow me to see them.


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-21  4:07 David Witbrodt
@ 2008-08-21  6:42 ` Yinghai Lu
  2008-08-21  7:04 ` Ilpo Järvinen
  1 sibling, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-21  6:42 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Wed, Aug 20, 2008 at 9:07 PM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
>
>> please apply attached patch to see if insert_resource/request resource
>> works on your conf
>
> Yinghai,
>
> Please advise me on how you would like me to handle 2.6.27 kernels.
> If I use your patch on 2.6.27-rc3, the message scroll off the 80x25
> screen before I can see them... and then the kernel hangs.  I can run
> the kernel with "hpet=disable", but I'm not sure you want that.  If
> you _do_ want that, just let me know.
>
> As an alternative, I can alter your patch to use a log level of
> something lower, like KERN_WARNING.  Then I could see the messages
> from your patch if I set a "loglevel=4" boot parameter, even on a
> kernel that hangs.  The normal messages should disappear, only
> leaving the messages from your patch.
>
>
> In the meantime, here is what I _did_ do to test your patch:
>
> ==================================
> $ git checkout -f v2.6.27-rc3
> HEAD is now at 30a2f3c... Linux 2.6.27-rc3
>
> $ git apply --verbose --check ../yh_insert_resource_debug.patch
> Checking patch kernel/resource.c...
>
> $ git apply --verbose ../yh_insert_resource_debug.patch
> Checking patch kernel/resource.c...
> Applied patch kernel/resource.c cleanly.
>
> $ git status
> # Not currently on any branch.
> # Changed but not updated:
> #   (use "git add <file>..." to update what will be committed)
> #
> #    modified:   kernel/resource.c
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> ==================================
>
> This kernel boots and hangs, and I cannot see your patch messages.  But
> I am sure they are there.  (See below.)
>
>
> To see your patch messages without altering the patch, I checked out
> an older revision that will boot.  Also, I just realized why I never get
> the earliest boot log messages from 'dmesg':  the standard value of
> CONFIG_LOG_BUF_SHIFT is 15 (32 KB), which is too small to capture all
> of my early boot messages.
>
> In view of these things, I checked out the last kernel that will run for
> me without hanging,
>
> $ git checkout -f 700efc1b
>
> and set CONFIG_LOG_BUF_SHIFT=18.  Your patch messages show up nicely this
> way:
> ==================================
> $ uname -r
> 2.6.25.test
>
> $ dmesg
> Linux version 2.6.25.test (dawitbro@fileserver) (gcc version 4.3.1 (Debian 4.3.1-2) ) #1 SMP Wed Aug 20 23:31:39 EDT 2008
> Command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
>  BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000077fe0000 (usable)
>  BIOS-e820: 0000000077fe0000 - 0000000077fe3000 (ACPI NVS)
>  BIOS-e820: 0000000077fe3000 - 0000000077ff0000 (ACPI data)
>  BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
>  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> Entering add_active_range(0, 0, 159) 0 entries of 3200 used
> Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
> end_pfn_map = 1048576
> DMI 2.5 present.
> ACPI: RSDP 000F7B80, 0024 (r2 RS690 )
> ACPI: RSDT 77FE3040, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> ACPI: FACP 77FE30C0, 0074 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> ACPI: DSDT 77FE3180, 4B0B (r1 RS690  AWRDACPI     1000 MSFT  3000000)
> ACPI: FACS 77FE0000, 0040
> ACPI: SSDT 77FE7DC0, 028A (r1 PTLTD  POWERNOW        1  LTP        1)
> ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
> ACPI: MCFG 77FE8140, 003C (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> ACPI: APIC 77FE7D00, 0068 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> No NUMA configuration found
> Faking a node at 0000000000000000-0000000077fe0000
> Entering add_active_range(0, 0, 159) 0 entries of 3200 used
> Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
> Bootmem setup node 0 0000000000000000-0000000077fe0000
>  NODE_DATA [000000000000c000 - 0000000000012fff]
>  bootmap [0000000000013000 -  0000000000021fff] pages f
> early res: 0 [0-fff] BIOS data page
> early res: 1 [6000-7fff] SMP_TRAMPOLINE
> early res: 2 [200000-7b5387] TEXT DATA BSS
> early res: 3 [9f000-aefff] EBDA
> early res: 4 [8000-bfff] PGTABLE
>  [ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
>  [ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
>  [ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
>  [ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
>  [ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
>  [ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
>  [ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
>  [ffffe20000e00000-ffffe20000ffffff] PMD ->ffff810002e00000 on node 0
>  [ffffe20001000000-ffffe200011fffff] PMD ->ffff810003200000 on node 0
>  [ffffe20001200000-ffffe200013fffff] PMD ->ffff810003600000 on node 0
>  [ffffe20001400000-ffffe200015fffff] PMD ->ffff810003a00000 on node 0
>  [ffffe20001600000-ffffe200017fffff] PMD ->ffff810003e00000 on node 0
>  [ffffe20001800000-ffffe200019fffff] PMD ->ffff810004200000 on node 0
>  [ffffe20001a00000-ffffe20001bfffff] PMD ->ffff810004600000 on node 0
> Zone PFN ranges:
>  DMA             0 ->     4096
>  DMA32        4096 ->  1048576
>  Normal    1048576 ->  1048576
> Movable zone start PFN for each node
> early_node_map[2] active PFN ranges
>    0:        0 ->      159
>    0:      256 ->   491488
> On node 0 totalpages: 491391
>  DMA zone: 56 pages used for memmap
>  DMA zone: 1486 pages reserved
>  DMA zone: 2457 pages, LIFO batch:0
>  DMA32 zone: 6663 pages used for memmap
>  DMA32 zone: 480729 pages, LIFO batch:31
>  Normal zone: 0 pages used for memmap
>  Movable zone: 0 pages used for memmap
> ATI board detected. Disabling timer routing over 8254.
> Detected use of extended apic ids on hypertransport bus
> ACPI: PM-Timer IO Port: 0x4008
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 (Bootup-CPU)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> Processor #1
> ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 2, 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 low level)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ9 used by override.
> Setting APIC routing to flat
> ACPI: HPET id: 0x10b9a201 base: 0xfed00000
> Using ACPI (MADT) for SMP configuration information
> insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
>    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [0, 9f3ff] conflict 0
> request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel code) [200000, 557241] conflict 1
> request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel data) [557242, 6b4397] conflict 1
> request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel bss) [736000, 7b5387] conflict 1
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [9f400, 9ffff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [f0000, fffff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [100000, 77fdffff] conflict 0
> request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel code) [200000, 557241] conflict 0
> request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel data) [557242, 6b4397] conflict 0
> request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel bss) [736000, 7b5387] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI Non-volatile Storage) [77fe0000, 77fe2fff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI Tables) [77fe3000, 77feffff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [77ff0000, 77ffffff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [e0000000, efffffff] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [fec00000, ffffffff] conflict 1
..
> insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) [fed00000, fed003ff]
>  insert_resource: first: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) [fed00000, fed003ff]
>  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) [fed00000, fed003ff]
>    insert_resource: child: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) [fed00000, fed003ff]
> insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
>  insert_resource: first: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) [fec00000, fec00fff]
>  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
>    insert_resource: child: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) [fec00000, fec00fff]

so old kernel doesn't register [fec00000, ffffffff] from e820 as
reserved. because lapic address register at first.

lapic, ioapic, and hpet0 addr all should be children of [fec00000,
fffffffff] as reserved from e820.

please use my print out patch with current kernel.

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-21  4:07 David Witbrodt
  2008-08-21  6:42 ` Yinghai Lu
@ 2008-08-21  7:04 ` Ilpo Järvinen
  1 sibling, 0 replies; 41+ messages in thread
From: Ilpo Järvinen @ 2008-08-21  7:04 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Wed, 20 Aug 2008, David Witbrodt wrote:

> Please advise me on how you would like me to handle 2.6.27 kernels.
> If I use your patch on 2.6.27-rc3, the message scroll off the 80x25 
> screen before I can see them... 

Couldn't you play with CONFIG_BOOT_PRINTK_DELAY?


-- 
 i.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-21 13:33 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-21 13:33 UTC (permalink / raw)
  To: Ilpo Järvinen
  Cc: Yinghai Lu, Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> > Please advise me on how you would like me to handle 2.6.27 kernels.
> > If I use your patch on 2.6.27-rc3, the message scroll off the 80x25 
> > screen before I can see them... 
> 
> Couldn't you play with CONFIG_BOOT_PRINTK_DELAY?

Thanks for this!  I am not a developer, so I am not familiar with all
of the little tweaks available in the kernel configs -- I've probably
seen this dozens of times, but ignored it because I wasn't debugging.

Now that I _am_ debugging, I wish I had paid more attention.

When I tried it, my kernel hung much earlier in the boot process.  The
help text for CONFIG_BOOT_PRINTK_DELAY even mentions that this can be
a problems on SMP systems, and that is exactly what I have.

Bummer.


Thanks though,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-21 14:09 David Witbrodt
  2008-08-21 15:33 ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-21 14:09 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> > $ dmesg
> > Linux version 2.6.25.test (dawitbro@fileserver) (gcc version 4.3.1 (Debian 
> 4.3.1-2) ) #1 SMP Wed Aug 20 23:31:39 EDT 2008
> > Command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 
> fbcon=scrollback:256k,font:10x18 debug
> > BIOS-provided physical RAM map:
> >  BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
> >  BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
> >  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> >  BIOS-e820: 0000000000100000 - 0000000077fe0000 (usable)
> >  BIOS-e820: 0000000077fe0000 - 0000000077fe3000 (ACPI NVS)
> >  BIOS-e820: 0000000077fe3000 - 0000000077ff0000 (ACPI data)
> >  BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
> >  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > Entering add_active_range(0, 0, 159) 0 entries of 3200 used
> > Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
> > end_pfn_map = 1048576
> > DMI 2.5 present.
> > ACPI: RSDP 000F7B80, 0024 (r2 RS690 )
> > ACPI: RSDT 77FE3040, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> > ACPI: FACP 77FE30C0, 0074 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> > ACPI: DSDT 77FE3180, 4B0B (r1 RS690  AWRDACPI     1000 MSFT  3000000)
> > ACPI: FACS 77FE0000, 0040
> > ACPI: SSDT 77FE7DC0, 028A (r1 PTLTD  POWERNOW        1  LTP        1)
> > ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
> > ACPI: MCFG 77FE8140, 003C (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> > ACPI: APIC 77FE7D00, 0068 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
> > No NUMA configuration found
> > Faking a node at 0000000000000000-0000000077fe0000
> > Entering add_active_range(0, 0, 159) 0 entries of 3200 used
> > Entering add_active_range(0, 256, 491488) 1 entries of 3200 used
> > Bootmem setup node 0 0000000000000000-0000000077fe0000
> >  NODE_DATA [000000000000c000 - 0000000000012fff]
> >  bootmap [0000000000013000 -  0000000000021fff] pages f
> > early res: 0 [0-fff] BIOS data page
> > early res: 1 [6000-7fff] SMP_TRAMPOLINE
> > early res: 2 [200000-7b5387] TEXT DATA BSS
> > early res: 3 [9f000-aefff] EBDA
> > early res: 4 [8000-bfff] PGTABLE
> >  [ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
> >  [ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
> >  [ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
> >  [ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
> >  [ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
> >  [ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
> >  [ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
> >  [ffffe20000e00000-ffffe20000ffffff] PMD ->ffff810002e00000 on node 0
> >  [ffffe20001000000-ffffe200011fffff] PMD ->ffff810003200000 on node 0
> >  [ffffe20001200000-ffffe200013fffff] PMD ->ffff810003600000 on node 0
> >  [ffffe20001400000-ffffe200015fffff] PMD ->ffff810003a00000 on node 0
> >  [ffffe20001600000-ffffe200017fffff] PMD ->ffff810003e00000 on node 0
> >  [ffffe20001800000-ffffe200019fffff] PMD ->ffff810004200000 on node 0
> >  [ffffe20001a00000-ffffe20001bfffff] PMD ->ffff810004600000 on node 0
> > Zone PFN ranges:
> >  DMA             0 ->     4096
> >  DMA32        4096 ->  1048576
> >  Normal    1048576 ->  1048576
> > Movable zone start PFN for each node
> > early_node_map[2] active PFN ranges
> >    0:        0 ->      159
> >    0:      256 ->   491488
> > On node 0 totalpages: 491391
> >  DMA zone: 56 pages used for memmap
> >  DMA zone: 1486 pages reserved
> >  DMA zone: 2457 pages, LIFO batch:0
> >  DMA32 zone: 6663 pages used for memmap
> >  DMA32 zone: 480729 pages, LIFO batch:31
> >  Normal zone: 0 pages used for memmap
> >  Movable zone: 0 pages used for memmap
> > ATI board detected. Disabling timer routing over 8254.
> > Detected use of extended apic ids on hypertransport bus
> > ACPI: PM-Timer IO Port: 0x4008
> > ACPI: Local APIC address 0xfee00000
> > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> > Processor #0 (Bootup-CPU)
> > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> > Processor #1
> > ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> > ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> > IOAPIC[0]: apic_id 2, 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 low level)
> > ACPI: IRQ0 used by override.
> > ACPI: IRQ2 used by override.
> > ACPI: IRQ9 used by override.
> > Setting APIC routing to flat
> > ACPI: HPET id: 0x10b9a201 base: 0xfed00000
> > Using ACPI (MADT) for SMP configuration information
> > insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) 
> [fee00000, fee00fff]
> >    insert_resource: good with request direct parent: (PCI mem) [0, 
> ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [0, 
> 9f3ff] conflict 0
> > request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel code) [200000, 
> 557241] conflict 1
> > request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel data) [557242, 
> 6b4397] conflict 1
> > request_resource: root: (System RAM) [0, 9f3ff], new: (Kernel bss) [736000, 
> 7b5387] conflict 1
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) 
> [9f400, 9ffff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) 
> [f0000, fffff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (System RAM) 
> [100000, 77fdffff] conflict 0
> > request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel code) 
> [200000, 557241] conflict 0
> > request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel data) 
> [557242, 6b4397] conflict 0
> > request_resource: root: (System RAM) [100000, 77fdffff], new: (Kernel bss) 
> [736000, 7b5387] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI 
> Non-volatile Storage) [77fe0000, 77fe2fff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (ACPI Tables) 
> [77fe3000, 77feffff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) 
> [77ff0000, 77ffffff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) 
> [e0000000, efffffff] conflict 0
> > request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) 
> [fec00000, ffffffff] conflict 1
> ..
> > insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) 
> [fed00000, fed003ff]
> >  insert_resource: first: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) 
> [fed00000, fed003ff]
> >  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 
> 0) [fed00000, fed003ff]
> >    insert_resource: child: (0000:00:14.0) [fed00000, fed003ff], new: (HPET 0) 
> [fed00000, fed003ff]
> > insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) 
> [fec00000, fec00fff]
> >  insert_resource: first: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) 
> [fec00000, fec00fff]
> >  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 
> 0) [fec00000, fec00fff]
> >    insert_resource: child: (pnp 00:0d) [fec00000, fec00fff], new: (IOAPIC 0) 
> [fec00000, fec00fff]
> 
> so old kernel doesn't register [fec00000, ffffffff] from e820 as
> reserved. because lapic address register at first.

Well, at least it tried!  ;)

request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (reserved) [fec00000, ffffffff] conflict 1


> lapic, ioapic, and hpet0 addr all should be children of [fec00000,
> fffffffff] as reserved from e820.

I can see that the resources are not recorded in the tree properly, but 
this kernel was still able to boot without hanging.  Is it enough that
the memory region was already marked as busy, or do these resource 
structures need to be in the tree for other purposes?


> please use my print out patch with current kernel.

On the suggestion of Ilpo Järvinen, I tried to delay the printk's long
enough to see them using CONFIG_BOOT_PRINTK_DELAY.  Unfortunately, I was
stung by what the help text for that option warns of:  the
CONFIG_BOOT_PRINTK_DELAY option can cause the kernel to hang on SMP
machines.

That is exactly what happens:  the kernel hangs pretty much immediately,
with only about a half dozen lines printed.

I did try my own suggestion:  change KERN_DEBUG to KERN_WARNING in your patch,
and boot with "loglevel=5".  This worked, and almost the only lines printed
were those from your patch.  However, without the printk delay everything
just scrolled away too fast to read... until the kernel hung.

I believe I can find a workaround to print this output in a more compact way...
your formatting takes up 2 lines for each printk.  However, I am busy this
morning and I have to work this afternoon.  I may not be able to provide
the entire output until tonight or tomorrow.

For now, I can only report that the last lines printed were the same as
these from the working kernel's 'dmesg' output:

========
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [3f6, 3f6] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [170, 177] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [376, 376] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [f900, f90f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:14.2) [fe020000, fe023fff] conflict 0
request_resource: root: (PCI Bus #01) [d8000000, dfffffff], new: (0000:01:05.0) [d8000000, dfffffff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdee0000, fdeeffff] conflict 0
request_resource: root: (PCI Bus #01) [e000, efff], new: (0000:01:05.0) [ee00, eeff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdd00000, fddfffff] conflict 0
request_resource: root: (PCI Bus #01) [fdd00000, fdefffff], new: (0000:01:05.2) [fdefc000, fdefffff] conflict 0
request_resource: root: (PCI Bus #02) [d000, dfff], new: (0000:02:05.0) [de00, deff] conflict 0
request_resource: root: (PCI Bus #02) [fdc00000, fdcfffff], new: (0000:02:05.0) [fdcff000, fdcff0ff] conflict 0
========

The only differences were trivial:  the "PCI Bus" strings now print in a
different format, like "PCI Bus 0000:01".

I will try to provide the entire output tonight or tomorrow.  It will be
difficult, though:  it looks like I have to try to fit the info from about
60 of the printk's in your patch onto the 80x25 VGA screen, and still
make it understandable enough to be useful.


BTW, in a previous message, I recursed the iomem_resource tree and printed
all of the elements that end up there.  This was not sufficient, right?  You
also want to see what is rejected and not stored in the tree, which your
patch's printks do show?


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-21 14:09 David Witbrodt
@ 2008-08-21 15:33 ` Yinghai Lu
  0 siblings, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-21 15:33 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Thu, Aug 21, 2008 at 7:09 AM, David Witbrodt <dawitbro@sbcglobal.net> wrote:

>
> I will try to provide the entire output tonight or tomorrow.  It will be
> difficult, though:  it looks like I have to try to fit the info from about
> 60 of the printk's in your patch onto the 80x25 VGA screen, and still
> make it understandable enough to be useful.
>

with hpet=disable?

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-21 16:53 David Witbrodt
  2008-08-21 17:57 ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-21 16:53 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> > I will try to provide the entire output tonight or tomorrow.  It will be
> > difficult, though:  it looks like I have to try to fit the info from about
> > 60 of the printk's in your patch onto the 80x25 VGA screen, and still
> > make it understandable enough to be useful.
> >
> 
> with hpet=disable?

Oh, well that's easy.  (See below.)  I assumed you needed the data for a
hanging kernel, not one with the workaround enabled.

I can still try to provide the output of the printk's in your patch later,
in that would have any value.  Here is 'dmesg' for a recent kernel with
"hpet=disable":

==================================
$ git show |head
commit 30a2f3c60a84092c8084dfe788b710f8d0768cd4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Aug 12 18:55:39 2008 -0700

    Linux 2.6.27-rc3

diff --git a/Makefile b/Makefile
index fd3ca6e..53bf6ec 100644
--- a/Makefile
+++ b/Makefile

$ dmesg
Linux version 2.6.27-rc3.test (dawitbro@fileserver) (gcc version 4.3.1 (Debian 4.3.1-2) ) #1 SMP Thu Aug 21 09:11:13 EDT 2008
Command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug hpet=disable
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
 BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000077fe0000 (usable)
 BIOS-e820: 0000000077fe0000 - 0000000077fe3000 (ACPI NVS)
 BIOS-e820: 0000000077fe3000 - 0000000077ff0000 (ACPI data)
 BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel code) [200000, 56ce41]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel code) [200000, 56ce41]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel data) [56ce42, 6d5f3f]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel data) [56ce42, 6d5f3f]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel bss) [773000, 7b7647]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel bss) [773000, 7b7647]
last_pfn = 0x77fe0 max_arch_pfn = 0x3ffffffff
init_memory_mapping
 0000000000 - 0077e00000 page 2M
 0077e00000 - 0077fe0000 page 4k
kernel direct mapping tables up to 77fe0000 @ 8000-c000
last_map_addr: 77fe0000 end: 77fe0000
DMI 2.5 present.
ACPI: RSDP 000F7B80, 0024 (r2 RS690 )
ACPI: RSDT 77FE3040, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: FACP 77FE30C0, 0074 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: DSDT 77FE3180, 4B0B (r1 RS690  AWRDACPI     1000 MSFT  3000000)
ACPI: FACS 77FE0000, 0040
ACPI: SSDT 77FE7DC0, 028A (r1 PTLTD  POWERNOW        1  LTP        1)
ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
ACPI: MCFG 77FE8140, 003C (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: APIC 77FE7D00, 0068 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
No NUMA configuration found
Faking a node at 0000000000000000-0000000077fe0000
Bootmem setup node 0 0000000000000000-0000000077fe0000
  NODE_DATA [0000000000001000 - 0000000000004fff]
  bootmap [000000000000a000 -  0000000000018fff] pages f
(5 early reservations) ==> bootmem [0000000000 - 0077fe0000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
  #2 [0000200000 - 00007b7648]    TEXT DATA BSS ==> [0000200000 - 00007b7648]
  #3 [000009f000 - 0000100000]    BIOS reserved ==> [000009f000 - 0000100000]
  #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
found SMP MP-table at [ffff8800000f3c80] 000f3c80
 [ffffe20000000000-ffffe20001bfffff] PMD -> [ffff880001200000-ffff880002dfffff] on node 0
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000000 -> 0x0000009f
    0: 0x00000100 -> 0x00077fe0
On node 0 totalpages: 491391
  DMA zone: 2376 pages, LIFO batch:0
  DMA32 zone: 480728 pages, LIFO batch:31
Detected use of extended apic ids on hypertransport bus
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 0, 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 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x10b9a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [0, 9f3ff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [0, 9f3ff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [9f400, 9ffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [9f400, 9ffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [f0000, fffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [f0000, fffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [100000, 77fdffff]
  insert_resource: first: (Kernel code) [200000, 56ce41], new: (System RAM) [100000, 77fdffff]
  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (System RAM) [100000, 77fdffff]
    insert_resource: child: (Kernel code) [200000, 56ce41], new: (System RAM) [100000, 77fdffff]
    insert_resource: child: (Kernel data) [56ce42, 6d5f3f], new: (System RAM) [100000, 77fdffff]
    insert_resource: child: (Kernel bss) [773000, 7b7647], new: (System RAM) [100000, 77fdffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI Non-volatile Storage) [77fe0000, 77fe2fff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI Non-volatile Storage) [77fe0000, 77fe2fff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI Tables) [77fe3000, 77feffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI Tables) [77fe3000, 77feffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [77ff0000, 77ffffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [77ff0000, 77ffffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [e0000000, efffffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [e0000000, efffffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [fec00000, ffffffff]
    insert_resource: good with request direct parent: (PCI mem) [0, ffffffffffffffff], new: (reserved) [fec00000, ffffffff]
request_resource: root: (PCI IO) [0, ffff], new: (dma1) [0, 1f] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (pic1) [20, 21] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (timer0) [40, 43] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (timer1) [50, 53] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (keyboard) [60, 60] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (keyboard) [64, 64] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (dma page reg) [80, 8f] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (pic2) [a0, a1] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (dma2) [c0, df] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (fpu) [f0, ff] conflict 0
Allocating PCI resources starting at 80000000 (gap: 78000000:68000000)
PERCPU: Allocating 45224 bytes of per cpu data
NR_CPUS: 4, nr_cpu_ids: 4, nr_node_ids 1
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 483104
Policy zone: DMA32
Kernel command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug hpet=disable
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
Detected 2499.716 MHz processor.
request_resource: root: (PCI IO) [0, ffff], new: (vga+) [3c0, 3df] conflict 0
Console: colour VGA+ 80x25
console [tty0] enabled
Checking aperture...
No AGP bridge found
Node 0: aperture @ 2ecc000000 size 32 MB
Aperture beyond 4GB. Ignoring.
Memory: 1930792k/1965952k available (3507k kernel code, 34772k reserved, 1444k data, 508k init)
CPA: page pool initialized 1 of 1 pages preallocated
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 5001.74 BogoMIPS (lpj=8332386)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
tseg: 0000000000
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
using C1E aware idle routine
Freeing SMP alternatives: 28k freed
ACPI: Core revision 20080609
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: AMD Processor model unknown stepping 02
Using local APIC timer interrupts.
APIC timer calibration result 12498579
Detected 12.498 MHz APIC timer.
Booting processor 1/1 ip 6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5001.71 BogoMIPS (lpj=8332337)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: AMD Processor model unknown stepping 02
Brought up 2 CPUs
Total of 2 processors activated (10002.45 BogoMIPS).
CPU0 attaching sched-domain:
 domain 0: span 0-1 level CPU
  groups: 0 1
  domain 1: span 0-1 level NODE
   groups: 0-1
CPU1 attaching sched-domain:
 domain 0: span 0-1 level CPU
  groups: 1 0
  domain 1: span 0-1 level NODE
   groups: 0-1
net_namespace: 800 bytes
NET: Registered protocol family 16
No dock devices found.
node 0 link 0: io port [d000, ffff]
TOM: 0000000080000000 aka 2048M
node 0 link 0: mmio [a0000, bffff]
node 0 link 0: mmio [d8000000, dfffffff]
node 0 link 0: mmio [80000000, d7ffffff]
node 0 link 0: mmio [f0000000, fe02ffff]
node 0 link 0: mmio [e0000000, e02fffff]
bus: [00,02] on node 0 link 0
bus: 00 index 0 io port: [0, ffff]
bus: 00 index 1 mmio: [a0000, bffff]
bus: 00 index 2 mmio: [80000000, efffffff]
bus: 00 index 3 mmio: [f0000000, fcffffffff]
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:13.5: supports D1
pci 0000:00:13.5: supports D2
pci 0000:00:13.5: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.5: PME# disabled
pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
pci 0000:00:14.2: PME# disabled
pci 0000:01:05.0: supports D1
pci 0000:01:05.0: supports D2
pci 0000:02:05.0: supports D1
pci 0000:02:05.0: supports D2
pci 0000:02:05.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:02:05.0: PME# disabled
pci 0000:00:14.4: transparent bridge
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:0d: mem resource (0xfed00000-0xfed000ff) overlaps 0000:00:14.0 BAR 1 (0xfed00000-0xfed003ff), disabling
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
request_resource: root: (PCI IO) [0, ffff], new: (PCI Bus 0000:01) [e000, efff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus 0000:01) [fdd00000, fdefffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus 0000:01) [d8000000, dfffffff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (PCI Bus 0000:02) [d000, dfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus 0000:02) [fdc00000, fdcfffff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (PCI Bus 0000:02) [fdf00000, fdffffff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [ff00, ff07] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fe00, fe03] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fd00, fd07] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fc00, fc03] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:12.0) [fb00, fb0f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:12.0) [fe02f000, fe02f3ff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.0) [fe02e000, fe02efff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.1) [fe02d000, fe02dfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.2) [fe02c000, fe02cfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.3) [fe02b000, fe02bfff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.4) [fe02a000, fe02afff] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:13.5) [fe029000, fe0290ff] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.0) [fa00, fa0f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:14.0) [fed00000, fed003ff] conflict 1
pci 0000:00:14.0: BAR 1: can't allocate resource
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [1f0, 1f7] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [3f6, 3f6] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [170, 177] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [376, 376] conflict 0
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.1) [f900, f90f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new: (0000:00:14.2) [fe020000, fe023fff] conflict 0
request_resource: root: (PCI Bus 0000:01) [d8000000, dfffffff], new: (0000:01:05.0) [d8000000, dfffffff] conflict 0
request_resource: root: (PCI Bus 0000:01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdee0000, fdeeffff] conflict 0
request_resource: root: (PCI Bus 0000:01) [e000, efff], new: (0000:01:05.0) [ee00, eeff] conflict 0
request_resource: root: (PCI Bus 0000:01) [fdd00000, fdefffff], new: (0000:01:05.0) [fdd00000, fddfffff] conflict 0
request_resource: root: (PCI Bus 0000:01) [fdd00000, fdefffff], new: (0000:01:05.2) [fdefc000, fdefffff] conflict 0
request_resource: root: (PCI Bus 0000:02) [d000, dfff], new: (0000:02:05.0) [de00, deff] conflict 0
request_resource: root: (PCI Bus 0000:02) [fdc00000, fdcfffff], new: (0000:02:05.0) [fdcff000, fdcff0ff] conflict 0
system 00:01: ioport range 0x4100-0x411f has been reserved
system 00:01: ioport range 0x228-0x22f has been reserved
system 00:01: ioport range 0x40b-0x40b has been reserved
system 00:01: ioport range 0x4d6-0x4d6 has been reserved
system 00:01: ioport range 0xc00-0xc01 has been reserved
system 00:01: ioport range 0xc14-0xc14 has been reserved
system 00:01: ioport range 0xc50-0xc52 has been reserved
system 00:01: ioport range 0xc6c-0xc6d has been reserved
system 00:01: ioport range 0xc6f-0xc6f has been reserved
system 00:01: ioport range 0xcd0-0xcd1 has been reserved
system 00:01: ioport range 0xcd2-0xcd3 has been reserved
system 00:01: ioport range 0xcd4-0xcdf has been reserved
system 00:01: ioport range 0x4000-0x40fe has been reserved
system 00:01: ioport range 0x4210-0x4217 has been reserved
system 00:01: ioport range 0xb10-0xb1f has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x220-0x225 has been reserved
system 00:07: ioport range 0xb00-0xb0f has been reserved
system 00:0c: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0d: iomem range 0xf0000-0xfffff could not be reserved
system 00:0d: iomem range 0x77fe0000-0x77ffffff could not be reserved
system 00:0d: iomem range 0xffff0000-0xffffffff could not be reserved
system 00:0d: iomem range 0x0-0x9ffff could not be reserved
system 00:0d: iomem range 0x100000-0x77fdffff could not be reserved
system 00:0d: iomem range 0x78000000-0x7fffffff has been reserved
system 00:0d: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:0d: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:0d: iomem range 0xfff80000-0xfffeffff could not be reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0:   IO window: 0xe000-0xefff
pci 0000:00:01.0:   MEM window: 0xfdd00000-0xfdefffff
pci 0000:00:01.0:   PREFETCH window: 0x000000d8000000-0x000000dfffffff
pci 0000:00:14.4: PCI bridge, secondary bus 0000:02
pci 0000:00:14.4:   IO window: 0xd000-0xdfff
pci 0000:00:14.4:   MEM window: 0xfdc00000-0xfdcfffff
pci 0000:00:14.4:   PREFETCH window: 0x000000fdf00000-0x000000fdffffff
NET: Registered protocol family 2
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 3771
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:05.0: Boot video device
uvesafb: (C) 1988-2005, ATI Technologies Inc. RS69001.00, RS69001.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. RS69001.00, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x56
uvesafb: framebuffer at 0xd8000000, mapped to 0xffffc20010980000, using 16384k, total 16384k
fb0: VESA VGA frame buffer device
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
fan PNP0C0B:00: registered as cooling_device0
ACPI: Fan [FAN] (on)
processor ACPI0007:00: registered as cooling_device1
processor ACPI0007:01: registered as cooling_device2
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (18 C)
hpet_acpi_add: no address or irqs in _CRS
Linux agpgart interface v0.103
loop: module loaded
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
eth0: RTL8169sc/8110sc at 0xffffc20000330000, 00:1b:b9:f4:88:d0, XID 18000000 IRQ 22
Uniform Multi-Platform E-IDE driver
atiixp 0000:00:14.1: IDE controller (0x1002:0x438c rev 0x00)
ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
atiixp 0000:00:14.1: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf900-0xf907
Probing IDE interface ide0...
hda: Maxtor 6H500R0, ATA DISK drive
hdb: SAMSUNG DVD-ROM SD-616E, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
isa bounce pool size: 16 pages
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
Probing IDE interface ide1...
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 512KiB
hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63
hda: cache flushes supported
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 >
hdb: ATAPI 48X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.20
Driver 'sd' needs updating - please use bus_type methods
ahci 0000:00:12.0: version 3.0
ahci 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck led clo pmp pio 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 16
ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 16
ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 16
ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 16
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: configured for UDMA/133
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
ehci_hcd 0000:00:13.5: PCI INT D -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 19, io mem 0xfe029000
ehci_hcd 0000:00:13.5: 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: 10 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:13.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 16, io mem 0xfe02e000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 17, io mem 0xfe02d000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 18, io mem 0xfe02c000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 17, io mem 0xfe02b000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.4: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 18, io mem 0xfe02a000
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
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
i2c /dev entries driver
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xfa00, revision 0
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.17.
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
HDA Intel 0000:01:05.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ALSA device list:
  #0: HDA ATI SB at 0xfe020000 irq 16
  #1: HDA ATI HDMI at 0xfdefc000 irq 19
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
powernow-k8: Found 1 AMD Processor model unknown processors (2 cpu cores) (version 2.20.00)
powernow-k8:    0 : fid 0x11 (2500 MHz), vid 0xc
powernow-k8:    1 : fid 0x10 (2400 MHz), vid 0xd
powernow-k8:    2 : fid 0xe (2200 MHz), vid 0xf
powernow-k8:    3 : fid 0xc (2000 MHz), vid 0x11
powernow-k8:    4 : fid 0xa (1800 MHz), vid 0x13
powernow-k8:    5 : fid 0x2 (1000 MHz), vid 0x16
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (HPET 0) [fed00000, fed003ff]
  insert_resource: first: (reserved) [fec00000, ffffffff], new: (HPET 0) [fed00000, fed003ff]
    insert_resource: good with request direct parent: (reserved) [fec00000, ffffffff], new: (HPET 0) [fed00000, fed003ff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Local APIC) [fee00000, fee00fff]
  insert_resource: first: (reserved) [fec00000, ffffffff], new: (Local APIC) [fee00000, fee00fff]
    insert_resource: good with request direct parent: (reserved) [fec00000, ffffffff], new: (Local APIC) [fee00000, fee00fff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
  insert_resource: first: (reserved) [fec00000, ffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
    insert_resource: good with request direct parent: (reserved) [fec00000, ffffffff], new: (IOAPIC 0) [fec00000, fec00fff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
  insert_resource: first: (reserved) [e0000000, efffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
  insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
    insert_resource: child: (reserved) [e0000000, efffffff], new: (PCI MMCONFIG 0) [e0000000, efffffff]
input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
input: AT Translated Set 2 keyboard as /class/input/input3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 508k freed
Write protecting the kernel read-only data: 4536k
input: PC Speaker as /class/input/input4
Adding 1951888k swap on /dev/hda2.  Priority:-1 extents:1 across:1951888k
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
r8169: eth0: link up
NET: Registered protocol family 10
Clocksource tsc unstable (delta = -63433933 ns)
warning: `ntpd' uses 32-bit capabilities (legacy support in use)
eth0: no IPv6 routers present

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-21 16:53 David Witbrodt
@ 2008-08-21 17:57 ` Yinghai Lu
  0 siblings, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-21 17:57 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Thu, Aug 21, 2008 at 9:53 AM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
>
>> > I will try to provide the entire output tonight or tomorrow.  It will be
>> > difficult, though:  it looks like I have to try to fit the info from about
>> > 60 of the printk's in your patch onto the 80x25 VGA screen, and still
>> > make it understandable enough to be useful.
>> >
>>
>> with hpet=disable?
>
> Oh, well that's easy.  (See below.)  I assumed you needed the data for a
> hanging kernel, not one with the workaround enabled.
>
> I can still try to provide the output of the printk's in your patch later,
> in that would have any value.  Here is 'dmesg' for a recent kernel with
> "hpet=disable":

insert_resource/request_resource works well

can you verify if hpet work on old kernel?

cat /proc/timers*

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-22  1:24 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-22  1:24 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev




> insert_resource/request_resource works well
> 
> can you verify if hpet work on old kernel?
> 
> cat /proc/timers*

$ ls /proc/t*
/proc/timer_list

/proc/tty:
driver    drivers  ldisc    ldiscs

$ grep -B 1 -A 5 hpet /proc/timer_list 
Tick Device: mode:     1
Clock Event Device: hpet
 max_delta_ns:   149983005959
 min_delta_ns:   3352
 mult:           61496114
 shift:          32
 mode:           1
 next_event:     9223372036854775807 nsecs
 set_next_event: hpet_legacy_next_event
 set_mode:       hpet_legacy_set_mode
 event_handler:  tick_handle_oneshot_broadcast
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000


If there's anything else I can do, just ask!
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23  2:25 David Witbrodt
  2008-08-23  5:41 ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-23  2:25 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev


Yinghai,

I finally found time to try to get some output using your patch for
resource.c on a kernel that hangs.

Some really good advice came in earlier today:  I can use "vga=1" to
get 80x50 mode during the early boot sequence.  I used that, and made
some alterations to the changes in your patch to squeeze more info
onto the screen.  I also changed KERN_DEBUG to KERN_ERR in your
printk's so that I could decrease the other output by using 
"loglevel=4".

While I cannot see the entire set of output from your debug printk's,
I can see the last 45+ lines that appear before the hang.  The results
were the same as when I used "hpet=disable":  the only difference 
between the working 2.6.25 kernel and the hanging 2.6.27 kernel was 
that the resource named "0000:00:14.0" (fed00000-fed003ff) switched
from "conflict=0" to "conflict=1".

The output from 'cat /proc/iomem' on a non-hanging kernel included
these two lines:

fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0


None of this is really new information, since it matches with info
I've already posted.  I just wanted to let you know the results of
your patch on a kernel that hangs.

If I find a way to read the info from the 15-20 lines that scroll 
away on me, and if I find a difference, I'll post that as well.


DW

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23  2:25 David Witbrodt
@ 2008-08-23  5:41 ` Yinghai Lu
  2008-08-23  6:56   ` Yinghai Lu
  0 siblings, 1 reply; 41+ messages in thread
From: Yinghai Lu @ 2008-08-23  5:41 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

On Fri, Aug 22, 2008 at 7:25 PM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
> Yinghai,
>
> I finally found time to try to get some output using your patch for
> resource.c on a kernel that hangs.
>
> Some really good advice came in earlier today:  I can use "vga=1" to
> get 80x50 mode during the early boot sequence.  I used that, and made
> some alterations to the changes in your patch to squeeze more info
> onto the screen.  I also changed KERN_DEBUG to KERN_ERR in your
> printk's so that I could decrease the other output by using
> "loglevel=4".
>
> While I cannot see the entire set of output from your debug printk's,
> I can see the last 45+ lines that appear before the hang.  The results
> were the same as when I used "hpet=disable":  the only difference
> between the working 2.6.25 kernel and the hanging 2.6.27 kernel was
> that the resource named "0000:00:14.0" (fed00000-fed003ff) switched
> from "conflict=0" to "conflict=1".
>
> The output from 'cat /proc/iomem' on a non-hanging kernel included
> these two lines:
>
> fed00000-fed003ff : HPET 0
>  fed00000-fed003ff : 0000:00:14.0
that mean is hpet using insert_resource.


pnp 00:0d: mem resource (0xfed00000-0xfed000ff) overlaps 0000:00:14.0
BAR 1 (0xfed00000-0xfed003ff), disabling
request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.0) [fa00,
fa0f] conflict 0
request_resource: root: (PCI mem) [0, ffffffffffffffff], new:
(0000:00:14.0) [fed00000, fed003ff] conflict 1
pci 0000:00:14.0: BAR 1: can't allocate resource
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xfa00, revision 0


because  (0000:00:14.0) [fed00000, fed003ff]  conflicts to (reserved)
[fec00000, ffffffff] from e820.


kernel:
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel
code) [200000, 56ce41]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (Kernel code) [200000, 56ce41]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel
data) [56ce42, 6d5f3f]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (Kernel data) [56ce42, 6d5f3f]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (Kernel
bss) [773000, 7b7647]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (Kernel bss) [773000, 7b7647]

E820:
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (System
RAM) [0, 9f3ff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (System RAM) [0, 9f3ff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new:
(reserved) [9f400, 9ffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (reserved) [9f400, 9ffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new:
(reserved) [f0000, fffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (reserved) [f0000, fffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (System
RAM) [100000, 77fdffff]
 insert_resource: first: (Kernel code) [200000, 56ce41], new: (System
RAM) [100000, 77fdffff]
 insert_resource: direct parent: (PCI mem) [0, ffffffffffffffff], new:
(System RAM) [100000, 77fdffff]
   insert_resource: child: (Kernel code) [200000, 56ce41], new:
(System RAM) [100000, 77fdffff]
   insert_resource: child: (Kernel data) [56ce42, 6d5f3f], new:
(System RAM) [100000, 77fdffff]
   insert_resource: child: (Kernel bss) [773000, 7b7647], new: (System
RAM) [100000, 77fdffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI
Non-volatile Storage) [77fe0000, 77fe2fff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (ACPI Non-volatile Storage) [77fe0000,
77fe2fff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new: (ACPI
Tables) [77fe3000, 77feffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (ACPI Tables) [77fe3000, 77feffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new:
(reserved) [77ff0000, 77ffffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (reserved) [77ff0000, 77ffffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new:
(reserved) [e0000000, efffffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (reserved) [e0000000, efffffff]
insert_resource: parent: (PCI mem) [0, ffffffffffffffff], new:
(reserved) [fec00000, ffffffff]
   insert_resource: good with request direct parent: (PCI mem) [0,
ffffffffffffffff], new: (reserved) [fec00000, ffffffff]



so old kernel lapic 0xfee0000, is insert at first, it will prevent
0xfec, ... 0xfffffff from e820 to be registered,
then (0000:00:14.0) [fed00000, fed003ff] got chance to be
registered..., timer will work...


root cause could be the chipset BAR1
request_resource: root: (PCI mem) [0, ffffffffffffffff], new:
(0000:00:14.0) [fed00000, fed003ff] conflict 1
is not handled properly...

guess when it can not get request_resource, it could clear that
BAR1...may need one quirk to save that.
just like we trust IO APIC addr in BAR for some devices.

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23  5:41 ` Yinghai Lu
@ 2008-08-23  6:56   ` Yinghai Lu
  0 siblings, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-23  6:56 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

please send out after booting with hpet=disable
lspci -tv
lspci -vvxxx

YH

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 11:42 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 11:42 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> pnp 00:0d: mem resource (0xfed00000-0xfed000ff) overlaps 0000:00:14.0
> BAR 1 (0xfed00000-0xfed003ff), disabling
> request_resource: root: (PCI IO) [0, ffff], new: (0000:00:14.0) [fa00,
> fa0f] conflict 0
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new:
> (0000:00:14.0) [fed00000, fed003ff] conflict 1
> pci 0000:00:14.0: BAR 1: can't allocate resource
> piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xfa00, revision 0
> 
> 
> because  (0000:00:14.0) [fed00000, fed003ff]  conflicts to (reserved)
> [fec00000, ffffffff] from e820.

[...]

> so old kernel lapic 0xfee0000, is insert at first, it will prevent
> 0xfec, ... 0xfffffff from e820 to be registered,
> then (0000:00:14.0) [fed00000, fed003ff] got chance to be
> registered..., timer will work...
> 
> 
> root cause could be the chipset BAR1
> request_resource: root: (PCI mem) [0, ffffffffffffffff], new:
> (0000:00:14.0) [fed00000, fed003ff] conflict 1
> is not handled properly...
> 
> guess when it can not get request_resource, it could clear that
> BAR1...may need one quirk to save that.
> just like we trust IO APIC addr in BAR for some devices.

Ahh, thank you for reviewing that with me.  It looks like you are
getting very close to a fix.

FYI, I have asked the other user who first reported a similar problem
(back in May) to try booting his kernel with "hpet=disable" and
report his results here.  We cannot be sure that his problem is
identical to mine, but I believe he has been compiling his own
kernels since May by manually reverting commit number 3def3d6d.

I'm hoping that he will be able to help us test patches which attempt
to fix the problem, but my understanding is that he is using the
machine quite heavily... so he may not be willing to do as much
testing as I.

I do know that his kernel hangs at a different point in the kernel
sources:  mine hangs before inet_init() returns, while his hangs
in ide_scan_pcibus() [or pci_init(), if he tried to add printk's
to the previous function, trying to get more info].

I'm hoping that the changes in 3def3d6d aren't going to force the
kernel team to create a different quirk for each motherboard that
experiences kernel hangs!  Once 2.6.26, there is some possibility
that you will start seeing a lot more reports of it.  (I'm hoping
not, though.)


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 11:58 David Witbrodt
  2008-08-23 13:36 ` Ingo Molnar
  2008-08-23 17:51 ` Yinghai Lu
  0 siblings, 2 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 11:58 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]



> please send out after booting with hpet=disable
> lspci -tv
> lspci -vvxxx

Info attached:

[-- Attachment #2: lspci-2.6.27-rc4-hpet-disable.txt --]
[-- Type: text/plain, Size: 31494 bytes --]

# lspci -tv
-[0000:00]-+-00.0  ATI Technologies Inc RS690 Host Bridge
           +-01.0-[0000:01]--+-05.0  ATI Technologies Inc RS690 [Radeon X1200 Series]
           |                 \-05.2  ATI Technologies Inc Radeon X1200 Series Audio Controller
           +-12.0  ATI Technologies Inc SB600 Non-Raid-5 SATA
           +-13.0  ATI Technologies Inc SB600 USB (OHCI0)
           +-13.1  ATI Technologies Inc SB600 USB (OHCI1)
           +-13.2  ATI Technologies Inc SB600 USB (OHCI2)
           +-13.3  ATI Technologies Inc SB600 USB (OHCI3)
           +-13.4  ATI Technologies Inc SB600 USB (OHCI4)
           +-13.5  ATI Technologies Inc SB600 USB Controller (EHCI)
           +-14.0  ATI Technologies Inc SBx00 SMBus Controller
           +-14.1  ATI Technologies Inc SB600 IDE
           +-14.2  ATI Technologies Inc SBx00 Azalia
           +-14.3  ATI Technologies Inc SB600 PCI to LPC Bridge
           +-14.4-[0000:02]----05.0  Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet
           +-18.0  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
           +-18.1  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
           +-18.2  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
           \-18.3  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control

# lspci -vvxxx
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
	Subsystem: ATI Technologies Inc RS690 Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 64
00: 02 10 10 79 06 00 20 22 00 00 00 06 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 10 79
30: 00 00 00 00 c4 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 42 20 05 00
50: 02 10 10 79 ff 00 00 00 00 00 00 00 00 00 00 00
60: 5f 00 00 00 00 00 00 00 00 02 20 00 98 f8 01 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 40 44 00 00 95 00 00 03 20 01 10 00 02 27 00 00
90: 00 00 00 78 40 c4 40 e3 00 00 00 00 01 00 00 00
a0: 00 00 00 00 00 00 00 00 07 01 00 00 49 01 10 07
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 08 00 94 01 60 00 11 11 d0 00 00 00
d0: 25 06 65 00 02 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 7f 00 00 00 00 00 00 00
f0: 00 00 00 00 00 80 80 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 99
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fdd00000-fdefffff
	Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
00: 02 10 12 79 07 00 30 02 00 00 04 06 00 63 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 44 e1 e1 20 02
20: d0 fd e0 fd 01 d8 f1 df 00 00 00 00 00 00 00 00
30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 08 00
40: 00 00 00 00 08 b0 03 a8 00 00 00 00 02 10 12 79
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 0d 00 00 00 02 10 12 79 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01)
	Subsystem: Elitegroup Computer Systems Device 4382
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at ff00 [size=8]
	Region 1: I/O ports at fe00 [size=4]
	Region 2: I/O ports at fd00 [size=8]
	Region 3: I/O ports at fc00 [size=4]
	Region 4: I/O ports at fb00 [size=16]
	Region 5: Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [70] SATA HBA <?>
	Kernel driver in use: ahci
00: 02 10 80 43 07 00 30 02 00 01 06 01 00 40 00 00
10: 01 ff 00 00 01 fe 00 00 01 fd 00 00 01 fc 00 00
20: 01 fb 00 00 00 f0 02 fe 00 00 00 00 19 10 82 43
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 00 00
40: 10 00 80 02 01 00 10 00 01 00 00 00 00 00 00 00
50: 05 70 84 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 70 22 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 12 00 10 00 0f 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 06 00 00 2c d5 00 b4 00 d5 00 b4 00
90: d5 00 b4 00 d5 00 b4 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 78 00 00 00 00 00 00 00 78 00 00
b0: 00 00 00 00 00 78 00 00 00 00 00 00 00 78 00 00
c0: 00 20 00 00 80 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
00: 02 10 87 43 07 00 a0 02 00 10 03 0c 01 40 80 00
10: 00 e0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00
40: 80 1f 00 00 0a 84 b7 18 07 35 00 00 00 00 00 00
50: 00 1c 00 00 00 00 00 00 ff ff ff ff ff 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 ff 00 00 80 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
00: 02 10 88 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 d0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
00: 02 10 89 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 c0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
00: 02 10 8a 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 b0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
00: 02 10 8b 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 a0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 19
	Region 0: Memory at fe029000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
		Bridge: PM- B3+
	Capabilities: [e4] Debug port: BAR=1 offset=00e0
	Kernel driver in use: ehci_hcd
00: 02 10 86 43 17 00 b0 02 00 20 03 0c 10 40 00 00
10: 00 90 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 c0 00 00 00 00 00 00 00 0b 04 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 40 00 0e 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 20 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 01 00 00 01 00 00 08 c0 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 e4 02 7e 00 00 40 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 0a 00 e0 20 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 13)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: I/O ports at fa00 [size=16]
	Region 1: Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+
	Kernel driver in use: piix4_smbus
00: 02 10 85 43 03 04 30 02 13 00 05 0c 00 00 80 00
10: 01 fa 00 00 00 00 00 80 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 b0 00 00 00 00 00 00 00 00 00 00 00
40: d4 3b 00 05 00 00 00 00 0f ff 00 00 00 00 00 00
50: f0 01 f0 0e f0 0f f0 07 11 0b f0 0f 00 00 00 00
60: 01 00 24 00 bf fd de 8f 3f 90 00 00 20 00 00 00
70: 00 01 00 00 08 00 c0 fe ff 6e 00 00 00 00 f0 0f
80: f0 0a f0 0f 00 00 00 00 00 00 00 00 8c 00 00 80
90: 01 fa 00 00 fa de ff 00 00 00 00 00 00 00 00 00
a0: 00 00 ff ff ff ff f0 08 ff fd 12 02 16 7b 20 00
b0: 08 00 02 a8 00 00 00 00 00 00 00 00 f0 0f 08 1a
c0: ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: d8 0c 00 00 00 00 44 00 00 00 00 00 aa 00 10 01

00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at 01f0 [size=8]
	Region 1: I/O ports at 03f4 [size=1]
	Region 2: I/O ports at 0170 [size=8]
	Region 3: I/O ports at 0374 [size=1]
	Region 4: I/O ports at f900 [size=16]
	Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Kernel driver in use: ATIIXP_IDE
00: 02 10 8c 43 05 00 30 02 00 8a 01 01 00 40 00 00
10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
20: 01 f9 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 70 00 00 00 00 00 00 00 ff 01 00 00
40: 20 20 00 00 20 20 00 00 00 00 44 00 00 00 00 00
50: 00 00 00 00 03 00 25 00 00 00 00 00 00 00 00 00
60: 00 00 40 00 10 2c 01 07 01 00 00 00 ff ff 0f 00
70: 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin ? routed to IRQ 16
	Region 0: Memory at fe020000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: HDA Intel
00: 02 10 83 43 06 00 10 04 00 00 03 04 01 40 00 00
10: 04 00 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 50 00 00 00 00 00 00 00 03 00 00 00
40: 00 00 02 00 00 00 00 00 00 00 00 00 01 00 00 00
50: 01 60 42 c8 00 00 00 00 00 00 00 00 00 00 00 00
60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
00: 02 10 8d 43 0f 00 20 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 04 00 00 00 ff ff c3 ff 3f ff 42 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 0a 00 00 0e 00 0f 00 f8 ff ff ff
70: 67 45 23 01 00 00 00 00 01 00 00 00 05 00 00 00
80: 08 00 03 a8 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fdc00000-fdcfffff
	Prefetchable memory behind bridge: fdf00000-fdffffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
00: 02 10 84 43 27 00 a0 02 00 01 04 06 00 40 81 00
10: 00 00 00 00 00 00 00 00 00 02 02 40 d0 d0 80 22
20: c0 fd c0 fd f0 fd f0 fd 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 26 00 30 ff 00 00 00 00 0c 01 3e d1 00 00 00 00
50: 01 00 00 00 08 00 03 a8 00 00 00 00 85 00 ff ff
60: ca 0e 17 00 8a 18 10 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 06
e0: 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: [80] HyperTransport: Host or Secondary Interface
		!!! Possibly incomplete decoding
		Command: WarmRst+ DblEnd-
		Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
		Link Config: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
		Revision ID: 1.02
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
60: 00 00 01 00 e4 00 00 00 20 c8 2f 0f 0c 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 08 00 01 21 20 00 11 11 22 06 75 80 02 00 00 00
90: 78 01 70 01 00 00 02 00 07 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 03 00 00 00 00 00 7f 00 00 00 00 00 01 00 00 00
50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00
60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00
70: 00 00 00 00 06 00 00 00 00 00 00 00 07 00 00 00
80: 03 0a 00 00 00 0b 00 00 03 00 d8 00 80 ff df 00
90: 03 00 80 00 00 ff d7 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 03 00 f0 00 00 02 fe 00
b0: 03 00 e0 00 80 2f e0 00 00 00 00 00 00 00 00 00
c0: 13 d0 00 00 00 f0 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 03 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 01 00 00 00 01 01 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: e0 3e 78 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 46 00 00 00 00 00 00 00
80: 02 00 00 00 00 00 00 00 24 f2 7d 5d 20 13 12 00
90: 10 0c 01 00 6b 00 10 b7 39 00 00 80 00 00 00 00
a0: ef 02 00 5d 00 00 00 00 00 00 00 00 00 00 00 00
b0: 04 57 ea 8f aa 00 00 00 ed d4 10 62 d8 60 90 01
c0: 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 27 c5 01 68 ff 34 0d c9 ea 94 0b c9 6f 92 01 89
e0: cf d4 21 09 e3 94 c8 69 ff 96 0f 4d ce d4 80 58
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: [f0] Secure device <?>
	Kernel driver in use: k8temp
00: 22 10 03 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 f0 00 00 00 00 00 00 00 00 00 00 00
40: ff 3b 04 00 40 00 10 0a 00 00 00 00 00 00 00 00
50: 20 48 0a 88 90 00 00 00 00 00 00 00 c0 9a 0a 2b
60: 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 11 01 32 51 21 40 30 50 00 2a 00 08 17 21 00 00
80: 00 00 07 23 13 21 13 21 00 00 00 00 00 00 00 00
90: 00 00 00 00 66 17 00 00 a0 f6 19 4b 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 01 a7 0d 00 00 00 a0 08 25 26 26 00
e0: 00 00 00 00 3e 21 35 00 19 17 00 00 00 00 00 00
f0: 0f 00 10 00 00 00 00 00 00 00 00 00 b2 0f 06 00

01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series]
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at d8000000 (64-bit, prefetchable) [size=128M]
	Region 2: Memory at fdee0000 (64-bit, non-prefetchable) [size=64K]
	Region 4: I/O ports at ee00 [size=256]
	Region 5: Memory at fdd00000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
00: 02 10 1e 79 07 00 10 00 00 00 00 03 01 40 80 00
10: 0c 00 00 d8 00 00 00 00 04 00 ee fd 00 00 00 00
20: 01 ee 00 00 00 00 d0 fd 00 00 00 00 19 10 21 26
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
50: 01 80 02 06 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller
	Subsystem: ATI Technologies Inc Radeon X1200 Series Audio Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 4 bytes
	Interrupt: pin B routed to IRQ 19
	Region 0: Memory at fdefc000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: HDA Intel
00: 02 10 19 79 06 00 10 00 00 00 03 04 01 40 00 00
10: 04 c0 ef fd 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 19 79
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 19 79
50: 01 60 02 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
	Subsystem: Elitegroup Computer Systems Device 8167
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 22
	Region 0: I/O ports at de00 [size=256]
	Region 1: Memory at fdcff000 (32-bit, non-prefetchable) [size=256]
	[virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: r8169
00: ec 10 67 81 17 00 b0 02 10 00 00 02 08 40 00 00
10: 01 de 00 00 00 f0 cf fd 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 67 81
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 20 40
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 c2 f7
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23 11:58 David Witbrodt
@ 2008-08-23 13:36 ` Ingo Molnar
  2008-08-23 15:03   ` Ingo Molnar
  2008-08-23 17:51 ` Yinghai Lu
  1 sibling, 1 reply; 41+ messages in thread
From: Ingo Molnar @ 2008-08-23 13:36 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev


David,

could you try the debug patch below ontop of latest tip/master:

  http://people.redhat.com/mingo/tip.git/README

the patch forcibly ignores resource conflicts and reports them. This 
will likely break some system - but if your hpet troubles are due to 
resource conflicts then this patch would make the kernel boot up fine on 
your system by default, with a working hpet.

You should also be getting a printout and a warning in the dmesg in that 
case.

	Ingo

------------>
>From 092990e259a462d39f1d8e9cd542898632b95fde Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@elte.hu>
Date: Sat, 23 Aug 2008 15:33:51 +0200
Subject: [PATCH] debug hack: ignore resource conflicts

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 kernel/resource.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/kernel/resource.c b/kernel/resource.c
index f5b518e..8419d56 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -156,6 +156,7 @@ static struct resource * __request_resource(struct resource *root, struct resour
 	for (;;) {
 		tmp = *p;
 		if (!tmp || tmp->start > end) {
+insert:
 			new->sibling = tmp;
 			*p = new;
 			new->parent = root;
@@ -164,7 +165,9 @@ static struct resource * __request_resource(struct resource *root, struct resour
 		p = &tmp->sibling;
 		if (tmp->end < start)
 			continue;
-		return tmp;
+		printk("ignoring resource conflict between %s/{%p..%p} and %s/{%p..%p}\n", new->name, (void *)new->start, (void *)new->end, tmp->name, (void *)tmp->start, (void *)tmp->end);
+		WARN_ON(1);
+		goto insert;
 	}
 }
 

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23 13:36 ` Ingo Molnar
@ 2008-08-23 15:03   ` Ingo Molnar
  0 siblings, 0 replies; 41+ messages in thread
From: Ingo Molnar @ 2008-08-23 15:03 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev


* Ingo Molnar <mingo@elte.hu> wrote:

> could you try the debug patch below ontop of latest tip/master:

please use the replacement debug patch below. (the previous one was 
buggy, it would likely lock up because it iterated incorrectly.)

[ and i'd also like to stress that this isnt a solution, this is a debug
  hack that can lead to a solution. ]

	Ingo

-------------->
>From dc1c9cafd20edacb14e902c5ee72547f14c12545 Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@elte.hu>
Date: Sat, 23 Aug 2008 15:33:51 +0200
Subject: [PATCH] debug: ignore resource conflicts

---
 kernel/resource.c |   10 +++++++---
 1 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/kernel/resource.c b/kernel/resource.c
index f5b518e..45877ec 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -156,15 +156,19 @@ static struct resource * __request_resource(struct resource *root, struct resour
 	for (;;) {
 		tmp = *p;
 		if (!tmp || tmp->start > end) {
+insert:
 			new->sibling = tmp;
 			*p = new;
 			new->parent = root;
 			return NULL;
 		}
-		p = &tmp->sibling;
-		if (tmp->end < start)
+		if (tmp->end < start) {
+			p = &tmp->sibling;
 			continue;
-		return tmp;
+		}
+		printk("ignoring resource conflict between %s/{%p..%p} and %s/{%p..%p}\n", new->name, (void *)new->start, (void *)new->end, tmp->name, (void *)tmp->start, (void *)tmp->end);
+		WARN_ON(1);
+		goto insert;
 	}
 }
 

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 15:42 David Witbrodt
  2008-08-23 15:55 ` Ingo Molnar
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 15:42 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> could you try the debug patch below ontop of latest tip/master:
> 
>   http://people.redhat.com/mingo/tip.git/README

Thanks Ingo.

I've been building your 'tip/master' tree daily (Just In Case) since 
Aug. 11, when you first asked me to try it!  ;)


> the patch forcibly ignores resource conflicts and reports them. This 
> will likely break some system - but if your hpet troubles are due to 
> resource conflicts then this patch would make the kernel boot up fine on 
> your system by default, with a working hpet.
> 
> You should also be getting a printout and a warning in the dmesg in that 
> case.

No offense... but this patch does something Bad.  [BTW, if you send patches
for me to try in the future, could you make them attachments?  I have not
replaced my old email system with the new one which uses my newer "server"
machines, so I have been temporarily forced to use my ISP's _broken_ web
interface for email.  Not only does that web client break threading in
LKML inboxes -- sorry folks! -- it messes up the whitespace in patches, so
I have to apply them manually, unless they are provided as attachments.]

It built OK, but when I rebooted it hung _extremely_ early.  All I got was

- 2 lines of GRUB output
- kernel boot parameters (maybe also from GRUB)
- "Decompressing Linux... Parsing ELF... done."
- "Booting the kernel"

... and there it hung.

I had forgotten to turn on debugging parameters, so I applied my own reduced
version of Yinghai's debugging patch for resource.c, and enabled 80x50 text
mode and set "loglevel=4", hoping I could tell you more about where the
kernel was hanging with your new patch.

Rebooting with those changes, the output was identical to the above.  The
kernel freezes before any calls of insert_resource() or request_resource().

I tried a third reboot, with "debug initcall_debug"... but the results
were the same.  The kernel hangs almost immediately with the patch you
sent.


[In case my own changes are suspect, I am providing the diff for resource.c
against the original tip/master version -- but this only shows the changes
made for the second and third reboots.  The first reboot was with a 
tip/master kernel using only the patch you sent me applied.]

$ git diff kernel/resource.c
diff --git a/kernel/resource.c b/kernel/resource.c
index f5b518e..167f385 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -156,6 +156,7 @@ static struct resource * __request_resource(struct resource *root, struct resour
     for (;;) {
         tmp = *p;
         if (!tmp || tmp->start > end) {
+insert:
             new->sibling = tmp;
             *p = new;
             new->parent = root;
@@ -164,7 +165,10 @@ static struct resource * __request_resource(struct resource *root, struct resour
         p = &tmp->sibling;
         if (tmp->end < start)
             continue;
-        return tmp;
+        printk("ignoring resource conflict between %s/{%p..%p} and %s/{%p..%p}\n", new->name, 
+               (void *)new->start, (void *)new->end, tmp->name, (void *)tmp->start, (void *)tmp->end);
+        WARN_ON(1);
+        goto insert;
     }
 }
 
@@ -197,10 +201,20 @@ static int __release_resource(struct resource *old)
 int request_resource(struct resource *root, struct resource *new)
 {
     struct resource *conflict;
+     resource_size_t  dstart, dend;
+     char has_conflict;
 
     write_lock(&resource_lock);
     conflict = __request_resource(root, new);
     write_unlock(&resource_lock);
+ 
+     dstart = new->start - root->start;
+     dend = root->end - new->end;
+     has_conflict = conflict ? '!' : ' ';
+ 
+     printk(KERN_ERR "R:%-12.12s%8llx-%-16llx(%c%-12.12s-%-6llx+%-6llx)\n", new->name, new->start, new->end,
+            has_conflict, root->name, dstart, dend);
+ 
     return conflict ? -EBUSY : 0;
 }
 
@@ -382,11 +396,15 @@ int insert_resource(struct resource *parent, struct resource *new)
 
     write_lock(&resource_lock);
 
+     printk(KERN_ERR "I:%-12.12s%8llx-%-16llx(P=%-12.12s)... ", new->name, new->start, new->end, parent->name);
+ 
     for (;; parent = first) {
          result = 0;
         first = __request_resource(parent, new);
-        if (!first)
-            goto out;
+         if (!first) {
+                 printk(KERN_ERR "good(P=%-12.12s)\n", parent->name);
+              goto out;
+         }
 
         result = -EBUSY;
         if (first == parent)
@@ -414,9 +432,13 @@ int insert_resource(struct resource *parent, struct resource *new)
     new->sibling = next->sibling;
     new->child = first;
 
+     printk(KERN_ERR "in(P=%-12.12s)... ", parent->name);
+ 
     next->sibling = NULL;
-    for (next = first; next; next = next->sibling)
-        next->parent = new;
+     for (next = first; next; next = next->sibling) {
+          next->parent = new;
+         printk(KERN_ERR "ch=%-12.12s\n", next->name);
+     }
 
     if (parent->child == first) {
         parent->child = new;

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23 15:42 David Witbrodt
@ 2008-08-23 15:55 ` Ingo Molnar
  0 siblings, 0 replies; 41+ messages in thread
From: Ingo Molnar @ 2008-08-23 15:55 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev


* David Witbrodt <dawitbro@sbcglobal.net> wrote:

>      for (;;) {
>          tmp = *p;
>          if (!tmp || tmp->start > end) {
> +insert:
>              new->sibling = tmp;
>              *p = new;
>              new->parent = root;
> @@ -164,7 +165,10 @@ static struct resource * __request_resource(struct resource *root, struct resour
>          p = &tmp->sibling;
>          if (tmp->end < start)
>              continue;
> -        return tmp;
> +        printk("ignoring resource conflict between %s/{%p..%p} and %s/{%p..%p}\n", new->name, 
> +               (void *)new->start, (void *)new->end, tmp->name, (void *)tmp->start, (void *)tmp->end);
> +        WARN_ON(1);
> +        goto insert;

sorry about that, my first patch was more broken than i thought (it will 
basically hang on _any_ box), please try the second patch.

Note how the above hack code does a stupid goto, and 'p' is updated for 
the next loop iteration already. The second version of the debug patch 
only updates 'p' in the 'continue' case and will hopefully get you much 
further into bootup!

	Ingo

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 16:32 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 16:32 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

[-- Attachment #1: Type: text/plain, Size: 7053 bytes --]



> > could you try the debug patch below ontop of latest tip/master:
> 
> please use the replacement debug patch below. (the previous one was 
> buggy, it would likely lock up because it iterated incorrectly.)

Oops!  My fault.  I was composing my reply a bit at a time, adding
stuff with each reboot, and couldn't see my inbox had this followup
from you before I hit Send.

> [ and i'd also like to stress that this isnt a solution, this is a debug
>   hack that can lead to a solution. ]

ACK.

Personally, if I had champagne here, I'd have popped the cork already.
This is the first 2.6.2[67] kernel I've had that can boot without
"hpet=ignore" or reverting the 2 commits from February.

Here are the messages about ignoring conflicts.  The full 'dmesg' output
is attached -- gzip'ed because it was over 100K (I used kernel parameters
"debug initcall_debug", and a bunch of unexpected stack traces also
appeared).


$ dmesg | grep ^ignoring
ignoring resource conflict between System RAM/{0000000000100000..0000000077fdffff} and Kernel code/{0000000000200000..000000000058b008}
ignoring resource conflict between 0000:00:14.0/{00000000fed00000..00000000fed003ff} and reserved/{00000000fec00000..00000000ffffffff}
ignoring resource conflict between pnp 00:0c/{00000000e0000000..00000000efffffff} and reserved/{00000000e0000000..00000000efffffff}
ignoring resource conflict between pnp 00:0d/{00000000000f0000..00000000000fffff} and reserved/{00000000000f0000..00000000000fffff}
ignoring resource conflict between pnp 00:0d/{0000000077fe0000..0000000077ffffff} and ACPI Non-volatile Storage/{0000000077fe0000..0000000077fe2fff}
ignoring resource conflict between pnp 00:0d/{00000000ffff0000..00000000ffffffff} and reserved/{00000000fec00000..00000000ffffffff}
ignoring resource conflict between pnp 00:0d/{0000000000000000..000000000009ffff} and System RAM/{0000000000000000..000000000009f3ff}
ignoring resource conflict between pnp 00:0d/{0000000000100000..0000000077fdffff} and System RAM/{0000000000100000..0000000077fdffff}
ignoring resource conflict between ehci_hcd/{00000000fe029000..00000000fe0290ff} and 0000:00:13.5/{00000000fe029000..00000000fe0290ff}
ignoring resource conflict between ohci_hcd/{00000000fe02e000..00000000fe02efff} and 0000:00:13.0/{00000000fe02e000..00000000fe02efff}
ignoring resource conflict between ohci_hcd/{00000000fe02d000..00000000fe02dfff} and 0000:00:13.1/{00000000fe02d000..00000000fe02dfff}
ignoring resource conflict between ohci_hcd/{00000000fe02c000..00000000fe02cfff} and 0000:00:13.2/{00000000fe02c000..00000000fe02cfff}
ignoring resource conflict between ohci_hcd/{00000000fe02b000..00000000fe02bfff} and 0000:00:13.3/{00000000fe02b000..00000000fe02bfff}
ignoring resource conflict between ohci_hcd/{00000000fe02a000..00000000fe02afff} and 0000:00:13.4/{00000000fe02a000..00000000fe02afff}
ignoring resource conflict between uvesafb/{00000000d8000000..00000000d8ffffff} and PCI Bus 0000:01/{00000000d8000000..00000000dfffffff}
ignoring resource conflict between uvesafb/{00000000000003c0..00000000000003df} and vga+/{00000000000003c0..00000000000003df}
ignoring resource conflict between ACPI PM1a_EVT_BLK/{0000000000004000..0000000000004003} and pnp 00:01/{0000000000004000..00000000000040fe}
ignoring resource conflict between ACPI PM1a_CNT_BLK/{0000000000004004..0000000000004005} and pnp 00:01/{0000000000004000..00000000000040fe}
ignoring resource conflict between ACPI PM_TMR/{0000000000004008..000000000000400b} and pnp 00:01/{0000000000004000..00000000000040fe}
ignoring resource conflict between ACPI PM2_CNT_BLK/{0000000000004050..0000000000004050} and pnp 00:01/{0000000000004000..00000000000040fe}
ignoring resource conflict between ACPI CPU throttle/{0000000000004010..0000000000004015} and ACPI CPU throttle/{0000000000004010..0000000000004015}
ignoring resource conflict between r8169/{000000000000de00..000000000000deff} and PCI Bus 0000:02/{000000000000d000..000000000000dfff}
ignoring resource conflict between r8169/{00000000fdcff000..00000000fdcff0ff} and PCI Bus 0000:02/{00000000fdc00000..00000000fdcfffff}
ignoring resource conflict between atiixp/{00000000000001f0..00000000000001f7} and 0000:00:14.1/{00000000000001f0..00000000000001f7}
ignoring resource conflict between atiixp/{00000000000003f6..00000000000003f6} and 0000:00:14.1/{00000000000003f6..00000000000003f6}
ignoring resource conflict between atiixp/{000000000000f900..000000000000f90f} and 0000:00:14.1/{000000000000f900..000000000000f90f}
ignoring resource conflict between ide_generic/{00000000000001f0..00000000000001f7} and atiixp/{00000000000001f0..00000000000001f7}
ignoring resource conflict between ide_generic/{00000000000003f6..00000000000003f6} and atiixp/{00000000000003f6..00000000000003f6}
ignoring resource conflict between ide_generic/{0000000000000170..0000000000000177} and 0000:00:14.1/{0000000000000170..0000000000000177}
ignoring resource conflict between ide_generic/{0000000000000376..0000000000000376} and 0000:00:14.1/{0000000000000376..0000000000000376}
ignoring resource conflict between ahci/{000000000000ff00..000000000000ff07} and 0000:00:12.0/{000000000000ff00..000000000000ff07}
ignoring resource conflict between ahci/{000000000000fe00..000000000000fe03} and 0000:00:12.0/{000000000000fe00..000000000000fe03}
ignoring resource conflict between ahci/{000000000000fd00..000000000000fd07} and 0000:00:12.0/{000000000000fd00..000000000000fd07}
ignoring resource conflict between ahci/{000000000000fc00..000000000000fc03} and 0000:00:12.0/{000000000000fc00..000000000000fc03}
ignoring resource conflict between ahci/{000000000000fb00..000000000000fb0f} and 0000:00:12.0/{000000000000fb00..000000000000fb0f}
ignoring resource conflict between ahci/{00000000fe02f000..00000000fe02f3ff} and 0000:00:12.0/{00000000fe02f000..00000000fe02f3ff}
ignoring resource conflict between piix4_smbus/{000000000000fa00..000000000000fa07} and 0000:00:14.0/{000000000000fa00..000000000000fa0f}
ignoring resource conflict between ICH HD audio/{00000000fe020000..00000000fe023fff} and 0000:00:14.2/{00000000fe020000..00000000fe023fff}
ignoring resource conflict between ICH HD audio/{00000000fdefc000..00000000fdefffff} and PCI Bus 0000:01/{00000000fdd00000..00000000fdefffff}
ignoring resource conflict between HPET 0/{00000000fed00000..00000000fed003ff} and 0000:00:14.0/{00000000fed00000..00000000fed003ff}
ignoring resource conflict between Local APIC/{00000000fee00000..00000000fee00fff} and pnp 00:0d/{00000000fee00000..00000000fee00fff}
ignoring resource conflict between IOAPIC 0/{00000000fec00000..00000000fec00fff} and pnp 00:0d/{00000000fec00000..00000000fec00fff}
ignoring resource conflict between PCI MMCONFIG 0/{00000000e0000000..00000000efffffff} and pnp 00:0c/{00000000e0000000..00000000efffffff}
ignoring resource conflict between serial-rsa/{00000000000003f0..00000000000003f7} and ide_generic/{00000000000003f6..00000000000003f6}
ignoring resource conflict between serial-rsa/{00000000000003f0..00000000000003f7} and ide_generic/{00000000000003f6..00000000000003f6}


Thanks Ingo,
Dave W.

[-- Attachment #2: dmesg-2.6.27-tip-master-49292a74.txt.gz --]
[-- Type: application/gzip, Size: 15987 bytes --]

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 16:44 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 16:44 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Yinghai Lu, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> sorry about that, my first patch was more broken than i thought (it will 
> basically hang on _any_ box), please try the second patch.

No complaints here.  When I made myself and my machines available to help
with this regression, that included the possibility of errors.

I just send a message with the output of 'dmesg | grep ^ignoring', along
with the full 'dmesg' output gzipped.  My crummy ISP webmail interface
may have choked on it, so if you don't get that output before you see
this, then let me know so I can resend it.  (It's over 100K, though --
should I reduce the CC line first, if I have to resend?)


> Note how the above hack code does a stupid goto, and 'p' is updated for 
> the next loop iteration already. The second version of the debug patch 
> only updates 'p' in the 'continue' case and will hopefully get you much 
> further into bootup!

*sniff*
*wiping tears*

I don't care if you DO make mistakes... I LOVE you guys, man!

If you folks can fix this, then I owe anybody involved a cube of their 
favorite beer!  I'm not a beer drinker myself....  I'll just have green
tea.  ;)


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23 11:58 David Witbrodt
  2008-08-23 13:36 ` Ingo Molnar
@ 2008-08-23 17:51 ` Yinghai Lu
  1 sibling, 0 replies; 41+ messages in thread
From: Yinghai Lu @ 2008-08-23 17:51 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

On Sat, Aug 23, 2008 at 4:58 AM, David Witbrodt <dawitbro@sbcglobal.net> wrote:
>
>
>> please send out after booting with hpet=disable
>> lspci -tv
>> lspci -vvxxx
>
> Info attached:

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 13)
	Subsystem: Elitegroup Computer Systems Device 2621
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: I/O ports at fa00 [size=16]
	Region 1: Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+
	Kernel driver in use: piix4_smbus
00: 02 10 85 43 03 04 30 02 13 00 05 0c 00 00 80 00
10: 01 fa 00 00 00 00 00 80 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 b0 00 00 00 00 00 00 00 00 00 00 00
40: d4 3b 00 05 00 00 00 00 0f ff 00 00 00 00 00 00
50: f0 01 f0 0e f0 0f f0 07 11 0b f0 0f 00 00 00 00
60: 01 00 24 00 bf fd de 8f 3f 90 00 00 20 00 00 00
70: 00 01 00 00 08 00 c0 fe ff 6e 00 00 00 00 f0 0f
80: f0 0a f0 0f 00 00 00 00 00 00 00 00 8c 00 00 80
90: 01 fa 00 00 fa de ff 00 00 00 00 00 00 00 00 00
a0: 00 00 ff ff ff ff f0 08 ff fd 12 02 16 7b 20 00
b0: 08 00 02 a8 00 00 00 00 00 00 00 00 f0 0f 08 1a
c0: ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: d8 0c 00 00 00 00 44 00 00 00 00 00 aa 00 10 01

it seems kernel update BAR1 from 0xfed00000 to 0x80000000 after it can
not give 0xfed00000 to that device.

please try attached patch, and send out lspci -vvxxxx again.

YH

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: hpet_in_bar1.patch --]
[-- Type: text/x-patch; name=hpet_in_bar1.patch, Size: 1359 bytes --]

[PATCH] x86: protect hpet in BAR for one ATI chipset

so avoid kernel don't allocate nre resource for it because it can not allocate the old
address from BIOS.

the same way like some IO APIC address in BAR handling

Signed-off-by: Yinghai Lu <yhlu.kenrel@gmail.com>

---
 drivers/pci/quirks.c |   16 ++++++++++++++++
 1 file changed, 16 insertions(+)

Index: linux-2.6/drivers/pci/quirks.c
===================================================================
--- linux-2.6.orig/drivers/pci/quirks.c
+++ linux-2.6/drivers/pci/quirks.c
@@ -1918,6 +1918,22 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_B
 			 PCI_DEVICE_ID_NX2_5709S,
 			 quirk_brcm_570x_limit_vpd);
 
+static void __init quirk_hpet_in_bar(struct pci_dev *pdev)
+{
+	int i;
+	unsigned int base, size;
+
+	/* the BAR1 is the location of the HPET...we must
+	 * not touch this, so forcibly insert it into the resource tree */
+	base = pci_resource_start(pdev, 1);
+	size = pci_resource_len(pdev, 1);
+	if (base && size) {
+		insert_resource(&iomem_resource, &pdev->resource[1]);
+		dev_info(&dev->dev, "HPET at %04x-%04x\n", name, base, base + size - 1);
+	}
+}
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATI, 0x3485, quirk_hpet_in_bar);
+
 #ifdef CONFIG_PCI_MSI
 /* Some chipsets do not support MSI. We cannot easily rely on setting
  * PCI_BUS_FLAGS_NO_MSI in its bus flags because there are actually

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 19:29 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 19:29 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Bill Fink, linux-kernel,
	Paul E. McKenney, Peter Zijlstra, Thomas Gleixner, H. Peter Anvin,
	netdev



> please try attached patch, and send out lspci -vvxxxx again.

I found that your patch was supposed to apply beginning at line 1918,
but the code in v2.6.27-rc4 that corresponded to the patch actually
was located at line 1790.

I also found that it would not compile, but was able to fix it...
hopefully somewhat as you intended:
========================
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 9236e7f..7853a05 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -1790,6 +1790,22 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM,
              PCI_DEVICE_ID_NX2_5709S,
              quirk_brcm_570x_limit_vpd);
 
+static void __init quirk_hpet_in_bar(struct pci_dev *pdev)
+{
+        /* int i; */
+    unsigned int base, size;
+
+    /* the BAR1 is the location of the HPET...we must
+     * not touch this, so forcibly insert it into the resource tree */
+    base = pci_resource_start(pdev, 1);
+    size = pci_resource_len(pdev, 1);
+    if (base && size) {
+        insert_resource(&iomem_resource, &pdev->resource[1]);
+        dev_info(&pdev->dev, "HPET at %04x-%04x\n", base, base + size - 1);
+    }
+}
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATI, 0x3485, quirk_hpet_in_bar);
+
 #ifdef CONFIG_PCI_MSI
 /* Some chipsets do not support MSI. We cannot easily rely on setting
  * PCI_BUS_FLAGS_NO_MSI in its bus flags because there are actually
========================

With these changes, the kernel still hangs at the same point as previous
kernels.

With "hpet=disable", nothing from your dev_info() call appears in 'dmesg'
output.


Dave W.

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 20:00 David Witbrodt
  2008-08-23 20:13 ` Rufus & Azrael
  0 siblings, 1 reply; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 20:00 UTC (permalink / raw)
  To: Rufus & Azrael
  Cc: Yinghai Lu, Ingo Molnar, Vivek Goyal, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev



> Thanks Yinghai,
> 
> Your patch applied, I attach lspci -vvxxxx.
> 
> Regards.

Hello "Rufus & Azrael",

Are you experiencing the same difficulties with kernels hanging after
version 2.6.25?

In my case, kernels before 2.6.26 worked fine, but all kernels since
2.6.26 hang during boot, and the problem was traced (using 'git bisect')
to commit number 3def3d6d.

Please let me know your situation.


Thanks,
Dave W.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
  2008-08-23 20:00 David Witbrodt
@ 2008-08-23 20:13 ` Rufus & Azrael
  0 siblings, 0 replies; 41+ messages in thread
From: Rufus & Azrael @ 2008-08-23 20:13 UTC (permalink / raw)
  To: David Witbrodt
  Cc: Yinghai Lu, Ingo Molnar, Vivek Goyal, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev

David Witbrodt wrote:
>    
>> Thanks Yinghai,
>>
>> Your patch applied, I attach lspci -vvxxxx.
>>
>> Regards.
>>      
>
> Hello "Rufus&  Azrael",
>
> Are you experiencing the same difficulties with kernels hanging after
> version 2.6.25?
>
> In my case, kernels before 2.6.26 worked fine, but all kernels since
> 2.6.26 hang during boot, and the problem was traced (using 'git bisect')
> to commit number 3def3d6d.
>
> Please let me know your situation.
>
>
> Thanks,
> Dave W.
>
>    
Hello David,

I have no such hanging on my recent kernels, just the dmesg :

> [    1.057255] hpet_resources: 0xfed00000 is busy
and I find the present post to try solving this regression.

Regards.



^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 23:09 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 23:09 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Ingo Molnar, Vivek Goyal, Paul E. McKenney, Peter Zijlstra,
	Thomas Gleixner, H. Peter Anvin, netdev, Rufus & Azrael


> dmesg and lspci -vvxxx with hpet=disable?
> 
> please boot with "debug initcall_debug hpet=disable"

Sorry, Yinghai.  I decided to shutdown for a time because of bad
thunderstorms.  Here is the requested output:

$ dmesg
Linux version 2.6.27-rc4.080823.hpet+bar1 (dawitbro@fileserver) (gcc version 4.3.1 (Debian 4.3.1-2) ) #1 SMP Sat Aug 23 15:40:47 EDT 2008
Command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug initcall_debug hpet=disable
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
 BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000077fe0000 (usable)
 BIOS-e820: 0000000077fe0000 - 0000000077fe3000 (ACPI NVS)
 BIOS-e820: 0000000077fe3000 - 0000000077ff0000 (ACPI data)
 BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
last_pfn = 0x77fe0 max_arch_pfn = 0x3ffffffff
init_memory_mapping
 0000000000 - 0077e00000 page 2M
 0077e00000 - 0077fe0000 page 4k
kernel direct mapping tables up to 77fe0000 @ 8000-c000
last_map_addr: 77fe0000 end: 77fe0000
DMI 2.5 present.
ACPI: RSDP 000F7B80, 0024 (r2 RS690 )
ACPI: RSDT 77FE3040, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: FACP 77FE30C0, 0074 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: DSDT 77FE3180, 4B0B (r1 RS690  AWRDACPI     1000 MSFT  3000000)
ACPI: FACS 77FE0000, 0040
ACPI: SSDT 77FE7DC0, 028A (r1 PTLTD  POWERNOW        1  LTP        1)
ACPI: HPET 77FE80C0, 0038 (r1 RS690  AWRDACPI 42302E31 AWRD       98)
ACPI: MCFG 77FE8140, 003C (r1 RS690  AWRDACPI 42302E31 AWRD        0)
ACPI: APIC 77FE7D00, 0068 (r1 RS690  AWRDACPI 42302E31 AWRD        0)
No NUMA configuration found
Faking a node at 0000000000000000-0000000077fe0000
Bootmem setup node 0 0000000000000000-0000000077fe0000
  NODE_DATA [0000000000001000 - 0000000000004fff]
  bootmap [000000000000a000 -  0000000000018fff] pages f
(5 early reservations) ==> bootmem [0000000000 - 0077fe0000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
  #2 [0000200000 - 0000f3db48]    TEXT DATA BSS ==> [0000200000 - 0000f3db48]
  #3 [000009f000 - 0000100000]    BIOS reserved ==> [000009f000 - 0000100000]
  #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
found SMP MP-table at [ffff8800000f3c80] 000f3c80
 [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000000 -> 0x0000009f
    0: 0x00000100 -> 0x00077fe0
On node 0 totalpages: 491391
  DMA zone: 418 pages, LIFO batch:0
  DMA32 zone: 476920 pages, LIFO batch:31
Detected use of extended apic ids on hypertransport bus
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 0, 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 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x10b9a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 78000000:68000000)
PERCPU: Allocating 45800 bytes of per cpu data
NR_CPUS: 4, nr_cpu_ids: 4, nr_node_ids 1
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 477338
Policy zone: DMA32
Kernel command line: root=/dev/hda1 ro video=uvesafb:1280x1024-16@60,mtrr:3 fbcon=scrollback:256k,font:10x18 debug initcall_debug hpet=disable
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
Detected 2499.714 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:    8
... MAX_LOCK_DEPTH:          48
... MAX_LOCKDEP_KEYS:        8191
... CLASSHASH_SIZE:           4096
... MAX_LOCKDEP_ENTRIES:     8192
... MAX_LOCKDEP_CHAINS:      16384
... CHAINHASH_SIZE:          8192
 memory used by lock dependency info: 3839 kB
 per task-struct memory footprint: 1920 bytes
Checking aperture...
No AGP bridge found
Node 0: aperture @ 2ecc000000 size 32 MB
Aperture beyond 4GB. Ignoring.
Memory: 1908672k/1965952k available (3610k kernel code, 56892k reserved, 1809k data, 512k init)
CPA: page pool initialized 1 of 1 pages preallocated
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 5001.73 BogoMIPS (lpj=8332380)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
tseg: 0000000000
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
using C1E aware idle routine
Freeing SMP alternatives: 25k freed
ACPI: Core revision 20080609
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: AMD Processor model unknown stepping 02
Using local APIC timer interrupts.
APIC timer calibration result 12498565
Detected 12.498 MHz APIC timer.
calling  migration_init+0x0/0x5b
initcall migration_init+0x0/0x5b returned 1 after 0 msecs
initcall migration_init+0x0/0x5b returned with error code 1 
calling  spawn_ksoftirqd+0x0/0x4e
initcall spawn_ksoftirqd+0x0/0x4e returned 0 after 0 msecs
calling  init_call_single_data+0x0/0x65
initcall init_call_single_data+0x0/0x65 returned 0 after 0 msecs
calling  spawn_softlockup_task+0x0/0x6d
initcall spawn_softlockup_task+0x0/0x6d returned 0 after 0 msecs
lockdep: fixing up alternatives.
Booting processor 1/1 ip 6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5001.71 BogoMIPS (lpj=8332342)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: AMD Processor model unknown stepping 02
Brought up 2 CPUs
Total of 2 processors activated (10002.45 BogoMIPS).
CPU0 attaching sched-domain:
 domain 0: span 0-1 level CPU
  groups: 0 1
  domain 1: span 0-1 level NODE
   groups: 0-1
CPU1 attaching sched-domain:
 domain 0: span 0-1 level CPU
  groups: 1 0
  domain 1: span 0-1 level NODE
   groups: 0-1
calling  init_cpufreq_transition_notifier_list+0x0/0x1e
initcall init_cpufreq_transition_notifier_list+0x0/0x1e returned 0 after 0 msecs
calling  net_ns_init+0x0/0x180
net_namespace: 904 bytes
initcall net_ns_init+0x0/0x180 returned 0 after 0 msecs
calling  cpufreq_tsc+0x0/0x19
initcall cpufreq_tsc+0x0/0x19 returned 0 after 0 msecs
calling  init_smp_flush+0x0/0x66
initcall init_smp_flush+0x0/0x66 returned 0 after 0 msecs
calling  sysctl_init+0x0/0x35
initcall sysctl_init+0x0/0x35 returned 0 after 0 msecs
calling  ksysfs_init+0x0/0xbd
initcall ksysfs_init+0x0/0xbd returned 0 after 0 msecs
calling  init_jiffies_clocksource+0x0/0xc
initcall init_jiffies_clocksource+0x0/0xc returned 0 after 0 msecs
calling  pm_init+0x0/0x3b
initcall pm_init+0x0/0x3b returned 0 after 0 msecs
calling  filelock_init+0x0/0x31
initcall filelock_init+0x0/0x31 returned 0 after 0 msecs
calling  init_script_binfmt+0x0/0xc
initcall init_script_binfmt+0x0/0xc returned 0 after 0 msecs
calling  init_elf_binfmt+0x0/0xc
initcall init_elf_binfmt+0x0/0xc returned 0 after 0 msecs
calling  init_compat_elf_binfmt+0x0/0xc
initcall init_compat_elf_binfmt+0x0/0xc returned 0 after 0 msecs
calling  random32_init+0x0/0xc9
initcall random32_init+0x0/0xc9 returned 0 after 0 msecs
calling  cpufreq_core_init+0x0/0x74
initcall cpufreq_core_init+0x0/0x74 returned 0 after 0 msecs
calling  cpuidle_init+0x0/0x36
initcall cpuidle_init+0x0/0x36 returned 0 after 0 msecs
calling  sock_init+0x0/0x60
initcall sock_init+0x0/0x60 returned 0 after 0 msecs
calling  netlink_proto_init+0x0/0x16d
NET: Registered protocol family 16
initcall netlink_proto_init+0x0/0x16d returned 0 after 0 msecs
calling  bdi_class_init+0x0/0x2f
initcall bdi_class_init+0x0/0x2f returned 0 after 0 msecs
calling  kobject_uevent_init+0x0/0x4c
initcall kobject_uevent_init+0x0/0x4c returned 0 after 0 msecs
calling  pcibus_class_init+0x0/0x13
initcall pcibus_class_init+0x0/0x13 returned 0 after 0 msecs
calling  pci_driver_init+0x0/0x12
initcall pci_driver_init+0x0/0x12 returned 0 after 0 msecs
calling  dock_init+0x0/0x5c
No dock devices found.
initcall dock_init+0x0/0x5c returned 0 after 0 msecs
calling  tty_class_init+0x0/0x34
initcall tty_class_init+0x0/0x34 returned 0 after 0 msecs
calling  vtconsole_class_init+0x0/0xc4
initcall vtconsole_class_init+0x0/0xc4 returned 0 after 0 msecs
calling  register_node_type+0x0/0xb9
initcall register_node_type+0x0/0xb9 returned 0 after 0 msecs
calling  enable_pci_io_ecs+0x0/0x3c
initcall enable_pci_io_ecs+0x0/0x3c returned 0 after 0 msecs
calling  early_fill_mp_bus_info+0x0/0x83e
node 0 link 0: io port [d000, ffff]
TOM: 0000000080000000 aka 2048M
node 0 link 0: mmio [a0000, bffff]
node 0 link 0: mmio [d8000000, dfffffff]
node 0 link 0: mmio [80000000, d7ffffff]
node 0 link 0: mmio [f0000000, fe02ffff]
node 0 link 0: mmio [e0000000, e02fffff]
bus: [00,02] on node 0 link 0
bus: 00 index 0 io port: [0, ffff]
bus: 00 index 1 mmio: [a0000, bffff]
bus: 00 index 2 mmio: [80000000, efffffff]
bus: 00 index 3 mmio: [f0000000, fcffffffff]
initcall early_fill_mp_bus_info+0x0/0x83e returned 0 after 0 msecs
calling  arch_kdebugfs_init+0x0/0xe
initcall arch_kdebugfs_init+0x0/0xe returned 0 after 0 msecs
calling  mtrr_if_init+0x0/0x84
initcall mtrr_if_init+0x0/0x84 returned 0 after 0 msecs
calling  ffh_cstate_init+0x0/0x3c
initcall ffh_cstate_init+0x0/0x3c returned -1 after 0 msecs
initcall ffh_cstate_init+0x0/0x3c returned with error code -1 
calling  acpi_pci_init+0x0/0x65
ACPI: bus type pci registered
initcall acpi_pci_init+0x0/0x65 returned 0 after 0 msecs
calling  init_acpi_device_notify+0x0/0x4b
initcall init_acpi_device_notify+0x0/0x4b returned 0 after 0 msecs
calling  pci_arch_init+0x0/0x4b
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
initcall pci_arch_init+0x0/0x4b returned 0 after 3 msecs
calling  topology_init+0x0/0xa1
initcall topology_init+0x0/0xa1 returned 0 after 0 msecs
calling  mtrr_init_finialize+0x0/0x41
initcall mtrr_init_finialize+0x0/0x41 returned 0 after 0 msecs
calling  param_sysfs_init+0x0/0x24b
initcall param_sysfs_init+0x0/0x24b returned 0 after 3 msecs
calling  pm_sysrq_init+0x0/0x20
initcall pm_sysrq_init+0x0/0x20 returned 0 after 0 msecs
calling  readahead_init+0x0/0x2e
initcall readahead_init+0x0/0x2e returned 0 after 0 msecs
calling  init_bio+0x0/0xbb
initcall init_bio+0x0/0xbb returned 0 after 0 msecs
calling  blk_settings_init+0x0/0x25
initcall blk_settings_init+0x0/0x25 returned 0 after 0 msecs
calling  blk_ioc_init+0x0/0x2d
initcall blk_ioc_init+0x0/0x2d returned 0 after 0 msecs
calling  genhd_device_init+0x0/0x4b
initcall genhd_device_init+0x0/0x4b returned 0 after 0 msecs
calling  pci_slot_init+0x0/0x50
initcall pci_slot_init+0x0/0x50 returned 0 after 0 msecs
calling  fbmem_init+0x0/0x98
initcall fbmem_init+0x0/0x98 returned 0 after 0 msecs
calling  acpi_init+0x0/0x21b
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
initcall acpi_init+0x0/0x21b returned 0 after 9 msecs
calling  acpi_scan_init+0x0/0x110
initcall acpi_scan_init+0x0/0x110 returned 0 after 6 msecs
calling  acpi_ec_init+0x0/0x61
initcall acpi_ec_init+0x0/0x61 returned 0 after 0 msecs
calling  acpi_pci_root_init+0x0/0x28
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:13.5: supports D1
pci 0000:00:13.5: supports D2
pci 0000:00:13.5: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.5: PME# disabled
pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
pci 0000:00:14.2: PME# disabled
pci 0000:01:05.0: supports D1
pci 0000:01:05.0: supports D2
PCI: bridge 0000:00:01.0 io port: [e000, efff]
PCI: bridge 0000:00:01.0 32bit mmio: [fdd00000, fdefffff]
PCI: bridge 0000:00:01.0 64bit mmio pref: [d8000000, dfffffff]
pci 0000:02:05.0: supports D1
pci 0000:02:05.0: supports D2
pci 0000:02:05.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:02:05.0: PME# disabled
pci 0000:00:14.4: transparent bridge
PCI: bridge 0000:00:14.4 io port: [d000, dfff]
PCI: bridge 0000:00:14.4 32bit mmio: [fdc00000, fdcfffff]
PCI: bridge 0000:00:14.4 32bit mmio pref: [fdf00000, fdffffff]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
initcall acpi_pci_root_init+0x0/0x28 returned 0 after 19 msecs
calling  acpi_pci_link_init+0x0/0x48
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
initcall acpi_pci_link_init+0x0/0x48 returned 0 after 3 msecs
calling  acpi_power_init+0x0/0x77
initcall acpi_power_init+0x0/0x77 returned 0 after 0 msecs
calling  acpi_system_init+0x0/0x263
initcall acpi_system_init+0x0/0x263 returned 0 after 0 msecs
calling  pnp_init+0x0/0x22
Linux Plug and Play Support v0.97 (c) Adam Belay
initcall pnp_init+0x0/0x22 returned 0 after 0 msecs
calling  pnpacpi_init+0x0/0x91
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:0d: mem resource (0xfed00000-0xfed000ff) overlaps 0000:00:14.0 BAR 1 (0xfed00000-0xfed003ff), disabling
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
initcall pnpacpi_init+0x0/0x91 returned 0 after 3 msecs
calling  misc_init+0x0/0x97
initcall misc_init+0x0/0x97 returned 0 after 0 msecs
calling  cn_init+0x0/0xf4
initcall cn_init+0x0/0xf4 returned 0 after 0 msecs
calling  init_scsi+0x0/0x81
SCSI subsystem initialized
initcall init_scsi+0x0/0x81 returned 0 after 0 msecs
calling  ata_init+0x0/0x3dd
libata version 3.00 loaded.
initcall ata_init+0x0/0x3dd returned 0 after 0 msecs
calling  usb_init+0x0/0x12d
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
initcall usb_init+0x0/0x12d returned 0 after 3 msecs
calling  serio_init+0x0/0x90
initcall serio_init+0x0/0x90 returned 0 after 0 msecs
calling  input_init+0x0/0x10c
initcall input_init+0x0/0x10c returned 0 after 0 msecs
calling  i2c_init+0x0/0x5e
initcall i2c_init+0x0/0x5e returned 0 after 0 msecs
calling  power_supply_class_init+0x0/0x3b
initcall power_supply_class_init+0x0/0x3b returned 0 after 0 msecs
calling  hwmon_init+0x0/0x47
initcall hwmon_init+0x0/0x47 returned 0 after 0 msecs
calling  thermal_init+0x0/0x4e
initcall thermal_init+0x0/0x4e returned 0 after 0 msecs
calling  pci_subsys_init+0x0/0x120
PCI: Using ACPI for IRQ routing
pci 0000:00:14.0: BAR 1: can't allocate resource
initcall pci_subsys_init+0x0/0x120 returned 0 after 0 msecs
calling  proto_init+0x0/0x31
initcall proto_init+0x0/0x31 returned 0 after 0 msecs
calling  net_dev_init+0x0/0x157
initcall net_dev_init+0x0/0x157 returned 0 after 0 msecs
calling  neigh_init+0x0/0x74
initcall neigh_init+0x0/0x74 returned 0 after 0 msecs
calling  genl_init+0x0/0xd5
initcall genl_init+0x0/0xd5 returned 0 after 12 msecs
calling  sysctl_init+0x0/0x46
initcall sysctl_init+0x0/0x46 returned 0 after 0 msecs
calling  pci_iommu_init+0x0/0x15
initcall pci_iommu_init+0x0/0x15 returned 0 after 0 msecs
calling  hpet_late_init+0x0/0xf7
initcall hpet_late_init+0x0/0xf7 returned -19 after 0 msecs
calling  clocksource_done_booting+0x0/0xd
initcall clocksource_done_booting+0x0/0xd returned 0 after 0 msecs
calling  init_pipe_fs+0x0/0x44
initcall init_pipe_fs+0x0/0x44 returned 0 after 0 msecs
calling  init_mnt_writers+0x0/0x77
initcall init_mnt_writers+0x0/0x77 returned 0 after 0 msecs
calling  eventpoll_init+0x0/0x98
initcall eventpoll_init+0x0/0x98 returned 0 after 0 msecs
calling  anon_inode_init+0x0/0x119
initcall anon_inode_init+0x0/0x119 returned 0 after 0 msecs
calling  acpi_event_init+0x0/0x80
initcall acpi_event_init+0x0/0x80 returned 0 after 9 msecs
calling  pnp_system_init+0x0/0x16
system 00:01: ioport range 0x4100-0x411f has been reserved
system 00:01: ioport range 0x228-0x22f has been reserved
system 00:01: ioport range 0x40b-0x40b has been reserved
system 00:01: ioport range 0x4d6-0x4d6 has been reserved
system 00:01: ioport range 0xc00-0xc01 has been reserved
system 00:01: ioport range 0xc14-0xc14 has been reserved
system 00:01: ioport range 0xc50-0xc52 has been reserved
system 00:01: ioport range 0xc6c-0xc6d has been reserved
system 00:01: ioport range 0xc6f-0xc6f has been reserved
system 00:01: ioport range 0xcd0-0xcd1 has been reserved
system 00:01: ioport range 0xcd2-0xcd3 has been reserved
system 00:01: ioport range 0xcd4-0xcdf has been reserved
system 00:01: ioport range 0x4000-0x40fe has been reserved
system 00:01: ioport range 0x4210-0x4217 has been reserved
system 00:01: ioport range 0xb10-0xb1f has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x220-0x225 has been reserved
system 00:07: ioport range 0xb00-0xb0f has been reserved
system 00:0c: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0d: iomem range 0xf0000-0xfffff could not be reserved
system 00:0d: iomem range 0x77fe0000-0x77ffffff could not be reserved
system 00:0d: iomem range 0xffff0000-0xffffffff could not be reserved
system 00:0d: iomem range 0x0-0x9ffff could not be reserved
system 00:0d: iomem range 0x100000-0x77fdffff could not be reserved
system 00:0d: iomem range 0x78000000-0x7fffffff has been reserved
system 00:0d: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:0d: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:0d: iomem range 0xfff80000-0xfffeffff could not be reserved
initcall pnp_system_init+0x0/0x16 returned 0 after 0 msecs
calling  chr_dev_init+0x0/0xa2
initcall chr_dev_init+0x0/0xa2 returned 0 after 0 msecs
calling  firmware_class_init+0x0/0x71
initcall firmware_class_init+0x0/0x71 returned 0 after 0 msecs
calling  loopback_init+0x0/0xc
initcall loopback_init+0x0/0xc returned 0 after 0 msecs
calling  cpufreq_gov_performance_init+0x0/0xc
initcall cpufreq_gov_performance_init+0x0/0xc returned 0 after 0 msecs
calling  init_acpi_pm_clocksource+0x0/0xb4
initcall init_acpi_pm_clocksource+0x0/0xb4 returned 0 after 0 msecs
calling  pcibios_assign_resources+0x0/0x8b
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0:   IO window: 0xe000-0xefff
pci 0000:00:01.0:   MEM window: 0xfdd00000-0xfdefffff
pci 0000:00:01.0:   PREFETCH window: 0x000000d8000000-0x000000dfffffff
pci 0000:00:14.4: PCI bridge, secondary bus 0000:02
pci 0000:00:14.4:   IO window: 0xd000-0xdfff
pci 0000:00:14.4:   MEM window: 0xfdc00000-0xfdcfffff
pci 0000:00:14.4:   PREFETCH window: 0x000000fdf00000-0x000000fdffffff
bus: 00 index 0 io port: [0, ffff]
bus: 00 index 1 mmio: [0, ffffffffffffffff]
bus: 01 index 0 io port: [e000, efff]
bus: 01 index 1 mmio: [fdd00000, fdefffff]
bus: 01 index 2 mmio: [d8000000, dfffffff]
bus: 01 index 3 mmio: [0, 0]
bus: 02 index 0 io port: [d000, dfff]
bus: 02 index 1 mmio: [fdc00000, fdcfffff]
bus: 02 index 2 mmio: [fdf00000, fdffffff]
bus: 02 index 3 io port: [0, ffff]
bus: 02 index 4 mmio: [0, ffffffffffffffff]
initcall pcibios_assign_resources+0x0/0x8b returned 0 after 0 msecs
calling  inet_init+0x0/0x250
Switched to high resolution mode on CPU 0
NET: Registered protocol family 2
Switched to high resolution mode on CPU 1
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 9, 3670016 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
initcall inet_init+0x0/0x250 returned 0 after 47 msecs
calling  af_unix_init+0x0/0x4b
NET: Registered protocol family 1
initcall af_unix_init+0x0/0x4b returned 0 after 0 msecs
calling  populate_rootfs+0x0/0xaf
initcall populate_rootfs+0x0/0xaf returned 0 after 1 msecs
calling  i8259A_init_sysfs+0x0/0x29
initcall i8259A_init_sysfs+0x0/0x29 returned 0 after 0 msecs
calling  vsyscall_init+0x0/0x63
initcall vsyscall_init+0x0/0x63 returned 0 after 0 msecs
calling  sbf_init+0x0/0x103
initcall sbf_init+0x0/0x103 returned 0 after 0 msecs
calling  i8237A_init_sysfs+0x0/0x29
initcall i8237A_init_sysfs+0x0/0x29 returned 0 after 0 msecs
calling  add_rtc_cmos+0x0/0x21
initcall add_rtc_cmos+0x0/0x21 returned 0 after 0 msecs
calling  cache_sysfs_init+0x0/0x5a3
initcall cache_sysfs_init+0x0/0x5a3 returned 0 after 0 msecs
calling  mce_init_device+0x0/0x1f6
initcall mce_init_device+0x0/0x1f6 returned 0 after 0 msecs
calling  periodic_mcheck_init+0x0/0x44
initcall periodic_mcheck_init+0x0/0x44 returned 0 after 0 msecs
calling  thermal_throttle_init_device+0x0/0x59
initcall thermal_throttle_init_device+0x0/0x59 returned 0 after 0 msecs
calling  threshold_init_device+0x0/0x465
initcall threshold_init_device+0x0/0x465 returned 0 after 0 msecs
calling  msr_init+0x0/0x120
initcall msr_init+0x0/0x120 returned 0 after 0 msecs
calling  cpuid_init+0x0/0x120
initcall cpuid_init+0x0/0x120 returned 0 after 0 msecs
calling  init_lapic_sysfs+0x0/0x34
initcall init_lapic_sysfs+0x0/0x34 returned 0 after 0 msecs
calling  ioapic_init_sysfs+0x0/0xb7
initcall ioapic_init_sysfs+0x0/0xb7 returned 0 after 0 msecs
calling  add_pcspkr+0x0/0x43
initcall add_pcspkr+0x0/0x43 returned 0 after 0 msecs
calling  uv_ptc_init+0x0/0x7a
initcall uv_ptc_init+0x0/0x7a returned 0 after 0 msecs
calling  uv_bau_init+0x0/0x62a
initcall uv_bau_init+0x0/0x62a returned 0 after 0 msecs
calling  init_vdso_vars+0x0/0x23f
initcall init_vdso_vars+0x0/0x23f returned 0 after 0 msecs
calling  ia32_binfmt_init+0x0/0x17
initcall ia32_binfmt_init+0x0/0x17 returned 0 after 0 msecs
calling  sysenter_setup+0x0/0x35c
initcall sysenter_setup+0x0/0x35c returned 0 after 0 msecs
calling  init_sched_debug_procfs+0x0/0x2c
initcall init_sched_debug_procfs+0x0/0x2c returned 0 after 0 msecs
calling  ioresources_init+0x0/0x3f
initcall ioresources_init+0x0/0x3f returned 0 after 0 msecs
calling  uid_cache_init+0x0/0x90
initcall uid_cache_init+0x0/0x90 returned 0 after 0 msecs
calling  init_posix_timers+0x0/0x95
initcall init_posix_timers+0x0/0x95 returned 0 after 0 msecs
calling  init_posix_cpu_timers+0x0/0xb5
initcall init_posix_cpu_timers+0x0/0xb5 returned 0 after 0 msecs
calling  nsproxy_cache_init+0x0/0x3d
initcall nsproxy_cache_init+0x0/0x3d returned 0 after 0 msecs
calling  timekeeping_init_device+0x0/0x29
initcall timekeeping_init_device+0x0/0x29 returned 0 after 0 msecs
calling  init_clocksource_sysfs+0x0/0x57
initcall init_clocksource_sysfs+0x0/0x57 returned 0 after 0 msecs
calling  init_timer_list_procfs+0x0/0x2f
initcall init_timer_list_procfs+0x0/0x2f returned 0 after 0 msecs
calling  lockdep_proc_init+0x0/0x62
initcall lockdep_proc_init+0x0/0x62 returned 0 after 0 msecs
calling  futex_init+0x0/0xce
initcall futex_init+0x0/0xce returned 0 after 0 msecs
calling  proc_dma_init+0x0/0x25
initcall proc_dma_init+0x0/0x25 returned 0 after 0 msecs
calling  percpu_modinit+0x0/0x80
initcall percpu_modinit+0x0/0x80 returned 0 after 0 msecs
calling  kallsyms_init+0x0/0x28
initcall kallsyms_init+0x0/0x28 returned 0 after 0 msecs
calling  ikconfig_init+0x0/0x3c
initcall ikconfig_init+0x0/0x3c returned 0 after 0 msecs
calling  utsname_sysctl_init+0x0/0x24
initcall utsname_sysctl_init+0x0/0x24 returned 0 after 0 msecs
calling  init_per_zone_pages_min+0x0/0x52
initcall init_per_zone_pages_min+0x0/0x52 returned 0 after 0 msecs
calling  pdflush_init+0x0/0x15
initcall pdflush_init+0x0/0x15 returned 0 after 0 msecs
calling  kswapd_init+0x0/0x6f
initcall kswapd_init+0x0/0x6f returned 0 after 0 msecs
calling  setup_vmstat+0x0/0x3a
initcall setup_vmstat+0x0/0x3a returned 0 after 0 msecs
calling  mm_sysfs_init+0x0/0x2c
initcall mm_sysfs_init+0x0/0x2c returned 0 after 0 msecs
calling  procswaps_init+0x0/0x25
initcall procswaps_init+0x0/0x25 returned 0 after 0 msecs
calling  init_tmpfs+0x0/0xd8
initcall init_tmpfs+0x0/0xd8 returned 0 after 0 msecs
calling  slab_sysfs_init+0x0/0xf4
initcall slab_sysfs_init+0x0/0xf4 returned 0 after 3 msecs
calling  fasync_init+0x0/0x2d
initcall fasync_init+0x0/0x2d returned 0 after 0 msecs
calling  aio_setup+0x0/0x76
initcall aio_setup+0x0/0x76 returned 0 after 0 msecs
calling  inotify_setup+0x0/0xd
initcall inotify_setup+0x0/0xd returned 0 after 0 msecs
calling  inotify_user_setup+0x0/0xbf
initcall inotify_user_setup+0x0/0xbf returned 0 after 0 msecs
calling  init_sys32_ioctl+0x0/0x8a
initcall init_sys32_ioctl+0x0/0x8a returned 0 after 0 msecs
calling  dnotify_init+0x0/0x2d
initcall dnotify_init+0x0/0x2d returned 0 after 0 msecs
calling  init_devpts_fs+0x0/0x35
initcall init_devpts_fs+0x0/0x35 returned 0 after 0 msecs
calling  init_ext3_fs+0x0/0x56
initcall init_ext3_fs+0x0/0x56 returned 0 after 0 msecs
calling  journal_init+0x0/0x9e
initcall journal_init+0x0/0x9e returned 0 after 0 msecs
calling  init_ext2_fs+0x0/0x55
initcall init_ext2_fs+0x0/0x55 returned 0 after 0 msecs
calling  init_ramfs_fs+0x0/0xc
initcall init_ramfs_fs+0x0/0xc returned 0 after 0 msecs
calling  init_fat_fs+0x0/0x47
initcall init_fat_fs+0x0/0x47 returned 0 after 0 msecs
calling  init_msdos_fs+0x0/0xc
initcall init_msdos_fs+0x0/0xc returned 0 after 0 msecs
calling  init_vfat_fs+0x0/0xf
initcall init_vfat_fs+0x0/0xf returned 0 after 0 msecs
calling  init_iso9660_fs+0x0/0x6b
initcall init_iso9660_fs+0x0/0x6b returned 0 after 0 msecs
calling  init_nfs_fs+0x0/0x148
initcall init_nfs_fs+0x0/0x148 returned 0 after 0 msecs
calling  init_nfsd+0x0/0xc2
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
initcall init_nfsd+0x0/0xc2 returned 0 after 0 msecs
calling  init_nlm+0x0/0x25
initcall init_nlm+0x0/0x25 returned 0 after 0 msecs
calling  init_nls_cp437+0x0/0xc
initcall init_nls_cp437+0x0/0xc returned 0 after 0 msecs
calling  init_nls_iso8859_1+0x0/0xc
initcall init_nls_iso8859_1+0x0/0xc returned 0 after 0 msecs
calling  init_udf_fs+0x0/0x55
initcall init_udf_fs+0x0/0x55 returned 0 after 0 msecs
calling  ipc_init+0x0/0x26
msgmni has been set to 3727
initcall ipc_init+0x0/0x26 returned 0 after 0 msecs
calling  ipc_sysctl_init+0x0/0x17
initcall ipc_sysctl_init+0x0/0x17 returned 0 after 0 msecs
calling  crypto_algapi_init+0x0/0x10
initcall crypto_algapi_init+0x0/0x10 returned 0 after 0 msecs
calling  cryptomgr_init+0x0/0xc
initcall cryptomgr_init+0x0/0xc returned 0 after 0 msecs
calling  hmac_module_init+0x0/0xc
initcall hmac_module_init+0x0/0xc returned 0 after 0 msecs
calling  md5_mod_init+0x0/0xc
initcall md5_mod_init+0x0/0xc returned 0 after 0 msecs
calling  sha1_generic_mod_init+0x0/0xc
initcall sha1_generic_mod_init+0x0/0xc returned 0 after 0 msecs
calling  des_generic_mod_init+0x0/0x37
initcall des_generic_mod_init+0x0/0x37 returned 0 after 0 msecs
calling  deflate_mod_init+0x0/0x11
initcall deflate_mod_init+0x0/0x11 returned 0 after 0 msecs
calling  noop_init+0x0/0x17
io scheduler noop registered
initcall noop_init+0x0/0x17 returned 0 after 0 msecs
calling  deadline_init+0x0/0x19
io scheduler deadline registered
initcall deadline_init+0x0/0x19 returned 0 after 0 msecs
calling  cfq_init+0x0/0x9a
io scheduler cfq registered (default)
initcall cfq_init+0x0/0x9a returned 0 after 0 msecs
calling  pci_init+0x0/0x2f
pci 0000:01:05.0: Boot video device
initcall pci_init+0x0/0x2f returned 0 after 111 msecs
calling  pci_proc_init+0x0/0x63
initcall pci_proc_init+0x0/0x63 returned 0 after 0 msecs
calling  pcie_portdrv_init+0x0/0x43
initcall pcie_portdrv_init+0x0/0x43 returned 0 after 0 msecs
calling  aer_service_init+0x0/0x1c
initcall aer_service_init+0x0/0x1c returned 0 after 0 msecs
calling  fb_console_init+0x0/0x153
initcall fb_console_init+0x0/0x153 returned 0 after 0 msecs
calling  uvesafb_init+0x0/0x3d6
uvesafb: (C) 1988-2005, ATI Technologies Inc. RS69001.00, RS69001.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. RS69001.00, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x56
uvesafb: framebuffer at 0xd8000000, mapped to 0xffffc20010c00000, using 16384k, total 16384k
fb0: VESA VGA frame buffer device
initcall uvesafb_init+0x0/0x3d6 returned 0 after 329 msecs
calling  acpi_reserve_resources+0x0/0xeb
initcall acpi_reserve_resources+0x0/0xeb returned 0 after 0 msecs
calling  acpi_button_init+0x0/0x5e
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
initcall acpi_button_init+0x0/0x5e returned 0 after 0 msecs
calling  acpi_fan_init+0x0/0x5e
fan PNP0C0B:00: registered as cooling_device0
ACPI: Fan [FAN] (on)
initcall acpi_fan_init+0x0/0x5e returned 0 after 0 msecs
calling  irqrouter_init_sysfs+0x0/0x39
initcall irqrouter_init_sysfs+0x0/0x39 returned 0 after 0 msecs
calling  acpi_processor_init+0x0/0xcd
processor ACPI0007:00: registered as cooling_device1
processor ACPI0007:01: registered as cooling_device2
initcall acpi_processor_init+0x0/0xcd returned 0 after 0 msecs
calling  acpi_thermal_init+0x0/0x84
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (17 C)
initcall acpi_thermal_init+0x0/0x84 returned 0 after 1 msecs
calling  rand_initialize+0x0/0x30
initcall rand_initialize+0x0/0x30 returned 0 after 0 msecs
calling  tty_init+0x0/0x1dc
initcall tty_init+0x0/0x1dc returned 0 after 25 msecs
calling  pty_init+0x0/0x2eb
initcall pty_init+0x0/0x2eb returned 0 after 0 msecs
calling  hpet_init+0x0/0x6f
hpet_acpi_add: no address or irqs in _CRS
initcall hpet_init+0x0/0x6f returned 0 after 1 msecs
calling  agp_init+0x0/0x2d
Linux agpgart interface v0.103
initcall agp_init+0x0/0x2d returned 0 after 1 msecs
calling  cn_proc_init+0x0/0x3f
initcall cn_proc_init+0x0/0x3f returned 0 after 0 msecs
calling  topology_sysfs_init+0x0/0x50
initcall topology_sysfs_init+0x0/0x50 returned 0 after 0 msecs
calling  loop_init+0x0/0x1ca
loop: module loaded
initcall loop_init+0x0/0x1ca returned 0 after 2 msecs
calling  pkt_init+0x0/0x1a9
initcall pkt_init+0x0/0x1a9 returned 0 after 0 msecs
calling  net_olddevs_init+0x0/0x97
initcall net_olddevs_init+0x0/0x97 returned 0 after 0 msecs
calling  rtl8169_init_module+0x0/0x1a
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
eth0: RTL8169sc/8110sc at 0xffffc20000336000, 00:1b:b9:f4:88:d0, XID 18000000 IRQ 22
initcall rtl8169_init_module+0x0/0x1a returned 0 after 7 msecs
calling  ide_init+0x0/0x72
Uniform Multi-Platform E-IDE driver
initcall ide_init+0x0/0x72 returned 0 after 2 msecs
calling  atiixp_ide_init+0x0/0x15
atiixp 0000:00:14.1: IDE controller (0x1002:0x438c rev 0x00)
ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
atiixp 0000:00:14.1: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf900-0xf907
Probing IDE interface ide0...
hda: Maxtor 6H500R0, ATA DISK drive
hdb: SAMSUNG DVD-ROM SD-616E, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
isa bounce pool size: 16 pages
initcall atiixp_ide_init+0x0/0x15 returned 0 after 762 msecs
calling  generic_ide_init+0x0/0x15
initcall generic_ide_init+0x0/0x15 returned 0 after 0 msecs
calling  ide_generic_init+0x0/0x253
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
Probing IDE interface ide1...
ide1 at 0x170-0x177,0x376 on irq 15
initcall ide_generic_init+0x0/0x253 returned 0 after 518 msecs
calling  idedisk_init+0x0/0xc
hda: max request size: 512KiB
hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63
hda: cache flushes supported
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 >
initcall idedisk_init+0x0/0xc returned 0 after 84 msecs
calling  ide_cdrom_init+0x0/0x15
hdb: ATAPI 48X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.20
initcall ide_cdrom_init+0x0/0x15 returned 0 after 6 msecs
calling  init_sd+0x0/0x119
Driver 'sd' needs updating - please use bus_type methods
initcall init_sd+0x0/0x119 returned 0 after 2 msecs
calling  ahci_init+0x0/0x15
ahci 0000:00:12.0: version 3.0
ahci 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck led clo pmp pio 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 16
ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 16
ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 16
ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 16
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD5000AACS-00ZUB0, 01.01B01, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: SB600 AHCI: limiting to 255 sectors per cmd
ata2.00: configured for UDMA/133
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      WDC WD5000AACS-0 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
initcall ahci_init+0x0/0x15 returned 0 after 2060 msecs
calling  cdrom_init+0x0/0x75
initcall cdrom_init+0x0/0x75 returned 0 after 0 msecs
calling  ehci_hcd_init+0x0/0x15
ehci_hcd 0000:00:13.5: PCI INT D -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 19, io mem 0xfe029000
ehci_hcd 0000:00:13.5: 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: 10 ports detected
initcall ehci_hcd_init+0x0/0x15 returned 0 after 122 msecs
calling  ohci_hcd_mod_init+0x0/0x45
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:13.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 16, io mem 0xfe02e000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 17, io mem 0xfe02d000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 18, io mem 0xfe02c000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 17, io mem 0xfe02b000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.4: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 18, io mem 0xfe02a000
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
initcall ohci_hcd_mod_init+0x0/0x45 returned 0 after 828 msecs
calling  usb_stor_init+0x0/0x4d
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
initcall usb_stor_init+0x0/0x4d returned 0 after 6 msecs
calling  i8042_init+0x0/0x40b
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
initcall i8042_init+0x0/0x40b returned 0 after 7 msecs
calling  mousedev_init+0x0/0x59
mice: PS/2 mouse device common for all mice
initcall mousedev_init+0x0/0x59 returned 0 after 2 msecs
calling  atkbd_init+0x0/0x29
initcall atkbd_init+0x0/0x29 returned 0 after 0 msecs
calling  psmouse_init+0x0/0x68
initcall psmouse_init+0x0/0x68 returned 0 after 0 msecs
calling  i2c_dev_init+0x0/0x9d
i2c /dev entries driver
initcall i2c_dev_init+0x0/0x9d returned 0 after 2 msecs
calling  i2c_piix4_init+0x0/0x15
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xfa00, revision 0
initcall i2c_piix4_init+0x0/0x15 returned 0 after 2 msecs
calling  k8temp_init+0x0/0x15
initcall k8temp_init+0x0/0x15 returned 0 after 0 msecs
calling  init_ladder+0x0/0xc
cpuidle: using governor ladder
initcall init_ladder+0x0/0xc returned 0 after 2 msecs
calling  init_menu+0x0/0xe
cpuidle: using governor menu
initcall init_menu+0x0/0xe returned 0 after 0 msecs
calling  hid_init+0x0/0x10
initcall hid_init+0x0/0x10 returned 0 after 0 msecs
calling  hid_init+0x0/0x62
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
initcall hid_init+0x0/0x62 returned 0 after 21 msecs
calling  init_soundcore+0x0/0x70
initcall init_soundcore+0x0/0x70 returned 0 after 0 msecs
calling  alsa_sound_init+0x0/0x90
Advanced Linux Sound Architecture Driver Version 1.0.17.
initcall alsa_sound_init+0x0/0x90 returned 0 after 2 msecs
calling  alsa_timer_init+0x0/0x195
initcall alsa_timer_init+0x0/0x195 returned 0 after 0 msecs
calling  alsa_pcm_init+0x0/0x64
initcall alsa_pcm_init+0x0/0x64 returned 0 after 0 msecs
calling  snd_mem_init+0x0/0x2f
initcall snd_mem_init+0x0/0x2f returned 0 after 0 msecs
calling  alsa_mixer_oss_init+0x0/0x33
initcall alsa_mixer_oss_init+0x0/0x33 returned 0 after 0 msecs
calling  alsa_pcm_oss_init+0x0/0x85
initcall alsa_pcm_oss_init+0x0/0x85 returned 0 after 0 msecs
calling  alsa_seq_oss_init+0x0/0x194
initcall alsa_seq_oss_init+0x0/0x194 returned 0 after 0 msecs
calling  alsa_seq_init+0x0/0x50
initcall alsa_seq_init+0x0/0x50 returned 0 after 0 msecs
calling  alsa_seq_device_init+0x0/0x60
initcall alsa_seq_device_init+0x0/0x60 returned 0 after 0 msecs
calling  alsa_seq_midi_event_init+0x0/0x3
initcall alsa_seq_midi_event_init+0x0/0x3 returned 0 after 0 msecs
calling  alsa_card_azx_init+0x0/0x15
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
HDA Intel 0000:01:05.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
initcall alsa_card_azx_init+0x0/0x15 returned 0 after 94 msecs
calling  alsa_sound_last_init+0x0/0x6b
ALSA device list:
  #0: HDA ATI SB at 0xfe020000 irq 16
  #1: HDA ATI HDMI at 0xfdefc000 irq 19
initcall alsa_sound_last_init+0x0/0x6b returned 0 after 6 msecs
calling  sysctl_core_init+0x0/0x27
initcall sysctl_core_init+0x0/0x27 returned 0 after 0 msecs
calling  flow_cache_init+0x0/0x1b5
initcall flow_cache_init+0x0/0x1b5 returned 0 after 0 msecs
calling  sysctl_ipv4_init+0x0/0x4a
initcall sysctl_ipv4_init+0x0/0x4a returned 0 after 0 msecs
calling  cubictcp_register+0x0/0x6b
TCP cubic registered
initcall cubictcp_register+0x0/0x6b returned 0 after 2 msecs
calling  xfrm_user_init+0x0/0x5c
Initializing XFRM netlink socket
initcall xfrm_user_init+0x0/0x5c returned 0 after 2 msecs
calling  packet_init+0x0/0x49
NET: Registered protocol family 17
initcall packet_init+0x0/0x49 returned 0 after 2 msecs
calling  init_sunrpc+0x0/0x6a
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
initcall init_sunrpc+0x0/0x6a returned 0 after 4 msecs
calling  powernowk8_init+0x0/0x94
powernow-k8: Found 1 AMD Processor model unknown processors (2 cpu cores) (version 2.20.00)
powernow-k8:    0 : fid 0x11 (2500 MHz), vid 0xc
powernow-k8:    1 : fid 0x10 (2400 MHz), vid 0xd
powernow-k8:    2 : fid 0xe (2200 MHz), vid 0xf
powernow-k8:    3 : fid 0xc (2000 MHz), vid 0x11
powernow-k8:    4 : fid 0xa (1800 MHz), vid 0x13
powernow-k8:    5 : fid 0x2 (1000 MHz), vid 0x16
initcall powernowk8_init+0x0/0x94 returned 0 after 14 msecs
calling  hpet_insert_resource+0x0/0x1e
initcall hpet_insert_resource+0x0/0x1e returned 0 after 0 msecs
calling  update_mp_table+0x0/0x68e
initcall update_mp_table+0x0/0x68e returned 0 after 0 msecs
calling  lapic_insert_resource+0x0/0x45
initcall lapic_insert_resource+0x0/0x45 returned 0 after 0 msecs
calling  init_lapic_nmi_sysfs+0x0/0x3e
initcall init_lapic_nmi_sysfs+0x0/0x3e returned 0 after 0 msecs
calling  ioapic_insert_resources+0x0/0x59
initcall ioapic_insert_resources+0x0/0x59 returned 0 after 0 msecs
calling  check_early_ioremap_leak+0x0/0x49
initcall check_early_ioremap_leak+0x0/0x49 returned 0 after 0 msecs
calling  sched_init_debug+0x0/0x8
initcall sched_init_debug+0x0/0x8 returned 0 after 0 msecs
calling  init_oops_id+0x0/0x30
initcall init_oops_id+0x0/0x30 returned 0 after 0 msecs
calling  disable_boot_consoles+0x0/0x3f
initcall disable_boot_consoles+0x0/0x3f returned 0 after 0 msecs
calling  pm_qos_power_init+0x0/0xd4
initcall pm_qos_power_init+0x0/0xd4 returned 0 after 0 msecs
calling  random32_reseed+0x0/0x99
initcall random32_reseed+0x0/0x99 returned 0 after 0 msecs
calling  pci_sysfs_init+0x0/0x4d
initcall pci_sysfs_init+0x0/0x4d returned 0 after 0 msecs
calling  acpi_wakeup_device_init+0x0/0xaf
initcall acpi_wakeup_device_init+0x0/0xaf returned 0 after 0 msecs
calling  seqgen_init+0x0/0x1e
initcall seqgen_init+0x0/0x1e returned 0 after 0 msecs
calling  scsi_complete_async_scans+0x0/0x120
initcall scsi_complete_async_scans+0x0/0x120 returned 0 after 0 msecs
calling  memmap_init+0x0/0xa7
initcall memmap_init+0x0/0xa7 returned 0 after 0 msecs
calling  pci_mmcfg_late_insert_resources+0x0/0x47
initcall pci_mmcfg_late_insert_resources+0x0/0x47 returned 0 after 0 msecs
calling  tcp_congestion_default+0x0/0xc
initcall tcp_congestion_default+0x0/0xc returned 0 after 0 msecs
input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
input: AT Translated Set 2 keyboard as /class/input/input3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 512k freed
Write protecting the kernel read-only data: 4972k
calling  evdev_init+0x0/0xc [evdev]
initcall evdev_init+0x0/0xc [evdev] returned 0 after 95 msecs
calling  pcspkr_init+0x0/0xc [pcspkr]
input: PC Speaker as /class/input/input4
initcall pcspkr_init+0x0/0xc [pcspkr] returned 0 after 29 msecs
Adding 1951888k swap on /dev/hda2.  Priority:-1 extents:1 across:1951888k
calling  cpufreq_gov_userspace_init+0x0/0xc [cpufreq_userspace]
initcall cpufreq_gov_userspace_init+0x0/0xc [cpufreq_userspace] returned 0 after 0 msecs
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
r8169: eth0: link up
calling  inet6_init+0x0/0x360 [ipv6]
NET: Registered protocol family 10
initcall inet6_init+0x0/0x360 [ipv6] returned 0 after 4 msecs
Clocksource tsc unstable (delta = -85223910 ns)
eth0: no IPv6 routers present
warning: `ntpd' uses 32-bit capabilities (legacy support in use)


$ lspci -vvxxx
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
    Subsystem: ATI Technologies Inc RS690 Host Bridge
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
    Latency: 64
00: 02 10 10 79 06 00 20 22 00 00 00 06 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 10 79
30: 00 00 00 00 c4 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 42 20 05 00
50: 02 10 10 79 ff 00 00 00 00 00 00 00 00 00 00 00
60: 5f 00 00 00 00 00 00 00 00 02 20 00 98 f8 01 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 40 44 00 00 95 00 00 03 20 01 10 00 02 27 00 00
90: 00 00 00 78 40 c4 40 e3 00 00 00 00 01 00 00 00
a0: 00 00 00 00 00 00 00 00 07 01 00 00 49 01 10 07
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 08 00 94 01 60 00 11 11 d0 00 00 00
d0: 25 06 65 00 02 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 7f 00 00 00 00 00 00 00
f0: 00 00 00 00 00 80 80 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 99
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
    I/O behind bridge: 0000e000-0000efff
    Memory behind bridge: fdd00000-fdefffff
    Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
    Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
    BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
    Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+
    Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
00: 02 10 12 79 07 00 30 02 00 00 04 06 00 63 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 44 e1 e1 20 02
20: d0 fd e0 fd 01 d8 f1 df 00 00 00 00 00 00 00 00
30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 08 00
40: 00 00 00 00 08 b0 03 a8 00 00 00 00 02 10 12 79
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 0d 00 00 00 02 10 12 79 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01)
    Subsystem: Elitegroup Computer Systems Device 4382
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64
    Interrupt: pin A routed to IRQ 16
    Region 0: I/O ports at ff00 [size=8]
    Region 1: I/O ports at fe00 [size=4]
    Region 2: I/O ports at fd00 [size=8]
    Region 3: I/O ports at fc00 [size=4]
    Region 4: I/O ports at fb00 [size=16]
    Region 5: Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [60] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [70] SATA HBA <?>
    Kernel driver in use: ahci
00: 02 10 80 43 07 00 30 02 00 01 06 01 00 40 00 00
10: 01 ff 00 00 01 fe 00 00 01 fd 00 00 01 fc 00 00
20: 01 fb 00 00 00 f0 02 fe 00 00 00 00 19 10 82 43
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 00 00
40: 10 00 80 02 01 00 10 00 01 00 00 00 00 00 00 00
50: 05 70 84 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 70 22 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 12 00 10 00 0f 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 06 00 00 2c d5 00 b4 00 d5 00 b4 00
90: d5 00 b4 00 d5 00 b4 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 78 00 00 00 00 00 00 00 78 00 00
b0: 00 00 00 00 00 78 00 00 00 00 00 00 00 78 00 00
c0: 00 20 00 00 80 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin A routed to IRQ 16
    Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
    Kernel driver in use: ohci_hcd
00: 02 10 87 43 07 00 a0 02 00 10 03 0c 01 40 80 00
10: 00 e0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00
40: 80 1f 00 00 0a 84 b7 18 07 35 00 00 00 00 00 00
50: 00 1c 00 00 00 00 00 00 ff ff ff ff ff 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 ff 00 00 80 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin B routed to IRQ 17
    Region 0: Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
    Kernel driver in use: ohci_hcd
00: 02 10 88 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 d0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin C routed to IRQ 18
    Region 0: Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
    Kernel driver in use: ohci_hcd
00: 02 10 89 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 c0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin B routed to IRQ 17
    Region 0: Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
    Kernel driver in use: ohci_hcd
00: 02 10 8a 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 b0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin C routed to IRQ 18
    Region 0: Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
    Kernel driver in use: ohci_hcd
00: 02 10 8b 43 07 00 a0 02 00 10 03 0c 01 40 00 00
10: 00 a0 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 64 bytes
    Interrupt: pin D routed to IRQ 19
    Region 0: Memory at fe029000 (32-bit, non-prefetchable) [size=256]
    Capabilities: [c0] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Bridge: PM- B3+
    Capabilities: [e4] Debug port: BAR=1 offset=00e0
    Kernel driver in use: ehci_hcd
00: 02 10 86 43 17 00 b0 02 00 20 03 0c 10 40 00 00
10: 00 90 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 c0 00 00 00 00 00 00 00 0b 04 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 40 00 0e 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 20 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 01 00 00 01 00 00 08 c0 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 e4 02 7e 00 00 40 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 0a 00 e0 20 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 13)
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Region 0: I/O ports at fa00 [size=16]
    Region 1: Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+
    Kernel driver in use: piix4_smbus
00: 02 10 85 43 03 04 30 02 13 00 05 0c 00 00 80 00
10: 01 fa 00 00 00 00 00 80 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 b0 00 00 00 00 00 00 00 00 00 00 00
40: d4 3b 00 05 00 00 00 00 0f ff 00 00 00 00 00 00
50: f0 01 f0 0e f0 0f f0 07 11 0b f0 0f 00 00 00 00
60: 01 00 24 00 bf fd de 8f 3f 90 00 00 20 00 00 00
70: 00 01 00 00 08 00 c0 fe ff 6e 00 00 00 00 f0 0f
80: f0 0a f0 0f 00 00 00 00 00 00 00 00 8c 00 00 80
90: 01 fa 00 00 fa de ff 00 00 00 00 00 00 00 00 00
a0: 00 00 ff ff ff ff f0 08 ff fd 12 02 16 7b 20 00
b0: 08 00 02 a8 00 00 00 00 00 00 00 00 f0 0f 08 1a
c0: ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: d8 0c 00 00 00 00 44 00 00 00 00 00 aa 00 10 01

00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64
    Interrupt: pin A routed to IRQ 16
    Region 0: I/O ports at 01f0 [size=8]
    Region 1: I/O ports at 03f4 [size=1]
    Region 2: I/O ports at 0170 [size=8]
    Region 3: I/O ports at 0374 [size=1]
    Region 4: I/O ports at f900 [size=16]
    Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
        Address: 00000000  Data: 0000
    Kernel driver in use: ATIIXP_IDE
00: 02 10 8c 43 05 00 30 02 00 8a 01 01 00 40 00 00
10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
20: 01 f9 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 70 00 00 00 00 00 00 00 ff 01 00 00
40: 20 20 00 00 20 20 00 00 00 00 44 00 00 00 00 00
50: 00 00 00 00 03 00 25 00 00 00 00 00 00 00 00 00
60: 00 00 40 00 10 2c 01 07 01 00 00 00 ff ff 0f 00
70: 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin ? routed to IRQ 16
    Region 0: Memory at fe020000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Address: 0000000000000000  Data: 0000
    Kernel driver in use: HDA Intel
00: 02 10 83 43 06 00 10 04 00 00 03 04 01 40 00 00
10: 04 00 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 50 00 00 00 00 00 00 00 03 00 00 00
40: 00 00 02 00 00 00 00 00 00 00 00 00 01 00 00 00
50: 01 60 42 c8 00 00 00 00 00 00 00 00 00 00 00 00
60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
00: 02 10 8d 43 0f 00 20 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 04 00 00 00 ff ff c3 ff 3f ff 42 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 0a 00 00 0e 00 0f 00 f8 ff ff ff
70: 67 45 23 01 00 00 00 00 01 00 00 00 05 00 00 00
80: 08 00 03 a8 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01)
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
    I/O behind bridge: 0000d000-0000dfff
    Memory behind bridge: fdc00000-fdcfffff
    Prefetchable memory behind bridge: fdf00000-fdffffff
    Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
    BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
00: 02 10 84 43 27 00 a0 02 00 01 04 06 00 40 81 00
10: 00 00 00 00 00 00 00 00 00 02 02 40 d0 d0 80 22
20: c0 fd c0 fd f0 fd f0 fd 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 26 00 30 ff 00 00 00 00 0c 01 3e d1 00 00 00 00
50: 01 00 00 00 08 00 03 a8 00 00 00 00 85 00 ff ff
60: ca 0e 17 00 8a 18 10 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 06
e0: 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Capabilities: [80] HyperTransport: Host or Secondary Interface
        !!! Possibly incomplete decoding
        Command: WarmRst+ DblEnd-
        Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
        Link Config: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
        Revision ID: 1.02
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
60: 00 00 01 00 e4 00 00 00 20 c8 2f 0f 0c 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 08 00 01 21 20 00 11 11 22 06 75 80 02 00 00 00
90: 78 01 70 01 00 00 02 00 07 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 03 00 00 00 00 00 7f 00 00 00 00 00 01 00 00 00
50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00
60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00
70: 00 00 00 00 06 00 00 00 00 00 00 00 07 00 00 00
80: 03 0a 00 00 00 0b 00 00 03 00 d8 00 80 ff df 00
90: 03 00 80 00 00 ff d7 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 03 00 f0 00 00 02 fe 00
b0: 03 00 e0 00 80 2f e0 00 00 00 00 00 00 00 00 00
c0: 13 d0 00 00 00 f0 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 03 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 01 00 00 00 01 01 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: e0 3e 78 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 46 00 00 00 00 00 00 00
80: 02 00 00 00 00 00 00 00 24 f2 7d 5d 20 13 12 00
90: 10 0c 01 00 6b 00 10 b7 39 00 00 80 00 00 00 00
a0: ef 02 00 5d 00 00 00 00 00 00 00 00 00 00 00 00
b0: d8 5d 43 fe 4d 00 00 00 ed d5 00 62 f8 21 b8 41
c0: 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 27 c5 01 68 fb 35 0d c9 ea 15 0b c9 6f 93 01 89
e0: c7 d5 01 09 e3 14 c8 69 ff 16 0f 4d ce d5 80 48
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Capabilities: [f0] Secure device <?>
    Kernel driver in use: k8temp
00: 22 10 03 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 f0 00 00 00 00 00 00 00 00 00 00 00
40: ff 3b 04 00 40 00 10 0a 00 00 00 00 00 00 00 00
50: 20 48 0a 88 d0 00 00 00 00 00 00 00 c0 1e 0a 2b
60: 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 11 01 32 51 21 40 30 50 00 2a 00 08 17 21 00 00
80: 00 00 07 23 13 21 13 21 00 00 00 00 00 00 00 00
90: 00 00 00 00 66 17 00 00 a0 76 19 0b 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 01 a7 0d 00 00 00 a0 08 25 26 26 00
e0: 00 00 00 00 3e 21 36 00 19 17 00 00 00 00 00 00
f0: 0f 00 10 00 00 00 00 00 00 00 00 00 b2 0f 06 00

01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series]
    Subsystem: Elitegroup Computer Systems Device 2621
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin A routed to IRQ 5
    Region 0: Memory at d8000000 (64-bit, prefetchable) [size=128M]
    Region 2: Memory at fdee0000 (64-bit, non-prefetchable) [size=64K]
    Region 4: I/O ports at ee00 [size=256]
    Region 5: Memory at fdd00000 (32-bit, non-prefetchable) [size=1M]
    Capabilities: [50] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Address: 0000000000000000  Data: 0000
00: 02 10 1e 79 07 00 10 00 00 00 00 03 01 40 80 00
10: 0c 00 00 d8 00 00 00 00 04 00 ee fd 00 00 00 00
20: 01 ee 00 00 00 00 d0 fd 00 00 00 00 19 10 21 26
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 21 26
50: 01 80 02 06 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller
    Subsystem: ATI Technologies Inc Radeon X1200 Series Audio Controller
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64, Cache Line Size: 4 bytes
    Interrupt: pin B routed to IRQ 19
    Region 0: Memory at fdefc000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Address: 0000000000000000  Data: 0000
    Kernel driver in use: HDA Intel
00: 02 10 19 79 06 00 10 00 00 00 03 04 01 40 00 00
10: 04 c0 ef fd 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 19 79
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 19 79
50: 01 60 02 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
    Subsystem: Elitegroup Computer Systems Device 8167
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
    Interrupt: pin A routed to IRQ 22
    Region 0: I/O ports at de00 [size=256]
    Region 1: Memory at fdcff000 (32-bit, non-prefetchable) [size=256]
    [virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
    Capabilities: [dc] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Kernel driver in use: r8169
00: ec 10 67 81 17 00 b0 02 10 00 00 02 08 40 00 00
10: 01 de 00 00 00 f0 cf fd 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 67 81
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 20 40
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 c2 f7
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


DW

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
@ 2008-08-23 23:11 David Witbrodt
  0 siblings, 0 replies; 41+ messages in thread
From: David Witbrodt @ 2008-08-23 23:11 UTC (permalink / raw)
  To: Rufus & Azrael
  Cc: Yinghai Lu, Ingo Molnar, Vivek Goyal, Paul E. McKenney,
	Peter Zijlstra, Thomas Gleixner, H. Peter Anvin, netdev


> > Are you experiencing the same difficulties with kernels hanging after
> > version 2.6.25?
> >
> > In my case, kernels before 2.6.26 worked fine, but all kernels since
> > 2.6.26 hang during boot, and the problem was traced (using 'git bisect')
> > to commit number 3def3d6d.
> >
> > Please let me know your situation.
> >
> >
> > Thanks,
> > Dave W.
> >
> >    
> Hello David,
> 
> I have no such hanging on my recent kernels, just the dmesg :
> 
> > [    1.057255] hpet_resources: 0xfed00000 is busy
> and I find the present post to try solving this regression.

OK, thanks.  I thought you might be someone else.  I found another person
having the hang regression, and invited him to participate here.  I guess
you're not that person....


DW

^ permalink raw reply	[flat|nested] 41+ messages in thread

end of thread, other threads:[~2008-08-23 23:11 UTC | newest]

Thread overview: 41+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-23 23:09 HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression David Witbrodt
  -- strict thread matches above, loose matches on Subject: below --
2008-08-23 23:11 David Witbrodt
2008-08-23 20:00 David Witbrodt
2008-08-23 20:13 ` Rufus & Azrael
2008-08-23 19:29 David Witbrodt
2008-08-23 16:44 David Witbrodt
2008-08-23 16:32 David Witbrodt
2008-08-23 15:42 David Witbrodt
2008-08-23 15:55 ` Ingo Molnar
2008-08-23 11:58 David Witbrodt
2008-08-23 13:36 ` Ingo Molnar
2008-08-23 15:03   ` Ingo Molnar
2008-08-23 17:51 ` Yinghai Lu
2008-08-23 11:42 David Witbrodt
2008-08-23  2:25 David Witbrodt
2008-08-23  5:41 ` Yinghai Lu
2008-08-23  6:56   ` Yinghai Lu
2008-08-22  1:24 David Witbrodt
2008-08-21 16:53 David Witbrodt
2008-08-21 17:57 ` Yinghai Lu
2008-08-21 14:09 David Witbrodt
2008-08-21 15:33 ` Yinghai Lu
2008-08-21 13:33 David Witbrodt
2008-08-21  4:07 David Witbrodt
2008-08-21  6:42 ` Yinghai Lu
2008-08-21  7:04 ` Ilpo Järvinen
2008-08-21  2:48 David Witbrodt
2008-08-20 17:42 David Witbrodt
2008-08-20 17:58 ` Yinghai Lu
2008-08-21  2:02   ` Yinghai Lu
2008-08-20 16:44 David Witbrodt
2008-08-20 14:32 David Witbrodt
2008-08-20 14:49 ` Ingo Molnar
2008-08-20 14:08 David Witbrodt
2008-08-20  4:51 David Witbrodt
2008-08-20  5:21 ` Yinghai Lu
2008-08-20  7:51   ` Bill Fink
2008-08-20  8:02     ` Yinghai Lu
2008-08-20  9:15       ` Ingo Molnar
2008-08-20  9:31         ` Yinghai Lu
2008-08-20  9:36           ` Ingo Molnar

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).