Re: MSIX failure
On Fri 2010-09-10 (10:41), Gareth de Vaux wrote: > > Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot > > btw. > > Ok, I'll have to get back to you in a day or 2 when I reboot. Done: $ sysctl -a | grep msi hw.bce.msi_enable: 1 hw.pci.honor_msi_blacklist: 0 hw.pci.enable_msix: 1 hw.pci.enable_msi: 1 I get the same MSIX failure message though. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MSIX failure
On Thu 2010-09-09 (17:00), Gareth de Vaux wrote: > On Thu 2010-09-09 (16:54), Kurt Jaeger wrote: > > -c asks for pci device capabilities, which are read in > > > > /usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR > > Ah. I'll have to schedule a reboot then .. pciconf -lcv, onboard: e...@pci0:0:25:0:class=0x02 card=0x8086 chip=0x10f08086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 13[e0] = PCI Advanced Features: FLR TP add-on: e...@pci0:5:1:0: class=0x02 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Gigabit Ethernet Controller (Copper) rev 5 (82541PI)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X supports 2048 burst read, 1 split transaction ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MSIX failure
On Sun, Sep 12, 2010 at 1:15 AM, Gareth de Vaux wrote: > On Fri 2010-09-10 (10:41), Gareth de Vaux wrote: > > > Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at > boot > > > btw. > > > > Ok, I'll have to get back to you in a day or 2 when I reboot. > > Done: > > $ sysctl -a | grep msi > hw.bce.msi_enable: 1 > hw.pci.honor_msi_blacklist: 0 > hw.pci.enable_msix: 1 > hw.pci.enable_msi: 1 > > I get the same MSIX failure message though. > > Ya, that's what I suspected, it just means the failure is not because your system is blacklisted. You still have not given me what I need to help: the exact details of the system, I don't need to see the pciconf of the NIC, I need to know about the motherboard/chipset its on. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Serial console problems with stable/8
Hi, On Friday I have updated a machine from 7.1 to stable/8. It is connected to a serial console. With 7.1 everything worked fine, but with stable/8 things seem to break. When the machine boots, everything appears normal, i.e. I get all of the boot output, but then the console freezes. The last thing that appears on the console is the time stamp from the date(1) command at the very end of /etc/rc. I do not get a login prompt, even though I see a getty process on ttyu0. No further output to the console happens, commands like "echo foo > /dev/console" freeze, too. According to ps -alx they hang in "ttydcd". I cannot even su(1) to root because it tries to print a message to the console, so it hangs, too. For the same reason I can't use shutdown(8) either. :-( This is what a hanging su(1) command looks like in ps -alxww: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 1533 1532 0 76 0 3392 3180 ttydcd I+ 00:00.05 su (zsh) Interestingly, the KDB sequences CR ~ ^B/^P/^R/ do work, which use the "low-level" console. So only the "high-level" console is frozen. When I boot with the getty on ttyu0 switched off in /etc/ttys, the console does *not* freeze, and output to /dev/console works normal (I don't get a login prompt, of course). I can use su(1), shutdown(8) and so on. But as soon as I try to start a getty on ttyu0, the darn thing ceases to work. Here's my setup (which worked perfectly fine with 7.1): /boot.config: -P /boot/loader.conf: kernel_options="-P" console="comconsole" /etc/ttys: ttyu0 "/usr/libexec/getty std.9600" vt100 off secure /boot/device.hints: hint.uart.0.at="isa" hint.uart.0.port="0x3F8" hint.uart.0.flags="0x10" hint.uart.0.irq="4" /var/run/dmesg.boot: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart0: console (9600,n,8,1) The serial port is connected to another PC that runs tip(1) in a screen(1) session, using a 9-pin nullmodem cable. That setup hasn't changed in ages; that other PC is running an older version of FreeBSD. I need this issue to be resolved, because the serial console is required for remote management (the machine is a 3-hours ride away from home). If it can't be resolved, I will have to downgrade it to 7.x. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd I suggested holding a "Python Object Oriented Programming Seminar", but the acronym was unpopular. -- Joseph Strout ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Serial console problems with stable/8
On Sun, Sep 12, 2010 at 05:26:12PM +0200, Oliver Fromme wrote: > On Friday I have updated a machine from 7.1 to stable/8. > It is connected to a serial console. With 7.1 everything > worked fine, but with stable/8 things seem to break. [...] > Here's my setup (which worked perfectly fine with 7.1): > > /boot.config: > -P > > /boot/loader.conf: > kernel_options="-P" > console="comconsole" > > /etc/ttys: > ttyu0 "/usr/libexec/getty std.9600" vt100 off secure Shouldn't this: ^^^ be 'on'...? -- greg byshenk - gbysh...@byshenk.net - Leiden, NL > /boot/device.hints: > hint.uart.0.at="isa" > hint.uart.0.port="0x3F8" > hint.uart.0.flags="0x10" > hint.uart.0.irq="4" > > /var/run/dmesg.boot: > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart0: [FILTER] > uart0: console (9600,n,8,1) > > The serial port is connected to another PC that runs tip(1) > in a screen(1) session, using a 9-pin nullmodem cable. > That setup hasn't changed in ages; that other PC is running > an older version of FreeBSD. > > I need this issue to be resolved, because the serial console > is required for remote management (the machine is a 3-hours > ride away from home). If it can't be resolved, I will have > to downgrade it to 7.x. > > Best regards >Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- > chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > I suggested holding a "Python Object Oriented Programming Seminar", > but the acronym was unpopular. > -- Joseph Strout > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why is NFSv4 so slow?
> On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote: > > > > > > I am experiencing similar issues with newnfs: > > > > > > 1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s > > > reading > > > from the NFS4-share on Gbit-Lan > > > > > > 2) Mounting with -t newnfs -o nfsv3 results in no performance gain > > > whatsoever. > > > > > > 3) Mounting with -t nfs results in 58MiB/s ! (Netcat has similar > > > performance) ??? not a hardware/driver issue from my pov > > > > Ok, so it does sound like an issue in the experimental client and > > not NFSv4. For the most part, the read code is the same as > > the regular client, but it hasn't been brought up-to-date > > with recent changes. > > Do you (or will you soon) have some patches I/we could test? I'm > willing to try anything to avoid mounting ten or so subdirectories in > each of my mount points. > > > One thing you could try is building a kernel without SMP enabled > > and see if that helps? (I only have single core hardware, so I won't > > see any SMP races.) If that helps, I can compare the regular vs > > experimental client for smp locking in the read stuff. > > I can try disabling SMP too. Should that really matter, if you're not > even pegging one CPU? The locks shouldn't have *that* much overhead... > > -- Rick C. Petty > Just fyi, I asked folks to run read tests on the clients (over on freebsd-fs), Sofar, I've only gotten one response, but they didn't see the problem you are (they did see a factor of 2 slower, but it is still 50Mbytes/sec). Maybe you can take a look at their email and compare his client with yours? His message is: http://docs.FreeBSD.org/cgi/mid.cgi?01NRSE7GZJEC0022AD Btw, if anyone who didn't see the posting on freebsd-fs and would like to run a quick test, it would be appreciated. Bascially do both kinds of mount using a FreeBSD8.1 or later client and then read a greater than 100Mbyte file with dd. # mount -t nfs -o nfsv3 :/path / - cd anywhere in mount that has > 100Mbyte file # dd if= of=/dev/null bs=1m # umount / Then repeat with # mount -t newnfs -o nfsv3 :/path / and post the results along with the client machine's info (machine arch/# of cores/memory/net interface used for NFS traffic). Thanks in advance to anyone who runs the test, rick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
VBox 3.2.8 & SATA virtual disks & FreeBSD 8.1-STABLE 20100912 -- (virtual) harddisks are not found on boot...
Hello, Freebsd-stable. I have VirtualBox-based FreeBSD 8.1 installation (32 bit, VirtualBox 3.2.8, WinXP/x64 host, but I thinks that host config is irrelevant). Two virtual HDDs are atteched to virtual SATA adapter (channels 0 & 1) and CD/DVD attached to virtual IDE adapter (Primary master). I've used FreeBSD 8.1-STABLE builded about two months ago and everything worked Ok with "Standard" (not AHCI) driver, root FS is ad4s1a. I'veupdatedFreeBSDtoday (12/09/2010) with csup & buildworld/buildkernel/installworld/installkernel (GENERIC kernel). Nothing was changed in VM config/setup. Now it can not be booted because KERNEL doesn't see any HDDs and can not mount root FS. It shows only "acd0" as "GEOM managed disk device". bootloader sees disk and reads kernel & modules without problems. I've tried to "load ahci" on boot prompt, but result is almost the same. AHCI driver sees two channels, but got timeouts on both -- oops, can not mout root FS again. I've tried to load "vboxdrv" (it is build right after kernel & world, so it should be in-sync), but here is abother fault: kernel panics in "(swapper)" process right after "acd0" detection (wihtout vboxdrv kernel complains about missing root FS exactly at same moment). I've googled this problem, but without any success. What should I do to revive my VM? -- // Black Lion AKA Lev Serebryakov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: VBox 3.2.8 & SATA virtual disks & FreeBSD 8.1-STABLE 20100912 -- (virtual) harddisks are not found on boot...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 13 Sep 2010 00:14+0400, Lev Serebryakov wrote: > I've googled this problem, but without any success. What should I do > to revive my VM? Try using normal IDE controllers unless you really depend on the simulated AHCI controllers. Trond. - -- - -- Trond Endrestøl | trond.endres...@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX |FreeBSD 8.1-STABLE & Alpine 2.00 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkyNO/oACgkQbYWZalUoElvo0wCeLvJhlmzl6B1Wr/WbLtE2VFl9 YLkAnRaM4MZX9q9G87qcwU/Yru4gaTDw =V4Zm -END PGP SIGNATURE-___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: VBox 3.2.8 & SATA virtual disks & FreeBSD 8.1-STABLE 20100912 -- (virtual) harddisks are not found on boot...
Lev Serebryakov wrote: > I have VirtualBox-based FreeBSD 8.1 installation (32 bit, VirtualBox > 3.2.8, WinXP/x64 host, but I thinks that host config is irrelevant). > > Two virtual HDDs are atteched to virtual SATA adapter (channels > 0 & 1) and CD/DVD attached to virtual IDE adapter (Primary master). > > I've used FreeBSD 8.1-STABLE builded about two months ago and > everything worked Ok with "Standard" (not AHCI) driver, root FS is > ad4s1a. > > I'veupdatedFreeBSDtoday (12/09/2010) with csup & > buildworld/buildkernel/installworld/installkernel (GENERIC kernel). > > Nothing was changed in VM config/setup. > > Now it can not be booted because KERNEL doesn't see any HDDs and > can not mount root FS. It shows only "acd0" as "GEOM managed disk device". > > bootloader sees disk and reads kernel & modules without problems. > > I've tried to "load ahci" on boot prompt, but result is almost the > same. AHCI driver sees two channels, but got timeouts on both -- > oops, can not mout root FS again. If ahci(4) also fails - at least enable verbose boot messages and send me all that ahci(4) reports. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Serial console problems with stable/8
Greg Byshenk wrote: > On Sun, Sep 12, 2010 at 05:26:12PM +0200, Oliver Fromme wrote: > > > On Friday I have updated a machine from 7.1 to stable/8. > > It is connected to a serial console. With 7.1 everything > > worked fine, but with stable/8 things seem to break. > > [...] > > > Here's my setup (which worked perfectly fine with 7.1): > > > > /boot.config: > > -P > > > > /boot/loader.conf: > > kernel_options="-P" > > console="comconsole" > > > > /etc/ttys: > > ttyu0 "/usr/libexec/getty std.9600" vt100 off secure > > Shouldn't this: ^^^ > be 'on'...? Yes, of course it *was* on (which caused the symptoms I described). As I explained, I had to turn it off so I could at least use su(1) and shutdown(8) without freezing the whole thing. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > Can the denizens of this group enlighten me about what the > advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling checker than "perl". -- An unknown poster and Fredrik Lundh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Serial console problems with stable/8
On Mon, Sep 13, 2010 at 08:37:24AM +0200, Oliver Fromme wrote: > Greg Byshenk wrote: > > On Sun, Sep 12, 2010 at 05:26:12PM +0200, Oliver Fromme wrote: > > > > > On Friday I have updated a machine from 7.1 to stable/8. > > > It is connected to a serial console. With 7.1 everything > > > worked fine, but with stable/8 things seem to break. > > > > [...] > > > > > Here's my setup (which worked perfectly fine with 7.1): > > > > > > /boot.config: > > > -P > > > > > > /boot/loader.conf: > > > kernel_options="-P" > > > console="comconsole" > > > > > > /etc/ttys: > > > ttyu0 "/usr/libexec/getty std.9600" vt100 off secure > > > > Shouldn't this: ^^^ > > be 'on'...? > > Yes, of course it *was* on (which caused the symptoms > I described). As I explained, I had to turn it off so > I could at least use su(1) and shutdown(8) without > freezing the whole thing. Is there a PS/2 keyboard hooked up to this machine when you're attempting to get serial console output? If so, I'm not too surprised it doesn't work (re: -P flag). Can you try the following? 1) Removing kernel_options and console from loader.conf 2) Place "-P" in /boot.config instead If this doesn't change the behaviour, please replace -P and with -D -h and see if there's any improvement. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
