From pyunyh at gmail.com Mon Sep 1 07:32:20 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Mon Sep 1 07:32:27 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <48B7A6AD.9020509@bah.homeip.net> References: <200808110000.58666.freebsd@razik.name> <48A317D8.5070702@bah.homeip.net> <48B78DE0.8070808@bah.homeip.net> <20080829060606.GC35562@cdnetworks.co.kr> <48B7A6AD.9020509@bah.homeip.net> Message-ID: <20080901073210.GE48568@cdnetworks.co.kr> On Fri, Aug 29, 2008 at 09:35:09AM +0200, Bernt Hansson wrote: > Pyun YongHyeon skrev: > > On Fri, Aug 29, 2008 at 07:49:20AM +0200, Bernt Hansson wrote: > > > > Lukas Razik: > > > >> Hello! > > > >> > > > >> I've a GigaByte GA-X48-DQ6 Motherboard with a "RTL8168/8111 PCI-E Gigabit > > > >> Ethernet NIC" and I've read that 7.0-RELEASE / amd64 should recognize these > > > >> cards (by the "re" driver) but it doesn't in my case. > > > > > > > > I got an Gigabyte GA-MA790FX-DS5 with the same network chip and it's > > > > working right out of the box. There are other issues with that motherboard. > > > > > > > > 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 > > > > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > > > > > > > re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x01 > > > > hdr=0x00 > > > > vendor = 'Realtek Semiconductor' > > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > > class = network > > > > subclass = ethernet > > > > > > > >> #uname -a : > > > >> FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 > > > >> root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > Just for the sake of it, I did an upgrade to 7.0-STABLE on 2008-08-20. > > > That killed my network card RTL8111B. > > > > Would you post the output of dmesg and "ifconfig re0"? > > Yes. But I reverted back to 7.0-RELEASE, so dmesg and ifconfig is for > that setup. > Ok, would you let me know what functionality of re(4) was broken in 7-stable? Just killed one's network is not enough to diagnose the problem. Did you ever tried to disable checksum offload on 7-stable? (i.e. ifconfig re0 -txcsum -rxcsum) -- Regards, Pyun YongHyeon From bernt at bah.homeip.net Mon Sep 1 11:06:08 2008 From: bernt at bah.homeip.net (Bernt Hansson) Date: Mon Sep 1 11:06:14 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <20080901073210.GE48568@cdnetworks.co.kr> References: <200808110000.58666.freebsd@razik.name> <48A317D8.5070702@bah.homeip.net> <48B78DE0.8070808@bah.homeip.net> <20080829060606.GC35562@cdnetworks.co.kr> <48B7A6AD.9020509@bah.homeip.net> <20080901073210.GE48568@cdnetworks.co.kr> Message-ID: <48BBCC93.40309@bah.homeip.net> Pyun YongHyeon skrev: > > > > Just for the sake of it, I did an upgrade to 7.0-STABLE on 2008-08-20. > > > > That killed my network card RTL8111B. > > > > > > Would you post the output of dmesg and "ifconfig re0"? > > > > Yes. But I reverted back to 7.0-RELEASE, so dmesg and ifconfig is for > > that setup. > > > > Ok, would you let me know what functionality of re(4) was broken in > 7-stable? Just killed one's network is not enough to diagnose the > problem. Did you ever tried to disable checksum offload on > 7-stable? (i.e. ifconfig re0 -txcsum -rxcsum) I didn't try fiddling with ifconfig. Ping and traceroute didn't work. Ping took anywere from 5 to 30 minutes to get a reply. From koitsu at FreeBSD.org Mon Sep 1 11:14:07 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Mon Sep 1 11:14:14 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <48BBCC93.40309@bah.homeip.net> References: <200808110000.58666.freebsd@razik.name> <48A317D8.5070702@bah.homeip.net> <48B78DE0.8070808@bah.homeip.net> <20080829060606.GC35562@cdnetworks.co.kr> <48B7A6AD.9020509@bah.homeip.net> <20080901073210.GE48568@cdnetworks.co.kr> <48BBCC93.40309@bah.homeip.net> Message-ID: <20080901111404.GA4765@icarus.home.lan> On Mon, Sep 01, 2008 at 01:05:55PM +0200, Bernt Hansson wrote: > Pyun YongHyeon skrev: > >> > > > Just for the sake of it, I did an upgrade to 7.0-STABLE on 2008-08-20. >> > > > That killed my network card RTL8111B. >> > > > > Would you post the output of dmesg and "ifconfig re0"? >> > > Yes. But I reverted back to 7.0-RELEASE, so dmesg and ifconfig is >> for >> > that setup. >> > >> >> Ok, would you let me know what functionality of re(4) was broken in >> 7-stable? Just killed one's network is not enough to diagnose the >> problem. Did you ever tried to disable checksum offload on >> 7-stable? (i.e. ifconfig re0 -txcsum -rxcsum) > > I didn't try fiddling with ifconfig. > Ping and traceroute didn't work. Ping took anywere from 5 to 30 minutes > to get a reply. Which is interesting, because I interpreted "that killed my network card" to mean "the re(4) code in RELENG_7 as of 2008/08/20 caused my network card to explode/die/burst into flames". Please try to be a little more precise when describing what problems you're having with a driver or hardware. Your above explanation ("ping and traceroute didn't work") is also too terse. bernt_hansson -vvv. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From don at sandvine.com Wed Sep 3 01:47:04 2008 From: don at sandvine.com (Don Bowman) Date: Wed Sep 3 01:47:11 2008 Subject: FreeBSD-AMD64 on Xeon MP Message-ID: On Mon Aug 11 21:23:58 UTC 2008 John Baldwin wrote: >On Monday 11 August 2008 11:25:01 am Michael Fuckner wrote: > > Hi all, > > > > I try to run FreeBSD-7-AMD64 on a Quad Xeon (Xeon MP 7320) and 32GB RAM. > > The Board is a X7QC3 by supermicro and the installation is done on > > another system, updated and plugged to this system. So I have a drive > > with 7-STABLE compiled today. > > > > The last line I see from dmesg is vga0- then the system freezes. > > > > Anyone using a similar configuration or knows what could be wrong? I > > still have some days left to play with it, before this box gets shipped > > to the customer. > > It is probably waiting for a config intr hook to complete. rwatson@ recently > added some code to HEAD to help with debugging hangs there. That patch > probably applies directly to 7.x and would be helpful in determining what is > hanging. So I have debugged this down (same board), using 32-bit kernel. I have found it is hanging reading from the UHCI controller (register 0x10). I am using HEAD. In uhci_root_ctrl_start(), in case C(UR_GET_STATUS, UT_READ_CLASS_OTHER):, it does: x = UREAD2(sc, port); now, this translates into a read from 0x3090 [UHCI base address is 0x3080, offset is 0x10 for the PORTSC0 register. I debugged this down by putting printf() in. I can't really fathom why that read would hang, does anyone have a suggestion on where to go next debugging? The chipset on this board is 631xESB/632xESB ICH. I tried putting a call to uhci_dumpregs() there, it hangs as well. So my assumption Is that a read to 0x3080 is hanging. Anyone have any suggestions? System has 4 XEON MP processors, Intel 7300 chipset, 1GB of RAM, motherboard is described http://www.supermicro.com/products/motherboard/Xeon7000/7300/X7QC3.cfm The IPMI is not installed. From ivoras at freebsd.org Wed Sep 3 08:07:53 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Wed Sep 3 08:08:06 2008 Subject: FreeBSD-AMD64 on Xeon MP In-Reply-To: References: Message-ID: Don Bowman wrote: > I tried putting a call to uhci_dumpregs() there, it hangs as well. So my > assumption > Is that a read to 0x3080 is hanging. > > Anyone have any suggestions? If the same thing that worked for me works for you (booting Linux before soft-rebooting into FreeBSD) than it would look like something isn't initialized right. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20080903/444d380f/signature.pgp From don at sandvine.com Wed Sep 3 17:01:54 2008 From: don at sandvine.com (Don Bowman) Date: Wed Sep 3 17:02:00 2008 Subject: FreeBSD-AMD64 on Xeon MP In-Reply-To: References: Message-ID: >From Ivan Voras > Don Bowman wrote: > > > I tried putting a call to uhci_dumpregs() there, it hangs as well. So > > my assumption Is that a read to 0x3080 is hanging. > > > > Anyone have any suggestions? > > If the same thing that worked for me works for you (booting Linux > before soft-rebooting into FreeBSD) than it would look like something > isn't initialized right. I am focusing in on SMM emulation. http://www.ussg.indiana.edu/hypermail/linux/kernel/0407.3/0688.html suggests something to me. What if I am executing this on a processor other than the boot processor, and the SMM code doesn't expect this? I'm not sure where I would try this patch in freebsd, but it seems promising. Ie I read 0xe090. This trips SMM for legacy(?). SMM is entered, does something, corrupts, leaves, and then a few instructions later I crash. The suggested workaround for this (different machine and OS) is to disable the legacy mode. FreeBSD seems to do this already I think, calling: pci_write_config(self, PCI_LEGSUP, PCI_LEGSUP_USBPIRQDEN, 2); in uhci_pci_attach() From freebsd at razik.name Thu Sep 4 17:45:46 2008 From: freebsd at razik.name (Lukas Razik) Date: Thu Sep 4 17:45:54 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <48A34FF0.3010304@razik.name> References: <200808110000.58666.freebsd@razik.name> <48A317D8.5070702@bah.homeip.net> <48A34FF0.3010304@razik.name> Message-ID: <200809041945.08368.freebsd@razik.name> Hello again! I'm back home and I still have the issue with my onboard RTL8168 NIC I've described here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2008/freebsd- hardware/20080817.freebsd-hardware As I wrote you in one of my old mails I've tested 7.0-RELEASE and 7.0-STABLE-200807 and my NIC isn't recognised by both kernel versions. So I also would like to try more current 7.0-STABLE-200808 but there's still no new snapshot for the amd64 architecture on your ftp server: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200808/ Are there no relevant changes done to amd64? BTW: Bernt wrote in his mail (see below) that he has a similar motherboard also with a RTL8168/8111 PCI-E Gigabit Ethernet NIC with revision 1 (my NIC is revision 2 - see below) and his one is recognized by 7.0-RELEASE. In 7.0-STABLE it also doesn't work with his NIC: http://lists.freebsd.org/pipermail/freebsd-hardware/2008-September/005367.html (How) Can I help you to solve this issue? Regards, Lukas On Wednesday 13 August 2008 23:19:44 Lukas Razik wrote: > Hello Bernt! > > Yes, you're right - that's interesting... > I only can state that with 7.0-RELEASE and with 7.0-STABLE-200807 > (07/15/08) it doesn't work. > _But_ on 2008-07-15 there was a change made to the re driver which is > relevant for the RTL8168 as you can see here: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c > > Maybe with the current if_re.c it works and to test this I could build a > new kernel from CVS but I come home not until September. :-( > > The only difference between our NICs which I see is the revision. Since > the revision of your chip is 0x01, the NIC's revision on my MoBo is 0x02 > ... Maybe that's the difference? > > Thanks for your statement! > > Regards, > Lukas > > Bernt Hansson schrieb: > > Lukas Razik: > >>Hello! > >> > >>I've a GigaByte GA-X48-DQ6 Motherboard with a "RTL8168/8111 PCI-E Gigabit > >>Ethernet NIC" and I've read that 7.0-RELEASE / amd64 should recognize > >> these cards (by the "re" driver) but it doesn't in my case. > > > > I got an Gigabyte GA-MA790FX-DS5 with the same network chip and it's > > working right out of the box. There are other issues with that > > motherboard. > > > > 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 > > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x01 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > > > >>#uname -a : > >>FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 > >>root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > >> > >>#pciconf -lv : > >>[...] > >>none2@pci0:4:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec > >>rev=0x02 hdr=0x00 > >> vendor = 'Realtek Semiconductor' > >> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > >> class = network > >> subclass = ethernet > >>[...] > >> > >>So, does FreeBSD 7.0 work with these NICs or am I out of luck? > >> > >>Regards and Many Thanks for your help! > >>Lukas > >> > >>_______________________________________________ > >>freebsd-hardware@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >>To unsubscribe, send any mail to > >> "freebsd-hardware-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From koitsu at FreeBSD.org Thu Sep 4 18:31:51 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Sep 4 18:31:57 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <200809041945.08368.freebsd@razik.name> References: <200808110000.58666.freebsd@razik.name> <48A317D8.5070702@bah.homeip.net> <48A34FF0.3010304@razik.name> <200809041945.08368.freebsd@razik.name> Message-ID: <20080904181549.GA24166@icarus.home.lan> On Thu, Sep 04, 2008 at 07:45:00PM +0200, Lukas Razik wrote: > So I also would like to try more current 7.0-STABLE-200808 but there's still > no new snapshot for the amd64 architecture on your ftp server: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200808/ > Are there no relevant changes done to amd64? Oh, there are many changes, but the snapshots for August were suspended for i386 and amd64 due to a cpio vs. GNU cpio problem. Do not bother trying the snapshots from July either, as they will fail during installation (cpio problems; the bin/base/etc. archives are broken and will spit out millions of errors on expansion). The only place right now which has newer snapshots (September), which should work fine: http://pub.allbsd.org/FreeBSD-snapshots/ -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From freebsd at razik.name Fri Sep 5 11:15:08 2008 From: freebsd at razik.name (Lukas Razik) Date: Fri Sep 5 11:15:17 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <20080904181549.GA24166@icarus.home.lan> References: <200808110000.58666.freebsd@razik.name> <200809041945.08368.freebsd@razik.name> <20080904181549.GA24166@icarus.home.lan> Message-ID: <200809051315.02827.freebsd@razik.name> Hello Jeremy, thanks for your always fast answer! On Thursday 04 September 2008 20:15:49 Jeremy Chadwick wrote: > On Thu, Sep 04, 2008 at 07:45:00PM +0200, Lukas Razik wrote: > > So I also would like to try more current 7.0-STABLE-200808 but there's > > still no new snapshot for the amd64 architecture on your ftp server: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200808/ > > Are there no relevant changes done to amd64? > > Oh, there are many changes, but the snapshots for August were suspended > for i386 and amd64 due to a cpio vs. GNU cpio problem. Do not bother > trying the snapshots from July either, as they will fail during > installation (cpio problems; the bin/base/etc. archives are broken > and will spit out millions of errors on expansion). > > The only place right now which has newer snapshots (September), which > should work fine: > > http://pub.allbsd.org/FreeBSD-snapshots/ This source is very nice! It's too bad that there are no mirrors... :-) I've tried the newest snapshot and as you told it works fine! :-) My onboard NICs are recognized now and I can use them without any problems. It's interesting because I've seen no changes in the last days here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c However, this issue is solved for me and also another one which I haven't mentioned yet. Because when I wanted to install 7.0-RELEASE from CD then there came the FreeBSD boot menu with a timer which runs from 10 to 0 seconds, you know... But there was a bug in the past: The timer didn't work (only the cursor under the time value "10" has blinked very fast) and I had to play with my [ESC], [SPACE], [ENTER] keys to push the boot process... Now in 7.0-RELENG_7-20080905-JPSNAP the timer also works fine. BTW: As I wrote you some weeks ago, I wanted to buy a HighPoint RocketRAID 3120 card, run some benchmarks under FreeBSD and tell you the results. I have the card for some hours now but it isn't recognized by 7.0-RELENG_7-20080905- JPSNAP... I will start a new thread for this issue but at first I want to test it with the newest RELENG_7 kernel from CVS... Regards and Many Thanks again for your help! Lukas From koitsu at FreeBSD.org Fri Sep 5 11:28:40 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Sep 5 11:28:47 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <200809051315.02827.freebsd@razik.name> References: <200808110000.58666.freebsd@razik.name> <200809041945.08368.freebsd@razik.name> <20080904181549.GA24166@icarus.home.lan> <200809051315.02827.freebsd@razik.name> Message-ID: <20080905112838.GA56375@icarus.home.lan> On Fri, Sep 05, 2008 at 01:15:02PM +0200, Lukas Razik wrote: > I've tried the newest snapshot and as you told it works fine! :-) > My onboard NICs are recognized now and I can use them without any problems. > It's interesting because I've seen no changes in the last days here: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c I can't explain what's going on then. The last commit I see for RELENG_7 was two weeks ago. I don't know what versions of the kernel (uname output please) you were trying where the NIC wasn't working. > However, this issue is solved for me and also another one which I haven't > mentioned yet. Because when I wanted to install 7.0-RELEASE from CD then there > came the FreeBSD boot menu with a timer which runs from 10 to 0 seconds, you > know... > But there was a bug in the past: The timer didn't work (only the cursor under > the time value "10" has blinked very fast) and I had to play with my [ESC], > [SPACE], [ENTER] keys to push the boot process... > Now in 7.0-RELENG_7-20080905-JPSNAP the timer also works fine. This probably has to do with loader(8) fixes within the past few weeks, specifically with regards to interrupts. I can point you to the commit if need be. > BTW: As I wrote you some weeks ago, I wanted to buy a HighPoint RocketRAID > 3120 card, run some benchmarks under FreeBSD and tell you the results. I have > the card for some hours now but it isn't recognized by 7.0-RELENG_7-20080905- > JPSNAP... > I will start a new thread for this issue but at first I want to test it with > the newest RELENG_7 kernel from CVS... The 3120 card is supported by the hptiop(4) driver. If you're having problems with it, you should report the problem to Highpoint directly. They write the driver themselves, but gets someone with src commit bits to commit the code for them. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From freebsd at razik.name Fri Sep 5 13:21:55 2008 From: freebsd at razik.name (Lukas Razik) Date: Fri Sep 5 13:22:03 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <20080905112838.GA56375@icarus.home.lan> References: <200808110000.58666.freebsd@razik.name> <200809051315.02827.freebsd@razik.name> <20080905112838.GA56375@icarus.home.lan> Message-ID: <200809051521.43973.freebsd@razik.name> Hi! On Friday 05 September 2008 13:28:38 Jeremy Chadwick wrote: > On Fri, Sep 05, 2008 at 01:15:02PM +0200, Lukas Razik wrote: > > I've tried the newest snapshot and as you told it works fine! :-) > > My onboard NICs are recognized now and I can use them without any > > problems. It's interesting because I've seen no changes in the last days > > here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c > > I can't explain what's going on then. The last commit I see for > RELENG_7 was two weeks ago. I don't know what versions of the kernel > (uname output please) you were trying where the NIC wasn't working. I wrote it in my older mail: http://lists.freebsd.org/pipermail/freebsd-hardware/2008-September/005373.html But the main thing is it works. :-) > > BTW: As I wrote you some weeks ago, I wanted to buy a HighPoint > > RocketRAID 3120 card, run some benchmarks under FreeBSD and tell you the > > results. I have the card for some hours now but it isn't recognized by > > 7.0-RELENG_7-20080905- JPSNAP... > > I will start a new thread for this issue but at first I want to test it > > with the newest RELENG_7 kernel from CVS... > > The 3120 card is supported by the hptiop(4) driver. If you're having > problems with it, you should report the problem to Highpoint directly. > They write the driver themselves, but gets someone with src commit bits > to commit the code for them. Oh, O.K. I wanted to give the FreeBSD-Developer of this driver root access to my system for faster bugfixing but then I'll write to HighPoint directly... Let's see how long they need to answer. Thanks for your hints! Regards, Lukas From freebsd at razik.name Fri Sep 5 15:26:49 2008 From: freebsd at razik.name (Lukas Razik) Date: Fri Sep 5 15:27:02 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <20080905112838.GA56375@icarus.home.lan> References: <200808110000.58666.freebsd@razik.name> <200809051315.02827.freebsd@razik.name> <20080905112838.GA56375@icarus.home.lan> Message-ID: <200809051521.43973.freebsd@razik.name> Hi! On Friday 05 September 2008 13:28:38 Jeremy Chadwick wrote: > On Fri, Sep 05, 2008 at 01:15:02PM +0200, Lukas Razik wrote: > > I've tried the newest snapshot and as you told it works fine! :-) > > My onboard NICs are recognized now and I can use them without any > > problems. It's interesting because I've seen no changes in the last days > > here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c > > I can't explain what's going on then. The last commit I see for > RELENG_7 was two weeks ago. I don't know what versions of the kernel > (uname output please) you were trying where the NIC wasn't working. I wrote it in my older mail: http://lists.freebsd.org/pipermail/freebsd-hardware/2008-September/005373.html But the main thing is it works. :-) > > BTW: As I wrote you some weeks ago, I wanted to buy a HighPoint > > RocketRAID 3120 card, run some benchmarks under FreeBSD and tell you the > > results. I have the card for some hours now but it isn't recognized by > > 7.0-RELENG_7-20080905- JPSNAP... > > I will start a new thread for this issue but at first I want to test it > > with the newest RELENG_7 kernel from CVS... > > The 3120 card is supported by the hptiop(4) driver. If you're having > problems with it, you should report the problem to Highpoint directly. > They write the driver themselves, but gets someone with src commit bits > to commit the code for them. Oh, O.K. I wanted to give the FreeBSD-Developer of this driver root access to my system for faster bugfixing but then I'll write to HighPoint directly... Let's see how long they need to answer. Thanks for your hints! Regards, Lukas From freebsd at razik.name Fri Sep 5 15:26:50 2008 From: freebsd at razik.name (Lukas Razik) Date: Fri Sep 5 15:27:02 2008 Subject: Issue with 7.0-RELEASE and Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC In-Reply-To: <200809051521.43973.freebsd@razik.name> References: <200808110000.58666.freebsd@razik.name> <20080905112838.GA56375@icarus.home.lan> <200809051521.43973.freebsd@razik.name> Message-ID: <200809051726.44747.freebsd@razik.name> > > > BTW: As I wrote you some weeks ago, I wanted to buy a HighPoint > > > RocketRAID 3120 card, run some benchmarks under FreeBSD and tell you > > > the results. I have the card for some hours now but it isn't recognized > > > by 7.0-RELENG_7-20080905- JPSNAP... > > > I will start a new thread for this issue but at first I want to test it > > > with the newest RELENG_7 kernel from CVS... > > > > The 3120 card is supported by the hptiop(4) driver. If you're having > > problems with it, you should report the problem to Highpoint directly. > > They write the driver themselves, but gets someone with src commit bits > > to commit the code for them. > > Oh, O.K. > I wanted to give the FreeBSD-Developer of this driver root access to my > system for faster bugfixing but then I'll write to HighPoint directly... > Let's see how long they need to answer. I've tried it again and the only problem was me ;-) (misconfiguration). Now the HighPoint RocketRAID 3120 controller works fine under 7.1-PRERELEASE from 2008-09-05. From freebsd at razik.name Fri Sep 5 15:59:48 2008 From: freebsd at razik.name (Lukas Razik) Date: Fri Sep 5 15:59:54 2008 Subject: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE Message-ID: <200809051759.45729.freebsd@razik.name> Hello Jeremy! We wrote about Areca's and HighPoint's HW-RAID controllers some weeks ago: http://lists.freebsd.org/pipermail/freebsd-hardware/2008-August/005339.html Now I've tested the HighPoint RocketRAID 3120 controller with two Samsung 320GB SATA (HD322HJ) harddisks under FreeBSD 7.1-PRERELEASE with the bonnie++ harddisk benchmark and the following modes: JBOD: http://net.razik.de/HPT_RR_3120/bonnie_JBOD.html RAID1: http://net.razik.de/HPT_RR_3120/bonnie_RAID1.html RAID0: http://net.razik.de/HPT_RR_3120/bonnie_RAID0.html I don't know the controllers from Areca but I think the reached values are O.K. Anyhow, the performance is better than with my old 3ware 8006-2LP PCI controller. Tested filesystem was: UFS2 with enabled Soft Updates. ------ Under Vista 64 (Benchmark: HD Tune): http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_JBOD.png http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_RAID1.png http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_RAID0.png One Samsung HD322HJ @ ICH9R onboard controller: http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_SAMSUNG_HD322HJ.png ------ Regards, Lukas PS: bonnie++ : http://www.coker.com.au/bonnie++ http://www.hdtune.com/ From goodredhat at yahoo.com Fri Sep 12 04:07:27 2008 From: goodredhat at yahoo.com (manish jain) Date: Fri Sep 12 04:07:33 2008 Subject: Question on the Intel 945G chipset Message-ID: <397519.89773.qm@web51304.mail.re2.yahoo.com> ? Hi, ? Till now I have been using FreeBSD 6.2 on a Tomato motherboard with an Intel 810 chipset and never had any problems configuring xorg with the i810 driver. ? I am now planning to upgrade to a new system with an Intel 945G chipset which has an integrated GMA 850 graphics core. ? Does FreeBSD 6.2?support the Intel 945G chipset ? If yes, what video driver would I need to use while configuring xorg ? ? If not, can you please suggest some other fairly recent Intel chipset which would work well with FreeBSD 6.2 and xorg ? ? Thanks Manish Jain ? From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ From gandalf at shopzeus.com Fri Sep 12 06:26:40 2008 From: gandalf at shopzeus.com (Laszlo Nagy) Date: Fri Sep 12 06:26:56 2008 Subject: Intel Server Board S5000PSLROMB + SAS ROMB Message-ID: <48CA0804.5080508@shopzeus.com> I'm about to buy a new server. There is a local distributor here and they offered good prices. The server will have 2 SAS disks in RAID-1 and 8 or 10 SATA 2 disks in RAID 1+0. Others told me that I MUST ask the hardware list before I buy it. Here is their opinion: > I don't know anything about how well this Intel RAID performs under > FreeBSD, but you should check that if you haven't already. From the > little bit I read about it I'm concerned if it's fast enough for as > many drives as you're using. The wrong disk controller will make a > slow mess out of any hardware you throw at it. And here is the hardware: - Boxed Intel Server Board S5000PSLROMB with 8-port SAS ROMB card (Supports 45nm processors (Harpertown and Wolfdale-DP) - Intel? RAID Activation key AXXRAK18E enables full intelligent SAS RAID on S5000PAL, S5000PSL, SR4850HW4/M, SR6850HW4/M. RoHS Compliant. - 512 MB 400MHz DDR2 ECC Registered CL3 DIMM Single Rank, x8(for s5000pslromb) - Intel? RAID Smart Battery AXXRSBBU3, optional battery back up for use with AXXRAK18E and SRCSAS144E. RoHS Complaint. - 4-drive SAS/SATA backplane with expander (requires 2 SAS ports) for SC5400BRP and SC5400LX (two pieces) The basic question is: - how well is this configuration supported in FreeBSD 7? - is this RAID controller fast and reliable with 10 or more disks? Can it take advantage of the disks, or should I use a different controller? Thanks, Laszlo From satz at iranger.com Sat Sep 13 22:08:01 2008 From: satz at iranger.com (Greg Satz) Date: Sat Sep 13 22:08:08 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 Message-ID: <48511BE0-9023-4A7F-A315-2F1CDD85258E@iranger.com> I have a DELL PE750 that boots fine under 6.1 but cannot boot 6.3. It appears that the SATA controller cannot initialize ata1 under 6.3. 6.3 has no problem initializing ata0. My CDROM is on ata0 and the disk is on ata1. Here is the relevant portions of the verbose output: 6.3: isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfea0-0xfeaf at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfea0 ata0: 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: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x4 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 ata0: [MPSAFE] ata1: 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=03 ostat0=80 ostat1=80 ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ... ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: stat0=0x80 err=0xff lsb=0xff msb=0xff ata1: reset tp2 stat0=80 stat1=80 devices=0x0 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 54 ata1: [MPSAFE] 6.1: isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfea0-0xfeaf at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfea0 ata0: 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: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x4 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 ata0: [MPSAFE] ata1: 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=03 ostat0=50 ostat1=00 ata1: stat0=0xd0 err=0x01 lsb=0x00 msb=0x00 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 54 ata1: [MPSAFE] I have the full verbose logs from both boots but didn't want to bomb the mailing list if this was something simple. Any clues appreciated. Thanks, Greg From vince at unsane.co.uk Mon Sep 15 18:37:17 2008 From: vince at unsane.co.uk (Vince Hoffman) Date: Mon Sep 15 18:37:26 2008 Subject: Question on the Intel 945G chipset In-Reply-To: <397519.89773.qm@web51304.mail.re2.yahoo.com> References: <397519.89773.qm@web51304.mail.re2.yahoo.com> Message-ID: <48CEAB32.8050500@unsane.co.uk> manish jain wrote: > > Hi, > > Till now I have been using FreeBSD 6.2 on a Tomato motherboard with an Intel 810 chipset and never had any problems configuring xorg with the i810 driver. > > I am now planning to upgrade to a new system with an Intel 945G chipset which has an integrated GMA 850 graphics core. > > Does FreeBSD 6.2 support the Intel 945G chipset ? If yes, what video driver would I need to use while configuring xorg ? > > If not, can you please suggest some other fairly recent Intel chipset which would work well with FreeBSD 6.2 and xorg ? > I dont remember if I tried on 6.x but using the intel driver (xf86-video-intel) on 7.x worked very well for me in a Intel 945gm chipset. Its certainly supported on 6.x (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/drm/drm_pciids.h?rev=1.2.2.4;content-type=text%2Fplain;only_with_tag=RELENG_6 and look for i945) Vince > Thanks > Manish Jain > > > > From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From lev at serebryakov.spb.ru Wed Sep 17 14:29:22 2008 From: lev at serebryakov.spb.ru (Lev A. Serebryakov) Date: Wed Sep 17 14:29:29 2008 Subject: em0 & FreeBSD-7.1-PRE: watchdog timeout when traffic consists of many small packets. Message-ID: <48D10F7E.3020206@serebryakov.spb.ru> I have on-board 1GiG network card: em0@pci0:0:25:0: class=0x020000 card=0x82681043 chip=0x10bd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82566DM-2 Gigabit Network Connection' class = network subclass = ethernet I have jumboframes enabled: em0: flags=8843 metric 0 mtu 9014 It works perfectly on large voulme transfers: copy 8GiB file va NFS or SMB works Ok in both direction. But when I try to run `kdeinit4' on this computer with DISPLAY points to other computer (my desktop), I get 2-3: em0: watchdog timeout -- resetting em0: link state changed to DOWN em0: link state changed to UP I found, that some chips should be reflashed with new EEPROM, but not this one. Is here any solution? uname -a FreeBSD xxx.xxx.xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sat Aug 30 23:42:02 MSD 2008 lev@xxx.xxx.xxx:/usr/home/storage/obj/usr/src/sys/BLOB amd64 -- // Lev Serebryakov From purchasing at itcomware1.com Wed Sep 17 17:43:04 2008 From: purchasing at itcomware1.com (purchasing) Date: Wed Sep 17 17:43:11 2008 Subject: Asset Recovery Services to channel and commercial customers Message-ID: <22fbb101c918ec$d52bb650$6501a8c0@itemail> Top dollar paid for surplus Cisco, Nortel & Sun Microsystems hardware. Send a list of your excess Networking, Telephony & Server hardware for an instant appraisal. Send List Now To Purchasing@itcomware1.com Jim Pazz I.T.comWare, Inc. 73 Defco Park Road North Haven, CT 06473 866.739.6291 x204 - toll free 203.234.7248 www.itcomware.com AIM itcomwarejp Skype joe.cisco Top Dollar Paid For Surplus Cisco-Nortel-Lucent-IBM-Sun-3Com-Adtran-Extreme-HP & Avaya Hardware Top Dollar Paid For Decommissioned Networking-Telephony-Server-Storage-Scanners & Barcode Hardware Top Dollar Paid For Excess-Surplus-Decommissioned-Off Lease-Excess & Overstocked IT Hardware To be taken of this list, please forward this email purchasing@itcomware1.com From schlesinger at netcologne.de Wed Sep 17 20:06:36 2008 From: schlesinger at netcologne.de (Thomas Schlesinger) Date: Wed Sep 17 20:06:42 2008 Subject: FreeBSD doesn't boot on Dell Studio Hybrid desktop Message-ID: <200809172145.19966.schlesinger@netcologne.de> Hi, I'm not able to boot FreeBSD on my new Dell Studio Hybrid desktop (140g). I've tried with several FreeBSD-Versions (6.x, 7.0, 8.0-CURRENT, 32 and 64 bit), but I'm unable to get a login. This happens, when I try it with 8.0-CURRENT, built for AMD64: Boot option 1 (default): Timecounter tick every 1.000msec ad4: ... acd0: ... "run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config" Boot option 2 (with ACPI disabled): Kernel panic/crash while booting, KDB starts, error message about /usr/src/sys/kern/vfs_subr.c:372 Boot option 3 (safe mode): like boot option 2 Boot option 4 (single user): like boot option 1 Boot option 5 (verbose logging): last message: ata4: "identify ch->device=00000000", then "run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config" I've put an "lspci -v" and an "lsusb -v" output from this machine, generated with Linux, which works flawlessly, here: http://www.filedropper.com/dellstudiohybrid . Does anybody have an idea how I can get FreeBSD to work on this machine? Thanks in advance, Thomas From tempo.raneo at infinito.it Thu Sep 18 02:21:58 2008 From: tempo.raneo at infinito.it (S.G.) Date: Thu Sep 18 02:22:05 2008 Subject: SMART threshold exceeded Message-ID: <48D1B4FD.8070606@infinito.it> Hi Randy, I've reads some posts by you about SMART threshold. I have a notebook, XPS 1530 by Dell, with a Seagate 7200rpm 160GB HD. The HD received a shock by impact (object falling on the notebook while turned on), and there are errors (LBA bad sectors). I have Zero Filled the disk many many times, and apparently the LBA are much lesser. A Seagate Technician told me that if after two Zero Fill the Seatools Long Test would have found no errors I could have used the drive again. He told that bad sectors was not a bad thing, "error" was something worse than bad sector. So, I supposely could use the drive. But Seatools says that SMART is Tripped, and the Dell Media Direct program, who need to install its own partition before the OS installation (before any other partition can be created by the OS during its install), it was not able to create it because "SMART threshold exceeded on ATA device". But I am allowed to install the OS (VISTA Home Premium). ALl the errors were in the last part of the disc, the last 8GB. So, I am creating 3 partitions, the first for Vista, the second for datas, the third for pagefile, and I am leaving the last 8GB of the disk not partitionned, not allocated. DO you think it is reasonably safe? Thanks for your help Sergio From bsd at fluffles.net Fri Sep 19 03:26:47 2008 From: bsd at fluffles.net (fluffles.net) Date: Fri Sep 19 03:26:54 2008 Subject: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE In-Reply-To: <200809051759.45729.freebsd@razik.name> References: <200809051759.45729.freebsd@razik.name> Message-ID: <48D31C82.8030007@fluffles.net> Lukas Razik wrote: > Hello Jeremy! > > We wrote about Areca's and HighPoint's HW-RAID controllers some weeks ago: > http://lists.freebsd.org/pipermail/freebsd-hardware/2008-August/005339.html > > Now I've tested the HighPoint RocketRAID 3120 controller with two Samsung > 320GB SATA (HD322HJ) harddisks under FreeBSD 7.1-PRERELEASE with the bonnie++ > harddisk benchmark and the following modes: > > JBOD: > http://net.razik.de/HPT_RR_3120/bonnie_JBOD.html > RAID1: > http://net.razik.de/HPT_RR_3120/bonnie_RAID1.html > RAID0: > http://net.razik.de/HPT_RR_3120/bonnie_RAID0.html > Hi Lukas, Your scores are too low, especially for RAID0. Could you please try: dd if=/dev/zero of=/path/to/raid/zerofile bs=1m count=20000 umount re-mount dd if=/path/to/raid/zerofile of=/dev/null bs=1m The unmount is necessary to clear the filecache, else you will be (partly) benchmarking your RAM since part of the data will come from RAM and not the disks; not what you want when testing disk performance. As a rule of thumb you should test with a size at least 8 times bigger than the sum of all write-back mechanisms, either in hardware or software. The 20GB zerofile in the example above is a safe guess. Also make sure the filesystem is near-empty when you benchmark, else you are benchmarking a slower portion of your harddrives so you can expect lower scores. If you get about the same scores with dd, try using a higher read-ahead (vfs.read_max value, set it to 32 for example). Also sometimes it's required to use a higher blocksize to get full potential, try: newfs -U -b 32768 /dev/ Warning: using 64KiB blocksize you risk hanging the system under heavy load (like 2 bonnies running simultaniously). Also *DO NOT* create partitions on the raid device, unless you have manually created them to avoid a "stripe misalignment", where one read request might hit two disks causing lower performance. Ideally you'd want a single disk to handle one I/O request, not several since the only real bottleneck is the seek time. So if your raid device is /dev/da0, just pass that to newfs, after making sure your partitions are gone with: dd if=/dev/zero of=/dev/da0 bs=1m count=20 This will, ofcourse, destroy all data on the RAIDrai volume. The last thing i can think of is stripesize, you should not set this lower than 64KiB to avoid two disks processing one I/O request (ata driver does 64KiB max requests i think, maxphys is 128KiB). But also because UFS2 begins at 64KiB offset, to allow for partitioning data to be preserved. So where you think the filesystems starts, for example as defined in a label, is not actually where the filesystem starts storing data. All these factors can cause RAID-performance to be low, or to be cloaked due to improper benchmarking. Many people using HDTune think their RAID does not perform well, while its just HDTune which was never meant to test RAID-arrays since RAIDs can only be faster when parallellisation is possible - processing 2 of more I/O at once by different physical disks. HDTune sends only one request at a time, and as such RAIDs that do not have internal read-ahead optimizations will fail in HDTune. An Areca however will perform well, due to its own optimizations. But normally the filesystem takes care of generating enough I/O, also on Windows. Also note that virtually all Windows systems using RAID are suffered by stripe misalignement, since Windows requires the use of partitions and Windows has neglected to take into account the misalignment issue by using a weird offset for the partitioning. It is possible to create an aligned partition using third party tools however. > I don't know the controllers from Areca but I think the reached values are > O.K. Anyhow, the performance is better than with my old 3ware 8006-2LP PCI > controller. > Tested filesystem was: UFS2 with enabled Soft Updates. > > ------ > > Under Vista 64 (Benchmark: HD Tune): > http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_JBOD.png > http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_RAID1.png > http://net.razik.de/HPT_RR_3120/Vista_HDTune_Benchmark_HPT_____DISK_0_0_RAID0.png > You should not use HDTune to test RAID-arrays, see also: http://www.fluffles.net/blogs/2.Why-HDTune-is-unsuitable-for-RAID-arrays.html Test with ATTO-256 and you should get higher scores. Just make sure the filesystem starts at the beginning of the volume and that it's close to empty. Hope its useful :) Regards, Veronica From freebsd at sopwith.solgatos.com Fri Sep 19 06:08:54 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Fri Sep 19 06:08:59 2008 Subject: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE In-Reply-To: Your message of "Fri, 19 Sep 2008 05:29:06 +0200." <48D31C82.8030007@fluffles.net> Message-ID: <200809190548.FAA08998@sopwith.solgatos.com> > If you get about the same scores with dd, try using a higher read-ahead > (vfs.read_max value, set it to 32 for example). Also sometimes it's > required to use a higher blocksize to get full potential, try: > > newfs -U -b 32768 /dev/ > > Warning: using 64KiB blocksize you risk hanging the system under heavy > load (like 2 bonnies running simultaniously). What's this about 64KiB blocksize hanging the system? Hang awhile then recover, or hang forever need a reboot? Is this a RAID thing or are normal disks at risk? It isn't obvious why a 64KiB blocksize would cause a problem in this day of multi GiB memory. From koitsu at FreeBSD.org Fri Sep 19 06:23:50 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Sep 19 06:23:58 2008 Subject: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE In-Reply-To: <200809190548.FAA08998@sopwith.solgatos.com> References: <48D31C82.8030007@fluffles.net> <200809190548.FAA08998@sopwith.solgatos.com> Message-ID: <20080919062348.GA37673@icarus.home.lan> On Thu, Sep 18, 2008 at 10:48:03PM +0100, Dieter wrote: > > If you get about the same scores with dd, try using a higher read-ahead > > (vfs.read_max value, set it to 32 for example). Also sometimes it's > > required to use a higher blocksize to get full potential, try: > > > > newfs -U -b 32768 /dev/ > > > > Warning: using 64KiB blocksize you risk hanging the system under heavy > > load (like 2 bonnies running simultaniously). > > What's this about 64KiB blocksize hanging the system? > Hang awhile then recover, or hang forever need a reboot? > Is this a RAID thing or are normal disks at risk? > It isn't obvious why a 64KiB blocksize would cause a > problem in this day of multi GiB memory. Why do you think the amount of memory people have in their computers has *anything* to do with a filesystem blocksize? If a large blocksize would crash a filesystem, it's not going to be due to "not having enough RAM". -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From bsd at fluffles.net Fri Sep 19 15:31:07 2008 From: bsd at fluffles.net (fluffles.net) Date: Fri Sep 19 15:31:12 2008 Subject: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE In-Reply-To: <200809190548.FAA08998@sopwith.solgatos.com> References: <200809190548.FAA08998@sopwith.solgatos.com> Message-ID: <48D3C64A.5010207@fluffles.net> Dieter wrote: >> If you get about the same scores with dd, try using a higher read-ahead >> (vfs.read_max value, set it to 32 for example). Also sometimes it's >> required to use a higher blocksize to get full potential, try: >> >> newfs -U -b 32768 /dev/ >> >> Warning: using 64KiB blocksize you risk hanging the system under heavy >> load (like 2 bonnies running simultaniously). >> > > What's this about 64KiB blocksize hanging the system? > Hang awhile then recover, or hang forever need a reboot? > Is this a RAID thing or are normal disks at risk? > See this, posted 2 years ago to freebsd-fs: http://freebsd.monkey.org/freebsd-fs/200610/msg00024.html Scott Long says the bug in vfs_bio.c is known but difficult to fix. They also argued that using a 64KiB blocksize should not be necessary. I have been getting slightly higher scores with 64KiB blocksize though, also with perfect alignment. 32KiB should be safe to use, i have not managed to crash the system under heavy I/O load. I'm curious if my suggestions gave you any better results, though. Regards, Veronica From benjie at addgene.org Fri Sep 19 15:34:46 2008 From: benjie at addgene.org (Benjie Chen) Date: Fri Sep 19 15:34:50 2008 Subject: Interrupts issues Message-ID: Hi FreeBSD hackers: I have two Dell workstations that I recently added FreeBSD 6.2 on. One is a Precision T3400, one is an Inspiron 530. Nothing fancy. Installed FBsd. Everything else is fine except both machines have interrupt storm issues: one core (both dual core) is 100% servicing interrupts. On the Precision, it's irq20 atapci, on Inspiron it's irq19 uhci. The other core is fine and both machines run well otherwise. I saw several recent posts on the net about some of these issues and did not find a resolution. It seems unlikely that it's just a ata or usb issue since both machines happen to have the same problem. Any thoughts? Thanks, Benjie From unixmania at gmail.com Sat Sep 20 02:50:35 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Sat Sep 20 02:50:38 2008 Subject: Interrupts issues In-Reply-To: References: Message-ID: On Fri, Sep 19, 2008 at 12:04 PM, Benjie Chen wrote: > Hi FreeBSD hackers: > > I have two Dell workstations that I recently added FreeBSD 6.2 on. One > is a Precision T3400, one is an Inspiron 530. Nothing fancy. Installed > FBsd. Everything else is fine except both machines have interrupt > storm issues: one core (both dual core) is 100% servicing interrupts. > On the Precision, it's irq20 atapci, on Inspiron it's irq19 uhci. The > other core is fine and both machines run well otherwise. > > I saw several recent posts on the net about some of these issues and > did not find a resolution. It seems unlikely that it's just a ata or > usb issue since both machines happen to have the same problem. > > Any thoughts? Please provide the output of "dmesg" after a boot in verbose mode. This may help the maintainers to understand your problem and give you additional instructions. Do you have any special reason to use FreeBSD 6.2? It is a rather old version, so I'd suggest you to try 7.1 instead. There are prerelease images available. Look at http://www.freebsd.org/where.html -- cd /usr/ports/sysutils/life make clean From volker at vwsoft.com Sat Sep 20 16:29:02 2008 From: volker at vwsoft.com (Volker) Date: Sat Sep 20 16:29:10 2008 Subject: Interrupts issues In-Reply-To: References: Message-ID: <48D51FAF.70603@vwsoft.com> On 12/23/-58 20:59, Carlos A. M. dos Santos wrote: > On Fri, Sep 19, 2008 at 12:04 PM, Benjie Chen wrote: >> Hi FreeBSD hackers: >> >> I have two Dell workstations that I recently added FreeBSD 6.2 on. One >> is a Precision T3400, one is an Inspiron 530. Nothing fancy. Installed >> FBsd. Everything else is fine except both machines have interrupt >> storm issues: one core (both dual core) is 100% servicing interrupts. >> On the Precision, it's irq20 atapci, on Inspiron it's irq19 uhci. The >> other core is fine and both machines run well otherwise. >> >> I saw several recent posts on the net about some of these issues and >> did not find a resolution. It seems unlikely that it's just a ata or >> usb issue since both machines happen to have the same problem. >> >> Any thoughts? > > Please provide the output of "dmesg" after a boot in verbose mode. > This may help the maintainers to understand your problem and give you > additional instructions. > > Do you have any special reason to use FreeBSD 6.2? It is a rather old > version, ... 6.2 has already been EOL'd in May. From freebsd at sopwith.solgatos.com Sat Sep 20 17:01:00 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat Sep 20 17:01:05 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: Your message of "Sat, 20 Sep 2008 14:54:14 +0200." <20080920125414.GS93308@cicely7.cicely.de> Message-ID: <200809201655.QAA10313@sopwith.solgatos.com> [ -hardware@ list added to existing -alpha@ thread as this doesn't seem to be alpha specific ] > This is because USB is absolutely crap for this purpose. > RS232 terminals, especially with long cables, can produce several kind > of spikes and ground loops, which USB is very very sensitive about. Many things about USB are crap (thanks, inthell), but if a USB to RS-232 bridge cannot handle normal spikes and ground loops, I'd blame the bridge, not USB itself. If the problem is spikes and ground loops there is probably some RS-232 filter/isolator available to clean them up. There could be a bug in the bridge which needs a software workaround. In any case the system shouldn't crash. Are there specific make&model USB to RS-232 bridges that people have had good luck with? > My advise is to use a completely other technology to connect the terminals. > A galvanic isolated USB device might work, but there are lot of PCI and > Ethernet devices on the market which are more solid by design than USB. The problem with PCI is the limited number of slots. :-( Ethernet could be a good solution for some applications, if you can get the software to deal with it. NFS is crap, *real* distributed file systems handled devices transparently. (thanks, Sun) Does anyone make firewire to RS-232 bridges? From remko at FreeBSD.org Sun Sep 21 07:57:46 2008 From: remko at FreeBSD.org (Remko Lodder) Date: Sun Sep 21 07:57:53 2008 Subject: Interrupts issues In-Reply-To: <48D51FAF.70603@vwsoft.com> References: <48D51FAF.70603@vwsoft.com> Message-ID: <48D5F518.4040904@FreeBSD.org> Volker wrote: > On 12/23/-58 20:59, Carlos A. M. dos Santos wrote: >> On Fri, Sep 19, 2008 at 12:04 PM, Benjie Chen wrote: >>> Hi FreeBSD hackers: >>> >>> I have two Dell workstations that I recently added FreeBSD 6.2 on. One >>> is a Precision T3400, one is an Inspiron 530. Nothing fancy. Installed >>> FBsd. Everything else is fine except both machines have interrupt >>> storm issues: one core (both dual core) is 100% servicing interrupts. >>> On the Precision, it's irq20 atapci, on Inspiron it's irq19 uhci. The >>> other core is fine and both machines run well otherwise. >>> >>> I saw several recent posts on the net about some of these issues and >>> did not find a resolution. It seems unlikely that it's just a ata or >>> usb issue since both machines happen to have the same problem. >>> >>> Any thoughts? >> Please provide the output of "dmesg" after a boot in verbose mode. >> This may help the maintainers to understand your problem and give you >> additional instructions. >> >> Do you have any special reason to use FreeBSD 6.2? It is a rather old >> version, ... > > 6.2 has already been EOL'd in May. > _______________________________________________ I need to join the club, my machine starts doing interrupt storms after an uptime of ${random} on the IRQ19 (atapci0) thingy. Next time I'll boot the machine I'll try to make it a verbose boot. It's a production machine which cannot restart on demand ofcourse :) Note: First the problems occured much more, this was because the usb interfaces on the machine co-existed with the atapci0 interface, after disabling usb on the system, it took a lot longer to trigger the interrupt storm (50 days if I recall correctly). Cheers remko Regular dmesg: Copyright (c) 1992-2008 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.1-PRERELEASE #7: Thu Sep 18 09:53:16 CEST 2008 root@xxxxx.elvandar.org:/usr/obj/usr/src/sys/xxxxx Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2799.99-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 2103840768 (2006 MB) avail memory = 2028867584 (1934 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7df00000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 pci1: at device 5.2 (no driver attached) pcib2: at device 7.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2 re0: turning off MSI enable bit. re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:92:b1:a3:2f re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] pci0: at device 19.0 (no driver attached) pci0: at device 19.1 (no driver attached) pci0: at device 19.2 (no driver attached) pci0: at device 19.3 (no driver attached) pci0: at device 19.4 (no driver attached) pci0: at device 19.5 (no driver attached) pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 acpi_button0: on acpi0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 orm0: at iomem 0xcd800-0xce7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: 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 ad4: 381554MB at ata2-master SATA300 ad6: 381554MB at ata3-master SATA300 SMP: AP CPU #1 Launched! Trying to mount root from zfs:tank/root -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From ticso at cicely7.cicely.de Thu Sep 25 13:08:05 2008 From: ticso at cicely7.cicely.de (Bernd Walter) Date: Thu Sep 25 13:08:12 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: <200809201655.QAA10313@sopwith.solgatos.com> References: <20080920125414.GS93308@cicely7.cicely.de> <200809201655.QAA10313@sopwith.solgatos.com> Message-ID: <20080925125417.GQ93308@cicely7.cicely.de> On Sat, Sep 20, 2008 at 09:55:59AM +0100, Dieter wrote: > [ -hardware@ list added to existing -alpha@ thread as this > doesn't seem to be alpha specific ] > > > This is because USB is absolutely crap for this purpose. > > RS232 terminals, especially with long cables, can produce several kind > > of spikes and ground loops, which USB is very very sensitive about. > > Many things about USB are crap (thanks, inthell), but if a USB to RS-232 > bridge cannot handle normal spikes and ground loops, I'd blame the > bridge, not USB itself. If the problem is spikes and ground loops > there is probably some RS-232 filter/isolator available to clean them > up. There could be a bug in the bridge which needs a software workaround. > In any case the system shouldn't crash. > > Are there specific make&model USB to RS-232 bridges that people > have had good luck with? USB can't handle spikes and ground loops. As said: use isolated devices, so you don't have the loops and spikes. You can blame the device for not being isolated, but you expect every device to provide expensive workaround for a design failure. USB is designed for cheap stuff - that's all about it. Yes - the system shouldn't crash, but don't expect it ever being fixed for FreeBSD-alpha. > > My advise is to use a completely other technology to connect the terminals. > > A galvanic isolated USB device might work, but there are lot of PCI and > > Ethernet devices on the market which are more solid by design than USB. > > The problem with PCI is the limited number of slots. :-( Well - not realy with server class alphas... > Ethernet could be a good solution for some applications, if you > can get the software to deal with it. NFS is crap, *real* distributed > file systems handled devices transparently. (thanks, Sun) This is a different topic. For RS232 Ethernet is quite reasonable. > Does anyone make firewire to RS-232 bridges? Or stay with the old DEC devices - they are rock solid even after all those years. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From wb at freebie.xs4all.nl Thu Sep 25 13:16:51 2008 From: wb at freebie.xs4all.nl (Wilko Bulte) Date: Thu Sep 25 13:17:03 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: <20080925125417.GQ93308@cicely7.cicely.de> References: <20080920125414.GS93308@cicely7.cicely.de> <200809201655.QAA10313@sopwith.solgatos.com> <20080925125417.GQ93308@cicely7.cicely.de> Message-ID: <20080925125852.GK59387@freebie.xs4all.nl> Quoting Bernd Walter, who wrote on Thu, Sep 25, 2008 at 02:54:17PM +0200 .. > On Sat, Sep 20, 2008 at 09:55:59AM +0100, Dieter wrote: > > [ -hardware@ list added to existing -alpha@ thread as this > > doesn't seem to be alpha specific ] > > > > > This is because USB is absolutely crap for this purpose. > > > RS232 terminals, especially with long cables, can produce several kind > > > of spikes and ground loops, which USB is very very sensitive about. > > > > Many things about USB are crap (thanks, inthell), but if a USB to RS-232 > > bridge cannot handle normal spikes and ground loops, I'd blame the > > bridge, not USB itself. If the problem is spikes and ground loops > > there is probably some RS-232 filter/isolator available to clean them > > up. There could be a bug in the bridge which needs a software workaround. > > In any case the system shouldn't crash. > > > > Are there specific make&model USB to RS-232 bridges that people > > have had good luck with? > > USB can't handle spikes and ground loops. > As said: use isolated devices, so you don't have the loops and spikes. > You can blame the device for not being isolated, but you expect every > device to provide expensive workaround for a design failure. > USB is designed for cheap stuff - that's all about it. 20mA current loop comes to mind > > > A galvanic isolated USB device might work, but there are lot of PCI and > > > Ethernet devices on the market which are more solid by design than USB. > > > > The problem with PCI is the limited number of slots. :-( > > Well - not realy with server class alphas... Yeah... a Turbolaser running a terminal server 8-) > > Does anyone make firewire to RS-232 bridges? > > Or stay with the old DEC devices - they are rock solid even after all > those years. DECserver900 are indeed rock solid. Run reverse-telnet driven bij conserver on FreeBSD. Works like a charm. I still have a considerable # of lines like that running in an engineering lab. conserver runs on Tru64 in that particular case. Wilko From freebsd at sopwith.solgatos.com Thu Sep 25 17:11:08 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Thu Sep 25 17:11:20 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: Your message of "Thu, 25 Sep 2008 14:54:17 +0200." <20080925125417.GQ93308@cicely7.cicely.de> Message-ID: <200809251701.RAA18993@sopwith.solgatos.com> [ -usb@ added to existing thread ] > > > This is because USB is absolutely crap for this purpose. > > > RS232 terminals, especially with long cables, can produce several kind > > > of spikes and ground loops, which USB is very very sensitive about. > > > > Many things about USB are crap (thanks, inthell), but if a USB to RS-232 > > bridge cannot handle normal spikes and ground loops, I'd blame the > > bridge, not USB itself. If the problem is spikes and ground loops > > there is probably some RS-232 filter/isolator available to clean them > > up. There could be a bug in the bridge which needs a software workaround. > > In any case the system shouldn't crash. > > > > Are there specific make&model USB to RS-232 bridges that people > > have had good luck with? > > USB can't handle spikes and ground loops. > As said: use isolated devices, so you don't have the loops and spikes. > You can blame the device for not being isolated, but you expect every > device to provide expensive workaround for a design failure. > USB is designed for cheap stuff - that's all about it. Surely a "good" USB to RS-232 bridge (if one exists?) or a RS-232 filter/isolator (assuming they exist?) would be *far* less expensive than the server class alpha you suggest below. And IIRC it is just speculation that the original poster's problem is caused by spikes or ground loops. > Yes - the system shouldn't crash, but don't expect it ever being fixed > for FreeBSD-alpha. There is a 6.4 coming out, yes? It is unlikely that the problem is alpha specific. If an alpha crashes, other archs will likely crash. > > > My advise is to use a completely other technology to connect the terminals. > > > A galvanic isolated USB device might work, but there are lot of PCI and > > > Ethernet devices on the market which are more solid by design than USB. > > > > The problem with PCI is the limited number of slots. :-( > > Well - not realy with server class alphas... In my world, a "server" means 1-4 full height 19" racks with quite large price tags and power&cooling requirements. Some people think a server is a pee-cee. So I'm not sure what you mean by "server class alphas". I have what I would call a "workstation" class alpha, which cost an obscene amount to get 6 PCI slots instead of 4, and at times they are all full. So I can't use up a slot just to get a couple more RS-232 ports. How many PCI slots does a server class alpha have? RS-232 doesn't require PCI levels of bandwidth. Something like a USB to RS-232 bridge could be a good solution, if I knew which make&model of bridge worked well with *BSD. Poking around on the web I can't even find what chip they have inside. Do these bridges actually work properly, or do they have gotchas like the USB to SATA/PATA bridges? > > Ethernet could be a good solution for some applications, if you > > can get the software to deal with it. NFS is crap, *real* distributed > > file systems handled devices transparently. (thanks, Sun) > > This is a different topic. > For RS232 Ethernet is quite reasonable. For some applications yes. But some apps want to open /dev/ttyXX and do ioctls on it. How does one use such an app on Free/Net/OpenBSD with the RS-232 device on some Ethernet connected RS-232 port? > > Does anyone make firewire to RS-232 bridges? > > Or stay with the old DEC devices - they are rock solid even after all > those years. It is not obvious what "old DEC devices" you are referring to. From koitsu at FreeBSD.org Thu Sep 25 17:38:41 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Sep 25 17:38:48 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: <200809251701.RAA18993@sopwith.solgatos.com> References: <20080925125417.GQ93308@cicely7.cicely.de> <200809251701.RAA18993@sopwith.solgatos.com> Message-ID: <20080925173837.GA3415@icarus.home.lan> On Thu, Sep 25, 2008 at 10:01:51AM +0100, Dieter wrote: > [ -usb@ added to existing thread ] > > > > > This is because USB is absolutely crap for this purpose. > > > > RS232 terminals, especially with long cables, can produce several kind > > > > of spikes and ground loops, which USB is very very sensitive about. > > > > > > Many things about USB are crap (thanks, inthell), but if a USB to RS-232 > > > bridge cannot handle normal spikes and ground loops, I'd blame the > > > bridge, not USB itself. If the problem is spikes and ground loops > > > there is probably some RS-232 filter/isolator available to clean them > > > up. There could be a bug in the bridge which needs a software workaround. > > > In any case the system shouldn't crash. > > > > > > Are there specific make&model USB to RS-232 bridges that people > > > have had good luck with? > > > > USB can't handle spikes and ground loops. > > As said: use isolated devices, so you don't have the loops and spikes. > > You can blame the device for not being isolated, but you expect every > > device to provide expensive workaround for a design failure. > > USB is designed for cheap stuff - that's all about it. > > Surely a "good" USB to RS-232 bridge (if one exists?) or a RS-232 > filter/isolator (assuming they exist?) would be *far* less expensive > than the server class alpha you suggest below. I'm coming into this conversation late, so my apologies. If by "bridge" you mean a USB adapter that supports RS232 serial, then yes, there are some which work quite nicely with FreeBSD. Anything that uses a Prolific chip will work well (supports custom serial rates, and does not drop/lose characters). The uplcom(4) driver is for this chip, and the man page lists off some consumer models/devices available. I can refer you to numerous people who have spoken to me privately or publicly on lists, praising the Prolific stuff. I have no idea if this driver works on Alphas. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From ticso at cicely7.cicely.de Thu Sep 25 19:00:33 2008 From: ticso at cicely7.cicely.de (Bernd Walter) Date: Thu Sep 25 19:00:47 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: <200809251701.RAA18993@sopwith.solgatos.com> References: <20080925125417.GQ93308@cicely7.cicely.de> <200809251701.RAA18993@sopwith.solgatos.com> Message-ID: <20080925190022.GB93308@cicely7.cicely.de> On Thu, Sep 25, 2008 at 10:01:51AM +0100, Dieter wrote: > [ -usb@ added to existing thread ] > > > > > This is because USB is absolutely crap for this purpose. > > > > RS232 terminals, especially with long cables, can produce several kind > > > > of spikes and ground loops, which USB is very very sensitive about. > > > > > > Many things about USB are crap (thanks, inthell), but if a USB to RS-232 > > > bridge cannot handle normal spikes and ground loops, I'd blame the > > > bridge, not USB itself. If the problem is spikes and ground loops > > > there is probably some RS-232 filter/isolator available to clean them > > > up. There could be a bug in the bridge which needs a software workaround. > > > In any case the system shouldn't crash. > > > > > > Are there specific make&model USB to RS-232 bridges that people > > > have had good luck with? > > > > USB can't handle spikes and ground loops. > > As said: use isolated devices, so you don't have the loops and spikes. > > You can blame the device for not being isolated, but you expect every > > device to provide expensive workaround for a design failure. > > USB is designed for cheap stuff - that's all about it. > > Surely a "good" USB to RS-232 bridge (if one exists?) or a RS-232 > filter/isolator (assuming they exist?) would be *far* less expensive > than the server class alpha you suggest below. It depend on how much RS232 you need and how many slots the OP has free. Nevertheless a "good" RS232 bridge if needed in number are not cheap either - ntoe that you can get affordable PCI extenders as well. > And IIRC it is just speculation that the original poster's problem is > caused by spikes or ground loops. No it is not speculation - I know USB very well and the device disconnected, which is very typical for electrical problems caused by ground loops. > > Yes - the system shouldn't crash, but don't expect it ever being fixed > > for FreeBSD-alpha. > > There is a 6.4 coming out, yes? It is unlikely that the problem is alpha specific. > If an alpha crashes, other archs will likely crash. This is a design problem with our USB stack, which is likely to be handled by the HPS stack which is going into current. The problems are way too old that there is a real chance that anyone will ever fix it in the old stack and the new one will not be backported to 6.x, since the changes for a stable branch are too invasive. > > > > My advise is to use a completely other technology to connect the terminals. > > > > A galvanic isolated USB device might work, but there are lot of PCI and > > > > Ethernet devices on the market which are more solid by design than USB. > > > > > > The problem with PCI is the limited number of slots. :-( > > > > Well - not realy with server class alphas... > > In my world, a "server" means 1-4 full height 19" racks with quite large > price tags and power&cooling requirements. Some people think a server > is a pee-cee. So I'm not sure what you mean by "server class alphas". Server doesn't mean rack, but beside from a few OEM boards and small 19" system all alphas have lots of free slots available. > I have what I would call a "workstation" class alpha, which cost an > obscene amount to get 6 PCI slots instead of 4, and at times they are > all full. So I can't use up a slot just to get a couple more RS-232 > ports. How many PCI slots does a server class alpha have? Well the AS4100 I have already has 8 slots which is not that uncommon for alpha servers. The real big ones can even have a few hundred slots. > RS-232 doesn't require PCI levels of bandwidth. Something like a It doesn't need high bandwidth, but it doesn't hurt either. For terminals it needs the ability to accept ground loops. For other purposes it needs low latency - USB has a latency of 1-2ms, which is a few thousand times higher than ISA. You can get better results with any kind of cheap ISA RS232 card. > USB to RS-232 bridge could be a good solution, if I knew which > make&model of bridge worked well with *BSD. Poking around on the web > I can't even find what chip they have inside. Really forget about USB to RS232. It is not the chip which is the problem it is the principal. You really need galvanic isolation, because USB can't handle ground loops, which no cheap device has. You can use any kind of chip with propper isolation, but then it is likely more expensive than any other kind of solution. > Do these bridges actually work properly, or do they have gotchas > like the USB to SATA/PATA bridges? The prolific bridges work well enough if you don't have a ground loop and FTDI chips are better IMHO. > > > Ethernet could be a good solution for some applications, if you > > > can get the software to deal with it. NFS is crap, *real* distributed > > > file systems handled devices transparently. (thanks, Sun) > > > > This is a different topic. > > For RS232 Ethernet is quite reasonable. > > For some applications yes. But some apps want to open /dev/ttyXX > and do ioctls on it. How does one use such an app on Free/Net/OpenBSD > with the RS-232 device on some Ethernet connected RS-232 port? It depend on the way you use it. In most cases you just use raw connection and configure it out of band. In some cases you use telnet encapsulation to allow break handling. But you are free to use other protocoll. Anyway: this doesn't apply to terminal use, since you don't need to change the communication parameters after initial setup. > > > Does anyone make firewire to RS-232 bridges? > > > > Or stay with the old DEC devices - they are rock solid even after all > > those years. > > It is not obvious what "old DEC devices" you are referring to. Reread the original post - it was about replacing a solid DEC ethernet terminal concentrator with a bunch of crappy USB-RS232 adapters. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From chris at evilpuma.com Sat Sep 27 23:32:32 2008 From: chris at evilpuma.com (Chris Manns) Date: Sat Sep 27 23:32:38 2008 Subject: FBSD 7.0 halts on compaq v2000 laptop Message-ID: I got a presario v2000 laptop with this hardware AMD64 turion 2800 unknown motherboard 512mb ddr ATi Xpress 200m chipset ATi Xpress 200m graphics (basically a x300 card) The machine has nothing on it atm, I initially tried PC-BSD which is FreeBSD7 then I tried with FreeBSD 7 AMD64 (PC-BSD is x86 atm) It halted at detecting the firewire ports. I tried without acpi (I think thatswhat it is, whatever you push 2 to disable at the boot loader) It went further to mounting something like md0. I've tried with verbose too, not much errors some stuff about a serial port i believe. Not sure where else to go with this, I've disabled other things like mtrr, I read that a guy got freebsd 6 to work by doing something like that, I couldn't find much info. Once I did that it halted at start_init /stand/sysinstall it did a few start_init's, thats the last one then she halted. I've got no clue why its halting at different areas depending on whats disabled. -- ~Chris Manns