Re: Any successful installs on a Broadcom HT1000 chipset?
Josh Paetzel
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Wednesday 21 November 2007 12:24:14 pm Travis Mikalson wrote:
> Freddie Cash wrote:
> > On November 21, 2007 04:26 am Barney Cordoba wrote:
> >> It would be a major
> >> black eye to the project to say "FreeBSD 7 is
> >> released, but BTW, if you have a supermicro or tyan
> >> opteron system it won't work at all".
> >
> > The HT1000 is only 1 of the Opteron chipsets available from Tyan, and
> > it's only available on their 1 socket boards (the Tomcats). The dual-
> > and quad- socket boards either use AMD or AMD+nVidia chipsets (Socket
> > 939/940), or nVidia chipsets (Socket AM2). Out of their entire lineup,
> > the HT1000 makes up maybe 10% of the chipsets used by Tyan.
> >
> > I'd hardly call that a "black eye". And it's only the onboard SATA
> > controller that has issues. Pop in a proper RAID controller, and it's =
no
> > longer an issue.
>
> Hate to sound like a broken record but that's exactly what I did and I
> ran into the same nasty data corruption problem on that controller, too.
> That was a little frustrating.
>
> atapci0@pci0:2:3:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x60811=
1ab
> rev=3D0x09 hdr=3D0x00
> vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> device =3D 'MV88SX6081 8-port SATA II PCI-X Controller'
> class =3D mass storage
> subclass =3D SCSI
>
> I don't want a hardware RAID or a "software RAID" controller, I just
> want normal SATA ports with no RAID so I can use ZFS :)
>
> I find myself much preferring ZFS to any other data management solution
> I have ever used, including 3ware hardware RAID which was my previous
> favorite.
>
> Another thing I haven't tried yet is a 3ware 9500 series PCI-X
> controller in my HT1000 board's PCI-X slot to see if that's also broken
> or if it's just a PCI-X + ata(4) specific problem.
>
> I'll reply with the result of that when I get to trying it out.
>
> >> Someone was complaining 2 years ago that they didn't
> >> have hardware to do the work. Is the FreeBSD project
> >> really so poorly funded that they can't get their
> >> hands on a $150 motherboard for 2 years?
> >
> > Ever considered sending one in? :)
>
> I am considering it. Are any reputable FreeBSD developers interested in
> this problem that could benefit from having the problematic hardware in
> their posession?
I'm in the middle of retiring nearly a dozen supermicro socket AM2 boards w=
ith=20
this chipset. With the SATA controllers in native SATA mode the disks get=
=20
scribbled on horribly. With the SATA controllers in legacy mode FreeBSD=20
detects them as ATA/33 but they seem to hold up a bit better. Under heavy=
=20
I/O load they will stay up for about a week before panicing, although once=
=20
they do panic they double panic and hang solid. I thought I was going dodg=
e=20
swapping platforms by installing 3ware 9550 RAID controllers but I all I=20
managed to do was reduce the panic rate to about once per month per box, so=
=20
there are gremlins that affect more than the onboard SATA I'm afraid. I've=
=20
attempted to work with at least one FreeBSD developer on a fix, but the=20
inability of the boxes to complete a panic, let alone write a crash dump ha=
s=20
made troubleshooting them incredibly painful. (Sometimes they don't even=20
manage to get the entire first line of the panic string on the console) Th=
e=20
fact that they will stand up for days under heavy I/O load doesn't help=20
either. Intermittant problems suck.
=2D-=20
Thanks,
Josh Paetzel
PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB
--nextPart2444793.9LFjqCKKDy
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQBHSPmJJvkB8SevrssRAimQAJ0dOkLs0RYQOA5tWMX2nUd3RZcl4wCeLMGa
IPLAD5upWp99SsYh5o4BlCc=
=ns6o
-----END PGP SIGNATURE-----
--nextPart2444793.9LFjqCKKDy--
Barney Cordoba
--- Freddie Cash <fjw...@gmail.com> wrote:
> On November 21, 2007 04:26 am Barney Cordoba wrote:
> > It would be a major
> > black eye to the project to say "FreeBSD 7 is
> > released, but BTW, if you have a supermicro or
> tyan
> > opteron system it won't work at all".
>
> The HT1000 is only 1 of the Opteron chipsets
> available from Tyan, and it's
> only available on their 1 socket boards (the
> Tomcats). The dual- and
> quad- socket boards either use AMD or AMD+nVidia
> chipsets (Socket
> 939/940), or nVidia chipsets (Socket AM2). Out of
> their entire lineup,
> the HT1000 makes up maybe 10% of the chipsets used
> by Tyan.
>
> I'd hardly call that a "black eye". And it's only
> the onboard SATA
> controller that has issues. Pop in a proper RAID
> controller, and it's no
> longer an issue.
>
There are a lot more single socket systems in the
field, so maybe its 10 % of their product line, but a
lot more than that in number of products sold.
Supermicro is a more important brand. They supply to
many large OEMs, including DELL. Dell's opteron
servers use the HT1000 chipset.
So chomp on them apples. Maybe 2 black eyes.
Barney
> > Someone was complaining 2 years ago that they
> didn't
> > have hardware to do the work. Is the FreeBSD
> project
> > really so poorly funded that they can't get their
> > hands on a $150 motherboard for 2 years?
>
> Ever considered sending one in? :)
____________________________________________________________________________________
Be a better sports nut! Let your teams follow you
with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
J. Martin Petersen
> Supermicro is a more important brand. They supply to
> many large OEMs, including DELL. Dell's opteron
> servers use the HT1000 chipset.
Just as a data point I'll note that HP uses them as well. For instance
the Proliant DL145 G3 (which is dual socket, dual core Opteron) comes
with HT1000 as the onboard SATA controller (unless you go for hot swap
SATA, I think) and something similar as the PATA controller (and the
cd/dvd-rom drive isn't detected).
(What we have tested is the following: FreeBSD {6.2-RELEASE, 7.0-BETA2}
installed on /dev/ad4, create one big partition on /dev/ad6 (both 250 GB
disks), newfs, mount then dd if=/dev/zero of=/mnt/foo bs=512k. After a
while the machine panics and the superblock on /dev/ad6 is corrupted. If
I omit newfs/mount, all is apparently well.)
Oh, if a committer needs remote access (ssh, remote kvm) to such a
machine just send me an email and I'll set it up. Likewise if there's
any patches to be tested or info to be gathered.
/Martin
Søren Schmidt
> At 07:26 AM 11/21/2007, Barney Cordoba wrote:
>> I've done a bit of research and it seems that this
>> chipset has been ignored for years now by the FreeBSD
>> team. Whats the reasoning for a major chipset used by
>
> I think you are jumping to conclusions. I have a HT1000 chipset board =
> and have been using it just fine for some time.=20
> (http://lists.freebsd.org/pipermail/freebsd-current/2007-November/07992=
0.html)=20
>
> There obviously are some cases were it does not, so its harder to=20
> track down than just a case of spending $150. If you do have such a=20
> board that does not work, perhaps make the offer of sending the=20
> problem board to a developer who is interested in fixing the issue.
That would be an excelent idea :)
As usual I'll try to get any ATA/SATA HW that shows up on my doorstep=20
working, thats the deal.
I dont have the means nor the motivation to spend my own hard earned $$=20
on all kinds of HW to get someone out there free support, simple as that.=
=2E
That said, I do have a HT1000 based board around a supermicro H8SSL that =
is used as a busy local fileserver, needless to say it works flawlessly.
So, to get this worked on and hopefully fixed, get me a failing board to =
work on here... private mail with address details etc can be had on=20
request...
-S=F8ren
Barney Cordoba
--- Søren Schmidt <s...@freebsd.org> wrote:
> Mike Tancsa wrote:
> > At 07:26 AM 11/21/2007, Barney Cordoba wrote:
> >> I've done a bit of research and it seems that
> this
> >> chipset has been ignored for years now by the
> FreeBSD
> >> team. Whats the reasoning for a major chipset
> used by
> >
> > I think you are jumping to conclusions. I have a
> HT1000 chipset board
> > and have been using it just fine for some time.
> >
>
(http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079920.html)
>
> >
> > There obviously are some cases were it does not,
> so its harder to
> > track down than just a case of spending $150. If
> you do have such a
> > board that does not work, perhaps make the offer
> of sending the
> > problem board to a developer who is interested in
> fixing the issue.
> That would be an excelent idea :)
>
> As usual I'll try to get any ATA/SATA HW that shows
> up on my doorstep
> working, thats the deal.
> I dont have the means nor the motivation to spend my
> own hard earned $$
> on all kinds of HW to get someone out there free
> support, simple as that..
>
> That said, I do have a HT1000 based board around a
> supermicro H8SSL that
> is used as a busy local fileserver, needless to say
> it works flawlessly.
>
> So, to get this worked on and hopefully fixed, get
> me a failing board to
> work on here... private mail with address details
> etc can be had on
> request...
>
> -Søren
>
Is your busy file server running 7.0, and is it
running in SATA mode? The MBs we've tried are H8SSP-i
and an H8SSL-i, both with the same, unsuccessful
results: bad file reads, signals when trying to run
apps, crash-and-burn on buildworld wthin 5 seconds.
Something happened between 6.2 and 7.0, as we were
able to run 6.2 on these systems.
Barney
____________________________________________________________________________________
Be a better sports nut! Let your teams follow you
with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
Barney Cordoba
--- Mike Tancsa <mi...@sentex.net> wrote:
> At 07:26 AM 11/21/2007, Barney Cordoba wrote:
> >I've done a bit of research and it seems that this
> >chipset has been ignored for years now by the
> FreeBSD
> >team. Whats the reasoning for a major chipset used
> by
>
> I think you are jumping to conclusions. I have a
> HT1000 chipset
> board and have been using it just fine for some
> time.
>
(http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079920.html)
> There obviously are some cases were it does not, so
> its harder to
> track down than just a case of spending $150. If
> you do have such a
> board that does not work, perhaps make the offer of
> sending the
> problem board to a developer who is interested in
> fixing the issue.
>
> ---Mike
Hello Mike,
It "works" in 6.x, albeit not in SATA mode, which kind
of detracts from using a really, really fast SATA
chipset. FreeBSD 7 doesn't work at all on the chipset
in any mode that can be set in the bios. You just get
signal 11s all over the place, bad file reads, etc.
Mike Tancsa
>(http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079920.html)
> > There obviously are some cases were it does not, so
> > its harder to
> > track down than just a case of spending $150. If
> > you do have such a
> > board that does not work, perhaps make the offer of
> > sending the
> > problem board to a developer who is interested in
> > fixing the issue.
> >
> > ---Mike
>
>
>Hello Mike,
>
>It "works" in 6.x, albeit not in SATA mode, which kind
>of detracts from using a really, really fast SATA
>chipset. FreeBSD 7 doesn't work at all on the chipset
>in any mode that can be set in the bios. You just get
>signal 11s all over the place, bad file reads, etc.
Hi,
I thought thats what I was using ?
# atacontrol info ata2
Master: ad4 <ST380811AS/3.AAE> Serial ATA II
Slave: no device present
# atacontrol cap ad4
Protocol Serial ATA II
device model ST380811AS
serial number 6PS0C1LW
firmware revision 3.AAE
cylinders 16383
heads 16
sectors/track 63
lba supported 156301488 sectors
lba48 supported 156301488 sectors
dma supported
overlap not supported
Feature Support Enable Value Vendor
write cache yes yes
read ahead yes yes
Native Command Queuing (NCQ) yes - 31/0x1F
Tagged Command Queuing (TCQ) no no 31/0x1F
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management no no 65278/0xFEFE
automatic acoustic management no no 0/0x00 208/0xD0
# grep HT /var/run/dmesg.boot
atapci0: <ServerWorks HT1000 SATA150 controller> port
0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb81f
mem 0xff3fe000-0xff3fffff irq 11 at device 14.0 on pci1
atapci1: <ServerWorks HT1000 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0
6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #1: Thu Oct 25 21:54:13 EDT 2007
Barney Cordoba
--- Mike Tancsa <mi...@sentex.net> wrote:
Ah, we tested an early 6.2 and it didn't come up in
SATA mode. Well thats promising. If we can just figure
out what's wrong with 7 now. Hopefully Soren can
figure out what might have changed.
Barney
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Søren Schmidt
> --- S=F8ren Schmidt <s...@freebsd.org> wrote:
>
> =20
>> Mike Tancsa wrote:
>> =20
>>> At 07:26 AM 11/21/2007, Barney Cordoba wrote:
>>>> I've done a bit of research and it seems that
>> this
>> =20
>>>> chipset has been ignored for years now by the
>> FreeBSD
>> =20
>>>> team. Whats the reasoning for a major chipset
>> used by
>> =20
>>> I think you are jumping to conclusions. I have a
>> HT1000 chipset board=20
>> =20
>>> and have been using it just fine for some time.=20
>>>
>>> =20
> (http://lists.freebsd.org/pipermail/freebsd-current/2007-November/07992=
0.html)
> =20
>>> There obviously are some cases were it does not,
>> so its harder to=20
>> =20
>>> track down than just a case of spending $150. If
>> you do have such a=20
>>> board that does not work, perhaps make the offer
>> of sending the=20
>> =20
>>> problem board to a developer who is interested in
>> fixing the issue.
>> That would be an excelent idea :)
>>
>> As usual I'll try to get any ATA/SATA HW that shows
>> working, thats the deal.
>> I dont have the means nor the motivation to spend my
>> on all kinds of HW to get someone out there free
>> support, simple as that..
>>
>> That said, I do have a HT1000 based board around a
>> is used as a busy local fileserver, needless to say
>> it works flawlessly.
>>
>> So, to get this worked on and hopefully fixed, get
>> work on here... private mail with address details
>> request...
>>
>> -S=F8ren
>>
>> =20
>
> Is your busy file server running 7.0, and is it
> running in SATA mode? The MBs we've tried are H8SSP-i
> and an H8SSL-i, both with the same, unsuccessful
> results: bad file reads, signals when trying to run
> apps, crash-and-burn on buildworld wthin 5 seconds.
This server has been running -current all the time with about biweekly=20
updates, so it has made the transition all the way from about 6.1 to=20
todays current without problems.
> Something happened between 6.2 and 7.0, as we were
> able to run 6.2 on these systems.
>
Looks like a pattern, something outside of ATA also caused HW issues on=20
some Promise controllers to appear in this period.
Just checked and nothing in ATA changed in regards to either the HT1000=20
or the Promise HW, its the same support code thats been there all the tim=
e.
It could be a sideeffect of now having more fine grained locking etc,=20
that makes these problems show up, your guess is as good as mine.
Again, the sticky point is that if I cant reproduce a problem here its=20
very hard to work on it, if not just plain impossible...
-S=F8ren
Barney Cordoba
--- Søren Schmidt <s...@deepcore.dk> wrote:
> Barney Cordoba wrote:
> > --- Søren Schmidt <s...@freebsd.org> wrote:
> >
> >
> >> Mike Tancsa wrote:
> >>
> >>> At 07:26 AM 11/21/2007, Barney Cordoba wrote:
> >>>
> >>>> I've done a bit of research and it seems that
> >>>>
> >> this
> >>
> >>>> chipset has been ignored for years now by the
> >>>>
> >> FreeBSD
> >>
> >>>> team. Whats the reasoning for a major chipset
> >>>>
> >> used by
> >>
> >>> I think you are jumping to conclusions. I have
> a
> >>>
> >> HT1000 chipset board
> >>
> >>> and have been using it just fine for some time.
> >>>
> >>>
> >
>
(http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079920.html)
> >
> >>> There obviously are some cases were it does not,
> >>>
> >> so its harder to
> >>
> >>> track down than just a case of spending $150.
> If
> >>>
> >> you do have such a
> >>
> >>> board that does not work, perhaps make the offer
> >>>
> >> of sending the
> >>
> >>> problem board to a developer who is interested
> in
> >>>
> >> fixing the issue.
> >> That would be an excelent idea :)
> >>
> >> As usual I'll try to get any ATA/SATA HW that
> shows
> >> up on my doorstep
> >> working, thats the deal.
> >> I dont have the means nor the motivation to spend
> my
> >> own hard earned $$
> >> on all kinds of HW to get someone out there free
> >> support, simple as that..
> >>
> >> That said, I do have a HT1000 based board around
> a
> >> supermicro H8SSL that
> >> is used as a busy local fileserver, needless to
> say
> >> it works flawlessly.
> >>
> >> So, to get this worked on and hopefully fixed,
> get
> >> me a failing board to
> >> work on here... private mail with address details
> >> etc can be had on
> >> request...
> >>
> >> -Søren
> >>
> >>
> >
> > Is your busy file server running 7.0, and is it
> > running in SATA mode? The MBs we've tried are
> H8SSP-i
> > and an H8SSL-i, both with the same, unsuccessful
> > results: bad file reads, signals when trying to
> run
> > apps, crash-and-burn on buildworld wthin 5
> seconds.
> >
> This server has been running -current all the time
> with about biweekly
> updates, so it has made the transition all the way
> from about 6.1 to
> todays current without problems.
> > Something happened between 6.2 and 7.0, as we were
> > able to run 6.2 on these systems.
> >
> >
> Looks like a pattern, something outside of ATA also
> caused HW issues on
> some Promise controllers to appear in this period.
> Just checked and nothing in ATA changed in regards
> to either the HT1000
> or the Promise HW, its the same support code thats
> been there all the time.
> It could be a sideeffect of now having more fine
> grained locking etc,
> that makes these problems show up, your guess is as
> good as mine.
>
> Again, the sticky point is that if I cant reproduce
> a problem here its
> very hard to work on it, if not just plain
> impossible...
A sticky point on this end is that it will cost more
to ship you a system than the cost of the product; you
being in Europe and the US dollar sucking in general.
I'm also not going to be able to get authorization to
ship overseas.
Could you send me the config file you're using on your
7.0 system with the H8SSL MB so I can give it a try
and see if its a config issue, or some device
conflict? You have the MB we're having trouble with,
so maybe we can learn enough to give you some ideas.I
have a system with an H8SSL-i that just plain doesn't
work with either SATA or IDE.
Barney
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
'Kockac' Matej Kubik
> Looks like a pattern, something outside of ATA also caused HW issues on
> some Promise controllers to appear in this period.
older version of 7-current for about 2 months (with frequent reboots)
and no sign of file corruption. (Newer versions are usually not able to
run at even /bin/sh on my system.) I'm able to pinpoint the exact patch
that causes these problems _for me_ - it's a VM patch (new physical
memory allocator) from June the 16th.
Unfortunately I can neither grant access to the machine for debugging nor
send in another board (I only have one) but I can provide debugging
information or test something...
By the way, I think it would be interesting to know if others do have
the problems even with older -current.
Matej Kubik
Travis Mikalson
> Mike Tancsa wrote:
>> At 07:26 AM 11/21/2007, Barney Cordoba wrote:
>>> I've done a bit of research and it seems that this
>>> chipset has been ignored for years now by the FreeBSD
>>> team. Whats the reasoning for a major chipset used by
>>
>> I think you are jumping to conclusions. I have a HT1000 chipset board
>> and have been using it just fine for some time.
>> (http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079920.html)
>>
>> There obviously are some cases were it does not, so its harder to
>> track down than just a case of spending $150. If you do have such a
>> board that does not work, perhaps make the offer of sending the
>> problem board to a developer who is interested in fixing the issue.
> That would be an excelent idea :)
>
> As usual I'll try to get any ATA/SATA HW that shows up on my doorstep
> working, thats the deal.
> I dont have the means nor the motivation to spend my own hard earned $$
> on all kinds of HW to get someone out there free support, simple as that..
>
> That said, I do have a HT1000 based board around a supermicro H8SSL that
> is used as a busy local fileserver, needless to say it works flawlessly.
>
> So, to get this worked on and hopefully fixed, get me a failing board to
> work on here... private mail with address details etc can be had on
> request...
>
Sřren,
Ok, I'm in for sending you some hardware so you can figure this out.
But, I'll need your advice on getting this hardware to you with us being
in different countries as well as your address and all that.
Please reply to me privately and take the rest of this conversation
off-list so we can figure it out.
Thanks!
-T
--
TerraNovaNet Internet Services - Key Largo, FL
Voice: (305)453-4011 x101 Fax: (305)451-5991
http://www.terranova.net/
----------------------------------------------
Life's not fair, but the root password helps.
Søren Schmidt
--------------070405020906020403010607
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Barney Cordoba wrote:
> S=F8ren Schmidt wrote:
>> This server has been running -current all the time
>> with about biweekly=20
>> updates, so it has made the transition all the way
>> from about 6.1 to=20
>> todays current without problems.
>> =20
>>> Something happened between 6.2 and 7.0, as we were
>>> able to run 6.2 on these systems.
>>>
>>> =20
>>> =20
>> Looks like a pattern, something outside of ATA also
>> caused HW issues on=20
>> some Promise controllers to appear in this period.
>> Just checked and nothing in ATA changed in regards
>> to either the HT1000=20
>> or the Promise HW, its the same support code thats
>> been there all the time.
>> It could be a sideeffect of now having more fine
>> grained locking etc,=20
>> that makes these problems show up, your guess is as
>> good as mine.
>>
>> Again, the sticky point is that if I cant reproduce
>> a problem here its=20
>> very hard to work on it, if not just plain
>> impossible...
>> =20
>
> A sticky point on this end is that it will cost more
> to ship you a system than the cost of the product; you
> being in Europe and the US dollar sucking in general.
> I'm also not going to be able to get authorization to
> ship overseas.=20
>
> =20
Maybe I can get the HW over here, paypal can be used to transfer the=20
funds in that case...
> Could you send me the config file you're using on your
> 7.0 system with the H8SSL MB so I can give it a try
> and see if its a config issue, or some device
> conflict? You have the MB we're having trouble with,
> so maybe we can learn enough to give you some ideas.I
> have a system with an H8SSL-i that just plain doesn't
> work with either SATA or IDE.
> =20
Sure find my config attached currently used with plain releng_7.
It might be worth while to compare HW revisions etc as well as there=20
might be differences.
One thing you could try would be to install a 6.2 system and if that=20
still works just grap ATA from releng_6 as that is now the same as in=20
-current and should fit almost cleanly into 6.2 as is, then give that a=20
run. Depending on the outcome we'll know more about where to look for=20
the problem.
For references sake could we please get a list of the actual HW that=20
people have problems with listed here, as detailed as possible please.
-S=F8ren
--------------070405020906020403010607
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
name="DEEPCORE"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="DEEPCORE"
machine i386
cpu I686_CPU
ident DEEPCORE
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
makeoptions MODULES_OVERRIDE=""
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B realtime extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options ADAPTIVE_GIANT # Giant mutex is adaptive.
# Firewall stuff.
options IPFIREWALL
options IPFIREWALL_FORWARD
options IPDIVERT
options DUMMYNET
# Basic HW infrastructure support.
device apic # I/O APIC
device acpi # ACPI support
# Bus support.
device pci
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
device atausb # USB device support
#options ATA_STATIC_ID # Static device numbering
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
device kbdmux # keyboard multiplexer
# syscons is the default console driver, resembling an SCO console
device sc
device splash # Splash screen and screen saver support
device vga # VGA video card driver
device agp # support several AGP chipsets
# Add suspend/resume support for the i8254.
device pmtimer
# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports
# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
device bge # Broadcom BCM570xx Gigabit Ethernet
device de # DEC/Intel DC21x4x (``Tulip'')
# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device gif # IPv6 and IPv4 tunneling
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device bpf # Berkeley packet filter
# USB support
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
#device udbp # USB Double Bulk Pipe devices
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device ums # Mouse
--------------070405020906020403010607
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
--------------070405020906020403010607--
John Baldwin
> For references sake could we please get a list of the actual HW that=20
=46YI, I've seen weird in-memory corruption with machines with the HT1000_S=
1=20
atapci device. In all the cases I've seen so far, a single page is corrupt=
ed=20
with garbage and the page happens to be used by UMA to hold credentials=20
including proc0's credentials. I've seen this corruption (trashed creds fo=
r=20
proc0 and other creds in that page) on many of the same boxes (Dell 1435's=
=20
IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKSMIO=20
rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux driver=
=20
uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests on tha=
t.
=2D-=20
John Baldwin
John Baldwin
Barney Cordoba
--- Søren Schmidt <s...@deepcore.dk> wrote:
> Barney Cordoba wrote:
> > Søren Schmidt wrote:
> >> This server has been running -current all the
> time
> >> with about biweekly
> >> updates, so it has made the transition all the
> way
> >> from about 6.1 to
> >> todays current without problems.
> >>
> >>> Something happened between 6.2 and 7.0, as we
> were
> >>> able to run 6.2 on these systems.
> >>>
> >>>
> >>>
> >> Looks like a pattern, something outside of ATA
> also
> >> caused HW issues on
> >> some Promise controllers to appear in this
> period.
> >> Just checked and nothing in ATA changed in
> regards
> >> to either the HT1000
> >> or the Promise HW, its the same support code
> thats
> >> been there all the time.
> >> It could be a sideeffect of now having more fine
> >> grained locking etc,
> >> that makes these problems show up, your guess is
> as
> >> good as mine.
> >>
> >> Again, the sticky point is that if I cant
> reproduce
> >> a problem here its
> >> very hard to work on it, if not just plain
> >> impossible...
> >>
> >
> > A sticky point on this end is that it will cost
> more
> > to ship you a system than the cost of the product;
> you
> > being in Europe and the US dollar sucking in
> general.
> > I'm also not going to be able to get authorization
> to
> > ship overseas.
> >
> >
> Maybe I can get the HW over here, paypal can be used
> to transfer the
> funds in that case...
> > Could you send me the config file you're using on
> your
> > 7.0 system with the H8SSL MB so I can give it a
> try
> > and see if its a config issue, or some device
> > conflict? You have the MB we're having trouble
> with,
> > so maybe we can learn enough to give you some
> ideas.I
> > have a system with an H8SSL-i that just plain
> doesn't
> > work with either SATA or IDE.
> >
> Sure find my config attached currently used with
> plain releng_7.
> It might be worth while to compare HW revisions etc
> as well as there
> might be differences.
> One thing you could try would be to install a 6.2
> system and if that
> still works just grap ATA from releng_6 as that is
> now the same as in
> -current and should fit almost cleanly into 6.2 as
> is, then give that a
> run. Depending on the outcome we'll know more about
> where to look for
> the problem.
>
> For references sake could we please get a list of
> the actual HW that
> people have problems with listed here, as detailed
> as possible please.
>
> -Søren
> > _______________________________________________
This is the HW info on the MBs we've tested. Both of
them run fine on 6.2 and both don't work at all in any
mode on 7.0. We've tried the 6.2 code in the 7.0
system, with the same problem. So it doesn't appear to
be the ATA code specifically.
Opteron / HT1000 details:
http://www.supermicro.com/Aplus/motherboard/Opteron1000/HT1000/H8SSL-i2.cfm
Supermicro H8SSL-i2 Opteron 1000-series AM2
Motherboard with:
AMD Opteron 1222 3.0GHz Dual-Core CPU (running UP)
2x512MB Corsair DDR2 PC2-4200
http://www.supermicro.com/Aplus/motherboard/Opteron/HT2000/H8SSP-i.cfm
Supermicro H8SSP-i Opteron 200-series Motherboard
with:
AMD Opteron 244 1.8GHz CPU
2x512MB Corsair PC3200 Registered DDR
Barney
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Søren Schmidt
>
> FYI, I've seen weird in-memory corruption with machines with the HT1000=
_S1=20
> atapci device. In all the cases I've seen so far, a single page is cor=
rupted=20
> with garbage and the page happens to be used by UMA to hold credentials=
=20
s for=20
> proc0 and other creds in that page) on many of the same boxes (Dell 143=
5's=20
> IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKSMI=
O=20
> rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux dr=
iver=20
> uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests on=
that.
>
> =20
OK, seems the chipset has some real problems, I have digged through all=20
the (very little) docs and info I got from serverworks back when, and=20
the only thing I can find is that the chips doesn't support MSI in any=20
shape or fashion or it will do really strange things.
Now on my system it seems to be disabled but I'm not sure yet how its=20
determined to be that way. Would be worth for you guys to check what the =
sysctl's "hw.pci.enable_msi" and "hw.pci.enable_msix" are set to.
I havn't looked into this yet, but I'm pretty sure we added MSI support=20
in the 6.2 -> 7.0 timeframe, so that might have uncovered this chipset=20
bug, and possibly the Promise data corruption one as well.
-S=F8ren
Søren Schmidt
Barney Cordoba
--- Søren Schmidt <s...@deepcore.dk> wrote:
> John Baldwin wrote:
> >
> > FYI, I've seen weird in-memory corruption with
> machines with the HT1000_S1
> > atapci device. In all the cases I've seen so far,
> a single page is corrupted
> > with garbage and the page happens to be used by
> UMA to hold credentials
> > including proc0's credentials. I've seen this
> corruption (trashed creds for
> > proc0 and other creds in that page) on many of the
> same boxes (Dell 1435's
> > IIRC) running on 6.2. I've tried switching the
> HT1000_S1 to use SWKSMIO
> > rather SWKS100 as I mentioned to you in an earlier
> e-mail (the Linux driver
> > uses equivalent of SWKSMIO FWIW) but don't have
> any conclusive tests on that.
> >
> >
> OK, seems the chipset has some real problems, I have
> digged through all
> the (very little) docs and info I got from
> serverworks back when, and
> the only thing I can find is that the chips doesn't
> support MSI in any
> shape or fashion or it will do really strange
> things.
> Now on my system it seems to be disabled but I'm not
> sure yet how its
> determined to be that way. Would be worth for you
> guys to check what the
> sysctl's "hw.pci.enable_msi" and
> "hw.pci.enable_msix" are set to.
> I havn't looked into this yet, but I'm pretty sure
> we added MSI support
> in the 6.2 -> 7.0 timeframe, so that might have
> uncovered this chipset
> bug, and possibly the Promise data corruption one as
> well.
>
> -Søren
That was something that was suggested a while ago when
I pointed out the linux disables MSI. It had no effect
in our systems.
Barney
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Barney Cordoba
John Baldwin
> John Baldwin wrote:
> >
_S1=20
> > atapci device. In all the cases I've seen so far, a single page is cor=
rupted=20
> > with garbage and the page happens to be used by UMA to hold credentials=
=20
> > including proc0's credentials. I've seen this corruption (trashed cred=
s for=20
> > proc0 and other creds in that page) on many of the same boxes (Dell 143=
5's=20
> > IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKSMI=
O=20
> > rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux dr=
iver=20
> > uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests on=
that.
> >
> > =20
> OK, seems the chipset has some real problems, I have digged through all=20
> the (very little) docs and info I got from serverworks back when, and=20
> the only thing I can find is that the chips doesn't support MSI in any=20
> shape or fashion or it will do really strange things.
> determined to be that way. Would be worth for you guys to check what the=
=20
> sysctl's "hw.pci.enable_msi" and "hw.pci.enable_msix" are set to.
> in the 6.2 -> 7.0 timeframe, so that might have uncovered this chipset=20
> bug, and possibly the Promise data corruption one as well.
The ata driver doesn't use MSI (no calls to pci_msi_count or pci_msi_alloc,
etc.), so this isn't an issue. Also, the boxes I've seen the corruption on
already have MSI disabled (it's still disabled by default in 6.x).
=2D-=20
John Baldwin
Søren Schmidt
> On Wednesday 28 November 2007 02:45:16 am S=F8ren Schmidt wrote:
>> John Baldwin wrote:
>> =20
>>> FYI, I've seen weird in-memory corruption with machines with the HT10=
00_S1=20
>>> atapci device. In all the cases I've seen so far, a single page is c=
orrupted=20
>>> with garbage and the page happens to be used by UMA to hold credentia=
ls=20
>>> including proc0's credentials. I've seen this corruption (trashed cr=
eds for=20
>>> proc0 and other creds in that page) on many of the same boxes (Dell 1=
435's=20
>>> IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKS=
MIO=20
>>> rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux =
driver=20
>>> uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests =
on that.
>>>
>>> =20
>>> =20
>> OK, seems the chipset has some real problems, I have digged through al=
l=20
>> the (very little) docs and info I got from serverworks back when, and =
>> the only thing I can find is that the chips doesn't support MSI in any=
=20
>> shape or fashion or it will do really strange things.
>> Now on my system it seems to be disabled but I'm not sure yet how its =
>> determined to be that way. Would be worth for you guys to check what t=
he=20
>> sysctl's "hw.pci.enable_msi" and "hw.pci.enable_msix" are set to.
>> I havn't looked into this yet, but I'm pretty sure we added MSI suppor=
t=20
>> in the 6.2 -> 7.0 timeframe, so that might have uncovered this chipset=
=20
>> bug, and possibly the Promise data corruption one as well.
>> =20
>
> The ata driver doesn't use MSI (no calls to pci_msi_count or pci_msi_al=
loc,
> etc.), so this isn't an issue. Also, the boxes I've seen the corruptio=
n on
> already have MSI disabled (it's still disabled by default in 6.x).
> =20
OK, its must be *totally* disabled not just for ATA but for everything=20
on those chipsets or they'll barf all over the place.
If we do that already we need to look into other places.
However, if we are dealing with in-memory corruption this is going to=20
get "interesting"....
Does that also happen if nothing uses DMA ?
-S=F8ren
Søren Schmidt
> On 28.11-08:42, John Baldwin wrote:
> [ ... ]
> =20
>> The ata driver doesn't use MSI (no calls to pci_msi_count or pci_msi_a=
lloc,
>> etc.), so this isn't an issue. Also, the boxes I've seen the corrupti=
on on
>> already have MSI disabled (it's still disabled by default in 6.x).
>> =20
>
> to 7 via BETA install i'm getting DMA errors. i will try to post
> more info when system has some downtime.
>
> can confirm the roll back to 6.2 appears to make things happy again.
> =20
Could you try to take /sys/dev/ata/* from releng_6 and fit it into the=20
6.2 system please ?
Should fit in there without too much trouble, and take ATA alone to=20
R7/-current level.
ttw...@cobbled.net
[ ... ]
> Could you try to take /sys/dev/ata/* from releng_6 and fit it into the
> Should fit in there without too much trouble, and take ATA alone to
will be a little before i'm able but will post as soon as possible.
John Baldwin
> >> the only thing I can find is that the chips doesn't support MSI in any=
=20
> >> shape or fashion or it will do really strange things.
> >> Now on my system it seems to be disabled but I'm not sure yet how its=
> >> determined to be that way. Would be worth for you guys to check what t=
he=20
> >> sysctl's "hw.pci.enable_msi" and "hw.pci.enable_msix" are set to.
> >> I havn't looked into this yet, but I'm pretty sure we added MSI suppor=
t=20
> >> in the 6.2 -> 7.0 timeframe, so that might have uncovered this chipset=
=20
> >> bug, and possibly the Promise data corruption one as well.
> >
> > The ata driver doesn't use MSI (no calls to pci_msi_count or pci_msi_al=
loc,
> > etc.), so this isn't an issue. Also, the boxes I've seen the corruptio=
n on
> > already have MSI disabled (it's still disabled by default in 6.x).
> > =20
> on those chipsets or they'll barf all over the place.
> If we do that already we need to look into other places.
> However, if we are dealing with in-memory corruption this is going to=20
> get "interesting"....
> Does that also happen if nothing uses DMA ?
Again, on the machines I'm seeing this on it was totally disabled. I don't=
think
I can totally disable DMA (NICs etc. must use DMA) on the machines and sinc=
e they
are in production and I only see the corruption as an after-effect when the=
boxes
panic or deadlock for another reason I'm not easily able to reproduce this.=
Also,
we do disable MSI for devices behind HT2000 chipsets because of a chip bug,=
but
not on HT1000 currently. However, MSI isn't on on 6.x anyway.
=2D-=20
John Baldwin
Travis Mikalson
> On Wednesday 28 November 2007 08:51:38 am Søren Schmidt wrote:
>> John Baldwin wrote:
>>>
>>>> John Baldwin wrote:
>>>>
>>>>> atapci device. In all the cases I've seen so far, a single page is corrupted
>>>>> with garbage and the page happens to be used by UMA to hold credentials
>>>>> including proc0's credentials. I've seen this corruption (trashed creds for
>>>>> proc0 and other creds in that page) on many of the same boxes (Dell 1435's
>>>>> IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKSMIO
>>>>> rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux driver
>>>>> uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests on that.
>>>>>
>>>>>
>>>>>
>>>> OK, seems the chipset has some real problems, I have digged through all
>>>> Now on my system it seems to be disabled but I'm not sure yet how its
>>>>
>>> etc.), so this isn't an issue. Also, the boxes I've seen the corruption on
>>> already have MSI disabled (it's still disabled by default in 6.x).
>>>
>> If we do that already we need to look into other places.
>> However, if we are dealing with in-memory corruption this is going to
>> Does that also happen if nothing uses DMA ?
>
> I can totally disable DMA (NICs etc. must use DMA) on the machines and since they
> are in production and I only see the corruption as an after-effect when the boxes
> panic or deadlock for another reason I'm not easily able to reproduce this. Also,
> we do disable MSI for devices behind HT2000 chipsets because of a chip bug, but
> not on HT1000 currently. However, MSI isn't on on 6.x anyway.
It does make sense that the problem with RELENG_7 is a memory corruption
issue, mine just seems to be triggered when I start using my PCI-X ata
devices. At boot random processes will start sig11'ing all over the
place randomly not to mention horrible corruption of my data.
Here's some testing I've just done with various FreeBSD versions on my
HT1000 Tyan S3950 motherboard, all went pretty badly...
Hm I guess we never tried 6.2 on this. It works way worse than 7.0.
All this testing is with a disk attached to the onboard SATA controller,
no Marvell PCI-X controller involved.
7.0-BETA3 amd64 and i386, onboard SATA controller causes massive data
corruption and things sig11 (like init and the "sh" that's running
/etc/rc), but system runs well when you use a SiI3114 4-port SATA 32-bit
PCI card.
6.2-R amd64, wont boot past "Timecounters tick every 1.000 msec" with
ACPI enabled. With ACPI disabled, after "Timecounters tick" it'll spew
stray irq 7, stray irq 7, not logging any more, and then it'll run at a
snail's pace. In 3-4 minutes it didn't manage to finish reading the
mfsroot and start sysinstall so I didn't go any further.
I tried with the SATA controller disabled and with the on-board "em"
NICs disabled, no effect on that problem.
6.3-BETA2 amd64, boots with ACPI enabled, sysinstall console is sluggish
indicating it's having the same problem, it's just not as severe.
Sysinstall almost made it through, but finally failed with a g_vfs_alloc
error while trying to write out the kernel distributions from CD to hard
drive. top was showing interrupt usage at 70%.
I booted that almost-completed 6.3-BETA2 installation up with the SMP
kernel for the hell of it, top showed 35% interrupt usage but ran a
little faster... things sig11'ed and there was massive data corruption
on the disk. fsck (not background fsck) even went crazy and ran out of
swap while trying to fsck /usr, etc. etc.
I tried to boot HEAD from today but unfortunately it hung at the boot
loader and wouldn't boot the kernel, so not much to say on that.
--
TerraNovaNet Internet Services - Key Largo, FL
Voice: (305)453-4011 x101 Fax: (305)451-5991
http://www.terranova.net/
----------------------------------------------
Life's not fair, but the root password helps.
J. Martin Petersen
> For references sake could we please get a list of the actual HW that
> people have problems with listed here, as detailed as possible please.
HP ProLiant DL145 G3 (SKU 411593-421; Dual-Core AMD Opteron 2214 HE, 2
GB memory, added 2x250 GB SATA disks and DVD/CD-rom) running FreeBSD
6.2-RELEASE. BIOS is the most recent, 2007.07.19 A.
pasca# uname -a
FreeBSD pasca.aub.dk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
11:05:30 UTC 2007
ro...@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386
pasca# pciconf -lv
pcib1@pci0:1:0: class=0x060400 card=0x00000090 chip=0x00361166 rev=0x00
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
hostb0@pci0:2:0: class=0x060000 card=0x02011166 chip=0x02051166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = HOST-PCI
atapci1@pci0:2:1: class=0x01018a card=0x320b103c chip=0x02141166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = mass storage
subclass = ATA
isab0@pci0:2:2: class=0x060100 card=0x02301166 chip=0x02341166 rev=0x00
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-ISA
ohci0@pci0:3:0: class=0x0c0310 card=0x320c103c chip=0x02231166 rev=0x01
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
ohci1@pci0:3:1: class=0x0c0310 card=0x320c103c chip=0x02231166 rev=0x01
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
ehci0@pci0:3:2: class=0x0c0320 card=0x320d103c chip=0x02231166 rev=0x01
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
none0@pci0:4:0: class=0x030000 card=0x31fa103c chip=0x0522102b rev=0x02
hdr=0x00
vendor = 'Matrox Electronic Systems Ltd.'
class = display
subclass = VGA
pcib3@pci0:6:0: class=0x060400 card=0x000000a0 chip=0x01401166 rev=0xa2
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
pcib4@pci0:7:0: class=0x060400 card=0x000000a0 chip=0x01421166 rev=0xa2
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
pcib5@pci0:8:0: class=0x060400 card=0x000000a0 chip=0x01441166 rev=0xa2
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
pcib6@pci0:9:0: class=0x060400 card=0x000000a0 chip=0x01421166 rev=0xa2
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
pcib7@pci0:10:0: class=0x060400 card=0x000000a0 chip=0x01441166
rev=0xa2 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
hostb1@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron HyperTransport Technology
Configuration'
class = bridge
subclass = HOST-PCI
hostb2@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron Address Map'
class = bridge
subclass = HOST-PCI
hostb3@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron DRAM Controller'
class = bridge
subclass = HOST-PCI
hostb4@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron Miscellaneous Control'
class = bridge
subclass = HOST-PCI
pcib2@pci1:13:0: class=0x060400 card=0x00000090 chip=0x01041166
rev=0xc0 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
atapci0@pci1:14:0: class=0x010405 card=0x320b103c chip=0x024a1166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = mass storage
subclass = RAID
pcib8@pci7:0:0: class=0x060400 card=0x00000060 chip=0x01031166 rev=0xb5
hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
bge0@pci8:4:0: class=0x020000 card=0x703e103c chip=0x167814e4 rev=0xa3
hdr=0x00
vendor = 'Broadcom Corporation'
class = network
subclass = ethernet
bge1@pci8:4:1: class=0x020000 card=0x703e103c chip=0x167814e4 rev=0xa3
hdr=0x00
vendor = 'Broadcom Corporation'
class = network
subclass = ethernet
Verbose boot:
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007
ro...@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0b63000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0b631b0.
Calibrating clock(s) ... i8254 clock: 1193173 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2194516692 Hz
CPU: Dual-Core AMD Opteron(tm) Processor 2214 HE (2194.52-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x40f12 Stepping = 2
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x2001<SSE3,CX16>
AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow>
AMD Features2=0x1f<LAHF,CMP,<b2>,<b3>,CR8>
HTT bit cleared - FreeBSD does not have licensing issues requiring it.
Cores per package: 2
Data TLB: 32 entries, fully associative
Instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way
associative
L2 internal cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 8-way
associative
real memory = 2146828288 (2047 MB)
Physical memory chunk(s):
0x0000000000001000 - 0x000000000009cfff, 638976 bytes (156 pages)
0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages)
0x0000000000c28000 - 0x000000007db12fff, 2096017408 bytes (511723 pages)
avail memory = 2095714304 (1998 MB)
MP Configuration Table version 1.4 found at 0xc009e271
Table 'FACP' at 0x7ff62b89
Table 'SPMI' at 0x7ff66b97
Table 'SSDT' at 0x7ff66bd7
Table 'SRAT' at 0x7ff66ddd
Table 'HPET' at 0x7ff66e7d
Table 'SSDT' at 0x7ff66eb5
Table 'MCFG' at 0x7ff66efe
Table 'SPCR' at 0x7ff66f3a
Table 'APIC' at 0x7ff66f8a
MADT: Found table at 0x7ff66f8a
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 1: enabled
SMP: Added CPU 1 (AP)
INTR: Adding local APIC 0 as a target
ACPI APIC Table: <PTLTD APIC >
INTR: Adding local APIC 1 as a target
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
bios32: Found BIOS32 Service Directory header at 0xc00f8540
bios32: Entry = 0xfd7ae (c00fd7ae) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xfd730+0x44
pnpbios: Found PnP BIOS data at 0xc00f8590
pnpbios: Entry = e65f:845a Rev = 1.0
Other BIOS signatures found:
APIC: CPU 0 has ACPI ID 0
APIC: CPU 1 has ACPI ID 1
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000
ioapic0: Routing external 8259A's -> intpin 0
ioapic0: intpin 0 -> ExtINT (edge, high)
ioapic0: intpin 1 -> ISA IRQ 1 (edge, high)
ioapic0: intpin 2 -> ISA IRQ 2 (edge, high)
ioapic0: intpin 3 -> ISA IRQ 3 (edge, high)
ioapic0: intpin 4 -> ISA IRQ 4 (edge, high)
ioapic0: intpin 5 -> ISA IRQ 5 (edge, high)
ioapic0: intpin 6 -> ISA IRQ 6 (edge, high)
ioapic0: intpin 7 -> ISA IRQ 7 (edge, high)
ioapic0: intpin 8 -> ISA IRQ 8 (edge, high)
ioapic0: intpin 9 -> ISA IRQ 9 (edge, high)
ioapic0: intpin 10 -> ISA IRQ 10 (edge, high)
ioapic0: intpin 11 -> ISA IRQ 11 (edge, high)
ioapic0: intpin 12 -> ISA IRQ 12 (edge, high)
ioapic0: intpin 13 -> ISA IRQ 13 (edge, high)
ioapic0: intpin 14 -> ISA IRQ 14 (edge, high)
ioapic0: intpin 15 -> ISA IRQ 15 (edge, high)
MADT: Found IO APIC ID 3, Interrupt 16 at 0xfec01000
ioapic1: intpin 0 -> PCI IRQ 16 (level, low)
ioapic1: intpin 1 -> PCI IRQ 17 (level, low)
ioapic1: intpin 2 -> PCI IRQ 18 (level, low)
ioapic1: intpin 3 -> PCI IRQ 19 (level, low)
ioapic1: intpin 4 -> PCI IRQ 20 (level, low)
ioapic1: intpin 5 -> PCI IRQ 21 (level, low)
ioapic1: intpin 6 -> PCI IRQ 22 (level, low)
ioapic1: intpin 7 -> PCI IRQ 23 (level, low)
ioapic1: intpin 8 -> PCI IRQ 24 (level, low)
ioapic1: intpin 9 -> PCI IRQ 25 (level, low)
ioapic1: intpin 10 -> PCI IRQ 26 (level, low)
ioapic1: intpin 11 -> PCI IRQ 27 (level, low)
ioapic1: intpin 12 -> PCI IRQ 28 (level, low)
ioapic1: intpin 13 -> PCI IRQ 29 (level, low)
ioapic1: intpin 14 -> PCI IRQ 30 (level, low)
ioapic1: intpin 15 -> PCI IRQ 31 (level, low)
MADT: Found IO APIC ID 4, Interrupt 32 at 0xfec02000
ioapic2: intpin 0 -> PCI IRQ 32 (level, low)
ioapic2: intpin 1 -> PCI IRQ 33 (level, low)
ioapic2: intpin 2 -> PCI IRQ 34 (level, low)
ioapic2: intpin 3 -> PCI IRQ 35 (level, low)
ioapic2: intpin 4 -> PCI IRQ 36 (level, low)
ioapic2: intpin 5 -> PCI IRQ 37 (level, low)
ioapic2: intpin 6 -> PCI IRQ 38 (level, low)
ioapic2: intpin 7 -> PCI IRQ 39 (level, low)
ioapic2: intpin 8 -> PCI IRQ 40 (level, low)
ioapic2: intpin 9 -> PCI IRQ 41 (level, low)
ioapic2: intpin 10 -> PCI IRQ 42 (level, low)
ioapic2: intpin 11 -> PCI IRQ 43 (level, low)
ioapic2: intpin 12 -> PCI IRQ 44 (level, low)
ioapic2: intpin 13 -> PCI IRQ 45 (level, low)
ioapic2: intpin 14 -> PCI IRQ 46 (level, low)
ioapic2: intpin 15 -> PCI IRQ 47 (level, low)
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
ioapic0: intpin 2 trigger: edge
ioapic0: intpin 2 polarity: high
lapic0: Routing NMI -> LINT1
lapic0: LINT1 trigger: edge
lapic0: LINT1 polarity: high
lapic1: Routing NMI -> LINT1
lapic1: LINT1 trigger: edge
lapic1: LINT1 polarity: high
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0: intpin 9 polarity: low
ioapic0: intpin 9 trigger: level
ioapic0 <Version 1.1> irqs 0-15 on motherboard
ioapic1 <Version 1.1> irqs 16-31 on motherboard
ioapic2 <Version 1.1> irqs 32-47 on motherboard
cpu0 BSP:
ID: 0x00000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
wlan: <802.11 Link Layer>
ath_rate: version 1.2 <SampleRate bit-rate selection algorithm>
null: <null device, zero device>
random: <entropy source, Software, Yarrow>
nfslock: pseudo-device
io: <I/O>
kbd: new array size 4
kbd1 at kbdmux0
mem: <memory>
Pentium Pro MTRR support enabled
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
rr232x: RocketRAID 232x controller driver v1.02 (Jan 12 2007 11:05:04)
npx0: INT 16 interface
acpi0: <PTLTD XSDT> on motherboard
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
pci_open(1): mode 1 addr port (0x0cf8) is 0x80016804
pci_open(1a): mode1res=0x80000000 (0x80000000)
pci_cfgcheck: device 0 1 [class=060400] [hdr=01] is there (id=00361166)
pcibios: BIOS version 2.10
Found $PIR table, 19 entries at 0xc00fde90
PCI-Only Interrupts: none
Location Bus Device Pin Link IRQs
embedded 0 3 A 0x02 10
embedded 0 4 A 0x18 3 5 7 11
embedded 1 14 A 0x08 5 7
slot 3 2 1 A 0x11 3 5 7 11
slot 3 2 1 B 0x12 3 5 7 11
slot 3 2 1 C 0x13 3 5 7 11
slot 3 2 1 D 0x14 3 5 7 11
embedded 0 6 A 0x2f 3 5 7 11
slot 1 3 0 A 0x21 3 5 7 11
slot 1 3 0 B 0x21 3 5 7 11
slot 1 3 0 C 0x21 3 5 7 11
slot 1 3 0 D 0x21 3 5 7 11
embedded 0 7 A 0x2f 3 5 7 11
embedded 0 8 A 0x2f 3 5 7 11
embedded 0 9 A 0x2f 3 5 7 11
slot 2 6 0 A 0x24 3 5 7 11
slot 2 6 0 B 0x24 3 5 7 11
slot 2 6 0 C 0x24 3 5 7 11
slot 2 6 0 D 0x24 3 5 7 11
embedded 0 10 A 0x2f 3 5 7 11
embedded 8 4 A 0x25 3 5 7 11
embedded 8 4 B 0x25 3 5 7 11
slot 4 16 1 A 0x28 15
slot 4 16 1 B 0x28 15
slot 4 16 1 C 0x28 15
slot 4 16 1 D 0x28 15
acpi_bus_number: root bus has no _BBN, assuming 0
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
AcpiOsDerivePciId: bus 0 dev 24 func 1
acpi0: Power Button (fixed)
acpi0: wakeup code va 0xda389000 pa 0x9c000
acpi_bus_number: root bus has no _BBN, assuming 0
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
AcpiOsDerivePciId: bus 0 dev 6 func 0
unknown: I/O range not supported
ACPI timer: 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 -> 0
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
pci_link0: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 10 N 0 10 11
pci_link0: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 10 N 0 10 11
pci_link0: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 10 11
pci_link1: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 10 11
pci_link1: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 10 11
pci_link1: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 10 11
pci_link2: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 7 N 0 5 7 11
pci_link2: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 7 N 0 5 7 11
pci_link2: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 5 7 11
pci_link3: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link3: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link3: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link4: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link4: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link4: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link5: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link5: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link5: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link6: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link6: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link6: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link7: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link7: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link7: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link8: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link8: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link8: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link9: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link9: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link9: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link10: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 5 N 0 3 4 5 7 11 12 14 15
pci_link10: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 5 N 0 3 4 5 7 11 12 14 15
pci_link10: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link11: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link11: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link11: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link12: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link12: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link12: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link13: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link13: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link13: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link14: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link14: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link14: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link15: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link15: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link15: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link16: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link16: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link16: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link17: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link17: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link17: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link18: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link18: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link18: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link19: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link19: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link19: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link20: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link20: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link20: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link21: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link21: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link21: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link22: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link22: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link22: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link23: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 5 N 0 3 4 5 7 11 12 14 15
pci_link23: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 5 N 0 3 4 5 7 11 12 14 15
pci_link23: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link24: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link24: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link24: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link25: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link25: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link25: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link26: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link26: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link26: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link27: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link27: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link27: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link28: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link28: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link28: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link29: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link29: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link29: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link30: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link30: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link30: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link31: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link31: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link31: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link32: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link32: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link32: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link33: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 11 N 0 3 4 5 7 11 12 14 15
pci_link33: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 11 N 0 3 4 5 7 11 12 14 15
pci_link33: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link34: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link34: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
pci_link34: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 7 11 12 14 15
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> on acpi0
ACPI: Found matching pin for 0.3.INTA at func 0: 10
pci0: <ACPI PCI bus> on pcib0
pci0: physical bus=0
found-> vendor=0x1166, dev=0x0036, revid=0x00
bus=0, slot=1, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1166, dev=0x0205, revid=0x00
bus=0, slot=2, func=0
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0147, statreg=0x0200, cachelnsz=0 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1166, dev=0x0214, revid=0x00
bus=0, slot=2, func=1
class=01-01-8a, hdrtype=0x00, mfdev=1
cmdreg=0x0155, statreg=0x0210, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
powerspec 2 supports D0 D3 current D0
map[20]: type 4, range 32, base 00001c00, size 4, enabled
found-> vendor=0x1166, dev=0x0234, revid=0x00
bus=0, slot=2, func=2
class=06-01-00, hdrtype=0x00, mfdev=1
cmdreg=0x0147, statreg=0x0200, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1166, dev=0x0223, revid=0x01
bus=0, slot=3, func=0
class=0c-03-10, hdrtype=0x00, mfdev=1
cmdreg=0x0157, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=10
powerspec 2 supports D0 D3 current D0
map[10]: type 1, range 32, base dfc05000, size 12, enabled
map[14]: type 4, range 32, base 00001000, size 8, enabled
pcib0: matched entry for 0.3.INTA (src \\_SB_.LNKU:0)
ioapic0: Changing trigger for pin 10 to level
ioapic0: Changing polarity for pin 10 to low
pcib0: slot 3 INTA routed to irq 10 via \\_SB_.LNKU
found-> vendor=0x1166, dev=0x0223, revid=0x01
bus=0, slot=3, func=1
class=0c-03-10, hdrtype=0x00, mfdev=0
cmdreg=0x0157, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=10
powerspec 2 supports D0 D3 current D0
map[10]: type 1, range 32, base dfc06000, size 12, enabled
map[14]: type 4, range 32, base 00001400, size 8, enabled
pcib0: matched entry for 0.3.INTA (src \\_SB_.LNKU:0)
pcib0: slot 3 INTA routed to irq 10 via \\_SB_.LNKU
found-> vendor=0x1166, dev=0x0223, revid=0x01
bus=0, slot=3, func=2
class=0c-03-20, hdrtype=0x00, mfdev=0
cmdreg=0x0117, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=10
powerspec 2 supports D0 D1 D2 D3 current D0
map[10]: type 1, range 32, base dfc07000, size 12, enabled
map[14]: type 4, range 32, base 00001800, size 8, enabled
pcib0: matched entry for 0.3.INTA (src \\_SB_.LNKU:0)
pcib0: slot 3 INTA routed to irq 10 via \\_SB_.LNKU
found-> vendor=0x102b, dev=0x0522, revid=0x02
bus=0, slot=4, func=0
class=03-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0007, statreg=0x0290, cachelnsz=16 (dwords)
lattimer=0x80 (3840 ns), mingnt=0x10 (4000 ns), maxlat=0x20
(8000 ns)
intpin=a, irq=5
powerspec 1 supports D0 D3 current D0
map[10]: type 3, range 32, base de000000, size 24, enabled
map[14]: type 1, range 32, base dfc00000, size 14, enabled
map[18]: type 1, range 32, base df000000, size 23, enabled
pcib0: matched entry for 0.4.INTA
pcib0: slot 4 INTA hardwired to IRQ 23
found-> vendor=0x1166, dev=0x0140, revid=0xa2
bus=0, slot=6, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
pcib0: matched entry for 0.6.INTA
pcib0: slot 6 INTA hardwired to IRQ 32
found-> vendor=0x1166, dev=0x0142, revid=0xa2
bus=0, slot=7, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
pcib0: matched entry for 0.7.INTA
pcib0: slot 7 INTA hardwired to IRQ 32
found-> vendor=0x1166, dev=0x0144, revid=0xa2
bus=0, slot=8, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
pcib0: matched entry for 0.8.INTA
pcib0: slot 8 INTA hardwired to IRQ 32
found-> vendor=0x1166, dev=0x0142, revid=0xa2
bus=0, slot=9, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
pcib0: matched entry for 0.9.INTA
pcib0: slot 9 INTA hardwired to IRQ 32
found-> vendor=0x1166, dev=0x0144, revid=0xa2
bus=0, slot=10, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
pcib0: matched entry for 0.10.INTA
pcib0: slot 10 INTA hardwired to IRQ 32
found-> vendor=0x1022, dev=0x1100, revid=0x00
bus=0, slot=24, func=0
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1022, dev=0x1101, revid=0x00
bus=0, slot=24, func=1
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1022, dev=0x1102, revid=0x00
bus=0, slot=24, func=2
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x1022, dev=0x1103, revid=0x00
bus=0, slot=24, func=3
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pcib1: secondary bus 1
pcib1: subordinate bus 2
pcib1: I/O decode 0x2000-0x2fff
pcib1: memory decode 0xdf900000-0xdf9fffff
pcib1: prefetched decode 0xfff00000-0xfffff
ACPI: Found matching pin for 1.14.INTA at func 0: 7
pci1: <ACPI PCI bus> on pcib1
pci1: physical bus=1
found-> vendor=0x1166, dev=0x0104, revid=0xc0
bus=1, slot=13, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0157, statreg=0x0230, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x07 (1750 ns), maxlat=0x02
(500 ns)
found-> vendor=0x1166, dev=0x024a, revid=0x00
bus=1, slot=14, func=0
class=01-04-05, hdrtype=0x00, mfdev=0
cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=7
powerspec 2 supports D0 D3 current D0
MSI supports 1 message
map[10]: type 4, range 32, base 00002040, size 3, enabled
pcib1: (null) requested I/O range 0x2040-0x2047: in range
map[14]: type 4, range 32, base 00002034, size 2, enabled
pcib1: (null) requested I/O range 0x2034-0x2037: in range
map[18]: type 4, range 32, base 00002038, size 3, enabled
pcib1: (null) requested I/O range 0x2038-0x203f: in range
map[1c]: type 4, range 32, base 00002030, size 2, enabled
pcib1: (null) requested I/O range 0x2030-0x2033: in range
map[20]: type 4, range 32, base 00002000, size 5, enabled
pcib1: (null) requested I/O range 0x2000-0x201f: in range
map[24]: type 1, range 32, base df900000, size 13, enabled
pcib1: (null) requested memory range 0xdf900000-0xdf901fff: good
pcib1: matched entry for 1.14.INTA (src \\_SB_.LNKS:0)
ioapic0: Changing trigger for pin 7 to level
ioapic0: Changing polarity for pin 7 to low
pcib1: slot 14 INTA routed to irq 7 via \\_SB_.LNKS
pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci1
pcib2: secondary bus 2
pcib2: subordinate bus 2
pcib2: I/O decode 0xf000-0xfff
pcib2: memory decode 0xfff00000-0xfffff
pcib2: prefetched decode 0xfff00000-0xfffff
pci2: <ACPI PCI bus> on pcib2
pci2: physical bus=2
atapci0: <ServerWorks HT1000 SATA150 controller> port
0x2040-0x2047,0x2034-0x203
7,0x2038-0x203f,0x2030-0x2033,0x2000-0x201f mem 0xdf900000-0xdf901fff
irq 7 at d
evice 14.0 on pci1
atapci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2000
ioapic0: routing intpin 7 (ISA IRQ 7) to vector 49
atapci0: [MPSAFE]
atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xdf900000
ata2: <ATA channel 0> on atapci0
ata2: reset tp1 mask=01 ostat0=50 ostat1=00
ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata2: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata2: [MPSAFE]
ata3: <ATA channel 1> on atapci0
ata3: reset tp1 mask=01 ostat0=50 ostat1=00
ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata3: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata3: [MPSAFE]
ata4: <ATA channel 2> on atapci0
ata4: reset tp1 mask=01 ostat0=7f ostat1=00
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata4: reset tp2 stat0=ff stat1=00 devices=0x0
ata4: [MPSAFE]
ata5: <ATA channel 3> on atapci0
ata5: reset tp1 mask=01 ostat0=7f ostat1=00
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: stat0=0x7f err=0xff lsb=0xff msb=0xff
ata5: reset tp2 stat0=ff stat1=00 devices=0x0
ata5: [MPSAFE]
atapci1: <ServerWorks HT1000 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x
177,0x376,0x1c00-0x1c0f at device 2.1 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1c00
ata0: <ATA channel 0> on atapci1
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
ata0: reset tp1 mask=01 ostat0=50 ostat1=ff
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80
ata0: reset tp2 stat0=80 stat1=00 devices=0x0
ioapic0: routing intpin 14 (ISA IRQ 14) to vector 50
ata0: [MPSAFE]
ata1: <ATA channel 1> on atapci1
atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170
atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376
ata1: reset tp1 mask=00 ostat0=ff ostat1=ff
ioapic0: routing intpin 15 (ISA IRQ 15) to vector 51
ata1: [MPSAFE]
isab0: <PCI-ISA bridge> at device 2.2 on pci0
isa0: <ISA bus> on isab0
ohci0: <OHCI (generic) USB controller> port 0x1000-0x10ff mem
0xdfc05000-0xdfc05
fff irq 10 at device 3.0 on pci0
ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfc05000
ohci0: (New OHCI DeviceId=0x02231166)
ioapic0: routing intpin 10 (ISA IRQ 10) to vector 52
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> port 0x1400-0x14ff mem
0xdfc06000-0xdfc06
fff irq 10 at device 3.1 on pci0
ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfc06000
ohci1: (New OHCI DeviceId=0x02231166)
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> port 0x1800-0x18ff mem
0xdfc07000-0xd
fc07fff irq 10 at device 3.2 on pci0
ehci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfc07000
ehci0: (New EHCI DeviceId=0x02231166)
ehci0: [GIANT-LOCKED]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: (0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
uhub3: vendor 0x04cc product 0x1520, class 9/0, rev 2.00/2.00, addr 2
uhub3: single transaction translator
uhub3: 3 ports with 3 removable, self powered
pci0: <display, VGA> at device 4.0 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> irq 32 at device 6.0 on pci0
pcib3: secondary bus 3
pcib3: subordinate bus 3
pcib3: I/O decode 0xf000-0xfff
pcib3: memory decode 0xfff00000-0xfffff
pcib3: prefetched decode 0xfff00000-0xfffff
pci3: <ACPI PCI bus> on pcib3
pci3: physical bus=3
pcib4: <ACPI PCI-PCI bridge> irq 32 at device 7.0 on pci0
pcib4: secondary bus 4
pcib4: subordinate bus 4
pcib4: I/O decode 0xf000-0xfff
pcib4: memory decode 0xfff00000-0xfffff
pcib4: prefetched decode 0xfff00000-0xfffff
pci4: <ACPI PCI bus> on pcib4
pci4: physical bus=4
pcib5: <ACPI PCI-PCI bridge> irq 32 at device 8.0 on pci0
pcib5: secondary bus 5
pcib5: subordinate bus 5
pcib5: I/O decode 0xf000-0xfff
pcib5: memory decode 0xfff00000-0xfffff
pcib5: prefetched decode 0xfff00000-0xfffff
pci5: <ACPI PCI bus> on pcib5
pci5: physical bus=5
pcib6: <ACPI PCI-PCI bridge> irq 32 at device 9.0 on pci0
pcib6: secondary bus 6
pcib6: subordinate bus 6
pcib6: I/O decode 0xf000-0xfff
pcib6: memory decode 0xfff00000-0xfffff
pcib6: prefetched decode 0xfff00000-0xfffff
pci6: <ACPI PCI bus> on pcib6
pci6: physical bus=6
pcib7: <ACPI PCI-PCI bridge> irq 32 at device 10.0 on pci0
pcib7: secondary bus 7
pcib7: subordinate bus 8
pcib7: I/O decode 0xf000-0xfff
pcib7: memory decode 0xdf800000-0xdf8fffff
pcib7: prefetched decode 0xfff00000-0xfffff
pcib7: could not get PCI interrupt routing table for \\_SB_.PCI0.EXB4 -
AE_NOT_F
OUND
pci7: <ACPI PCI bus> on pcib7
pci7: physical bus=7
found-> vendor=0x1166, dev=0x0103, revid=0xb5
bus=7, slot=0, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
cmdreg=0x0147, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns)
pcib8: <ACPI PCI-PCI bridge> at device 0.0 on pci7
pcib8: secondary bus 8
pcib8: subordinate bus 8
pcib8: I/O decode 0xf000-0xfff
pcib8: memory decode 0xdf800000-0xdf8fffff
pcib8: prefetched decode 0xfff00000-0xfffff
pci8: <ACPI PCI bus> on pcib8
pci8: physical bus=8
found-> vendor=0x14e4, dev=0x1678, revid=0xa3
bus=8, slot=4, func=0
class=02-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0156, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
intpin=a, irq=5
powerspec 2 supports D0 D3 current D0
MSI supports 8 messages, 64 bit
map[10]: type 1, range 64, base df810000, size 16, enabled
pcib8: (null) requested memory range 0xdf810000-0xdf81ffff: good
pcib7: (null) requested memory range 0xdf810000-0xdf81ffff: good
map[18]: type 1, range 64, base df800000, size 16, enabled
pcib8: (null) requested memory range 0xdf800000-0xdf80ffff: good
pcib7: (null) requested memory range 0xdf800000-0xdf80ffff: good
pcib8: matched entry for 8.4.INTA
pcib8: slot 4 INTA hardwired to IRQ 36
found-> vendor=0x14e4, dev=0x1678, revid=0xa3
bus=8, slot=4, func=1
class=02-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0156, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
intpin=b, irq=5
powerspec 2 supports D0 D3 current D0
MSI supports 8 messages, 64 bit
map[10]: type 1, range 64, base df830000, size 16, enabled
pcib8: (null) requested memory range 0xdf830000-0xdf83ffff: good
pcib7: (null) requested memory range 0xdf830000-0xdf83ffff: good
map[18]: type 1, range 64, base df820000, size 16, enabled
pcib8: (null) requested memory range 0xdf820000-0xdf82ffff: good
pcib7: (null) requested memory range 0xdf820000-0xdf82ffff: good
pcib8: matched entry for 8.4.INTB
pcib8: slot 4 INTB hardwired to IRQ 36
bge0: <Broadcom unknown BCM5714, ASIC rev. 0x9003> mem
0xdf810000-0xdf81ffff,0xd
f800000-0xdf80ffff irq 36 at device 4.0 on pci8
bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xdf810000
miibus0: <MII bus> on bge0
brgphy0: <BCM5714 10/100/1000baseTX PHY> on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX
-FDX, auto
bge0: bpf attached
bge0: Ethernet address: 00:18:71:86:f6:ef
ioapic2: routing intpin 4 (PCI IRQ 36) to vector 53
bge0: [MPSAFE]
bge1: <Broadcom unknown BCM5714, ASIC rev. 0x9003> mem
0xdf830000-0xdf83ffff,0xd
f820000-0xdf82ffff irq 36 at device 4.1 on pci8
bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xdf830000
miibus1: <MII bus> on bge1
brgphy1: <BCM5714 10/100/1000baseTX PHY> on miibus1
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX
-FDX, auto
bge1: bpf attached
bge1: Ethernet address: 00:18:71:87:4e:39
bge1: [MPSAFE]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0047
atkbd: keyboard ID 0xffffffff (1)
atkbd: failed to reset the keyboard.
kbd0 at atkbd0
kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000
ioapic0: routing intpin 1 (ISA IRQ 1) to vector 54
atkbd0: [GIANT-LOCKED]
psm0: unable to allocate IRQ
sio0: irq maps: 0x4401 0x4411 0x4401 0x4401
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
ioapic0: routing intpin 4 (ISA IRQ 4) to vector 55
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
unknown: status reg test failed ff
ex_isa_identify()
ata: ata0 already exists; skipping it
ata: ata1 already exists; skipping it
atkbdc: atkbdc0 already exists; skipping it
sio: sio0 already exists; skipping it
pnp_identify: Trying Read_Port at 203
pnp_identify: Trying Read_Port at 243
pnp_identify: Trying Read_Port at 283
pnp_identify: Trying Read_Port at 2c3
pnp_identify: Trying Read_Port at 303
pnp_identify: Trying Read_Port at 343
pnp_identify: Trying Read_Port at 383
pnp_identify: Trying Read_Port at 3c3
PNP Identify complete
ahc_isa_probe 0: ioport 0xc00 alloc failed
ahc_isa_probe 1: ioport 0x1c00 alloc failed
sc: sc0 already exists; skipping it
vga: vga0 already exists; skipping it
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
adv0: not probed (disabled)
aha0: not probed (disabled)
aic0: not probed (disabled)
bt0: not probed (disabled)
cs0: not probed (disabled)
ed0: not probed (disabled)
fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fe0: not probed (disabled)
ie0: not probed (disabled)
lnc0: not probed (disabled)
ppc0: parallel port not found.
ppc0: <Parallel port> failed to probe at irq 7 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd1, terminal emulator: sc (syscons terminal)
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: irq maps: 0x4401 0x4401 0x4401 0x4401
sio1: probe failed test(s): 0 1 2 4 6 7 9
sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0
sio2: not probed (disabled)
sio3: not probed (disabled)
sn0: not probed (disabled)
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
vt0: not probed (disabled)
isa_probe_children: probing PnP devices
ukbd0: ServerEngines SE USB Device, rev 1.10/0.01, addr 2, iclass 3/1
kbd2 at ukbd0
kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000
ums0: ServerEngines SE USB Device, rev 1.10/0.01, addr 2, iclass 3/1
ums0: 8 buttons and Z dir.
Device configuration finished.
Reducing kern.maxvnodes 134325 -> 100000
procfs registered
lapic: Divisor 2, Frequency 99750283 hz
Timecounter "TSC" frequency 2194516692 Hz quality -100
Timecounters tick every 1.000 msec
lo0: bpf attached
rr232x: no controller detected.
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad4: 238475MB <Seagate ST3250620NS 3BJP> at ata2-master SATA150
ad4: 488397168 sectors [484521C/16H/63S] 16 sectors/interrupt 1 depth queue
GEOM: new disk ad4
ad4: Adaptec check1 failed
ad4: LSI (v3) check1 failed
ad4: LSI (v2) check1 failed
ad4: FreeBSD check1 failed
ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad6: 238475MB <Seagate ST3250620NS 3.BJH> at ata3-master SATA150
ad6: 488397168 sectors [484521C/16H/63S] 16 sectors/interrupt 1 depth queue
ad6: Adaptec check1 failed
ad6: LSI (v3) check1 failed
ad6: LSI (v2) check1 failed
ad6: FreeBSD check1 failed
ATA PseudoRAID loaded
SMP: AP CPU #1 Launched!
cpu1 AP:
ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
INTR: Assigning IRQ 1 to local APIC 0
ioapic0: Assigning ISA IRQ 1 to local APIC 0
INTR: Assigning IRQ 4 to local APIC 1
ioapic0: Assigning ISA IRQ 4 to local APIC 1
INTR: Assigning IRQ 7 to local APIC 0
ioapic0: Assigning ISA IRQ 7 to local APIC 0
INTR: Assigning IRQ 9 to local APIC 1
ioapic0: Assigning ISA IRQ 9 to local APIC 1
INTR: Assigning IRQ 10 to local APIC 0
ioapic0: Assigning ISA IRQ 10 to local APIC 0
INTR: Assigning IRQ 14 to local APIC 1
ioapic0: Assigning ISA IRQ 14 to local APIC 1
INTR: Assigning IRQ 15 to local APIC 0
ioapic0: Assigning ISA IRQ 15 to local APIC 0
INTR: Assigning IRQ 36 to local APIC 1
ioapic2: Assigning PCI IRQ 36 to local APIC 1
GEOM: new disk ad6
Trying to mount root from ufs:/dev/ad4s1a
start_init: trying /sbin/init
bge0: link UP
bge0: link state changed to UP
Failure scenario:
Create partition, slice and filesystem on ad6 and mount it on /mnt. Then:
dd if=/dev/zero of=/mnt/foo bs=512k
This fails every time with "disk full", sometimes after 8 MB, other
times after 70 GB. Sometimes the file system can be recovered by fsck
(usually when the amount of data written isn't much), other times the
superblock is damaged (usually when a lot of data is written).
Andrey V. Elsukov
> Again, on the machines I'm seeing this on it was totally disabled. I don't think
> I can totally disable DMA (NICs etc. must use DMA) on the machines and since they
> are in production and I only see the corruption as an after-effect when the boxes
> panic or deadlock for another reason I'm not easily able to reproduce this. Also,
> we do disable MSI for devices behind HT2000 chipsets because of a chip bug, but
> not on HT1000 currently. However, MSI isn't on on 6.x anyway.
Hi, John.
Anton Yuzhaninov has mentioned in the top of this thread that
this bug may be easy reproduced by using external PCI-X card.
He tried use PCI-X Marvell card and got lots of corruptions on
the integrated HT1000. Can you or Soren try the same way to
reproduce?
--
WBR, Andrey V. Elsukov
Søren Schmidt
> John Baldwin wrote:
>> don't think
>> I can totally disable DMA (NICs etc. must use DMA) on the machines=20
>> and since they
>> are in production and I only see the corruption as an after-effect=20
>> when the boxes
>> panic or deadlock for another reason I'm not easily able to reproduce =
>> this. Also,
>> we do disable MSI for devices behind HT2000 chipsets because of a=20
>> chip bug, but
>> not on HT1000 currently. However, MSI isn't on on 6.x anyway.
>
> Hi, John.
>
> Anton Yuzhaninov has mentioned in the top of this thread that
> this bug may be easy reproduced by using external PCI-X card.
> He tried use PCI-X Marvell card and got lots of corruptions on
> the integrated HT1000. Can you or Soren try the same way to
> reproduce?
As I told earlier the fileserver I have here with the HT1000 chip also=20
has a marvel 6081 and it is on PCI-X. There are 4 disks on each and it=20
moves lots of data around on a daily basis, no problems whatsoever. I=20
have planned downtime today on it and will experiment with it, but I=20
can't hold it off for too long...
-S=F8ren
Andrey V. Elsukov
>> Anton Yuzhaninov has mentioned in the top of this thread that
>> this bug may be easy reproduced by using external PCI-X card.
>> He tried use PCI-X Marvell card and got lots of corruptions on
>> the integrated HT1000. Can you or Soren try the same way to
>> reproduce?
> As I told earlier the fileserver I have here with the HT1000 chip also
May be here is different HW revisions? You have an old revision and
now people with this bug have a new revision?
I don't see in the this thread any verbose dmesg or pciconf outputs.
So, people, who have problems and who don't have it, can you show
your `pciconf -l`?
--
WBR, Andrey V. Elsukov
Mike Tancsa
>May be here is different HW revisions? You have an old revision and
>now people with this bug have a new revision?
>I don't see in the this thread any verbose dmesg or pciconf outputs.
>So, people, who have problems and who don't have it, can you show
>your `pciconf -l`?
My board works well and has since the 6.1 days
# pciconf -lvc
pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x00361166
rev=0x00 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
cap 07[90] = PCI-X bridge supports
cap 08[a0] = HT MSI address window enabled at 0xfee00000
cap 08[b0] = HT slave
hostb0@pci0:2:0: class=0x060000 card=0x02011166
chip=0x02051166 rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = HOST-PCI
atapci1@pci0:2:1: class=0x01018a card=0x02141166
chip=0x02141166 rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = mass storage
subclass = ATA
isab0@pci0:2:2: class=0x060100 card=0x02301166 chip=0x02341166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-ISA
ohci0@pci0:3:0: class=0x0c0310 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
cap 01[dc] = powerspec 2 supports D0 D3 current D0
ohci1@pci0:3:1: class=0x0c0310 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
cap 01[dc] = powerspec 2 supports D0 D3 current D0
ehci0@pci0:3:2: class=0x0c0320 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = serial bus
subclass = USB
cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0
em2@pci0:4:0: class=0x020000 card=0x387010f1 chip=0x10768086
rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82547EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
cap 01[dc] = powerspec 2 supports D0 D3 current D0
cap 07[e4] = PCI-X supports 2048 burst read, 1 split transaction
em3@pci0:5:0: class=0x020000 card=0x387010f1 chip=0x10768086
rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82547EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
cap 01[dc] = powerspec 2 supports D0 D3 current D0
cap 07[e4] = PCI-X supports 2048 burst read, 1 split transaction
none0@pci0:6:0: class=0x030000 card=0x002018ca chip=0x002018ca
rev=0x00 hdr=0x00
vendor = 'XGI Technology Inc'
class = display
subclass = VGA
cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0
rl0@pci0:7:0: class=0x020000 card=0x813910ec chip=0x813910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
class = network
subclass = ethernet
cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0
hostb1@pci0:24:0: class=0x060000 card=0x00000000
chip=0x11001022 rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron HyperTransport Technology Configuration'
class = bridge
subclass = HOST-PCI
cap 08[80] = HT host
hostb2@pci0:24:1: class=0x060000 card=0x00000000
chip=0x11011022 rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron Address Map'
class = bridge
subclass = HOST-PCI
hostb3@pci0:24:2: class=0x060000 card=0x00000000
chip=0x11021022 rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron DRAM Controller'
class = bridge
subclass = HOST-PCI
hostb4@pci0:24:3: class=0x060000 card=0x00000000
chip=0x11031022 rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon 64 / Opteron Miscellaneous Control'
class = bridge
subclass = HOST-PCI
cap 0f[f0] = unknown
pcib2@pci1:13:0: class=0x060400 card=0x00000000
chip=0x01041166 rev=0xb2 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = bridge
subclass = PCI-PCI
cap 07[90] = PCI-X 64-bit bridge supports 133MHz
atapci0@pci1:14:0: class=0x010405 card=0x024a1166
chip=0x024a1166 rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
class = mass storage
subclass = RAID
cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 8
split transactions
cap 01[90] = powerspec 2 supports D0 D3 current D0
cap 05[a0] = MSI supports 1 message
em0@pci2:3:0: class=0x020000 card=0x117a8086 chip=0x10798086
rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82546EB Dual Port Gigabit Ethernet Controller'
class = network
subclass = ethernet
cap 01[dc] = powerspec 2 supports D0 D3 current D0
cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1
split transaction
cap 05[f0] = MSI supports 1 message, 64 bit
em1@pci2:3:1: class=0x020000 card=0x117a8086 chip=0x10798086
rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82546EB Dual Port Gigabit Ethernet Controller'
class = network
subclass = ethernet
cap 01[dc] = powerspec 2 supports D0 D3 current D0
cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1
split transaction
cap 05[f0] = MSI supports 1 message, 64 bit
# cat /var/run/dmesg.boot
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.3-PRERELEASE #1: Thu Oct 25 21:54:13 EDT 2007
mdta...@iolite2.sentex.ca:/usr/obj/usr/src/sys/iolite
ACPI APIC Table: <A M I OEMAPIC >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3800+ (2413.18-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x40ff2 Stepping = 2
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
Features2=0x2001<SSE3,CX16>
AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
AMD Features2=0x1d<LAHF,SVM,ExtAPIC,CR8>
real memory = 1073676288 (1023 MB)
avail memory = 1041670144 (993 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-15 on motherboard
ioapic1 <Version 1.1> irqs 16-31 on motherboard
ioapic2 <Version 1.1> irqs 32-47 on motherboard
kbd1 at kbdmux0
acpi0: <A M I OEMXSDT> on motherboard
acpi0: Power Button (fixed)
acpi0: Sleep Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci1
pci2: <ACPI PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection Version - 6.6.6> port
0xa880-0xa8bf mem 0xff2c0000-0xff2dffff,0xff280000-0xff2bffff irq 16
at device 3.0 on pci2
em0: Ethernet address: 00:0e:0c:81:14:d4
em1: <Intel(R) PRO/1000 Network Connection Version - 6.6.6> port
0xac00-0xac3f mem 0xff2e0000-0xff2fffff irq 17 at device 3.1 on pci2
em1: Ethernet address: 00:0e:0c:81:14:d5
atapci0: <ServerWorks HT1000 SATA150 controller> port
0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb81f
mem 0xff3fe000-0xff3fffff irq 11 at device 14.0 on pci1
ata2: <ATA channel 0> on atapci0
ata3: <ATA channel 1> on atapci0
ata4: <ATA channel 2> on atapci0
ata5: <ATA channel 3> on atapci0
atapci1: <ServerWorks HT1000 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0
ata0: <ATA channel 0> on atapci1
ata1: <ATA channel 1> on atapci1
isab0: <PCI-ISA bridge> at device 2.2 on pci0
isa0: <ISA bus> on isab0
ohci0: <OHCI (generic) USB controller> port 0xe000-0xe0ff mem
0xff6b4000-0xff6b4fff irq 10 at device 3.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> port 0xe400-0xe4ff mem
0xff6b5000-0xff6b5fff irq 10 at device 3.1 on pci0
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> port 0xe800-0xe8ff mem
0xff6b6000-0xff6b6fff irq 10 at device 3.2 on pci0
ehci0: [GIANT-LOCKED]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: (0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
em2: <Intel(R) PRO/1000 Network Connection Version - 6.6.6> port
0xdc00-0xdc3f mem 0xff680000-0xff69ffff,0xff660000-0xff67ffff irq 24
at device 4.0 on pci0
em2: Ethernet address: 00:e0:81:5e:be:3c
em3: <Intel(R) PRO/1000 Network Connection Version - 6.6.6> port
0xd880-0xd8bf mem 0xff620000-0xff63ffff,0xff600000-0xff61ffff irq 25
at device 5.0 on pci0
em3: Ethernet address: 00:e0:81:5e:be:3d
pci0: <display, VGA> at device 6.0 (no driver attached)
rl0: <RealTek 8139 10/100BaseTX> port 0xd400-0xd4ff mem
0xff6b3c00-0xff6b3cff irq 27 at device 7.0 on pci0
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:50:fc:a7:9d:04
acpi_button0: <Power Button> on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A, console
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem
0xc0000-0xc7fff,0xc8000-0xc9fff,0xca000-0xcafff,0xcb000-0xcbfff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 2413179713 Hz quality 800
Timecounters tick every 1.000 msec
ad4: 76319MB <Seagate ST380811AS 3.AAE> at ata2-master SATA150
Trying to mount root from ufs:/dev/ad4s1a
---Mike
Travis Mikalson
> Søren Schmidt wrote:
>>> Anton Yuzhaninov has mentioned in the top of this thread that
>>> this bug may be easy reproduced by using external PCI-X card.
>>> He tried use PCI-X Marvell card and got lots of corruptions on
>>> the integrated HT1000. Can you or Soren try the same way to
>>> reproduce?
>> As I told earlier the fileserver I have here with the HT1000 chip also
>> has a marvel 6081 and it is on PCI-X. There are 4 disks on each and it
>> moves lots of data around on a daily basis, no problems whatsoever. I
>> have planned downtime today on it and will experiment with it, but I
>> can't hold it off for too long...
>
> people with this bug have a new revision?
> I don't see in the this thread any verbose dmesg or pciconf outputs.
> So, people, who have problems and who don't have it, can you show
> your `pciconf -l`?
I think I posted it already but here it is again. I should also mention
I just updated my BIOS to a very recently released one from Tyan (v2.00)
and it had no effect and I've also tweaked pretty much every weird
obscure knob in the CMOS to no avail... Including disabling serial and
on-board NICs and using the SATA controller in P-ATA (legacy) mode, etc.
This is the board that works poorly as I described yesterday with 6.2,
6.3 and has the memory/data corruption in RELENG_7.
$ pciconf -lv
pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0x00361166
rev=0x00 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'HT1000 PCI/PCI-X bridge'
class = bridge
subclass = PCI-PCI
hostb0@pci0:0:2:0: class=0x060000 card=0x02011166 chip=0x02051166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'HT1000 Legacy South Bridge'
class = bridge
subclass = HOST-PCI
atapci1@pci0:0:2:1: class=0x01018a card=0x02141166 chip=0x02141166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'HT1000 Legacy IDE controller'
class = mass storage
subclass = ATA
isab0@pci0:0:2:2: class=0x060100 card=0x02301166 chip=0x02341166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'HT1000 LPC Bridge'
class = bridge
subclass = PCI-ISA
none0@pci0:0:3:0: class=0x0c0310 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = '0x0223 USB controller'
class = serial bus
subclass = USB
none1@pci0:0:3:1: class=0x0c0310 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = '0x0223 USB controller'
class = serial bus
subclass = USB
none2@pci0:0:3:2: class=0x0c0320 card=0x02231166 chip=0x02231166
rev=0x01 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = '0x0223 USB controller'
class = serial bus
subclass = USB
em0@pci0:0:4:0: class=0x020000 card=0x387010f1 chip=0x10768086 rev=0x05
hdr=0x00
vendor = 'Intel Corporation'
device = '82541EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
em1@pci0:0:5:0: class=0x020000 card=0x387010f1 chip=0x10768086 rev=0x05
hdr=0x00
vendor = 'Intel Corporation'
device = '82541EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
vgapci0@pci0:0:6:0: class=0x030000 card=0x002018ca chip=0x002018ca
rev=0x00 hdr=0x00
vendor = 'XGI Technology Inc'
class = display
subclass = VGA
atapci2@pci0:0:7:0: class=0x010400 card=0x61141095 chip=0x31141095
rev=0x02 hdr=0x00
vendor = 'Silicon Image Inc (Was: CMD Technology Inc)'
device = 'Sil 3114 SATALink/SATARaid Controller'
class = mass storage
subclass = RAID
hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = '(K8) Athlon 64/Opteron HyperTransport Technology
Configuration'
class = bridge
subclass = HOST-PCI
hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = '(K8) Athlon 64/Opteron Address Map'
class = bridge
subclass = HOST-PCI
hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = '(K8) Athlon 64/Opteron DRAM Controller'
class = bridge
subclass = HOST-PCI
hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = '(K8) Athlon 64/Opteron Miscellaneous Control'
class = bridge
subclass = HOST-PCI
pcib2@pci0:1:13:0: class=0x060400 card=0x4f00d3f7 chip=0x01041166
rev=0xc0 hdr=0x01
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'HT1000 PCI/PCI-X bridge'
class = bridge
subclass = PCI-PCI
atapci0@pci0:1:14:0: class=0x010405 card=0x024a1166 chip=0x024a1166
rev=0x00 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'BCM5785 (HT1000) SATA Native SATA Mode'
class = mass storage
subclass = RAID
$ cat /var/run/dmesg.boot
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-BETA3 #8: Tue Nov 27 16:59:39 UTC 2007
t...@newtog.tog.net:/usr/obj/usr/src/sys/tognet
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual-Core AMD Opteron(tm) Processor 1212 (1995.02-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x40f32 Stepping = 2
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x2001<SSE3,CX16>
AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>
Cores per package: 2
usable memory = 2138079232 (2039 MB)
avail memory = 2062680064 (1967 MB)
ACPI APIC Table: <A M I OEMAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-15 on motherboard
ioapic1 <Version 1.1> irqs 16-31 on motherboard
ioapic2 <Version 1.1> irqs 32-47 on motherboard
kbd1 at kbdmux0
acpi0: <A M I OEMXSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: Sleep Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7ff00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
cpu0: <ACPI CPU> on acpi0
powernow0: <PowerNow! K8> on cpu0
device_attach: powernow0 attach returned 6
cpu1: <ACPI CPU> on acpi0
powernow1: <PowerNow! K8> on cpu1
device_attach: powernow1 attach returned 6
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci1
pci2: <ACPI PCI bus> on pcib2
atapci0: <ServerWorks HT1000 SATA150 controller> port
0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb81f
mem 0xff2fe000-0xff2fffff irq 11 at device 14.0 on pci1
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
atapci1: <ServerWorks HT1000 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci1
ata1: [ITHREAD]
isab0: <PCI-ISA bridge> at device 2.2 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, USB> at device 3.0 (no driver attached)
pci0: <serial bus, USB> at device 3.1 (no driver attached)
pci0: <serial bus, USB> at device 3.2 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> port
0xe000-0xe03f mem 0xff680000-0xff69ffff,0xff5e0000-0xff5fffff irq 24 at
device 4.0 on pci0
em0: Ethernet address: 00:e0:81:81:25:0a
em0: [FILTER]
em1: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> port
0xdc00-0xdc3f mem 0xff5a0000-0xff5bffff,0xff580000-0xff59ffff irq 25 at
device 5.0 on pci0
em1: Ethernet address: 00:e0:81:81:25:0b
em1: [FILTER]
vgapci0: <VGA-compatible display> port 0xec00-0xec7f mem
0xf8000000-0xfbffffff,0xff6c0000-0xff6fffff at device 6.0 on pci0
atapci2: <SiI SiI 3114 SATA150 controller> port
0xe880-0xe887,0xe800-0xe803,0xe480-0xe487,0xe400-0xe403,0xe080-0xe08f
mem 0xff6bbc00-0xff6bbfff irq 27 at device 7.0 on pci0
atapci2: [ITHREAD]
ata6: <ATA channel 0> on atapci2
ata6: [ITHREAD]
ata7: <ATA channel 1> on atapci2
ata7: [ITHREAD]
ata8: <ATA channel 2> on atapci2
ata8: [ITHREAD]
ata9: <ATA channel 3> on atapci2
ata9: [ITHREAD]
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio0: [FILTER]
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcc7ff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
Timecounters tick every 1.000 msec
ZFS filesystem version 6
ZFS storage pool version 6
acd0: DVDROM <Pioneer DVD-ROM ATAPIModel DVD-106S 0109/E1.09> at
ata0-master UDMA66
ad12: 476940MB <Seagate ST3500630NS 3.AEG> at ata6-master SATA150
ad14: 476940MB <Seagate ST3500630NS 3.AEG> at ata7-master SATA150
SMP: AP CPU #1 Launched!
GEOM_MIRROR: Device mirror/gm0 launched (2/2).
GEOM_MIRROR: Device mirror/gm1 launched (2/2).
WARNING: Expected rawoffset 0, found 63
Trying to mount root from zfs:zroot
WARNING: Expected rawoffset 0, found 63
--
TerraNovaNet Internet Services - Key Largo, FL
Voice: (305)453-4011 x101 Fax: (305)451-5991
http://www.terranova.net/
----------------------------------------------
Life's not fair, but the root password helps.
Barney Cordoba
--- Mike Tancsa <mi...@sentex.net> wrote:
> At 02:26 AM 11/29/2007, Andrey V. Elsukov wrote:
>
> >May be here is different HW revisions? You have an
> old revision and
> >now people with this bug have a new revision?
> >I don't see in the this thread any verbose dmesg or
> pciconf outputs.
> >So, people, who have problems and who don't have
> it, can you show
> >your `pciconf -l`?
>
> My board works well and has since the 6.1 days
>
> # pciconf -lvc
> pcib1@pci0:1:0: class=0x060400 card=0x00000000
> chip=0x00361166
> rev=0x00 hdr=0x01
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = bridge
> subclass = PCI-PCI
> cap 07[90] = PCI-X bridge supports
> cap 08[a0] = HT MSI address window enabled at
> 0xfee00000
> cap 08[b0] = HT slave
> hostb0@pci0:2:0: class=0x060000
> card=0x02011166
> chip=0x02051166 rev=0x00 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = bridge
> subclass = HOST-PCI
> atapci1@pci0:2:1: class=0x01018a
> card=0x02141166
> chip=0x02141166 rev=0x00 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = mass storage
> subclass = ATA
> isab0@pci0:2:2: class=0x060100 card=0x02301166
> chip=0x02341166
> rev=0x00 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = bridge
> subclass = PCI-ISA
> ohci0@pci0:3:0: class=0x0c0310 card=0x02231166
> chip=0x02231166
> rev=0x01 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = serial bus
> subclass = USB
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> ohci1@pci0:3:1: class=0x0c0310 card=0x02231166
> chip=0x02231166
> rev=0x01 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = serial bus
> subclass = USB
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> ehci0@pci0:3:2: class=0x0c0320 card=0x02231166
> chip=0x02231166
> rev=0x01 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = serial bus
> subclass = USB
> cap 01[dc] = powerspec 2 supports D0 D1 D2 D3
> current D0
> em2@pci0:4:0: class=0x020000 card=0x387010f1
> chip=0x10768086
> rev=0x05 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82547EI Gigabit Ethernet
> Controller'
> class = network
> subclass = ethernet
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> cap 07[e4] = PCI-X supports 2048 burst read, 1
> split transaction
> em3@pci0:5:0: class=0x020000 card=0x387010f1
> chip=0x10768086
> rev=0x05 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82547EI Gigabit Ethernet
> Controller'
> class = network
> subclass = ethernet
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> cap 07[e4] = PCI-X supports 2048 burst read, 1
> split transaction
> none0@pci0:6:0: class=0x030000 card=0x002018ca
> chip=0x002018ca
> rev=0x00 hdr=0x00
> vendor = 'XGI Technology Inc'
> class = display
> subclass = VGA
> cap 01[40] = powerspec 2 supports D0 D1 D2 D3
> current D0
> rl0@pci0:7:0: class=0x020000 card=0x813910ec
> chip=0x813910ec
> rev=0x10 hdr=0x00
> vendor = 'Realtek Semiconductor'
> device = 'RT8139 (A/B/C/810x/813x/C+) Fast
> Ethernet Adapter'
> class = network
> subclass = ethernet
> cap 01[50] = powerspec 2 supports D0 D1 D2 D3
> current D0
> hostb1@pci0:24:0: class=0x060000
> card=0x00000000
> chip=0x11001022 rev=0x00 hdr=0x00
> vendor = 'Advanced Micro Devices (AMD)'
> device = 'Athlon 64 / Opteron
> HyperTransport Technology Configuration'
> class = bridge
> subclass = HOST-PCI
> cap 08[80] = HT host
> hostb2@pci0:24:1: class=0x060000
> card=0x00000000
> chip=0x11011022 rev=0x00 hdr=0x00
> vendor = 'Advanced Micro Devices (AMD)'
> device = 'Athlon 64 / Opteron Address Map'
> class = bridge
> subclass = HOST-PCI
> hostb3@pci0:24:2: class=0x060000
> card=0x00000000
> chip=0x11021022 rev=0x00 hdr=0x00
> vendor = 'Advanced Micro Devices (AMD)'
> device = 'Athlon 64 / Opteron DRAM
> Controller'
> class = bridge
> subclass = HOST-PCI
> hostb4@pci0:24:3: class=0x060000
> card=0x00000000
> chip=0x11031022 rev=0x00 hdr=0x00
> vendor = 'Advanced Micro Devices (AMD)'
> device = 'Athlon 64 / Opteron Miscellaneous
> Control'
> class = bridge
> subclass = HOST-PCI
> cap 0f[f0] = unknown
> pcib2@pci1:13:0: class=0x060400
> card=0x00000000
> chip=0x01041166 rev=0xb2 hdr=0x01
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = bridge
> subclass = PCI-PCI
> cap 07[90] = PCI-X 64-bit bridge supports
> 133MHz
> atapci0@pci1:14:0: class=0x010405
> card=0x024a1166
> chip=0x024a1166 rev=0x00 hdr=0x00
> vendor = 'ServerWorks (Was: Reliance
> Computer Corp)'
> class = mass storage
> subclass = RAID
> cap 07[60] = PCI-X 64-bit supports 133MHz, 512
> burst read, 8
> split transactions
> cap 01[90] = powerspec 2 supports D0 D3
> current D0
> cap 05[a0] = MSI supports 1 message
> em0@pci2:3:0: class=0x020000 card=0x117a8086
> chip=0x10798086
> rev=0x03 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82546EB Dual Port Gigabit
> Ethernet Controller'
> class = network
> subclass = ethernet
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048
> burst read, 1
> split transaction
> cap 05[f0] = MSI supports 1 message, 64 bit
> em1@pci2:3:1: class=0x020000 card=0x117a8086
> chip=0x10798086
> rev=0x03 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82546EB Dual Port Gigabit
> Ethernet Controller'
> class = network
> subclass = ethernet
> cap 01[dc] = powerspec 2 supports D0 D3
> current D0
> cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048
> burst read, 1
> split transaction
> cap 05[f0] = MSI supports 1 message, 64 bit
>
> # cat /var/run/dmesg.boot
> Copyright (c) 1992-2007 The FreeBSD Project.
>
=== message truncated ===
I think we've established that 6.x works and 7.x
doesn't.
Barney
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Travis Mikalson
> --- Mike Tancsa <mi...@sentex.net> wrote:
>
>> At 02:26 AM 11/29/2007, Andrey V. Elsukov wrote:
>>
>>> May be here is different HW revisions? You have an
>> old revision and
>>> now people with this bug have a new revision?
>>> I don't see in the this thread any verbose dmesg or
>> pciconf outputs.
>>> So, people, who have problems and who don't have
>> it, can you show
>>> your `pciconf -l`?
>> My board works well and has since the 6.1 days
>
> doesn't.
>
> Barney
Not mine, I'm afraid.
See post from yesterday where I tried 6.2 and 6.3 on my Tyan S3950 and
it worked poorly.
Not sure what the major difference between one HT1000 board and another
could be, but mine seems to be in the most-afflicted category. I count
myself lucky that it works as well as it does with RELENG_7 so long as I
avoid the PCI-X slot or the on-board SATA.
--
TerraNovaNet Internet Services - Key Largo, FL
Voice: (305)453-4011 x101 Fax: (305)451-5991
http://www.terranova.net/
----------------------------------------------
Life's not fair, but the root password helps.
Barney Cordoba
It seems to me it makes more sense to use a different
MB than avoiding the slot and not using SATA. One of
the attractions of the HT1000 is the SATA performance.
Are you sending Soren a MB, or what is the status of
that?
Barney
____________________________________________________________________________________
Be a better sports nut! Let your teams follow you
with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
Travis Mikalson
I have three of them already so.. I'd like them to work. I consider the
broken status temporary and the SiI3114 controllers a temporary
workaround. And of course I'd like FreeBSD to work well for everybody
else on this platform.
> Are you sending Soren a MB, or what is the status of
> that?
Yes, I corresponded with Søren privately and I am going to send him a
Tyan S3950 kit, he was unable to reproduce the issue on his specific
HT1000-based hardware.
--
TerraNovaNet Internet Services - Key Largo, FL
Voice: (305)453-4011 x101 Fax: (305)451-5991
http://www.terranova.net/
----------------------------------------------
Life's not fair, but the root password helps.
Josh Paetzel
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Monday 26 November 2007 06:34:08 pm Barney Cordoba wrote:
>
> Ah, we tested an early 6.2 and it didn't come up in
> SATA mode. Well thats promising. If we can just figure
> out what's wrong with 7 now. Hopefully Soren can
> figure out what might have changed.
>
> Barney
>
I've got extensive experience trying to make the H8SSL-i work under load. =
=20
I've tried RELENG_6_2, RELENG_6 and RELENG_7 at various points in time, usi=
ng=20
either the onboard SATA and gmirror or PCI-X 9550SE 3wares.
My results are: Given enough time and load every combination has hung.
My best results: RELENG_6_2 with the 3ware cards. I can get 2 weeks out o=
f a=20
box at moderate load on average before it panics.
Worst results: Tied between RELENG_7 with the 3ware cards and RELENG_6_2 w=
ith=20
the onboard SATA in native SATA mode. Data corruption is so bad installati=
on=20
is generally not possible.
I can probably manage SSH + serial console access to anyone who wants to ta=
ke=20
a crack at fixing for a while with whatever combination of hardware and=20
=46reeBSD version you want. We're in the process of migrating off them, wh=
ich=20
will leave some hardware laying around for a couple weeks.
=2D-=20
Thanks,
Josh Paetzel
PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB
--nextPart2025945.nsenufIUJM
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQBHVG+MJvkB8SevrssRAirTAJ9e5xq942WzlUsPxKwwTCrkkswzUACdFfIg
whBrxgy3lZDaMvrthjA5XHE=
=aZt6
-----END PGP SIGNATURE-----
--nextPart2025945.nsenufIUJM--