I cheered too soon ... I just tested 2.6.22-rc5 and it hangs
again at the same point, right after printing:
agpgart: Detected an Intel 965G Chipset.
So far I tested:
188e1f81ba31af1b65a2f3611df4c670b092bbac BAD 2007-06-17 04:09:12 v2.6.22-rc5
99f9f3d49cbc7d944476f6fde53a77ec789ab2aa GOOD 2007-06-12 00:46:08 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
3334500b460a5eede2e3466ca97a90fe3b91ceb5 GOOD 2007-06-11 20:39:05 Merge master.kernel.org:/pub/scm/linux/kernel/git/davej/agpgart
df80b148869291621ddf51eb8716658d5bfba811 GOOD 2007-05-31 05:51:21 [AGPGART] intel_agp: add support for 945GME
9614ece14f23f2ce54a076c471aec9c91e51e79c GOOD 2007-05-30 03:45:58 [AGPGART] intel_agp: use table for device probe
c4ca881796b7e14120851ddf6e04845ef94a314a BAD 2007-05-30 03:40:46 [AGPGART] intel_agp: cleanup intel private data
e141d999b682cda9907179e3b843acb64c34a1d8 BAD 2007-06-10 07:26:20
b44c0267b7571b449e05f390349c4e4d080f0f4c BAD 2007-06-11 20:32:28 Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb
bb3d2dd72302ea3eefcc6738cdd39ed5864b62f8 BAD 2007-06-11 20:31:43 Merge master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6
1a539a87280b3032fd12bc93a4a82f1d8aa97ca8 BAD 2007-06-08 22:46:58
5ecd3100e695228ac5e0ce0e325e252c0f11806f BAD 2007-06-05 02:57:25 v2.6.22-rc4
c420bc9f09a0926b708c3edb27eacba434a4f4ba BAD 2007-05-26 04:55:14 v2.6.22-rc3
55b637c6a003a8c4850b41a2c2fd6942d8a7f530 BAD 2007-05-19 06:06:17 v2.6.22-rc2
... ...
BAD v2.6.19-rc1
GOOD v2.6.18
I am now doing a bisect between 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
and 188e1f81ba31af1b65a2f3611df4c670b092bbac.
The hardware that I'm using is:
An ASUS P5B Deluxe motherboard with an Intel Core 2 Quad QX6700 2.66 GHz,
4 GB of low latency DIMMs (two times KHX6400D2LLK2/2GN - two DIMM's each, 4 DIMM's
in total, which are CL4-4-4). Asus EN8600 GTS 256MB.
--
Carlo Wood <[email protected]>
On Sun, Jun 17, 2007 at 03:07:14PM -0400, Dave Jones wrote:
> Out of curiousity, I'd like to see your lspci
> (not -v or anything, just run with no args)
$ lspci
00:00.0 Host bridge: Intel Corporation P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0400 (rev a1)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 12)
04:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
04:02.1 Input device controller: Creative Labs SB Live! Game Port (rev 08)
04:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
--
Carlo Wood <[email protected]>
Because I CC new people, let me summarize:
2.6.18 works fine. Most kernels after that print
"agpgart: Detected an Intel 965G Chipset."
and then either hang (I have to hard reset them), hard
reset by themselves or print one or two more lines mostly
related to hardcrashes (memory page faults or otherwise)
and hang then. This can vary from boot to boot even
with the same kernel.
Some kernels don't hang. They never hang - they always work.
Kernels that work do NOT print "agpgart: Detected an Intel
965G Chipset." (All I know is that I have an ASUS P5B motherboard
with a iP965, whether it's this 'G' or not I don't know).
This is the regression that 'git bisect' comes with:
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
d09c6b809432668371b5de9102f4f9aa6a7c79cc is first bad commit
commit d09c6b809432668371b5de9102f4f9aa6a7c79cc
Author: Paul Mundt <[email protected]>
Date: Thu Jun 14 15:13:16 2007 +0900
mm: Fix memory/cpu hotplug section mismatch and oops.
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the following section mismatch:
WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
.init.text: (between 'free_area_init_node' and '__build_all_zonelists')
This happens as a result of:
-> free_area_init_node()
-> free_area_init_core()
-> zone_pcp_init() <-- all __meminit up to this point
-> zone_batchsize() <-- marked as __cpuinit fo
This happens because CONFIG_HOTPLUG_CPU=n sets __cpuinit to __init, but
CONFIG_MEMORY_HOTPLUG=y unsets __meminit.
Changing zone_batchsize() to __devinit fixes this.
__devinit is the only thing that is common between CONFIG_HOTPLUG_CPU=y and
CONFIG_MEMORY_HOTPLUG=y. In the long run, perhaps this should be moved to
another section identifier completely. Without this, memory hot-add
of offline nodes (via hotadd_new_pgdat()) will oops if CPU hotplug is
not also enabled.
Signed-off-by: Paul Mundt <[email protected]>
Acked-by: Yasunori Goto <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
--
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
:040000 040000 230b105fa4d9eb2ed873cca8e9ec1b5502ffce79 37636618f4eb88827ec1e524ebb3ac37e44e90f1 M mm
==================
If you want my opinion on this: git bisect is broken :p
I was very surprised that it printed this at this point.
One bisect before, it said there were still 96 revision to check.
Anyway - here are some facts of the kernels that I tested:
188e1f81ba31af1b65a2f3611df4c670b092bbac BAD 2007-06-17 04:09:12 v2.6.22-rc5
3e903e7b1605aff88d7f89a96fab5e43081b914f BAD 2007-06-16 19:16:01
de7f928ca460005086a8296be07c217aac4b625d BAD 2007-06-16 02:34:34 Merge master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6
d1be0a8225f2cb1cdc356ebb0ae6800f023ce67d BAD 2007-06-16 02:24:44
ce9b2b0abbf019d5259eb089a1cc256852930f67 BAD 2007-06-16 02:24:43
d09c6b809432668371b5de9102f4f9aa6a7c79cc BAD 2007-06-14 08:13:16 mm: Fix memory/cpu hotplug section mismatch and oops.
cf68676222e54cd0a31efd968da00e65f9a0963f GOOD 2007-06-11 10:12:49
99f9f3d49cbc7d944476f6fde53a77ec789ab2aa GOOD 2007-06-12 00:46:08 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
3334500b460a5eede2e3466ca97a90fe3b91ceb5 GOOD 2007-06-11 20:39:05 Merge master.kernel.org:/pub/scm/linux/kernel/git/davej/agpgart
df80b148869291621ddf51eb8716658d5bfba811 GOOD 2007-05-31 05:51:21 [AGPGART] intel_agp: add support for 945GME
9614ece14f23f2ce54a076c471aec9c91e51e79c GOOD 2007-05-30 03:45:58 [AGPGART] intel_agp: use table for device probe
c4ca881796b7e14120851ddf6e04845ef94a314a BAD 2007-05-30 03:40:46 [AGPGART] intel_agp: cleanup intel private data
e141d999b682cda9907179e3b843acb64c34a1d8 BAD 2007-06-10 07:26:20
b44c0267b7571b449e05f390349c4e4d080f0f4c BAD 2007-06-11 20:32:28 Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb
bb3d2dd72302ea3eefcc6738cdd39ed5864b62f8 BAD 2007-06-11 20:31:43 Merge master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6
1a539a87280b3032fd12bc93a4a82f1d8aa97ca8 BAD 2007-06-08 22:46:58
5ecd3100e695228ac5e0ce0e325e252c0f11806f BAD 2007-06-05 02:57:25 v2.6.22-rc4
c420bc9f09a0926b708c3edb27eacba434a4f4ba BAD 2007-05-26 04:55:14 v2.6.22-rc3
55b637c6a003a8c4850b41a2c2fd6942d8a7f530 BAD 2007-05-19 06:06:17 v2.6.22-rc2
... ...
BAD v2.6.19-rc1
GOOD v2.6.18
The order and date is the order and date as is shown by gitk --all.
I'd appreciate any suggestions or questions at this point, as I have no
idea what to do next to find this problem.
--
Carlo Wood <[email protected]>
PS The hardware that I'm using is:
An ASUS P5B Deluxe motherboard with an Intel Core 2 Quad QX6700 2.66 GHz,
4 GB of low latency DIMMs (two times KHX6400D2LLK2/2GN - two DIMM's each, 4 DIMM's
in total, which are CL4-4-4). Asus EN8600 GTS 256MB.
On Sun, Jun 17, 2007 at 11:49:05PM +0200, Carlo Wood wrote:
> Kernels that work do NOT print "agpgart: Detected an Intel
> 965G Chipset." (All I know is that I have an ASUS P5B motherboard
> with a iP965, whether it's this 'G' or not I don't know).
>
The obvious question of course is whether actually reverting this
changeset fixes your problem? I would be very surprised if it did.
If it does make a difference, please provide the values for
CONFIG_HOTPLUG, CONFIG_MEMORY_HOTPLUG and CONFIG_HOTPLUG_CPU from your
.config.
I would wager that you only have CONFIG_HOTPLUG=y, in which case, the
only difference over previous kernels will be that zone_batchlist() is no
longer flagged as __init, and so it won't be freed -- this was the reason
for the "special section" comment in the changeset, as currently it's
left hanging around for folks that aren't doing cpu/memory hotplug, since
__devinit was the closest that both cpu and memory hotplug had in common.
I can't imagine that this would impact you at all, though.
On Mon, Jun 18, 2007 at 08:18:58AM +0900, Paul Mundt wrote:
> The obvious question of course is whether actually reverting this
> changeset fixes your problem? I would be very surprised if it did.
Having a git commit Id, like d09c6b809432668371b5de9102f4f9aa6a7c79cc,
how can I create a .diff file from that?
> If it does make a difference, please provide the values for
> CONFIG_HOTPLUG, CONFIG_MEMORY_HOTPLUG and CONFIG_HOTPLUG_CPU from your
> .config.
>
> I would wager that you only have CONFIG_HOTPLUG=y, in which case, the
> only difference over previous kernels will be that zone_batchlist() is no
> longer flagged as __init, and so it won't be freed -- this was the reason
> for the "special section" comment in the changeset, as currently it's
> left hanging around for folks that aren't doing cpu/memory hotplug, since
> __devinit was the closest that both cpu and memory hotplug had in common.
>
> I can't imagine that this would impact you at all, though.
I think git bisect made an error... as you can see for yourself
with the list of tested git Id's that I gave - it didn't test
both sides of that patch imho. If you tell me how to extract a patch
then I'll manually unapply it to some failing kernel revisions and
see if that makes a difference.
--
Carlo Wood <[email protected]>
On Mon, Jun 18, 2007 at 02:10:49AM +0200, Carlo Wood wrote:
> On Mon, Jun 18, 2007 at 08:18:58AM +0900, Paul Mundt wrote:
> > The obvious question of course is whether actually reverting this
> > changeset fixes your problem? I would be very surprised if it did.
>
> Having a git commit Id, like d09c6b809432668371b5de9102f4f9aa6a7c79cc,
> how can I create a .diff file from that?
>
$ git show d09c6b809432668371b5de9102f4f9aa6a7c79cc | patch -p1 -R
... build and test ...
$ git show d09c6b809432668371b5de9102f4f9aa6a7c79cc | patch -p1
... back to original (or git checkout-index -f mm/page_alloc.c) ...
if you just want to test that single change.
> I think git bisect made an error... as you can see for yourself
> with the list of tested git Id's that I gave - it didn't test
> both sides of that patch imho. If you tell me how to extract a patch
> then I'll manually unapply it to some failing kernel revisions and
> see if that makes a difference.
>
Assuming that reverting that patch makes no difference, can you provide
the output of 'git bisect log'?
On Mon, 18 Jun 2007 09:25:48 +0900
Paul Mundt <[email protected]> wrote:
> $ git show d09c6b809432668371b5de9102f4f9aa6a7c79cc | patch -p1 -R
> ... build and test ...
> $ git show d09c6b809432668371b5de9102f4f9aa6a7c79cc | patch -p1
> ... back to original (or git checkout-index -f mm/page_alloc.c) ...
Please forgive my git fanboyism, but assuming you have no
uncommitted changes in your working tree, you could also:
$ git revert -n d09c6b809432
... build and test ...
$ git reset --hard
... back to original ...
cheers,
Sean
On Sun, 17 Jun 2007, Carlo Wood wrote:
>
> If you want my opinion on this: git bisect is broken :p
> I was very surprised that it printed this at this point.
Hmm. Possible. However, I *really* would need the git bisect log to see
what's up. So far, we have never seen a bug in "git bisect" that wasn't
either due to the user specifying path-names to limit the testing (and the
bug not being in that set of path-names), or the user not realizing that
with non-linear history the "git bisect" is actually a fairly complex op.
That said, "git bisect" _can_ give the "wrong" results in the sense that
the commit it points to may not be the one you are actually looking for,
if:
- the bug is sporadic, and not entirely repeatable, and a kernel you
marked as good wasn't really good, your test just didn't happen to
catch it that time around.
- the bug comes and goes, and the commit that "git bisect" pinpoints may
well *show* the bug, but may not be the *cause* of the bug (ie there
might be two or more independent things that have to come together for
the bug to trigger, and as a result there is not a "single" commit that
acts as a clear boundary)
But hey, a bug in "git bisect" is certainly _possible_. I just consider it
fairly unlikely by now.
> One bisect before, it said there were still 96 revision to check.
>
> Anyway - here are some facts of the kernels that I tested:
You seem to not actually have used "git bisect" to generate this list.
Quite frankly, the most likely cause for the bad bisection result is that
you have not used "git bisect" at all to let it pick the bisection points.
That really doesn't work. If you start giving "git bisect" points to test
that aren't "within" the space of points you had already told git bisect
about, you're no longer bisecting, you're giving it random points.
> I'd appreciate any suggestions or questions at this point, as I have no
> idea what to do next to find this problem.
If you do a real "git bisect", and don't just give it random points that
you want to check (you obviously _do_ need to give it one "good" and one
"bad" initially, but after that you *have* to pick a point that is within
the query space), you'll not get any sensible values out of git bisect.
"git bisect" will also give you a log in ".git/BISECT_LOG", which others
can use to follow your bisection. That might be useful to see.
Linus
On Mon, Jun 18, 2007 at 10:01:34AM -0700, Linus Torvalds wrote:
> On Sun, 17 Jun 2007, Carlo Wood wrote:
> >
> > If you want my opinion on this: git bisect is broken :p
> > I was very surprised that it printed this at this point.
>
> Hmm. Possible. However, I *really* would need the git bisect log to see
> what's up.
I had already done a git bisect reset :/
> So far, we have never seen a bug in "git bisect" that wasn't
> either due to the user specifying path-names to limit the testing (and the
> bug not being in that set of path-names), or the user not realizing that
> with non-linear history the "git bisect" is actually a fairly complex op.
I realize that it is non-linear - and I didn't do anything to "speed
things up". Just build -> boot -> git bisect good/bad -> build etc.
> That said, "git bisect" _can_ give the "wrong" results in the sense that
> the commit it points to may not be the one you are actually looking for,
> if:
>
> - the bug is sporadic, and not entirely repeatable, and a kernel you
> marked as good wasn't really good, your test just didn't happen to
> catch it that time around.
>
> - the bug comes and goes, and the commit that "git bisect" pinpoints may
> well *show* the bug, but may not be the *cause* of the bug (ie there
> might be two or more independent things that have to come together for
> the bug to trigger, and as a result there is not a "single" commit that
> acts as a clear boundary)
I don't believe that either of these is the case. I have booted
about 8 different kernel revisions several times (most three times),
alternating between them (not the same three times on a row) and the
ones that boot correctly always booted correctly, while the ones that
hung, always hung (although in a totally reproducable way).
Nevertheless, it is not 100% impossible. I have the feeling that it
MIGHT be related to the fact that I have 4 CPU's - and that perhaps some
race condition is involved. And if that is the case, then there might be
some kernel version where boot/not-boot is less reliable then with the
eight I tested - apart from that three times isn't very much (but doing
it for four good kernels and two bad kernels, it still is a reasonable
indication for reproducability).
> But hey, a bug in "git bisect" is certainly _possible_. I just consider it
> fairly unlikely by now.
> > One bisect before, it said there were still 96 revision to check.
> >
> > Anyway - here are some facts of the kernels that I tested:
>
> You seem to not actually have used "git bisect" to generate this list.
I didn't -- what is the command to generate a list like this with git?
> Quite frankly, the most likely cause for the bad bisection result is that
> you have not used "git bisect" at all to let it pick the bisection points.
Heh - now you are insulting me :p I said I did, and I did.
The reason that I made that list manually is because wanted to have more
overview. I use this alias to build the kernels:
hikaru:/usr/src/kernel/git/linux-2.6>alias build
alias build='cp /boot/config-2.6.22-rc4-hikaru-amd64 .config &&
make-kpkg clean && VER=$(date +"%Y%m%d%H%M") && BRANCH=$(git branch |
grep "^\*" | sed -e "s/\* //") && NAMEEXT="-$BRANCH-$(git rev-list
--max-count=1 $BRANCH)-$(dpkg-architecture -qDEB_HOST_ARCH)" &&
make-kpkg --revision=$VER --append-to-version=-$NAMEEXT --rootcmd
fakeroot clean && make-kpkg --revision=$VER --append-to-version=$NAMEEXT
--rootcmd fakeroot --initrd kernel_image modules_image'
That results in debian kernel package names like:
-rw-r--r-- 1 carlo carlo 18790180 2007-06-17 22:55 linux-image-2.6.22-rc4-bisect-d09c6b809432668371b5de9102f4f9aa6a7c79cc-amd64_200706172247_amd64.deb
-rw-r--r-- 1 carlo carlo 18790446 2007-06-17 22:42 linux-image-2.6.22-rc4-bisect-ce9b2b0abbf019d5259eb089a1cc256852930f67-amd64_200706172234_amd64.deb
-rw-r--r-- 1 carlo carlo 18789884 2007-06-17 22:24 linux-image-2.6.22-rc4-bisect-d1be0a8225f2cb1cdc356ebb0ae6800f023ce67d-amd64_200706172216_amd64.deb
-rw-r--r-- 1 carlo carlo 18790420 2007-06-17 22:09 linux-image-2.6.22-rc4-bisect-de7f928ca460005086a8296be07c217aac4b625d-amd64_200706172201_amd64.deb
-rw-r--r-- 1 carlo carlo 18790430 2007-06-17 21:04 linux-image-2.6.22-rc4-bisect-3e903e7b1605aff88d7f89a96fab5e43081b914f-amd64_200706172032_amd64.deb
-rw-r--r-- 1 carlo carlo 18789698 2007-06-17 20:21 linux-image-2.6.22-rc4-bisect-cf68676222e54cd0a31efd968da00e65f9a0963f-amd64_200706172012_amd64.deb
-rw-r--r-- 1 carlo carlo 18789796 2007-06-17 18:51 linux-image-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64_200706171843_amd64.deb
-rw-r--r-- 1 carlo carlo 18814550 2007-06-17 17:53 linux-image-2.6.22-rc1-bisect-c4ca881796b7e14120851ddf6e04845ef94a314a-amd64_200706171745_amd64.deb
-rw-r--r-- 1 carlo carlo 18814168 2007-06-17 17:14 linux-image-2.6.22-rc1-bisect-9614ece14f23f2ce54a076c471aec9c91e51e79c-amd64_200706171646_amd64.deb
-rw-r--r-- 1 carlo carlo 18815254 2007-06-17 07:25 linux-image-2.6.22-rc1-bisect-df80b148869291621ddf51eb8716658d5bfba811-amd64_200706170717_amd64.deb
-rw-r--r-- 1 carlo carlo 18826878 2007-06-17 06:36 linux-image-2.6.22-rc4-bisect-b44c0267b7571b449e05f390349c4e4d080f0f4c-amd64_200706170628_amd64.deb
-rw-r--r-- 1 carlo carlo 18826402 2007-06-17 04:20 linux-image-2.6.22-rc4-bisect-e141d999b682cda9907179e3b843acb64c34a1d8-amd64_200706170412_amd64.deb
-rw-r--r-- 1 carlo carlo 18830334 2007-06-17 03:30 linux-image-2.6.22-rc4-bisect-3334500b460a5eede2e3466ca97a90fe3b91ceb5-amd64_200706170323_amd64.deb
-rw-r--r-- 1 carlo carlo 18827134 2007-06-17 02:50 linux-image-2.6.22-rc4-bisect-bb3d2dd72302ea3eefcc6738cdd39ed5864b62f8-amd64_200706170243_amd64.deb
-rw-r--r-- 1 carlo carlo 18824900 2007-06-17 02:37 linux-image-2.6.22-rc4-bisect-1a539a87280b3032fd12bc93a4a82f1d8aa97ca8-amd64_200706170230_amd64.deb
-rw-r--r-- 1 carlo carlo 18829904 2007-06-16 16:24 linux-image-2.6.22-rc4-master-99f9f3d49cbc7d944476f6fde53a77ec789ab2aa-amd64_200706161616_amd64.deb
-rw-r--r-- 1 carlo carlo 18818812 2007-06-16 05:59 linux-image-2.6.22-rc4-master-5ecd3100e695228ac5e0ce0e325e252c0f11806f-amd64_200706160551_amd64.deb
-rw-r--r-- 1 carlo carlo 18818284 2007-06-15 21:39 linux-image-2.6.22-rc3-bisect-c420bc9f09a0926b708c3edb27eacba434a4f4ba-amd64_200706152131_amd64.deb
-rw-r--r-- 1 carlo carlo 18823918 2007-06-15 21:26 linux-image-2.6.22-rc4-bisect-5ecd3100e695228ac5e0ce0e325e252c0f11806f-amd64_200706152119_amd64.deb
-rw-r--r-- 1 carlo carlo 18817072 2007-06-15 18:13 linux-image-2.6.22-rc3-bisect-0e9871df2389560e94ba01e40959140ee56def4b-amd64_200706151805_amd64.deb
-rw-r--r-- 1 carlo carlo 18815324 2007-06-15 17:41 linux-image-2.6.22-rc2-bisect-55b637c6a003a8c4850b41a2c2fd6942d8a7f530-amd64_200706151733_amd64.deb
or after installation:
||/ Name Version Description
ii linux-image-2.6.22-rc4-bisect-3e903e7b1605aff88d7f89a96fab5e43081b914f-amd64 200706172032 Linux kernel binary image for version 2.6.22
and kernel versions like 2.6.22-rc4-bisect-3e903e7b1605aff88d7f89a96fab5e43081b914f-amd64 etc.
Heh - hopefully you have 20" monitors like met :p
However - it didn't give me an overview of the git bisect good/bad
process. Therefore I used 'gitk -all' and it's search function to
find all the kernels that I tested and put them in a file, such
creating that list I posted here. If there is a way to generate
this list with a command, please tell me :)
> That really doesn't work. If you start giving "git bisect" points to test
> that aren't "within" the space of points you had already told git bisect
> about, you're no longer bisecting, you're giving it random points.
Some online documention said you can use git reset --hard gitId to
choose a different point nearby what git bisect 'suggests' to test next.
I didn't do that in this case however.
> > I'd appreciate any suggestions or questions at this point, as I have no
> > idea what to do next to find this problem.
>
> If you do a real "git bisect", and don't just give it random points that
> you want to check (you obviously _do_ need to give it one "good" and one
> "bad" initially, but after that you *have* to pick a point that is within
> the query space), you'll not get any sensible values out of git bisect.
I suppose you mean: ... then you WILL get sensible values out of git
bisect. But, since I already did a real "git bisect" without giving it
random points, I am afraid you jumped conclusions.
> "git bisect" will also give you a log in ".git/BISECT_LOG", which others
> can use to follow your bisection. That might be useful to see.
No such file exists (anymore).
However, I can easily reproduce it. From my history file I can see that I started with:
git bisect start
git bisect bad v2.6.22-rc5
git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
I wrote everything down on paper (the git id's and whether they
were good or bad), so I can reproduce it with:
hikaru:/usr/src/kernel/git/linux-2.6>git bisect start
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad v2.6.22-rc5
hikaru:/usr/src/kernel/git/linux-2.6>git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
Bisecting: 128 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
hikaru:/usr/src/kernel/git/linux-2.6>git bisect good
Bisecting: 111 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[3e903e7b1605aff88d7f89a96fab5e43081b914f] cpuset: zero malloc - fix for old cpusets
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
Bisecting: 103 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[de7f928ca460005086a8296be07c217aac4b625d] Merge master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
Bisecting: 98 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[d1be0a8225f2cb1cdc356ebb0ae6800f023ce67d] ide-scsi: fix OOPS in idescsi_expiry()
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
Bisecting: 97 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[ce9b2b0abbf019d5259eb089a1cc256852930f67] Resume from RAM on HPC nx6325 broken
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
Bisecting: 96 revisions left to test after this
D include/asm-blackfin/macros.h
M scripts/package/Makefile
D scripts/package/builddeb
[d09c6b809432668371b5de9102f4f9aa6a7c79cc] mm: Fix memory/cpu hotplug section mismatch and oops.
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
d09c6b809432668371b5de9102f4f9aa6a7c79cc is first bad commit
commit d09c6b809432668371b5de9102f4f9aa6a7c79cc
Author: Paul Mundt <[email protected]>
Date: Thu Jun 14 15:13:16 2007 +0900
mm: Fix memory/cpu hotplug section mismatch and oops.
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the following section mismatch:
WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
.init.text: (between 'free_area_init_node' and '__build_all_zonelists')
This happens as a result of:
-> free_area_init_node()
-> free_area_init_core()
-> zone_pcp_init() <-- all __meminit up to this point
-> zone_batchsize() <-- marked as __cpuinit fo
This happens because CONFIG_HOTPLUG_CPU=n sets __cpuinit to __init, but
CONFIG_MEMORY_HOTPLUG=y unsets __meminit.
Changing zone_batchsize() to __devinit fixes this.
__devinit is the only thing that is common between CONFIG_HOTPLUG_CPU=y and
CONFIG_MEMORY_HOTPLUG=y. In the long run, perhaps this should be moved to
another section identifier completely. Without this, memory hot-add
of offline nodes (via hotadd_new_pgdat()) will oops if CPU hotplug is
not also enabled.
Signed-off-by: Paul Mundt <[email protected]>
Acked-by: Yasunori Goto <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
--
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
:040000 040000 230b105fa4d9eb2ed873cca8e9ec1b5502ffce79 37636618f4eb88827ec1e524ebb3ac37e44e90f1 M mm
and (useless, on top of the above, now I see it):
hikaru:/usr/src/kernel/git/linux-2.6>git bisect log
git-bisect start
# bad: [aec07c7abc280bd5d0ca33b7cda3eb7b9b6e89c1] Linux 2.6.22-rc5
git-bisect bad aec07c7abc280bd5d0ca33b7cda3eb7b9b6e89c1
# good: [99f9f3d49cbc7d944476f6fde53a77ec789ab2aa] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
git-bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
# good: [cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
git-bisect good cf68676222e54cd0a31efd968da00e65f9a0963f
# bad: [3e903e7b1605aff88d7f89a96fab5e43081b914f] cpuset: zero malloc - fix for old cpusets
git-bisect bad 3e903e7b1605aff88d7f89a96fab5e43081b914f
# bad: [de7f928ca460005086a8296be07c217aac4b625d] Merge master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6
git-bisect bad de7f928ca460005086a8296be07c217aac4b625d
# bad: [d1be0a8225f2cb1cdc356ebb0ae6800f023ce67d] ide-scsi: fix OOPS in idescsi_expiry()
git-bisect bad d1be0a8225f2cb1cdc356ebb0ae6800f023ce67d
# bad: [ce9b2b0abbf019d5259eb089a1cc256852930f67] Resume from RAM on HPC nx6325 broken
git-bisect bad ce9b2b0abbf019d5259eb089a1cc256852930f67
# bad: [d09c6b809432668371b5de9102f4f9aa6a7c79cc] mm: Fix memory/cpu hotplug section mismatch and oops.
git-bisect bad d09c6b809432668371b5de9102f4f9aa6a7c79cc
--
Carlo Wood <[email protected]>
On Mon, Jun 18, 2007 at 08:12:25PM +0200, Carlo Wood wrote:
> ones that boot correctly always booted correctly, while the ones that
> hung, always hung (although in a totally reproducable way).
Sorry - that should be "although NOT in a totally reproducable way"
If you every doubt it's the Real Carlo Wood, look for him
leaving out the word 'not' 50% of the time ;)
--
Carlo Wood <[email protected]>
On Mon, 18 Jun 2007, Carlo Wood wrote:
>
> I suppose you mean: ... then you WILL get sensible values out of git
> bisect. But, since I already did a real "git bisect" without giving it
> random points, I am afraid you jumped conclusions.
Hey, fair enough.
That said, your "git bisect" really *does* act oddly.
> However, I can easily reproduce it. From my history file I can see that I started with:
>
> git bisect start
> git bisect bad v2.6.22-rc5
> git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
Goodie.
> I wrote everything down on paper (the git id's and whether they
> were good or bad), so I can reproduce it with:
I can follow along, but I get *totally*different* git bisection points!
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect start
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad v2.6.22-rc5
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
> Bisecting: 128 revisions left to test after this
> D include/asm-blackfin/macros.h
> M scripts/package/Makefile
> D scripts/package/builddeb
You seem to have a modified tree! What are those modifications to the
blackfin macros.h etc files?
You *should* have gotten this:
[torvalds@woody linux]$ git bisect start
[torvalds@woody linux]$ git bisect bad v2.6.22-rc5
[torvalds@woody linux]$ git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
Bisecting: 127 revisions left to test after this
[9808901b6c63a1c850b072e624c228901a9eaf10] Blackfin serial driver: ignore framing and parity errors
but those are just off by one, at least (127 vs 128 commits left).
> [cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good
> Bisecting: 111 revisions left to test after this
And that's totally broken. Even if I don't use the "9808901b6" commit, and
use your "cf686762" commit, I get:
[torvalds@woody linux]$ git bisect good cf68676222e54cd0a31efd968da00e65f9a0963f
Bisecting: 63 revisions left to test after this
[aba297927d1d558c7a94548135133bdf9172708a] Merge master.kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6
Notice? The "127 revisions left to test after this" has become "63
revisions left to test after this".
That number should be cut in half each time. And you shouldn't get some
strange dirty tree indications.
It might be worth it just making sure your git is ok. It really is acting
oddly. What version is it?
Linus
On Mon, Jun 18, 2007 at 11:35:03AM -0700, Linus Torvalds wrote:
> I can follow along, but I get *totally*different* git bisection points!
>
> > hikaru:/usr/src/kernel/git/linux-2.6>git bisect start
> > hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad v2.6.22-rc5
> > hikaru:/usr/src/kernel/git/linux-2.6>git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
> > Bisecting: 128 revisions left to test after this
> > D include/asm-blackfin/macros.h
> > M scripts/package/Makefile
> > D scripts/package/builddeb
>
> You seem to have a modified tree! What are those modifications to the
> blackfin macros.h etc files?
I never (manually) changed anything - so, this should be the result
of the fact that I use the same directory tree to (re)build the kernel
every time.
That 'D' means they are deleted I'd think - so the changes are clear.
I am sorry, but I am totally new to git - I know cvs and svn (and even
then I never used branches :(), but I don't know how to find out what
those differences are with git.
I could start looking on the web - but it's a fact that I don't even
know what I would look for: in order to create a diff one needs two
points. No doubt one point is the current state of my local copy,
but what would that other point be to compare with?
If you would be so kind to ask things like: What is the result of
this or that command, when it comes to git, then I will be faster
and more accurate to tell you :). I added the result of 'git diff'
below.
> You *should* have gotten this:
>
> [torvalds@woody linux]$ git bisect start
> [torvalds@woody linux]$ git bisect bad v2.6.22-rc5
> [torvalds@woody linux]$ git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
> Bisecting: 127 revisions left to test after this
> [9808901b6c63a1c850b072e624c228901a9eaf10] Blackfin serial driver: ignore framing and parity errors
>
> but those are just off by one, at least (127 vs 128 commits left).
>
> > [cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
> > hikaru:/usr/src/kernel/git/linux-2.6>git bisect good
> > Bisecting: 111 revisions left to test after this
>
> And that's totally broken. Even if I don't use the "9808901b6" commit, and
> use your "cf686762" commit, I get:
>
> [torvalds@woody linux]$ git bisect good cf68676222e54cd0a31efd968da00e65f9a0963f
> Bisecting: 63 revisions left to test after this
> [aba297927d1d558c7a94548135133bdf9172708a] Merge master.kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6
>
> Notice? The "127 revisions left to test after this" has become "63
> revisions left to test after this".
Well,... when, and because, it's not a linear thing as you mentioned
before - it's not necessarily precisely a cut into half... so I thought,
seeing those weird (not half) numbers that that was the cause.
> That number should be cut in half each time. And you shouldn't get some
> strange dirty tree indications.
>
> It might be worth it just making sure your git is ok. It really is acting
> oddly. What version is it?
git version 1.4.4.4
I am using Debian (suite 'testing') and trying to be a debian purist -
so it isn't like I can easily upgrade to 1.5.x : there is no debian
package for that version in 'testing'.
Nevertheless, if you think it's important - then I can download and
compile a tar ball of course - certainly when I don't have to install
it to test it.
--
Carlo Wood <[email protected]>
PS The result of 'git diff' is:
diff --git a/include/asm-blackfin/macros.h b/include/asm-blackfin/macros.h
deleted file mode 100644
index e69de29..0000000
diff --git a/scripts/package/Makefile b/scripts/package/Makefile
index 7c434e0..f758b75 100644
--- a/scripts/package/Makefile
+++ b/scripts/package/Makefile
@@ -1,99 +1,2 @@
-# Makefile for the different targets used to generate full packages of a kernel
-# It uses the generic clean infrastructure of kbuild
-
-# Ignore the following files/directories during tar operation
-TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn --exclude CVS
-
-
-# RPM target
-# ---------------------------------------------------------------------------
-# The rpm target generates two rpm files:
-# /usr/src/packages/SRPMS/kernel-2.6.7rc2-1.src.rpm
-# /usr/src/packages/RPMS/i386/kernel-2.6.7rc2-1.<arch>.rpm
-# The src.rpm files includes all source for the kernel being built
-# The <arch>.rpm includes kernel configuration, modules etc.
-#
-# Process to create the rpm files
-# a) clean the kernel
-# b) Generate .spec file
-# c) Build a tar ball, using symlink to make kernel version
-# first entry in the path
-# d) and pack the result to a tar.gz file
-# e) generate the rpm files, based on kernel.spec
-# - Use /. to avoid tar packing just the symlink
-
-# Do we have rpmbuild, otherwise fall back to the older rpm
-RPM := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \
- else echo rpm; fi)
-
-# Remove hyphens since they have special meaning in RPM filenames
-KERNELPATH := kernel-$(subst -,,$(KERNELRELEASE))
-MKSPEC := $(srctree)/scripts/package/mkspec
-PREV := set -e; cd ..;
-
-# rpm-pkg
-# ---------------------------------------------------------------------------
-$(objtree)/kernel.spec: $(MKSPEC) $(srctree)/Makefile
- $(CONFIG_SHELL) $(MKSPEC) > $@
-
-rpm-pkg rpm: $(objtree)/kernel.spec FORCE
- $(MAKE) clean
- $(PREV) ln -sf $(srctree) $(KERNELPATH)
- $(PREV) tar -cz $(RCS_TAR_IGNORE) -f $(KERNELPATH).tar.gz $(KERNELPATH)/.
- $(PREV) rm $(KERNELPATH)
-
- set -e; \
- $(CONFIG_SHELL) $(srctree)/scripts/mkversion > $(objtree)/.tmp_version
- set -e; \
- mv -f $(objtree)/.tmp_version $(objtree)/.version
-
- $(RPM) --target $(UTS_MACHINE) -ta ../$(KERNELPATH).tar.gz
- rm ../$(KERNELPATH).tar.gz
-
-clean-files := $(objtree)/kernel.spec
-
-# binrpm-pkg
-# ---------------------------------------------------------------------------
-$(objtree)/binkernel.spec: $(MKSPEC) $(srctree)/Makefile
- $(CONFIG_SHELL) $(MKSPEC) prebuilt > $@
-
-binrpm-pkg: $(objtree)/binkernel.spec FORCE
- $(MAKE) KBUILD_SRC=
- set -e; \
- $(CONFIG_SHELL) $(srctree)/scripts/mkversion > $(objtree)/.tmp_version
- set -e; \
- mv -f $(objtree)/.tmp_version $(objtree)/.version
-
- $(RPM) --define "_builddir $(srctree)" --target $(UTS_MACHINE) -bb $<
-
-clean-files += $(objtree)/binkernel.spec
-
-# Deb target
-# ---------------------------------------------------------------------------
-deb-pkg: FORCE
- $(MAKE) KBUILD_SRC=
- $(CONFIG_SHELL) $(srctree)/scripts/package/builddeb
-
-clean-dirs += $(objtree)/debian/
-
-
-# tarball targets
-# ---------------------------------------------------------------------------
-tar%pkg: FORCE
- $(MAKE) KBUILD_SRC=
- $(CONFIG_SHELL) $(srctree)/scripts/package/buildtar $@
-
-clean-dirs += $(objtree)/tar-install/
-
-
-# Help text displayed when executing 'make help'
-# ---------------------------------------------------------------------------
-help: FORCE
- @echo ' rpm-pkg - Build the kernel as an RPM package'
- @echo ' binrpm-pkg - Build an rpm package containing the compiled kernel'
- @echo ' and modules'
- @echo ' deb-pkg - Build the kernel as an deb package'
- @echo ' tar-pkg - Build the kernel as an uncompressed tarball'
- @echo ' targz-pkg - Build the kernel as a gzip compressed tarball'
- @echo ' tarbz2-pkg - Build the kernel as a bzip2 compressed tarball'
-
+# Dummy file
+help:
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
deleted file mode 100644
index 6edb29f..0000000
--- a/scripts/package/builddeb
+++ /dev/null
@@ -1,123 +0,0 @@
-#!/bin/sh
-#
-# builddeb 1.2
-# Copyright 2003 Wichert Akkerman <[email protected]>
-#
-# Simple script to generate a deb package for a Linux kernel. All the
-# complexity of what to do with a kernel after it is installer or removed
-# is left to other scripts and packages: they can install scripts in the
-# /etc/kernel/{pre,post}{inst,rm}.d/ directories that will be called on
-# package install and removal.
-
-set -e
-
-# Some variables and settings used throughout the script
-version=$KERNELRELEASE
-tmpdir="$objtree/debian/tmp"
-packagename=linux-$version
-
-if [ "$ARCH" == "um" ] ; then
- packagename=user-mode-linux-$version
-fi
-
-# Setup the directory structure
-rm -rf "$tmpdir"
-mkdir -p "$tmpdir/DEBIAN" "$tmpdir/lib" "$tmpdir/boot"
-if [ "$ARCH" == "um" ] ; then
- mkdir -p "$tmpdir/usr/lib/uml/modules/$version" "$tmpdir/usr/share/doc/$packagename" "$tmpdir/usr/bin"
-fi
-
-# Build and install the kernel
-if [ "$ARCH" == "um" ] ; then
- $MAKE linux
- cp System.map "$tmpdir/usr/lib/uml/modules/$version/System.map"
- cp .config "$tmpdir/usr/share/doc/$packagename/config"
- gzip "$tmpdir/usr/share/doc/$packagename/config"
- cp $KBUILD_IMAGE "$tmpdir/usr/bin/linux-$version"
-else
- cp System.map "$tmpdir/boot/System.map-$version"
- cp .config "$tmpdir/boot/config-$version"
- cp $KBUILD_IMAGE "$tmpdir/boot/vmlinuz-$version"
-fi
-
-if grep -q '^CONFIG_MODULES=y' .config ; then
- INSTALL_MOD_PATH="$tmpdir" make KBUILD_SRC= modules_install
- if [ "$ARCH" == "um" ] ; then
- mv "$tmpdir/lib/modules/$version"/* "$tmpdir/usr/lib/uml/modules/$version/"
- rmdir "$tmpdir/lib/modules/$version"
- fi
-fi
-
-# Install the maintainer scripts
-for script in postinst postrm preinst prerm ; do
- mkdir -p "$tmpdir/etc/kernel/$script.d"
- cat <<EOF > "$tmpdir/DEBIAN/$script"
-#!/bin/sh
-
-set -e
-
-test -d /etc/kernel/$script.d && run-parts --arg="$version" /etc/kernel/$script.d
-exit 0
-EOF
- chmod 755 "$tmpdir/DEBIAN/$script"
-done
-
-name="Kernel Compiler <$(id -nu)@$(hostname -f)>"
-# Generate a simple changelog template
-cat <<EOF > debian/changelog
-linux ($version) unstable; urgency=low
-
- * A standard release
-
- -- $name $(date -R)
-EOF
-
-# Generate a control file
-if [ "$ARCH" == "um" ]; then
-
-cat <<EOF > debian/control
-Source: linux
-Section: base
-Priority: optional
-Maintainer: $name
-Standards-Version: 3.6.1
-
-Package: $packagename
-Architecture: any
-Description: User Mode Linux kernel, version $version
- User-mode Linux is a port of the Linux kernel to its own system call
- interface. It provides a kind of virtual machine, which runs Linux
- as a user process under another Linux kernel. This is useful for
- kernel development, sandboxes, jails, experimentation, and
- many other things.
- .
- This package contains the Linux kernel, modules and corresponding other
- files version $version
-EOF
-
-else
-cat <<EOF > debian/control
-Source: linux
-Section: base
-Priority: optional
-Maintainer: $name
-Standards-Version: 3.6.1
-
-Package: $packagename
-Architecture: any
-Description: Linux kernel, version $version
- This package contains the Linux kernel, modules and corresponding other
- files version $version
-EOF
-fi
-
-# Fix some ownership and permissions
-chown -R root:root "$tmpdir"
-chmod -R go-w "$tmpdir"
-
-# Perform the final magic
-dpkg-gencontrol -isp
-dpkg --build "$tmpdir" ..
-
-exit 0
-
On Mon, 18 Jun 2007, Carlo Wood wrote:
>
> Well,... when, and because, it's not a linear thing as you mentioned
> before - it's not necessarily precisely a cut into half... so I thought,
> seeing those weird (not half) numbers that that was the cause.
You're correct - "git bisect" will not always be able to find an exact
half-way point, and I was wrong to imply that it will always be quite that
close.
It's easily off by a few commits because of merges that make it harder to
find a good bisection point, but it should never (practically) be off by
quite as much as you saw.
For example, I could expect that from 127 commits, it would go down to 70
rather than 64. But not to 110 - not unless there are some *really*
strange patterns with lots of criss-crossing merges.
And indeed, for me, using the same commit ID's as you used, I see a nice
bisection to just about exactly half.
> > It might be worth it just making sure your git is ok. It really is acting
> > oddly. What version is it?
>
> git version 1.4.4.4
You really do want to use git-1.5.x these days.
It does look like 1.4.4.4 may have a bug, although I'm really surprised:
we've certainly tweaked stuff in bisection, but I and others have used
"git bisect" since long before the git-1.4 days, and it has always worked
ok. So I wonder if it's something specific to that debian build.
Or possibly to the fact that you have some other dirty state (you might
want to do a "git diff HEAD" to see what the changes are, and maybe a "git
checkout -f" to get rid of any differences)
> I am using Debian (suite 'testing') and trying to be a debian purist -
> so it isn't like I can easily upgrade to 1.5.x : there is no debian
> package for that version in 'testing'.
I'm surprised that debuan
>
> Nevertheless, if you think it's important - then I can download and
> compile a tar ball of course - certainly when I don't have to install
> it to test it.
>
> --
> Carlo Wood <[email protected]>
>
> PS The result of 'git diff' is:
>
> diff --git a/include/asm-blackfin/macros.h b/include/asm-blackfin/macros.h
> deleted file mode 100644
> index e69de29..0000000
Ok, something deleted an empty file. Probably "make distclean". Our "make
clean" is sometimes too aggressive, and we generally shouldn't have empty
files.
> diff --git a/scripts/package/Makefile b/scripts/package/Makefile
> index 7c434e0..f758b75 100644
> --- a/scripts/package/Makefile
> +++ b/scripts/package/Makefile
but this one has actually been modified. To this:
> +# Dummy file
> +help:
And finally,
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> deleted file mode 100644
> index 6edb29f..0000000
That one also has been actually deleted. And "make distclean" doesn't do
that. You have something else going on.
Linus
On Mon, 18 Jun 2007, Linus Torvalds wrote:
> On Mon, 18 Jun 2007, Carlo Wood wrote:
>
> > diff --git a/scripts/package/Makefile b/scripts/package/Makefile
> > index 7c434e0..f758b75 100644
> > --- a/scripts/package/Makefile
> > +++ b/scripts/package/Makefile
>
> but this one has actually been modified. To this:
>
> > +# Dummy file
> > +help:
>
> And finally,
>
> > diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> > deleted file mode 100644
> > index 6edb29f..0000000
>
> That one also has been actually deleted. And "make distclean" doesn't do
> that. You have something else going on.
Probably make-kpkg removing the in-tree instructions for building debian
packages so that its own rules will be used instead or something like
that.
-Daniel
*This .sig left intentionally blank*
On Mon, Jun 18, 2007 at 01:42:18PM -0700, Linus Torvalds wrote:
> You really do want to use git-1.5.x these days.
>
> It does look like 1.4.4.4 may have a bug, although I'm really surprised:
> we've certainly tweaked stuff in bisection, but I and others have used
> "git bisect" since long before the git-1.4 days, and it has always worked
> ok. So I wonder if it's something specific to that debian build.
Well, it does indeed.
Without changing ANYTHING to my linux-2.6 source tree - I just
installed git 1.5.2.1 and now it behaves the way you describe.
Conclusion: the weird behaviour that you think was wrong is
totally due to git 1.4.4.4.
I'll redo the bisect with this new git.
--
Carlo Wood <[email protected]>
On Tue, 19 Jun 2007, Carlo Wood wrote:
>
> Conclusion: the weird behaviour that you think was wrong is
> totally due to git 1.4.4.4.
Ok. I'll bounce a note to Junio just due to curiosity in case he goes
"ahh, yeah, it was that known bug", but I'll otherwise ignore this.
Git-1.5.x is such a radically better version (not because it fixes this
bug, but because we fixed a number of other issues, notably some very
basic usability things), that I think any git users should really upgrade
to a newer version.
IOW, there's simply no reason to stay on anything older (git has always
been backwards compatible since very early on, so upgrading to a newer
version of git won't break anything, although some of the new UI's might
obviously cause you to do things differently).
> I'll redo the bisect with this new git.
Thanks,
Linus
On Mon, Jun 18, 2007 at 03:57:51PM -0700, Linus Torvalds wrote:
> > I'll redo the bisect with this new git.
>
> Thanks,
> Linus
Well, I did a new 'git bisect' - and if you ask me - it is still broken.
It's conclusion was this time:
hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
01da41b86f6e5f9a724e20a63f093d77e37d8056 is first bad commit
commit 01da41b86f6e5f9a724e20a63f093d77e37d8056
Author: Alexey Dobriyan <[email protected]>
Date: Sat Mar 3 01:13:35 2007 +0000
parisc: make command_line[] static
Signed-off-by: Alexey Dobriyan <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Kyle McMartin <[email protected]>
:040000 040000 eb42c17f2b8c686380fa540723d09e4b27127236 0a77f9c56f35076ae79f9f12a37769500c8f5ee9 M arch
Here is the log:
hikaru:/usr/src/kernel/git/linux-2.6>git bisect log
git-bisect start
# bad: [188e1f81ba31af1b65a2f3611df4c670b092bbac] Linux 2.6.22-rc5
git-bisect bad 188e1f81ba31af1b65a2f3611df4c670b092bbac
# good: [99f9f3d49cbc7d944476f6fde53a77ec789ab2aa] Merge branch
# 'for-linus' of
# git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
git-bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
# good: [9808901b6c63a1c850b072e624c228901a9eaf10] Blackfin serial
# driver: ignore framing and parity errors
git-bisect good 9808901b6c63a1c850b072e624c228901a9eaf10
# bad: [aba297927d1d558c7a94548135133bdf9172708a] Merge
# master.kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6
git-bisect bad aba297927d1d558c7a94548135133bdf9172708a
# good: [0127d6d5d925321650e7b92364420325689a03ef] Merge branch 'master'
# of master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6
git-bisect good 0127d6d5d925321650e7b92364420325689a03ef
# bad: [25971f68d392f1816e21520e9e59648403b0bdad] [PARISC] fix section
# mismatch in ccio-dma
git-bisect bad 25971f68d392f1816e21520e9e59648403b0bdad
# bad: [7022672e4046fac4699aa5f8ff2a5213b7ec4ff9] [PARISC] spelling
# fixes: arch/parisc/
git-bisect bad 7022672e4046fac4699aa5f8ff2a5213b7ec4ff9
# bad: [fd3eef10f5a55acdefbd3f53ca7618a35cb6231f] [PARISC] Wire up
# kexec_load syscall
git-bisect bad fd3eef10f5a55acdefbd3f53ca7618a35cb6231f
# bad: [2c8307f63dd5caaf7ff8ad5118951e559a9ed5c8] parisc: sync compat
# getdents
git-bisect bad 2c8307f63dd5caaf7ff8ad5118951e559a9ed5c8
# bad: [01da41b86f6e5f9a724e20a63f093d77e37d8056] parisc: make
# command_line[] static
git-bisect bad 01da41b86f6e5f9a724e20a63f093d77e37d8056
Personally I am convinced that the real problem is with
8888985144db8f4cb7e56154b31bdf233d3550bf
[AGPGART] intel_agp: fix device probe
This patch trys to fix device probe in two cases. First we should
correctly detect device if integrated graphics device is not enabled
or exists, like an add-in card is plugged. Second on some type of intel
GMCH, it might have multiple graphic chip models, like 945GME case, so
we should be sure the detect works through the whole table.
Signed-off-by: Wang Zhenyu <[email protected]>
Signed-off-by: Dave Jones <[email protected]>
The result of this patch is that the kernel starts to print
"agpgart: Detected an Intel 965G Chipset." again with the usual
disastrous results. Now, that doesn't mean that this patch is
wrong - but it explains why the problem returns after this patch.
--
Carlo Wood <[email protected]>
On Wed, Jun 20, 2007 at 01:37:16AM +0200, Carlo Wood wrote:
> Personally I am convinced that the real problem is with
> 8888985144db8f4cb7e56154b31bdf233d3550bf
>
> [AGPGART] intel_agp: fix device probe
>
> This patch trys to fix device probe in two cases. First we should
> correctly detect device if integrated graphics device is not enabled
> or exists, like an add-in card is plugged. Second on some type of intel
> GMCH, it might have multiple graphic chip models, like 945GME case, so
> we should be sure the detect works through the whole table.
>
> Signed-off-by: Wang Zhenyu <[email protected]>
> Signed-off-by: Dave Jones <[email protected]>
>
>
> The result of this patch is that the kernel starts to print
> "agpgart: Detected an Intel 965G Chipset." again with the usual
> disastrous results. Now, that doesn't mean that this patch is
> wrong - but it explains why the problem returns after this patch.
Right, without this patch, probing was broken, so we never matched
an agp driver to the chipset. The question remains though, why
the initialisation of the chip is so broken.
Dave
--
http://www.codemonkey.org.uk
On Wed, 20 Jun 2007, Carlo Wood wrote:
> On Mon, Jun 18, 2007 at 03:57:51PM -0700, Linus Torvalds wrote:
> > > I'll redo the bisect with this new git.
> >
> > Thanks,
> > Linus
>
> Well, I did a new 'git bisect' - and if you ask me - it is still broken.
>
> It's conclusion was this time:
>
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad
> 01da41b86f6e5f9a724e20a63f093d77e37d8056 is first bad commit
>
> parisc: make command_line[] static
Heh.
Yeah, at this point I think we can pretty much guarantee that your problem
is one of two cases:
- either a bit random, and depends on some timing thing, and one of the
kernels you marked "good" wasn't really.
It's not likely that you marked a good kernel bad, of course, since
with a good kernel, everything should have always worked, but with a
bad kernel and a bug that isn't entirely reproducible, you'd mark it
"good" by mistake - because it just randomly didn't show the problem.
OR
- we actually have two different commits that introduce the problem for
you, and it comes and goes, and the bisection doesn't work, because
there isn't a clear "this side works, that other side does not"
situation.
For example, later on you say:
> Personally I am convinced that the real problem is with
> 8888985144db8f4cb7e56154b31bdf233d3550bf
but if you look at your commit log, you have:
> # bad: [25971f68d392f1816e21520e9e59648403b0bdad] [PARISC] fix section
> # mismatch in ccio-dma
> git-bisect bad 25971f68d392f1816e21520e9e59648403b0bdad
Notice? You said that 25971f68d392f1816e21520e9e59648403b0bdad was bad,
but that is *before_ the 8888985144db8f4cb7e56154b31bdf233d3550bf commit.
Do a
gitk 25971f68d3..8888985144
to see that part of the history.
So maybe you didn't test that kernel properly? And maybe it really is
random, and something has happened that just makes it happen more often?
Also, some *really* nasty bugs end up being about bad initialization, and
it turns out that what happens more is not which kernel you run, but what
the *previous* kernel you ran is, because it left some device driver state
that the bug doesn't clean up!
Anyway, can you try that 25971f68d3 kernel one more time? You marked it
bad, but if that kernel is bad, then the commit you are pointing to is
*not* the culprit.
Linus
On 2007.06.20 01:37:16 +0000, Carlo Wood wrote:
> The result of this patch is that the kernel starts to print
> "agpgart: Detected an Intel 965G Chipset." again with the usual
> disastrous results. Now, that doesn't mean that this patch is
> wrong - but it explains why the problem returns after this patch.
>
Yep, the device table patch doesn't change any function, so your problem
started from when 965G support patch has been in kernel.
Carlo, pls try a kernel param of "pci=nommconf" to see if that could
fix your hang. There might be a BIOS bug, as similar issue also happen
like https://bugzilla.novell.com/show_bug.cgi?id=228683
I think for i965 we could have following patch to fix this, we may
fail if no IGD device got detected.
Signed-off-by: Wang Zhenyu <[email protected]>
---
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index 0439ee9..5a54a9c 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -1855,15 +1855,15 @@ static const struct intel_driver_description {
{ PCI_DEVICE_ID_INTEL_82946GZ_HB, PCI_DEVICE_ID_INTEL_82946GZ_IG, 0, "946GZ",
&intel_845_driver, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_1_HB, PCI_DEVICE_ID_INTEL_82965G_1_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965Q_HB, PCI_DEVICE_ID_INTEL_82965Q_IG, 0, "965Q",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_HB, PCI_DEVICE_ID_INTEL_82965G_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GM_IG, 1, "965GM",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GME_IG, 0, "965GME/GLE",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_7505_0, 0, 0, "E7505", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_7205_0, 0, 0, "E7205", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_G33_HB, PCI_DEVICE_ID_INTEL_G33_IG, 0, "G33",
@@ -1917,6 +1917,7 @@ static int __devinit agp_intel_probe(struct pci_dev *pdev,
}
if (bridge->driver == NULL) {
+ /* The bridge has no AGP or no gfx device */
printk(KERN_WARNING PFX "Failed to find bridge device "
"(chip_id: %04x)\n", intel_agp_chipsets[i].gmch_chip_id);
agp_put_bridge(bridge);
---
On 2007.06.20 09:15:21 +0000, Wang Zhenyu wrote:
>
> I think for i965 we could have following patch to fix this, we may
> fail if no IGD device got detected.
>
oops, missing 946G, what a name...
Signed-off-by: Wang Zhenyu <[email protected]>
---
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index 0439ee9..145b4a1 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -1853,17 +1853,17 @@ static const struct intel_driver_description {
{ PCI_DEVICE_ID_INTEL_82945GM_HB, PCI_DEVICE_ID_INTEL_82945GME_IG, 0, "945GME",
&intel_845_driver, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82946GZ_HB, PCI_DEVICE_ID_INTEL_82946GZ_IG, 0, "946GZ",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_1_HB, PCI_DEVICE_ID_INTEL_82965G_1_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965Q_HB, PCI_DEVICE_ID_INTEL_82965Q_IG, 0, "965Q",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_HB, PCI_DEVICE_ID_INTEL_82965G_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GM_IG, 1, "965GM",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GME_IG, 0, "965GME/GLE",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_7505_0, 0, 0, "E7505", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_7205_0, 0, 0, "E7205", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_G33_HB, PCI_DEVICE_ID_INTEL_G33_IG, 0, "G33",
@@ -1917,6 +1917,7 @@ static int __devinit agp_intel_probe(struct pci_dev *pdev,
}
if (bridge->driver == NULL) {
+ /* The bridge has no AGP or no gfx device */
printk(KERN_WARNING PFX "Failed to find bridge device "
"(chip_id: %04x)\n", intel_agp_chipsets[i].gmch_chip_id);
agp_put_bridge(bridge);
---
On Tue, Jun 19, 2007 at 05:09:10PM -0700, Linus Torvalds wrote:
> Heh.
>
> Yeah, at this point I think we can pretty much guarantee that your problem
> is one of two cases:
>
> - either a bit random, and depends on some timing thing, and one of the
> kernels you marked "good" wasn't really.
Nope
> It's not likely that you marked a good kernel bad, of course, since
> with a good kernel, everything should have always worked, but with a
> bad kernel and a bug that isn't entirely reproducible, you'd mark it
> "good" by mistake - because it just randomly didn't show the problem.
Nope
> OR
>
> - we actually have two different commits that introduce the problem for
> you, and it comes and goes, and the bisection doesn't work, because
> there isn't a clear "this side works, that other side does not"
> situation.
Yes
Looking a bit closer to the bisect myself, I note that
25971f68d392f1816e21520e9e59648403b0bdad and
aba297927d1d558c7a94548135133bdf9172708a are part of
a branch that is derived from a very "old" revision.
git bisect assumes that such an old revision is good,
but in fact - that was already bad as well, because
the history of this bug is:
2.6.22-rc5 BAD
2.6.22-rc4+somethingelse BAD
2.6.22-rc4+something GOOD
2.6.22-rc4 BAD
...
2.6.18-rc1 BAD
2.6.18 GOOD
Thus: BAD BAD BAD GOOD GOOD BAD BAD
and git bisect can't handle that, even though I started
with a 'good' start point and a bad start point at the end.
> For example, later on you say:
>
> > Personally I am convinced that the real problem is with
> > 8888985144db8f4cb7e56154b31bdf233d3550bf
>
> but if you look at your commit log, you have:
>
> > # bad: [25971f68d392f1816e21520e9e59648403b0bdad] [PARISC] fix section
> > # mismatch in ccio-dma
> > git-bisect bad 25971f68d392f1816e21520e9e59648403b0bdad
>
> Notice? You said that 25971f68d392f1816e21520e9e59648403b0bdad was bad,
> but that is *before_ the 8888985144db8f4cb7e56154b31bdf233d3550bf commit.
> Do a
>
> gitk 25971f68d3..8888985144
>
> to see that part of the history.
This part is thus based upon a revision so old that it was bad again,
even before the small period that it was good.
> So maybe you didn't test that kernel properly? And maybe it really is
> random, and something has happened that just makes it happen more often?
No, it is really 100% reproducible.
--
Carlo Wood <[email protected]>
On Wed, Jun 20, 2007 at 03:11:20PM +0200, Carlo Wood wrote:
> 2.6.22-rc5 BAD
> 2.6.22-rc4+somethingelse BAD
> 2.6.22-rc4+something GOOD
> 2.6.22-rc4 BAD
> ...
> 2.6.18-rc1 BAD
> 2.6.18 GOOD
Ok, that made no sense. I meant:
> 2.6.19-rc1 BAD
> 2.6.18 GOOD
--
Carlo Wood <[email protected]>
On Wed, Jun 20, 2007 at 09:15:21AM +0800, Wang Zhenyu wrote:
> Yep, the device table patch doesn't change any function, so your problem
> started from when 965G support patch has been in kernel.
Yup
> Carlo, pls try a kernel param of "pci=nommconf" to see if that could
> fix your hang. There might be a BIOS bug, as similar issue also happen
> like https://bugzilla.novell.com/show_bug.cgi?id=228683
That bugreport looks EXACTLY like the problem that I ran into.
Note that they have the same motherboard as me: ASUS P5B Deluxe
I will try pci=nommconf in a moment. It isn't the best workaround
however as it should reduce the available RAM from 4GB to 3GB.
agp=off would be a better workaround.
Carlo Wood <[email protected]>
On Wed, Jun 20, 2007 at 09:15:21AM +0800, Wang Zhenyu wrote:
> Carlo, pls try a kernel param of "pci=nommconf" to see if that could
> fix your hang.
This does not fix the problem.
Prestine 2.6.22-rc5 with param pci=nommconf results in:
^MPress any key to continue.
^MPress any key to continue.
^MPress 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-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[11;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 ^[[11;75H^[[m^[[m^[[12;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode) ^[[12;75H^[[m^[[m^[[13;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (serial console) ^[[13;75H^[[m^[[m^[[14;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[14;75H^[[m^[[m^[[15;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[15;75H^[[m^[[m^[[16;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[16;75H^[[m^[[16;78Hv^[[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 ^[[5;75H^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7m^[[8;3H Debian GNU/Linux, kernel 2.!
6.22-rc5
-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[7m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[7m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[H^[[J Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611
df4c670b092bbac-amd64 (serial console)'
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd
64 root=/dev/md2 ro pci=nommconf 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 pci=nommconf 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[0x03] enabled)
Processor #3
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled)
Processor #2
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 pci=nommconf 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.664 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.90 BogoMIPS (lpj=10673812)
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 16666638
Detected 16.666 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/4 APIC 0x3
Initializing CPU#1
Calibrating delay using timer specific routine.. 5333.36 BogoMIPS (lpj=10666736)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 1/3 -> 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.48 BogoMIPS (lpj=10666973)
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 0x2
Initializing CPU#3
Calibrating delay using timer specific routine.. 5333.54 BogoMIPS (lpj=10667095)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L3 cache: 4096K
CPU 3/2 -> 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=3361
NET: Registered protocol family 16
ACPI: bus type pci registered
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
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
Time: tsc clocksource has been installed.
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(1182347467.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
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
usb 4-2: new low speed USB device using uhci_hcd and address 2
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 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: device descriptor read/all, error -71
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]
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 4
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 0xffffc2000144a900 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata2: SATA max UDMA/133 cmd 0xffffc2000144a980 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata3: SATA max UDMA/133 cmd 0xffffc2000144aa00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata4: SATA max UDMA/133 cmd 0xffffc2000144aa80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata5: SATA max UDMA/133 cmd 0xffffc2000144ab00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata6: SATA max UDMA/133 cmd 0xffffc2000144ab80 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
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 3018 MB/s
raid6: int64x4 2883 MB/s
raid6: int64x8 1930 MB/s
raid6: sse2x1 4191 MB/s
raid6: sse2x2 5469 MB/s
raid6: sse2x4 7920 MB/s
raid6: using algorithm sse2x4 (7920 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 ...
kinit: name_to_dAttempting manual resume
ev_t(/dev/md1) = md1(9,1)
kinit: trying to resume from /dev/md1
kinit: No resume image, doing normal boot...
kjournald starting. Commit interval 5 seconds
Done.
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
^MINIT: version 2.86 booting^M
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.
and then hangs.
--
Carlo Wood <[email protected]>
On Wed, Jun 20, 2007 at 09:42:27AM +0800, Wang Zhenyu wrote:
> oops, missing 946G, what a name...
>
> Signed-off-by: Wang Zhenyu <[email protected]>
> ---
> diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
> index 0439ee9..145b4a1 100644
> --- a/drivers/char/agp/intel-agp.c
> +++ b/drivers/char/agp/intel-agp.c
> @@ -1853,17 +1853,17 @@ static const struct intel_driver_description {
> { PCI_DEVICE_ID_INTEL_82945GM_HB, PCI_DEVICE_ID_INTEL_82945GME_IG, 0, "945GME",
> &intel_845_driver, &intel_915_driver },
> { PCI_DEVICE_ID_INTEL_82946GZ_HB, PCI_DEVICE_ID_INTEL_82946GZ_IG, 0, "946GZ",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_82965G_1_HB, PCI_DEVICE_ID_INTEL_82965G_1_IG, 0, "965G",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_82965Q_HB, PCI_DEVICE_ID_INTEL_82965Q_IG, 0, "965Q",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_82965G_HB, PCI_DEVICE_ID_INTEL_82965G_IG, 0, "965G",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GM_IG, 1, "965GM",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GME_IG, 0, "965GME/GLE",
> - &intel_845_driver, &intel_i965_driver },
> + NULL, &intel_i965_driver },
> { PCI_DEVICE_ID_INTEL_7505_0, 0, 0, "E7505", &intel_7505_driver, NULL },
> { PCI_DEVICE_ID_INTEL_7205_0, 0, 0, "E7205", &intel_7505_driver, NULL },
> { PCI_DEVICE_ID_INTEL_G33_HB, PCI_DEVICE_ID_INTEL_G33_IG, 0, "G33",
> @@ -1917,6 +1917,7 @@ static int __devinit agp_intel_probe(struct pci_dev *pdev,
> }
>
> if (bridge->driver == NULL) {
> + /* The bridge has no AGP or no gfx device */
> printk(KERN_WARNING PFX "Failed to find bridge device "
> "(chip_id: %04x)\n", intel_agp_chipsets[i].gmch_chip_id);
> agp_put_bridge(bridge);
> ---
This patch causes 2.6.22-rc5 to boot :).
However, the resulting dmesg is:
==snip======================================
^MPress any key to continue.
^MPress 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-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[11;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 ^[[11;75H^[[m^[[m^[[12;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (single-user mode) ^[[12;75H^[[m^[[m^[[13;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 (serial console) ^[[13;75H^[[m^[[m^[[14;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[14;75H^[[m^[[m^[[15;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[15;75H^[[m^[[m^[[16;3H Debian GNU/Linux, kernel 2.6.22-rc2-bisect-2c8307f63dd5caaf7ff8ad5118> ^[[16;75H^[[m^[[16;78Hv^[[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-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188!
e1f81ba3
1af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[7m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[7m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[7m^[[11;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 ^[[11;75H^[[m^[[m^[[11;3H Debian GNU/Linux, kernel 2.6.22-rc4-hikaru-amd64 ^[[11;75H^[[m^[[m^[[7m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[10;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[10;75H^[[m^[[m^[[7m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[9;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[9;75H^[[m^[[m^[[7m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[8;3H Debian GNU/Linux, kernel 2.6.22-rc5-master-188e1f81ba31af1b65a2f3611d> ^[[8;75H^[[m^[[m^[[7m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[m^[[7m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[5;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[5;75H^[[m^[[m^[[7m^[[6;3H Debian G!
NU/Linux
, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[6;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[6;75H^[[m^[[m^[[7m^[[7;3H Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4> ^[[7;75H^[[m^[[H^[[J Booting 'Debian GNU/Linux, kernel 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df
4c670b092bbac-amd64 (serial console)'
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64
root=/dev/md2 ro console=tty0 console=ttyS0,38400n8
[Linux-bzImage, setup=0x1e00, size=0x17ac68]
initrd /initrd.img-2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4c670b092bbac-am
d64
[Linux-initrd @ 0x379e6000, 0x60996b bytes]
savedefault
Linux version 2.6.22-rc5-agp0-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 (carlo@hikaru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Jun 20 15:28:37 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=10673830)
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 16666652
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.36 BogoMIPS (lpj=10666730)
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=10666782)
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=10666729)
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=3316
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
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
Time: tsc clocksource has been installed.
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(1182347106.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
usb 4-2: configuration #1 chosen from 1 choice
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
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 0xffffc20001446900 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata2: SATA max UDMA/133 cmd 0xffffc20001446980 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata3: SATA max UDMA/133 cmd 0xffffc20001446a00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata4: SATA max UDMA/133 cmd 0xffffc20001446a80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata5: SATA max UDMA/133 cmd 0xffffc20001446b00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 0
ata6: SATA max UDMA/133 cmd 0xffffc20001446b80 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: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 usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 6 ports detected
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<6>ACPI: PCI Interrupt 0000:04:03.0[A] -> sda7 sda8GSI 21 (level, low) -> IRQ 21
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
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[feaff800-feafffff] Max Packet=[2048] IR/IT contexts=[4/8]
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 >
usb 4-2: USB disconnect, address 2
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
usb 4-2: new low speed USB device using uhci_hcd and address 3
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 ...
usb 4-2: configuration #1 chosen from 1 choice
input: Microsoft Microsoft Wireless Intellimouse Explorer? 1.0A as /class/input/input2
input: USB HID v1.10 Mouse [Microsoft Microsoft Wireless Intellimouse Explorer? 1.0A] on usb-0000:00:1d.1-2
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 2879 MB/s
raid6: int64x8 1920 MB/s
raid6: sse2x1 4193 MB/s
raid6: sse2x2 4804 MB/s
raid6: sse2x4 7876 MB/s
raid6: using algorithm sse2x4 (7876 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 ...
kinit: name_to_dAttempting manual resume
ev_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
Begin: Running /EXT3-fs: mounted filesystem with ordered data mode.
scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
Mount failed for selinuxfs on /selinux: No such device
^MINIT: version 2.86 booting^M
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...agpgart: Failed to find bridge device (chip_id: 29a2)
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
sky2 eth0: addr 00:1a:92:3a:4a:c1
input: PC Speaker as /class/input/input3
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/input4
done.
Setting parameters of disc: (none).
Checking root file system...fsck 1.40-WIP (14-Nov-2006)
/dev/md2: clean, 20949/488640 files, 153388/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: [email protected]
.
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, 48/24096 files, 61709/96256 blocks
/dev/md5: clean, 40442/1221600 files, 1029243/2441824 blocks
/dev/sdd2: clean, 10111/4889248 files, 5934404/9765511 blocks (check in 3 mounts)
/dev/sdd3: clean, 2050/21987328 files, 40298300/43961872 blocks
/dev/md8: clean, 116771/2747136 files, 909674/5490144 blocks
/dev/md3: clean, 107476/2443200 files, 699836/4883712 blocks
/dev/md6: clean, 53/1221600 files, 76570/2441824 blocks (check in 3 mounts)
/dev/md7: clean, 1179373/7323648 files, 7577434/14647200 blocks
/dev/md4: clean, 8182/732960 files, 293632/1465856 blocks
/dev/mapper/encrypted: clean, 14627/12222464 files, 13984183/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-c84448a9-0a57-4c2a-9a41-c60e0591ba06 sid32-df306a93-1d63-494d-a726-c924190900c6.
^MINIT: Entering runlevel: 2^M
Starting system log daemon....
Starting kernel log daemon....
Starting portmap daemon...Already running..
Starting HP Linux Printing and Imaging System:sky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
hpiod hpssd.
Loading ACPI modules...input: Power Button (FF) as /class/input/input5
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input6
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 [email protected]).
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:
==snip======================================
and I am not sure if you will consider the:
agpgart: Failed to find bridge device (chip_id: 29a2)
a bug.
--
Carlo Wood <[email protected]>
On 2007.06.20 16:02:37 +0000, Carlo Wood wrote:
>
> and I am not sure if you will consider the:
>
> agpgart: Failed to find bridge device (chip_id: 29a2)
>
> a bug.
yeah, the error message needs to be fixed only if AGP cap
exists. I was checking with other GMCH data sheets, we'd better
disable AGP for chip that has no AGP port. I will send out
another patch later.
Thanks Carlo to report this problem. The following patch should fix
his and potential issue.
[AGPGART] intel_agp: don't load if no IGD detected and no AGP port
After i915 chip, GMCH has no AGP port. Origin bridge driver in device
table will try to access illegal regs like APBASE, APSIZE, etc. This
may cause problem.
So mark them as NULL in the table, we won't load if no IGD got detect
and bridge has no AGP port.
Signed-off-by: Wang Zhenyu <[email protected]>
---
drivers/char/agp/intel-agp.c | 35 +++++++++++++++++++----------------
1 files changed, 19 insertions(+), 16 deletions(-)
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index 0439ee9..a124060 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -1843,35 +1843,35 @@ static const struct intel_driver_description {
&intel_845_driver, &intel_830_driver },
{ PCI_DEVICE_ID_INTEL_82875_HB, 0, 0, "i875", &intel_845_driver, NULL },
{ PCI_DEVICE_ID_INTEL_82915G_HB, PCI_DEVICE_ID_INTEL_82915G_IG, 0, "915G",
- &intel_845_driver, &intel_915_driver },
+ NULL, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82915GM_HB, PCI_DEVICE_ID_INTEL_82915GM_IG, 0, "915GM",
- &intel_845_driver, &intel_915_driver },
+ NULL, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82945G_HB, PCI_DEVICE_ID_INTEL_82945G_IG, 0, "945G",
- &intel_845_driver, &intel_915_driver },
+ NULL, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82945GM_HB, PCI_DEVICE_ID_INTEL_82945GM_IG, 1, "945GM",
- &intel_845_driver, &intel_915_driver },
+ NULL, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82945GM_HB, PCI_DEVICE_ID_INTEL_82945GME_IG, 0, "945GME",
- &intel_845_driver, &intel_915_driver },
+ NULL, &intel_915_driver },
{ PCI_DEVICE_ID_INTEL_82946GZ_HB, PCI_DEVICE_ID_INTEL_82946GZ_IG, 0, "946GZ",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_1_HB, PCI_DEVICE_ID_INTEL_82965G_1_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965Q_HB, PCI_DEVICE_ID_INTEL_82965Q_IG, 0, "965Q",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965G_HB, PCI_DEVICE_ID_INTEL_82965G_IG, 0, "965G",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GM_IG, 1, "965GM",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_82965GM_HB, PCI_DEVICE_ID_INTEL_82965GME_IG, 0, "965GME/GLE",
- &intel_845_driver, &intel_i965_driver },
+ NULL, &intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_7505_0, 0, 0, "E7505", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_7205_0, 0, 0, "E7205", &intel_7505_driver, NULL },
{ PCI_DEVICE_ID_INTEL_G33_HB, PCI_DEVICE_ID_INTEL_G33_IG, 0, "G33",
- &intel_845_driver, &intel_g33_driver },
+ NULL, &intel_g33_driver },
{ PCI_DEVICE_ID_INTEL_Q35_HB, PCI_DEVICE_ID_INTEL_Q35_IG, 0, "Q35",
- &intel_845_driver, &intel_g33_driver },
+ NULL, &intel_g33_driver },
{ PCI_DEVICE_ID_INTEL_Q33_HB, PCI_DEVICE_ID_INTEL_Q33_IG, 0, "Q33",
- &intel_845_driver, &intel_g33_driver },
+ NULL, &intel_g33_driver },
{ 0, 0, 0, NULL, NULL, NULL }
};
@@ -1917,8 +1917,11 @@ static int __devinit agp_intel_probe(struct pci_dev *pdev,
}
if (bridge->driver == NULL) {
- printk(KERN_WARNING PFX "Failed to find bridge device "
- "(chip_id: %04x)\n", intel_agp_chipsets[i].gmch_chip_id);
+ /* bridge has no AGP and no IGD detected */
+ if (cap_ptr)
+ printk(KERN_WARNING PFX "Failed to find bridge device "
+ "(chip_id: %04x)\n",
+ intel_agp_chipsets[i].gmch_chip_id);
agp_put_bridge(bridge);
return -ENODEV;
}
--
1.4.4.4
On Thu, Jun 21, 2007 at 01:43:18PM +0800, Wang Zhenyu wrote:
> Thanks Carlo to report this problem. The following patch should fix
> his and potential issue.
Thanks for fixing it Wang :)
I have to admit that the Real Reason I did put time into this is because
I wanted to be sure that when debian upgrades 'testing' to the next
kernel, that I wouldn't be f*ck*d. But - as I just read in the new
kernel testing howto - that is a legit reason to do kernel testing ;)
> [AGPGART] intel_agp: don't load if no IGD detected and no AGP port
>
> After i915 chip, GMCH has no AGP port. Origin bridge driver in device
> table will try to access illegal regs like APBASE, APSIZE, etc. This
> may cause problem.
I am glad to see that you found a real reason for why it might have
gone wrong. Just not initializing because it's not needed, but not
understanding WHY it went wrong would have been rather unsatisfactory.
I've tested this patch - and it works (is this the point where I'd
add an 'Ack-something'? Here is the dmesg (the -agp1 in the version
is your patch):
Linux version 2.6.22-rc5-agp1-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 (carlo@hikaru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Jun 21 15:16:09 CEST 2007
Command line: root=/dev/md2 ro
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)
Entering add_active_range(0, 0, 158) 0 entries of 3200 used
Entering add_active_range(0, 256, 524176) 1 entries of 3200 used
Entering add_active_range(0, 1048576, 1572864) 2 entries of 3200 used
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
Entering add_active_range(0, 0, 158) 0 entries of 3200 used
Entering add_active_range(0, 256, 524176) 1 entries of 3200 used
Entering add_active_range(0, 1048576, 1572864) 2 entries of 3200 used
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
On node 0 totalpages: 1048366
DMA zone: 56 pages used for memmap
DMA zone: 993 pages reserved
DMA zone: 2949 pages, LIFO batch:0
DMA32 zone: 14280 pages used for memmap
DMA32 zone: 505800 pages, LIFO batch:31
Normal zone: 7168 pages used for memmap
Normal zone: 517120 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
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)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
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
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
time.c: Detected 2666.668 MHz processor.
Console: colour VGA+ 80x25
Checking aperture...
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
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=10673831)
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 16666663
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.36 BogoMIPS (lpj=10666734)
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=10666780)
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=10666722)
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=3353
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: Probing PCI hardware (bus 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 Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
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: ACPI device : hid PNP0A08
pnp: ACPI device : hid PNP0C01
pnp: ACPI device : hid PNP0200
pnp: ACPI device : hid PNP0B00
pnp: ACPI device : hid PNP0800
pnp: ACPI device : hid PNP0C04
pnp: ACPI device : hid PNP0501
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0103
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0303
pnp: ACPI device : hid PNP0F03
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0C01
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: the driver 'system' has been registered
pnp: match found with the PnP device '00:01' and the driver 'system'
pnp: 00:01: iomem range 0xfed14000-0xfed19fff has been reserved
pnp: match found with the PnP device '00:07' and the driver 'system'
pnp: 00:07: ioport range 0x290-0x297 has been reserved
pnp: match found with the PnP device '00:08' and the driver 'system'
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: match found with the PnP device '00:0a' and the driver 'system'
pnp: 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
Time: tsc clocksource has been installed.
pnp: match found with the PnP device '00:0d' and the driver 'system'
pnp: 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
pnp: match found with the PnP device '00:0e' and the driver 'system'
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
PCI: Setting latency timer of device 0000:00:01.0 to 64
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.5 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 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(1182441605.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)
Boot video device is 0000:01:00.0
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:01.0:pcie00]
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
PCI: Setting latency timer of device 0000:00:1c.5 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.5:pcie00]
Allocate Port Service[0000:00:1c.5:pcie02]
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Linux agpgart interface v0.102 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
pnp: the driver 'serial' has been registered
pnp: match found with the PnP device '00:06' and the driver 'serial'
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
pnp: the driver 'i8042 kbd' has been registered
pnp: match found with the PnP device '00:0b' and the driver 'i8042 kbd'
pnp: the driver 'i8042 aux' has been registered
pnp: match found with the PnP device '00:0c' and the driver 'i8042 aux'
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
Freeing unused kernel memory: 296k freed
input: AT Translated Set 2 keyboard as /class/input/input0
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
PCI: Setting latency timer of device 0000:00:1a.0 to 64
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
libata version 2.21 loaded.
ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1a.1 to 64
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
PCI: Setting latency timer of device 0000:00:1a.7 to 64
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
PCI: cache line size of 32 is not supported by device 0000:00:1a.7
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
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 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
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 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
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 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
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 7
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
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
ahci 0000:00:1f.2: version 2.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 2
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
PCI: Setting latency timer of device 0000:00:1f.2 to 64
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] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: 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] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 145226112 512-byte hardware sectors (74356 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: 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] Mode Sense: 00 3a 00 00
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] Mode Sense: 00 3a 00 00
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] Mode Sense: 00 3a 00 00
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] Mode Sense: 00 3a 00 00
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
sr 4:0:0:0: Attached scsi CD-ROM sr0
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
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
pnp: the driver 'ide' has been registered
Probing IDE interface ide0...
Probing IDE interface ide1...
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d800011b7cd2]
md: raid1 personality registered for level 1
raid5: automatically using best checksumming function: generic_sse
generic_sse: 9514.000 MB/sec
raid5: using function: generic_sse (9514.000 MB/sec)
raid6: int64x1 2501 MB/s
raid6: int64x2 3018 MB/s
raid6: int64x4 2876 MB/s
raid6: int64x8 1920 MB/s
raid6: sse2x1 4192 MB/s
raid6: sse2x2 4387 MB/s
raid6: sse2x4 7840 MB/s
raid6: using algorithm sse2x4 (7840 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: md0 stopped.
md: bind<sdb1>
md: bind<sdc1>
md: bind<sda1>
raid1: raid set md0 active with 3 out of 3 mirrors
md: md1 stopped.
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
md: md2 stopped.
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
md: md3 stopped.
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
md: md4 stopped.
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
md: md5 stopped.
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
md: md6 stopped.
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
md: md7 stopped.
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
md: md8 stopped.
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
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input2
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:02:00.0 to 64
sky2 0000:02:00.0: v1.14 addr 0xfe9fc000 irq 17 Yukon-EC Ultra (0xb4) rev 2
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
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
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
iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
EXT3 FS on md2, internal journal
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!
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
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.
Adding 15631096k swap on /dev/mapper/cswap. Priority:1 extents:1 across:15631096k
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
sky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
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]
pnp: the driver 'parport_pc' has been registered
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
Installing knfsd (copyright (C) 1996 [email protected]).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
eth1: no IPv6 routers present
Hmm, the dmesg stops here... Perhaps I should have
captured it with the serial console. But well, I'll
consider it fixed I don't think there was a warning
message. If there is then I'll post that later.
--
Carlo Wood <[email protected]>
On 2007.06.21 18:10:50 +0000, Carlo Wood wrote:
>
> I am glad to see that you found a real reason for why it might have
> gone wrong. Just not initializing because it's not needed, but not
> understanding WHY it went wrong would have been rather unsatisfactory.
>
yes, I understand, but it looks we did the wrong thing in the first step,
so... Thanks for testing this!
> On Thu, 21 Jun 2007 13:43:18 +0800 Wang Zhenyu <[email protected]> wrote:
> Thanks Carlo to report this problem. The following patch should fix
> his and potential issue.
>
> [AGPGART] intel_agp: don't load if no IGD detected and no AGP port
>
> After i915 chip, GMCH has no AGP port. Origin bridge driver in device
> table will try to access illegal regs like APBASE, APSIZE, etc. This
> may cause problem.
>
> So mark them as NULL in the table, we won't load if no IGD got detect
> and bridge has no AGP port.
Looking at the above, I have no way of telling what the actual bug is, nor
have I any way of telling what the consequences would be of not having this
patch in 2.6.22. Nor can I tell whether we want it in 2.6.21.x.
I probably _could_ work this out, and kinda did with a bit of list-trolling
(verdict: needed in 2.6.22) but please, take care to describe the
importance of a patch in the changelog?
Thanks.
On Sat, Jun 23, 2007 at 09:52:03AM -0700, Andrew Morton wrote:
> > On Thu, 21 Jun 2007 13:43:18 +0800 Wang Zhenyu <[email protected]> wrote:
> > Thanks Carlo to report this problem. The following patch should fix
> > his and potential issue.
> >
> > [AGPGART] intel_agp: don't load if no IGD detected and no AGP port
> >
> > After i915 chip, GMCH has no AGP port. Origin bridge driver in device
> > table will try to access illegal regs like APBASE, APSIZE, etc. This
> > may cause problem.
> >
> > So mark them as NULL in the table, we won't load if no IGD got detect
> > and bridge has no AGP port.
>
> Looking at the above, I have no way of telling what the actual bug is, nor
> have I any way of telling what the consequences would be of not having this
> patch in 2.6.22. Nor can I tell whether we want it in 2.6.21.x.
>
> I probably _could_ work this out, and kinda did with a bit of list-trolling
> (verdict: needed in 2.6.22) but please, take care to describe the
> importance of a patch in the changelog?
This got merged a day or two ago.
"will try to access illegal regs.." being the key part of the changelog
above. Without this diff, it goes bang, and stops booting on certain
chipsets.
Dave
--
http://www.codemonkey.org.uk
On Sat, 23 Jun 2007 14:42:21 -0400 Dave Jones <[email protected]> wrote:
> > I probably _could_ work this out, and kinda did with a bit of list-trolling
> > (verdict: needed in 2.6.22) but please, take care to describe the
> > importance of a patch in the changelog?
>
> This got merged a day or two ago.
OK. -stable didn't appear to get a copy though?
On Sat, Jun 23, 2007 at 11:50:49AM -0700, Andrew Morton wrote:
> On Sat, 23 Jun 2007 14:42:21 -0400 Dave Jones <[email protected]> wrote:
>
> > > I probably _could_ work this out, and kinda did with a bit of list-trolling
> > > (verdict: needed in 2.6.22) but please, take care to describe the
> > > importance of a patch in the changelog?
> >
> > This got merged a day or two ago.
>
> OK. -stable didn't appear to get a copy though?
Correct. It'll need a slightly different fix due to the cleanups done in .22rc
I also wanted it to sit for a few days to make sure there aren't any
other nasties lurking that this churn has unearthed.
Dave
--
http://www.codemonkey.org.uk
On 2007.06.23 11:50:49 +0000, Andrew Morton wrote:
> On Sat, 23 Jun 2007 14:42:21 -0400 Dave Jones <[email protected]> wrote:
>
> > > I probably _could_ work this out, and kinda did with a bit of list-trolling
> > > (verdict: needed in 2.6.22) but please, take care to describe the
> > > importance of a patch in the changelog?
> >
> > This got merged a day or two ago.
>
> OK. -stable didn't appear to get a copy though?
The point is that as those host bridges only support PCIE with no AGP port, our
AGP driver shouldn't act. And by another side it can fix possible mystery problems
(like Carlo's P965) when our AGP driver does act then.