RE: ATA Drive Issues
Ville, Yes I definitely noticed the "blame the hardware" issue. I suppose it is just the communities way of going through the process of elimination. The upgrade to 6.1 seems to be the best thing I have done so far. Now if I can just figure out why the 5.4 machine doesn't reboot on panics. I worry that 6.1 also has this issue but since it hasn't paniced I can't tell. Once I can figure that problem out I am home free. -- Wil Hatfield -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ville Lundberg Sent: Monday, April 03, 2006 11:29 AM To: freebsd-questions@freebsd.org Subject: RE: ATA Drive Issues > From: "Wil Hatfield" <[EMAIL PROTECTED]> > I am giving 6.1 a whirl. > In the first 5 minutes I have already noticed that there are some > obvious filesystem issues fixed. I ran a tar and compared the > speed to that on one of my 4.x boxes and low and behold they are > about the same. THANK GOD! Hi, I had similar issues with a server freezing, and it also turned out to be WRITE_DMA failures on one of the (SATA) HDs. This was on 6.0-release, and upgrading to 6-stable helped. Nice to see it fixed your problem, too. 6.1 seems to be a really stable and performing branch. When reporting problems for HDs, it's good policy to always state the HD and motherboard/chipset brand, and to point out if/when one has checked/renewed the cabling (as you did). Also test results from smartmontools and HD manufacturer disk tests are good to state. Even when doing this, the FreeBSD community is peculiarly keen on blaming everything on failing HW and bad cabling. My experience is, though, that the first thing to blame (when cabling and HDs have passed tests), is the HD controller, especially when it's one of the crappy ones, like Silicon Image 3xxx. These crappy chipsets results in that FreeBSD doesn't have good support for them, as they are unreliable per definition. I don't meen to critisize FreeBSD, on the contrary. But it's a bit annoying to always get responses to all HD related stuff that "your HW is failing", when everything you've done for the last week is tests which claim it isn't. I'm not familiar with the innards of FreeBSD, so could someone explain why FreeBSD is so picky about cabling? I'm pretty well-read in physics, so the theory of FreeBSD using less-energetic electrons to pass data in the cables doesn't seem to hold up (insert smiley here). I mean, if other operating systems don't do some sort of error checking to exclude the errors on HD/CD-ROM drives that make FreeBSD hiccup, then what's up? --Ville ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
> From: "Wil Hatfield" <[EMAIL PROTECTED]> > I am giving 6.1 a whirl. > In the first 5 minutes I have already noticed that there are some > obvious filesystem issues fixed. I ran a tar and compared the > speed to that on one of my 4.x boxes and low and behold they are > about the same. THANK GOD! Hi, I had similar issues with a server freezing, and it also turned out to be WRITE_DMA failures on one of the (SATA) HDs. This was on 6.0-release, and upgrading to 6-stable helped. Nice to see it fixed your problem, too. 6.1 seems to be a really stable and performing branch. When reporting problems for HDs, it's good policy to always state the HD and motherboard/chipset brand, and to point out if/when one has checked/renewed the cabling (as you did). Also test results from smartmontools and HD manufacturer disk tests are good to state. Even when doing this, the FreeBSD community is peculiarly keen on blaming everything on failing HW and bad cabling. My experience is, though, that the first thing to blame (when cabling and HDs have passed tests), is the HD controller, especially when it's one of the crappy ones, like Silicon Image 3xxx. These crappy chipsets results in that FreeBSD doesn't have good support for them, as they are unreliable per definition. I don't meen to critisize FreeBSD, on the contrary. But it's a bit annoying to always get responses to all HD related stuff that "your HW is failing", when everything you've done for the last week is tests which claim it isn't. I'm not familiar with the innards of FreeBSD, so could someone explain why FreeBSD is so picky about cabling? I'm pretty well-read in physics, so the theory of FreeBSD using less-energetic electrons to pass data in the cables doesn't seem to hold up (insert smiley here). I mean, if other operating systems don't do some sort of error checking to exclude the errors on HD/CD-ROM drives that make FreeBSD hiccup, then what's up? --Ville ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
I did a make -j80 buildworld and this is about the worse that it got. The build finished without freezes of any kind. last pid: 98605; load averages: 19.98, 14.50, 10.16 up 0+00:52:34 15:54:35 45 processes: 1 running, 43 sleeping, 1 zombie CPU states: 14.8% user, 0.0% nice, 5.1% system, 0.2% interrupt, 79.9% idle Mem: 19M Active, 494M Inact, 158M Wired, 44K Cache, 112M Buf, 1331M Free Swap: 4096M Total, 4096M Free So I ran it again with two big tarballs being made in the background and that one finished too as did the tarballs in a very timely manner. I think I have found some stability and performance for my new machines. Thanks for all the help guys. The skies look so much bluer and brighter today.. ;-) Cheers, -- Wil Hatfield ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
I am giving 6.1 a whirl. In the first 5 minutes I have already noticed that there are some obvious filesystem issues fixed. I ran a tar and compared the speed to that on one of my 4.x boxes and low and behold they are about the same. THANK GOD! Now I didn't put your -j100 to the test but I did give a -j20 a shot. No DMA issues, no kernel panics, and actually pretty good performance overall. 109 processes: 20 running, 88 sleeping, 1 zombie CPU states: 98.0% user, 0.0% nice, 2.0% system, 0.0% interrupt, 0.0% idle Mem: 147M Active, 72M Inact, 109M Wired, 112M Buf, 1673M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 49641 root1 1290 12476K 11880K RUN1 0:01 45.00% cc1 49487 root1 1210 10148K 9584K CPU3 0 0:01 29.60% cc1 49585 root1 1210 12780K 12220K RUN0 0:01 28.71% cc1 49653 root1 1290 11036K 10428K RUN3 0:00 27.00% cc1 49649 root1 1280 9476K 8880K RUN1 0:00 24.00% cc1 49571 root1 1210 12540K 11972K RUN0 0:01 22.06% cc1 49592 root1 1210 11728K 11104K RUN0 0:00 13.31% cc1 49618 root1 1220 10684K 10116K RUN0 0:01 12.61% cc1 49599 root1 1210 10924K 10352K CPU1 0 0:00 12.26% cc1 49595 root1 1210 10576K 10012K RUN0 0:00 11.91% cc1 49632 root1 1210 10876K 10312K CPU2 0 0:00 10.85% cc1 49605 root1 1210 10704K 10132K RUN0 0:00 10.50% cc1 49630 root1 1210 10656K 10088K RUN0 0:00 10.50% cc1 49603 root1 1210 10864K 10296K RUN0 0:00 10.50% cc1 49621 root1 1210 10712K 10144K RUN0 0:00 8.75% cc1 49637 root1 1210 10920K 10300K RUN0 0:00 8.75% cc1 49611 root1 1210 10936K 10364K RUN0 0:00 8.40% cc1 49470 root1 80 3576K 3464K ppwait 2 0:00 3.50% make 588 root1 960 6120K 3096K select 0 0:03 0.00% sshd 37381 root1 960 548K 436K select 0 0:00 0.00% make 37467 root1 960 808K 696K select 0 0:00 0.00% make 37380 root1 960 2472K 1720K CPU0 0 0:00 0.00% top 597 root1 960 6080K 3080K select 0 0:00 0.00% sshd 47338 root1 960 772K 664K select 0 0:00 0.00% make 603 root1 200 5108K 3200K pause 2 0:00 0.00% csh 594 root1 200 4852K 2880K pause 0 0:00 0.00% csh Now off to try to kill it some more. -- Wil Hatfield -Original Message- From: Anish Mistry [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 6:42 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield Subject: Re: ATA Drive Issues On Friday 31 March 2006 21:28, Wil Hatfield wrote: > Beto, > > > fair enough, but you should be able to use some of the > > performance testing tools to hammer the server before pushing it > > live. > > Suggestions for tools that REALLY hammer? "make -j100 buildworld" is always fun :) > > > -- > Wil Hatfield > > > > -Original Message- > From: Norberto Meijome [mailto:[EMAIL PROTECTED] > Sent: Friday, March 31, 2006 5:17 PM > To: Wil Hatfield > Cc: freebsd-questions@freebsd.org > Subject: Re: ATA Drive Issues > > > On Fri, 31 Mar 2006 18:00:34 -0800 > > "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > > Beto, > > > > I am currently trying to upgrade one without customers on it to > > 6.0. But as was the problem with 5.4 the problems don't show up > > until the machine is under high load. So even under 6 I won't > > have a clue if the issues are fixed until I get the customers on > > it. So it doesn't make alot of difference. > > fair enough, but you should be able to use some of the performance > testing tools to hammer the server before pushing it live. > > > I checked with the manufacturer or the machine and they assure me > > that they installed brand new high quality 80/40 cables. But then > > again what did I expect them to say. So do you know of a good > > high quality 80/40 manufacture and where I can buy some new > > cables? What's the best of the best? > > not really - i had my bad experience with cables, just went out, > got the ones that a) weren't 10 for a buck , b) actually looked > well built. I just went to my preferred provider here in town > (eer... "online" actually...but they are local (Syd, AU) ) > > > At Supermicro's recommendation I already phlashed to the latest > > bios. > > cool - but my point was not to assume that new bios would be better > - it may actually be a step backwards when combined with your other > hardware and software. > > > Well it is good to know you think 6 is b
RE: ATA Drive Issues
At 05:52 PM 3/31/2006, fbsd_user wrote: Hay I am ran ata HD on 5.4 and now on 6.0 with out any problems. Your problems may be caused by your HD starting to go bad. You didn't say if you're running plain [parrallel] ATA or Serial ATA. Nearly two years ago I tried to replace our Samba file server with a new box running SATA with the Adaptec controller (1210??) based on the SiI 3112 chipset (same one ragged on here a couple days ago) and FBSD 5.something. Never made it into production -- same hangs you describe. I filed this issue: kern/70379: System hangs under heavy disk IO with SiI 3112 SATA150 There were a couple related fixes, but none completely cured it. I switched to a Promise SATA controller, and the problem was lessened to the point the machine was usable. But I can still make it hang just tar'ing a file system to a tar file on the same drive. Just bought a new Dell SC430 with SATA to replace the whole thing. Running 6.0 for a week now, and it seems solid. It's all Intel electronics: atapci0: . Don't know if the controllers are junk, or it's a FBSD issue. Once the new machine is swapped in, I plan to experiment with 6.0 on the old one to see. -Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Fri, 31 Mar 2006 18:28:09 -0800 "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > > fair enough, but you should be able to use some of the performance > > testing tools to hammer the server before pushing it live. > > Suggestions for tools that REALLY hammer? if it's going to be a webserver, use ab (apache's benchmark tool) to simulate high traffic. at the same time, you could run other tools on the server itself (bonny (sp?) from memory, etc). building the kernel (-j[num_cpuX2) ) seems like a nice way to add some load to the box... do a search in /usr/ports/sysutils for benchmarking utils. good luck B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
I'm not that frustrated. ;-) -- Wil Hatfield -Original Message- From: Anish Mistry [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 6:42 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield Subject: Re: ATA Drive Issues On Friday 31 March 2006 21:28, Wil Hatfield wrote: > Beto, > > > fair enough, but you should be able to use some of the > > performance testing tools to hammer the server before pushing it > > live. > > Suggestions for tools that REALLY hammer? "make -j100 buildworld" is always fun :) > > > -- > Wil Hatfield > > > > -Original Message- > From: Norberto Meijome [mailto:[EMAIL PROTECTED] > Sent: Friday, March 31, 2006 5:17 PM > To: Wil Hatfield > Cc: freebsd-questions@freebsd.org > Subject: Re: ATA Drive Issues > > > On Fri, 31 Mar 2006 18:00:34 -0800 > > "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > > Beto, > > > > I am currently trying to upgrade one without customers on it to > > 6.0. But as was the problem with 5.4 the problems don't show up > > until the machine is under high load. So even under 6 I won't > > have a clue if the issues are fixed until I get the customers on > > it. So it doesn't make alot of difference. > > fair enough, but you should be able to use some of the performance > testing tools to hammer the server before pushing it live. > > > I checked with the manufacturer or the machine and they assure me > > that they installed brand new high quality 80/40 cables. But then > > again what did I expect them to say. So do you know of a good > > high quality 80/40 manufacture and where I can buy some new > > cables? What's the best of the best? > > not really - i had my bad experience with cables, just went out, > got the ones that a) weren't 10 for a buck , b) actually looked > well built. I just went to my preferred provider here in town > (eer... "online" actually...but they are local (Syd, AU) ) > > > At Supermicro's recommendation I already phlashed to the latest > > bios. > > cool - but my point was not to assume that new bios would be better > - it may actually be a step backwards when combined with your other > hardware and software. > > > Well it is good to know you think 6 is better than 5.4. But then > > again you are running SATA and we all know 6 runs SATA better. > > Hopefully it runs ATA better too. > > actually, that's the only box with SATA - all the others run PATA > or SCSI. > B > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Anish Mistry [EMAIL PROTECTED] AM Productions http://am-productions.biz/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Friday 31 March 2006 21:28, Wil Hatfield wrote: > Beto, > > > fair enough, but you should be able to use some of the > > performance testing tools to hammer the server before pushing it > > live. > > Suggestions for tools that REALLY hammer? "make -j100 buildworld" is always fun :) > > > -- > Wil Hatfield > > > > -Original Message- > From: Norberto Meijome [mailto:[EMAIL PROTECTED] > Sent: Friday, March 31, 2006 5:17 PM > To: Wil Hatfield > Cc: freebsd-questions@freebsd.org > Subject: Re: ATA Drive Issues > > > On Fri, 31 Mar 2006 18:00:34 -0800 > > "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > > Beto, > > > > I am currently trying to upgrade one without customers on it to > > 6.0. But as was the problem with 5.4 the problems don't show up > > until the machine is under high load. So even under 6 I won't > > have a clue if the issues are fixed until I get the customers on > > it. So it doesn't make alot of difference. > > fair enough, but you should be able to use some of the performance > testing tools to hammer the server before pushing it live. > > > I checked with the manufacturer or the machine and they assure me > > that they installed brand new high quality 80/40 cables. But then > > again what did I expect them to say. So do you know of a good > > high quality 80/40 manufacture and where I can buy some new > > cables? What's the best of the best? > > not really - i had my bad experience with cables, just went out, > got the ones that a) weren't 10 for a buck , b) actually looked > well built. I just went to my preferred provider here in town > (eer... "online" actually...but they are local (Syd, AU) ) > > > At Supermicro's recommendation I already phlashed to the latest > > bios. > > cool - but my point was not to assume that new bios would be better > - it may actually be a step backwards when combined with your other > hardware and software. > > > Well it is good to know you think 6 is better than 5.4. But then > > again you are running SATA and we all know 6 runs SATA better. > > Hopefully it runs ATA better too. > > actually, that's the only box with SATA - all the others run PATA > or SCSI. > B > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Anish Mistry [EMAIL PROTECTED] AM Productions http://am-productions.biz/ pgp49Wxe3ASSc.pgp Description: PGP signature
RE: ATA Drive Issues
Beto, > fair enough, but you should be able to use some of the performance > testing tools to hammer the server before pushing it live. Suggestions for tools that REALLY hammer? -- Wil Hatfield -Original Message- From: Norberto Meijome [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 5:17 PM To: Wil Hatfield Cc: freebsd-questions@freebsd.org Subject: Re: ATA Drive Issues On Fri, 31 Mar 2006 18:00:34 -0800 "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > Beto, > > I am currently trying to upgrade one without customers on it to 6.0. > But as was the problem with 5.4 the problems don't show up until the > machine is under high load. So even under 6 I won't have a clue if > the issues are fixed until I get the customers on it. So it doesn't > make alot of difference. fair enough, but you should be able to use some of the performance testing tools to hammer the server before pushing it live. > > I checked with the manufacturer or the machine and they assure me > that they installed brand new high quality 80/40 cables. But then > again what did I expect them to say. So do you know of a good high > quality 80/40 manufacture and where I can buy some new cables? What's > the best of the best? not really - i had my bad experience with cables, just went out, got the ones that a) weren't 10 for a buck , b) actually looked well built. I just went to my preferred provider here in town (eer... "online" actually...but they are local (Syd, AU) ) > > At Supermicro's recommendation I already phlashed to the latest bios. > cool - but my point was not to assume that new bios would be better - it may actually be a step backwards when combined with your other hardware and software. > Well it is good to know you think 6 is better than 5.4. But then > again you are running SATA and we all know 6 runs SATA better. > Hopefully it runs ATA better too. actually, that's the only box with SATA - all the others run PATA or SCSI. B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Fri, 31 Mar 2006 18:00:34 -0800 "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > Beto, > > I am currently trying to upgrade one without customers on it to 6.0. > But as was the problem with 5.4 the problems don't show up until the > machine is under high load. So even under 6 I won't have a clue if > the issues are fixed until I get the customers on it. So it doesn't > make alot of difference. fair enough, but you should be able to use some of the performance testing tools to hammer the server before pushing it live. > > I checked with the manufacturer or the machine and they assure me > that they installed brand new high quality 80/40 cables. But then > again what did I expect them to say. So do you know of a good high > quality 80/40 manufacture and where I can buy some new cables? What's > the best of the best? not really - i had my bad experience with cables, just went out, got the ones that a) weren't 10 for a buck , b) actually looked well built. I just went to my preferred provider here in town (eer... "online" actually...but they are local (Syd, AU) ) > > At Supermicro's recommendation I already phlashed to the latest bios. > cool - but my point was not to assume that new bios would be better - it may actually be a step backwards when combined with your other hardware and software. > Well it is good to know you think 6 is better than 5.4. But then > again you are running SATA and we all know 6 runs SATA better. > Hopefully it runs ATA better too. actually, that's the only box with SATA - all the others run PATA or SCSI. B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
Just never seen that before out of WD. Seen it with Seagate though. So I guess it could happen. But there are 3 batches involved I believe. The 4 200GB could be from the same batch but unlikely. Purchased first two then the second two a month later. Wil Hatfield -Original Message- From: David Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 5:54 PM To: FreeBSD Questions Cc: Wil Hatfield Subject: Re: ATA Drive Issues On Mar 31, 2006, at 6:25 PM, Wil Hatfield wrote: > So are you saying that I have 5 new drives (a week old) all with > the same > problems? And S.M.A.R.T doesn't show any of the issues. > > I need to go play the lottery. ;-) Whats so strange about the notion of 5 identical new drives out of the same batch having the same problem? -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
Beto, I am currently trying to upgrade one without customers on it to 6.0. But as was the problem with 5.4 the problems don't show up until the machine is under high load. So even under 6 I won't have a clue if the issues are fixed until I get the customers on it. So it doesn't make alot of difference. I checked with the manufacturer or the machine and they assure me that they installed brand new high quality 80/40 cables. But then again what did I expect them to say. So do you know of a good high quality 80/40 manufacture and where I can buy some new cables? What's the best of the best? At Supermicro's recommendation I already phlashed to the latest bios. Well it is good to know you think 6 is better than 5.4. But then again you are running SATA and we all know 6 runs SATA better. Hopefully it runs ATA better too. -- Wil Hatfield -Original Message- From: Norberto Meijome [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 4:48 PM To: Wil Hatfield Cc: freebsd-questions@freebsd.org Subject: Re: ATA Drive Issues On Fri, 31 Mar 2006 15:43:35 -0800 "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > Ok I am just nervous about going to 6.x and putting these customers > through this not once more, but twice when I have to go back to 4.x. Sorry for asking the obvious, but why not try with 6 without any customers on the servers? putting new hardware/software straight into production seems to me like looking for troubles. Anyway, back to the problem at hand, just because they ARE new doesn't mean the cables/drives are NOT bad. Granted, that many drives in a bad state would be weird...but not really if they are from the same manufacturer's batch. smartmon clearing them would suggest that it's cabling issue. seriously, TRYING new good quality cables from a different provider can't be that hard/expensive? alternatively, try different BIOS version. usually a new version of the bIOS fixes problems. BUT I have a server (dual amd64 TYAN box, 2x SATA-I controllers with 4 SATA-II drives) which would simply not boot with a newer version of the bios, so I left it at the original BIOS (yes, keep backups of your BIOS upgrades! :-) . FWIW, 6 is better than 5.4, at least for me. good luck, Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Mar 31, 2006, at 6:25 PM, Wil Hatfield wrote: So are you saying that I have 5 new drives (a week old) all with the same problems? And S.M.A.R.T doesn't show any of the issues. I need to go play the lottery. ;-) Whats so strange about the notion of 5 identical new drives out of the same batch having the same problem? -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Fri, 31 Mar 2006 15:43:35 -0800 "Wil Hatfield" <[EMAIL PROTECTED]> wrote: > Ok I am just nervous about going to 6.x and putting these customers > through this not once more, but twice when I have to go back to 4.x. Sorry for asking the obvious, but why not try with 6 without any customers on the servers? putting new hardware/software straight into production seems to me like looking for troubles. Anyway, back to the problem at hand, just because they ARE new doesn't mean the cables/drives are NOT bad. Granted, that many drives in a bad state would be weird...but not really if they are from the same manufacturer's batch. smartmon clearing them would suggest that it's cabling issue. seriously, TRYING new good quality cables from a different provider can't be that hard/expensive? alternatively, try different BIOS version. usually a new version of the bIOS fixes problems. BUT I have a server (dual amd64 TYAN box, 2x SATA-I controllers with 4 SATA-II drives) which would simply not boot with a newer version of the bios, so I left it at the original BIOS (yes, keep backups of your BIOS upgrades! :-) . FWIW, 6 is better than 5.4, at least for me. good luck, Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
David, So are you saying that I have 5 new drives (a week old) all with the same problems? And S.M.A.R.T doesn't show any of the issues. I need to go play the lottery. ;-) -- Wil Hatfield -Original Message- From: David Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 3:50 PM To: FreeBSD Questions Cc: Wil Hatfield Subject: Re: ATA Drive Issues On Mar 31, 2006, at 4:52 PM, fbsd_user wrote: > Your problems may be caused by your HD starting to go bad. I agree. Its the classic symptoms of cable, power supply noise, and/ or HD CPU going sour. I have a brand new drive here with similar problems. And its twin from the same batch without. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Mar 31, 2006, at 4:52 PM, fbsd_user wrote: Your problems may be caused by your HD starting to go bad. I agree. Its the classic symptoms of cable, power supply noise, and/ or HD CPU going sour. I have a brand new drive here with similar problems. And its twin from the same batch without. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
Yah but I didn't see it as being "fixed" in 6.x either. That is why I mentioned the lack of acknowledgement. If there wasn't a bug acknowledged and tracked how can it be fixed? Perhaps none of the Write_DMA problemed folks have gone to 6.x and when they finally do the problem with show up again. Who knows. I guess maybe I am supposed to be that person. Ok I am just nervous about going to 6.x and putting these customers through this not once more, but twice when I have to go back to 4.x. So far I have the Write_DMA problems and Fatal Traps that claim /dev/ad0 to be the problem. Three outages today. Maybe it is time to look into the penguin. -- Wil Hatfield -Original Message- From: Anish Mistry [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 3:34 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield Subject: Re: ATA Drive Issues On Friday 31 March 2006 17:45, Wil Hatfield wrote: > I was afraid Soren was going to be mentioned. Well shouldn't the > FreeBSD 5.4 release information state that it isn't recommended for > machines with ATA drives? I really have no way of downgrading to > 5.3 without losing a couple hundred customers over it. But with > all these filesystem freezes I guess I will eventually lose them > anyways. > > Without the acknowledgement of the bugs and proper bug tracking I > doubt that these issues are going to get fixed in 5.5 or 6.1 > either. It seems the ATA issues are being ignored. How can a > release make it this far down the branch without fixing the good > old ATA drive issues first? ATA on 6.x and CURRENT are being maintained by Soren, just not 5.x. Moving to 6.x should fix the problem. Checking gnats only shows outstanding WRITE_DMA issues for 5.x. > > Cheers, > > -- > Wil Hatfield > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Anish > Mistry Sent: Friday, March 31, 2006 2:29 PM > To: freebsd-questions@freebsd.org > Cc: Wil Hatfield - HyperConX > Subject: Re: ATA Drive Issues > > On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > > What is the problem with 5.4 and ATA drives? I am running the > > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > > drives, no raids and no scsi anything. Every now and then under a > > bit of load the harddrive freezes with either a kernel panic or a > > Write_DMA error. I have to reboot the machine and run fsck -y to > > recover. Sometimes I have to run it twice. > >From my understanding ATA in 5.4 is slightly broken since Soren > > hasn't > > actually touched that code. The last time he touched the 5.x > branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a > while back. My tape drive disappeared :(. I didn't have time to > investigate, so I just backed down to 5.3, which works fine while I > work up a schedule to migrate to 6.X. > > -- > Anish Mistry > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Anish Mistry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Friday 31 March 2006 17:45, Wil Hatfield wrote: > I was afraid Soren was going to be mentioned. Well shouldn't the > FreeBSD 5.4 release information state that it isn't recommended for > machines with ATA drives? I really have no way of downgrading to > 5.3 without losing a couple hundred customers over it. But with > all these filesystem freezes I guess I will eventually lose them > anyways. > > Without the acknowledgement of the bugs and proper bug tracking I > doubt that these issues are going to get fixed in 5.5 or 6.1 > either. It seems the ATA issues are being ignored. How can a > release make it this far down the branch without fixing the good > old ATA drive issues first? ATA on 6.x and CURRENT are being maintained by Soren, just not 5.x. Moving to 6.x should fix the problem. Checking gnats only shows outstanding WRITE_DMA issues for 5.x. > > Cheers, > > -- > Wil Hatfield > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Anish > Mistry Sent: Friday, March 31, 2006 2:29 PM > To: freebsd-questions@freebsd.org > Cc: Wil Hatfield - HyperConX > Subject: Re: ATA Drive Issues > > On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > > What is the problem with 5.4 and ATA drives? I am running the > > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > > drives, no raids and no scsi anything. Every now and then under a > > bit of load the harddrive freezes with either a kernel panic or a > > Write_DMA error. I have to reboot the machine and run fsck -y to > > recover. Sometimes I have to run it twice. > >From my understanding ATA in 5.4 is slightly broken since Soren > > hasn't > > actually touched that code. The last time he touched the 5.x > branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a > while back. My tape drive disappeared :(. I didn't have time to > investigate, so I just backed down to 5.3, which works fine while I > work up a schedule to migrate to 6.X. > > -- > Anish Mistry > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Anish Mistry pgpIfXzpnXLP8.pgp Description: PGP signature
RE: ATA Drive Issues
5 brand new harddrives all going bad within 5 hours of installing FreeBSD 5.4? Not likely. And as I said smarttools reports there are no issues with any of the drives. What size/type/manufacturer are your ATA drives that you are running 5.4 with? -- Wil Hatfield -Original Message- From: fbsd_user [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 2:52 PM To: Wil Hatfield; freebsd-questions@freebsd.org Subject: RE: ATA Drive Issues Hay I am ran ata HD on 5.4 and now on 6.0 with out any problems. Your problems may be caused by your HD starting to go bad. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wil Hatfield Sent: Friday, March 31, 2006 5:46 PM To: freebsd-questions@freebsd.org Subject: RE: ATA Drive Issues I was afraid Soren was going to be mentioned. Well shouldn't the FreeBSD 5.4 release information state that it isn't recommended for machines with ATA drives? I really have no way of downgrading to 5.3 without losing a couple hundred customers over it. But with all these filesystem freezes I guess I will eventually lose them anyways. Without the acknowledgement of the bugs and proper bug tracking I doubt that these issues are going to get fixed in 5.5 or 6.1 either. It seems the ATA issues are being ignored. How can a release make it this far down the branch without fixing the good old ATA drive issues first? Cheers, -- Wil Hatfield -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anish Mistry Sent: Friday, March 31, 2006 2:29 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield - HyperConX Subject: Re: ATA Drive Issues On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > What is the problem with 5.4 and ATA drives? I am running the > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > drives, no raids and no scsi anything. Every now and then under a > bit of load the harddrive freezes with either a kernel panic or a > Write_DMA error. I have to reboot the machine and run fsck -y to > recover. Sometimes I have to run it twice. >From my understanding ATA in 5.4 is slightly broken since Soren hasn't actually touched that code. The last time he touched the 5.x branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a while back. My tape drive disappeared :(. I didn't have time to investigate, so I just backed down to 5.3, which works fine while I work up a schedule to migrate to 6.X. -- Anish Mistry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
Hay I am ran ata HD on 5.4 and now on 6.0 with out any problems. Your problems may be caused by your HD starting to go bad. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wil Hatfield Sent: Friday, March 31, 2006 5:46 PM To: freebsd-questions@freebsd.org Subject: RE: ATA Drive Issues I was afraid Soren was going to be mentioned. Well shouldn't the FreeBSD 5.4 release information state that it isn't recommended for machines with ATA drives? I really have no way of downgrading to 5.3 without losing a couple hundred customers over it. But with all these filesystem freezes I guess I will eventually lose them anyways. Without the acknowledgement of the bugs and proper bug tracking I doubt that these issues are going to get fixed in 5.5 or 6.1 either. It seems the ATA issues are being ignored. How can a release make it this far down the branch without fixing the good old ATA drive issues first? Cheers, -- Wil Hatfield -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anish Mistry Sent: Friday, March 31, 2006 2:29 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield - HyperConX Subject: Re: ATA Drive Issues On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > What is the problem with 5.4 and ATA drives? I am running the > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > drives, no raids and no scsi anything. Every now and then under a > bit of load the harddrive freezes with either a kernel panic or a > Write_DMA error. I have to reboot the machine and run fsck -y to > recover. Sometimes I have to run it twice. >From my understanding ATA in 5.4 is slightly broken since Soren hasn't actually touched that code. The last time he touched the 5.x branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a while back. My tape drive disappeared :(. I didn't have time to investigate, so I just backed down to 5.3, which works fine while I work up a schedule to migrate to 6.X. -- Anish Mistry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ATA Drive Issues
I was afraid Soren was going to be mentioned. Well shouldn't the FreeBSD 5.4 release information state that it isn't recommended for machines with ATA drives? I really have no way of downgrading to 5.3 without losing a couple hundred customers over it. But with all these filesystem freezes I guess I will eventually lose them anyways. Without the acknowledgement of the bugs and proper bug tracking I doubt that these issues are going to get fixed in 5.5 or 6.1 either. It seems the ATA issues are being ignored. How can a release make it this far down the branch without fixing the good old ATA drive issues first? Cheers, -- Wil Hatfield -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anish Mistry Sent: Friday, March 31, 2006 2:29 PM To: freebsd-questions@freebsd.org Cc: Wil Hatfield - HyperConX Subject: Re: ATA Drive Issues On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > What is the problem with 5.4 and ATA drives? I am running the > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > drives, no raids and no scsi anything. Every now and then under a > bit of load the harddrive freezes with either a kernel panic or a > Write_DMA error. I have to reboot the machine and run fsck -y to > recover. Sometimes I have to run it twice. >From my understanding ATA in 5.4 is slightly broken since Soren hasn't actually touched that code. The last time he touched the 5.x branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a while back. My tape drive disappeared :(. I didn't have time to investigate, so I just backed down to 5.3, which works fine while I work up a schedule to migrate to 6.X. -- Anish Mistry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Drive Issues
On Friday 31 March 2006 17:08, Wil Hatfield - HyperConX wrote: > What is the problem with 5.4 and ATA drives? I am running the > latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA > drives, no raids and no scsi anything. Every now and then under a > bit of load the harddrive freezes with either a kernel panic or a > Write_DMA error. I have to reboot the machine and run fsck -y to > recover. Sometimes I have to run it twice. From my understanding ATA in 5.4 is slightly broken since Soren hasn't actually touched that code. The last time he touched the 5.x branch was for 5.3. I had a weird issue with a 5.3->5.4 upgrade a while back. My tape drive disappeared :(. I didn't have time to investigate, so I just backed down to 5.3, which works fine while I work up a schedule to migrate to 6.X. -- Anish Mistry pgp0NZXsOaVjE.pgp Description: PGP signature
ATA Drive Issues
What is the problem with 5.4 and ATA drives? I am running the latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA drives, no raids and no scsi anything. Every now and then under a bit of load the harddrive freezes with either a kernel panic or a Write_DMA error. I have to reboot the machine and run fsck -y to recover. Sometimes I have to run it twice. As per several posts that were similar I have the following uneffectively enabled in my loader.conf file. hw.ata.ata_dma=0 hw.ata.atapi_dma=0 However, this hasn't fixed the problem. From the amount of issues similar to mine I am going to take a whack at the fact that I don't think it is strickly a DMA or drive issue. The DMA issue is just the result of a deeper underlying problem. Maybe something in the kernel or drivers. This same issue is relevant for 3 brand new Supermicro machines all running nearly the same Western Digital drives. 4 drives are 200GB WDs and 1 is a 160GB WD. All with brand new cables. Since this is all brand new equipment please don't pass this off as a bad cable. It isn't. As for the drives I have smarttools running on these systems now and there are no bad sectors and the drive health is all clean. Absolutely no issues as reported by smarttools. No changes in any of the attributes at all. Here is some more info: --dmesg.today snippet-- Copyright (c) 1992-2005 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 5.4-RELEASE-p11 #0: Tue Mar 28 17:18:36 PST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2146893824 (2047 MB) avail memory = 2099638272 (2002 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 0.0 on pci2 pci3: on pcib3 pci2: at device 0.1 (no driver attached) pcib4: at device 0.2 on pci2 pci4: on pcib4 em0: port 0x2000-0x203f mem 0xdd20-0xdd21 irq 54 at device 2.0 on pci4 em0: Ethernet address: 00:30:48:2c:c3:80 em0: Speed:N/A Duplex:N/A em1: port 0x2040-0x207f mem 0xdd22-0xdd23 irq 55 at device 2.1 on pci4 em1: Ethernet address: 00:30:48:2c:c3:81 em1: Speed:N/A Duplex:N/A pci2: at device 0.3 (no driver attached) pcib5: irq 16 at device 4.0 on pci0 pci5: on pcib5 pcib6: at device 0.0 on pci5 pci6: on pcib6 pci5: at device 0.1 (no driver attached) pcib7: at device 0.2 on pci5 pci7: on pcib7 pci5: at device 0.3 (no driver attached) pcib8: irq 16 at device 6.0 on pci0 pci8: on pcib8 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.3 (no driver attached) pci0: at device 29.7 (no driver attached) pcib9: at device 30.0 on pci0 pci9: on pcib9 pci9: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x14a0-0x14af,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xc8000-0xc8fff,0xc-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging unlimited ad0: 190782MB [387621/16/63] at ata0-master PIO4 ad1: 190782MB [387621/16/63] at ata0-slave P
ATA Drive Issues
What is the problem with 5.4 and ATA drives? I am running the latest release of FreeBSD 5.4-RELEASE-p11. I have two basic ATA drives, no raids and no scsi anything. Every now and then under a bit of load the harddrive freezes with either a kernel panic or a Write_DMA error. I have to reboot the machine and run fsck -y to recover. Sometimes I have to run it twice. As per several posts that were similar I have the following uneffectively enabled in my loader.conf file. hw.ata.ata_dma=0 hw.ata.atapi_dma=0 However, this hasn't fixed the problem. From the amount of issues similar to mine I am going to take a whack at the fact that I don't think it is strickly a DMA or drive issue. The DMA issue is just the result of a deeper underlying problem. Maybe something in the kernel or drivers. This same issue is relevant for 3 brand new Supermicro machines all running nearly the same Western Digital drives. 4 drives are 200GB WDs and 1 is a 160GB WD. All with brand new cables. Since this is all brand new equipment please don't pass this off as a bad cable. It isn't. As for the drives I have smarttools running on these systems now and there are no bad sectors and the drive health is all clean. Absolutely no issues as reported by smarttools. No changes in any of the attributes at all. Here is some more info: --dmesg.today snippet-- Copyright (c) 1992-2005 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 5.4-RELEASE-p11 #0: Tue Mar 28 17:18:36 PST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2146893824 (2047 MB) avail memory = 2099638272 (2002 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 0.0 on pci2 pci3: on pcib3 pci2: at device 0.1 (no driver attached) pcib4: at device 0.2 on pci2 pci4: on pcib4 em0: port 0x2000-0x203f mem 0xdd20-0xdd21 irq 54 at device 2.0 on pci4 em0: Ethernet address: 00:30:48:2c:c3:80 em0: Speed:N/A Duplex:N/A em1: port 0x2040-0x207f mem 0xdd22-0xdd23 irq 55 at device 2.1 on pci4 em1: Ethernet address: 00:30:48:2c:c3:81 em1: Speed:N/A Duplex:N/A pci2: at device 0.3 (no driver attached) pcib5: irq 16 at device 4.0 on pci0 pci5: on pcib5 pcib6: at device 0.0 on pci5 pci6: on pcib6 pci5: at device 0.1 (no driver attached) pcib7: at device 0.2 on pci5 pci7: on pcib7 pci5: at device 0.3 (no driver attached) pcib8: irq 16 at device 6.0 on pci0 pci8: on pcib8 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.3 (no driver attached) pci0: at device 29.7 (no driver attached) pcib9: at device 30.0 on pci0 pci9: on pcib9 pci9: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x14a0-0x14af,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xc8000-0xc8fff,0xc-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging unlimited ad0: 190782MB [387621/16/63] at ata0-master PIO4 ad1: 190782MB [387621/16/63] at ata0-slave P
