Re: em device hangs on ifconfig alias ...
Atanas wrote: Dan Nelson said the following on 6/28/06 3:52 PM: In the last episode (Jun 28), User Freebsd said: has anyone figured out why the em device 'hangs' for about 30-45 seconds whenever you ifconfig alias a new IP on to the device? The em driver resets the card when you add an IP to it, and unless you've configured your switch not to autodetect fancy features on that port, it may very well take 45 seconds for it to come up. For me the em reset actually takes about a second or so per single IP alias. But more aliases you got, longer the timeout becomes. In case you have hundreds (like I do), a single reboot might cost you something like 10-15 minutes of downtime, just for the aliases to come up. Does anybody know a better NIC driver alternative when dealing with lots of IP aliases? Regards, Atanas ___ For me its IP alias additions take 1 or maybe 2secs, but it is noticeable, but really isn't an issue for me. As far as I have noticed the em driver in 6.1 after being rebuilt is at its peak of driver quality, so much in fact that since 6.1 its recommended not to even bother with polling with em if you need maximum network performance as it won't go any faster, the em driver for 6.1 got very large performance improvement compared to older em driver versions before 6.1-release, which I suspect got over hacked over time. I am pretty sure I used to only be able to get 200,300mbits/sec max but now I can get up to 850mbits on some and on the lowest side 500mbits/sec on others which I suspect is due to cable quality etc. I am just thankful for it working as it is. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
On Thu, 29 Jun 2006, Fabian Keil wrote: I wish I could. The machine died before I read your message. I was logged in on the serial console running tail -f /var/log/messages. Last messages were: Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4275000(2048) val=a020c0de @ 0xc4275000 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4055800(2048) val=a020c0de @ 0xc4055800 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4ca(2048) val=a020c0de @ 0xc4ca Jun 29 00:42:20 tor kernel: Memory modified after free 0xc39ef000(2048) val=a020c0de @ 0xc39ef000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc4bd7000(2048) val=a020c0de @ 0xc4bd7000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3c8a000(2048) val=a020c0de @ 0xc3c8a000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc33bd000(2048) val=a020c0de @ 0xc33bd000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3f1d000(2048) val=a020c0de @ 0xc3f1d000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc45dc800(2048) val=a020c0de @ 0xc45dc800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc429e000(2048) val=a020c0de @ 0xc429e000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3aef800(2048) val=a020c0de @ 0xc3aef800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc432a000(2048) val=a020c0de @ 0xc432a000 Jun 29 00:42:24 tor kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=34263674 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3dff800(2048) val=a020c0d Ctrl+Alt+ESC didn't trigger any reaction, so I caused a reset through the ISP's webinterface. Now the system appears to be hosed, at least FreeBSD never reaches the login: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2 [nothing] Probably something which would be easy to resolve with keyboard access and a screen, but I think I'm forced to use the RecoveryManager. Unfortunately recovery means reinstalling the preconfigured GNU/Linux which I than can replace with FreeBSD again. If there ever was a core dump it will be gone, and so will be kernel.debug. On the bright side you can chose the OS to go with. Should I use Current to see if the problem still exists? The ATA error above is a bit distressing, as is the fact that it won't boot. Is [nothing] normally the FreeBSD boot loader rather than nothing? I would suggest running some hardware diagnostics to make sure we're dealing with reliable hardware before continuing so that we're not chasing both hardware and software problems, since you can't reliably debug software problems in the presence of hardware failures. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, 28 Jun 2006, User Freebsd wrote: On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). 'k, re-adding ... and I take it there is no more 'DDB_UNATTENDED' option? Something equivalent? This is now KDB_UNATTENDED, since it affects by DDB and GDB. KDB is the common debugger framework backend used to implement front-end debuggins ervices. Ya, figured this one out when I tried to compile ... someone might want to add a mention of the new options in the ddb man page though :) You mean like the following text in the ddb(4) man page? NAME ddb -- interactive kernel debugger SYNOPSIS options KDB options DDB To prevent activation of the debugger on kernel panic(9): options KDB_UNATTENDED Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
On Thu, 2006-Jun-29 17:30:07 +1000, Michael Vince wrote: For me its IP alias additions take 1 or maybe 2secs, but it is noticeable, but really isn't an issue for me. But it obviously is for Atanas, who has 100's of aliases. As far as I have noticed the em driver in 6.1 after being rebuilt is at its peak of driver quality, ... now I can get up to 850mbits on some and on the lowest side 500mbits/sec on others which I suspect is due to cable quality etc. In other words, the shortcomings of the em device/driver aren't an issue for you. Other people have different requirements and the em(4) is currently unsuitable for them. -- Peter Jeremy pgpCzMs0W9tP4.pgp Description: PGP signature
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
Robert Watson [EMAIL PROTECTED] wrote: On Thu, 29 Jun 2006, Fabian Keil wrote: I wish I could. The machine died before I read your message. I was logged in on the serial console running tail -f /var/log/messages. Last messages were: Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4275000(2048) val=a020c0de @ 0xc4275000 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4055800(2048) val=a020c0de @ 0xc432a000 Jun 29 00:42:24 tor kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=34263674 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3dff800(2048) val=a020c0d Ctrl+Alt+ESC didn't trigger any reaction, so I caused a reset through the ISP's webinterface. Now the system appears to be hosed, at least FreeBSD never reaches the login: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2 [nothing] The ATA error above is a bit distressing, as is the fact that it won't boot. Is [nothing] normally the FreeBSD boot loader rather than nothing? The 1 Linux ... part already is the FreeBSD boot loader. Normally it goes: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2 FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) login: I would suggest running some hardware diagnostics to make sure we're dealing with reliable hardware before continuing so that we're not chasing both hardware and software problems, since you can't reliably debug software problems in the presence of hardware failures. I'll see what the ports collection has to offer (running smartmontools right now) but so far it's the only ATA message I got. Probably something which would be easy to resolve with keyboard access and a screen, but I think I'm forced to use the RecoveryManager. Unfortunately recovery means reinstalling the preconfigured GNU/Linux which I than can replace with FreeBSD again. If there ever was a core dump it will be gone, and so will be kernel.debug. Lucky me. The RecoveryManager turned out to be a full featured PXE-booted GNU/Linux system. It allowed me to fetch and replace /dev/ad0s2a (/) through ssh. The system is online again. After fsck -y /dev/ad0s3d (/usr) the whole tor jail is gone, but the rest of this slice seems to be ok, including kernel.debug. I can't fsck /var: [EMAIL PROTECTED] ~]$ sudo fsck /dev/ad0s3d ** /dev/ad0s3d ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes fsck_4.2bsd: cannot alloc 1082190976 bytes for inoinfo but it can still be mounted. No core dump though. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: configuring sio1 for serial console ...
On Thu, 29 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). 'k, re-adding ... and I take it there is no more 'DDB_UNATTENDED' option? Something equivalent? This is now KDB_UNATTENDED, since it affects by DDB and GDB. KDB is the common debugger framework backend used to implement front-end debuggins ervices. Ya, figured this one out when I tried to compile ... someone might want to add a mention of the new options in the ddb man page though :) You mean like the following text in the ddb(4) man page? NAME ddb -- interactive kernel debugger SYNOPSIS options KDB options DDB To prevent activation of the debugger on kernel panic(9): options KDB_UNATTENDED Ack, I was probably reading on one of my 4.x boxes :( But, the handbook does need to be updated: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
On Thu, 29 Jun 2006, Peter Jeremy wrote: On Thu, 2006-Jun-29 17:30:07 +1000, Michael Vince wrote: For me its IP alias additions take 1 or maybe 2secs, but it is noticeable, but really isn't an issue for me. But it obviously is for Atanas, who has 100's of aliases. In my case, it isn't 100's, but the problem is noticeable ... I have my start up scripts, right now, do the ifconfig, sleep for 45 seconds, and then start up the jail ... and even then, apache doesn't *always* start up, since sometimes that isn't long enough for the network to come back up for DNS to be reachable :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Support for QLogic QLE2460 ?
Hi, At work, we recently bought a QLogic QLE2460 FC host adapter. However, FreeBSD doesn't seem to support this card. pciconf -lv gives: --- [EMAIL PROTECTED]:0:0: class=0x0c0400 card=0x01371077 chip=0x24321077 rev=0x02 hdr=0x00 vendor = 'QLogic Corporation' class= serial bus subclass = Fibre Channel --- man isp(4) does not mention support for this card, either. We tried adding the PCI ID, assuming the card is supported by the 2423 driver. However, this fails with: --- Qlogic ISP Driver, FreeBSD Version 5.9, Core Version 2.10 isp0: Qlogic ISP 2432 PCI Express FC-AL Adapter port 0xec00-0xecff mem 0xfe6fc000-0xfe6f irq 16 at device 0.0 on pci4 isp0: Reserved 0x4000 bytes for rid 0x14 type 3 at 0xfe6fc000 isp0: using Memory space register mapping ioapic0: routing intpin 16 (PCI IRQ 16) to vector 50 isp0: [GIANT-LOCKED] isp0: Polled Mailbox Command (0x0) Timeout device_attach: isp0 attach returned 6 --- Linux seems to have drivers for it, and the same goes for Solaris. Has anyone managed to get this card working on a FreeBSD 6 machine? I can't seem to find any support in it in -CURRENT either. Thanks, -- Rink P.W. Springer- http://rink.nu Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions. - Castlevania: Symphony of the Night pgpeAuPW8KjZm.pgp Description: PGP signature
Re: FreeBSD 6 and MySQL with DBs on a NAS
I wasn't able to find anyone seeing a similar problem as what I describe. I'm using FreeBSD 6.1, MySQL 5.0.21 built from ports and a NetApp share provided over NFS. Has anyone else ever seen the issue as described in the e-mail below? -- Mark P. Hennessy Alexey Karagodov [EMAIL PROTECTED] wrote: there was some problems with NFS on FreeBSD 6 ... try to google problem related to NFS or search this mailing list 2006/6/27, [EMAIL PROTECTED] [EMAIL PROTECTED] : Hi, I was wondering if anyone else had encountered this issue and/or come up with what needs to be done to resolve it: I currently have MySQL 5.0.22 built from ports on a FreeBSD 6.1 machine with the DB data residing on a NetApp share connected via NFS. A strange thing happens often after a few hours or a couple of days, some tables that are very active start to crash for no apparent reason as far as I can tell. Example output from check table tablename: ++---+--+---+ | Table | Op| Msg_type | Msg_text | ++---+--+---+ | dbname.tablename | check | warning | Table is marked as crashed | | dbname.tablename | check | error| Found key at page 18259968 that points to record outside datafile | | dbname.tablename | check | error| Corrupt | ++---+--+---+ Upon moving the DB data to a local drive, the system operates flawlessly and has done so for many weeks, but I really need to keep these data on the networked share. The problem didn't happen when I was using FreeBSD 4.11, it only started after upgrading to FreeBSD 6.0 or 6.1. A poster on a MySQL mailing list suggested perhaps it could be a file locking issue at the OS level and so I post my inquiry here. I've seen this happen on FreeBSD 6.0 and 6.1 with MySQL 4.1.x and MySQL 5.0.x built from ports. Has anyone else seen this and if so has a resolution been found? -- Mark P. Hennessy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
detached disk fsck lock
Hi all, I have several computers of different configurations (other motherboards, controllers). Each have 14-20 hdd devices (ATA SATA). All hdd is WDC WDJD or WDC WDJB. Computers periodically crashed with disk detached (random disk id) error: subdisk10: detached ad10: detached g_vfs_done():ad10s1h[READ(offset=289109770240, length=65536)]error = 6 g_vfs_done():ad10s1h[READ(offset=289297481728, length=131072)]error = 6 g_vfs_done():ad10s1h[READ(offset=296795766784, length=131072)]error = 6 -- skipped -- panic: vinvalbuf: dirty bufs Uptime: 13h32m44s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... After reboot, it's quite likely (20-30 percents) that fsck (running in background mode) lock in ufs state and can't be killed even by SIGKILL. After it all others processes working with that device lock in ufs state too. It's appear on all FreeBSD 6 versions, from 6.0 RELEASE to 6.1-STABLE. -- Best regards, bymer mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expensive timeout?
On Wed, 28 Jun 2006, User Freebsd wrote: On Wed, 28 Jun 2006, Jonathan Noack wrote: Please don't top-post... User Freebsd wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Just got this on the console of one of hte servers that has been causing problems ... Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s not a very informative error, and that is all that was there, nothing before, nothing after ... Oh, wait, does this have something to do with the Deadlock options I just added to the kernel? Yes, if you look in /sys/kern/kern_timeout.c you'll note that the Expensive timeout(9) function printf is inside an #ifdef DIAGNOSTIC. 'k, but is this something that I should be concerned about, or just ignore? You can convert it to a function name using the addr2line command combining the function pointer, 0xc0520e18, with your kernel.debug, then let us know. This is an advisory diagnostic message to let developers know a kernel function running in a time-critical path is taking too long to run, and is worth reporting. You probably don't want to run with DIAGNOSTIC unless you really want to. INVARIANTS+WITNESS are sufficient for most debugging. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with fetch
I'm a first time poster, so forgive me if this is the wrong list or if I break etiquette. Fetch frequently fails for me when installing ports via pkg_add or directly from the ports tree. Regardless of the port I'm trying to add, it almost always returns the following... Using 'pkg_add': --BEGIN SNIP-- [EMAIL PROTECTED]:~ 160:0# pkg_add -r xpdf Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz: Syntax error in parameters or arguments pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz' by URL --END SNIP-- Using ports directly: --BEGIN SNIP-- [EMAIL PROTECTED]:/usr/ports/graphics/xpdf 163:0# make install clean === Vulnerability check disabled, database not found = xpdf-3.01.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from ftp://ftp.foolabs.com/pub/xpdf/. fetch: ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/support/xpdf/. fetch: ftp://ftp.funet.fi/pub/TeX/CTAN/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ctan.unsw.edu.au/tex-archive/support/xpdf/. fetch: ftp://ctan.unsw.edu.au/tex-archive/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ftp.tex.ac.uk/tex-archive/support/xpdf/. fetch: ftp://ftp.tex.ac.uk/tex-archive/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ftp.kddlabs.co.jp/CTAN/support/xpdf/. fetch: ftp://ftp.kddlabs.co.jp/CTAN/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ctan.tug.org/tex-archive/support/xpdf/. fetch: ftp://ctan.tug.org/tex-archive/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from ftp://ftp.dante.de/tex-archive/support/xpdf/. fetch: ftp://ftp.dante.de/tex-archive/support/xpdf/xpdf-3.01.tar.gz: Syntax error in parameters or arguments = Attempting to fetch from http://ring.sakura.ad.jp/archives/text/CTAN/support/xpdf/. xpdf-3.01.tar.gz 100% of 585 kB 140 kBps = xpdf-3.01pl1.patch doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from ftp://ftp.foolabs.com/pub/xpdf/. fetch: ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.01pl1.patch: Syntax error in parameters or arguments = Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/xpdf-3.01pl1.patch: Syntax error in parameters or arguments = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/ports/graphics/xpdf. [EMAIL PROTECTED]:/usr/ports/graphics/xpdf 164:1# --END SNIP-- I think the key error in all of this is the part that says Syntax error in parameters or arguments. This only seems to happen with FTP sites as opposed to HTTP sites. I can retrieve said files with wget without a hitch, so I'm at a loss as to what's going on. I've frobbed nearly every knob that fetch has to no avail. I'm running 6.1: FreeBSD SS002.admin.siloamsprings.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:42:56 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 It's a fresh install, I'll probably update soon. I had the same problem in 5.4. Thank you in advance for any help you may be able to provide! cmh -- Christopher M. Hobbs Systems Technician, City of Siloam Springs [EMAIL PROTECTED], (479).524.5136 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Weird problem upgrading 5.4 to 6.1
Hi, I have FreeBSD 5.4 box with Intel865 chipset. The 5.4 works fine nearly a year. But strange troubles happens when I've tried to upgrade to 6.1 (via make buildworld make kernel). The loader show me following messages and then hangs when I try to boot new kernel: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0. Booting with old kernel works fine. Also BIOS see IDE drive. Googling don't get any relevant info. I've attached my kernel config. Does anybody have ideas how to fix this? TIA, Sergey Shyman PIONEER Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vanderpool on FreeBSD
On Wed, 28 Jun 2006, Mohacsi Janos wrote: Here is a link where you can find screenshot. http://skye.ki.iif.hu/~mohacsi/freebsd/xen-vt-freebsd.png I try to find a way to boot with serial console in order to capture the first error message. Regards, The first screen can be seen: http://skye.ki.iif.hu/~mohacsi/freebsd/xen-vt-freebsd2.png Any hint would welcome. Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 Dear All, Does anybody succeed to boot FreeBSD on an Intel Vanderpool capable machine? My colleague tried it and the result is a BTX halt as can be seen on the screenshot attached. He succesfully run unmodified Linux, Windows 2003 under Xen virtual machines, but FreeBSD failed in the boot phase. By the way what is the state of Xen port of FreeBSD? Thanks, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with fetch
Christopher Hobbs wrote: I'm a first time poster, so forgive me if this is the wrong list or if I break etiquette. Fetch frequently fails for me when installing ports via pkg_add or directly from the ports tree. Regardless of the port I'm trying to add, it almost always returns the following... Using 'pkg_add': --BEGIN SNIP-- [EMAIL PROTECTED]:~ 160:0# pkg_add -r xpdf Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz: Syntax error in parameters or arguments pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz' by URL --END SNIP-- ... This is probably better-suited to the freebsd-questions@ list, but I'll take a quick stab at it. Could it be that you're behind a firewall or FTP proxy that doesn't support active FTP transfers? You mentioned you tried several of the knobs for fetch, but did you try the same fetch with the -p flag? fetch -p ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Jun 28, 2006, at 6:28 PM, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: 'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? If configured to use a serial console (console=comconsole in loader.conf), you can enter the debugger with BREAK_TO_DEBUGGER in the kernel config by sending a serial break. With my portmasters, I telnet to a TCP port to connect to the serial console, so I send a telnet break, using ^]send break. I *used* to set BREAK_TO_DEBUGGER also, but I discovered (the hard, painful, revenue-costing way) that if you ever power cycle a Cyclades TS1000 terminal server, it sends a break signal down each and every serial line attached to it. So, now I configure my debuggering in the kernel like this: # Kernel debugging options KDB #Enable the kernel debugger options KDB_TRACE options KDB_UNATTENDED # Enable the ddb debugger backend. options DDB # break on sequence CR ~ ^b options ALT_BREAK_TO_DEBUGGER This lets me get the best of both worlds. It is amazing that the CR ~ ^b sequence will respond even when the box itself is totally unresponsive due to some runaway process or other shortage of memory condition. Another thing you may wish to consider is adding option SW_WATCHDOG then running the watchdog daemon. It may help you by panicking your way out of deadlock automatically. You could also investigate getting a hardware watchdog card that works with watchdogd.
Re: configuring sio1 for serial console ...
On Jun 28, 2006, at 6:36 PM, Freddie Cash wrote: BOOT_COMCONSOLE_SPEED=19220 As of 6.0 this no longer works beyond the stage 0 boot, ie, the kernel boot messages come at a different speed. The man page for boot says you can add -S to boot.config as of 6.0, but it didn't work until 6.1 (at least for me) to set the speed. There was big discussion about this on stable@ list a couple of months ago.
Re: configuring sio1 for serial console ...
On Jun 29, 2006, at 4:03 AM, Robert Watson wrote: To prevent activation of the debugger on kernel panic(9): options KDB_UNATTENDED My experience is that if you have a serial console, it assumes you're attended if there is carrier detected on the wire. Console servers seem to do this making this option a bit less than useful at times, but still worthy of inclusion.
Re: bad pte panic, no dump :(
On Wed, 2006-06-28 at 11:14 -0500, Larry Rosenman wrote: Greetings, FreeBSD/amd64 6.1-STABLE (June 18, 18:44 US/Central), running on Intel EM64T Xeons. got a one-off bad pte panic, and when it tried to dump to a gmirror slice, it hung. [...] The out of the blue, while talking IMAP to this one, got the bad pte panic. I've seen this twice now on my only amd64 machine: http://docs.FreeBSD.org/cgi/mid.cgi?1148482556.35287.18.camel Memory testing has so far revealed no issues. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Kostik Belousov writes: Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. Yes from a 6.1 stable around 6-25-06 What this means ? That you have _this_ revisions of the files, and your LA skyrocketed ? LA = load average? Our problem is vmstat 'b' column growing and nfs causing locks on the server side. When the machine locked it was running a background fsck. I saw Giant a lot in the status of the nfsd. I am really wondering if 6.1 is ready for production under heavy load. And for sure the NFS client in the whole 6.X line seems problematic (see my post in the stable list under subject: NFS clients freeze and can not disconnect). As for the vmstat, about the only thing doing anything even remotely appearing to be doing work is NFS. For instance I saw this in another thread: ps ax -O ppid,flags,mwchan | awk '($6 ~ /^D/ || $6 == STAT) $3 !~ /^20.$/' And in the machine in question it shows PID PPID F MWCHAN TT STAT TIME COMMAND 16124 16123 0 biowr ?? D 46:24.76 nfsd: server (nfsd) 16125 16123 0 biowr ?? D 16:05.58 nfsd: server (nfsd) 16126 16123 0 biowr ?? D 11:05.53 nfsd: server (nfsd) 16127 16123 0 biowr ?? D 8:01.21 nfsd: server (nfsd) 16128 16123 0 biowr ?? D 6:19.15 nfsd: server (nfsd) 16129 16123 0 biowr ?? D 5:01.27 nfsd: server (nfsd) 16130 16123 0 biowr ?? D 3:55.56 nfsd: server (nfsd) 16131 16123 0 biowr ?? D 3:13.11 nfsd: server (nfsd) 16132 16123 0 biowr ?? D 2:43.26 nfsd: server (nfsd) 16133 16123 0 biowr ?? D 2:16.40 nfsd: server (nfsd) 16134 16123 0 biowr ?? D 1:57.00 nfsd: server (nfsd) 16135 16123 0 biowr ?? D 1:41.02 nfsd: server (nfsd) 16136 16123 0 biowr ?? D 1:27.07 nfsd: server (nfsd) 16137 16123 0 biowr ?? D 1:15.25 nfsd: server (nfsd) 16138 16123 0 biowr ?? D 1:06.54 nfsd: server (nfsd) 16139 16123 0 biowr ?? D 0:57.57 nfsd: server (nfsd) 16140 16123 0 biowr ?? D 0:50.65 nfsd: server (nfsd) 16141 16123 0 biowr ?? D 0:44.60 nfsd: server (nfsd) 16142 16123 0 biowr ?? D 0:38.29 nfsd: server (nfsd) 16143 16123 0 biowr ?? D 0:34.21 nfsd: server (nfsd) 16144 16123 0 biowr ?? D 0:29.34 nfsd: server (nfsd) 16145 16123 0 biowr ?? D 0:26.35 nfsd: server (nfsd) 16146 16123 0 biowr ?? D 0:22.25 nfsd: server (nfsd) 16147 16123 0 biowr ?? D 0:18.17 nfsd: server (nfsd) 16148 16123 0 biowr ?? D 0:15.95 nfsd: server (nfsd) 16149 16123 0 biowr ?? D 0:13.66 nfsd: server (nfsd) 16150 16123 0 biowr ?? D 0:10.81 nfsd: server (nfsd) 16151 16123 0 biowr ?? D 0:08.92 nfsd: server (nfsd) 16152 16123 0 biowr ?? D 0:06.82 nfsd: server (nfsd) 16153 16123 0 biowr ?? D 0:05.16 nfsd: server (nfsd) 84338 100434100 ufs ?? D 0:02.00 qmgr -l -t fifo -u 91632 100434100 biowr ?? D 0:00.02 cleanup -z -t unix -u 91650 100434100 ufs ?? D 0:00.04 [smtpd] 91912 866354100 biowr ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 91916 905794100 biowr ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 71677 716724002 ppwait p1 D 0:00.15 -su (csh) The iostat for that machine shows: iostat 5 tty da0pass0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 130 15.35 109 1.63 0.00 0 0.00 6 0 6 1 87 0 36 10.43 230 2.34 0.00 0 0.00 3 0 2 1 93 0 12 10.81 280 2.96 0.00 0 0.00 6 0 2 0 92 0 12 13.03 259 3.30 0.00 0 0.00 0 0 1 1 98 0 12 12.87 259 3.26 0.00 0 0.00 5 0 2 1 91 0 12 17.17 228 3.82 0.00 0 0.00 8 0 3 1 87 0 12 18.38 306 5.49 0.00 0 0.00 3 0 2 1 94 0 12 14.53 284 4.04 0.00 0 0.00 6 0 3 1 89 0 12 26.03 213 5.41 0.00 0 0.00 5 0 3 2 91 Before that machine went into production, during the stress test I saw the machine do 700+ tps and substantially more MB/s. We also have another machine identical hardware wise and although it's tps is 50 to 100 less than this one.. the machine is always ver low in the 'b' column. I am trying now to read up in vmstat.. to see if I can see anything wrong in vmstat -s 1660720108 cpu context switches 736683712 device interrupts 46973243 software interrupts 99310719 traps 3405487756 system calls 46 kernel threads created 385149 fork() calls 7785 vfork() calls 0 rfork() calls 2809 swap pager pageins 4449 swap pager pages paged in 2027 swap pager pageouts 4609 swap pager pages paged out
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Thu, Jun 29, 2006 at 01:38:54PM -0400, Francisco Reyes wrote: Kostik Belousov writes: Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. Yes from a 6.1 stable around 6-25-06 What this means ? That you have _this_ revisions of the files, and your LA skyrocketed ? LA = load average? Our problem is vmstat 'b' column growing and nfs causing locks on the server side. When the machine locked it was running a background fsck. I saw Giant a lot in the status of the nfsd. This seems to be a different issue. BTW, I have already heard complaints about deadlocks caused by combination of nfsd and snapshots. Probably, I will look into this, but cannot give you estimations when. For now, you could turn off background fsck. pgpWAqck5MnOg.pgp Description: PGP signature
Re: FreeBSD 6 and MySQL with DBs on a NAS
[EMAIL PROTECTED] writes: I wasn't able to find anyone seeing a similar problem as what I describe. I'm using FreeBSD 6.1, MySQL 5.0.21 built from ports and a NetApp share provided over NFS. Recently we have been having problems with Mysql in 6.X (1 machine 6.0 stable and another 6.1 Stable). In our case it seems the Mysql (4.X from ports) was either causing or contributing to the machine crashing. Has anyone else ever seen the issue as described in the e-mail below? I also saw another thread describing Mysql problems in 6.X.. that is what made me check in our system if the crashes were related to mysql. One machine crashed 4 times in 5 days. So far since removing mysql it has been ok.. but it has only been 2 days since we removed mysql from the machine. I currently have MySQL 5.0.22 built from ports on a FreeBSD 6.1 machine with the DB data residing on a NetApp share connected via NFS. Isn't this a bad idea to begin with? Using an NFS mount to do database work. Also NFS in 6.X... specially the client seems to have issues. I am even considering to move my 6.X machines that are NFS clients back to 5.5 if I can't find a fix. In particular if a server dies, the client in 6.X freezes the machine if you try to connect to the path that was mounted on the NFS server. Soft mount did not help. strange thing happens often after a few hours or a couple of days, some tables that are very active start to crash for no apparent reason as far as I can tell. I could be wrong, but I think doing a database over NFS is likely not a good idea from a performance and stability standpoint. Specially a heavily used database. Upon moving the DB data to a local drive, the system operates flawlessly and has done so for many weeks, but I really need to keep these data on the networked share. Why do you need it in the networked share? The problem didn't happen when I was using FreeBSD 4.11, it only started after upgrading to FreeBSD 6.0 or 6.1. As I wrote above.. I have very little (approaching none) faith in the NFS client in 6.X Where I work we are even tying to see if we can get a hold of one of the NFS developers in FreeBSD and even pay to have this issue looked at.. So far I wrote to two of them, but have not heard back from them. I believe I have 2 more names to try, beyond that I am not sure we can remain with 6.X on the nfs clients. I have yet to try automaunt to see if that would help, but in general even when the server is up I kind of wonder if the client is stable. A poster on a MySQL mailing list suggested perhaps it could be a file locking issue at the OS level and so I post my inquiry here. That is one of the reasons I am suggesting against using a NFS share to do DB work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Thu, Jun 29, 2006 at 01:38:54PM -0400, Francisco Reyes wrote: I am really wondering if 6.1 is ready for production under heavy load. And for sure the NFS client in the whole 6.X line seems problematic (see my post in the stable list under subject: NFS clients freeze and can not disconnect). It's not easily possible for a FreeBSD developer to put these kinds of stresses on a machine, so we rely on our users to help us with these problems. In particular, if it is possible for people to create synthetic workloads based on their own codebases, on non-production machines, these problems are more likely to be solved. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Mark Linimon writes: It's not easily possible for a FreeBSD developer to put these kinds of stresses on a machine, so we rely on our users to help us with these problems. And this is why I have been trying to someone to PAY him/her to help us. I have been trying to find if anyone that works with the NFS code in FreeBSD would have time to work with us on a consulting bases to get the NFS client in 6 fixed. As for the vmstat problem with that machine.. the same.. if someone was willing to help us track down what in 6.X .. or even our settings.. is causing this heavy load we would definitely be willing to pay. Should I contact the FreeBSD foundation for this? In particular the NFS client is a killer problem for us. Anyone can recommend who to talk to? Should I be writing to the filesystem list? I am not sure how much of a problem the nfs server side is, but the client in the whole 6.X line has been problematic for us. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Kostik Belousov writes: This seems to be a different issue. BTW, I have already heard complaints about deadlocks caused by combination of nfsd and snapshots. I think you can add: nfsd + background fsck too. Probably, I will look into this, but cannot give you estimations when. Thank!! For now, you could turn off background fsck. We did.. and it was horrible.. It seems mysql was crashing the machine so we had 4 reboots in about 5 days. Since we had to give up on background fsck, that meant 2 hours every time the machine rebooted (the machine in question has 10+ million files in the volume which takes the 2 hours to fsck). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Thu, 29 Jun 2006, Francisco Reyes wrote: Kostik Belousov writes: Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. Yes from a 6.1 stable around 6-25-06 What this means ? That you have _this_ revisions of the files, and your LA skyrocketed ? LA = load average? Our problem is vmstat 'b' column growing and nfs causing locks on the server side. When the machine locked it was running a background fsck. I saw Giant a lot in the status of the nfsd. 'k, you are going through something similar to me, it seems ... have you implemented the stuff on: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html and: enabled DDB within your kernel? (man ddb) ... DDB is required for the deadlocks debugging ... also, is this a machine you have 'easy hands on' for? (ie. in my case, I'm dealing with remote servers, which is *really* fun) ... Actually, what you will want to do is setup a serial console if you can, so that you can 'trap the output' of the commands that stuff like ps and all that will throw out from DDB, unless you *really* like to write? I can help you get this all setup offlist if you wish, just email me and we'll work through the steps required ... once you have a debug environment in place, then generating a good/complete/in depth problem report is easier ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Thu, Jun 29, 2006 at 01:57:13PM -0400, Francisco Reyes wrote: And this is why I have been trying to someone to PAY him/her to help us. OK, sorry, I had not picked this up from the thread, which I had mostly just been scanning. My apologies. Should I contact the FreeBSD foundation for this? You can ask, but the Foundation AFAICT isn't really set up for something like this. They are mostly looking at funding new initiatives, again, from what I can tell. Currently there's no right way to do this. I'd like to see someone set up a marketplace for things like this but I don't have time to do it myself (plus, I would participate -- a definite conflict of interest). In the meantime you can try posting to freebsd-jobs@ and/or look through the list of FreeBSD Consulting Service Providers at http://www.freebsd.org/commercial/consult_bycat.html. It also references http://berklix.com/~jhs/consultants/, but I don't know if that is up-to-date. Finally, I'd happily take on the job myself, but I'd be lying if I said I knew anything about the problem at hand :-) Good luck. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Where to start from
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Jakubik Sent: Wednesday, June 28, 2006 4:26 PM To: Mihir Sanghavi Cc: freebsd-stable@freebsd.org Subject: Re: Where to start from Mihir Sanghavi wrote: Hi, I have installed FreeBSD 5.5 . My computer is still not hooked to the network. I would like to start working on it. what should I start with as I have never worked with BSD before. are there any good tutorials to start with? Thanks Start again, this time install FreeBSD 6.1 instead. Then proceed to http://www.freebsd.org/docs.html . DSW A number of us suggested that he start conservatively, Mike, based on what his needs would be. I wrote him a long e-mail that discussed the pros and cons of each RELEASE stream, and he's made his choice. Since you yourself are having some heartburn with RELENG_6, perhaps you can sympathize with someone who doesn't need the grief while trying to learn? ;-] Mihir, the Handbook is also resident on your computer in /usr/share/doc/(en|your language)/books/handbook I suggest that you read everything in books and articles first (assuming you've loaded the package or port for a web browser like Mozilla or Firefox), then type 'man man' at a prompt. More precise finger-pointing will have to follow more detail as to your desired usage, but let me suggest that freebsd-questions would be more appropriate for such discussions. This list is for technical discussions related to ongoing bugfixing and upgrades to the system. Another good resource is http://www.daemonnews.org, and the online forum there is also a good place to ask for suggestions. -- Don WildeOrg 01737505-844-1126 Earth Halted: Please reboot to continue ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS Locking Issue
This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. That's when I ran across the rpc.lockd issues that have been discussed earlier. Our production setup has diskless clients running KDE, which due to this bug is now dead on 6.1. I also have my mail server delivering messages to a file server via NFS. I even have servers booting diskless with NFS provided file systems... all of which are dead on 6.1. The last discussion our bug updates I've seen on this issue were about 3 months ago. This leaves me with a number of questions I hope can be answered here on this list. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? Is anyone working on a fix for this? If so, is there any kind of time frame where this fix might be MFC'd to 6-STABLE? I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Later on, -- Michael Collette IT Manager TestEquity LLC [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
me - too ... 2006/6/29, Michael Collette [EMAIL PROTECTED]: This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. That's when I ran across the rpc.lockd issues that have been discussed earlier. Our production setup has diskless clients running KDE, which due to this bug is now dead on 6.1. I also have my mail server delivering messages to a file server via NFS. I even have servers booting diskless with NFS provided file systems... all of which are dead on 6.1. The last discussion our bug updates I've seen on this issue were about 3 months ago. This leaves me with a number of questions I hope can be answered here on this list. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? Is anyone working on a fix for this? If so, is there any kind of time frame where this fix might be MFC'd to 6-STABLE? I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Later on, -- Michael Collette IT Manager TestEquity LLC [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- С Уважением, Алексей Карагодов. Проектирование, построение, администрирование и поддержка информационных систем. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1 and ATA problems
Hello, It seems that I'm having problems with 6.1 (6-STABLE) and ATA. This particular system is an ASUS P3V4X, which is a VIA (Apollo Pro) chipset. I installed 6.0 (From CD) on the system just fine, then I built a gmirror using ad0 and ad2. I then proceeded to update to 6-STABLE. One I rebooted, ad2 just disappeared. I tried all sorts of things. If I removed all devices except ad2, the system would boot the kernel and then when it went to mount root it wouldn't find any drives. If I move ad2 to ad1 (slave on ata0), the drive shows up fine. I currently have my two mirrored drives on ad0/ad1 and I put a cdrom drive on ata1. ata1 is detected just fine but nothing is probed on that channel. Here's my dmesg: FreeBSD 6.1-STABLE #0: Thu Jun 29 13:37:27 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEPTUNE Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (752.83-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073725440 (1023 MB) avail memory = 1045999616 (997 MB) kbd1 at kbdmux0 acpi0: ASUS P3V_4X on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C596B UDMA66 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd800-0xd80f at device 4.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, USB at device 4.2 (no driver attached) pci0: bridge, HOST-PCI at device 4.3 (no driver attached) rl0: Accton MPX 5030/5038 10/100BaseTX port 0xd000-0xd0ff mem 0xe080-0xe08000ff at device 9.0 on pci0 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:29:54:ae:da pci0: multimedia, audio at device 11.0 (no driver attached) fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 752826072 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled ad0: 9787MB WDC AC310200R 17.01J17 at ata0-master UDMA66 ad1: 9787MB WDC WD102AA 80.10A80 at ata0-slave UDMA66 GEOM_MIRROR: Device gm0 created (id=291540166). GEOM_MIRROR: Device gm0: provider ad0 detected. GEOM_MIRROR: Device gm0: provider ad1 detected. GEOM_MIRROR: Device gm0: provider ad0 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. GEOM_MIRROR: Device gm0: rebuilding provider ad1. Trying to mount root from ufs:/dev/mirror/gm0a Accounting enabled Basically, no matter what device I put on ata1, it disappears until 6.1. When booting under 6.0, everything shows up fine. I'd be happy to forward additional information as needed. Please let me know. Thanks, Jaime Bozza ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Force ugen device for printer?
Hi all, how can I force my system (6.1-STABLE) to create a ugen device for my printer? My printer, a HP PSC 1610 is recognized as a ulpt device and the cardreader on it as umass. Printing on the ultp device works fine, but I cannot use the scanner function with sane. I tried the hplip driver (/usr/ports/printing/hplip) to solve the scanning problem, but it only works on ugen devices. When I kldunload the ulpt and umass modules from my kernel before connecting the printer, it creates a ugen device and everything works fine. My problem is, that I need at least the umass module for USB sticks and my external harddisk. So my question is, can I configure devd or something else to not create a ulpt and umass device for my printer but create a ugen device (maybe by matching the vendor ID of the printer)? Thanks, Christian Schade signature.asc Description: OpenPGP digital signature
Re: NFS Locking Issue
Michael Collette writes: This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. I wish I had done that.. :-( That's when I ran across the rpc.lockd issues that have been discussed earlier. I am not familiar with that, but I can tell you from experience that the nfs client code in 6.X has issues.. In particular if the server goes down the client machine doesn't allow you to unmount the volume.. and if you have programs trying to acces the downed mount, the whole machine may end up freezing. ... I also have my mail server delivering messages to a file server via NFS. We use NFS as our storage sever for pop/imap, but use the MTA to deliver to the machine. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? It is for us.. I am even trying to see if we can even pay someone to expedite getting NFS fixed in 6. Unfortunately we decided to increase our NFS usage after I had installed 6.X in a number of new machines. Is anyone working on a fix for this? If there is I have not read about it. I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. I am fairly new to NFS.. but I am getting the impression that FreeBSD's NFS is not as mature as other platforms. I also think it has a lot to do with usage patterns. I have seen mentions of people having hundreds of clients connected to a single NFS server... yet I see problems with just a handfull of clients. Maybe the issue is only with the 6.X branch. Sadly part of the reason I moved some newer machines to 6.X was because of some comments I saw on how NFS had been improved in 6.X :-( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
If_ndis with marvel strange problem.
Ok, so... I have asus wl108g a marvell chipset. I'm running: FreeBSD silentbox 5.5-RELEASE FreeBSD 5.5-RELEASE #0: Tue May 23 14:58:27 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The card can't accosiate with APs, only with Ad-Hoc modes cards!? I've found a drivers for 'client' mode card at asus site and compiled it with ndisgen. the driver loads ok after kldload: --- no match for ObfReferenceObject no match for _except_handler3 no match for MmProbeAndLockPages no match for MmUnlockPages ndis0: ASUS 802.11b/g Network Adapter mem 0xd311-0xd311,0xd310-0xd310 irq 5 at device 8.0 on pci1 ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00:11:d8:85:ca:0f ndis0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 1Mbps 2Mbps 5.5Mbps 11Mbps --- the card is in ifconfig ndis0: #ifconfig ndis0 ndis0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:11:d8:85:ca:0f media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel -1 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 ok, so here we go... on one computer (a linux box) I set: #iwconfig wlan0 essid test channel 1 enc 12345678901234567890123456 mode Ad-Hoc on the fbsd box I do: #ifconfig ndis0 ssid test channel 1 weptxkey 1 wepkey 1:0x12345678901234567890123456 wepmode on mediaopt adhoc up and I get the ndis0 card associated with test ssid to the other linux box card! Even running encryption. but when I do: #ifconfig ndis0 ssid myap channel 9 weptxkey 1 wepkey 1:0x3974d8d297cc86284ca4e4251f wepmode on up well... nothing happens, the card blinks a few times for transmission and nothing, stays in status no carrier and an empty ssid! I can't get the point? I've tested setting other mediaopt than Adhoc but the driver returns error Please HELP! Thank you very much! Any ideas are welcome! This message was sent using IMP, the Internet Messaging Program. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird problem upgrading 5.4 to 6.1
Sergey Shyman writes: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0. Is that a RAID you are booting from? Booting with old kernel works fine. Also BIOS see IDE drive. Single IDE drive? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
Rong-en Fan wrote: On 6/29/06, Michael Collette [EMAIL PROTECTED] wrote: This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. That's when I ran across the rpc.lockd issues that have been discussed earlier. Our production setup has diskless clients running KDE, which due to this bug is now dead on 6.1. I also have my mail server delivering messages to a file server via NFS. I even have servers booting diskless with NFS provided file systems... all of which are dead on 6.1. The last discussion our bug updates I've seen on this issue were about 3 months ago. This leaves me with a number of questions I hope can be answered here on this list. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? Is anyone working on a fix for this? If so, is there any kind of time frame where this fix might be MFC'd to 6-STABLE? I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Try 6.1-STABLE, especially make sure you have $FreeBSD: src/usr.sbin/rpc.lockd/kern.c,v 1.16.2.1 2006/06/02 01:20:58 rodrigc Exp $ for usr.sbin/rpc.lockd/kern.c, and see if this helps. I am running STABLE on all my test boxes, and the problem is very much there. It's not everything that locks up though. I'm able to bring X up with twm, but unable to launch any Gnome or KDE applications without them being stranded in a lock state. I sure would have loved for your suggestion to be correct. For what it's worth, all the boxes I'm working with are on STABLE no more than a week old. I ran fresh build worlds on all of them before getting the rest of my configs going. Thanks, -- Michael Collette IT Manager TestEquity LLC [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
On Thu, 29 Jun 2006 22:25:30 +0200, Michael Collette [EMAIL PROTECTED] wrote: Rong-en Fan wrote: On 6/29/06, Michael Collette [EMAIL PROTECTED] wrote: This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. That's when I ran across the rpc.lockd issues that have been discussed earlier. Our production setup has diskless clients running KDE, which due to this bug is now dead on 6.1. I also have my mail server delivering messages to a file server via NFS. I even have servers booting diskless with NFS provided file systems... all of which are dead on 6.1. The last discussion our bug updates I've seen on this issue were about 3 months ago. This leaves me with a number of questions I hope can be answered here on this list. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? Is anyone working on a fix for this? If so, is there any kind of time frame where this fix might be MFC'd to 6-STABLE? I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Try 6.1-STABLE, especially make sure you have $FreeBSD: src/usr.sbin/rpc.lockd/kern.c,v 1.16.2.1 2006/06/02 01:20:58 rodrigc Exp $ for usr.sbin/rpc.lockd/kern.c, and see if this helps. I am running STABLE on all my test boxes, and the problem is very much there. It's not everything that locks up though. I'm able to bring X up with twm, but unable to launch any Gnome or KDE applications without them being stranded in a lock state. I sure would have loved for your suggestion to be correct. For what it's worth, all the boxes I'm working with are on STABLE no more than a week old. I ran fresh build worlds on all of them before getting the rest of my configs going. Thanks, Hello, I run my client with the -L mount option. This makes NFS locks local to the client, which is a workaround for me. If you depend on locks enforced on the server it wil not work. Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS Locking Issue
I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. It is first time since years i have no problem. It certainly did not work with FreeBSD-5 and i still have a machine with FreeBSD-6.0 which does not work properly (frequently loses the NFS mount, but it gets remounted some times later by amd). Anyways i have exactly 0 problem with the 6.1 machine. I could extend that to say that everything works very well on that machine, nothing is slow, including disk access. This has not always been the case. Stability wise, i have not seen any panic, hang or whatever since i have compiled a kernel adapted to my hardware. I got a panic with the generic kernel soon after installation, but now machine is totally stable. -- Michel TALON ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-STABLE panic
I have an odd problem with 6.1 where it panics, and then when it reboots the
system hangs solid just after printing how much memory is in the system, the
only way out is the reset switch.
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xb6
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0512564
stack pointer = 0x28:0xdea06b1c
frame pointer = 0x28:0xdea06b4c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 3
current process = 1114 (Xorg)
trap number = 12
panic: page fault
Uptime: 1d16h47m39s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335
319 303 28
7 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc04eaf44 in boot (howto=260) at /data/src/sys/kern/kern_shutdown.c:409
#2 0xc04eb1dc in panic (fmt=0xc06462f7 %s)
at /data/src/sys/kern/kern_shutdown.c:565
#3 0xc06262dc in trap_fatal (frame=0xdea06adc, eva=182)
at /data/src/sys/i386/i386/trap.c:836
#4 0xc0626043 in trap_pfault (frame=0xdea06adc, usermode=0, eva=182)
at /data/src/sys/i386/i386/trap.c:744
#5 0xc0625ca1 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = 8191, tf_esi = 14, tf_ebp
= -559912116, tf_isp = -559912184, tf_ebx = -1010665600, tf_edx
= -1007513240, tf_ecx = 0, tf_eax = -1066928096, tf_trapno = 12, tf_err = 0,
tf_eip = -1068423836, tf_cs = 32, tf_eflags = 2175622, tf_esp = -106823,
tf_ss = -1007513240})
at /data/src/sys/i386/i386/trap.c:434
#6 0xc0615b3a in calltrap () at /data/src/sys/i386/i386/exception.s:139
#7 0xc0512564 in soo_poll (fp=0xe, events=-559912044, active_cred=0xdea06b84,
td=0x40) at /data/src/sys/kern/sys_socket.c:232
#8 0xc050cff1 in kern_select (td=0xc3c27780, nd=64, fd_in=0x81bf7c0,
fd_ou=0x0,
fd_ex=0x0, tvp=0xdea06cd0) at /data/src/sys/kern/sys_generic.c:763
#9 0xc050cc40 in select (td=0xc3c27780, uap=0xdea06d04)
---Type return to continue, or q return to quit---
at /data/src/sys/kern/sys_generic.c:667
#10 0xc06265f3 in syscall (frame=
{tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 0, tf_esi = -1, tf_ebp
= -1077941800, tf_isp = -559911580, tf_ebx = -1, tf_edx = 0, tf_ecx = 0,
tf_eax = 93, tf_trapno = 22, tf_err = 2, tf_eip = 673900391, tf_cs = 51,
tf_eflags = 2110098, tf_esp = -1077942388, tf_ss = 59})
at /data/src/sys/i386/i386/trap.c:981
#11 0xc0615b8f in Xint0x80_syscall ()
at /data/src/sys/i386/i386/exception.s:200
#12 0x0033 in ?? ()
I am using the 'nv' driver - normally I use the nvidia one but I was trying
to reduce the number of variables.
I have run memtest86 for a while as well and cpuburn with no adverse results.
The system seems to crash every few days although this is the first one I had
since installing a debug kernel so maybe they are different, however the
non-debug ones looked the same as each other.
This system was originally a Duron 800 and I was having stability issues so
I updated it to a Sempron 3300+ (still i386), there is no one piece of
original
hardware in the system (there was a TV tuner card but I removed that for
test purposes).
The verbose dmesg was shortened so I don't have a full copy, I have attached
the partial verbose dmesg and the full normal dmesg.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pcib0: matched entry for 0.10.INTA
pcib0: slot 10 INTA hardwired to IRQ 18
found- vendor=0x1106, dev=0x3149, revid=0x80
bus=0, slot=15, func=0
class=01-04-00, hdrtype=0x00, mfdev=1
cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords)
lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=b, irq=11
powerspec 2 supports D0 D3 current D0
map[10]: type 4, range 32, base e000, size 3, enabled
map[14]: type 4, range 32, base e100, size 2, enabled
map[18]: type 4, range 32, base e200, size 3, enabled
map[1c]: type 4, range 32, base e300, size 2, enabled
Re: Force ugen device for printer?
On Thursday 29 June 2006 16:01, Christian Schade wrote: Hi all, how can I force my system (6.1-STABLE) to create a ugen device for my printer? My printer, a HP PSC 1610 is recognized as a ulpt device and the cardreader on it as umass. Printing on the ultp device works fine, but I cannot use the scanner function with sane. I tried the hplip driver (/usr/ports/printing/hplip) to solve the scanning problem, but it only works on ugen devices. When I kldunload the ulpt and umass modules from my kernel before connecting the printer, it creates a ugen device and everything works fine. I'm working on enhancing the relability of the hpiod interaction, but I am running low on time right now. My problem is, that I need at least the umass module for USB sticks and my external harddisk. So my question is, can I configure devd or something else to not create a ulpt and umass device for my printer but create a ugen device (maybe by matching the vendor ID of the printer)? So if you don't kldload ulpt, but kldload umass you don't get some ugen endpoints and a umass device? Would you provide a the output of usbdevs -vvv. Thanks, -- Anish Mistry pgpGMXDeP6WH1.pgp Description: PGP signature
Re: bad pte panic, no dump :(
On Wed, 28 Jun 2006, Larry Rosenman wrote: Greetings, FreeBSD/amd64 6.1-STABLE (June 18, 18:44 US/Central), running on Intel EM64T Xeons. got a one-off bad pte panic, and when it tried to dump to a gmirror slice, it hung. I've seen this, too, on FreeBSD 6.1-PRERELEASE #6: Thu Feb 9 01:01:54 WST 2006 i386. It only appears to occur under load, so I suspect a hardware problem. I am taking this server offline in the next few weeks to try and track it down. Hope it doesn't happen again! David Adam [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
Michel Talon writes: Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. What volume are we talking about? My own problems and other reports I see are all under heavy load. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quota and snapshots in 6.1-RELEASE
Konstantin Belousov wrote: On Tue, Jun 06, 2006 at 01:49:04PM -0400, Mike Jakubik wrote: Scott Long wrote: Dmitriy Kirhlarov wrote: Hi! On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want If you use snapshots with your quotas, update to 6.1-STABLE. If you Sorry, guys. You are mean RELENG_6_1 or RELENG_6? WBR RELENG_6. However, the changes will likely make their way into RELENG_6_1 in a few weeks as part of an errata update. Scott I have just done tests on 6.1-R and RELENG_6 as of yesterday evening. Unfortunately both still lock up hard, no crash, just a frozen system. I cant enter the KDB (ddb) via the console, but its unusable, as it wont let me type in anything. There must be some other change in -CURRENT that fixes this, as -CURRENT did not freeze during my previous tests. Just to confirm, here is the ID of ufs_quota.c on my RELENG_6 system: /usr/src/sys/ufs/ufs/ufs_quota.c: $FreeBSD: src/sys/ufs/ufs/ufs_quota.c,v 1.74.2.4 2006/05/14 00:23:27 tegge Exp $ The hangs are mostly related to snapshots. It would be better to update to the latest RELENG_6. Hangs on RELENG_6_1 is not so much interesting. For hanged RELENG_6 system, please do what described below and post the log of the ddb session. I'm not sure whether kbdmux was MFCed into RELENG_6 (AFAIR, yes). If you have it in your kernel, add the line hint.kbdmux.0.disabled=1 into the /boot/device.hints to make ddb usable. After that, on the hang, enter ddb, and do ps and tr pid for all suspected processes. Better yet, add the following options to your kernel: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC and, after hang, do in ddb show allpcpu show alllocks show lockedvnods ps For each process mentioned in show output, do where pid (for threaded processes, do thread thread-id; where). BTW, it would be great to add this instructions to the FAQ. Well, i finally got around to setting up a serial console on this box, the following is the output from the debugger after the system stopped responding. Let me know if you need any more/different information, i also made the kernel changes you recommended. FreeBSD 6.1-STABLE #1: Thu Jun 10 00:22:29 EDT 2006 --- KDB: enter: Line break on console [thread pid 12 tid 14 ] Stopped at kdb_enter+0x30: leave db ps pid proc uid ppid pgrp flag stat wmesgwchan cmd 552 c36228302 550 549 0004000 [SLPQ flswai 0xc0707c24][SLP] rm 550 c35708302 549 549 0004000 [SLPQ wait 0xc3570830][SLP] sh 549 c342ec482 548 549 0004000 [SLPQ wait 0xc342ec48][SLP] sh 548 c36226240 422 422 000 [SLPQ piperd 0xc36027f8][SLP] cron 547 c361f8300 524 547 0004002 [SLPQ ufs 0xc3777c94][SLP] ls 546 c36bc4180 544 544 0004002 [SLPQ wdrain 0xc0707be4][SLP] fsck_4.2bsd 544 c36bcc480 511 544 0004002 [SLPQ wait 0xc36bcc48][SLP] fsck 524 c35e020c0 522 524 0004002 [SLPQ wait 0xc35e020c][SLP] bash 522 c3570c480 406 522 0004100 [SLPQ flswai 0xc0707c24][SLP] sshd 515 c36bc20c0 0 0 204 [SLPQ wdrain 0xc0707be4][SLP] md0 511 c36bb6240 500 511 0004002 [SLPQ wait 0xc36bb624][SLP] bash 509 c3570418 65 1 509 100 [SLPQ select 0xc0707644][SLP] dhclient 500 c361fa3c0 406 500 0004100 [SLPQ flswai 0xc0707c24][SLP] sshd 480 c342ea3c0 1 256 000 [SLPQ select 0xc0707644][SLP] dhclient 465 c361f6240 1 465 0004002 [SLPQ ttyin 0xc342b010][SLP] getty 464 c35e0c480 1 464 0004002 [SLPQ ttyin 0xc3429410][SLP] getty 463 c356fa3c0 1 463 0004002 [SLPQ ttyin 0xc3429810][SLP] getty 462 c356f4180 1 462 0004002 [SLPQ ttyin 0xc343f010][SLP] getty 422 c342e6240 1 422 000 [SLPQ nanslp 0xc06ba32c][SLP] cron 416 c356f000 25 1 416 100 [SLPQ pause 0xc356f034][SLP] sendmail 412 c356f6240 1 412 100 [SLPQ select 0xc0707644][SLP] sendmail 406 c35e0 1 406 100 [SLPQ select 0xc0707644][SLP] sshd 290 c361f20c0 1 290 000 [SLPQ flswai 0xc0707c24][SLP] syslogd 256 c36224180 1 256 000 [SLPQ select 0xc0707644][SLP] devd 145 c356f8300 1 145 000 [SLPQ pause 0xc356f864][SLP] adjkerntz 38 c3378c480 0 0 204 [SLPQ - 0xd56f5cf8][SLP] schedcpu 37 c342d0000 0 0 204 [SLPQ sdflush 0xc070a3b4][SLP] softdepflush 36 c342d20c0 0 0 204 [SLPQ vlruwt 0xc342d20c][SLP] vnlru 35 c342d4180 0 0 204 [SLPQ ufs 0xc363c46c][SLP] syncer 34 c342d6240 0 0 204 [SLPQ wdrain 0xc0707be4][SLP] bufdaemon 33 c342d8300 0 0 20c [SLPQ pgzero 0xc070b324][SLP] pagezero 32 c342da3c0
Re: em device hangs on ifconfig alias ...
Atanas writes: I have some newer machines with 2 Broadcom chips on-board. I plan to give them a try at some point in the future, but I'm not sure how stable the bge driver For us they have been a problem. Primarily because it causes all kinds of freezing/crashes when having an IPMI board. I believe it has performed ok in machines where we don't have an IPMI card. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
On Thu, 29 Jun 2006, Francisco Reyes wrote: Michel Talon writes: Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. What volume are we talking about? My own problems and other reports I see are all under heavy load. the one thing that sticks out to me about this report is that they upgraded teh NFS server to FC5 ... what was the server running before? if FreeBSD, could the problem be an interaction problem between the NFS server and client, vs just the client side? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
User Freebsd wrote: On Thu, 29 Jun 2006, Peter Jeremy wrote: On Thu, 2006-Jun-29 17:30:07 +1000, Michael Vince wrote: For me its IP alias additions take 1 or maybe 2secs, but it is noticeable, but really isn't an issue for me. But it obviously is for Atanas, who has 100's of aliases. In my case, it isn't 100's, but the problem is noticeable ... I have my start up scripts, right now, do the ifconfig, sleep for 45 seconds, and then start up the jail ... and even then, apache doesn't *always* start up, since sometimes that isn't long enough for the network to come back up for DNS to be reachable :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) The thing that have to ask is if Atanas has 100's why can't he just boot Freebsd have have them all prebound to the interface at startup, why would you need to add and remove them constantly by the hundreds during normal server uptime? I do restart my jails now and then, but because the IPs are already bound to the interface I don't have any pause issues. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
User Freebsd writes: the one thing that sticks out to me about this report is that they upgraded teh NFS server to FC5 I wonder if the FreeBSD 6.X client would freeze with a non FreeBSD NFS server. Would be interesting to have that info for comparison. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quota and snapshots in 6.1-RELEASE
On Thu, Jun 29, 2006 at 10:48:06PM -0400, Mike Jakubik wrote: Konstantin Belousov wrote: On Tue, Jun 06, 2006 at 01:49:04PM -0400, Mike Jakubik wrote: Scott Long wrote: Dmitriy Kirhlarov wrote: Hi! On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want If you use snapshots with your quotas, update to 6.1-STABLE. If you Sorry, guys. You are mean RELENG_6_1 or RELENG_6? WBR RELENG_6. However, the changes will likely make their way into RELENG_6_1 in a few weeks as part of an errata update. Scott I have just done tests on 6.1-R and RELENG_6 as of yesterday evening. Unfortunately both still lock up hard, no crash, just a frozen system. I cant enter the KDB (ddb) via the console, but its unusable, as it wont let me type in anything. There must be some other change in -CURRENT that fixes this, as -CURRENT did not freeze during my previous tests. Just to confirm, here is the ID of ufs_quota.c on my RELENG_6 system: /usr/src/sys/ufs/ufs/ufs_quota.c: $FreeBSD: src/sys/ufs/ufs/ufs_quota.c,v 1.74.2.4 2006/05/14 00:23:27 tegge Exp $ The hangs are mostly related to snapshots. It would be better to update to the latest RELENG_6. Hangs on RELENG_6_1 is not so much interesting. For hanged RELENG_6 system, please do what described below and post the log of the ddb session. I'm not sure whether kbdmux was MFCed into RELENG_6 (AFAIR, yes). If you have it in your kernel, add the line hint.kbdmux.0.disabled=1 into the /boot/device.hints to make ddb usable. After that, on the hang, enter ddb, and do ps and tr pid for all suspected processes. Better yet, add the following options to your kernel: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC and, after hang, do in ddb show allpcpu show alllocks show lockedvnods ps For each process mentioned in show output, do where pid (for threaded processes, do thread thread-id; where). BTW, it would be great to add this instructions to the FAQ. Well, i finally got around to setting up a serial console on this box, the following is the output from the debugger after the system stopped responding. Let me know if you need any more/different information, i also made the kernel changes you recommended. FreeBSD 6.1-STABLE #1: Thu Jun 10 00:22:29 EDT 2006 --- KDB: enter: Line break on console [thread pid 12 tid 14 ] Stopped at kdb_enter+0x30: leave db ps pid proc uid ppid pgrp flag stat wmesgwchan cmd 552 c36228302 550 549 0004000 [SLPQ flswai 0xc0707c24][SLP] rm 550 c35708302 549 549 0004000 [SLPQ wait 0xc3570830][SLP] sh 549 c342ec482 548 549 0004000 [SLPQ wait 0xc342ec48][SLP] sh 548 c36226240 422 422 000 [SLPQ piperd 0xc36027f8][SLP] cron 547 c361f8300 524 547 0004002 [SLPQ ufs 0xc3777c94][SLP] ls 546 c36bc4180 544 544 0004002 [SLPQ wdrain 0xc0707be4][SLP] fsck_4.2bsd 544 c36bcc480 511 544 0004002 [SLPQ wait 0xc36bcc48][SLP] fsck 524 c35e020c0 522 524 0004002 [SLPQ wait 0xc35e020c][SLP] bash 522 c3570c480 406 522 0004100 [SLPQ flswai 0xc0707c24][SLP] sshd 515 c36bc20c0 0 0 204 [SLPQ wdrain 0xc0707be4][SLP] md0 511 c36bb6240 500 511 0004002 [SLPQ wait 0xc36bb624][SLP] bash 509 c3570418 65 1 509 100 [SLPQ select 0xc0707644][SLP] dhclient 500 c361fa3c0 406 500 0004100 [SLPQ flswai 0xc0707c24][SLP] sshd 480 c342ea3c0 1 256 000 [SLPQ select 0xc0707644][SLP] dhclient 465 c361f6240 1 465 0004002 [SLPQ ttyin 0xc342b010][SLP] getty 464 c35e0c480 1 464 0004002 [SLPQ ttyin 0xc3429410][SLP] getty 463 c356fa3c0 1 463 0004002 [SLPQ ttyin 0xc3429810][SLP] getty 462 c356f4180 1 462 0004002 [SLPQ ttyin 0xc343f010][SLP] getty 422 c342e6240 1 422 000 [SLPQ nanslp 0xc06ba32c][SLP] cron 416 c356f000 25 1 416 100 [SLPQ pause 0xc356f034][SLP] sendmail 412 c356f6240 1 412 100 [SLPQ select 0xc0707644][SLP] sendmail 406 c35e0 1 406 100 [SLPQ select 0xc0707644][SLP] sshd 290 c361f20c0 1 290 000 [SLPQ flswai 0xc0707c24][SLP] syslogd 256 c36224180 1 256 000 [SLPQ select 0xc0707644][SLP] devd 145 c356f8300 1 145 000 [SLPQ pause 0xc356f864][SLP] adjkerntz 38 c3378c480 0 0 204 [SLPQ - 0xd56f5cf8][SLP] schedcpu 37 c342d0000 0 0 204 [SLPQ sdflush 0xc070a3b4][SLP] softdepflush 36 c342d20c0 0 0 204 [SLPQ vlruwt 0xc342d20c][SLP] vnlru 35 c342d4180 0 0 204 [SLPQ ufs 0xc363c46c][SLP] syncer 34 c342d624
Re: Force ugen device for printer?
Anish Mistry wrote: So if you don't kldload ulpt, but kldload umass you don't get some ugen endpoints and a umass device? Right. If I kldunload only ulpt, I get umass devices but not ugen. :-( Would you provide a the output of usbdevs -vvv. addr 1: full speed, self powered, config 1, OHCI root hub(0x), nVidia(0x), rev 1.00 port 1 powered port 2 powered port 3 addr 2: low speed, power 100 mA, config 1, PS/2+USB Mouse(0x0210), vendor 0x1267(0x1267), rev 22.70 port 4 addr 3: low speed, power 100 mA, config 1, USB Gaming Keyboard Pro(0x8000), Chicony(0x06a3), rev 1.30 port 5 powered port 6 addr 4: full speed, power 500 mA, config 1, USB Audio(0xc000), vendor 0x06f8(0x06f8), rev 1.00 port 7 addr 5: full speed, self powered, config 1, PSC 1600 series(0x4811), HP(0x03f0), rev 1.00 port 8 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), nVidia(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, ATAPI-6 Bridge Controller(0x2507), Prolific Technology Inc.(0x067b), rev 0.01 port 6 powered port 7 powered port 8 powered signature.asc Description: OpenPGP digital signature
Re: NFS Locking Issue
On Fri, Jun 30, 2006 at 01:03:09AM +0200, Michel Talon wrote: I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. It is first time since years i have no problem. It certainly did not work with FreeBSD-5 and i still have a machine with FreeBSD-6.0 which does not work properly (frequently loses the NFS mount, but it gets remounted some times later by amd). Anyways i have exactly 0 problem with the 6.1 machine. I could extend that to say that everything works very well on that machine, nothing is slow, including disk access. This has not always been the case. Stability wise, i have not seen any panic, hang or whatever since i have compiled a kernel adapted to my hardware. I got a panic with the generic kernel soon after installation, but now machine is totally stable. I only started to see the lockd problems when upgrading the server side to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x and 7-current and the lockd problem only showed up when upgrading the server from 5.x to 6.x. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quota and snapshots in 6.1-RELEASE
On Fri, Jun 30, 2006 at 07:05:36AM +0300, Kostik Belousov wrote: OK, please, provide also your fstab, information on md config and dmesg, and kernel config. Also, it would be good to see the output of alltrace in ddb. It seems that your kernel does not contain quota option ? Oh, I see, you _do_ have quotas. Please, show the quota configuration. Meanwhile, output of alltrace is very much needed. pgpuB1VgO9sRT.pgp Description: PGP signature
Re: em device hangs on ifconfig alias ...
On Fri, 30 Jun 2006, Michael Vince wrote: The thing that have to ask is if Atanas has 100's why can't he just boot Freebsd have have them all prebound to the interface at startup, why would you need to add and remove them constantly by the hundreds during normal server uptime? I do restart my jails now and then, but because the IPs are already bound to the interface I don't have any pause issues. In my case, I move jails around between machines for load balancing reasons ... so, a physical server may be up for, hell, in one case, 211 days, but a vServer may only have been on it a few days ... The other funny thing about the current em driver is that if you move an IP to it from a different server, the appropriate ARP packets aren't sent out to redirect the IP traffic .. recently, someone pointed me to arping, which has solved my problem *external* to the driver ... I have a third machine that uses an em driver, but its an older 4.x kernel, and it operates perfectly ... no timeouts/hangs and sends out the appropriate ARP packet ... all three servers are connected to the same Cisco switch, with all ports configured identically, so it isn't a switch issue, as someone else intimated ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
