Hi,
I've got a new machine and don't think I'm getting all
the speed out of it
that I should be. Any hints/ideas for what I can do
to make the most of my
new hardware?
FreeBSD 5.4-Release
Shuttle SN25P
Nvidia NForce 4 with SATA 150
WD Raptor HD
I ran atacontrol and it reports:
# atacontrol list
ATA channel 0:
Master: ad0 <Maxtor 6Y160P0/YAR41BW0> ATA/ATAPI
revision 7
Slave: acd0 <SONY DVD RW DRU-510A/1.0c> ATA/ATAPI
revision 6
ATA channel 1:
Master: no device present
Slave: no device present
ATA channel 2:
Master: no device present
Slave: no device present
ATA channel 3:
Master: ad6 <WDC WD740GD-00FLA2/31.08F31> Serial
ATA v1.0
Slave: no device present
ATA channel 4:
Master: no device present
Slave: no device present
ATA channel 5:
Master: no device present
Slave: no device present
# atacontrol mode 3
Master = UDMA33
Slave = BIOSPIO
It looks like the standard IDE port is being detected
as the nForce4 but the
SATA controllers aren't - they just get labelled
"GENERIC". Check it out
below.
A verbose dmesg reports:
atapci0: <nVidia nForce4 UDMA133 controller> port
0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at
device 6.0 on pci0
atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at
0xf000
ata0: channel #0 on atapci0
atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at
0x1f0
atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at
0x3f6
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata0-slave: stat=0x00 err=0x01 lsb=0x14 msb=0xeb
ata0: reset tp2 stat0=50 stat1=00
devices=0x9<ATAPI_SLAVE,ATA_MASTER>
ata0: [MPSAFE]
ata1: channel #1 on atapci0
atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at
0x170
atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at
0x376
ata1: reset tp1 mask=00 ostat0=ff ostat1=ff
ata1: [MPSAFE]
atapci1: <GENERIC ATA controller> port
0xd800-0xd80f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7
irq 20 at
device 7.0 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at
0xd800
atapci1: [MPSAFE]
ata2: channel #0 on atapci1
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at
0x9f0
atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at
0xbf0
ata2: reset tp1 mask=03 ostat0=7f ostat1=7f
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2-slave: stat=0x7f err=0xff lsb=0xff msb=0xff
ata2: reset tp2 stat0=ff stat1=ff devices=0x0
ata2: [MPSAFE]
ata3: channel #1 on atapci1
atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at
0x970
atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at
0xb70
ata3: reset tp1 mask=03 ostat0=50 ostat1=00
ata3-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata3-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00
ata3: reset tp2 stat0=50 stat1=00
devices=0x1<ATA_MASTER>
ata3: [MPSAFE]
atapci2: <GENERIC ATA controller> port
0xc400-0xc40f,0xb60-0xb63,0x960-0x967,0xbe0-0xbe3,0x9e0-0x9e7
irq 22 at
device 8.0 on pci0
atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at
0xc400
atapci2: [MPSAFE]
ata4: channel #0 on atapci2
atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at
0x9e0
atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at
0xbe0
ata4: reset tp1 mask=03 ostat0=7f ostat1=7f
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4-slave: stat=0x7f err=0xff lsb=0xff msb=0xff
ata4: reset tp2 stat0=ff stat1=ff devices=0x0
ata4: [MPSAFE]
ata5: channel #1 on atapci2
atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at
0x960
atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at
0xb60
ata5: reset tp1 mask=03 ostat0=7f ostat1=7f
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5-slave: stat=0x7f err=0xff lsb=0xff msb=0xff
ata5: reset tp2 stat0=ff stat1=ff devices=0x0
ata5: [MPSAFE]
Any hints/ideas for what I can do to make the most of
my new hardware?
Thanks,
Alan Bryan
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
On Wed, 18 May 2005, alan bryan wrote:> Hi, > > I've got a new machine and don't think I'm getting all the speed out of > it that I should be. Any hints/ideas for what I can do to make the most > of my new hardware? >Can you post the output of "pciconf -lv"? The nForce IDE controller is properly detected, but it looks like there's another one in the system. Looking at the spec for the system it may be the proprietary nVidia RAID controller. The pciconf output should help us identify if thats the issue.> FreeBSD 5.4-Release > Shuttle SN25P > Nvidia NForce 4 with SATA 150 > WD Raptor HD > > I ran atacontrol and it reports: > # atacontrol list > ATA channel 0: > Master: ad0 <Maxtor 6Y160P0/YAR41BW0> ATA/ATAPI > revision 7 > Slave: acd0 <SONY DVD RW DRU-510A/1.0c> ATA/ATAPI > revision 6 > ATA channel 1: > Master: no device present > Slave: no device present > ATA channel 2: > Master: no device present > Slave: no device present > ATA channel 3: > Master: ad6 <WDC WD740GD-00FLA2/31.08F31> Serial > ATA v1.0 > Slave: no device present > ATA channel 4: > Master: no device present > Slave: no device present > ATA channel 5: > Master: no device present > Slave: no device present > # atacontrol mode 3 > Master = UDMA33 > Slave = BIOSPIO > > It looks like the standard IDE port is being detected > as the nForce4 but the > SATA controllers aren't - they just get labelled > "GENERIC". Check it out > below. > A verbose dmesg reports: > atapci0: <nVidia nForce4 UDMA133 controller> port > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at > device 6.0 on pci0 > atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at > 0xf000 > ata0: channel #0 on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at > 0x1f0 > atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at > 0x3f6 > ata0: reset tp1 mask=03 ostat0=50 ostat1=00 > ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 > ata0-slave: stat=0x00 err=0x01 lsb=0x14 msb=0xeb > ata0: reset tp2 stat0=50 stat1=00 > devices=0x9<ATAPI_SLAVE,ATA_MASTER> > ata0: [MPSAFE] > ata1: channel #1 on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at > 0x170 > atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at > 0x376 > ata1: reset tp1 mask=00 ostat0=ff ostat1=ff > ata1: [MPSAFE] > atapci1: <GENERIC ATA controller> port > 0xd800-0xd80f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 > irq 20 at > device 7.0 on pci0 > atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at > 0xd800 > atapci1: [MPSAFE] > ata2: channel #0 on atapci1 > atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at > 0x9f0 > atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at > 0xbf0 > ata2: reset tp1 mask=03 ostat0=7f ostat1=7f > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2-slave: stat=0x7f err=0xff lsb=0xff msb=0xff > ata2: reset tp2 stat0=ff stat1=ff devices=0x0 > ata2: [MPSAFE] > ata3: channel #1 on atapci1 > atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at > 0x970 > atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at > 0xb70 > ata3: reset tp1 mask=03 ostat0=50 ostat1=00 > ata3-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 > ata3-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 > ata3: reset tp2 stat0=50 stat1=00 > devices=0x1<ATA_MASTER> > ata3: [MPSAFE] > atapci2: <GENERIC ATA controller> port > 0xc400-0xc40f,0xb60-0xb63,0x960-0x967,0xbe0-0xbe3,0x9e0-0x9e7 > irq 22 at > device 8.0 on pci0 > atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at > 0xc400 > atapci2: [MPSAFE] > ata4: channel #0 on atapci2 > atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at > 0x9e0 > atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at > 0xbe0 > ata4: reset tp1 mask=03 ostat0=7f ostat1=7f > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4-slave: stat=0x7f err=0xff lsb=0xff msb=0xff > ata4: reset tp2 stat0=ff stat1=ff devices=0x0 > ata4: [MPSAFE] > ata5: channel #1 on atapci2 > atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at > 0x960 > atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at > 0xb60 > ata5: reset tp1 mask=03 ostat0=7f ostat1=7f > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-master: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5-slave: stat=0x7f err=0xff lsb=0xff msb=0xff > ata5: reset tp2 stat0=ff stat1=ff devices=0x0 > ata5: [MPSAFE] > > Any hints/ideas for what I can do to make the most of > my new hardware? > > Thanks, > Alan Bryan > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >-- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
--- Doug White <dwhite@gumbysoft.com> wrote:> I guess turning off the RAID converts the chips into > standard SATA > controllers. I'll have to look into that. An nForce > 4 machine recently > appeared at work, so I'll see what I can get it to > do.That's my understanding. FYI: I also tried turning on "RAID" in the bios and not actually assigning any of the disks to any RAID sets and everthing behaved just the same so it does't seem to matter whether it's on or off in the bios (assuming no disks actually used in an array).> It looks like sos added support for atapci1 and 2 in > this listing in the > ATAmkIII patchset. While that patchset is in > -CURRENT you'll have to > apply the -stable patches yourself. Search the list > archives for the > location, soren posts it now and again.I upgraded my source from 5.4-RELEASE to 5-STABLE and applied the patchset, compiled a new kernel, installed it and rebooted. (This was the "n" version of ATAmkIII which I think is the latest.) It booted, I saw something about ATAPI2 and 3 and SATA and I got all excited for a second as I thought it was going to work. Then, a bunch of stuff flies by real fast and it ends with the following and then hard locks up. (manually retyped as the machine locks) ata2: CONNECT REQUESTED ata2: DISCONNECT REQUESTED ... (lots of those) subdisk6: detached ad6: detached ata2: SATA connect status=00000000 ata3: SATA connect ready time=0ms Any ideas? I'm confused about the attach/detach stuff as I'm not using any RAID, it's turned off in the bios. Just trying to get a single SATA drive to work. To further probe and test I tried physically moving the drive to other SATA sockets on the MB. When I did this I can get the system to boot up but it can't find the file systems. I manually told it where the root filesystem was. (it was now on ata5: so I told it ad10s1a, it then completed loading root filesystem)>From this point I thought, well, at least now I cantry atacontrol to see what's up. atacontrol mode 5 showed the disk still at UDMA33! I gave the command atacontrol mode 5 UDMA133 BIOSIO to try to set it higher but it didn't change anything. So, I'm now out of ideas. Anybody else have any? I could try -CURRENT but my understanding is that with the 5-STABLE and the patchset I'm pretty much the same ATA-wise, correct? Thanks for all the help thus far! --Alan Bryan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
> (manually retyped as the machine locks) > ata2: CONNECT REQUESTED > ata2: DISCONNECT REQUESTED > ... (lots of those) > subdisk6: detached > ad6: detached > ata2: SATA connect status=00000000 > ata3: SATA connect ready time=0msOK, it may not be so much a lock up as I was just a bit impatient. After a while it panics with: Fatal trap 12 Page fault while in kernel mode fault virtual address 0x20c There's a bunch more that I can write down if that helps. Maybe I need to take a digital picture of the screen before it reboots as I'm a slow writer. Thanks for the help, I'd love to have this thing running at it's capable speed potential. This is my main workstation/desktop. I could update to -CURRENT if anyone thinks that will solve the disk speed problem without causing too many more. (Just do average desktop stuff like KDE3) If -CURRENT is in too much flux right now though maybe I'm better off with working but slow. --Alan Bryan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Here's a recap of all the things I've tried and discovered in a bunch of testing today. Tried mkIII "m" patches and that doesn't show atapici1 or atapici2 - they just show as GENERIC with drives as UDMA33 Tried mkIII "n" patches and then atapici1 shows as nForce4 with SATA drives but has further problems detailed below. atapici2 always shows up in dmesg as GENERIC no matter what. Tried custom kernel, disabling all other parts of ATA with no difference. # 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 options ATA_STATIC_ID # Static device numbering Tried disabling the standard IDE ports in bios, turning off DMA on SATA, and other bios tweaks with no changes. With the "n" patches I get randomly alternating: lockup, Fatal trap 12 panic, or full boot but then it can't find the root filesystem as the disk is showing as detached. If I get lucky and it goes most of the way I get results like the following: ata2: CONNECT REQUESTED ata2: DISCONNECT REQUESTED ... (lots of those!) ad6: 70911MB <WDC WD740GD-00FLA2 31.08F31> at ata3-master SATA 150 ad6: detached ata3: DISCONNECTED ata2: CONNECTED ata2: SATA connect status=00000000 ata2: DISCONNECTED ata3: CONNECTED ata3: SATA connect ready time=0ms ... Mounting root from ufs:/dev/ad6s1a setrootbyname failed ffs_mountroot: can't find rootvp root mount failed:6 Is there something else I should try to help in debugging this further? Is there anything in -CURRENT that would help this to work better than 5-STABLE plus the ATA mkIII "n" patches? Thanks for all the help! --Alan Bryan --- Doug White <dwhite@gumbysoft.com> wrote:> On Fri, 20 May 2005, alan bryan wrote: > > > > > --- Doug White <dwhite@gumbysoft.com> wrote: > > > Can you post the output of "pciconf -lv"? The > nForce > > > IDE controller is > > > properly detected, but it looks like there's > another > > > one in the system. > > > Looking at the spec for the system it may be the > > > proprietary nVidia RAID > > > controller. The pciconf output should help us > > > identify if thats the > > > issue. > > > > FYI: RAID features are disabled in the BIOS, I'm > just > > trying to get a single SATA drive to work at full > > speed. The other drive in this system is IDE and > that > > seems to be working at proper speed. Thanks for > the > > help! > > I guess turning off the RAID converts the chips into > standard SATA > controllers. I'll have to look into that. An nForce > 4 machine recently > appeared at work, so I'll see what I can get it to > do. > > > atapci0@pci0:6:0: class=0x01018a > card=0x50361297 > > chip=0x005310de rev=0xa2 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > class = mass storage > > subclass = ATA > > atapci1@pci0:7:0: class=0x010185 > card=0x50361297 > > chip=0x005410de rev=0xa3 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > class = mass storage > > subclass = ATA > > atapci2@pci0:8:0: class=0x010185 > card=0xcb8410de > > chip=0x005510de rev=0xa3 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > class = mass storage > > subclass = ATA > > It looks like sos added support for atapci1 and 2 in > this listing in the > ATAmkIII patchset. While that patchset is in > -CURRENT you'll have to > apply the -stable patches yourself. Search the list > archives for the > location, soren posts it now and again. > > -- > Doug White | FreeBSD: The Power > to Serve > dwhite@gumbysoft.com | www.FreeBSD.org >__________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail
--- Søren Schmidt <sos@FreeBSD.org> wrote:> > Is there anything in -CURRENT that would help this > to > > work better than 5-STABLE plus the ATA mkIII "n" > > patches? > > Yes, I've done quite a bit of changes that affects > this on -current. > However its done blindfolded since I dont have a > nForce4 based system > here yet (but should soon). > > - SørenHow soon is "soon"? I may be able to send you some hardware too if that would be helpful. I tried a -CURRENT kernel today but didn't build/install world or anything else as I don't want to mess up this machines 5.4 installation. The result was that it now seems to identify all the atapici0 - atapici3 controllers and doesn't do the repeated DISCONNECTED/CONNECTED messages but it still panicked near the end of the bootup process, around the USB area. I called a friend today who has a spare SATA drive I can borrow so I'll be picking that up tomorrow and I'll swap out drives and do a fresh -CURRENT install tomorrow on that new drive to see if I can get it any further along towards a successful boot. I'll report back with my findings. Thanks for the help! --Alan Bryan __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/