DRI/AGP on AMD64 based machine

DRI/AGP on AMD64 based machine

[Alex Bennee]

Hi,

For a while now I've been meaning to get DRI running with my rv350
graphics card on my AMD64 machine. However I don't seem to be able to
get the right config-fu in the kernel to enable all the components.

For my sins I've been following the Gentoo Howto Wiki
(http://gentoo-wiki.com/HOWTO_DRI_with_ATi_Open-Source_Drivers)

A lot of the AGP stuff in the Kernel seems to be locked to 32 bit
kernels. The instructions seem to imply there is an am64-agp module
(which looks as though it builds in the tree but doesn't install) and
possibly an nvidea-agp module. I'm a little confused as I have both AMD
and NVidia chipsets on my machine:

malory agp # lspci             
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev
a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management
(rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0
Controller (rev a2)
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb
AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller
(v2.5) (rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller
(v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI
Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge
(rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon
9550]
01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550]
(Secondary)
02:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80)
02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)

Any clues on the correct AGP config options to switch on gratefully
received. My current .config looks like:

08:56 alex@malory [linux-2.6-stable.git] >grep "AGP" .config
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=m
# CONFIG_AGP_SIS is not set
CONFIG_AGP_VIA=m

08:59 alex@malory [linux-2.6-stable.git] >grep "DRM" .config
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
CONFIG_DRM_MGA=m
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

Regards,


--
Alex, homepage: http://www.bennee.com/~alex/
Television has brought back murder into the home -- where it belongs. --
Alfred Hitchcock

Re: DRI/AGP on AMD64 based machine

[Dave Jones]

On Wed, Jun 13, 2007 at 09:02:15AM +0100, Alex Bennee wrote:
 > Hi,
 > 
 > For a while now I've been meaning to get DRI running with my rv350
 > graphics card on my AMD64 machine. However I don't seem to be able to
 > get the right config-fu in the kernel to enable all the components.
 > 
 > For my sins I've been following the Gentoo Howto Wiki
 > (http://gentoo-wiki.com/HOWTO_DRI_with_ATi_Open-Source_Drivers)
 > 
 > A lot of the AGP stuff in the Kernel seems to be locked to 32 bit
 > kernels. The instructions seem to imply there is an am64-agp module
 > (which looks as though it builds in the tree but doesn't install) and
 > possibly an nvidea-agp module. I'm a little confused as I have both AMD
 > and NVidia chipsets on my machine:

For the sake of AGP, we only use the on-CPU GART.
The (nvidia) chipset one is ignored.

If amd64-agp isn't working for you, attach your dmesg.
(You can also confirm its working by running testgart[1])

	Dave

[1] http://www.codemonkey.org.uk/projects/agp/testgart.c

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

Re: DRI/AGP on AMD64 based machine

[Carlo Wood]

On Wed, Jun 13, 2007 at 12:29:25PM -0400, Dave Jones wrote:
> For the sake of AGP, we only use the on-CPU GART.
> The (nvidia) chipset one is ignored.
> 
> If amd64-agp isn't working for you, attach your dmesg.
> (You can also confirm its working by running testgart[1])

Hi Dave, I have an amd64 box for which every kernel
after 2.6.18 hangs during boot, so I have no dmesg :(

I used git bisect to find out where the problem patch is,
and assuming bisect works (imho it jumped between versions
very weirdly: closing in on the last 6 revisions, it
jumped from 2.6.18 to 2.6.18-rc2 to 2.6.18-rc6), the problem
is a patch in intel-agp.c, where support for the intel 965G
is added (which I have).

I mailed the author of the patch, including the git Id
of that patch... but he didn't reply... and I didn't keep the
mail :/ So, I am afraid I can't give much details.

I'd still like to have it sorted out. If you give me the
green light (in the sense that you are willing to help
a kernel-newbie when needed) then I'll have another
attempt at getting more information.

-- 
Carlo Wood <carlo@alinoe.com>

PS I believe it was you who committed the patch.

Re: DRI/AGP on AMD64 based machine

[Dave Airlie]

On 6/14/07, Carlo Wood <carlo@alinoe.com> wrote:
> On Wed, Jun 13, 2007 at 12:29:25PM -0400, Dave Jones wrote:
> > For the sake of AGP, we only use the on-CPU GART.
> > The (nvidia) chipset one is ignored.
> >
> > If amd64-agp isn't working for you, attach your dmesg.
> > (You can also confirm its working by running testgart[1])
>
> Hi Dave, I have an amd64 box for which every kernel
> after 2.6.18 hangs during boot, so I have no dmesg :(
>
> I used git bisect to find out where the problem patch is,
> and assuming bisect works (imho it jumped between versions
> very weirdly: closing in on the last 6 revisions, it
> jumped from 2.6.18 to 2.6.18-rc2 to 2.6.18-rc6), the problem
> is a patch in intel-agp.c, where support for the intel 965G
> is added (which I have).

How do you have a 965G in an amd64 box? does not compute.

Dave.

Re: DRI/AGP on AMD64 based machine

[Carlo Wood]

On Thu, Jun 14, 2007 at 11:17:50AM +1000, Dave Airlie wrote:
> How do you have a 965G in an amd64 box? does not compute.

Why not?  It's the ASUS P5B Deluxe motherboard with an
Intel P965/ICH8R chipset. The cpu is a QX6700 2.66 GHz,
that's an Intel Core 2 Quad Extreme.

amd64 is just the architecture, not the brand. It's an
all intel machine, if that's what you mean.

-- 
Carlo Wood <carlo@alinoe.com>

Re: DRI/AGP on AMD64 based machine

[Dave Airlie]

On 6/14/07, Carlo Wood <carlo@alinoe.com> wrote:
> On Thu, Jun 14, 2007 at 11:17:50AM +1000, Dave Airlie wrote:
> > How do you have a 965G in an amd64 box? does not compute.
>
> Why not?  It's the ASUS P5B Deluxe motherboard with an
> Intel P965/ICH8R chipset. The cpu is a QX6700 2.66 GHz,
> that's an Intel Core 2 Quad Extreme.
>
> amd64 is just the architecture, not the brand. It's an
> all intel machine, if that's what you mean.
>

x86-64 is an architecture, amd64 is used by some people however in
your case agp-amd64 is not what you wanted, you have a problem with
intel-agp.c then.. which is different than what started this thread..

Dave.

[AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Thu, Jun 14, 2007 at 03:15:06AM +0200, Carlo Wood wrote:
> Hi Dave, I have an amd64 box for which every kernel
> after 2.6.18 hangs during boot, so I have no dmesg :(
> 
> I used git bisect to find out where the problem patch is,
> and assuming bisect works (imho it jumped between versions
> very weirdly: closing in on the last 6 revisions, it
> jumped from 2.6.18 to 2.6.18-rc2 to 2.6.18-rc6), the problem
> is a patch in intel-agp.c, where support for the intel 965G
> is added (which I have).
> 
> I mailed the author of the patch, including the git Id
> of that patch... but he didn't reply... and I didn't keep the
> mail :/ So, I am afraid I can't give much details.
> 
> I'd still like to have it sorted out. If you give me the
> green light (in the sense that you are willing to help
> a kernel-newbie when needed) then I'll have another
> attempt at getting more information.

Dave, I have no idea why you never replied to this -- don't
you care that kernels 2.6.19 through 2.6.21 lockup on boot? --
here is a follow up on this matter.

I am not sure which patch it was exactly that broke things, but
I think it was:

    [AGPGART] Intel 965 Express support.
        
	    From: Alan Hourihane <alanh@tungstengraphics.com>
	    From: Eric Anholt <eric@anholt.net>
	    Signed-off-by: Dave Jones <davej@redhat.com>

65c25aadfa4e917060e99fe459f33a6a07db53cc

which was supplied after 2.6.18 and before 2.6.19-rc1.

If I remember that correctly, then Alan should have a mail
from me with the exact git Id (he never replied either).

The patch causes my machine to lock up and/or crash
in various ways (depending on the exact version of the kernel),
very shortly after printing: agpgart: Detected an Intel 965G Chipset.

The first kernel version that stops doing that is 2.6.22-rc5.
I used git bisect once more to find the patch that fixes this bug:

commit 9614ece14f23f2ce54a076c471aec9c91e51e79c
Author: Wang Zhenyu <zhenyu.z.wang@intel.com>
Date:   Wed May 30 09:45:58 2007 +0800

    [AGPGART] intel_agp: use table for device probe

    Fixed issues noted by Christoph Hellwig, and I changed device table
    scan a bit to allow the case that some models of graphics chips may
    have same host bridge type. This type of chip will be added in the future.

    This patch cleans up device probe function. Eric Anholt was the original aut hor.

    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Wang Zhenyu <zhenyu.z.wang@intel.com>
    Signed-off-by: Dave Jones <davej@redhat.com>

:040000 040000 625da154215c98f9016e14b952131a0c1ec8597b cddcf0b42d3632d20d7ee863 91d6ae6d258632e2 M      drivers

I am mailing this mostly because the comment doesn't seem to indicate
that the author is aware that this patch fixes an existing regression
(it worked fine for me with 2.6.18).

Anyway, thanks for fixing this Wang Zhenyu.

If anyone wants to know more (like what hardware I'm using), please
show me that you're actually alive / reading my mails.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Sun, Jun 17, 2007 at 06:22:35PM +0200, Carlo Wood wrote:

 > > Hi Dave, I have an amd64 box for which every kernel
 > > after 2.6.18 hangs during boot, so I have no dmesg :(
 > > 
 > > I used git bisect to find out where the problem patch is,
 > > and assuming bisect works (imho it jumped between versions
 > > very weirdly: closing in on the last 6 revisions, it
 > > jumped from 2.6.18 to 2.6.18-rc2 to 2.6.18-rc6), the problem
 > > is a patch in intel-agp.c, where support for the intel 965G
 > > is added (which I have).
 > Dave, I have no idea why you never replied to this -- don't
 > you care that kernels 2.6.19 through 2.6.21 lockup on boot? --

Sometimes things fall through the cracks..
I haven't heard any similar problems, which makes it somewhat odd.

 > The patch causes my machine to lock up and/or crash
 > in various ways (depending on the exact version of the kernel),
 > very shortly after printing: agpgart: Detected an Intel 965G Chipset.
 > 
 > The first kernel version that stops doing that is 2.6.22-rc5.
 > I used git bisect once more to find the patch that fixes this bug:
 > I am mailing this mostly because the comment doesn't seem to indicate
 > that the author is aware that this patch fixes an existing regression
 > (it worked fine for me with 2.6.18).

Indeed, it was unknown to me too, this should have just been
a clean-up.

 > If anyone wants to know more (like what hardware I'm using), please
 > show me that you're actually alive / reading my mails.

Out of curiousity, I'd like to see your lspci
(not -v or anything, just run with no args)

	Dave


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

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 03:07:14PM -0400, Dave Jones wrote:
> Sometimes things fall through the cracks..
> I haven't heard any similar problems, which makes it somewhat odd.

Ok. Well, the lockup is all to real here :p

I suspect a memory corruption going on, as under certain circumstances
there is printed more after the "agpgart: Detected an Intel 965G
Chipset." -- that is, the kernel *sometimes* doesn't hang silently,
but either reboots by itself (hard reset) or prints something
that looks like a total crash to me. Often, this is prefixed by
the name of running process. I am sorry, I never wrote any of that
down. Only the last time, it then went like:

agpgart: Detected an Intel 965G Chipset.
modprobe: Corrupt page table at address 20
PGD 178c6c067 PUD 201000c0049c04f BAD

This very same kernel (I boot it several times to see how
reproducable things were) always prints "agpgart: Detected an Intel 965G
Chipset." but then either hangs (two times), prints the above
and hangs (one time) or hard resets (one time).

Then I also booted the other kernels several times, and kernels
that booted fine ALWAYS boot fine - while kernels that locked
up (that I tested by booting them three times) only printed
the agpgart line and locked up three times.

>  > The patch causes my machine to lock up and/or crash
>  > in various ways (depending on the exact version of the kernel),
>  > very shortly after printing: agpgart: Detected an Intel 965G Chipset.
>  > 
>  > The first kernel version that stops doing that is 2.6.22-rc5.
>  > I used git bisect once more to find the patch that fixes this bug:
>  > I am mailing this mostly because the comment doesn't seem to indicate
>  > that the author is aware that this patch fixes an existing regression
>  > (it worked fine for me with 2.6.18).
> 
> Indeed, it was unknown to me too, this should have just been
> a clean-up.

I hope you saw my later post too? I sent it to you too - but also to the
list, so I don't know if you'll notice it.

The Subject of that post is: 2.6.22-rc5 regression

I concluded too soon that 2.6.22-rc5 was working :(.
I just really tested it and it doesn't! Same error.

Please have a look at that other post of me and lets continue this
thread there.

> Out of curiousity, I'd like to see your lspci
> (not -v or anything, just run with no args)

I'll add that to that other thread.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Sun, Jun 17, 2007 at 09:59:01PM +0200, Carlo Wood wrote:
 > On Sun, Jun 17, 2007 at 03:07:14PM -0400, Dave Jones wrote:
 > > Sometimes things fall through the cracks..
 > > I haven't heard any similar problems, which makes it somewhat odd.
 > 
 > Ok. Well, the lockup is all to real here :p
 > 
 > I suspect a memory corruption going on, as under certain circumstances
 > there is printed more after the "agpgart: Detected an Intel 965G
 > Chipset." -- that is, the kernel *sometimes* doesn't hang silently,
 > but either reboots by itself (hard reset) or prints something
 > that looks like a total crash to me. Often, this is prefixed by
 > the name of running process. I am sorry, I never wrote any of that
 > down. Only the last time, it then went like:
 > 
 > agpgart: Detected an Intel 965G Chipset.
 > modprobe: Corrupt page table at address 20
 > PGD 178c6c067 PUD 201000c0049c04f BAD

That's pretty bad corruption indeed.  What I'm puzzling over though
is why other 965G users aren't seeing the same thing.
My own 965G seems to be fine, though that's using Intel graphics
instead of nvidia.

(Just to rule it out, I'm assuming at this stage in boot that the
 nvidia driver module has never been loaded?)

And if you never load the agpgart modules, you never see lockups?

Right now, I'm at a loss to explain this.

	Dave

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

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 04:49:04PM -0400, Dave Jones wrote:
> That's pretty bad corruption indeed.  What I'm puzzling over though
> is why other 965G users aren't seeing the same thing.
> My own 965G seems to be fine, though that's using Intel graphics
> instead of nvidia.
> 
> (Just to rule it out, I'm assuming at this stage in boot that the
>  nvidia driver module has never been loaded?)

Doesn't even exist for that kernel. I only compiled a new
nvidia driver module for one kernel - the one that I am using
on a daily basis.

> And if you never load the agpgart modules, you never see lockups?

What would the name be of such module?

In fact, I think that when the kernel does NOT lockup, it
doesn't print this "agpgart: Detected.." line either.

Ie, the dmesg of cf68676222e54cd0a31efd968da00e65f9a0963f
which boots fine, gives:

$ grep Detected dmesg-cf686
time.c: Detected 2666.669 MHz processor.
Detected 16.666 MHz APIC timer.

$ grep agpgart dmesg-cf686
Linux agpgart interface v0.102 (c) Dave Jones


Does that give an indication of what you want me to test/try?

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Sun, Jun 17, 2007 at 11:13:38PM +0200, Carlo Wood wrote:
 > On Sun, Jun 17, 2007 at 04:49:04PM -0400, Dave Jones wrote:
 > > That's pretty bad corruption indeed.  What I'm puzzling over though
 > > is why other 965G users aren't seeing the same thing.
 > > My own 965G seems to be fine, though that's using Intel graphics
 > > instead of nvidia.
 > > 
 > > (Just to rule it out, I'm assuming at this stage in boot that the
 > >  nvidia driver module has never been loaded?)
 > 
 > Doesn't even exist for that kernel. I only compiled a new
 > nvidia driver module for one kernel - the one that I am using
 > on a daily basis.
 > 
 > > And if you never load the agpgart modules, you never see lockups?
 > 
 > What would the name be of such module?

intel-agp

Though by the looks of things, with the working kernel, you don't have
it loaded (it's dependant upon the 'agpgart' module, which prints the
"Detected" line that was missing).

	Dave

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

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
>  > What would the name be of such module?
> 
> intel-agp
> 
> Though by the looks of things, with the working kernel, you don't have
> it loaded (it's dependant upon the 'agpgart' module, which prints the
> "Detected" line that was missing).

hikaru:~>lsmod | grep agp
intel_agp              31776  0

It's loaded right now... that is with 2.6.22-rc4-+something (one of the
working ones).  I don't know WHEN it was loaded though. Probably
not at the same time as the others. 

And

hikaru:~>dmesg | grep agpgart
Linux agpgart interface v0.102 (c) Dave Jones

No 'Detected' line :/

Also, I noted that this 'agpgart: Detected..' line is always(?) printed
right after (often even without THAT line having printed a newline yet!)
something like:

udev: Waiting for /dev to be fully populated...agpgart: Detected an Intel 965G Chipset.

And this 'udev: Waiting for /dev to be fully populated' (sorry, didn't
write down the exact phrase, this is from memory) is also not printed
by kernels that work.

-- 
Carlo Wood <carlo@alinoe.com>

PS I asked you move to the other thread - it's a bit annoying to have
two threads about this now.

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
>  > What would the name be of such module?
> 
> intel-agp
> 
> Though by the looks of things, with the working kernel, you don't have
> it loaded (it's dependant upon the 'agpgart' module, which prints the
> "Detected" line that was missing).

I can rmmod intel-agp without problems.
The agpgart module isn't loaded.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
> intel-agp
> 
> Though by the looks of things, with the working kernel, you don't have
> it loaded (it's dependant upon the 'agpgart' module, which prints the
> "Detected" line that was missing).

You are wrong.

1)

I don't have any agpgart module at all, in any of the kernels that I compiled.

$ find /lib/modules -name 'agpgart.ko'
$ /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 -name '*agp*.ko'
/lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/sis-agp.ko
/lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko
/lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/via-agp.ko

2)

$ strings /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko | grep 'agpgart: Detected an Intel'
<6>agpgart: Detected an Intel %s Chipset.

Hence, in the case that the kernel works, intel-agp is loaded
WITHOUT printing this Detected line - while when it doesn't work,
it is loaded while printing this line.

Perhaps my "solution" is to remove this module completely?
I don't seem to need it.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Mon, Jun 18, 2007 at 12:36:49AM +0200, Carlo Wood wrote:
 > On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
 > > intel-agp
 > > 
 > > Though by the looks of things, with the working kernel, you don't have
 > > it loaded (it's dependant upon the 'agpgart' module, which prints the
 > > "Detected" line that was missing).
 > 
 > You are wrong.
 > I don't have any agpgart module at all, in any of the kernels that I compiled.

ok, then you must have CONFIG_AGP=y

 > $ find /lib/modules -name 'agpgart.ko'
 > $ /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 -name '*agp*.ko'
 > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/sis-agp.ko
 > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko
 > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/via-agp.ko
 > 
 > 2)
 > 
 > $ strings /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko | grep 'agpgart: Detected an Intel'
 > <6>agpgart: Detected an Intel %s Chipset.
 > 
 > Hence, in the case that the kernel works, intel-agp is loaded
 > WITHOUT printing this Detected line

That doesn't make much sense.  The hardware doesn't change between
a working & not-working kernel, and somehow the PCI probing fails.
Hmm, do you have CONFIG_EDAC set ?
There's an outstanding bug (well, lack of feature) , where it claims
the PCI device before AGP gets a chance to.
This is unrelated to your hang however, but would at least explain
the inconsistent probing.

 > Perhaps my "solution" is to remove this module completely?
 > I don't seem to need it.

It's needed only for 3d, but it'd be good to figure out why its so
broken on your system, even if you don't need it.

	Dave

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

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Sun, Jun 17, 2007 at 06:49:18PM -0400, Dave Jones wrote:
> ok, then you must have CONFIG_AGP=y

I do - not voluntary however. For some mysterious reason I am
unable to set it to n or m. I am also not able to set CONFIG_AGP_INTEL
to n, only to y or m.
(using make 'menuconfig' for example).

>  > $ find /lib/modules -name 'agpgart.ko'
>  > $ /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 -name '*agp*.ko'
>  > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/sis-agp.ko
>  > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko
>  > /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/via-agp.ko
>  > 
>  > 2)
>  > 
>  > $ strings /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko | grep 'agpgart: Detected an Intel'
>  > <6>agpgart: Detected an Intel %s Chipset.
>  > 
>  > Hence, in the case that the kernel works, intel-agp is loaded
>  > WITHOUT printing this Detected line
> 
> That doesn't make much sense.  The hardware doesn't change between
> a working & not-working kernel, and somehow the PCI probing fails.
> Hmm, do you have CONFIG_EDAC set ?

CONFIG_EDAC=m

$ lsmod | grep edac
$

> There's an outstanding bug (well, lack of feature) , where it claims
> the PCI device before AGP gets a chance to.
> This is unrelated to your hang however, but would at least explain
> the inconsistent probing.
> 
>  > Perhaps my "solution" is to remove this module completely?
>  > I don't seem to need it.
> 
> It's needed only for 3d,

Nope - I just played UT2004 without problems, and without intel-agp loaded.

> but it'd be good to figure out why its so
> broken on your system, even if you don't need it.

Please tell me what to do / try.
I'm an experienced coder - but I never really played with the
kernel before - so you'll have to spell out how to turn on debugging etc.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Mon, Jun 18, 2007 at 02:06:43AM +0200, Carlo Wood wrote:
 > On Sun, Jun 17, 2007 at 06:49:18PM -0400, Dave Jones wrote:
 > > ok, then you must have CONFIG_AGP=y
 > 
 > I do - not voluntary however. For some mysterious reason I am
 > unable to set it to n or m.

You likely have CONFIG_IOMMU set. This makes AGP non-optional.

 > I am also not able to set CONFIG_AGP_INTEL
 > to n, only to y or m.
 > (using make 'menuconfig' for example).

Can't explain that one.

 > >  > Hence, in the case that the kernel works, intel-agp is loaded
 > >  > WITHOUT printing this Detected line
 > > 
 > > That doesn't make much sense.  The hardware doesn't change between
 > > a working & not-working kernel, and somehow the PCI probing fails.
 > > Hmm, do you have CONFIG_EDAC set ?
 > 
 > CONFIG_EDAC=m
 > 
 > $ lsmod | grep edac

ok, red herring.

 > > There's an outstanding bug (well, lack of feature) , where it claims
 > > the PCI device before AGP gets a chance to.
 > > This is unrelated to your hang however, but would at least explain
 > > the inconsistent probing.
 > > 
 > >  > Perhaps my "solution" is to remove this module completely?
 > >  > I don't seem to need it.
 > > 
 > > It's needed only for 3d,
 > 
 > Nope - I just played UT2004 without problems, and without intel-agp loaded.

Using the nvidia driver? It has its own built-in AGP support which will
get used if the kernel AGP support is missing.

 > > but it'd be good to figure out why its so
 > > broken on your system, even if you don't need it.
 > 
 > Please tell me what to do / try.
 > I'm an experienced coder - but I never really played with the
 > kernel before - so you'll have to spell out how to turn on debugging etc.

Right now, I'm at a loss to explain the corruption, so it's
difficult to suggest what to try.

	Dave

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

Re: [AGPGART] intel_agp: use table for device probe

[Dave Airlie]

>
> Right now, I'm at a loss to explain the corruption, so it's
> difficult to suggest what to try.

The thing is here, this is PCIE, so if there is a GPU plugged into the
PCIE 16x slot in theory the main onboard graphics should disable, AGP
code is used to control the GART for the onboard chip, in this case a
plugged in card will  not use AGP, I wonder have Intel tested with a
pcie card in place...

Dave.

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
> >Right now, I'm at a loss to explain the corruption, so it's
> >difficult to suggest what to try.
> 
> The thing is here, this is PCIE, so if there is a GPU plugged into the
> PCIE 16x slot in theory the main onboard graphics should disable, AGP
> code is used to control the GART for the onboard chip, in this case a
> plugged in card will  not use AGP, I wonder have Intel tested with a
> pcie card in place...

That is Chinese for me :/.
Do you want me to try something?

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Dave Airlie]

> >
> > The thing is here, this is PCIE, so if there is a GPU plugged into the
> > PCIE 16x slot in theory the main onboard graphics should disable, AGP
> > code is used to control the GART for the onboard chip, in this case a
> > plugged in card will  not use AGP, I wonder have Intel tested with a
> > pcie card in place...
>
> That is Chinese for me :/.
> Do you want me to try something?
>

Well it was more for davej's benefit, in theory for your machine with
a PCIE graphics card you don't need agpgart enabled at all granted it
shouldn't screw up if it is..

Dave.

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Mon, Jun 18, 2007 at 12:18:32PM +1000, Dave Airlie wrote:
> Well it was more for davej's benefit, in theory for your machine with
> a PCIE graphics card you don't need agpgart enabled at all granted it
> shouldn't screw up if it is..

I can't disable it though.

I am not THAT much interested in disabling it however as long as I
get help here to debug this. I am interested in finding out what is
causing the crash, can't stand it to have a bug on my machine without
knowing what it is ;)

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Wang Zhenyu]

On 2007.06.18 03:56:36 +0000, Carlo Wood wrote:
> On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
> > >Right now, I'm at a loss to explain the corruption, so it's
> > >difficult to suggest what to try.
> > 
> > The thing is here, this is PCIE, so if there is a GPU plugged into the
> > PCIE 16x slot in theory the main onboard graphics should disable, AGP
> > code is used to control the GART for the onboard chip, in this case a
> > plugged in card will  not use AGP, I wonder have Intel tested with a
> > pcie card in place...

Agree. We seem to always enable AGP even IGD is disabled or not exists,
other card should not depend on this module ever.

> 
> That is Chinese for me :/.
> Do you want me to try something?

Carlo, I've just built latest kernel git tree on a Dell 965G box and
have a NV card plugged-in. It boots fine.

Linux agpgart interface v0.102 (c) Dave Jones
agpgart: Detected an Intel 965G Chipset.
agpgart: AGP aperture is 256M @ 0x0

I don't know why it hangs your machine when loading this module, it should
just not bother anything. But from your last "modprobe: ..." line, it seems
there's really badness somewhere, do you have serial console to see more
in the message?

Re: [AGPGART] intel_agp: use table for device probe

[Chuck Ebbert]

On 06/17/2007 10:37 PM, Wang Zhenyu wrote:
> On 2007.06.18 03:56:36 +0000, Carlo Wood wrote:
>> On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
>>>> Right now, I'm at a loss to explain the corruption, so it's
>>>> difficult to suggest what to try.
>>> The thing is here, this is PCIE, so if there is a GPU plugged into the
>>> PCIE 16x slot in theory the main onboard graphics should disable, AGP
>>> code is used to control the GART for the onboard chip, in this case a
>>> plugged in card will  not use AGP, I wonder have Intel tested with a
>>> pcie card in place...
> 
> Agree. We seem to always enable AGP even IGD is disabled or not exists,
> other card should not depend on this module ever.
> 
>> That is Chinese for me :/.
>> Do you want me to try something?
> 
> Carlo, I've just built latest kernel git tree on a Dell 965G box and
> have a NV card plugged-in. It boots fine.
> 
> Linux agpgart interface v0.102 (c) Dave Jones
> agpgart: Detected an Intel 965G Chipset.
> agpgart: AGP aperture is 256M @ 0x0
> 
> I don't know why it hangs your machine when loading this module, it should
> just not bother anything. But from your last "modprobe: ..." line, it seems
> there's really badness somewhere, do you have serial console to see more
> in the message?

There are also these bug reports:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229913
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242101

Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones]

On Mon, Jun 18, 2007 at 01:42:13PM -0400, Chuck Ebbert wrote:
 > On 06/17/2007 10:37 PM, Wang Zhenyu wrote:
 > > On 2007.06.18 03:56:36 +0000, Carlo Wood wrote:
 > >> On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
 > >>>> Right now, I'm at a loss to explain the corruption, so it's
 > >>>> difficult to suggest what to try.
 > >>> The thing is here, this is PCIE, so if there is a GPU plugged into the
 > >>> PCIE 16x slot in theory the main onboard graphics should disable, AGP
 > >>> code is used to control the GART for the onboard chip, in this case a
 > >>> plugged in card will  not use AGP, I wonder have Intel tested with a
 > >>> pcie card in place...
 > > 
 > > Agree. We seem to always enable AGP even IGD is disabled or not exists,
 > > other card should not depend on this module ever.
 > > 
 > >> That is Chinese for me :/.
 > >> Do you want me to try something?
 > > 
 > > Carlo, I've just built latest kernel git tree on a Dell 965G box and
 > > have a NV card plugged-in. It boots fine.
 > > 
 > > Linux agpgart interface v0.102 (c) Dave Jones
 > > agpgart: Detected an Intel 965G Chipset.
 > > agpgart: AGP aperture is 256M @ 0x0
 > > 
 > > I don't know why it hangs your machine when loading this module, it should
 > > just not bother anything. But from your last "modprobe: ..." line, it seems
 > > there's really badness somewhere, do you have serial console to see more
 > > in the message?
 > 
 > There are also these bug reports:
 > 
 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229913
 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242101

good find.

Looking through intel-agp brings up a wart that I've been 
complaining about for a while.

Start looking for functions with '965' in them.
the first one you hit is the wonderfully named
'intel_i830_init_gtt_entries'.
Two thirds of that function no longer have anything to
do with an i830.  Instead of adding a intel_i965_init_gtt_entries,
this thing has grown into a monster dealing with three different
generations of hardware.

This results in tables like this..

static const struct agp_bridge_driver intel_i965_driver = {
       .owner                  = THIS_MODULE,
       .aperture_sizes         = intel_i830_sizes,
       .size_type              = FIXED_APER_SIZE,
       .num_aperture_sizes     = 4,
       .needs_scratch_page     = TRUE,
       .configure              = intel_i915_configure,
       .fetch_size             = intel_i9xx_fetch_size,
       .cleanup                = intel_i915_cleanup,
       .tlb_flush              = intel_i810_tlbflush,
       .mask_memory            = intel_i965_mask_memory,
       .masks                  = intel_i810_masks,
       .agp_enable             = intel_i810_agp_enable,
       .cache_flush            = global_cache_flush,
       .create_gatt_table      = intel_i965_create_gatt_table,
       .free_gatt_table        = intel_i830_free_gatt_table,
       .insert_memory          = intel_i915_insert_entries,
       .remove_memory          = intel_i915_remove_entries,
       .alloc_by_type          = intel_i830_alloc_by_type,
       .free_by_type           = intel_i810_free_by_type,
       .agp_alloc_page         = agp_generic_alloc_page,
       .agp_destroy_page       = agp_generic_destroy_page,
       .agp_type_to_mask_type  = intel_i830_type_to_mask_type,

so we use bits and pieces from 810, 830, 915, and throw in
some new 965 routines too.  Why is this a mess ?
Because it's non-trivial to just look at this table
and spot bugs like "wait, that 810 should be using 915"
without lots of staring at data sheets.
Additionally each time we twist these routines to cope with
an additional chipset, we risk breaking previous generations.

Having functions do ONE thing is a good thing, even if
it means having 15 of them that look similar.
The alternative of a single function that becomes a nest
of if's & switches is just horrible.

It could be that all of the above is actually pointing to
the correct routines.  It could also be that the codepaths
in those routines, as twisty as they are, are fine, and this
is just some normal bug, but hunting for it becomes a lot
harder when the code is this baroque.

	Dave

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

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Mon, Jun 18, 2007 at 01:42:13PM -0400, Chuck Ebbert wrote:
> There are also these bug reports:
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229913
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242101

I managed to set up a serial console for booting, and because
of these bug reports tried to boot 2.6.22-rc5 with and without
agp=off. With agp=off it does indeed boot fine.

Here is the result for both cases (I've been so free to remove
any occurance of ^M and replace ESC with the two characters ^[):

rawserial-master-188e1:

Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
^[[H^[[J
    GNU GRUB  version 0.97  (635K lower / 2095680K upper memory)

^[[m^[[4;2H+-------------------------------------------------------------------------+^[[5;2H|^[[5;76H|^[[6;2H|^[[6;76H|^[[7;2H|^[[7;76H|^[[8;2H|^[[8;76H|^[[9;2H|^[[9;76H|^[[10;2H|^[[10;76H|^[[11;2H|^[[11;76H|^[[12;2H|^[[12;76H|^[[13;2H|^[[13;76H|^[[14;2H|^[[14;76H|^[[15;2H|^[[15;76H|^[[16;2H|^[[16;76H|^[[17;2H+-------------------------------------------------------------------------+^[[m
    Use the ^ and v keys to select which entry is highlighted.
    Press enter to boot the selected OS, 'e' to edit the
    commands before booting, or 'c' for a command-line.^[[5;78H ^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64                        ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode)     ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.18-4-amd64                                 ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.18-4-amd64 (single-user mode)              ^[[10;75H^[[m^[[m^[[11;3H                                                                         ^[[11;75H^[[m^[[m^[[12;3H                                                                         ^[[12;75H^[[m^[[m^[[13;3H                                                                         ^[[13;75H^[[m^[[m^[[14;3H                                                                         ^[[14;75H^[[m^[[m^[[15;3H                                                                         ^[[15;75H^[[m^[[m^[[16;3H                                                                         ^[[16;75H^[[m^[[16;78H ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 5 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 4 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 3 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 2 seconds.   ^[[5;75H^[[23;4H                                                                    ^[[5;75H^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31a!
 f1b65a2f
3611d>  ^[[5;75H^[[m^[[H^[[J  Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611
df4c670b092bbac-amd64'

root  (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel  /vmlinuz-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd
64 root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
   [Linux-bzImage, setup=0x1e00, size=0x17ac68]
initrd  /initrd.img-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-
amd64
   [Linux-initrd @ 0x379e6000, 0x60989e bytes]
savedefault

Linux version 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 (carlo@hikaru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Jun 17 18:45:05 CEST 2007
Command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
 BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007ff90000 (usable)
 BIOS-e820: 000000007ff90000 - 000000007ff9e000 (ACPI data)
 BIOS-e820: 000000007ff9e000 - 000000007ffe0000 (ACPI NVS)
 BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000180000000 (usable)
end_pfn_map = 1572864
DMI 2.4 present.
ACPI: RSDP 000FAE40, 0024 (r2 ACPIAM)
ACPI: XSDT 7FF90100, 0054 (r1 ÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿ  3000709 MSFT       97)
ACPI: FACP 7FF90290, 00F4 (r3 MSTEST OEMFACP   3000709 MSFT       97)
ACPI: DSDT 7FF905C0, 8E7D (r1  A0483 A0483035       35 INTL 20060113)
ACPI: FACS 7FF9E000, 0040
ACPI: APIC 7FF90390, 006C (r1 MSTEST OEMAPIC   3000709 MSFT       97)
ACPI: MCFG 7FF90400, 003C (r1 MSTEST OEMMCFG   3000709 MSFT       97)
ACPI: SLIC 7FF90440, 0176 (r1 ÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿ  3000709 MSFT       97)
ACPI: OEMB 7FF9E040, 007B (r1 MSTEST AMI_OEM   3000709 MSFT       97)
ACPI: HPET 7FF99440, 0038 (r1 MSTEST OEMHPET   3000709 MSFT       97)
No NUMA configuration found
Faking a node at 0000000000000000-0000000180000000
Bootmem setup node 0 0000000000000000-0000000180000000
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1572864
early_node_map[3] active PFN ranges
    0:        0 ->      158
    0:      256 ->   524176
    0:  1048576 ->  1572864
ACPI: PM-Timer IO Port: 0x808
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Processor #2
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
Processor #3
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to flat
ACPI: HPET id: 0x8086a202 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
swsusp: Registered nosave memory region: 000000000009e000 - 000000000009f000
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000e4000
swsusp: Registered nosave memory region: 00000000000e4000 - 0000000000100000
swsusp: Registered nosave memory region: 000000007ff90000 - 000000007ff9e000
swsusp: Registered nosave memory region: 000000007ff9e000 - 000000007ffe0000
swsusp: Registered nosave memory region: 000000007ffe0000 - 0000000080000000
swsusp: Registered nosave memory region: 0000000080000000 - 00000000fee00000
swsusp: Registered nosave memory region: 00000000fee00000 - 00000000fee01000
swsusp: Registered nosave memory region: 00000000fee01000 - 00000000ffb00000
swsusp: Registered nosave memory region: 00000000ffb00000 - 0000000100000000
Allocating PCI resources starting at 88000000 (gap: 80000000:7ee00000)
SMP: Allowing 4 CPUs, 0 hotplug CPUs
PERCPU: Allocating 37768 bytes of per cpu data
Built 1 zonelists.  Total pages: 1025869
Kernel command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
time.c: Detected 2666.666 MHz processor.
Console: colour VGA+ 80x25
Checking aperture...
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing software IO TLB between 0x1059000 - 0x5059000
Memory: 4030964k/6291456k available (2015k kernel code, 162500k reserved, 947k data, 296k init)
Calibrating delay using timer specific routine.. 5336.91 BogoMIPS (lpj=10673826)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 0/0 -> Node 0
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
Using local APIC timer interrupts.
result 16666650
Detected 16.666 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/4 APIC 0x2
Initializing CPU#1
Calibrating delay using timer specific routine.. 5333.56 BogoMIPS (lpj=10667122)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 1/2 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
SMP alternatives: switching to SMP code
Booting processor 2/4 APIC 0x1
Initializing CPU#2
Calibrating delay using timer specific routine.. 5333.39 BogoMIPS (lpj=10666789)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 2/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU2: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#2]: passed.
SMP alternatives: switching to SMP code
Booting processor 3/4 APIC 0x3
Initializing CPU#3
Calibrating delay using timer specific routine.. 5333.36 BogoMIPS (lpj=10666733)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 3/3 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU3: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#3]: passed.
Brought up 4 CPUs
migration_cost=3360
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH6 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 *14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 15 devices
ACPI: ACPI bus type pnp unregistered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NET: Registered protocol family 8
NET: Registered protocol family 20
PCI-GART: No AMD northbridge found.
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
ACPI: RTC can wake from S4
pnp: 00:01: iomem range 0xfed14000-0xfed19fff has been reserved
pnp: 00:07: ioport range 0x290-0x297 has been reserved
pnp: 00:08: iomem range 0xffafe000-0xffb0cbff could not be reserved
pnp: 00:08: iomem range 0xffb00000-0xffbfffff could not be reserved
pnp: 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
pnp: 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
pnp: 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
pnp: 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:0e: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0e: iomem range 0xc0000-0xcffff has been reserved
Time: tsc clocksource has been installed.
pnp: 00:0e: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0e: iomem range 0x100000-0x7fffffff could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: a000-afff
  MEM window: f8800000-fe8fffff
  PREFETCH window: bfe00000-dfdfffff
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: dfe00000-dfefffff
PCI: Bridge: 0000:00:1c.5
  IO window: b000-bfff
  MEM window: fe900000-fe9fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
  IO window: c000-cfff
  MEM window: fea00000-feafffff
  PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 17 (level, low) -> IRQ 17
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 524288 (order: 11, 12582912 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 6182k freed
audit: initializing netlink socket (disabled)
audit(1182191783.492:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
assign_interrupt_mode Found MSI capability
assign_interrupt_mode Found MSI capability
assign_interrupt_mode Found MSI capability
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.102 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03: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
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /class/input/input0
Freeing unused kernel memory: 296k freed
Loading, please wait...
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
ACPI Warning (tbutils-0158): Incorrect checksum in table [OEMB] -  F5, should be F4 [20070126]
ACPI: SSDT 7FF9E0C0, 0208 (r1    AMI   CPU1PM        1 INTL 20060113)
ACPI: SSDT 7FF9E2D0, 013A (r1    AMI   CPU2PM        1 INTL 20060113)
ACPI: SSDT 7FF9E410, 013A (r1    AMI   CPU3PM        1 INTL 20060113)
ACPI: SSDT 7FF9E550, 013A (r1    AMI   CPU4PM        1 INTL 20060113)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000e000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
SCSI subsystem initialized
ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 17 (level, low) -> IRQ 17
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000e080
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d880
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000dc00
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:1a.7[C] -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 6
usb 4-2: new low speed USB device using uhci_hcd and address 2
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfebff400
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 4 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 7
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfebff000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb 4-2: configuration #1 chosen from 1 choice
usb 4-2: can't set config #1, error -71
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 6 ports detected
usb 4-2: USB disconnect, address 2
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
usb 4-2: new low speed USB device using uhci_hcd and address 3
usb 4-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A as /class/input/input1
input: USB HID v1.10 Mouse [Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A] on usb-0000:00:1d.1-2
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 cmd 0xffffc20001448900 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata2: SATA max UDMA/133 cmd 0xffffc20001448980 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata3: SATA max UDMA/133 cmd 0xffffc20001448a00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata4: SATA max UDMA/133 cmd 0xffffc20001448a80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata5: SATA max UDMA/133 cmd 0xffffc20001448b00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata6: SATA max UDMA/133 cmd 0xffffc20001448b80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata1.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata1.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata2.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata2.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata2.00: configured for UDMA/133
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata3.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata3.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 625142448
ata4.00: ATA-7: ST3320620AS, 3.AAE, max UDMA/133
ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 625142448
ata4.00: configured for UDMA/133
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI: LITE-ON DVDRW LH-20A1S, 9L02, max UDMA/100
ata5.00: configured for UDMA/100
ata6: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 2:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access     ATA      ST3320620AS      3.AA PQ: 0 ANSI: 5
scsi 4:0:0:0: CD-ROM            LITE-ON  DVDRW LH-20A1S   9L02 PQ: 0 ANSI: 5
ACPI: PCI Interrupt 0000:04:03.0[A] -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21]  MMIO=[feaff800-feafffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] 145226112 512-byte hardware sectors (74356 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 145226112 512-byte hardware sectors (74356 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 >
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: [sdc] 145226112 512-byte hardware sectors (74356 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 145226112 512-byte hardware sectors (74356 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 >
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd1 sdd2 sdd3
sd 3:0:0:0: [sdd] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: Attached scsi generic sg3 type 0
sr 4:0:0:0: Attached scsi generic sg4 type 5
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Begin: Loading Mmd: raid1 personality registered for level 1
D modules ...
raid5: automatically using best checksumming function: generic_sse
Success: loaded module raid1.
   generic_sse:  9514.000 MB/sec
raid5: using function: generic_sse (9514.000 MB/sec)
raid6: int64x1   2500 MB/s
raid6: int64x2   3017 MB/s
raid6: int64x4   2881 MB/s
raid6: int64x8   1921 MB/s
raid6: sse2x1    4193 MB/s
raid6: sse2x2    4612 MB/s
raid6: sse2x4    7864 MB/s
raid6: using algorithm sse2x4 (7864 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Success: loaded module raid456.
Done.
Begin: Amd: md0 stopped.
ssembling all MD arrays ...
md: bind<sdb1>
md: bind<sdc1>
md: bind<sda1>
raid1: raid set md0 active with 3 out of 3 mirrors
mdadm: /dev/md0 md: md1 stopped.
has been started with 3 drives.
md: bind<sdb2>
md: bind<sdc2>
md: bind<sda2>
raid5: device sda2 operational as raid disk 0
raid5: device sdc2 operational as raid disk 2
raid5: device sdb2 operational as raid disk 1
raid5: allocated 3212kB for md1
raid5: raid level 5 set md1 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda2
 disk 1, o:1, dev:sdb2
 disk 2, o:1, dev:sdc2
mdadm: /dev/md1 md: md2 stopped.
has been started with 3 drives.
md: bind<sdb3>
md: bind<sdc3>
md: bind<sda3>
raid5: device sda3 operational as raid disk 0
raid5: device sdc3 operational as raid disk 2
raid5: device sdb3 operational as raid disk 1
raid5: allocated 3212kB for md2
raid5: raid level 5 set md2 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 2, o:1, dev:sdc3
mdadm: /dev/md2 md: md3 stopped.
has been started with 3 drives.
md: bind<sdb5>
md: bind<sdc5>
md: bind<sda5>
raid5: device sda5 operational as raid disk 0
raid5: device sdc5 operational as raid disk 2
raid5: device sdb5 operational as raid disk 1
raid5: allocated 3212kB for md3
raid5: raid level 5 set md3 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda5
 disk 1, o:1, dev:sdb5
 disk 2, o:1, dev:sdc5
mdadm: /dev/md3 md: md4 stopped.
has been started with 3 drives.
md: bind<sdb6>
md: bind<sdc6>
md: bind<sda6>
raid5: device sda6 operational as raid disk 0
raid5: device sdc6 operational as raid disk 2
raid5: device sdb6 operational as raid disk 1
raid5: allocated 3212kB for md4
raid5: raid level 5 set md4 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda6
 disk 1, o:1, dev:sdb6
 disk 2, o:1, dev:sdc6
mdadm: /dev/md4 md: md5 stopped.
has been started with 3 drives.
md: bind<sdb7>
md: bind<sdc7>
md: bind<sda7>
raid5: device sda7 operational as raid disk 0
raid5: device sdc7 operational as raid disk 2
raid5: device sdb7 operational as raid disk 1
raid5: allocated 3212kB for md5
raid5: raid level 5 set md5 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda7
 disk 1, o:1, dev:sdb7
 disk 2, o:1, dev:sdc7
mdadm: /dev/md5 md: md6 stopped.
has been started with 3 drives.
md: bind<sdb8>
md: bind<sdc8>
md: bind<sda8>
raid5: device sda8 operational as raid disk 0
raid5: device sdc8 operational as raid disk 2
raid5: device sdb8 operational as raid disk 1
raid5: allocated 3212kB for md6
raid5: raid level 5 set md6 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda8
 disk 1, o:1, dev:sdb8
 disk 2, o:1, dev:sdc8
mdadm: /dev/md6 md: md7 stopped.
has been started with 3 drives.
md: bind<sdb9>
md: bind<sdc9>
md: bind<sda9>
raid5: device sda9 operational as raid disk 0
raid5: device sdc9 operational as raid disk 2
raid5: device sdb9 operational as raid disk 1
raid5: allocated 3212kB for md7
raid5: raid level 5 set md7 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda9
 disk 1, o:1, dev:sdb9
 disk 2, o:1, dev:sdc9
mdadm: /dev/md7 md: md8 stopped.
has been started with 3 drives.
md: bind<sdb10>
md: bind<sdc10>
md: bind<sda10>
raid5: device sda10 operational as raid disk 0
raid5: device sdc10 operational as raid disk 2
raid5: device sdb10 operational as raid disk 1
raid5: allocated 3212kB for md8
raid5: raid level 5 set md8 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda10
 disk 1, o:1, dev:sdb10
 disk 2, o:1, dev:sdc10
mdadm: /dev/md8 has been started with 3 drives.
Success: assembled all arrays.
Done.
Begin: Executing udevtrigger again ...
Done.
Done.
Begin: Running /scripts/local-premount ...
Attempting manual resume
kinit: name_to_dev_t(/dev/md1) = md1(9,1)
kinit: trying to resume from /dev/md1
kinit: No resume image, doing normal boot...
Done.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
Mount failed for selinuxfs on /selinux:  No such device
INIT: version 2.86 booting
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...agpgart: Detected an Intel 965G Chipset.


======================================================================================
rawserial-master-188e1-agp=off:

Press any key to continue.
Press any key to continue.
Press any key to continue.
Press any key to continue.
^[[H^[[J
    GNU GRUB  version 0.97  (635K lower / 2095680K upper memory)

^[[m^[[4;2H+-------------------------------------------------------------------------+^[[5;2H|^[[5;76H|^[[6;2H|^[[6;76H|^[[7;2H|^[[7;76H|^[[8;2H|^[[8;76H|^[[9;2H|^[[9;76H|^[[10;2H|^[[10;76H|^[[11;2H|^[[11;76H|^[[12;2H|^[[12;76H|^[[13;2H|^[[13;76H|^[[14;2H|^[[14;76H|^[[15;2H|^[[15;76H|^[[16;2H|^[[16;76H|^[[17;2H+-------------------------------------------------------------------------+^[[m
    Use the ^ and v keys to select which entry is highlighted.
    Press enter to boot the selected OS, 'e' to edit the
    commands before booting, or 'c' for a command-line.^[[5;78H ^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64                        ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode)     ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.18-4-amd64                                 ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.18-4-amd64 (single-user mode)              ^[[10;75H^[[m^[[m^[[11;3H                                                                         ^[[11;75H^[[m^[[m^[[12;3H                                                                         ^[[12;75H^[[m^[[m^[[13;3H                                                                         ^[[13;75H^[[m^[[m^[[14;3H                                                                         ^[[14;75H^[[m^[[m^[[15;3H                                                                         ^[[15;75H^[[m^[[m^[[16;3H                                                                         ^[[16;75H^[[m^[[16;78H ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 5 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 4 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 3 seconds.   ^[[5;75H^[[23;4H                                                                    ^[[5;75H^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[H^[[J  Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-m!
 aster-18
8e1f81ba31af1b65a2f3611
df4c670b092bbac-amd64'

root  (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel  /vmlinuz-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd
64 root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
   [Linux-bzImage, setup=0x1e00, size=0x17ac68]
initrd  /initrd.img-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-
amd64
   [Linux-initrd @ 0x379e6000, 0x60989e bytes]
savedefault

Linux version 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 (carlo@hikaru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Jun 17 18:45:05 CEST 2007
Command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
 BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007ff90000 (usable)
 BIOS-e820: 000000007ff90000 - 000000007ff9e000 (ACPI data)
 BIOS-e820: 000000007ff9e000 - 000000007ffe0000 (ACPI NVS)
 BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000180000000 (usable)
end_pfn_map = 1572864
DMI 2.4 present.
ACPI: RSDP 000FAE40, 0024 (r2 ACPIAM)
ACPI: XSDT 7FF90100, 0054 (r1 ÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿ  3000709 MSFT       97)
ACPI: FACP 7FF90290, 00F4 (r3 MSTEST OEMFACP   3000709 MSFT       97)
ACPI: DSDT 7FF905C0, 8E7D (r1  A0483 A0483035       35 INTL 20060113)
ACPI: FACS 7FF9E000, 0040
ACPI: APIC 7FF90390, 006C (r1 MSTEST OEMAPIC   3000709 MSFT       97)
ACPI: MCFG 7FF90400, 003C (r1 MSTEST OEMMCFG   3000709 MSFT       97)
ACPI: SLIC 7FF90440, 0176 (r1 ÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿ  3000709 MSFT       97)
ACPI: OEMB 7FF9E040, 007B (r1 MSTEST AMI_OEM   3000709 MSFT       97)
ACPI: HPET 7FF99440, 0038 (r1 MSTEST OEMHPET   3000709 MSFT       97)
No NUMA configuration found
Faking a node at 0000000000000000-0000000180000000
Bootmem setup node 0 0000000000000000-0000000180000000
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1572864
early_node_map[3] active PFN ranges
    0:        0 ->      158
    0:      256 ->   524176
    0:  1048576 ->  1572864
ACPI: PM-Timer IO Port: 0x808
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Processor #2
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
Processor #3
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to flat
ACPI: HPET id: 0x8086a202 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
swsusp: Registered nosave memory region: 000000000009e000 - 000000000009f000
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000e4000
swsusp: Registered nosave memory region: 00000000000e4000 - 0000000000100000
swsusp: Registered nosave memory region: 000000007ff90000 - 000000007ff9e000
swsusp: Registered nosave memory region: 000000007ff9e000 - 000000007ffe0000
swsusp: Registered nosave memory region: 000000007ffe0000 - 0000000080000000
swsusp: Registered nosave memory region: 0000000080000000 - 00000000fee00000
swsusp: Registered nosave memory region: 00000000fee00000 - 00000000fee01000
swsusp: Registered nosave memory region: 00000000fee01000 - 00000000ffb00000
swsusp: Registered nosave memory region: 00000000ffb00000 - 0000000100000000
Allocating PCI resources starting at 88000000 (gap: 80000000:7ee00000)
SMP: Allowing 4 CPUs, 0 hotplug CPUs
PERCPU: Allocating 37768 bytes of per cpu data
Built 1 zonelists.  Total pages: 1025869
Kernel command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
time.c: Detected 2666.669 MHz processor.
Console: colour VGA+ 80x25
Checking aperture...
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing software IO TLB between 0x1059000 - 0x5059000
Memory: 4030964k/6291456k available (2015k kernel code, 162500k reserved, 947k data, 296k init)
Calibrating delay using timer specific routine.. 5336.89 BogoMIPS (lpj=10673790)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 0/0 -> Node 0
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
Using local APIC timer interrupts.
result 16666671
Detected 16.666 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/4 APIC 0x2
Initializing CPU#1
Calibrating delay using timer specific routine.. 5333.45 BogoMIPS (lpj=10666915)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 1/2 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
SMP alternatives: switching to SMP code
Booting processor 2/4 APIC 0x1
Initializing CPU#2
Calibrating delay using timer specific routine.. 5333.58 BogoMIPS (lpj=10667172)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 2/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU2: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#2]: passed.
SMP alternatives: switching to SMP code
Booting processor 3/4 APIC 0x3
Initializing CPU#3
Calibrating delay using timer specific routine.. 5333.36 BogoMIPS (lpj=10666726)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 3/3 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU3: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
checking TSC synchronization [CPU#0 -> CPU#3]: passed.
Brought up 4 CPUs
migration_cost=3357
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH6 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 *14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 15 devices
ACPI: ACPI bus type pnp unregistered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NET: Registered protocol family 8
NET: Registered protocol family 20
PCI-GART: No AMD northbridge found.
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
ACPI: RTC can wake from S4
pnp: 00:01: iomem range 0xfed14000-0xfed19fff has been reserved
pnp: 00:07: ioport range 0x290-0x297 has been reserved
pnp: 00:08: iomem range 0xffafe000-0xffb0cbff could not be reserved
pnp: 00:08: iomem range 0xffb00000-0xffbfffff could not be reserved
pnp: 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
pnp: 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
pnp: 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
pnp: 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
Time: tsc clocksource has been installed.
pnp: 00:0e: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0e: iomem range 0xc0000-0xcffff has been reserved
pnp: 00:0e: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0e: iomem range 0x100000-0x7fffffff could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: a000-afff
  MEM window: f8800000-fe8fffff
  PREFETCH window: bfe00000-dfdfffff
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: dfe00000-dfefffff
PCI: Bridge: 0000:00:1c.5
  IO window: b000-bfff
  MEM window: fe900000-fe9fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
  IO window: c000-cfff
  MEM window: fea00000-feafffff
  PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 17 (level, low) -> IRQ 17
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 524288 (order: 11, 12582912 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 6182k freed
audit: initializing netlink socket (disabled)
audit(1182191286.492:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
assign_interrupt_mode Found MSI capability
assign_interrupt_mode Found MSI capability
assign_interrupt_mode Found MSI capability
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03: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
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /class/input/input0
Freeing unused kernel memory: 296k freed
Loading, please wait...
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
ACPI Warning (tbutils-0158): Incorrect checksum in table [OEMB] -  F5, should be F4 [20070126]
ACPI: SSDT 7FF9E0C0, 0208 (r1    AMI   CPU1PM        1 INTL 20060113)
ACPI: SSDT 7FF9E2D0, 013A (r1    AMI   CPU2PM        1 INTL 20060113)
ACPI: SSDT 7FF9E410, 013A (r1    AMI   CPU3PM        1 INTL 20060113)
ACPI: SSDT 7FF9E550, 013A (r1    AMI   CPU4PM        1 INTL 20060113)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000e000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
SCSI subsystem initialized
ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 17 (level, low) -> IRQ 17
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000e080
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:1a.7[C] -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfebff400
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d800
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d880
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:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000dc00
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 7
usb 5-2: new low speed USB device using uhci_hcd and address 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfebff000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 6 ports detected
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
usb 5-2: new low speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A as /class/input/input1
input: USB HID v1.10 Mouse [Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A] on usb-0000:00:1d.1-2
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 cmd 0xffffc20001448900 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata2: SATA max UDMA/133 cmd 0xffffc20001448980 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata3: SATA max UDMA/133 cmd 0xffffc20001448a00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata4: SATA max UDMA/133 cmd 0xffffc20001448a80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata5: SATA max UDMA/133 cmd 0xffffc20001448b00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata6: SATA max UDMA/133 cmd 0xffffc20001448b80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata1.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata1.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata2.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata2.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata2.00: configured for UDMA/133
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata3.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
ata3.00: 145226112 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: ata_hpa_resize 1: sectors = 145226112, hpa_sectors = 145226112
ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 625142448
ata4.00: ATA-7: ST3320620AS, 3.AAE, max UDMA/133
ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 625142448
ata4.00: configured for UDMA/133
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI: LITE-ON DVDRW LH-20A1S, 9L02, max UDMA/100
ata5.00: configured for UDMA/100
ata6: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 2:0:0:0: Direct-Access     ATA      WDC WD740ADFD-00 20.0 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access     ATA      ST3320620AS      3.AA PQ: 0 ANSI: 5
scsi 4:0:0:0: CD-ROM            LITE-ON  DVDRW LH-20A1S   9L02 PQ: 0 ANSI: 5
ACPI: PCI Interrupt 0000:04:03.0[A] -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21]  MMIO=[feaff800-feafffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] 145226112 512-byte hardware sectors (74356 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 145226112 512-byte hardware sectors (74356 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 >
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: [sdc] 145226112 512-byte hardware sectors (74356 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 145226112 512-byte hardware sectors (74356 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 >
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdd] 625142448 512-byte hardware sectors (320073 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd1 sdd2 sdd3
sd 3:0:0:0: [sdd] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: Attached scsi generic sg3 type 0
sr 4:0:0:0: Attached scsi generic sg4 type 5
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Begin: Loading Mmd: raid1 personality registered for level 1
D modules ...
raid5: automatically using best checksumming function: generic_sse
Success: loaded module raid1.
   generic_sse:  9512.000 MB/sec
raid5: using function: generic_sse (9512.000 MB/sec)
raid6: int64x1   2501 MB/s
raid6: int64x2   3018 MB/s
raid6: int64x4   2881 MB/s
raid6: int64x8   1921 MB/s
raid6: sse2x1    4208 MB/s
raid6: sse2x2    5243 MB/s
raid6: sse2x4    7870 MB/s
raid6: using algorithm sse2x4 (7870 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Success: loaded module raid456.
Done.
Begin: Amd: md0 stopped.
ssembling all MD arrays ...
md: bind<sdb1>
md: bind<sdc1>
md: bind<sda1>
raid1: raid set md0 active with 3 out of 3 mirrors
mdadm: /dev/md0 md: md1 stopped.
has been started with 3 drives.
md: bind<sdb2>
md: bind<sdc2>
md: bind<sda2>
raid5: device sda2 operational as raid disk 0
raid5: device sdc2 operational as raid disk 2
raid5: device sdb2 operational as raid disk 1
raid5: allocated 3212kB for md1
raid5: raid level 5 set md1 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda2
 disk 1, o:1, dev:sdb2
 disk 2, o:1, dev:sdc2
mdadm: /dev/md1 md: md2 stopped.
has been started with 3 drives.
md: bind<sdb3>
md: bind<sdc3>
md: bind<sda3>
raid5: device sda3 operational as raid disk 0
raid5: device sdc3 operational as raid disk 2
raid5: device sdb3 operational as raid disk 1
raid5: allocated 3212kB for md2
raid5: raid level 5 set md2 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 2, o:1, dev:sdc3
mdadm: /dev/md2 md: md3 stopped.
has been started with 3 drives.
md: bind<sdb5>
md: bind<sdc5>
md: bind<sda5>
raid5: device sda5 operational as raid disk 0
raid5: device sdc5 operational as raid disk 2
raid5: device sdb5 operational as raid disk 1
raid5: allocated 3212kB for md3
raid5: raid level 5 set md3 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda5
 disk 1, o:1, dev:sdb5
 disk 2, o:1, dev:sdc5
mdadm: /dev/md3 md: md4 stopped.
has been started with 3 drives.
md: bind<sdb6>
md: bind<sdc6>
md: bind<sda6>
raid5: device sda6 operational as raid disk 0
raid5: device sdc6 operational as raid disk 2
raid5: device sdb6 operational as raid disk 1
raid5: allocated 3212kB for md4
raid5: raid level 5 set md4 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda6
 disk 1, o:1, dev:sdb6
 disk 2, o:1, dev:sdc6
mdadm: /dev/md4 md: md5 stopped.
has been started with 3 drives.
md: bind<sdb7>
md: bind<sdc7>
md: bind<sda7>
raid5: device sda7 operational as raid disk 0
raid5: device sdc7 operational as raid disk 2
raid5: device sdb7 operational as raid disk 1
raid5: allocated 3212kB for md5
raid5: raid level 5 set md5 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda7
 disk 1, o:1, dev:sdb7
 disk 2, o:1, dev:sdc7
mdadm: /dev/md5 md: md6 stopped.
has been started with 3 drives.
md: bind<sdb8>
md: bind<sdc8>
md: bind<sda8>
raid5: device sda8 operational as raid disk 0
raid5: device sdc8 operational as raid disk 2
raid5: device sdb8 operational as raid disk 1
raid5: allocated 3212kB for md6
raid5: raid level 5 set md6 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda8
 disk 1, o:1, dev:sdb8
 disk 2, o:1, dev:sdc8
mdadm: /dev/md6 md: md7 stopped.
has been started with 3 drives.
md: bind<sdb9>
md: bind<sdc9>
md: bind<sda9>
raid5: device sda9 operational as raid disk 0
raid5: device sdc9 operational as raid disk 2
raid5: device sdb9 operational as raid disk 1
raid5: allocated 3212kB for md7
raid5: raid level 5 set md7 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda9
 disk 1, o:1, dev:sdb9
 disk 2, o:1, dev:sdc9
mdadm: /dev/md7 md: md8 stopped.
has been started with 3 drives.
md: bind<sdb10>
md: bind<sdc10>
md: bind<sda10>
raid5: device sda10 operational as raid disk 0
raid5: device sdc10 operational as raid disk 2
raid5: device sdb10 operational as raid disk 1
raid5: allocated 3212kB for md8
raid5: raid level 5 set md8 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:sda10
 disk 1, o:1, dev:sdb10
 disk 2, o:1, dev:sdc10
mdadm: /dev/md8 has been started with 3 drives.
Success: assembled all arrays.
Done.
Begin: Executing udevtrigger again ...
Done.
Done.
Begin: Running /scripts/local-premount ...
Attempting manual resume
kinit: name_to_dev_t(/dev/md1) = md1(9,1)
kinit: trying to resume from /dev/md1
kinit: No resume image, doing kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
normal boot...
Done.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
Mount failed for selinuxfs on /selinux:  No such device
INIT: version 2.86 booting
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
sky2 0000:02:00.0: v1.14 addr 0xfe9fc000 irq 17 Yukon-EC Ultra (0xb4) rev 2
input: PC Speaker as /class/input/input2
sky2 eth0: addr 00:1a:92:3a:4a:c1
PCI: Enabling device 0000:00:1f.3 (0001 -> 0003)
ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18
gameport: EMU10K1 is pci0000:04:02.1/gameport0, io 0xcc00, speed 1041kHz
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 23 (level, low) -> IRQ 23
input: PS/2 Logitech Mouse as /class/input/input3
done.
Setting parameters of disc: (none).
Checking root file system...fsck 1.40-WIP (14-Nov-2006)
/dev/md2: clean, 14667/488640 files, 100111/975904 blocks
done.
EXT3 FS on md2, internal journal
Setting the system clock..
Cleaning up ifupdown....
Loading kernel modules...loop: module loaded
coretemp coretemp.0: Using undocumented features, absolute temperature might be wrong!
coretemp coretemp.1: Using undocumented features, absolute temperature might be wrong!
coretemp coretemp.2: Using undocumented features, absolute temperature might be wrong!
coretemp coretemp.3: Using undocumented features, absolute temperature might be wrong!
done.
Loading device-mapper supportdevice-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
.
Generating udev events for MD arrays...done.
Starting early crypto disks... cswap(starting) encrypted(starting)
Enter LUKS passphrase: 
key slot 1 unlocked.
Command successful.
done.
Starting remaining crypto disks... cswap(running) encrypted(running)done.
Checking file systems...fsck 1.40-WIP (14-Nov-2006)
/dev/md0: clean, 36/24096 files, 35121/96256 blocks (check after next mount)
/dev/md5: clean, 40392/1221600 files, 1043914/2441824 blocks
/dev/sdd2: clean, 10111/4889248 files, 5934404/9765511 blocks
/dev/sdd3: clean, 1778/21987328 files, 35333378/43961872 blocks (check in 5 mounts)
/dev/md8: clean, 116771/2747136 files, 909662/5490144 blocks
/dev/md3: clean, 101351/2443200 files, 672471/4883712 blocks
/dev/md6: clean, 53/1221600 files, 76570/2441824 blocks
/dev/md7: clean, 1179413/7323648 files, 5757529/14647200 blocks
/dev/md4: clean, 7509/732960 files, 268934/1465856 blocks (check in 3 mounts)
/dev/mapper/encrypted: clean, 14607/12222464 files, 13969744/24414646 blocks
done.
Setting kernel variables...done.
Mounting local filesystems...kjournald starting.  Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdd2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdd3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
done.
Activating swapfile swap...Adding 15631096k swap on /dev/mapper/cswap.  Priority:1 extents:1 across:15631096k
done.
Detecting hardware...Setting up networking....
Configuring network interfaces...done.
Starting portmap daemon....
sky2 eth1: enabling interface
sky2 eth1: ram buffer 0K
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
Setting sensors limits: done.
Setting console screen modes and fonts.
Setting up ALSA...done.
Recovering schroot sessions: sid32-df306a93-1d63-494d-a726-c924190900c6.
INIT: Entering runlevel: 2
Starting system log daemon....
Starting kernel log daemon....
Starting portmap daemon...Already running..
Starting HP Linux Printing and Imaging System: hpiod hpssdsky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
.
Loading ACPI modules...input: Power Button (FF) as /class/input/input4
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input5
ACPI: Power Button (CM) [PWRB]
.
Starting Advanced Configuration and Power Interface daemon....
Starting BitTorrent tracker: disabled in /etc/default/bittorrent.
Starting Common Unix Printing System: cupsdlp: driver loaded but no devices found
ppdev: user-space parallel port driver
.
Starting system message bus: dbus.
Starting network connection manager: NetworkManager.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting network events dispatcher: NetworkManagerDispatcher.
Starting MTA: exim4.
Starting mouse interface server: gpm.
Starting disk temperature monitoring daemon: hddtemp:  /dev/sda /dev/sdb /dev/sdc /dev/sdd..
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsdNFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
 mountd.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshd.
Starting GNOME Display Manager: gdm.
Starting NFS common utilities: statd idmapd.
Starting DHCP D-Bus daemon: dhcdbd.
Starting Hardware abstraction layer: hald.
Starting MD monitoring service: mdadm --monitor.
Starting anac(h)ronistic cron: anacron.
Starting periodic command scheduler: crond.

Debian GNU/Linux lenny/sid hikaru ttyS0

hikaru login: 
===================================================================================

And the diff between the two:

--- rawserial-master-188e1-agp=off	2007-06-18 22:00:49.000000000 +0200
+++ rawserial-master-188e1	2007-06-18 22:00:59.000000000 +0200
@@ -2,19 +2,22 @@
 Press any key to continue.
 Press any key to continue.
 Press any key to continue.
+Press any key to continue.
+Press any key to continue.
+Press any key to continue.
 ^[[H^[[J
     GNU GRUB  version 0.97  (635K lower / 2095680K upper memory)
 
 ^[[m^[[4;2H+-------------------------------------------------------------------------+^[[5;2H|^[[5;76H|^[[6;2H|^[[6;76H|^[[7;2H|^[[7;76H|^[[8;2H|^[[8;76H|^[[9;2H|^[[9;76H|^[[10;2H|^[[10;76H|^[[11;2H|^[[11;76H|^[[12;2H|^[[12;76H|^[[13;2H|^[[13;76H|^[[14;2H|^[[14;76H|^[[15;2H|^[[15;76H|^[[16;2H|^[[16;76H|^[[17;2H+-------------------------------------------------------------------------+^[[m
     Use the ^ and v keys to select which entry is highlighted.
     Press enter to boot the selected OS, 'e' to edit the
-    commands before booting, or 'c' for a command-line.^[[5;78H ^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64                        ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode)     ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.18-4-amd64                                 ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.18-4-amd64 (single-user mode)              ^[[10;75H^[[m^[[m^[[11;3H                                                                         ^[[11;75H^[[m^[[m^[[12;3H                                                                         ^[[12;75H^[[m^[[m^[[13;3H                                                                         ^[[13;75H^[[m^[[m^[[14;3H                                                                         ^[[14;75H^[[m^[[m^[[15;3H                                                                         ^[[15;75H^[[m^[[m^[[16;3H                                                                         ^[[16;75H^[[m^[[16;78H ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 5 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 4 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 3 seconds.   ^[[5;75H^[[23;4H                                                                    ^[[5;75H^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[H^[[J  Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-!
 master-1
88e1f81ba31af1b65a2f3611
+    commands before booting, or 'c' for a command-line.^[[5;78H ^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64                        ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode)     ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.18-4-amd64                                 ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.18-4-amd64 (single-user mode)              ^[[10;75H^[[m^[[m^[[11;3H                                                                         ^[[11;75H^[[m^[[m^[[12;3H                                                                         ^[[12;75H^[[m^[[m^[[13;3H                                                                         ^[[13;75H^[[m^[[m^[[14;3H                                                                         ^[[14;75H^[[m^[[m^[[15;3H                                                                         ^[[15;75H^[[m^[[m^[[16;3H                                                                         ^[[16;75H^[[m^[[16;78H ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 5 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 4 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 3 seconds.   ^[[5;75H^[[23;4H The highlighted entry will be booted automatically in 2 seconds.   ^[[5;75H^[[23;4H                                                                    ^[[5;75H^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d>  ^[[6;75H^[[m^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31!
 af1b65a2
f3611d>  ^[[5;75H^[[m^[[H^[[J  Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611
 df4c670b092bbac-amd64'
 
 root  (hd0,0)
  Filesystem type is ext2fs, partition type 0xfd
 kernel  /vmlinuz-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd
-64 root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
+64 root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
    [Linux-bzImage, setup=0x1e00, size=0x17ac68]
 initrd  /initrd.img-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-
 amd64
@@ -22,7 +25,7 @@
 savedefault
 
 Linux version 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 (carlo@hikaru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Jun 17 18:45:05 CEST 2007
-Command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
+Command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
 BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
  BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
@@ -88,17 +91,17 @@
 SMP: Allowing 4 CPUs, 0 hotplug CPUs
 PERCPU: Allocating 37768 bytes of per cpu data
 Built 1 zonelists.  Total pages: 1025869
-Kernel command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8 agp=off
+Kernel command line: root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
 Initializing CPU#0
 PID hash table entries: 4096 (order: 12, 32768 bytes)
 Extended CMOS year: 2000
-time.c: Detected 2666.669 MHz processor.
+time.c: Detected 2666.666 MHz processor.
 Console: colour VGA+ 80x25
 Checking aperture...
 PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
 Placing software IO TLB between 0x1059000 - 0x5059000
 Memory: 4030964k/6291456k available (2015k kernel code, 162500k reserved, 947k data, 296k init)
-Calibrating delay using timer specific routine.. 5336.89 BogoMIPS (lpj=10673790)
+Calibrating delay using timer specific routine.. 5336.91 BogoMIPS (lpj=10673826)
 Security Framework v1.0.0 initialized
 SELinux:  Disabled at boot.
 Capability LSM initialized
@@ -115,12 +118,12 @@
 SMP alternatives: switching to UP code
 ACPI: Core revision 20070126
 Using local APIC timer interrupts.
-result 16666671
+result 16666650
 Detected 16.666 MHz APIC timer.
 SMP alternatives: switching to SMP code
 Booting processor 1/4 APIC 0x2
 Initializing CPU#1
-Calibrating delay using timer specific routine.. 5333.45 BogoMIPS (lpj=10666915)
+Calibrating delay using timer specific routine.. 5333.56 BogoMIPS (lpj=10667122)
 CPU: L1 I cache: 32K, L1 D cache: 32K
 CPU: L3 cache: 4096K
 CPU 1/2 -> Node 0
@@ -132,7 +135,7 @@
 SMP alternatives: switching to SMP code
 Booting processor 2/4 APIC 0x1
 Initializing CPU#2
-Calibrating delay using timer specific routine.. 5333.58 BogoMIPS (lpj=10667172)
+Calibrating delay using timer specific routine.. 5333.39 BogoMIPS (lpj=10666789)
 CPU: L1 I cache: 32K, L1 D cache: 32K
 CPU: L3 cache: 4096K
 CPU 2/1 -> Node 0
@@ -144,7 +147,7 @@
 SMP alternatives: switching to SMP code
 Booting processor 3/4 APIC 0x3
 Initializing CPU#3
-Calibrating delay using timer specific routine.. 5333.36 BogoMIPS (lpj=10666726)
+Calibrating delay using timer specific routine.. 5333.36 BogoMIPS (lpj=10666733)
 CPU: L1 I cache: 32K, L1 D cache: 32K
 CPU: L3 cache: 4096K
 CPU 3/3 -> Node 0
@@ -154,7 +157,7 @@
 Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz stepping 07
 checking TSC synchronization [CPU#0 -> CPU#3]: passed.
 Brought up 4 CPUs
-migration_cost=3357
+migration_cost=3360
 NET: Registered protocol family 16
 ACPI: bus type pci registered
 PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
@@ -200,9 +203,9 @@
 pnp: 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
 pnp: 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
 pnp: 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
-Time: tsc clocksource has been installed.
 pnp: 00:0e: iomem range 0x0-0x9ffff could not be reserved
 pnp: 00:0e: iomem range 0xc0000-0xcffff has been reserved
+Time: tsc clocksource has been installed.
 pnp: 00:0e: iomem range 0xe0000-0xfffff could not be reserved
 pnp: 00:0e: iomem range 0x100000-0x7fffffff could not be reserved
 PCI: Bridge: 0000:00:01.0
@@ -233,7 +236,7 @@
 checking if image is initramfs... it is
 Freeing initrd memory: 6182k freed
 audit: initializing netlink socket (disabled)
-audit(1182191286.492:1): initialized
+audit(1182191783.492:1): initialized
 VFS: Disk quotas dquot_6.5.1
 Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
 io scheduler noop registered
@@ -244,6 +247,7 @@
 assign_interrupt_mode Found MSI capability
 assign_interrupt_mode Found MSI capability
 Real Time Clock Driver v1.12ac
+Linux agpgart interface v0.102 (c) Dave Jones
 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
 RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
@@ -281,49 +285,52 @@
 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:1a.7[C] -> GSI 18 (level, low) -> IRQ 18
-ehci_hcd 0000:00:1a.7: EHCI Host Controller
-ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 3
-ehci_hcd 0000:00:1a.7: debug port 1
-ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfebff400
-ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
-usb usb3: configuration #1 chosen from 1 choice
-hub 3-0:1.0: USB hub found
-hub 3-0:1.0: 4 ports detected
 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
 uhci_hcd 0000:00:1d.0: UHCI Host Controller
-uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4
+uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 3
 uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d800
-usb usb4: configuration #1 chosen from 1 choice
-hub 4-0:1.0: USB hub found
-hub 4-0:1.0: 2 ports detected
+usb usb3: configuration #1 chosen from 1 choice
+hub 3-0:1.0: USB hub found
+hub 3-0:1.0: 2 ports detected
 ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
 uhci_hcd 0000:00:1d.1: UHCI Host Controller
-uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5
+uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 4
 uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d880
-usb usb5: configuration #1 chosen from 1 choice
-hub 5-0:1.0: USB hub found
-hub 5-0:1.0: 2 ports detected
+usb usb4: configuration #1 chosen from 1 choice
+hub 4-0:1.0: USB hub found
+hub 4-0:1.0: 2 ports detected
 ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
 uhci_hcd 0000:00:1d.2: UHCI Host Controller
-uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6
+uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 5
 uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000dc00
+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:1a.7[C] -> GSI 18 (level, low) -> IRQ 18
+ehci_hcd 0000:00:1a.7: EHCI Host Controller
+ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 6
+usb 4-2: new low speed USB device using uhci_hcd and address 2
+ehci_hcd 0000:00:1a.7: debug port 1
+ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfebff400
+ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
 usb usb6: configuration #1 chosen from 1 choice
 hub 6-0:1.0: USB hub found
-hub 6-0:1.0: 2 ports detected
+hub 6-0:1.0: 4 ports detected
 ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23
 ehci_hcd 0000:00:1d.7: EHCI Host Controller
 ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 7
-usb 5-2: new low speed USB device using uhci_hcd and address 2
 ehci_hcd 0000:00:1d.7: debug port 1
 ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfebff000
 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
+usb 4-2: configuration #1 chosen from 1 choice
+usb 4-2: can't set config #1, error -71
 usb usb7: configuration #1 chosen from 1 choice
 hub 7-0:1.0: USB hub found
 hub 7-0:1.0: 6 ports detected
+usb 4-2: USB disconnect, address 2
 ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
-usb 5-2: new low speed USB device using uhci_hcd and address 3
-usb 5-2: configuration #1 chosen from 1 choice
+usb 4-2: new low speed USB device using uhci_hcd and address 3
+usb 4-2: configuration #1 chosen from 1 choice
 usbcore: registered new interface driver hiddev
 input: Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A as /class/input/input1
 input: USB HID v1.10 Mouse [Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A] on usb-0000:00:1d.1-2
@@ -426,16 +433,16 @@
 D modules ...
 raid5: automatically using best checksumming function: generic_sse
 Success: loaded module raid1.
-   generic_sse:  9512.000 MB/sec
-raid5: using function: generic_sse (9512.000 MB/sec)
-raid6: int64x1   2501 MB/s
-raid6: int64x2   3018 MB/s
+   generic_sse:  9514.000 MB/sec
+raid5: using function: generic_sse (9514.000 MB/sec)
+raid6: int64x1   2500 MB/s
+raid6: int64x2   3017 MB/s
 raid6: int64x4   2881 MB/s
 raid6: int64x8   1921 MB/s
-raid6: sse2x1    4208 MB/s
-raid6: sse2x2    5243 MB/s
-raid6: sse2x4    7870 MB/s
-raid6: using algorithm sse2x4 (7870 MB/s)
+raid6: sse2x1    4193 MB/s
+raid6: sse2x2    4612 MB/s
+raid6: sse2x4    7864 MB/s
+raid6: using algorithm sse2x4 (7864 MB/s)
 md: raid6 personality registered for level 6
 md: raid5 personality registered for level 5
 md: raid4 personality registered for level 4
@@ -577,10 +584,10 @@
 Attempting manual resume
 kinit: name_to_dev_t(/dev/md1) = md1(9,1)
 kinit: trying to resume from /dev/md1
-kinit: No resume image, doing kjournald starting.  Commit interval 5 seconds
-EXT3-fs: mounted filesystem with ordered data mode.
-normal boot...
+kinit: No resume image, doing normal boot...
 Done.
+kjournald starting.  Commit interval 5 seconds
+EXT3-fs: mounted filesystem with ordered data mode.
 Begin: Running /scripts/local-bottom ...
 Done.
 Done.
@@ -590,138 +597,4 @@
 INIT: version 2.86 booting
 Starting the hotplug events dispatcher: udevd.
 Synthesizing the initial hotplug events...done.
-Waiting for /dev to be fully populated...iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
-iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0860)
-iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
-ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
-sky2 0000:02:00.0: v1.14 addr 0xfe9fc000 irq 17 Yukon-EC Ultra (0xb4) rev 2
-input: PC Speaker as /class/input/input2
-sky2 eth0: addr 00:1a:92:3a:4a:c1
-PCI: Enabling device 0000:00:1f.3 (0001 -> 0003)
-ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18
-gameport: EMU10K1 is pci0000:04:02.1/gameport0, io 0xcc00, speed 1041kHz
-ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 23 (level, low) -> IRQ 23
-input: PS/2 Logitech Mouse as /class/input/input3
-done.
-Setting parameters of disc: (none).
-Checking root file system...fsck 1.40-WIP (14-Nov-2006)
-/dev/md2: clean, 14667/488640 files, 100111/975904 blocks
-done.
-EXT3 FS on md2, internal journal
-Setting the system clock..
-Cleaning up ifupdown....
-Loading kernel modules...loop: module loaded
-coretemp coretemp.0: Using undocumented features, absolute temperature might be wrong!
-coretemp coretemp.1: Using undocumented features, absolute temperature might be wrong!
-coretemp coretemp.2: Using undocumented features, absolute temperature might be wrong!
-coretemp coretemp.3: Using undocumented features, absolute temperature might be wrong!
-done.
-Loading device-mapper supportdevice-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
-.
-Generating udev events for MD arrays...done.
-Starting early crypto disks... cswap(starting) encrypted(starting)
-Enter LUKS passphrase: 
-key slot 1 unlocked.
-Command successful.
-done.
-Starting remaining crypto disks... cswap(running) encrypted(running)done.
-Checking file systems...fsck 1.40-WIP (14-Nov-2006)
-/dev/md0: clean, 36/24096 files, 35121/96256 blocks (check after next mount)
-/dev/md5: clean, 40392/1221600 files, 1043914/2441824 blocks
-/dev/sdd2: clean, 10111/4889248 files, 5934404/9765511 blocks
-/dev/sdd3: clean, 1778/21987328 files, 35333378/43961872 blocks (check in 5 mounts)
-/dev/md8: clean, 116771/2747136 files, 909662/5490144 blocks
-/dev/md3: clean, 101351/2443200 files, 672471/4883712 blocks
-/dev/md6: clean, 53/1221600 files, 76570/2441824 blocks
-/dev/md7: clean, 1179413/7323648 files, 5757529/14647200 blocks
-/dev/md4: clean, 7509/732960 files, 268934/1465856 blocks (check in 3 mounts)
-/dev/mapper/encrypted: clean, 14607/12222464 files, 13969744/24414646 blocks
-done.
-Setting kernel variables...done.
-Mounting local filesystems...kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md0, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md5, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on sdd2, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on sdd3, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md8, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md3, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md6, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md7, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on md4, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-kjournald starting.  Commit interval 5 seconds
-EXT3 FS on dm-1, internal journal
-EXT3-fs: mounted filesystem with ordered data mode.
-done.
-Activating swapfile swap...Adding 15631096k swap on /dev/mapper/cswap.  Priority:1 extents:1 across:15631096k
-done.
-Detecting hardware...Setting up networking....
-Configuring network interfaces...done.
-Starting portmap daemon....
-sky2 eth1: enabling interface
-sky2 eth1: ram buffer 0K
-NET: Registered protocol family 10
-lo: Disabled Privacy Extensions
-ADDRCONF(NETDEV_UP): eth1: link is not ready
-Setting sensors limits: done.
-Setting console screen modes and fonts.
-Setting up ALSA...done.
-Recovering schroot sessions: sid32-df306a93-1d63-494d-a726-c924190900c6.
-INIT: Entering runlevel: 2
-Starting system log daemon....
-Starting kernel log daemon....
-Starting portmap daemon...Already running..
-Starting HP Linux Printing and Imaging System: hpiod hpssdsky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both
-ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
-.
-Loading ACPI modules...input: Power Button (FF) as /class/input/input4
-ACPI: Power Button (FF) [PWRF]
-input: Power Button (CM) as /class/input/input5
-ACPI: Power Button (CM) [PWRB]
-.
-Starting Advanced Configuration and Power Interface daemon....
-Starting BitTorrent tracker: disabled in /etc/default/bittorrent.
-Starting Common Unix Printing System: cupsdlp: driver loaded but no devices found
-ppdev: user-space parallel port driver
-.
-Starting system message bus: dbus.
-Starting network connection manager: NetworkManager.
-Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
-Starting network events dispatcher: NetworkManagerDispatcher.
-Starting MTA: exim4.
-Starting mouse interface server: gpm.
-Starting disk temperature monitoring daemon: hddtemp:  /dev/sda /dev/sdb /dev/sdc /dev/sdd..
-Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
-Exporting directories for NFS kernel daemon....
-Starting NFS kernel daemon: nfsdNFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
-NFSD: starting 90-second grace period
- mountd.
-Starting internet superserver: inetd.
-Starting OpenBSD Secure Shell server: sshd.
-Starting GNOME Display Manager: gdm.
-Starting NFS common utilities: statd idmapd.
-Starting DHCP D-Bus daemon: dhcdbd.
-Starting Hardware abstraction layer: hald.
-Starting MD monitoring service: mdadm --monitor.
-Starting anac(h)ronistic cron: anacron.
-Starting periodic command scheduler: crond.
-
-Debian GNU/Linux lenny/sid hikaru ttyS0
-
-hikaru login: 
+Waiting for /dev to be fully populated...agpgart: Detected an Intel 965G Chipset.



As you can see, lots and lots of things are being done between

Linux agpgart interface v0.102 (c) Dave Jones

and

agpgart: Detected an Intel 965G Chipset.

-- 
Carlo Wood <carlo@alinoe.com>

Re: [AGPGART] intel_agp: use table for device probe

[Carlo Wood]

On Mon, Jun 18, 2007 at 10:37:26AM +0800, Wang Zhenyu wrote:
> Carlo, I've just built latest kernel git tree on a Dell 965G box and
> have a NV card plugged-in. It boots fine.

It would be nice if you could test it with the exact same
hardware ... I am pretty sure it should be reproducable then *cough*

> Linux agpgart interface v0.102 (c) Dave Jones
> agpgart: Detected an Intel 965G Chipset.
> agpgart: AGP aperture is 256M @ 0x0
> 
> I don't know why it hangs your machine when loading this module, it should
> just not bother anything. But from your last "modprobe: ..." line, it seems
> there's really badness somewhere, do you have serial console to see more
> in the message?

The reason I react a bit late to your post is because in the meantime
I set up a serial console and figured out how to boot that way... and
captured the boot messages.

I will add that to one of the other posts, because as a result of
what they posted there I added agp=off - and that (indeed) makes it
possible for me to boot. Please see my next post thus.

-- 
Carlo Wood <carlo@alinoe.com>