From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 13:08:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8AC016A41C for ; Wed, 8 Jun 2005 13:08:15 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxsf06.cluster1.charter.net (mxsf06.cluster1.charter.net [209.225.28.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60ABB43D49 for ; Wed, 8 Jun 2005 13:08:15 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxip17a.cluster1.charter.net (mxip17a.cluster1.charter.net [209.225.28.147]) by mxsf06.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j58D8CNu004469 for ; Wed, 8 Jun 2005 09:08:12 -0400 Received: from pc-24-151-49-073.newt1.ct.charter.com (HELO bedroom) (24.151.49.73) by mxip17a.cluster1.charter.net with ESMTP; 08 Jun 2005 09:08:12 -0400 X-IronPort-AV: i="3.93,182,1115006400"; d="scan'208"; a="1147340088:sNHT24472330" From: "Matt Smith" To: Date: Wed, 8 Jun 2005 09:08:11 -0400 Message-ID: <000401c56c2b$1fd9ad00$0201a8c0@bedroom> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20050608120040.C1E8316A442@hub.freebsd.org> Subject: RE: 5.4 RC2 freezing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 13:08:15 -0000 pflog0: promiscuous mode enabled Do you want to be running this way? Matt -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of freebsd-stable-request@freebsd.org Sent: Wednesday, June 08, 2005 8:01 AM To: freebsd-stable@freebsd.org Subject: freebsd-stable Digest, Vol 113, Issue 5 Send freebsd-stable mailing list submissions to freebsd-stable@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-stable or, via email, send a message with subject or body 'help' to freebsd-stable-request@freebsd.org You can reach the person managing the list at freebsd-stable-owner@freebsd.org When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-stable digest..." Today's Topics: 1. Re: 5.4-RC2 freezing - ATA related? (Peter Jeremy) 2. Re: FreeBSD 5.4: Is it generally unstable? (Matthias Buelow) 3. Re: PANIC in RELENG_5 (Palle Girgensohn) 4. Re: FreeBSD 5.4: Is it generally unstable? (Igor Robul) ---------------------------------------------------------------------- Message: 1 Date: Wed, 8 Jun 2005 20:12:15 +1000 From: Peter Jeremy Subject: Re: 5.4-RC2 freezing - ATA related? To: Steve Watt Cc: stable@freebsd.org Message-ID: <20050608101215.GH39114@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii On Tue, 2005-May-31 16:47:19 -0700, Steve Watt wrote: >>> The vnode locks are held by processes: >>> PID name waiting on >>> 487 perl [ufs c3c1c1b4] >>> 57 syncer [snaplk c535f500] (holds 2 locks) >>> 476 perl [ufs c87e4f1c] >>> 489 perl [snaplk c535f500] (holds 2 locks) >>> 3337 mksnap_ffs [getblk d77656f4] ... >This is a filesystem lock problem, not an ATA driver problem. I analyzed >it, and posted the results to -hackers last week, with the subject "snapshots >and innds". I saw your previous post but the symptoms don't look the same to me. Your deadlock has mksnap_ffs blocked on ufs whilst Elliot's problem has mksnap_ffs blocked on getblk. getblk is a lower level call (physical I/O) and I don't see how a FS problem could cause problems for getblk calls. -- Peter Jeremy ------------------------------ Message: 2 Date: Wed, 08 Jun 2005 12:26:22 +0200 From: Matthias Buelow Subject: Re: FreeBSD 5.4: Is it generally unstable? To: David Hogan Cc: freebsd-stable@freebsd.org Message-ID: <42A6C7CE.9000002@incubus.de> Content-Type: text/plain; charset=ISO-8859-1 David Hogan wrote: > In my time with the Trustix lists, I don't think I came across a serious > kernel issue that wasn't caused by either a lack of a preinstalled driver or > a bad stick of ram. Would you say that this holds true for FreeBSD? I If that Trustix works for you now well, you'd be careless to migrate now. If it works, why change it? My experience with the 5.x tree so far is that it's ok for a SOHO or private environment but I wouldn't trust it if my money (or job) depended on it. Maybe in a year, or two but not now. mkb. ------------------------------ Message: 3 Date: Wed, 08 Jun 2005 13:01:08 +0200 From: Palle Girgensohn Subject: Re: PANIC in RELENG_5 To: Kay Abendroth Cc: freebsd-stable@freebsd.org Message-ID: Content-Type: text/plain; charset=us-ascii; format=flowed Mine, and most others with this problem, have Dell 2850. Same ethernet controller, though, `em'...? /Palle --On onsdag, juni 08, 2005 11.27.01 +0200 Kay Abendroth wrote: > Output of 'dmesg': > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.4-STABLE #0: Fri Jun 3 08:49:22 UTC 2005 > root@susi.redhill.net:/usr/obj/usr/src/sys/SUSI > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) XP 1700+ (1470.01-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 > Features=0x383fbff MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> > AMD Features=0xc0400000 > real memory = 1610547200 (1535 MB) > avail memory = 1568534528 (1495 MB) > mptable_probe: MP Config Table has bad signature: ^\^A > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > cpu0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem > 0xe0000000-0xe3ffffff at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci0: at device 8.0 (no driver attached) > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd000-0xd07f mem > 0xe7060000-0xe706007f irq 11 at device 10.0 on pci0 > miibus0: on xl0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:04:75:73:e3:ad > pci0: at device 11.0 (no driver attached) > em0: port > 0xd800-0xd83f mem 0xe7000000-0xe703ffff,0xe7040000-0xe705ffff irq 11 at > device 12.0 on pci0 > em0: Ethernet address: 00:04:23:b1:d5:92 > em0: Speed:N/A Duplex:N/A > isab0: at device 17.0 on pci0 > isa0: on isab0 > atapci0: port > 0xe800-0xe80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > acpi_tz0: on acpi0 > speaker0: port 0x61 on acpi0 > fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on > acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > pmtimer0 on isa0 > orm0: at iomem 0xcc000-0xcc7ff,0xc0000-0xc87ff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "TSC" frequency 1470010559 Hz quality 800 > Timecounters tick every 1.000 msec > ad0: 114473MB [232581/16/63] at ata0-master UDMA100 > ad1: 39083MB [79408/16/63] at ata0-slave UDMA100 > Mounting root from ufs:/dev/ad1s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > WARNING: /usr was not properly dismounted > WARNING: /var was not properly dismounted > /var: mount pending error: blocks 20 files 1 > WARNING: /opt was not properly dismounted > WARNING: /zbackup was not properly dismounted > em0: Link is up 1000 Mbps Full Duplex > em0: Link is up 1000 Mbps Full Duplex > pflog0: promiscuous mode enabled > pid 64090 (squid), uid 0: exited on signal 6 (core dumped) > pid 75212 (squid), uid 0: exited on signal 6 (core dumped) > > > Palle Girgensohn wrote: >> >> --On tisdag, juni 07, 2005 18.03.55 +0200 Kay Abendroth >> wrote: >> >>> >>> Hello, >>> >>> today I had another panic on my FreeBSD-Box. The last one occured 4 days >>> ago. >>> >>> Please reply if sth. is missing. >>> >>> Kind regards, >>> Kay >> >> >> Hi! >> >> What brand is your machine? Can you supply a dmesg? >> >> /Palle >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > ------------------------------ Message: 4 Date: Wed, 08 Jun 2005 15:26:11 +0400 From: Igor Robul Subject: Re: FreeBSD 5.4: Is it generally unstable? To: freebsd-stable@freebsd.org Message-ID: <42A6D5D3.10305@speechpro.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Matthias Buelow wrote: > > >If that Trustix works for you now well, you'd be careless to migrate >now. If it works, why change it? >My experience with the 5.x tree so far is that it's ok for a SOHO or >private environment but I wouldn't trust it if my money (or job) >depended on it. Maybe in a year, or two but not now. > I use 5-STABLE as our Samba/Courier-IMAP/exim/bugzilla/CVS server in production environment. One of problems I have is LanSafe III software for Linux, which worked fine on FreeBSD 4.X, but does not work as expected on FreeBSD 5.X. But it also does not work on Mandrake 10.1. Also we have FreeBSD 5-STABLE internal router, and FreeBSD 5-STABLE gateway/IPSec + small hosting for some of our sites (in jail (8)). ------------------------------ _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" End of freebsd-stable Digest, Vol 113, Issue 5 **********************************************