From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 07:26:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CCD5106566C for ; Sun, 1 Nov 2009 07:26:24 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 19DBB8FC20 for ; Sun, 1 Nov 2009 07:26:23 +0000 (UTC) Received: from current.Sisis.de (ppp-88-217-48-99.dynamic.mnet-online.de [88.217.48.99]) by dd12710.kasserver.com (Postfix) with ESMTP id 758F9184F89E6; Sun, 1 Nov 2009 08:26:22 +0100 (CET) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id nA17QTam002396; Sun, 1 Nov 2009 08:26:29 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sun, 1 Nov 2009 08:26:29 +0100 From: Matthias Apitz To: kde-freebsd@kde.org Message-ID: <20091101072629.GA2334@current.Sisis.de> References: <20091030151754.GA5849@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091030151754.GA5849@current.Sisis.de> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: freebsd-current@freebsd.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 07:26:24 -0000 El da Friday, October 30, 2009 a las 04:17:55PM +0100, Matthias Apitz escribi: > > Hello, > > I have in a VM a 9-CURRENT and compiled/installed from the ports first > x11/kde3 (which worked fine) and now in addition x11/kde4 (which comes > up also fine). > > But, > > A start of KDE3 from ~/.xinitrc via exec /usr/local/bin/startkde > complains in the following code: > > # We set LD_BIND_NOW to increase the efficiency of kdeinit. > # kdeinit unsets this variable before loading applications. > LD_BIND_NOW=true start_kdeinit_wrapper --new-startup +kcminit_startup > if test $? -ne 0; then > # Startup error > echo 'startkde: Could not start kdeinit. Check your installation.' 1>&2 > xmessage -geometry 500x100 "Could not start kdeinit. Check your installation." > fi > > i.e. it brings up this xmessage box and in the log files I can see that > 'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up > fine. This is, as I said, after compiling the port x11/kde4. The file > /usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 > and neither the shared libs it is depending: > > $ ldd /usr/local/bin/start_kdeinit_wrapper > /usr/local/bin/start_kdeinit_wrapper: > libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x2808e000) > libc.so.7 => /lib/libc.so.7 (0x280c2000) > > What could cause this behaviour? Thanks +Cc: freebsd-current I digged into that deeper with the sources... start_kdeinit_wrapper -> start_kdeinit -> kdeinit is (on non-Linux) just an execvp(2) chain of the above three programs; on FreeBSD it would not even be necessary because non of them runs with setuid on execution. As mentioned, the three programs /usr/local/bin/start_kdeinit_wrapper /usr/local/bin/start_kdeinit /usr/local/bin/kdeinit have been compiled on -CURRENT r197801 and have been untouched and working since October, 16. On October 30, I compiled in addition the port x11/kde4, which does not touch the above programs and also not the shared libs used by them; after the installation of x11/kde4 the start_kdeinit_wrapper now aborts: $ /usr/local/bin/start_kdeinit_wrapper Abort trap: 6 it does not abort when you set # sysctl security.bsd.map_at_zero=1 security.bsd.map_at_zero: 0 -> 1 I think that security.bsd.map_at_zero was already 0 before compiling x11/kde4, i.e. no part of KDE4 changed this sysctl value; so it remains open, what caused this effect, but at least it is working again; Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 09:06:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6351E106566C for ; Sun, 1 Nov 2009 09:06:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swipnet.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id EAE0D8FC0A for ; Sun, 1 Nov 2009 09:06:53 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=qUQ4jkHYiCcA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=mK_AVkanAAAA:8 a=rR8CIsAL7J0ri7yMbN8A:9 a=hXWa4S34qlpy5hq9Khg2yfpqBmoA:4 a=9xyTavCNlvEA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1157271038; Sun, 01 Nov 2009 10:06:52 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 1 Nov 2009 10:08:05 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <31d643300910311245r593326e1me8574bdff5198b51@mail.gmail.com> <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> In-Reply-To: <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911011008.06891.hselasky@c2i.net> Cc: Matthias Rampke Subject: Re: Host OS (OS X 10.6.1) panic when booting 8.0-RC2 in VirtualBox 3.0.10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 09:06:54 -0000 On Saturday 31 October 2009 21:06:36 Matthias Rampke wrote: > On Sat, Oct 31, 2009 at 8:45 PM, Matthias Rampke > > wrote: > > Hello, > > > > I have been experiencing reproducible kernel panics in Mac OS X 10.6.1 > > when booting 8.0-RC1 and -RC2 (amd64) in a VirtualBox VM. > > > > I had a (mostly pristine) 7.2-RELEASE running in this VM and tried to > > upgrade to 8.0-RC2 with freebsd-update. > > This does not happen in a new, freshly installed VM. Now it hangs at > usbus initialization, but I suppose that's a different story (the > pains of using USB with VirtualBox, they never end). > > Any ideas what went wrong with the update? And if you turn off USB support in virtual box? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 09:41:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FE14106566B for ; Sun, 1 Nov 2009 09:41:50 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id DA8F38FC1A for ; Sun, 1 Nov 2009 09:41:49 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=qUQ4jkHYiCcA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=mK_AVkanAAAA:8 a=Pj85_RLrrjgBc_PsHEEA:9 a=RX1E5oPAnyTqDECy4lwd4W_uj1YA:4 a=9xyTavCNlvEA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1317133250; Sun, 01 Nov 2009 10:41:48 +0100 To: freebsd-current@freebsd.org Content-Disposition: inline From: Hans Petter Selasky X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpO< =?iso-8859-1?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t; @ =?iso-8859-1?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",; u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv Date: Sun, 1 Nov 2009 10:43:00 +0100 MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911011043.02614.hselasky@c2i.net> Cc: Matthias Rampke Subject: Re: Host OS (OS X 10.6.1) panic when booting 8.0-RC2 in VirtualBox 3.0.10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 09:41:50 -0000 On Saturday 31 October 2009 21:06:36 Matthias Rampke wrote: > On Sat, Oct 31, 2009 at 8:45 PM, Matthias Rampke > > wrote: > > Hello, > > > > I have been experiencing reproducible kernel panics in Mac OS X 10.6.1 > > when booting 8.0-RC1 and -RC2 (amd64) in a VirtualBox VM. > > > > I had a (mostly pristine) 7.2-RELEASE running in this VM and tried to > > upgrade to 8.0-RC2 with freebsd-update. > > This does not happen in a new, freshly installed VM. Now it hangs at > usbus initialization, but I suppose that's a different story (the > pains of using USB with VirtualBox, they never end). > > Any ideas what went wrong with the update? Hi, I just booted FreeBSD 8.0 RC-2 the live ISO in Virtual box (3.0.8) on a MAC and I don't see any problems. Are you sure that the /boot/kernel/ is free from stale modules from FreeBSD 7.x ? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 09:58:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8D25106568B for ; Sun, 1 Nov 2009 09:58:26 +0000 (UTC) (envelope-from christof.schulze@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id ED0D58FC19 for ; Sun, 1 Nov 2009 09:58:25 +0000 (UTC) Received: (qmail invoked by alias); 01 Nov 2009 09:58:24 -0000 Received: from g224222134.adsl.alicedsl.de (EHLO klausdieter0815.dyndns.org) [92.224.222.134] by mail.gmx.com (mp-eu005) with SMTP; 01 Nov 2009 10:58:24 +0100 X-Authenticated: #56306756 X-Provags-ID: V01U2FsdGVkX1/3oE94nwb3vHR2SRUfx6yurSMTcMsEpKatf0z4oQ Tb/VqBg1Qg7WTl Received: by myhost.mydomain.de (Postfix, from userid 1001) id C9CC693; Sun, 25 Oct 2009 19:10:25 +0100 (CET) From: Christof Schulze To: freebsd-current@freebsd.org Date: Sun, 25 Oct 2009 19:10:20 +0100 User-Agent: KMail/1.12.0 (FreeBSD/7.2-STABLE; KDE/4.3.0; amd64; ; ) References: <200910111158.14692.hselasky@freebsd.org> In-Reply-To: <200910111158.14692.hselasky@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2056464.Xqo0nKU5r0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200910251910.25269.christof.schulze@gmx.com> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.72 Subject: Re: [patch] USB video support in KDE4 + sane + more under FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 09:58:26 -0000 --nextPart2056464.Xqo0nKU5r0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Am Sonntag 11 Oktober 2009 11:58:11 schrieb Hans Petter Selasky: > Hi, > > [USB webcam patches] Thank you Hans, it is good to see that there is some activity with webcams= =20 and FreeBSD as I did not get mine to run yet. I will give it a try as soon as possible Christof =2D-=20 () ascii ribbon campaign - against html e-mail=20 /\ www.asciiribbon.org - against proprietary attachments --nextPart2056464.Xqo0nKU5r0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEABECAAYFAkrklJEACgkQpZfyPAmdZJmP+ACgyUVvd2nkE8UNf4RzWqSgaxJd V7sAn0Ki5yISMa0kewbrjgfFTRIvnV5U =MiIY -----END PGP SIGNATURE----- --nextPart2056464.Xqo0nKU5r0-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 10:32:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09A181065670 for ; Sun, 1 Nov 2009 10:32:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D92EF8FC15 for ; Sun, 1 Nov 2009 10:32:24 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 926F646B06; Sun, 1 Nov 2009 05:32:24 -0500 (EST) Date: Sun, 1 Nov 2009 10:32:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Matthias Apitz In-Reply-To: <20091101072629.GA2334@current.Sisis.de> Message-ID: References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 10:32:25 -0000 On Sun, 1 Nov 2009, Matthias Apitz wrote: >> i.e. it brings up this xmessage box and in the log files I can see that >> 'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up fine. >> This is, as I said, after compiling the port x11/kde4. The file >> /usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 >> and neither the shared libs it is depending: >> >> $ ldd /usr/local/bin/start_kdeinit_wrapper >> /usr/local/bin/start_kdeinit_wrapper: >> libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x2808e000) >> libc.so.7 => /lib/libc.so.7 (0x280c2000) Could you show us readelf -l /usr/local/bin/start_kdeinit_wrapper > it does not abort when you set > > # sysctl security.bsd.map_at_zero=1 > security.bsd.map_at_zero: 0 -> 1 > > I think that security.bsd.map_at_zero was already 0 before compiling > x11/kde4, i.e. no part of KDE4 changed this sysctl value; so it remains > open, what caused this effect, but at least it is working again; Could you confirm you are running with a userspace/kernel of at least r198203 (the date of the last PIE-related fix following a move to disallowing NULL mappings). Robert From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 10:39:28 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D50831065670 for ; Sun, 1 Nov 2009 10:39:28 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3598FC08 for ; Sun, 1 Nov 2009 10:39:28 +0000 (UTC) Received: from current.Sisis.de (ppp-88-217-48-99.dynamic.mnet-online.de [88.217.48.99]) by dd12710.kasserver.com (Postfix) with ESMTP id E744D184F85C3; Sun, 1 Nov 2009 11:39:26 +0100 (CET) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id nA1AdYeu003023; Sun, 1 Nov 2009 11:39:34 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sun, 1 Nov 2009 11:39:34 +0100 From: Matthias Apitz To: Robert Watson Message-ID: <20091101103934.GA3004@current.Sisis.de> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 10:39:29 -0000 El da Sunday, November 01, 2009 a las 10:32:24AM +0000, Robert Watson escribi: > > On Sun, 1 Nov 2009, Matthias Apitz wrote: > > >>i.e. it brings up this xmessage box and in the log files I can see that > >>'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up fine. > >>This is, as I said, after compiling the port x11/kde4. The file > >>/usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 > >>and neither the shared libs it is depending: > >> > >>$ ldd /usr/local/bin/start_kdeinit_wrapper > >>/usr/local/bin/start_kdeinit_wrapper: > >> libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x2808e000) > >> libc.so.7 => /lib/libc.so.7 (0x280c2000) > > Could you show us readelf -l /usr/local/bin/start_kdeinit_wrapper Here we go: $ readelf -l /usr/local/bin/start_kdeinit_wrapper Elf file type is EXEC (Executable file) Entry point 0x8048480 There are 6 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x000034 0x08048034 0x08048034 0x000c0 0x000c0 R E 0x4 INTERP 0x0000f4 0x080480f4 0x080480f4 0x00015 0x00015 R 0x1 [Requesting program interpreter: /libexec/ld-elf.so.1] LOAD 0x000000 0x08048000 0x08048000 0x006a8 0x006a8 R E 0x1000 LOAD 0x0006a8 0x080496a8 0x080496a8 0x00104 0x0010c RW 0x1000 DYNAMIC 0x0006b8 0x080496b8 0x080496b8 0x000c0 0x000c0 RW 0x4 NOTE 0x00010c 0x0804810c 0x0804810c 0x00018 0x00018 R 0x4 Section to Segment mapping: Segment Sections... 00 01 .interp 02 .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_ r .rel.plt .init .plt .text .fini .rodata 03 .data .eh_frame .dynamic .ctors .dtors .jcr .got .bss 04 .dynamic 05 .note.ABI-tag > >it does not abort when you set > > > ># sysctl security.bsd.map_at_zero=1 > >security.bsd.map_at_zero: 0 -> 1 > > > >I think that security.bsd.map_at_zero was already 0 before compiling > >x11/kde4, i.e. no part of KDE4 changed this sysctl value; so it remains > >open, what caused this effect, but at least it is working again; > > Could you confirm you are running with a userspace/kernel of at least > r198203 (the date of the last PIE-related fix following a move to > disallowing NULL mappings). NAK, userland and kernel is: $ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Mon Oct 12 13:33:32 CEST 2009 guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 10:45:42 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B43E1065692 for ; Sun, 1 Nov 2009 10:45:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E24E78FC1E for ; Sun, 1 Nov 2009 10:45:41 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 6399D46B06; Sun, 1 Nov 2009 05:45:41 -0500 (EST) Date: Sun, 1 Nov 2009 10:45:41 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Matthias Apitz In-Reply-To: <20091101103934.GA3004@current.Sisis.de> Message-ID: References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 10:45:42 -0000 On Sun, 1 Nov 2009, Matthias Apitz wrote: >> Could you confirm you are running with a userspace/kernel of at least >> r198203 (the date of the last PIE-related fix following a move to >> disallowing NULL mappings). > > NAK, userland and kernel is: > > $ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 > r197801: Mon Oct 12 13:33:32 CEST 2009 > guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 Sounds like an upgrade should fix this -- if not, please let us know ASAP as it might be an issue for 8.0 as well. Robert From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 11:44:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 828231065670 for ; Sun, 1 Nov 2009 11:44:35 +0000 (UTC) (envelope-from matthias.rampke@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id DF1F18FC08 for ; Sun, 1 Nov 2009 11:44:34 +0000 (UTC) Received: by bwz5 with SMTP id 5so5325733bwz.3 for ; Sun, 01 Nov 2009 03:44:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=MSEIrc868ReuvY9t96U13g1uD5DYmjimXHRjmutAGz4=; b=Ivx+JPXV+AsDKEofhdBI7iCsku6CTxgUcmQhqoO4u7gNS5rEz2cAB1StZjaHvzGRGA CnjYFYVmVaJ5Qu5Gn4Mq5Vet5gAi3bgRilMSkDlvZJV0puG+7725ZrKXUosfkPCJe06g AC+4DTUZuMJxvbmDkJBd9DMp5JlpjrvrwkQ60= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Yw9XonP3jXa8WQ5tEZ1nFJY54EYbjecgsW5QtVLQH+fl4X7KAek5nirscFBT7sg93W NL2VM5LcXZOLF5AyO9SvqByV2UQQHQ0img+kxYocFtP37yZG92xSAyr7vynUqYfiAq9L zkhUtFhrQABgTZFqAgXPguDzlTxcXKMPujDJg= MIME-Version: 1.0 Received: by 10.204.150.69 with SMTP id x5mr2921583bkv.197.1257075872095; Sun, 01 Nov 2009 03:44:32 -0800 (PST) In-Reply-To: References: <31d643300910311245r593326e1me8574bdff5198b51@mail.gmail.com> <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> From: Matthias Rampke Date: Sun, 1 Nov 2009 12:44:12 +0100 Message-ID: <31d643300911010344u680c1c4fj87d7654b12380af1@mail.gmail.com> To: Robert Watson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Host OS (OS X 10.6.1) panic when booting 8.0-RC2 in VirtualBox 3.0.10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 11:44:35 -0000 On Sat, Oct 31, 2009 at 11:03 PM, Robert Watson wrote= : > > I'd suggest > making a backup copy of the bad VM so that you can trigger it on demand > later. done. > >> This does not happen in a new, freshly installed VM. Now it hangs at usb= us >> initialization, but I suppose that's a different story (the pains of usi= ng >> USB with VirtualBox, they never end). > > This, on the other hand, could be our bug; there's a new USB stack in 8.0= . > =A0I suggest creating a new thread for that issue with a usb-related subj= ect > line to make sure the right folk see it. > > Robert > No need, the problem resolved itself by de- and reactivating USB in VBox (thanks HPS). This is definitely not a FreeBSD-related problem, I have been having problems accessing a specific USB drive from within VMs, both FreeBSD and OpenSolaris, and that one appears to have been the problem here as well. So, the current status is: The cleanly installed 8.0-RC2 works, the updated one not. So this is either my bad or the freebsd-update did something wrong. I'll try to find out what and keep you posted. thx for all the suggestions, M. --=20 Matthias Rampke +49 179 - 166 09 18 http://www.matthias-rampke.de/ From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 12:28:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A239E1065670 for ; Sun, 1 Nov 2009 12:28:35 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 79F048FC1B for ; Sun, 1 Nov 2009 12:28:35 +0000 (UTC) Received: from [192.168.2.101] (host217-43-176-60.range217-43.btcentralplus.com [217.43.176.60]) by cyrus.watson.org (Postfix) with ESMTPSA id A78E646B39; Sun, 1 Nov 2009 07:28:34 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: "Robert N. M. Watson" In-Reply-To: <31d643300911010344u680c1c4fj87d7654b12380af1@mail.gmail.com> Date: Sun, 1 Nov 2009 12:28:32 +0000 Content-Transfer-Encoding: 7bit Message-Id: <3B6CC16F-DC7C-4D95-AC68-0B14C3741A30@freebsd.org> References: <31d643300910311245r593326e1me8574bdff5198b51@mail.gmail.com> <31d643300910311306m6caa73cfi8930465e43773ff4@mail.gmail.com> <31d643300911010344u680c1c4fj87d7654b12380af1@mail.gmail.com> To: Matthias Rampke X-Mailer: Apple Mail (2.1076) Cc: freebsd-current@freebsd.org Subject: Re: Host OS (OS X 10.6.1) panic when booting 8.0-RC2 in VirtualBox 3.0.10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 12:28:35 -0000 On 1 Nov 2009, at 11:44, Matthias Rampke wrote: > So, the current status is: The cleanly installed 8.0-RC2 works, the > updated one not. So this is either my bad or the freebsd-update did > something wrong. I'll try to find out what and keep you posted. If they're supposed to be the same binary kernel (check the version string/etc on early boot), then it might be worth simply doing md5 sums and seeing if they are the same (likewise loader binaries and kernel modules). Is there any chance you have non-base system kernel modules installed in /boot/modules or the like? Robert From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 13:08:23 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDC471065670; Sun, 1 Nov 2009 13:08:23 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 76FAB8FC2C; Sun, 1 Nov 2009 13:08:23 +0000 (UTC) Received: from current.Sisis.de (ppp-88-217-48-99.dynamic.mnet-online.de [88.217.48.99]) by dd12710.kasserver.com (Postfix) with ESMTP id EBD2A184F82FB; Sun, 1 Nov 2009 14:08:21 +0100 (CET) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id nA1D8LR5003670; Sun, 1 Nov 2009 14:08:21 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sun, 1 Nov 2009 14:08:20 +0100 From: Matthias Apitz To: Robert Watson Message-ID: <20091101130820.GA3658@current.Sisis.de> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 13:08:23 -0000 El da Sunday, November 01, 2009 a las 10:45:41AM +0000, Robert Watson escribi: > > On Sun, 1 Nov 2009, Matthias Apitz wrote: > > >>Could you confirm you are running with a userspace/kernel of at least > >>r198203 (the date of the last PIE-related fix following a move to > >>disallowing NULL mappings). > > > >NAK, userland and kernel is: > > > >$ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 > >r197801: Mon Oct 12 13:33:32 CEST 2009 > >guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 > > Sounds like an upgrade should fix this -- if not, please let us know ASAP > as it might be an issue for 8.0 as well. Robert, do you have an idea why this (with the same kernel/userland) only shows up after installing the port x11/kde4? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 13:13:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CE67106568D; Sun, 1 Nov 2009 13:13:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id E789B8FC24; Sun, 1 Nov 2009 13:13:38 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA1DDYAj081248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Nov 2009 15:13:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA1DDY7u003147; Sun, 1 Nov 2009 15:13:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA1DDY92003146; Sun, 1 Nov 2009 15:13:34 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 1 Nov 2009 15:13:34 +0200 From: Kostik Belousov To: Matthias Apitz Message-ID: <20091101131334.GO2147@deviant.kiev.zoral.com.ua> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> <20091101130820.GA3658@current.Sisis.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s9kDAZ2EyO0AcRYa" Content-Disposition: inline In-Reply-To: <20091101130820.GA3658@current.Sisis.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org, Robert Watson Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 13:13:39 -0000 --s9kDAZ2EyO0AcRYa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 01, 2009 at 02:08:20PM +0100, Matthias Apitz wrote: > El d?a Sunday, November 01, 2009 a las 10:45:41AM +0000, Robert Watson es= cribi?: >=20 > >=20 > > On Sun, 1 Nov 2009, Matthias Apitz wrote: > >=20 > > >>Could you confirm you are running with a userspace/kernel of at least= =20 > > >>r198203 (the date of the last PIE-related fix following a move to=20 > > >>disallowing NULL mappings). > > > > > >NAK, userland and kernel is: > > > > > >$ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0= =20 > > >r197801: Mon Oct 12 13:33:32 CEST 2009=20 > > >guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 > >=20 > > Sounds like an upgrade should fix this -- if not, please let us know AS= AP=20 > > as it might be an issue for 8.0 as well. >=20 > Robert, do you have an idea why this (with the same kernel/userland) > only shows up after installing the port x11/kde4? The only way to understand what happen there is to ktrace the whole process tree, and then look up execve(2) of which binary causes SIGABRT. --s9kDAZ2EyO0AcRYa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrtiX4ACgkQC3+MBN1Mb4gR6gCgjGwpC2diXGD9QX0XfXEWsk9p fDIAoN1IQk8SaUSpKfR2eWmJ1eDU4j+e =fAEq -----END PGP SIGNATURE----- --s9kDAZ2EyO0AcRYa-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 13:17:44 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDF8910656CD for ; Sun, 1 Nov 2009 13:17:44 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C45418FC13 for ; Sun, 1 Nov 2009 13:17:44 +0000 (UTC) Received: from [192.168.2.101] (host217-43-176-60.range217-43.btcentralplus.com [217.43.176.60]) by cyrus.watson.org (Postfix) with ESMTPSA id E1D9946B29; Sun, 1 Nov 2009 08:17:43 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: "Robert N. M. Watson" In-Reply-To: <20091101130820.GA3658@current.Sisis.de> Date: Sun, 1 Nov 2009 13:17:41 +0000 Content-Transfer-Encoding: 7bit Message-Id: <8514BDB1-FB1B-4B7F-8050-ED01D446B07F@FreeBSD.org> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> <20091101130820.GA3658@current.Sisis.de> To: Matthias Apitz X-Mailer: Apple Mail (2.1076) Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 13:17:45 -0000 On 1 Nov 2009, at 13:08, Matthias Apitz wrote: >>> $ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0- >>> CURRENT #0 >>> r197801: Mon Oct 12 13:33:32 CEST 2009 >>> guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 >> >> Sounds like an upgrade should fix this -- if not, please let us >> know ASAP >> as it might be an issue for 8.0 as well. > > Robert, do you have an idea why this (with the same kernel/userland) > only shows up after installing the port x11/kde4? KDE uses some pre-linking techniques to reduce startup time for applications; I'm not sure what the current version of the code does exactly, but it wouldn't surprise me if it involves PIE executables, which were known to have problems with our null-mapping prevention until recent bug fixes to rtld. If the problem goes away with an upgrade to a new userspace/kernel, I wouldn't worry too much about it. We added the null-mapping prevention a few weeks ago, and later discovered it interacted badly with bugs in our handling of PIE in- kernel and in rtld. Most likely (if the problem goes away with an upgrade), you just ended up with a bad combination of the two that was resolved. Robert From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 16:42:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE3461065692 for ; Sun, 1 Nov 2009 16:42:29 +0000 (UTC) (envelope-from wgodfrey@ena.com) Received: from mail.ena.com (mail.ena.com [96.4.3.70]) by mx1.freebsd.org (Postfix) with ESMTP id ACEED8FC1F for ; Sun, 1 Nov 2009 16:42:29 +0000 (UTC) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 1 Nov 2009 10:30:29 -0600 Message-ID: In-Reply-To: <200910290330.n9T3U1WZ055689@freefall.freebsd.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: amd64/140067: [boot] 8.0-RC2 from ISO, after install, hangs on boot right before loader Thread-Index: AcpYSCG1FFKJreBFTZCskikuBOE37QCx2ElA References: Your message of Thu, 29 Oct 2009 03:28:50 GMT<200910290328.n9T3SoGC018607@www.freebsd.org> <200910290330.n9T3U1WZ055689@freefall.freebsd.org> From: "Weldon Godfrey" To: , , X-Mailman-Approved-At: Sun, 01 Nov 2009 17:15:30 +0000 Cc: Subject: RE: amd64/140067: [boot] 8.0-RC2 from ISO, after install, hangs on boot right before loader X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 16:42:30 -0000 I went ahead and tested booting 8.0-RC2 in the Dell with the Perc5/I and a spare 3ware card, it booted Ok, I swapped the computers around, this would mean I would try to boot with our 3ware controller and with our drive chasis attached and using the Perc5/I, it hung at "-" after boot manager again. I disconnected the drive chasis (we have two SAS chasis with a total of 24 drive). It booted. I had thought I tried this before bit this time it worked. I tried just attaching 1 chasis and 12 drives. It locked up at the "-" again I went into the 3ware controller and disabled the ability to boot from the 3ware card (we don't need to boot from it anyway), and with both chasis attached, it worked. We went ahead and went back to the computer with a PERC6/I controller and it worked with the 3ware BIOS set not able to boot. So it appears, that something has happened during the boot/loader process in 8.0-RC2 that doesn't like the 3ware controller advertising its drives as bootable. This ticket is attached to amd64 but that was my mistake. This problem happens pre-kernel. Let me know if someone can change the category of if you prefer for me to submit a new PR. Thanks!!! Weldon =20 -----Original Message----- From: FreeBSD-gnats-submit@FreeBSD.org [mailto:FreeBSD-gnats-submit@FreeBSD.org]=20 Sent: Wednesday, October 28, 2009 10:30 PM To: Weldon Godfrey Subject: Re: amd64/140067: [boot] 8.0-RC2 from ISO, after install, hangs on boot right before loader Thank you very much for your problem report. It has the internal identification `amd64/140067'. The individual assigned to look at your report is: freebsd-amd64.=20 You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D140067 >Category: amd64 >Responsible: freebsd-amd64 >Synopsis: [boot] 8.0-RC2 from ISO, after install, hangs on boot right before loader >Arrival-Date: Thu Oct 29 03:30:01 UTC 2009 From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 17:51:44 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8812F1065676 for ; Sun, 1 Nov 2009 17:51:44 +0000 (UTC) (envelope-from ben@wanderview.com) Received: from mail.wanderview.com (mail.wanderview.com [66.92.166.102]) by mx1.freebsd.org (Postfix) with ESMTP id 122448FC26 for ; Sun, 1 Nov 2009 17:51:43 +0000 (UTC) Received: from xykon.in.wanderview.com (xykon.in.wanderview.com [10.76.10.152]) (authenticated bits=0) by mail.wanderview.com (8.14.3/8.14.3) with ESMTP id nA1HeP98008704 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 1 Nov 2009 17:40:25 GMT (envelope-from ben@wanderview.com) From: Ben Kelly Content-Type: multipart/mixed; boundary=Apple-Mail-152--382848992 Date: Sun, 1 Nov 2009 12:40:25 -0500 Message-Id: <92BA99AC-E038-44F4-A443-91FF5AA2968F@wanderview.com> To: current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Spam-Score: -1.44 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.64 on 10.76.20.1 Cc: Subject: ifmcstat fails to build without KVM and with INET6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 17:51:44 -0000 --Apple-Mail-152--382848992 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Hello all, I'm having difficulty compiling a freshly updated checkout of head using WITHOUT_KVM src.conf. The error is in src/usr.sbin/ifmcstat/ ifmcstat.c. It appears the problem is due to the in6_ifinfo() function definition being incorrectly under an #ifdef WITH_KVM section. I was able to fix the problem with the attached patch. Just FYI in case anyone else hits this problem. - Ben --Apple-Mail-152--382848992 Content-Disposition: attachment; filename=ifmcstat.patch Content-Type: application/octet-stream; name="ifmcstat.patch" Content-Transfer-Encoding: 7bit Index: usr.sbin/ifmcstat/ifmcstat.c =================================================================== --- usr.sbin/ifmcstat/ifmcstat.c (revision 242) +++ usr.sbin/ifmcstat/ifmcstat.c (working copy) @@ -442,32 +442,6 @@ #ifdef INET6 static void -in6_ifinfo(struct mld_ifinfo *mli) -{ - - printf("\t"); - switch (mli->mli_version) { - case MLD_VERSION_1: - case MLD_VERSION_2: - printf("mldv%d", mli->mli_version); - break; - default: - printf("mldv?(%d)", mli->mli_version); - break; - } - printb(" flags", mli->mli_flags, "\020\1SILENT"); - if (mli->mli_version == MLD_VERSION_2) { - printf(" rv %u qi %u qri %u uri %u", - mli->mli_rv, mli->mli_qi, mli->mli_qri, mli->mli_uri); - } - if (vflag >= 2) { - printf(" v1timer %u v2timer %u", mli->mli_v1_timer, - mli->mli_v2_timer); - } - printf("\n"); -} - -static void if6_addrlist(struct ifaddr *ifap) { struct ifnet ifnet; @@ -764,6 +738,33 @@ #endif /* WITH_KVM */ #ifdef INET6 + +static void +in6_ifinfo(struct mld_ifinfo *mli) +{ + + printf("\t"); + switch (mli->mli_version) { + case MLD_VERSION_1: + case MLD_VERSION_2: + printf("mldv%d", mli->mli_version); + break; + default: + printf("mldv?(%d)", mli->mli_version); + break; + } + printb(" flags", mli->mli_flags, "\020\1SILENT"); + if (mli->mli_version == MLD_VERSION_2) { + printf(" rv %u qi %u qri %u uri %u", + mli->mli_rv, mli->mli_qi, mli->mli_qri, mli->mli_uri); + } + if (vflag >= 2) { + printf(" v1timer %u v2timer %u", mli->mli_v1_timer, + mli->mli_v2_timer); + } + printf("\n"); +} + static const char * inet6_n2a(struct in6_addr *p) { --Apple-Mail-152--382848992-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 1 21:53:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6B36106566B; Sun, 1 Nov 2009 21:53:38 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6921B8FC08; Sun, 1 Nov 2009 21:53:37 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuMFAFGS7UqDaFvJ/2dsb2JhbACQIQHHXoQ5BIFi X-IronPort-AV: E=Sophos;i="4.44,662,1249272000"; d="scan'208";a="52030966" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 01 Nov 2009 16:53:37 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 3FBFEFB8027; Sun, 1 Nov 2009 16:53:37 -0500 (EST) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vC3WPGoW-n0R; Sun, 1 Nov 2009 16:53:35 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 82C6FFB801F; Sun, 1 Nov 2009 16:53:35 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nA1M0n523077; Sun, 1 Nov 2009 17:00:49 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 1 Nov 2009 17:00:49 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: dfr@freebsd.org, O.Seibert@cs.ru.nl Subject: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 21:53:38 -0000 I can now reproduce what I think others were seeing as slow reconnects when using NFSv3 over TCP against a server that disconnects inactive TCP connections. I have had some luck figuring out what is going on and can reproduce it fairly easily, but I really need help from someone who understands the FreeBSD TCP stack. Here's what happens when things break: - the krpc client does a reconnect like normal and the 3 way handshake works for the new socket. - the client sends an RPC on the new socket - at about the same time as this data send, the FreeBSD client sends a reset (yes, that's correct, an RST). --> not surprisingly, the server closes down the new connection and things get stuck until a timeout and another reconnect get things going again. This can be seen by the snoop trace that follows, with the RST at packet #18. (If there isn't a client->server RST packet generated by FreeBSD, the new connection works fine.) What do I know about this from printfs in the code: - It seems to happen when the new socket is at the same address as the old one. (Not a bug. Just happens that uma_zalloc() allocates the same memory as the old one that has been soclose()'d.) - It is timing related. If I add too many printfs, I can't reproduce the problem. My TCP is really rusty, but my theory is that some timer has been set by the FIN sent from the server for the old socket and it is still working on sending the RST when, somehow, the new socket and its tcp pcb get used for the send? Anyone out there able to help? (Please, please..) Here's a snoop trace of one of these (sorry about the long lines). You can see a successful reconnect, a Fin from the server disconnecting after 360sec and then the new connection being created with port#871. Then, at packet #18, there's that pesky RST!! --- snoop trace of FreeBSD-current client nfsv4-test mounted against a Solaris10 server called nfsv4-solaris. (The mount is the regular client, although that shouldn't matter, using NFSv3 over TCP.) 1 0.00000 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=864 Fin Ack=2981056244 Seq=3573648276 Len=0 Win=16588 Options= 2 0.00010 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Syn Seq=729399224 Len=0 Win=65535 Options= 3 0.00054 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=864 S=2049 Rst Seq=2981056244 Len=0 Win=0 4 0.00055 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=740 S=2049 Syn Ack=729399225 Seq=38857223 Len=0 Win=49232 Options= 5 0.00086 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Ack=38857224 Seq=729399225 Len=0 Win=8326 Options= 6 0.00104 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris NFS C FSSTAT3 FH=9D01 7 0.00180 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=740 S=2049 Ack=729399357 Seq=38857224 Len=0 Win=49100 Options= 8 0.00295 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca NFS R FSSTAT3 OK 9 0.10350 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Ack=38857396 Seq=729399357 Len=0 Win=16588 Options= 10 360.00514 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=740 S=2049 Fin Ack=729399357 Seq=38857396 Len=0 Win=49232 Options= 11 360.00549 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Rst Ack=38857397 Seq=729399357 Len=0 Win=0 12 360.00557 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Rst Ack=38857397 Seq=729399357 Len=0 Win=0 13 360.00586 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=740 Ack=38857397 Seq=729399357 Len=0 Win=16588 Options= 14 360.00594 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=740 S=2049 Rst Seq=38857397 Len=0 Win=0 15 495.15000 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=871 Syn Seq=369106877 Len=0 Win=65535 Options= 16 495.15013 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=871 S=2049 Syn Ack=369106878 Seq=159825643 Len=0 Win=49232 Options= 17 495.15040 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=871 Ack=159825644 Seq=369106878 Len=0 Win=8326 Options= 18 495.15089 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=871 Rst Ack=159825644 Seq=369106878 Len=0 Win=0 19 495.15162 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris NFS C FSSTAT3 FH=9D01 20 495.15265 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=871 S=2049 Rst Seq=159825644 Len=0 Win=0 21 495.15305 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=883 Syn Seq=3875668538 Len=0 Win=65535 Options= 22 495.15322 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=883 S=2049 Syn Ack=3875668539 Seq=159964181 Len=0 Win=49232 Options= 23 495.15348 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=883 Ack=159964182 Seq=3875668539 Len=0 Win=8326 Options= 24 495.15368 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris NFS C FSSTAT3 FH=9D01 25 495.15374 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=883 Rst Ack=159964182 Seq=3875668539 Len=0 Win=0 26 495.15427 nfsv4-solaris -> nfsv4-test.cis.uoguelph.ca TCP D=883 S=2049 Ack=3875668671 Seq=159964182 Len=0 Win=49100 Options= 27 495.15457 nfsv4-test.cis.uoguelph.ca -> nfsv4-solaris TCP D=2049 S=883 Rst Ack=159964182 Seq=3875668671 Len=0 Win=0 From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 01:04:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61FA5106566B for ; Mon, 2 Nov 2009 01:04:23 +0000 (UTC) (envelope-from don@siad.net) Received: from omr11.networksolutionsemail.com (omr11.networksolutionsemail.com [205.178.146.61]) by mx1.freebsd.org (Postfix) with ESMTP id CC28C8FC17 for ; Mon, 2 Nov 2009 01:04:22 +0000 (UTC) Received: from mail.networksolutionsemail.com (mail.networksolutionsemail.com [205.178.146.50]) by omr11.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id nA20Zuwx031020 for ; Sun, 1 Nov 2009 19:35:56 -0500 Received: (qmail 15395 invoked by uid 78); 2 Nov 2009 00:35:56 -0000 Received: from unknown (HELO ?192.168.1.66?) (don@siad.net@68.122.21.45) by ns-omr1.lb.hosting.dc2.netsol.com with SMTP; 2 Nov 2009 00:35:56 -0000 Message-ID: <4AEE296B.5040302@siad.net> Date: Sun, 01 Nov 2009 16:35:55 -0800 From: "Don L. Belcher" Organization: SIAD Inc. User-Agent: Thunderbird 2.0.0.23 (X11/20090925) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: bootstrap loader problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 01:04:23 -0000 New Dell 1737 laptop The following error occurs with versions 7.2 release and later this message is from 8 RC2. All versions tried with 7.1 release and earlier work fine, I tried 7.1, 7.2 and 6.4. I rebuilt 8 RC2 CD with "loader" from 7.1 release and the 8 RC2 comes up O.K. now. I have two questions: 1) is anybody familiar with this problem 2) is it ok to install 8 RC2 using the 7.1 "loader" BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard panic: free: guard1 fail @ 0xbb797074 from (diretory path to) common/console.c:94 --> Press a key (etc) From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 10:06:55 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C4531065670; Mon, 2 Nov 2009 10:06:55 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id C9E068FC15; Mon, 2 Nov 2009 10:06:54 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id 74723184E6E5B; Mon, 2 Nov 2009 11:06:53 +0100 (CET) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id nA2A6tr6002946; Mon, 2 Nov 2009 11:06:55 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Mon, 2 Nov 2009 11:06:55 +0100 From: Matthias Apitz To: Robert Watson Message-ID: <20091102100655.GA2934@current.Sisis.de> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 10:06:55 -0000 El da Sunday, November 01, 2009 a las 10:45:41AM +0000, Robert Watson escribi: > > On Sun, 1 Nov 2009, Matthias Apitz wrote: > > >>Could you confirm you are running with a userspace/kernel of at least > >>r198203 (the date of the last PIE-related fix following a move to > >>disallowing NULL mappings). > > > >NAK, userland and kernel is: > > > >$ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 > >r197801: Mon Oct 12 13:33:32 CEST 2009 > >guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 > > Sounds like an upgrade should fix this -- if not, please let us know ASAP > as it might be an issue for 8.0 as well. Would this require as well to re-compile all my ~1200 ports or are there no changes in the ABI since r197801? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 10:13:30 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14BF1106568D for ; Mon, 2 Nov 2009 10:13:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DFE628FC0A for ; Mon, 2 Nov 2009 10:13:29 +0000 (UTC) Received: from [192.168.2.101] (host217-43-176-60.range217-43.btcentralplus.com [217.43.176.60]) by cyrus.watson.org (Postfix) with ESMTPSA id 0A04846B06; Mon, 2 Nov 2009 05:13:28 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes From: "Robert N. M. Watson" In-Reply-To: <20091102100655.GA2934@current.Sisis.de> Date: Mon, 2 Nov 2009 10:13:27 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <570D2EEB-B09F-4B71-A1E8-2A1D760B0634@FreeBSD.org> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de> <20091101103934.GA3004@current.Sisis.de> <20091102100655.GA2934@current.Sisis.de> To: Matthias Apitz X-Mailer: Apple Mail (2.1076) Cc: kde-freebsd@kde.org, freebsd-current@FreeBSD.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 10:13:30 -0000 On 2 Nov 2009, at 10:06, Matthias Apitz wrote: > El d=EDa Sunday, November 01, 2009 a las 10:45:41AM +0000, Robert =20 > Watson escribi=F3: > >> >> On Sun, 1 Nov 2009, Matthias Apitz wrote: >> >>>> Could you confirm you are running with a userspace/kernel of at =20 >>>> least >>>> r198203 (the date of the last PIE-related fix following a move to >>>> disallowing NULL mappings). >>> >>> NAK, userland and kernel is: >>> >>> $ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-=20 >>> CURRENT #0 >>> r197801: Mon Oct 12 13:33:32 CEST 2009 >>> guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 >> >> Sounds like an upgrade should fix this -- if not, please let us =20 >> know ASAP >> as it might be an issue for 8.0 as well. > > Would this require as well to re-compile all my ~1200 ports or are =20 > there > no changes in the ABI since r197801? I'm not aware of ABI changes, but that's always a risk when updating =20 on the -CURRENT branch. Another approach would be to extract the =20 relevant changes and apply them to your current source tree, but there =20= are a fair number and you wouldn't want to miss any. I believe they're =20= all to either the kernel or rtld. Robert= From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 12:09:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D4CE106566C for ; Mon, 2 Nov 2009 12:09:13 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [199.237.202.236]) by mx1.freebsd.org (Postfix) with ESMTP id C09768FC15 for ; Mon, 2 Nov 2009 12:09:12 +0000 (UTC) Received: from neu.net (neu.net [199.237.202.236]) by neu.net (8.13.6.20060614/8.13.6) with ESMTP id nA2C99mu085725 for ; Mon, 2 Nov 2009 12:09:11 GMT Date: Mon, 2 Nov 2009 12:09:09 +0000 (GMT) From: AN To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.95.1 at neu.net X-Virus-Status: Clean Subject: amd64-9 packages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 12:09:13 -0000 According to: http://pointyhat.freebsd.org/errorlogs/packagestats.html there are no packages for amd64 9 current. FreeBSD package building statistics as of Mon Nov 2 11:45:02 UTC 2009 amd64-9 0 0 0 0 0 0 N N When can we expect these packages to be available? TIA From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 12:21:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2A60106566B for ; Mon, 2 Nov 2009 12:21:53 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [199.237.202.236]) by mx1.freebsd.org (Postfix) with ESMTP id 504958FC21 for ; Mon, 2 Nov 2009 12:21:52 +0000 (UTC) Received: from neu.net (neu.net [199.237.202.236]) by neu.net (8.13.6.20060614/8.13.6) with ESMTP id nA2CLlSe092065; Mon, 2 Nov 2009 12:21:49 GMT Date: Mon, 2 Nov 2009 12:21:47 +0000 (GMT) From: AN To: Remko Lodder In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.95.1 at neu.net X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: amd64-9 packages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 12:21:54 -0000 On Mon, 2 Nov 2009, Remko Lodder wrote: > > You are asking port related things on a -current mailinglist. Perhaps you > should try ports@? > > On Nov 2, 2009, at 1:09 PM, AN wrote: > >> According to: http://pointyhat.freebsd.org/errorlogs/packagestats.html >> there are no packages for amd64 9 current. >> > > > -- > /"\ Best regards, | remko@FreeBSD.org > \ / Remko Lodder | remko@EFnet > X http://www.evilcoder.org/ | > / \ ASCII Ribbon Campaign | Against HTML Mail and News Thank you, sorry for the noise. From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 12:15:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6BE51065672 for ; Mon, 2 Nov 2009 12:15:03 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from mailgate.jr-hosting.nl (mailgate.jr-hosting.nl [78.46.126.30]) by mx1.freebsd.org (Postfix) with ESMTP id 689B98FC15 for ; Mon, 2 Nov 2009 12:15:03 +0000 (UTC) Received: from websrv01.jr-hosting.nl (websrv01 [78.47.69.233]) by mailgate.jr-hosting.nl (Postfix) with ESMTP id 860891CD2C; Mon, 2 Nov 2009 13:15:01 +0100 (CET) Received: from milamber.elvandar.org ([78.47.44.222] helo=[10.0.3.2]) by websrv01.jr-hosting.nl with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N4voL-0004H3-G3; Mon, 02 Nov 2009 13:15:01 +0100 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Remko Lodder In-Reply-To: Date: Mon, 2 Nov 2009 13:15:00 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: To: AN X-Mailer: Apple Mail (2.1076) X-Mailman-Approved-At: Mon, 02 Nov 2009 12:36:15 +0000 Cc: freebsd-current@freebsd.org Subject: Re: amd64-9 packages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 12:15:03 -0000 You are asking port related things on a -current mailinglist. Perhaps you should try ports@? On Nov 2, 2009, at 1:09 PM, AN wrote: > According to: http://pointyhat.freebsd.org/errorlogs/packagestats.html > there are no packages for amd64 9 current. > -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 13:22:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72CC71065670 for ; Mon, 2 Nov 2009 13:22:06 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 35C2D8FC1B for ; Mon, 2 Nov 2009 13:22:05 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-167-182.rz.uni-karlsruhe.de [141.3.167.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 25EF08A0DF8 for ; Mon, 2 Nov 2009 14:22:05 +0100 (CET) Message-ID: <4AEEDCFB.3060604@bsdforen.de> Date: Mon, 02 Nov 2009 14:22:03 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 13:22:06 -0000 It appears that my 8.0-RC2 system (notebook) forgets its mixer settings with every reboot. FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct 31 02:49:30 CET 2009 root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 13:30:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08B631065676 for ; Mon, 2 Nov 2009 13:30:49 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id C0AD58FC12 for ; Mon, 2 Nov 2009 13:30:48 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id BE23F6D41B; Mon, 2 Nov 2009 13:30:47 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 76F62844E9; Mon, 2 Nov 2009 14:30:47 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Dominic Fandrey References: <4AEEDCFB.3060604@bsdforen.de> Date: Mon, 02 Nov 2009 14:30:47 +0100 In-Reply-To: <4AEEDCFB.3060604@bsdforen.de> (Dominic Fandrey's message of "Mon, 02 Nov 2009 14:22:03 +0100") Message-ID: <86fx8xm4u0.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 13:30:49 -0000 Dominic Fandrey writes: > It appears that my 8.0-RC2 system (notebook) forgets its mixer > settings with every reboot. Check the contents of /var/db/*-state. (if it were up to me, we'd store the mixer state in /var/db/mixer/$foo instead of /var/db/$foo-state) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 14:21:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7CCE1065672 for ; Mon, 2 Nov 2009 14:21:45 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.211.178]) by mx1.freebsd.org (Postfix) with ESMTP id B07CB8FC1F for ; Mon, 2 Nov 2009 14:21:45 +0000 (UTC) Received: by ywh8 with SMTP id 8so4663389ywh.3 for ; Mon, 02 Nov 2009 06:21:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.101.153.30 with SMTP id f30mr2735151ano.0.1257171697529; Mon, 02 Nov 2009 06:21:37 -0800 (PST) In-Reply-To: <86fx8xm4u0.fsf@ds4.des.no> References: <4AEEDCFB.3060604@bsdforen.de> <86fx8xm4u0.fsf@ds4.des.no> Date: Mon, 2 Nov 2009 15:21:36 +0100 Message-ID: <367b2c980911020621o1ef34413ra07310e97b0dc982@mail.gmail.com> From: Olivier Smedts To: Dominic Fandrey Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 14:21:46 -0000 2009/11/2 Dag-Erling Sm=F8rgrav : > Dominic Fandrey writes: >> It appears that my 8.0-RC2 system (notebook) forgets its mixer >> settings with every reboot. > > Check the contents of /var/db/*-state. Also, do you use a desktop environment with a mixer app which could interfere with the system mixer ? (like KMix for KDE) I had the same problem until I realized my mixer resets came from KMix) Cheers, Olivier > > (if it were up to me, we'd store the mixer state in /var/db/mixer/$foo > instead of /var/db/$foo-state) > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --=20 Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 15:08:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC5F71065742 for ; Mon, 2 Nov 2009 15:08:52 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 7B8F58FC1C for ; Mon, 2 Nov 2009 15:08:52 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-167-182.rz.uni-karlsruhe.de [141.3.167.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 2458A8A0D25; Mon, 2 Nov 2009 16:08:51 +0100 (CET) Message-ID: <4AEEF601.9080801@bsdforen.de> Date: Mon, 02 Nov 2009 16:08:49 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Olivier Smedts References: <4AEEDCFB.3060604@bsdforen.de> <86fx8xm4u0.fsf@ds4.des.no> <367b2c980911020621o1ef34413ra07310e97b0dc982@mail.gmail.com> In-Reply-To: <367b2c980911020621o1ef34413ra07310e97b0dc982@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 15:08:52 -0000 Olivier Smedts wrote: > 2009/11/2 Dag-Erling Smørgrav : >> Dominic Fandrey writes: >>> It appears that my 8.0-RC2 system (notebook) forgets its mixer >>> settings with every reboot. >> Check the contents of /var/db/*-state. > > Also, do you use a desktop environment with a mixer app which could > interfere with the system mixer ? (like KMix for KDE) > I had the same problem until I realized my mixer resets came from KMix) Most definitely not. The only mixer application is /usr/sbin/mixer. # pkg_info -Ex mix sdl_mixer-1.2.8_2 From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 15:12:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ADE2106566B for ; Mon, 2 Nov 2009 15:12:58 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2098FC2A for ; Mon, 2 Nov 2009 15:12:58 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-167-182.rz.uni-karlsruhe.de [141.3.167.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 678B98A0DA0; Mon, 2 Nov 2009 16:12:55 +0100 (CET) Message-ID: <4AEEF6F4.2080904@bsdforen.de> Date: Mon, 02 Nov 2009 16:12:52 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <4AEEDCFB.3060604@bsdforen.de> <86fx8xm4u0.fsf@ds4.des.no> In-Reply-To: <86fx8xm4u0.fsf@ds4.des.no> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 15:12:58 -0000 Dag-Erling Smørgrav wrote: > Dominic Fandrey writes: >> It appears that my 8.0-RC2 system (notebook) forgets its mixer >> settings with every reboot. > > Check the contents of /var/db/*-state. Thanks for the pointer. Is that updated during shutdown or every time the mixer settings are changed? The file is not in sync with my current mixer settings. > (if it were up to me, we'd store the mixer state in /var/db/mixer/$foo > instead of /var/db/$foo-state) Sounds sensible to me. Ever wrote a PR? Is there a manual page with in depth information? mixer(8) doesn't mention the mixerX-state files. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 15:56:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ED301065676 for ; Mon, 2 Nov 2009 15:56:52 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id D9C988FC22 for ; Mon, 2 Nov 2009 15:56:51 +0000 (UTC) Received: by yxe1 with SMTP id 1so4770651yxe.3 for ; Mon, 02 Nov 2009 07:56:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=eJlm4I4JiSIBY9scCd+fE6AQinu55CgsAS+X3Q8Fjn4=; b=u45svL5LIhC4+HoCzgAftys0coC9O1zyCd9PN3uHHrBQk/CWEv8H+FZYv+HZDDrmg6 W6ayCRo60Xy1vCI4JzbgTnYKEuiNTXtwpkOuZxYWRQSYiRy5fPoBvjl3y2Ir8Joncvlc bewT6tAVGCM4TALeLNnMZs1Sm/zLwoZwoCT7k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=GycffoJDjvqXc/zRB1gFchs7E3xBLEn3JHila4oW57k1kwTdwj0F/zOL+0rL595NwQ DjThrW5V4tOA08iGCIG/F3JyzOsojW6PJb72hLNdn2pdit2P3JoDLjeyDimr9alyiUnN f2HXITwIHUzaFxbKEh0/Crw6Rx7GnfdxNpFgU= Received: by 10.90.45.11 with SMTP id s11mr8954470ags.72.1257177407758; Mon, 02 Nov 2009 07:56:47 -0800 (PST) Received: from ?192.168.1.100? ([190.177.224.62]) by mx.google.com with ESMTPS id 8sm2575475yxb.43.2009.11.02.07.56.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Nov 2009 07:56:46 -0800 (PST) From: Gonzalo Nemmi To: freebsd-current@freebsd.org Date: Mon, 2 Nov 2009 13:56:42 -0200 User-Agent: KMail/1.9.10 References: <4AEEDCFB.3060604@bsdforen.de> In-Reply-To: <4AEEDCFB.3060604@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911021356.43043.gnemmi@gmail.com> Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 15:56:52 -0000 On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > It appears that my 8.0-RC2 system (notebook) forgets its mixer > settings with every reboot. > > FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct 31 > 02:49:30 CET 2009 > root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510 >b-8 amd64 > > Regards May I ask how are you setting them? Regards Gonzalo From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 17:25:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4EEC1065679 for ; Mon, 2 Nov 2009 17:25:45 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.211.178]) by mx1.freebsd.org (Postfix) with ESMTP id 97D758FC1B for ; Mon, 2 Nov 2009 17:25:45 +0000 (UTC) Received: by ywh8 with SMTP id 8so4847680ywh.3 for ; Mon, 02 Nov 2009 09:25:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:date:subject:from:to:user-agent:mime-version :content-type:content-transfer-encoding:x-priority:importance; bh=RH10RwzHK+TP4UscDbtYYuhutEG8pfWvDLgY/IBbFR4=; b=RONHe6MmWMtE12bmiSCi6a05KHiumesAcfIpis+ZwUCBUApbc9wHdcFrS16cAgJL6s TbrAThGb6iD3PEfRBJh/L50++IFQWez4bhv7s1PsT69qzJgg8p7ahU0ohjDyf3XQa7Ww 7+oQC0xxqXnw4eltq5fLwb7wsiKENHh/V9M5M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:subject:from:to:user-agent:mime-version :content-type:content-transfer-encoding:x-priority:importance; b=EJXPfeOzcePEX0pZIfas1+BjxDfjg8q33dPPLnfaSSEhW6oYaBGMDZK8eL1tAkSvom jXbVdNBBsqLr14u4n2Rpa49KGrCwdJy4ZjW6Ph28jqZPXfsmSNME5FD5FLCxsAsBwHA2 b2WbKas+4swyx69A9DOSsdHoU8+q5Sxh7yxjg= Received: by 10.91.28.9 with SMTP id f9mr9212225agj.89.1257182734562; Mon, 02 Nov 2009 09:25:34 -0800 (PST) Received: from cygnus.homeunix.com ([189.71.46.105]) by mx.google.com with ESMTPS id 39sm1424562yxd.45.2009.11.02.09.25.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Nov 2009 09:25:32 -0800 (PST) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id CC099B805F; Mon, 2 Nov 2009 14:25:24 -0300 (BRT) Received: from 189.99.44.50 (SquirrelMail authenticated user matheus) by cygnus.homeunix.com with HTTP; Mon, 2 Nov 2009 15:25:24 -0200 (BRST) Message-ID: <4480d94e7b5662b5a506e2d72bf75f8f.squirrel@cygnus.homeunix.com> Date: Mon, 2 Nov 2009 15:25:24 -0200 (BRST) From: "Nenhum_de_Nos" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: status on usb/139598 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 17:25:46 -0000 hail, what's the status on this issue ? I wrote some bytes in this external usb hdd and now upgraded to 8.0-rc2, then I can't read them :( the other 7.2 box I have is in work, and I'm on vacation starting today :) no workarounds ? I must install a 7.2 to read it ? thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 15:52:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B5D51065695 for ; Mon, 2 Nov 2009 15:52:36 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id F13E78FC21 for ; Mon, 2 Nov 2009 15:52:35 +0000 (UTC) Received: (qmail 62060 invoked by uid 89); 2 Nov 2009 15:52:33 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 2 Nov 2009 15:52:33 -0000 Date: Mon, 2 Nov 2009 10:52:33 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Mailman-Approved-At: Mon, 02 Nov 2009 17:39:32 +0000 Subject: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 15:52:36 -0000 Up until yesterday, we have been running FreeBSD-CURRENT of 12/08. We started to see a couple months ago some very odd network behavior. Something happens to the stack that causes processes accessing the network to just hang. After the problem happens, usually (but not always), you can't ssh in. Always, you can't ssh or telnet out, and nothing can access the NFS shares on the server. You can ping everything from the server. You can't even do a route add, you can't ssh if you use just the IP address (although pinging with hostnames it doesn't have cached or in hosts table resolves). When you try to ssh out, do a route add from the box, the process just hangs. You can't control C it at all, it hangs forever. There is nothing in dmesg or messages to indicate an issue. I try to up/down the interfaces. In CURRENT-12/08, it may allow things to work for like 30s. We upgraded to 8.0-RC2 yesterday and, at first, the problem appeared to happen a lot more often. We expected that was related with the increase in network performance. At least in 8.0-RC2, I did see a large amount of input errors with netstat -in on the heavily loaded interface before it started the locking up behavior. I have replaced the ethernet cable and move ports. The Catalyst 3650 never records any errors. The problem would reoccur in about 5 minutes once our load kicked in this morning. One change in this upgrade, we switched from NFS v2 to v3. When we downgraded to the previous OS, we stayed at v3. The problem was just about as bad with v3 with the 12/08 OS We went back to RC2 with NFS v2 and appeared to stabilize to a degree. It ran for about an hour and a half and then the issue came up We are currently back to the 12/08 version using NFS2 and watching things. We are using a Dell PowerEdge 2950-iii, the problem happens when using the onboard nics using the bce driver and with an Intel card using the em driver I am hunting down any MTU/duplex/speed problems that could cause it (haven't found any so far). Of course, any problems on the network wouldn't (ideally) freak out the network stack on the server). I don't know how to troubleshoot this further on the server since I am not getting any problems indicated in logging, panics, cores, etc. Any help is appreciated. Thanks, Weldon From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 19:22:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A75A3106566B for ; Mon, 2 Nov 2009 19:22:39 +0000 (UTC) (envelope-from jh@sandstorm.net) Received: from sirocco.sandstorm.net (sirocco.sandstorm.net [69.33.111.75]) by mx1.freebsd.org (Postfix) with ESMTP id 482578FC16 for ; Mon, 2 Nov 2009 19:22:39 +0000 (UTC) Received: from lister.sandstorm.net (ip-69-33-111-74.bos.megapath.net [69.33.111.74]) (authenticated bits=0) by sirocco.sandstorm.net (8.13.8/8.13.3) with ESMTP id nA2JMZhx092518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Nov 2009 14:22:35 -0500 (EST) (envelope-from jh@sandstorm.net) Message-ID: <4AEF317B.8030200@sandstorm.net> Date: Mon, 02 Nov 2009 14:22:35 -0500 From: John Hood User-Agent: Thunderbird 2.0.0.23 (X11/20090928) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on sirocco.sandstorm.net X-Mailman-Approved-At: Mon, 02 Nov 2009 19:30:57 +0000 Subject: gnome, automounting, and ataraid don't get along well X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 19:22:39 -0000 [I sent this last week to freebsd-gnome and freebsd-current, but it didn't appear on freebsd-current.] I upgraded my desktop machine to 8.0-RC2 and 8.0-RELEASE packages recently. This machine uses an Intel chipset, ICH9R southbridge, and two SATA drives configured in a RAID1 with Intel's soft-RAID BIOS. ad10 and ad12 are automatically configured into an array by ataraid that shows up as ar0, which has FreeBSD installed in a typical UFS multi-partition setup. I'm using the GNOME desktop. At first glance, all appears to be happy. But when I run a software build that creates/mounts filesystem images with the md driver, I get an authentication dialog (at http://users.rcn.com/john70/auth.jpg ) which wants to mount something but doesn't say what. If I authenticate, gnome then proceeds to mount multiple devices in /dev/ufsid and/or partitions of ad12s1, ignoring the fact that that they're part of a RAID that's already mounted. (It seemed to ignore the md device, though.) I get this in syslog, suggesting that kernel & mount are unaware of the duplicate mounts: Oct 27 17:54:40 lister kernel: WARNING: /site was not properly dismounted Oct 27 17:54:40 lister kernel: /site: mount pending error: blocks 32 files 2 This obviously has big potential for filesystem corruption on any FreeBSD 8.0 system using GNOME and ataraid. Fortunately, I seem not to have lost any data. This also happens when attaching/detaching a USB drive. I didn't see any of this with FreeBSD 7.1, probably because automounting was broken or disabled there. I see several problems here. 1) the GNOME authentication dialog gives you no clue what it's trying to mount (when I saw it, I guessed it was GNOME's automounting wanting to play with the md device), and no clue that its caller will apply the authorization on six other mounts it has pending. 2) the devices in /dev/ufsid/ are associated with partitions on the adN drives, not for the RAID they're assembled into (not sure whether ata or ataraid or geom/glabel is responsible for this). I only see devices for one of the drives, but I think this is because the mirrored filesystems have the same UFS IDs on each drive and duplicates get disallowed/not-handled somewhere. 3) adN devices that are in an ATA raid are still visible in /dev and mountable. 4) GNOME isn't aware of any of this (should it be, or should the issue be handled in devfs & GEOM?) 5) There doesn't seem to be any tool to check or repair an ataraid mirror. For the moment, I've got the authentication disabled so the problem doesn't arise. If anyone wants to look at this, I'll be happy to help, otherwise I'll look at ataraid when I get a chance. --jh From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 20:37:50 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F04831065695 for ; Mon, 2 Nov 2009 20:37:50 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 826E58FC2F for ; Mon, 2 Nov 2009 20:37:50 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.3/8.14.3) with ESMTP id nA2KbmBs031297; Mon, 2 Nov 2009 15:37:48 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.3/8.14.3/Submit) id nA2Kbm43031296; Mon, 2 Nov 2009 15:37:48 -0500 (EST) (envelope-from wollman) Date: Mon, 2 Nov 2009 15:37:48 -0500 (EST) From: Garrett Wollman Message-Id: <200911022037.nA2Kbm43031296@hergotha.csail.mit.edu> To: jh@sandstorm.net References: <4AEF317B.8030200@sandstorm.net> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Mon, 02 Nov 2009 15:37:48 -0500 (EST) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu X-Mailman-Approved-At: Mon, 02 Nov 2009 21:13:50 +0000 Cc: current@freebsd.org Subject: Re: gnome, automounting, and ataraid don't get along well X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 20:37:51 -0000 In article <4AEF317B.8030200@sandstorm.net>, jh@sandstorm.net writes: >2) the devices in /dev/ufsid/ are associated with partitions on the adN >drives, not for the RAID they're assembled into (not sure whether ata or >ataraid or geom/glabel is responsible for this). This is a long-standing bug in ataraid. It should not be possible to open the individual members of a RAID set for writing, and the existence of the ataraid should spoil other consumers of the individual disk providers. (The same thing happens with regular UFS labels. I think the actual problem is that ataraid works behind GEOM's back, but doesn't withdraw the disk providers so GEOM thinks they are separate devices.) The only workaround that I have found is to disable the poor-man's-RAID and use gmirror instead. In general, having used both ataraid and gmirror systems since 5.x, my impression is that gmirror works better and is more manageable. -GAWollman From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 21:11:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B805E1065679 for ; Mon, 2 Nov 2009 21:11:16 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5248FC08 for ; Mon, 2 Nov 2009 21:11:15 +0000 (UTC) Received: (qmail 86991 invoked by uid 89); 2 Nov 2009 21:11:14 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 2 Nov 2009 21:11:14 -0000 Date: Mon, 2 Nov 2009 16:11:13 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: freebsd-current@freebsd.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Mon, 02 Nov 2009 21:29:44 +0000 Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 21:11:16 -0000 If memory serves me right, sometime around 10:52am, Weldon S Godfrey 3 told me: > > Up until yesterday, we have been running FreeBSD-CURRENT of 12/08. We started > to see a couple months ago some very odd network behavior. Something happens > to the stack that causes processes accessing the network to just hang. After > the problem happens, usually (but not always), you can't ssh in. Always, you > can't ssh or telnet out, and nothing can access the NFS shares on the server. > You can ping everything from the server. You can't even do a route add, you > can't ssh if you use just the IP address (although pinging with hostnames it > doesn't have cached or in hosts table resolves). When you try to ssh out, do > a route add from the box, the process just hangs. You can't control C it at > all, it hangs forever. There is nothing in dmesg or messages to indicate an > issue. I try to up/down the interfaces. In CURRENT-12/08, it may allow > things to work for like 30s. > > We upgraded to 8.0-RC2 yesterday and, at first, the problem appeared to happen > a lot more often. We expected that was related with the increase in network > performance. At least in 8.0-RC2, I did see a large amount of input errors > with netstat -in on the heavily loaded interface before it started the locking > up behavior. I have replaced the ethernet cable and move ports. The Catalyst > 3650 never records any errors. The problem would reoccur in about 5 minutes > once our load kicked in this morning. > > > One change in this upgrade, we switched from NFS v2 to v3. When we downgraded > to the previous OS, we stayed at v3. The problem was just about as bad with > v3 with the 12/08 OS > > We went back to RC2 with NFS v2 and appeared to stabilize to a degree. > It ran for about an hour and a half and then the issue came up > > We are currently back to the 12/08 version using NFS2 and watching things. > > We are using a Dell PowerEdge 2950-iii, the problem happens when using the > onboard nics using the bce driver and with an Intel card using the em driver > > I am hunting down any MTU/duplex/speed problems that could cause it (haven't > found any so far). Of course, any problems on the network wouldn't (ideally) > freak out the network stack on the server). I don't know how to troubleshoot > this further on the server since I am not getting any problems indicated in > logging, panics, cores, etc. > > Any help is appreciated. > I have swapped out the computer, switch, ethernet card, 3ware card. We are running on 8.0-CURRENT 12/08 that was what we where using with a lot less issues. No help. If it happens again, I am going to try to do a netif restart and routing restart. Although I believe I tried that at the begining and it did not help. From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 21:48:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D11EE106568B for ; Mon, 2 Nov 2009 21:48:34 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id 7AFAC8FC17 for ; Mon, 2 Nov 2009 21:48:33 +0000 (UTC) Received: (qmail 89846 invoked by uid 89); 2 Nov 2009 21:48:32 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 2 Nov 2009 21:48:32 -0000 Date: Mon, 2 Nov 2009 16:48:31 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: freebsd-current@freebsd.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Mon, 02 Nov 2009 22:00:41 +0000 Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 21:48:34 -0000 If memory serves me right, sometime around 4:11pm, Weldon S Godfrey 3 told me: > > > If memory serves me right, sometime around 10:52am, Weldon S Godfrey 3 told > me: > >> >> Up until yesterday, we have been running FreeBSD-CURRENT of 12/08. We >> started to see a couple months ago some very odd network behavior. Something >> happens to the stack that causes processes accessing the network to just >> hang. After the problem happens, usually (but not always), you can't ssh >> in. Always, you can't ssh or telnet out, and nothing can access the NFS >> shares on the server. You can ping everything from the server. You can't >> even do a route add, you can't ssh if you use just the IP address (although >> pinging with hostnames it doesn't have cached or in hosts table resolves). >> When you try to ssh out, do a route add from the box, the process just >> hangs. You can't control C it at all, it hangs forever. There is nothing >> in dmesg or messages to indicate an issue. I try to up/down the interfaces. >> In CURRENT-12/08, it may allow things to work for like 30s. >> >> We upgraded to 8.0-RC2 yesterday and, at first, the problem appeared to >> happen a lot more often. We expected that was related with the increase in >> network performance. At least in 8.0-RC2, I did see a large amount of input >> errors with netstat -in on the heavily loaded interface before it started >> the locking up behavior. I have replaced the ethernet cable and move ports. >> The Catalyst 3650 never records any errors. The problem would reoccur in >> about 5 minutes once our load kicked in this morning. >> >> >> One change in this upgrade, we switched from NFS v2 to v3. When we >> downgraded to the previous OS, we stayed at v3. The problem was just about >> as bad with v3 with the 12/08 OS >> >> We went back to RC2 with NFS v2 and appeared to stabilize to a degree. >> It ran for about an hour and a half and then the issue came up >> >> We are currently back to the 12/08 version using NFS2 and watching things. >> >> We are using a Dell PowerEdge 2950-iii, the problem happens when using the >> onboard nics using the bce driver and with an Intel card using the em driver >> >> I am hunting down any MTU/duplex/speed problems that could cause it (haven't >> found any so far). Of course, any problems on the network wouldn't >> (ideally) freak out the network stack on the server). I don't know how to >> troubleshoot this further on the server since I am not getting any problems >> indicated in logging, panics, cores, etc. >> >> Any help is appreciated. >> > > > I have swapped out the computer, switch, ethernet card, 3ware card. We are > running on 8.0-CURRENT 12/08 that was what we where using with a lot less > issues. No help. > > If it happens again, I am going to try to do a netif restart and routing > restart. Although I believe I tried that at the begining and it did not help. > BTW.. doing a netif / routing restart doesn't help From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 00:23:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFE87106566C for ; Tue, 3 Nov 2009 00:23:03 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6FD8FC1E for ; Tue, 3 Nov 2009 00:23:03 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N57Ap-0000xJ-1k for freebsd-current@freebsd.org; Tue, 03 Nov 2009 01:22:59 +0100 Received: from 78-1-134-182.adsl.net.t-com.hr ([78.1.134.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 01:22:59 +0100 Received: from ivoras by 78-1-134-182.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 01:22:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 03 Nov 2009 01:22:35 +0100 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-134-182.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (X11/20090612) In-Reply-To: Sender: news Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 00:23:04 -0000 Weldon S Godfrey 3 wrote: > I don't > know how to troubleshoot this further on the server since I am not > getting any problems indicated in logging, panics, cores, etc. If you have console access to the system, the generic advice would be to compile a kernel with the kernel debugger - options KDB and DDB (see http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html), enter the debugger, force a kernel dump file to be created (by entering "call doadump") and then proceed with post-mortem examination of the kernel at your leisure (e.g. from a remote ssh console, etc). See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html for instructions on what information to collect. If you can provoke your problem with using WITNESS that would probably be great, but it will slow down your production machine noticeably. When WITNESS is enabled you might also get more information - such as LOR warnings, which you should also collect. Keep the dump file, someone might ask you for more information. Good luck! From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 01:03:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A83FC106568B for ; Tue, 3 Nov 2009 01:03:31 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay2.uni-muenster.de (ZIVM-EXRELAY2.UNI-MUENSTER.DE [128.176.192.15]) by mx1.freebsd.org (Postfix) with ESMTP id 3B8528FC1D for ; Tue, 3 Nov 2009 01:03:30 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,670,1249250400"; d="scan'208";a="227911626" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER01.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay2.uni-muenster.de with ESMTP; 03 Nov 2009 02:03:30 +0100 Received: by ZIVMAILUSER01.UNI-MUENSTER.DE (Postfix, from userid 149459) id 1C8C11B0766; Tue, 3 Nov 2009 02:03:29 +0100 (CET) Date: Tue, 03 Nov 2009 02:03:29 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Dominic Fandrey , Alexander Best Message-ID: In-Reply-To: <4AEBFAA3.9020003@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 01:03:31 -0000 Dominic Fandrey schrieb am 2009-10-31: > Alexander Best wrote: > > i've experienced similar issues with msdosfs. it seems especially > > /sbin/fsck_msdosfs needs some updating. > > cheers. > > alex > Not only that, write access is really broken. looks like someone with really good fs/fat16/fat32 knowledge needs to take a look at this. seems fat16/fat32 quality has been steadily going down hill since releng_4 imo. i guess the freebsd-fs@ guys know about these problems but don't have the time to deal with it. most of them are probably working on zfs. good thing however that you posted a pr (kern/140134). hope somebody will step up and fix the msdosfs code. alex From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 01:02:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9ECB106566C for ; Tue, 3 Nov 2009 01:02:12 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id B8BE58FC15 for ; Tue, 3 Nov 2009 01:02:11 +0000 (UTC) Received: (qmail 2224 invoked by uid 89); 3 Nov 2009 01:02:08 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 01:02:08 -0000 Date: Mon, 2 Nov 2009 20:02:08 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Ivan Voras In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 02:42:56 +0000 Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 01:02:12 -0000 If memory serves me right, sometime around Tomorrow, Ivan Voras told me: > Weldon S Godfrey 3 wrote: > >> I don't know how to troubleshoot this further on the server since I am not >> getting any problems indicated in logging, panics, cores, etc. > > If you have console access to the system, the generic advice would be to > compile a kernel with the kernel debugger - options KDB and DDB (see > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html), > enter the debugger, force a kernel dump file to be created (by entering "call > doadump") and then proceed with post-mortem examination of the kernel at your > leisure (e.g. from a remote ssh console, etc). > > See > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html > for instructions on what information to collect. > > If you can provoke your problem with using WITNESS that would probably be > great, but it will slow down your production machine noticeably. When WITNESS > is enabled you might also get more information - such as LOR warnings, which > you should also collect. > > Keep the dump file, someone might ask you for more information. > Thanks, I will work on trying to get a system with those enabled. Another thought that came to mind that this sounds like some sort of network buffer exhaustion. Is there anything to look for there? From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 01:28:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F10C106566B for ; Tue, 3 Nov 2009 01:28:10 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 816648FC16 for ; Tue, 3 Nov 2009 01:28:10 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 10A258C099; Mon, 2 Nov 2009 19:28:10 -0600 (CST) Date: Mon, 2 Nov 2009 19:28:10 -0600 From: Mark Linimon To: Alexander Best Message-ID: <20091103012810.GB31768@lonesome.com> References: <4AEBFAA3.9020003@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Tue, 03 Nov 2009 02:53:23 +0000 Cc: Dominic Fandrey , freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 01:28:10 -0000 On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: > i guess the freebsd-fs@ guys know about these problems but don't have > the time to deal with it. most of them are probably working on zfs. AFAIK there are only a handful of people working on ZFS. We certainly need more people willing to work on filesystems code. In general it does have a large learning curve, so it's not as attractive as some of the other areas. That's probably why, as the kernel has undergone radical changes (e.g. for SMP) over time, that some of the fs code has not kept up. mcl From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 05:46:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A544F106566B; Tue, 3 Nov 2009 05:46:54 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net [41.161.16.135]) by mx1.freebsd.org (Postfix) with ESMTP id 408738FC24; Tue, 3 Nov 2009 05:46:53 +0000 (UTC) Received: from [41.154.0.10] (helo=clue.co.za) by inbound01.jnb1.gp-online.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1N5CEG-0001S3-C2; Tue, 03 Nov 2009 07:46:52 +0200 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N5CEF-0002fT-Mm; Tue, 03 Nov 2009 07:46:51 +0200 To: Robert Watson From: "Ian Freislich" X-Attribution: BOFH Date: Tue, 03 Nov 2009 07:46:51 +0200 Message-Id: Cc: FreeBSD-Current Subject: Believed fixed (was: Re: Another panic (during netisr?)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 05:46:54 -0000 Robert Watson wrote: > Since debugging this went offline, the quick summary for the list > is: it looks like a race condition in the read-write locking for > tcbinfo in 8.x/9.x was responsible, and I've now committed a fix > to head and merged to stable/8 this morning. If this recurs with > the fix, please let me know, because that would mean we fixed the > wrong bug. :-) Since this I've not had a panic on our routers in the last 25 days. Before, it would panic about every 5 days with a corrupted stack. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 07:07:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76C1C106568D for ; Tue, 3 Nov 2009 07:07:31 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 323108FC15 for ; Tue, 3 Nov 2009 07:07:30 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-162-89.rz.uni-karlsruhe.de [141.3.162.89]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 952398A0D25; Tue, 3 Nov 2009 08:07:29 +0100 (CET) Message-ID: <4AEFD6AE.6020906@bsdforen.de> Date: Tue, 03 Nov 2009 08:07:26 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Gonzalo Nemmi References: <4AEEDCFB.3060604@bsdforen.de> <200911021356.43043.gnemmi@gmail.com> In-Reply-To: <200911021356.43043.gnemmi@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 07:07:31 -0000 Gonzalo Nemmi wrote: > On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: >> It appears that my 8.0-RC2 system (notebook) forgets its mixer >> settings with every reboot. >> >> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct 31 >> 02:49:30 CET 2009 >> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510 >> b-8 amd64 >> >> Regards > > May I ask how are you setting them? > > Regards > Gonzalo With mixer(8). But now the settings are remembered. I suppose some evil app is to blame. But nothing apart from Skype comes to mind and I configured it not to touch the mixer settings. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 08:08:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 938E71065670 for ; Tue, 3 Nov 2009 08:08:16 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 701F48FC1E for ; Tue, 3 Nov 2009 08:08:16 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id BF51C46B09; Tue, 3 Nov 2009 03:08:15 -0500 (EST) Date: Tue, 3 Nov 2009 08:08:15 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ian Freislich In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD-Current Subject: Re: Believed fixed (was: Re: Another panic (during netisr?)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 08:08:16 -0000 On Tue, 3 Nov 2009, Ian Freislich wrote: > Robert Watson wrote: >> Since debugging this went offline, the quick summary for the list is: it >> looks like a race condition in the read-write locking for tcbinfo in >> 8.x/9.x was responsible, and I've now committed a fix to head and merged to >> stable/8 this morning. If this recurs with the fix, please let me know, >> because that would mean we fixed the wrong bug. :-) > > Since this I've not had a panic on our routers in the last 25 days. Before, > it would panic about every 5 days with a corrupted stack. Sounds good, thanks! Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 08:21:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78566106566C for ; Tue, 3 Nov 2009 08:21:44 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7598FC20 for ; Tue, 3 Nov 2009 08:21:43 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=k1cZ69oyAFV370kodyMA:9 a=MkY1mWtJHtE2BHuU797wlEW1D-gA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1320573180; Tue, 03 Nov 2009 09:21:41 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Tue, 3 Nov 2009 09:20:48 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4480d94e7b5662b5a506e2d72bf75f8f.squirrel@cygnus.homeunix.com> In-Reply-To: <4480d94e7b5662b5a506e2d72bf75f8f.squirrel@cygnus.homeunix.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911030920.49134.hselasky@c2i.net> Cc: Nenhum_de_Nos Subject: Re: status on usb/139598 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 08:21:44 -0000 On Monday 02 November 2009 18:25:24 Nenhum_de_Nos wrote: > hail, > > what's the status on this issue ? > > I wrote some bytes in this external usb hdd and now upgraded to 8.0-rc2, > then I can't read them :( > > the other 7.2 box I have is in work, and I'm on vacation starting today :) > > no workarounds ? I must install a 7.2 to read it ? > > thanks, > > matheus Hi, There is no news, beside from: Please check that sys/dev/usb/controller/ehci.c is up to date with 9-current. --HPS From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 08:49:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 506731065676; Tue, 3 Nov 2009 08:49:18 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from s2m-is-001.service2media.com (rev-130-102.virtu.nl [217.114.102.130]) by mx1.freebsd.org (Postfix) with ESMTP id D16AB8FC22; Tue, 3 Nov 2009 08:49:17 +0000 (UTC) Received: from nox-laptop.localnet ([10.0.1.45] RDNS failed) by s2m-is-001.service2media.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Nov 2009 09:37:12 +0100 From: Pieter de Goeje To: freebsd-current@freebsd.org Date: Tue, 3 Nov 2009 09:37:10 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.31-14-generic; KDE/4.3.2; x86_64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911030937.11619.pieter@degoeje.nl> X-OriginalArrivalTime: 03 Nov 2009 08:37:12.0225 (UTC) FILETIME=[D6B48110:01CA5C60] Cc: Weldon S Godfrey 3 , Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 08:49:18 -0000 On Tuesday 03 November 2009 02:02:08 Weldon S Godfrey 3 wrote: > If memory serves me right, sometime around Tomorrow, Ivan Voras told me: > > > Weldon S Godfrey 3 wrote: > > > >> I don't know how to troubleshoot this further on the server since I am not > >> getting any problems indicated in logging, panics, cores, etc. > > > > If you have console access to the system, the generic advice would be to > > compile a kernel with the kernel debugger - options KDB and DDB (see > > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html), > > enter the debugger, force a kernel dump file to be created (by entering "call > > doadump") and then proceed with post-mortem examination of the kernel at your > > leisure (e.g. from a remote ssh console, etc). > > > > See > > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html > > for instructions on what information to collect. > > > > If you can provoke your problem with using WITNESS that would probably be > > great, but it will slow down your production machine noticeably. When WITNESS > > is enabled you might also get more information - such as LOR warnings, which > > you should also collect. > > > > Keep the dump file, someone might ask you for more information. > > > > Thanks, I will work on trying to get a system with those enabled. > > Another thought that came to mind that this sounds like some sort of > network buffer exhaustion. Is there anything to look for there? Are you perhaps using em(4)? There was an mbuf leak in the driver, which was fixed recently. You can check mbuf usage with netstat -m. -- Pieter de Goeje From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 09:52:58 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88DDF1065672 for ; Tue, 3 Nov 2009 09:52:58 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id 078D68FC26 for ; Tue, 3 Nov 2009 09:52:57 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA39qpSZ008885; Tue, 3 Nov 2009 09:52:51 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5G4J-00008L-Nr; Tue, 03 Nov 2009 09:52:51 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA2IGvUb091537; Mon, 2 Nov 2009 18:16:57 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nA2IGvi7091536; Mon, 2 Nov 2009 18:16:57 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Weldon S Godfrey 3 In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 02 Nov 2009 18:16:56 +0000 Message-Id: <1257185816.44755.29.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 09:52:58 -0000 On Mon, 2009-11-02 at 10:52 -0500, Weldon S Godfrey 3 wrote: > Up until yesterday, we have been running FreeBSD-CURRENT of 12/08. We > started to see a couple months ago some very odd network behavior. > Something happens to the stack that causes processes accessing the network > to just hang. After the problem happens, usually (but not always), you > can't ssh in. Always, you can't ssh or telnet out, and nothing can access > the NFS shares on the server. You can ping everything from the server. > You can't even do a route add, you can't ssh if you use just the IP > address (although pinging with hostnames it doesn't have cached or in > hosts table resolves). When you try to ssh out, do a route add from the > box, the process just hangs. You can't control C it at all, it hangs > forever. There is nothing in dmesg or messages to indicate an issue. I > try to up/down the interfaces. In CURRENT-12/08, it may allow things to > work for like 30s. Some things that would be useful: - Does "arp -da" fix things? - What's the output of "netstat -m" while the networking is broken? - What does CTRL-T show for the hung SSH or route processes? - What does "procstat -kk" on the same processes show? - Does going to single user mode ("init 1" and killing off any leftover processes) cause the machine to start working again? If so, what's the output of "netstat -m" afterwards? If you look to be hitting some of the limits shown by "netstat -m", try logging the date, "netstat -m" and "vmstat -m" to a file every 30 seconds or similar so that we can see if it is a memory leak, and what may be leaking. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 10:11:07 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB6EB106568F for ; Tue, 3 Nov 2009 10:11:07 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id 7015D8FC15 for ; Tue, 3 Nov 2009 10:11:07 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA3AAmRg014391; Tue, 3 Nov 2009 10:10:48 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5GLg-0000t2-2S; Tue, 03 Nov 2009 10:10:48 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA3AAlnb099038; Tue, 3 Nov 2009 10:10:47 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nA3AAlCk099037; Tue, 3 Nov 2009 10:10:47 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Rick van der Zwet In-Reply-To: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 03 Nov 2009 10:10:47 +0000 Message-Id: <1257243047.98619.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org, hselasky@FreeBSD.org, freebsd-usb@FreeBSD.org Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 10:11:07 -0000 [freebsd-current cc'd, as that was where the thread started, but this probably belongs on -usb, replies should go there] On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote: > The first net interface of a aue(4) define used to be called aue0 > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no > sign of ue(4) btw). > > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and > freebsd-current@. But I could not find the reason why the naming > convention on this aue differs from the regular stuff, anybody? > > /Rick > > quick# dmesg | tail -8 > ugen1.3: at usbus1 > aue0: on usbus1 > miibus1: on aue0 > ukphy0: PHY 1 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on aue0 > ue0: Ethernet address: 00:00:e8:00:11:36 > ue0: link state changed to DOWN > > quick# ifconfig -l > bfe0 lo0 ue0 Hmm, this looks like a serious bug, possibly in the new USB subsystem (HPS CC'd). I've got an axe(4) device, which also does the same: ugen7.3: at usbus7 axe0: on usbus7 axe0: PHYADDR 0xe0:0x10 miibus1: on axe0 ukphy0: PHY 16 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on axe0 ue0: Ethernet address: 00:50:b6:05:57:a7 ue0: link state changed to DOWN Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 10:43:36 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70B7510656C0 for ; Tue, 3 Nov 2009 10:43:36 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id E12E78FC12 for ; Tue, 3 Nov 2009 10:43:35 +0000 (UTC) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA3Agfuv011908; Tue, 3 Nov 2009 10:42:41 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5GqX-0004hH-Hw; Tue, 03 Nov 2009 10:42:41 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA3AgfAe099536; Tue, 3 Nov 2009 10:42:41 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nA3AgfgD099535; Tue, 3 Nov 2009 10:42:41 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Kai Gallasch In-Reply-To: <20091031231545.493cee89@boiler.free.de> References: <20091031231545.493cee89@boiler.free.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 03 Nov 2009 10:42:40 +0000 Message-Id: <1257244960.98619.36.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 10:43:36 -0000 On Sat, 2009-10-31 at 23:15 +0100, Kai Gallasch wrote: > Hi. > > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > When I try to do a make buildworld or make buildkernel the server > reboots without any message left in the logs. The same happens > when building bigger ports (for example ruby18 or perl58) > > With 8.0-RC2 debug flags and witness seem to be disabled in the > standard GENERIC kernel, so unfortunately it is not possible for me to > build a debug kernel without my server crashing.. First place I think I'd start id by running memtest86 on the machine overnight. This sounds like possible hardware issue to me, it would be good to see if we can confirm that that is the case. > Now my idea was to install the old 8.0-BETA4 and upgrade to RC2 through > makeworld + buildkernel (gdb+witness). But no luck. When trying to > upgrade to RC2 the 8.0-BETA4 also crashes. At least 8.0-BETA4 has debug > + witness active in the GENERIC kernel.. > > So below some debug output of 8.0-BETA4 crashing. Has a vfs/ffs LOR > problem with the BETA4 already been fixed? The debug output you included were just lock order reversals, and don't seem to be related to your crash. I think 8.0-BETA4 still had the debugger compiled in (you can test by pressing ctrl-alt-escape ion the console, if you do drop to the debugger, give the "c" command to continue). If the debugger is compiled in, then the spontaneous reboot without dropping to the debugger suggests even more that it may be hardware related. If you do get to the debugger, a copy of all of the messages on screen and the output of the "bt" command would be very useful. When you do your kernel recompile, please include full debugging, including WITNESS, INVARIANTS, KDB, DDB etc. FWIW, don't worry about building world now, a BETA4 world should work fine with a RC2 kernel. You may be able to get a kernel built even though it keeps crashing by clearing out /usr/obj to start with and then just repeating cd /usr/src && make buildkernel -DKERNFAST after every crash. > Does it make sense to send in a pr with the old 8.0-BETA4? It depends what the bug is to be honest. So far there isn't really enough information to determine the cause, and therefore there isn't really enough info for a PR. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 11:04:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A85A1106568B; Tue, 3 Nov 2009 11:04:17 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe12.swip.net [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id AC4958FC18; Tue, 3 Nov 2009 11:04:16 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UCflARi49IcA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=p6NVgGBU1vQ2caJ32RIA:9 a=OtAmMAkJGGkWUAIKcvUA:7 a=wJlQUFfP-54dsvDomPGtlXuK048A:4 a=Zzef8cBpXGKMt_rX:21 a=zFcG4CBDPOfxa_WF:21 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1144636901; Tue, 03 Nov 2009 12:04:14 +0100 Received-SPF: softfail receiver=mailfe12.swip.net; client-ip=188.126.201.140; envelope-from=hselasky@freebsd.org From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Tue, 3 Nov 2009 12:03:21 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> In-Reply-To: <1257243047.98619.8.camel@buffy.york.ac.uk> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911031203.22103.hselasky@freebsd.org> Cc: Gavin Atkinson , freebsd-current@freebsd.org, Rick van der Zwet Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 11:04:17 -0000 On Tuesday 03 November 2009 11:10:47 Gavin Atkinson wrote: > [freebsd-current cc'd, as that was where the thread started, but this > probably belongs on -usb, replies should go there] > > On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote: > > The first net interface of a aue(4) define used to be called aue0 > > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no > > sign of ue(4) btw). > > > > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and > > freebsd-current@. But I could not find the reason why the naming > > convention on this aue differs from the regular stuff, anybody? > > > > /Rick > > > > quick# dmesg | tail -8 > > ugen1.3: at usbus1 > > aue0: on usbus1 > > miibus1: on aue0 > > ukphy0: PHY 1 on miibus1 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ue0: on aue0 > > ue0: Ethernet address: 00:00:e8:00:11:36 > > ue0: link state changed to DOWN > > > > quick# ifconfig -l > > bfe0 lo0 ue0 > > Hmm, this looks like a serious bug, possibly in the new USB subsystem > (HPS CC'd). > > I've got an axe(4) device, which also does the same: > > ugen7.3: at usbus7 > axe0: on usbus7 > axe0: PHYADDR 0xe0:0x10 > miibus1: on axe0 > ukphy0: PHY 16 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on axe0 > ue0: Ethernet address: 00:50:b6:05:57:a7 > ue0: link state changed to DOWN Hi, All USB ethernet adapters are now named ue0. You will get one axe0 event and one ue0 event. So there should be no problems regarding devd.conf . --HPS From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 11:07:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A833C106566B; Tue, 3 Nov 2009 11:07:14 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id D589B8FC18; Tue, 3 Nov 2009 11:07:12 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UCflARi49IcA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=xzg1ZBY50pbcvyk_5xIA:9 a=aevmJ9JxKSu9oa9zSWWyIwMXj3cA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1339345046; Tue, 03 Nov 2009 12:07:11 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Tue, 3 Nov 2009 12:06:19 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> <200911031203.22103.hselasky@freebsd.org> In-Reply-To: <200911031203.22103.hselasky@freebsd.org> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911031206.19512.hselasky@c2i.net> Cc: Gavin Atkinson , freebsd-usb@freebsd.org, Rick van der Zwet Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 11:07:14 -0000 On Tuesday 03 November 2009 12:03:21 Hans Petter Selasky wrote: > Hi, > > All USB ethernet adapters are now named ue0. You will get one axe0 event > and one ue0 event. So there should be no problems regarding devd.conf . > > --HPS s/ue0/ueN/ --HPS From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 11:38:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DD08106566B for ; Tue, 3 Nov 2009 11:38:28 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from web51804.mail.re2.yahoo.com (web51804.mail.re2.yahoo.com [206.190.38.235]) by mx1.freebsd.org (Postfix) with SMTP id 163C68FC16 for ; Tue, 3 Nov 2009 11:38:27 +0000 (UTC) Received: (qmail 24775 invoked by uid 60001); 3 Nov 2009 11:11:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1257246707; bh=uG9aAEfXsvpwsTZL+let79r1+IkNe10ZpE7naUMs/7M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=Gr4hl8hgpmzeMYPsD5Vs/lbbnsW5r6K5inY4rHPmDdB4hj7vuq/sQ2Vx4NQcWsBOsfcmdzSXH9rkia6fnTpv8IgvAzJOc0kLNFyVND1uAIRGmi8OtRkDgKKUHQAT+2yUFOWBQiW6ulOe1HxE1Z5qZwh7o6aLqaW2gPHlC5KkY+Q= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=bsAqoM46xteZLDRdNr1R0oC5P5RXSNoBWMOgkAK6P1Rxze4uvkxlJcSOOa2qBW5h70c+YCTHdpsQ3lQI24Lg99MknXWyvaU1NvIqVYwdfmd0fNeidpGUcf02H39VDsjjPkSSYTKnLb1yqbJJ41awICGXs+9xmAe7f7C9XfZPyws=; Message-ID: <143477.23789.qm@web51804.mail.re2.yahoo.com> X-YMail-OSG: w9kBAoYVM1mpTXE7xNa6VROp4XihppulMcIfVpGxHVHcToTCpTZdPMTO2XJffy.cLweKIESCbKkeLQFljdSGTkF00whCWF8kmcl8iIknGyrnFmhuDQj_whd0TJCLK54HuWdEPNcG94j6ct9C9BEHsNM4izc6nGnU0An8Rw9SIN4j0mpz1aGKIm30GSHs4dgH2vzIrYvIw2bRKxJRUPcI8pLImz_AUFKaB6Rc.vUBeMhnthm0vorZzks5r4PZaeEqF3yxTgv8q9opmNGOlNXPNOmHJuxhilQlbCyj3Je8HWBwMNZuMmUNno8nkTBoZDJV8keirWaA20TRvnjx3hVZfdD0_iI7B5pBKnxSvGnUKjTQYB0dPHvTehkwUPatPe5SCZVO3gbwYWKj.uXmxY.UTpOdnwTFke551rAfuNds8PqNINq4GwGC5M8js4xfXN10OdjeAwLz8kjxcCpD6YM.6G5DmR83cQIf6M4yCK9lju08lRCHR9U5b0EsrLsdDC382jtDaaLjlpwL6v5JPLs3Uje.Oh5Un3DnxOPOx4JO1qwDJSLZMNeUGb8WvW6WefIav31aZL.Fa0kH7.5CvDh2YjuIDjj1FreaIYebyg-- Received: from [75.158.17.63] by web51804.mail.re2.yahoo.com via HTTP; Tue, 03 Nov 2009 03:11:47 PST X-Mailer: YahooMailRC/211.6 YahooMailWebService/0.7.361.4 Date: Tue, 3 Nov 2009 03:11:47 -0800 (PST) From: PseudoCylon To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Wireless usb + wep = no usbd_do_request X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 11:38:28 -0000 Hi, I'm porting a wireless usb driver (if_run) to freebsd current, and I got stuck. Once I "ifconfig wlan0 wepkey 1:0x... weptxkey 1" I cannot call usbd_do_request() any more. Even ifconfig didn't exit. Chipset supports h/w en/decryption, so cannot write keys on chip. (It works without encryption, by the way.) So, I tried the same thing on another device, linksys wusb54gc with if_rum. It worked fine, but about 3 to 4 min later. (Just left it alone.) It started giving error rum0: could not multi read MAC register: USB_ERR_TIMEOUT and rum0: device timeout when ifconfig wlan0 down, rum0: could not multi write MAC register: USB_ERR_TIMEOUT which means failed on usbd_do_request() (This could be totally different issue.) Any ideas, patches, or walkaround? More info #uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r198150M: Fri Oct 16 22:44:08 UTC 2009 amd64 ddb trace output 20+ minutes after "ifconfig wepkey" (using if_run) Tracing command ifconfig pid 1586 tid 100159 td 0xffffff000b3d3a80 sched_switch() at sched_switch+0x180 mi_switch() at mi_switch+0x21d sleepq_switch() at sleepq_switch+0x123 sleepq_wait() at sleepq_wait+0x4d _sleep() at _sleep+0x357 taskqueue_drain() at taskqueue_drain+0xc2 ieee80211_waitfor_parent() at ieee80211_waitfor_parent+0x3e ieee80211_ioctl() at ieee80211_ioctl+0x162 ifioctl() at ifioctl+0xde4 kern_ioctl() at kern_ioctl+0xc5 ioctl() at ioctl+0xfd syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 Also, sleep mutex became spin mutex. I get a panic panic: mtx_lock of spin mutex(null) It works fine before ifconfig wepkey. __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 12:08:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 835D2106568B for ; Tue, 3 Nov 2009 12:08:49 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id 1A58F8FC17 for ; Tue, 3 Nov 2009 12:08:48 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id d26so860676eyd.9 for ; Tue, 03 Nov 2009 04:08:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=iTBkJ0dRWQ5iTd6CPPFjud6FBzr79F/kwbUtRC+s+2c=; b=d5jNL1v0UwggY5Jor2wFxXU2DWLbkYg/l8YLq/rDh5rdPJMxB5VG3Li23fppyDs5/9 lsrC6APG7HikrYxGhTonvqPkaBWR2Fm9Bm/0DWnN1Ncue9kNtbuglENaAAkJJFyki8np C3nYqOqEKg9gRUncz5Xc5lmy14otgOH4y9eAg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TxrwovCNFez3PKm4Vy4aDpkrqt4CJYYPEwMSMLRnSUaYdDQk9DyvqTtTlkP5eQrpaa sORzkUXms1lAElBII4geRizZR1y/LdIz30C9R6qmTBxBfw11NM9GpgIrekjKyBruiAIh hxAWxuohBp0aAzvSRdLlQmw9yVJxC+Tvlv3XA= MIME-Version: 1.0 Received: by 10.213.23.205 with SMTP id s13mr67335ebb.4.1257250127830; Tue, 03 Nov 2009 04:08:47 -0800 (PST) In-Reply-To: <143477.23789.qm@web51804.mail.re2.yahoo.com> References: <143477.23789.qm@web51804.mail.re2.yahoo.com> Date: Tue, 3 Nov 2009 13:08:47 +0100 Message-ID: <3a142e750911030408t25dd59b0rcda6eccd8c24c0c9@mail.gmail.com> From: Paul B Mahol To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: Wireless usb + wep = no usbd_do_request X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 12:08:49 -0000 On 11/3/09, PseudoCylon wrote: > Hi, > > I'm porting a wireless usb driver (if_run) to freebsd current, and I got > stuck. Once I "ifconfig wlan0 wepkey 1:0x... weptxkey 1" I cannot call > usbd_do_request() any more. Even ifconfig didn't exit. Chipset supports h/w > en/decryption, so cannot write keys on chip. (It works without encryption, > by the way.) > > So, I tried the same thing on another device, linksys wusb54gc with if_rum. > It worked fine, but about 3 to 4 min later. (Just left it alone.) It started > giving error > rum0: could not multi read MAC register: USB_ERR_TIMEOUT and > rum0: device timeout > when ifconfig wlan0 down, > rum0: could not multi write MAC register: USB_ERR_TIMEOUT > which means failed on usbd_do_request() (This could be totally different > issue.) I get this one multiple times after card got detached but vap was not manually destroyed. Recently I did not used if_rum more that 5 min I think(maybe in AP mode when I was testing hidden ssid ...) > Any ideas, patches, or walkaround? Make sure how locks are handled between net80211, usb and driver itself. > More info > #uname -a > FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r198150M: Fri Oct 16 22:44:08 > UTC 2009 amd64 > > ddb trace output 20+ minutes after "ifconfig wepkey" (using if_run) > Tracing command ifconfig pid 1586 tid 100159 td 0xffffff000b3d3a80 > sched_switch() at sched_switch+0x180 > mi_switch() at mi_switch+0x21d > sleepq_switch() at sleepq_switch+0x123 > sleepq_wait() at sleepq_wait+0x4d > _sleep() at _sleep+0x357 > taskqueue_drain() at taskqueue_drain+0xc2 > ieee80211_waitfor_parent() at ieee80211_waitfor_parent+0x3e > ieee80211_ioctl() at ieee80211_ioctl+0x162 > ifioctl() at ifioctl+0xde4 > kern_ioctl() at kern_ioctl+0xc5 > ioctl() at ioctl+0xfd > syscall() at syscall+0x1af > Xfast_syscall() at Xfast_syscall+0xe1 > > Also, sleep mutex became spin mutex. I get a panic > panic: mtx_lock of spin mutex(null) > It works fine before ifconfig wepkey. It is hard to tell without code example but wepkey works fine with if_rum last time I tried, note that if_rum have done encryption in software mode. From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 12:14:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DB50106566C; Tue, 3 Nov 2009 12:14:39 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 8E4798FC1C; Tue, 3 Nov 2009 12:14:38 +0000 (UTC) Received: by bwz5 with SMTP id 5so7686629bwz.3 for ; Tue, 03 Nov 2009 04:14:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=t1BGlaZoVZqa/lCOqCfftCunKf43z0+fdp5NPr4DSFk=; b=jQTUi/tYqEuezPmf1VeRdtKY3K/QfLlE2Ls8LJ8AuH9N0pmJq3cUaQSSVG4bvyNhnA vWHfBD+9rCMSNgrlv5+8It9o9zJiLYSIQRA1FABSsFOuimDFBNx0D/jWng03snL36/gR fnPiBOpj5cc43At8YEwDSJsBABvb3hBaoY7E4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=gw74qTjemKyChmcANIMqOAN0II+pK2kwxQscdypakiALxO85NByt64O4wvFvCnXSpU 6dhSNTh9HrnKGHtEOBFk+B8OINCgffnEAExo1ZTLUm4DsF3LRdOrbckOUvhmztPQ7lSv Wb3oPcDfHHFC/nOQ29c/lgRVjgErxUFLi3U3g= Received: by 10.204.48.140 with SMTP id r12mr1511001bkf.112.1257250477639; Tue, 03 Nov 2009 04:14:37 -0800 (PST) Received: from mac-mini.lan (bl7-30-163.dsl.telepac.pt [85.240.30.163]) by mx.google.com with ESMTPS id 15sm23082bwz.8.2009.11.03.04.14.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Nov 2009 04:14:36 -0800 (PST) Sender: Rui Paulo Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Rui Paulo In-Reply-To: <200911031203.22103.hselasky@freebsd.org> Date: Tue, 3 Nov 2009 12:14:34 +0000 Content-Transfer-Encoding: 7bit Message-Id: References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> <200911031203.22103.hselasky@freebsd.org> To: Hans Petter Selasky X-Mailer: Apple Mail (2.1076) Cc: Rick van der Zwet , Gavin Atkinson , freebsd-usb@freebsd.org, freebsd-current@freebsd.org Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 12:14:39 -0000 On 3 Nov 2009, at 11:03, Hans Petter Selasky wrote: > On Tuesday 03 November 2009 11:10:47 Gavin Atkinson wrote: >> [freebsd-current cc'd, as that was where the thread started, but this >> probably belongs on -usb, replies should go there] >> >> On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote: >>> The first net interface of a aue(4) define used to be called aue0 >>> afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). >>> (no >>> sign of ue(4) btw). >>> >>> I was looking in the UPDATING, man, mailinglists freebsd-usb@ and >>> freebsd-current@. But I could not find the reason why the naming >>> convention on this aue differs from the regular stuff, anybody? >>> >>> /Rick >>> >>> quick# dmesg | tail -8 >>> ugen1.3: at usbus1 >>> aue0: on usbus1 >>> miibus1: on aue0 >>> ukphy0: PHY 1 on miibus1 >>> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>> ue0: on aue0 >>> ue0: Ethernet address: 00:00:e8:00:11:36 >>> ue0: link state changed to DOWN >>> >>> quick# ifconfig -l >>> bfe0 lo0 ue0 >> >> Hmm, this looks like a serious bug, possibly in the new USB subsystem >> (HPS CC'd). >> >> I've got an axe(4) device, which also does the same: >> >> ugen7.3: at usbus7 >> axe0: on usbus7 >> axe0: PHYADDR 0xe0:0x10 >> miibus1: on axe0 >> ukphy0: PHY 16 on miibus1 >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on axe0 >> ue0: Ethernet address: 00:50:b6:05:57:a7 >> ue0: link state changed to DOWN > > Hi, > > All USB ethernet adapters are now named ue0. You will get one axe0 > event and > one ue0 event. So there should be no problems regarding devd.conf . Fair enough, but this must be mentioned in src/UPDATING. -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 12:45:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29579106566B for ; Tue, 3 Nov 2009 12:45:09 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-gx0-f218.google.com (mail-gx0-f218.google.com [209.85.217.218]) by mx1.freebsd.org (Postfix) with ESMTP id D3CA88FC13 for ; Tue, 3 Nov 2009 12:45:08 +0000 (UTC) Received: by gxk10 with SMTP id 10so2851583gxk.3 for ; Tue, 03 Nov 2009 04:45:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=EQzurEtJZcCYl0o0qBXPtWlnXp+8j+DZR00TEEdRKqc=; b=KIrPnG9rjDRFhA7tbLJiiClg68QDMA3sEYoNsyzp082Usk2AxFLH2CKyleO6tnhEw4 7AwxVBTtyBfTSpNkO6PUeWugWfyvxIpN7XLB3Q/ilwBL1/8M7bdxkzkm9cmYNpn6l1UK D9p/0X4hnkFd95y/OInMoG000+fmgH7zWEEbU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=N0ngv79qUz6uz/xtNPCr3jtTT2+Jetmc4H9gPzXH6NY02xLak+6Fpafwa08X+embGM 78Dcd8Z6qBz9xgKvGnfqW9p4SRq1Yb+6q5nP2wXiYSZSe5b7YXFDhFizgngtSDLQTDZR S+3s369BCl49UWM/I3EMcn+eHbY1EO0L6dKWQ= Received: by 10.91.28.2 with SMTP id f2mr141598agj.16.1257252307977; Tue, 03 Nov 2009 04:45:07 -0800 (PST) Received: from ?192.168.1.100? ([190.177.224.62]) by mx.google.com with ESMTPS id 22sm21102yxe.39.2009.11.03.04.45.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Nov 2009 04:45:07 -0800 (PST) From: Gonzalo Nemmi To: freebsd-current@freebsd.org Date: Tue, 3 Nov 2009 10:45:03 -0200 User-Agent: KMail/1.9.10 References: <4AEEDCFB.3060604@bsdforen.de> <200911021356.43043.gnemmi@gmail.com> <4AEFD6AE.6020906@bsdforen.de> In-Reply-To: <4AEFD6AE.6020906@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911031045.03823.gnemmi@gmail.com> Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 12:45:09 -0000 On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: > Gonzalo Nemmi wrote: > > On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > >> It appears that my 8.0-RC2 system (notebook) forgets its mixer > >> settings with every reboot. > >> > >> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct > >> 31 02:49:30 CET 2009 > >> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 > >>510 b-8 amd64 > >> > >> Regards > > > > May I ask how are you setting them? > > > > Regards > > Gonzalo > > With mixer(8). But now the settings are remembered. > > I suppose some evil app is to blame. But nothing apart from Skype > comes to mind and I configured it not to touch the mixer settings. > > Regards Sorry but I have to ask ... have you tried configuring mixer settings as described in section 7.2.4 of the FreBSD handbook? That is to say: "The default values for the different mixer channels are hardcoded in the sourcecode of the pcm(4) driver. There are many different applications and daemons that allow you to set values for the mixer that are remembered between invocations, but this is not a clean solution. It is possible to set default mixer values at the driver level -- this is accomplished by defining the appropriate values in /boot/device.hints, e.g.: hint.pcm.0.vol="50" This will set the volume channel to a default value of 50 when the pcm(4) module is loaded." because that works for me :s Best Regards Gonzalo From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 12:45:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB7501065693 for ; Tue, 3 Nov 2009 12:45:33 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7D54A8FC08 for ; Tue, 3 Nov 2009 12:45:33 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 8A12A6D41B; Tue, 3 Nov 2009 12:45:32 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 5D63A84503; Tue, 3 Nov 2009 13:45:32 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Dominic Fandrey References: <4AEEDCFB.3060604@bsdforen.de> <86fx8xm4u0.fsf@ds4.des.no> <4AEEF6F4.2080904@bsdforen.de> Date: Tue, 03 Nov 2009 13:45:32 +0100 In-Reply-To: <4AEEF6F4.2080904@bsdforen.de> (Dominic Fandrey's message of "Mon, 02 Nov 2009 16:12:52 +0100") Message-ID: <86r5sfn5eb.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 12:45:33 -0000 Dominic Fandrey writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Check the contents of /var/db/*-state. > Thanks for the pointer. Is that updated during shutdown or > every time the mixer settings are changed? During shutdown. > Sounds sensible to me. Ever wrote a PR? Not in about ten years... > Is there a manual page with in depth information? mixer(8) doesn't > mention the mixerX-state files. /etc/rc.d/mixer DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 13:36:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 851071065695 for ; Tue, 3 Nov 2009 13:36:48 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id 15B168FC16 for ; Tue, 3 Nov 2009 13:36:47 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id d26so880155eyd.9 for ; Tue, 03 Nov 2009 05:36:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=vzGy4jSW5btpgYwfdyGtMsKw1c7HLlcQsAnhgSk3O3I=; b=EpegzTaKLzxAXpniXxPNr/BlyzWillt2VWBOjzT/+YgLMMguNClBdROze+WGahM4Xi Os9ekWjqeaAvZrcbMKqsa8BA87yCPW4+SQFv5JCryRSVyI1ZaqZCZuoAVWJZdbd/sTLA SpFDMwCDUheoBchpEWxNXAYuaZdKfhf7oqQAw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=LiNMSFDxStsezS3TsAjC7+SBknt8XeaoFEe8EyhkrrxG2mCnPxmIVP+2AmNb6DEoz4 I5VLyTyhzawtptg/p4Kv9GrcS6YTsh+iB2cRhMwhpdMpDucySZ0EIKYOBuR1QNtQfYtK lcPTbxq8CsDg0xTiIVwri6x3+Nq/H0EuALOdA= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.86.131 with SMTP id w3mr6351254wee.156.1257255407166; Tue, 03 Nov 2009 05:36:47 -0800 (PST) In-Reply-To: References: <200911030937.11619.pieter@degoeje.nl> From: Ivan Voras Date: Tue, 3 Nov 2009 14:36:27 +0100 X-Google-Sender-Auth: 3c6f69ea042f07e7 Message-ID: <9bbcef730911030536p5707fc2fg7228eb69b729b288@mail.gmail.com> To: Weldon S Godfrey 3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Pieter de Goeje , freebsd-current@freebsd.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 13:36:48 -0000 2009/11/3 Weldon S Godfrey 3 : > > > If memory serves me right, sometime around 9:37am, Pieter de Goeje told m= e: > >> Are you perhaps using em(4)? There was an mbuf leak in the driver, which >> was fixed recently. >> You can check mbuf usage with netstat -m. >> > > we are using onboard NICs on the Dell using the bce driver. =C2=A0We did = try > several times to see if using an intel PCIexpress card using the em drive= r, > and we had the same symptoms. > > Could the bce driver have the same leak? It would be unlikely to pass unnoticed since Dells are common hardware... From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 13:32:26 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04BB81065679 for ; Tue, 3 Nov 2009 13:32:26 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id 87FE18FC29 for ; Tue, 3 Nov 2009 13:32:25 +0000 (UTC) Received: (qmail 47187 invoked by uid 89); 3 Nov 2009 13:32:24 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 13:32:24 -0000 Date: Tue, 3 Nov 2009 08:32:24 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Gavin Atkinson In-Reply-To: <1257185816.44755.29.camel@buffy.york.ac.uk> Message-ID: References: <1257185816.44755.29.camel@buffy.york.ac.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 14:05:39 +0000 Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 13:32:26 -0000 If memory serves me right, sometime around Yesterday, Gavin Atkinson told me: Gavin, thank you A LOT for helping us with this, I have answered as much as I can from the most recent crash below. We did hit max mbufs. It is at 25Kclusters, which is the default. I have upped it to 32K because a rather old article mentioned that as the top end and I need to get into work so I am not trying to do this with a remote console to go higher. I have already set it to reboot next with 64K clusters. I already have kmem maxed to what is bootable (or at least at one time) in 8.0, 4GB, how high can I safely go? This is a NFS server running ZFS with sustained 5 min averages of 120-200Mb/s running as a store for a mail system. > Some things that would be useful: > > - Does "arp -da" fix things? no, it hangs like ssh, route add, etc > - What's the output of "netstat -m" while the networking is broken? Tue Nov 3 07:02:11 CST 2009 36971/2033/39004 mbufs in use (current/cache/total) 24869/731/25600/25600 mbuf clusters in use (current/cache/total/max) 24314/731 mbuf+clusters out of packet secondary zone in use (current/cache) 0/35/35/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 58980K/2110K/61091K bytes allocated to network (current/cache/total) 0/201276/90662 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines > - What does CTRL-T show for the hung SSH or route processes? of the arp: load: 0.01 cmd: arp 6144 [zonelimit] 0.00u 0.00s 0% 996k > - What does "procstat -kk" on the same processes show? sorry I couldn't get this to run this time, remote console issues > - Does going to single user mode ("init 1" and killing off any leftover > processes) cause the machine to start working again? If so, what's the > output of "netstat -m" afterwards? no, mbuf was still maxed out below is the last vmstat -m Type InUse MemUse HighUse Requests Size(s) ntfs_nthash 1 512K - 1 pfs_nodes 20 5K - 20 256 GEOM 262 52K - 4551 16,32,64,128,256,512,1024,2048 isadev 9 2K - 9 128 cdev 13 4K - 13 256 sigio 1 1K - 1 64 filedesc 127 64K - 6412 512,1024 kenv 75 11K - 80 16,32,64,128 kqueue 0 0K - 188 256,2048 proc-args 41 2K - 5647 16,32,64,128 scsi_cd 0 0K - 333 16 ithread 119 21K - 119 32,128,256 acpica 888 78K - 121045 16,32,64,128,256,512,1024 KTRACE 100 13K - 100 128 acpitask 0 0K - 1 64 linker 139 596K - 181 16,32,64,128,256,512,1024,2048 lockf 11 2K - 399 64,128 CAM dev queue 4 1K - 4 128 ip6ndp 5 1K - 5 64,128 temp 48 562K - 14544952 16,32,64,128,256,512,1024,2048,4096 devbuf 17105 36341K - 24988 16,32,64,128,512,1024,2048,4096 module 420 53K - 420 128 mtx_pool 1 8K - 1 osd 2 1K - 2 16 CAM queue 62 52K - 2211 16,32,64,128,256,512,1024,2048 subproc 562 722K - 6851 512,4096 proc 2 16K - 2 session 33 5K - 127 128 pgrp 37 5K - 190 128 cred 62 16K - 29192756 256 uidinfo 4 3K - 99 64,2048 plimit 17 5K - 910 256 acpisem 15 1K - 15 64 sysctltmp 0 0K - 13867 16,32,64,128,256,512,1024,2048,4096 sysctloid 5400 270K - 5782 16,32,64,128 sysctl 0 0K - 11423 16,32,64 callout 7 3584K - 7 umtx 780 98K - 780 128 p1003.1b 1 1K - 1 16 SWAP 2 3281K - 2 64 kbdmux 8 9K - 8 16,256,512,2048,4096 bus-sc 103 188K - 4558 16,32,64,128,256,512,1024,2048,4096 bus 1174 93K - 57792 16,32,64,128,256,512,1024 clist 54 7K - 54 128 devstat 32 65K - 32 32,4096 eventhandler 64 6K - 64 64,128 kobj 276 1104K - 387 4096 rman 144 18K - 601 16,32,128 mfibuf 3 21K - 12 32,256,512,2048,4096 sbuf 0 0K - 14350 16,32,64,128,256,512,1024,2048,4096 scsi_da 0 0K - 504 16 CAM SIM 4 1K - 4 256 stack 0 0K - 194 256 taskqueue 13 2K - 13 16,32,128 Unitno 11 1K - 4759 32,64 iov 0 0K - 1193 16,64,256,512 select 98 13K - 98 128 ioctlops 0 0K - 14716 16,32,64,128,256,512,1024,4096 msg 4 30K - 4 2048,4096 sem 4 8K - 4 512,1024,2048,4096 shm 1 16K - 1 tty 25 25K - 25 1024 pts 3 1K - 3 256 mbuf_tag 0 0K - 2 32 shmfd 1 8K - 1 CAM periph 54 14K - 371 16,32,64,128,256 pcb 28 157K - 148 16,32,128,1024,2048,4096 soname 5 1K - 18699 16,32,128 biobuf 4 8K - 6 2048 vfscache 1 1024K - 1 cl_savebuf 0 0K - 7 64,128 export_host 5 3K - 5 512 vfs_hash 1 512K - 1 vnodes 2 1K - 2 256 vnodemarker 0 0K - 4832 512 mount 222 15K - 807 16,32,64,128,256,1024 ata_generic 1 1K - 1 1024 BPF 4 1K - 4 128 ether_multi 22 2K - 24 16,32,64 ifaddr 54 14K - 54 32,64,128,256,512,4096 ifnet 5 9K - 5 256,2048 clone 5 20K - 5 4096 arpcom 3 1K - 3 16 routetbl 65 11K - 949 32,64,128,256,512 in_multi 3 1K - 3 64 sctp_iter 0 0K - 3 256 sctp_ifn 3 1K - 3 128 sctp_ifa 4 1K - 4 128 sctp_vrf 1 1K - 1 64 sctp_a_it 0 0K - 3 16 hostcache 1 28K - 1 acd_driver 1 2K - 1 2048 syncache 1 92K - 1 in6_multi 19 2K - 19 32,64,128 ip6_moptions 1 1K - 1 32 NFS FHA 13 3K - 18480347 64,2048 rpc 1381 716K - 82214178 32,64,128,256,512,2048 audit_evclass 168 6K - 205 32 newblk 1 1K - 1 512 inodedep 1 512K - 1 pagedep 1 128K - 1 ufs_dirhash 45 9K - 45 16,32,64,128,512 ufs_mount 3 11K - 3 512,2048 UMAHash 3 130K - 12 512,1024,2048,4096 acpidev 56 4K - 56 64 vm_pgdata 2 129K - 2 128 CAM XPT 589 369K - 2047 32,64,128,256,1024 io_apic 2 4K - 2 2048 pci_link 16 2K - 16 32,128 memdesc 1 4K - 1 4096 msi 3 1K - 3 128 nexusdev 3 1K - 3 16 entropy 1024 64K - 1024 64 twa_commands 2 104K - 101 256 atkbddev 2 1K - 2 64 UART 6 4K - 6 16,512,1024 USBHC 1 1K - 1 128 USBdev 30 11K - 30 16,32,64,128,256,512 USB 157 54K - 190 16,32,64,128,256,1024 DEVFS1 152 76K - 153 512 DEVFS3 165 42K - 167 256 DEVFS 16 1K - 17 16,128 solaris 822038 707024K - 235790398 16,32,64,128,256,512,1024,2048,4096 kstat_data 2 1K - 2 64 From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 14:05:26 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5593106566C for ; Tue, 3 Nov 2009 14:05:26 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 830928FC08 for ; Tue, 3 Nov 2009 14:05:26 +0000 (UTC) Received: from bb.ipt.ru ([194.62.233.89]) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1N5K0V-000ANU-FM for freebsd-current@FreeBSD.org; Tue, 03 Nov 2009 17:05:11 +0300 To: freebsd-current@FreeBSD.org From: Boris Samorodov Date: Tue, 03 Nov 2009 17:05:11 +0300 Message-ID: <65275688@bb.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 14:05:26 -0000 Hello List, print/acroread8 doesn't work for me at 9-CURRENT: ----- % uname -a FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15:15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST % sysctl compat.linux compat.linux.oss_version: 198144 compat.linux.osrelease: 2.6.16 compat.linux.osname: Linux ------ Setting security.bsd.map_at_zero to 1 doesn't change anything. There is nothing at console/log files. Here is the tail of linux_kdump: ----- ... 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" 78586 ld-2.9.so RET linux_open JUSTRETURN 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" 78586 ld-2.9.so RET linux_open 4 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) 78586 ld-2.9.so RET linux_fstat64 0 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) 78586 ld-2.9.so GIO fd 4 read 96 bytes "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^[b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" 78586 ld-2.9.so RET read 96/0x60 78586 ld-2.9.so CALL close(0x4) 78586 ld-2.9.so RET close 0 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 78586 ld-2.9.so PSIG SIGSEGV caught handler=0x83814b6 mask=0x0 code=0x0 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0x8) 78586 ld-2.9.so RET linux_rt_sigaction 0 78586 ld-2.9.so CALL linux_exit_group(0x1) ----- -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 13:35:20 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 178391065692 for ; Tue, 3 Nov 2009 13:35:20 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id A25458FC2D for ; Tue, 3 Nov 2009 13:35:19 +0000 (UTC) Received: (qmail 47528 invoked by uid 89); 3 Nov 2009 13:35:17 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 13:35:17 -0000 Date: Tue, 3 Nov 2009 08:35:17 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Pieter de Goeje In-Reply-To: <200911030937.11619.pieter@degoeje.nl> Message-ID: References: <200911030937.11619.pieter@degoeje.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 14:11:03 +0000 Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 13:35:20 -0000 If memory serves me right, sometime around 9:37am, Pieter de Goeje told me: > Are you perhaps using em(4)? There was an mbuf leak in the driver, which was fixed recently. > You can check mbuf usage with netstat -m. > we are using onboard NICs on the Dell using the bce driver. We did try several times to see if using an intel PCIexpress card using the em driver, and we had the same symptoms. Could the bce driver have the same leak? Thanks! Weldon From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 14:18:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E30E310656E8 for ; Tue, 3 Nov 2009 14:18:52 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pz0-f202.google.com (mail-pz0-f202.google.com [209.85.222.202]) by mx1.freebsd.org (Postfix) with ESMTP id AD8678FC15 for ; Tue, 3 Nov 2009 14:18:52 +0000 (UTC) Received: by pzk40 with SMTP id 40so3911663pzk.7 for ; Tue, 03 Nov 2009 06:18:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=+ZoD3Y7x4x9lh8D3c1qHOGr5lVZ8+z7AWOQp/Z9hu+U=; b=iyonov68VhdUoNKkXgrZ2ge9a90zqLMKet2a86RosYrLCLC06TVu4s9kPJV99hWpRN RukVwxyDKl7XqllIrWm1uApZuIB5vGRUsDtpynC55N8T40R3SmWhDFwiZbccE7L9j9Gg 4VM3HOo37kH9GF88JVWQN1h8BOjeDsZmVF0mc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bVt8ihPErvetItLkWKxASgoiafTTQzv0kzhvEpaDgrudlidyrzvG3ypzsQ/kBtbh/9 ec9rjl47gnRvPgPC/YnO/dngEmjiUYuik4sIwRDpI5T0PO1TnPXxfm3+KDYSOTRxsWso jjoqDsE4wBrdFMkjKMgZ/+nZHwFxSrum2ONq0= MIME-Version: 1.0 Received: by 10.142.60.8 with SMTP id i8mr477wfa.310.1257257932297; Tue, 03 Nov 2009 06:18:52 -0800 (PST) In-Reply-To: References: <1257185816.44755.29.camel@buffy.york.ac.uk> Date: Tue, 3 Nov 2009 08:18:52 -0600 Message-ID: <6201873e0911030618u3984a7c1hc05331b0021f796f@mail.gmail.com> From: Adam Vande More To: Weldon S Godfrey 3 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Gavin Atkinson , freebsd-current@freebsd.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 14:18:53 -0000 On Tue, Nov 3, 2009 at 7:32 AM, Weldon S Godfrey 3 wrote: > > > If memory serves me right, sometime around Yesterday, Gavin Atkinson told > me: > > Gavin, thank you A LOT for helping us with this, I have answered as much as > I can from the most recent crash below. We did hit max mbufs. It is at > 25Kclusters, which is the default. I have upped it to 32K because a rather > old article mentioned that as the top end and I need to get into work so I > am not trying to do this with a remote console to go higher. I have already > set it to reboot next with 64K clusters. I already have kmem maxed to what > is bootable (or at least at one time) in 8.0, 4GB, how high can I safely go? > This is a NFS server running ZFS with sustained 5 min averages of > 120-200Mb/s running as a store for a mail system. > > > Some things that would be useful: >> >> - Does "arp -da" fix things? >> > > no, it hangs like ssh, route add, etc > > > - What's the output of "netstat -m" while the networking is broken? >> > Tue Nov 3 07:02:11 CST 2009 > 36971/2033/39004 mbufs in use (current/cache/total) > 24869/731/25600/25600 mbuf clusters in use (current/cache/total/max) > 24314/731 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/35/35/12800 4k (page size) jumbo clusters in use > (current/cache/total/max) > 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) > 58980K/2110K/61091K bytes allocated to network (current/cache/total) > 0/201276/90662 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/0/0 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > > > - What does CTRL-T show for the hung SSH or route processes? >> > > of the arp: > load: 0.01 cmd: arp 6144 [zonelimit] 0.00u 0.00s 0% 996k > > > - What does "procstat -kk" on the same processes show? >> > sorry I couldn't get this to run this time, remote console issues > > > - Does going to single user mode ("init 1" and killing off any leftover >> processes) cause the machine to start working again? If so, what's the >> output of "netstat -m" afterwards? >> > > no, mbuf was still maxed out > > > below is the last vmstat -m Type InUse MemUse HighUse Requests > Size(s) > ntfs_nthash 1 512K - 1 > pfs_nodes 20 5K - 20 256 > GEOM 262 52K - 4551 16,32,64,128,256,512,1024,2048 > isadev 9 2K - 9 128 > cdev 13 4K - 13 256 > sigio 1 1K - 1 64 > filedesc 127 64K - 6412 512,1024 > kenv 75 11K - 80 16,32,64,128 > kqueue 0 0K - 188 256,2048 > proc-args 41 2K - 5647 16,32,64,128 > scsi_cd 0 0K - 333 16 > ithread 119 21K - 119 32,128,256 > acpica 888 78K - 121045 16,32,64,128,256,512,1024 > KTRACE 100 13K - 100 128 > acpitask 0 0K - 1 64 > linker 139 596K - 181 16,32,64,128,256,512,1024,2048 > lockf 11 2K - 399 64,128 > CAM dev queue 4 1K - 4 128 > ip6ndp 5 1K - 5 64,128 > temp 48 562K - 14544952 > 16,32,64,128,256,512,1024,2048,4096 > devbuf 17105 36341K - 24988 16,32,64,128,512,1024,2048,4096 > module 420 53K - 420 128 > mtx_pool 1 8K - 1 > osd 2 1K - 2 16 > CAM queue 62 52K - 2211 16,32,64,128,256,512,1024,2048 > subproc 562 722K - 6851 512,4096 > proc 2 16K - 2 > session 33 5K - 127 128 > pgrp 37 5K - 190 128 > cred 62 16K - 29192756 256 > uidinfo 4 3K - 99 64,2048 > plimit 17 5K - 910 256 > acpisem 15 1K - 15 64 > sysctltmp 0 0K - 13867 > 16,32,64,128,256,512,1024,2048,4096 > sysctloid 5400 270K - 5782 16,32,64,128 > sysctl 0 0K - 11423 16,32,64 > callout 7 3584K - 7 > umtx 780 98K - 780 128 > p1003.1b 1 1K - 1 16 > SWAP 2 3281K - 2 64 > kbdmux 8 9K - 8 16,256,512,2048,4096 > bus-sc 103 188K - 4558 > 16,32,64,128,256,512,1024,2048,4096 > bus 1174 93K - 57792 16,32,64,128,256,512,1024 > clist 54 7K - 54 128 > devstat 32 65K - 32 32,4096 > eventhandler 64 6K - 64 64,128 > kobj 276 1104K - 387 4096 > rman 144 18K - 601 16,32,128 > mfibuf 3 21K - 12 32,256,512,2048,4096 > sbuf 0 0K - 14350 > 16,32,64,128,256,512,1024,2048,4096 > scsi_da 0 0K - 504 16 > CAM SIM 4 1K - 4 256 > stack 0 0K - 194 256 > taskqueue 13 2K - 13 16,32,128 > Unitno 11 1K - 4759 32,64 > iov 0 0K - 1193 16,64,256,512 > select 98 13K - 98 128 > ioctlops 0 0K - 14716 16,32,64,128,256,512,1024,4096 > msg 4 30K - 4 2048,4096 > sem 4 8K - 4 512,1024,2048,4096 > shm 1 16K - 1 > tty 25 25K - 25 1024 > pts 3 1K - 3 256 > mbuf_tag 0 0K - 2 32 > shmfd 1 8K - 1 > CAM periph 54 14K - 371 16,32,64,128,256 > pcb 28 157K - 148 16,32,128,1024,2048,4096 > soname 5 1K - 18699 16,32,128 > biobuf 4 8K - 6 2048 > vfscache 1 1024K - 1 > cl_savebuf 0 0K - 7 64,128 > export_host 5 3K - 5 512 > vfs_hash 1 512K - 1 > vnodes 2 1K - 2 256 > vnodemarker 0 0K - 4832 512 > mount 222 15K - 807 16,32,64,128,256,1024 > ata_generic 1 1K - 1 1024 > BPF 4 1K - 4 128 > ether_multi 22 2K - 24 16,32,64 > ifaddr 54 14K - 54 32,64,128,256,512,4096 > ifnet 5 9K - 5 256,2048 > clone 5 20K - 5 4096 > arpcom 3 1K - 3 16 > routetbl 65 11K - 949 32,64,128,256,512 > in_multi 3 1K - 3 64 > sctp_iter 0 0K - 3 256 > sctp_ifn 3 1K - 3 128 > sctp_ifa 4 1K - 4 128 > sctp_vrf 1 1K - 1 64 > sctp_a_it 0 0K - 3 16 > hostcache 1 28K - 1 > acd_driver 1 2K - 1 2048 > syncache 1 92K - 1 > in6_multi 19 2K - 19 32,64,128 > ip6_moptions 1 1K - 1 32 > NFS FHA 13 3K - 18480347 64,2048 > rpc 1381 716K - 82214178 32,64,128,256,512,2048 > audit_evclass 168 6K - 205 32 > newblk 1 1K - 1 512 > inodedep 1 512K - 1 > pagedep 1 128K - 1 > ufs_dirhash 45 9K - 45 16,32,64,128,512 > ufs_mount 3 11K - 3 512,2048 > UMAHash 3 130K - 12 512,1024,2048,4096 > acpidev 56 4K - 56 64 > vm_pgdata 2 129K - 2 128 > CAM XPT 589 369K - 2047 32,64,128,256,1024 > io_apic 2 4K - 2 2048 > pci_link 16 2K - 16 32,128 > memdesc 1 4K - 1 4096 > msi 3 1K - 3 128 > nexusdev 3 1K - 3 16 > entropy 1024 64K - 1024 64 > twa_commands 2 104K - 101 256 > atkbddev 2 1K - 2 64 > UART 6 4K - 6 16,512,1024 > USBHC 1 1K - 1 128 > USBdev 30 11K - 30 16,32,64,128,256,512 > USB 157 54K - 190 16,32,64,128,256,1024 > DEVFS1 152 76K - 153 512 > DEVFS3 165 42K - 167 256 > DEVFS 16 1K - 17 16,128 > solaris 822038 707024K - 235790398 > 16,32,64,128,256,512,1024,2048,4096 > kstat_data 2 1K - 2 64 > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > from man tuning: kern.ipc.nmbclusters may be adjusted to increase the number of network mbufs the system is willing to allocate. Each cluster represents approx- imately 2K of memory, so a value of 1024 represents 2M of kernel memory reserved for network buffers. You can do a simple calculation to figure out how many you need. If you have a web server which maxes out at 1000 simultaneous connections, and each connection eats a 16K receive and 16K send buffer, you need approximately 32MB worth of network buffers to deal with it. A good rule of thumb is to multiply by 2, so 32MBx2 = 64MB/2K = 32768. So for this case you would want to set kern.ipc.nmbclusters to 32768. We recommend values between 1024 and 4096 for machines with mod- erates amount of memory, and between 4096 and 32768 for machines with greater amounts of memory. Under no circumstances should you specify an arbitrarily high value for this parameter, it could lead to a boot-time crash. The -m option to netstat(1) may be used to observe network clus- ter use. Older versions of FreeBSD do not have this tunable and require that the kernel config(8) option NMBCLUSTERS be set instead. More and more programs are using the sendfile(2) system call to transmit files over the network. The kern.ipc.nsfbufs sysctl controls the number of file system buffers sendfile(2) is allowed to use to perform its work. This parameter nominally scales with kern.maxusers so you should not need to modify this parameter except under extreme circumstances. See the TUNING section in the sendfile(2) manual page for details. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 14:28:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D14C106568F for ; Tue, 3 Nov 2009 14:28:56 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id DF9118FC12 for ; Tue, 3 Nov 2009 14:28:55 +0000 (UTC) Received: from desktop1.yuno ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N5KRu-000K3W-0g; Tue, 03 Nov 2009 14:33:30 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Mark Linimon" , "Alexander Best" References: <4AEBFAA3.9020003@bsdforen.de> <20091103012810.GB31768@lonesome.com> Date: Tue, 03 Nov 2009 14:28:40 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Message-ID: In-Reply-To: <20091103012810.GB31768@lonesome.com> User-Agent: Opera Mail/10.00 (FreeBSD) Cc: Dominic Fandrey , freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 14:28:56 -0000 As an example, this is a 1GB fat32 disk. da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) desktop1# ls /dev | grep da0~ desktop1# ls /dev | grep da0 da0 desktop1# fdisk /dev/da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 114 (0x72),(unknown) start 778135908, size 1141509631 (557377 Meg), flag 6f beg: cyl 357/ head 116/ sector 40; end: cyl 357/ head 32/ sector 45 The data for partition 2 is: sysid 101 (0x65),(Novell Netware/386 3.xx) start 168689522, size 1936028240 (945326 Meg), flag 69 beg: cyl 288/ head 115/ sector 43; end: cyl 367/ head 114/ sector 50 The data for partition 3 is: sysid 121 (0x79),(QNX4.x 3rd part) start 1869881465, size 1936028192 (945326 Meg), flag 73 beg: cyl 366/ head 32/ sector 33; end: cyl 357/ head 32/ sector 43 The data for partition 4 is: sysid 13 (0x0d),(unknown) start 0, size 3637226496 (1775989 Meg), flag 74 beg: cyl 372/ head 97/ sector 50; end: cyl 0/ head 10/ sector 0 desktop1# On Tue, 03 Nov 2009 01:28:10 -0000, Mark Linimon wrote: > On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: >> i guess the freebsd-fs@ guys know about these problems but don't have >> the time to deal with it. most of them are probably working on zfs. > > AFAIK there are only a handful of people working on ZFS. > > We certainly need more people willing to work on filesystems code. In > general it does have a large learning curve, so it's not as attractive > as some of the other areas. That's probably why, as the kernel has > undergone radical changes (e.g. for SMP) over time, that some of the > fs code has not kept up. > > mcl > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 15:13:55 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DBE7106566C for ; Tue, 3 Nov 2009 15:13:55 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id E23678FC13 for ; Tue, 3 Nov 2009 15:13:54 +0000 (UTC) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA3FDf7V029586; Tue, 3 Nov 2009 15:13:41 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5L4m-0005Vo-RE; Tue, 03 Nov 2009 15:13:40 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA3FDZZt002132; Tue, 3 Nov 2009 15:13:35 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nA3FDYiA002131; Tue, 3 Nov 2009 15:13:34 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Weldon S Godfrey 3 In-Reply-To: References: <1257185816.44755.29.camel@buffy.york.ac.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 03 Nov 2009 15:13:34 +0000 Message-Id: <1257261214.98619.92.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:13:55 -0000 On Tue, 2009-11-03 at 08:32 -0500, Weldon S Godfrey 3 wrote: > > If memory serves me right, sometime around Yesterday, Gavin Atkinson told me: > > Gavin, thank you A LOT for helping us with this, I have answered as much > as I can from the most recent crash below. We did hit max mbufs. It is > at 25Kclusters, which is the default. I have upped it to 32K because a > rather old article mentioned that as the top end and I need to get into > work so I am not trying to do this with a remote console to go higher. I > have already set it to reboot next with 64K clusters. I already have kmem > maxed to what is bootable (or at least at one time) in 8.0, 4GB, how high > can I safely go? This is a NFS server running ZFS with sustained 5 min > averages of 120-200Mb/s running as a store for a mail system. > > > Some things that would be useful: > > > > - Does "arp -da" fix things? > > no, it hangs like ssh, route add, etc > > > - What's the output of "netstat -m" while the networking is broken? > Tue Nov 3 07:02:11 CST 2009 > 36971/2033/39004 mbufs in use (current/cache/total) > 24869/731/25600/25600 mbuf clusters in use (current/cache/total/max) > 24314/731 mbuf+clusters out of packet secondary zone in use > (current/cache) > 0/35/35/12800 4k (page size) jumbo clusters in use > (current/cache/total/max) > 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) > 58980K/2110K/61091K bytes allocated to network (current/cache/total) > 0/201276/90662 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/0/0 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines OK, at least we've figured out what is going wrong then. As a workaround to get the machine to stay up longer, you should be able to set kern.ipc.nmbclusters=256000 in /boot/loader.conf -but hopefully we can resolve this soon. Firstly, what kernel was the above output from? And what network card are you using? In your initial post you mentioned testing both bce(4) and em(4) cards, be aware that em(4) had an issue that would cause exactly this issue, which was fixed with a commit on September 11th (r197093). Make sure your kernel is from after that date if you are using em(4). I guess it is also possible that bce(4) has the same issue, I'm not aware of any fixes to it recently. So, from here, I think the best thing would be to just use the em(4) NIC and an up-to-date kernel, and see if you can reproduce the issue. How important is this machine? If em(4) works, are you able to help debug the issues with the bce(4) driver? Thanks, Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 15:47:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C3D610656C3 for ; Tue, 3 Nov 2009 15:47:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 1FAB58FC24 for ; Tue, 3 Nov 2009 15:47:52 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA3Fll0N031781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Nov 2009 17:47:47 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA3FllAa033488; Tue, 3 Nov 2009 17:47:47 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA3FllrP033487; Tue, 3 Nov 2009 17:47:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 3 Nov 2009 17:47:47 +0200 From: Kostik Belousov To: Boris Samorodov Message-ID: <20091103154747.GC2331@deviant.kiev.zoral.com.ua> References: <65275688@bb.ipt.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FsscpQKzF/jJk6ya" Content-Disposition: inline In-Reply-To: <65275688@bb.ipt.ru> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:47:53 -0000 --FsscpQKzF/jJk6ya Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > Hello List, >=20 > print/acroread8 doesn't work for me at 9-CURRENT: > ----- > % uname -a > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15:15:= 13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > % sysctl compat.linux > compat.linux.oss_version: 198144 > compat.linux.osrelease: 2.6.16 > compat.linux.osname: Linux > ------ >=20 > Setting security.bsd.map_at_zero to 1 doesn't change anything. There is > nothing at console/log files. Here is the tail of linux_kdump: > ----- > ... > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc04d9= 3e9475cbf44698a-x86.cache-2" > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf4469= 8a-x86.cache-2" > 78586 ld-2.9.so RET linux_open JUSTRETURN > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a0234dc= 04d93e9475cbf44698a-x86.cache-2" > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf= 44698a-x86.cache-2" > 78586 ld-2.9.so RET linux_open 4 > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > 78586 ld-2.9.so RET linux_fstat64 0 > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > 78586 ld-2.9.so GIO fd 4 read 96 bytes > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^[b\M= -TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > 78586 ld-2.9.so RET read 96/0x60 > 78586 ld-2.9.so CALL close(0x4) > 78586 ld-2.9.so RET close 0 > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > 78586 ld-2.9.so PSIG SIGSEGV caught handler=3D0x83814b6 mask=3D0x0 code= =3D0x0 > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0x8) > 78586 ld-2.9.so RET linux_rt_sigaction 0 > 78586 ld-2.9.so CALL linux_exit_group(0x1) It would be interesting to see which address faulted. If not, can you do search for a kernel revision that broke acroread ? Good starting points are r198507 and r198554. --FsscpQKzF/jJk6ya Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrwUKIACgkQC3+MBN1Mb4h3LQCgz37K8CKZ4/YsmUd23hdC7OOc zQwAmwZ52OQJbXsO7FPU2Zbb15SzUBgH =VpQf -----END PGP SIGNATURE----- --FsscpQKzF/jJk6ya-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 15:52:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6D54106568B; Tue, 3 Nov 2009 15:52:25 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 92D058FC2A; Tue, 3 Nov 2009 15:52:25 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 2394E48A58; Tue, 3 Nov 2009 15:52:24 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbNQqYa12yaT; Tue, 3 Nov 2009 15:52:21 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 3A24348A78; Tue, 3 Nov 2009 15:52:17 +0000 (GMT) Message-ID: <4AF05177.7030705@tomjudge.com> Date: Tue, 03 Nov 2009 15:51:19 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Weldon S Godfrey 3 References: <200911030937.11619.pieter@degoeje.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pieter de Goeje , freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:52:25 -0000 Weldon S Godfrey 3 wrote: > > > If memory serves me right, sometime around 9:37am, Pieter de Goeje told me: > >> Are you perhaps using em(4)? There was an mbuf leak in the driver, >> which was fixed recently. >> You can check mbuf usage with netstat -m. >> > > we are using onboard NICs on the Dell using the bce driver. We did try > several times to see if using an intel PCIexpress card using the em > driver, and we had the same symptoms. > > Could the bce driver have the same leak? The bce driver does not have a memory leak, it does however have a bug which causes memory fragmentation leading to denied mbuf allocation. There is a work around for this in current, you can get the patch like this: http://svn.freebsd.org/viewvc/base/head/ You need to put options BCE_JUMBO_HDRSPLIT In your kernel to enable the work arround. Tom From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 15:57:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FDEB1065672 for ; Tue, 3 Nov 2009 15:57:10 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 3F46E8FC16 for ; Tue, 3 Nov 2009 15:57:10 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-167-185.rz.uni-karlsruhe.de [141.3.167.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 3F2A28A0E14; Tue, 3 Nov 2009 16:57:09 +0100 (CET) Message-ID: <4AF052D4.8060401@bsdforen.de> Date: Tue, 03 Nov 2009 16:57:08 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Gonzalo Nemmi References: <4AEEDCFB.3060604@bsdforen.de> <200911021356.43043.gnemmi@gmail.com> <4AEFD6AE.6020906@bsdforen.de> <200911031045.03823.gnemmi@gmail.com> In-Reply-To: <200911031045.03823.gnemmi@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:57:10 -0000 Gonzalo Nemmi wrote: > On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: >> Gonzalo Nemmi wrote: >>> On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: >>>> It appears that my 8.0-RC2 system (notebook) forgets its mixer >>>> settings with every reboot. >>>> >>>> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct >>>> 31 02:49:30 CET 2009 >>>> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 >>>> 510 b-8 amd64 >>>> >>>> Regards >>> May I ask how are you setting them? >>> >>> Regards >>> Gonzalo >> With mixer(8). But now the settings are remembered. >> >> I suppose some evil app is to blame. But nothing apart from Skype >> comes to mind and I configured it not to touch the mixer settings. >> >> Regards > > Sorry but I have to ask ... have you tried configuring mixer settings as > described in section 7.2.4 of the FreBSD handbook? > > That is to say: > > "The default values for the different mixer channels are hardcoded in > the sourcecode of the pcm(4) driver. There are many different > applications and daemons that allow you to set values for the mixer > that are remembered between invocations, but this is not a clean > solution. ... Rather outdated in my opinion. Automatic mixer remembering without configuring anything has ever worked since I started using FreeBSD (i.e. 2005). From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 16:08:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6157B106566C for ; Tue, 3 Nov 2009 16:08:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 34E8D8FC21 for ; Tue, 3 Nov 2009 16:08:11 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C602D46B2C; Tue, 3 Nov 2009 11:08:10 -0500 (EST) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 292658A01D; Tue, 3 Nov 2009 11:08:10 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 3 Nov 2009 10:19:36 -0500 User-Agent: KMail/1.9.7 References: <4AEE296B.5040302@siad.net> In-Reply-To: <4AEE296B.5040302@siad.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911031019.36362.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 03 Nov 2009 11:08:10 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: Re: bootstrap loader problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 16:08:11 -0000 On Sunday 01 November 2009 7:35:55 pm Don L. Belcher wrote: > New Dell 1737 laptop > > The following error occurs with versions 7.2 release and later > this message is from 8 RC2. All versions tried with 7.1 release and > earlier work fine, I tried 7.1, 7.2 and 6.4. I rebuilt 8 RC2 CD with > "loader" > from 7.1 release and the 8 RC2 comes up O.K. now. > I have two questions: > 1) is anybody familiar with this problem > 2) is it ok to install 8 RC2 using the 7.1 "loader" > > BTX loader 1.00 BTX version is 1.02 > Consoles: internal video/keyboard > panic: free: guard1 fail @ 0xbb797074 from (diretory path to) > common/console.c:94 > --> Press a key (etc) I have not seen that before. Can you try compiling a loader on 8 that doesn't include GPT support? (cd /sys/boot; make LOADER_NO_GPT_SUPPORT=yes) A loader from 7.1 should work ok on 8.0. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 16:46:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C23D106566B for ; Tue, 3 Nov 2009 16:46:34 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from s2m-is-001.service2media.com (rev-130-102.virtu.nl [217.114.102.130]) by mx1.freebsd.org (Postfix) with ESMTP id AB78C8FC08 for ; Tue, 3 Nov 2009 16:46:33 +0000 (UTC) Received: from nox-laptop.localnet ([10.0.1.45] RDNS failed) by s2m-is-001.service2media.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Nov 2009 17:46:32 +0100 From: Pieter de Goeje To: Dominic Fandrey Date: Tue, 3 Nov 2009 17:46:31 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.31-14-generic; KDE/4.3.2; x86_64; ; ) References: <4AEEDCFB.3060604@bsdforen.de> <200911031045.03823.gnemmi@gmail.com> <4AF052D4.8060401@bsdforen.de> In-Reply-To: <4AF052D4.8060401@bsdforen.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200911031746.31571.pieter@degoeje.nl> X-OriginalArrivalTime: 03 Nov 2009 16:46:32.0056 (UTC) FILETIME=[32872F80:01CA5CA5] Cc: freebsd-current@freebsd.org, Gonzalo Nemmi Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 16:46:34 -0000 On Tuesday 03 November 2009 16:57:08 Dominic Fandrey wrote: > Gonzalo Nemmi wrote: > > On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: > >> Gonzalo Nemmi wrote: > >>> On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > >>>> It appears that my 8.0-RC2 system (notebook) forgets its mixer > >>>> settings with every reboot. > >>>> > >>>> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct > >>>> 31 02:49:30 CET 2009 > >>>> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 > >>>> 510 b-8 amd64 > >>>> > >>>> Regards > >>> May I ask how are you setting them? > >>> > >>> Regards > >>> Gonzalo > >> With mixer(8). But now the settings are remembered. > >> > >> I suppose some evil app is to blame. But nothing apart from Skype > >> comes to mind and I configured it not to touch the mixer settings. > >> > >> Regards > > > > Sorry but I have to ask ... have you tried configuring mixer settings as > > described in section 7.2.4 of the FreBSD handbook? > > > > That is to say: > > > > "The default values for the different mixer channels are hardcoded in > > the sourcecode of the pcm(4) driver. There are many different > > applications and daemons that allow you to set values for the mixer > > that are remembered between invocations, but this is not a clean > > solution. ... > > Rather outdated in my opinion. Automatic mixer remembering without > configuring anything has ever worked since I started using FreeBSD > (i.e. 2005). Perhaps you are using reboot/halt instead of shutdown? Reboot and halt will not start the shutdown scripts. -- Pieter de Goeje From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 15:43:37 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 645E61065679 for ; Tue, 3 Nov 2009 15:43:37 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id 047738FC16 for ; Tue, 3 Nov 2009 15:43:36 +0000 (UTC) Received: (qmail 57975 invoked by uid 89); 3 Nov 2009 15:43:34 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 15:43:34 -0000 Date: Tue, 3 Nov 2009 10:43:34 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Gavin Atkinson In-Reply-To: <1257261214.98619.92.camel@buffy.york.ac.uk> Message-ID: References: <1257185816.44755.29.camel@buffy.york.ac.uk> <1257261214.98619.92.camel@buffy.york.ac.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 16:49:08 +0000 Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:43:37 -0000 If memory serves me right, sometime around 3:13pm, Gavin Atkinson told me: > OK, at least we've figured out what is going wrong then. As a > workaround to get the machine to stay up longer, you should be able to > set kern.ipc.nmbclusters=256000 in /boot/loader.conf -but hopefully we > can resolve this soon. > > Firstly, what kernel was the above output from? And what network card > are you using? In your initial post you mentioned testing both bce(4) > and em(4) cards, be aware that em(4) had an issue that would cause > exactly this issue, which was fixed with a commit on September 11th > (r197093). Make sure your kernel is from after that date if you are > using em(4). I guess it is also possible that bce(4) has the same > issue, I'm not aware of any fixes to it recently. > > So, from here, I think the best thing would be to just use the em(4) NIC > and an up-to-date kernel, and see if you can reproduce the issue. > > How important is this machine? If em(4) works, are you able to help > debug the issues with the bce(4) driver? > > Thanks, > > Gavin > we used the em card only a few times, but each time we used it, the problem happened so we have been staying with the on board nics using the bce driver. Would leaving in the em card cause any issues, even if it isn't up? This output was from a kernel on 12/08. The issue really came up while we tried to swap to 8.0-RC2. We plan to swap back sometime in the near future. The same symptoms happened with RC2 so I am sure it is a kmem exhaustion. I am guessing v3 requires a lot more. When we switch, i'll change to using the em card. This machine is very important. I could set up an additional machine, but I don't have the ability to simulate the load nor have the large drive array attached. Thanks! Weldon From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 16:54:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001D21065679; Tue, 3 Nov 2009 16:54:46 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id AFEBF8FC16; Tue, 3 Nov 2009 16:54:46 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id CAFDA48A78; Tue, 3 Nov 2009 16:54:45 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqcZA1+muMIH; Tue, 3 Nov 2009 16:54:42 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id B3D8548A75; Tue, 3 Nov 2009 16:54:41 +0000 (GMT) Message-ID: <4AF06017.6000505@tomjudge.com> Date: Tue, 03 Nov 2009 16:53:43 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Weldon S Godfrey 3 References: <200911030937.11619.pieter@degoeje.nl> <4AF05177.7030705@tomjudge.com> In-Reply-To: <4AF05177.7030705@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pieter de Goeje , freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 16:54:47 -0000 Tom Judge wrote: > Weldon S Godfrey 3 wrote: >> >> >> If memory serves me right, sometime around 9:37am, Pieter de Goeje >> told me: >> >>> Are you perhaps using em(4)? There was an mbuf leak in the driver, >>> which was fixed recently. >>> You can check mbuf usage with netstat -m. >>> >> >> we are using onboard NICs on the Dell using the bce driver. We did >> try several times to see if using an intel PCIexpress card using the >> em driver, and we had the same symptoms. >> >> Could the bce driver have the same leak? > > The bce driver does not have a memory leak, it does however have a bug > which causes memory fragmentation leading to denied mbuf allocation. > > > There is a work around for this in current, you can get the patch like > this: > > http://svn.freebsd.org/viewvc/base/head/ > That should be: svn diff -r 198319:198320 http://svn.freebsd.org/base/head > You need to put > > options BCE_JUMBO_HDRSPLIT > > In your kernel to enable the work arround. > > Tom > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:02:34 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A8E21065695 for ; Tue, 3 Nov 2009 17:02:34 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id 1EA9C8FC1A for ; Tue, 3 Nov 2009 17:02:33 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA3H2Ar5021276; Tue, 3 Nov 2009 17:02:10 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5Mll-0007J6-1M; Tue, 03 Nov 2009 17:02:09 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA3H28I5006339; Tue, 3 Nov 2009 17:02:08 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nA3H28E2006338; Tue, 3 Nov 2009 17:02:08 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Weldon S Godfrey 3 In-Reply-To: References: <1257185816.44755.29.camel@buffy.york.ac.uk> <1257261214.98619.92.camel@buffy.york.ac.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 03 Nov 2009 17:02:07 +0000 Message-Id: <1257267727.98619.111.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:02:34 -0000 On Tue, 2009-11-03 at 10:43 -0500, Weldon S Godfrey 3 wrote: > This output was from a kernel on 12/08. The issue really came up while we > tried to swap to 8.0-RC2. We plan to swap back sometime in the near > future. The same symptoms happened with RC2 so I am sure it is a kmem > exhaustion. I am guessing v3 requires a lot more. When we switch, i'll > change to using the em card. Sorry, can you clarify: have you ever tested the em card with the 8.0-RC2 kernel? > This machine is very important. I could set up an additional machine, but > I don't have the ability to simulate the load nor have the large drive > array attached. OK, thanks. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:26:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9F6F106566B for ; Tue, 3 Nov 2009 17:26:40 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 48D9D8FC1A for ; Tue, 3 Nov 2009 17:26:40 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N5N9S-0000TQ-9Q for freebsd-current@freebsd.org; Tue, 03 Nov 2009 18:26:38 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 18:26:38 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 18:26:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Tue, 03 Nov 2009 09:26:15 -0800 Lines: 50 Message-ID: References: <20091031231545.493cee89@boiler.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: <20091031231545.493cee89@boiler.free.de> Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:26:40 -0000 Kai Gallasch wrote: > Hi. > > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > When I try to do a make buildworld or make buildkernel the server > reboots without any message left in the logs. The same happens > when building bigger ports (for example ruby18 or perl58) > > With 8.0-RC2 debug flags and witness seem to be disabled in the > standard GENERIC kernel, so unfortunately it is not possible for me to > build a debug kernel without my server crashing.. > > Now my idea was to install the old 8.0-BETA4 and upgrade to RC2 through > makeworld + buildkernel (gdb+witness). But no luck. When trying to > upgrade to RC2 the 8.0-BETA4 also crashes. At least 8.0-BETA4 has debug > + witness active in the GENERIC kernel.. > > So below some debug output of 8.0-BETA4 crashing. Has a vfs/ffs LOR > problem with the BETA4 already been fixed? > > Does it make sense to send in a pr with the old 8.0-BETA4? > > BTW. I installed 7.2-STABLE on this same server and did a "make > buildworld" and "make buildkernel" which completed without any problem. > > Cheers, > --Kai > > > ----- make buildworld -j7 crash, freebsd 8.0-amd64-beta4 ----- Definitely try the usual memory testing, power supply testing, etc. I had a similar problem, but with a HP DL385G5 that has some sort of "memory issue," and it would just silently reboot (which turned out to be a machine check exception.) I could never finger the problem be it with bios, the actual memory, or the fact that there's only one 4 core cpu on a two socket board and only the associated memory bank filled. I did various memory swaps to no avail, it would run memtest86 all day with no errors, and in the end I just turned superpages off and it works . Like a champ. If vm.pmap.pg_ps_enabled is 1 in 8.0-rc2, you might try rebooting with vm.pmap.pg_ps_enabled="0" in /boot/loader.conf and try another buildworld. From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:08:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47BF71065672; Tue, 3 Nov 2009 17:08:35 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from vppmailmx01.vip.hr (vppmailmx01.vip.hr [212.91.113.7]) by mx1.freebsd.org (Postfix) with ESMTP id 52CA58FC0A; Tue, 3 Nov 2009 17:08:33 +0000 (UTC) Received: from [95.168.120.40] by vppmailmx01.vip.hr with ESMTP id <20091103165804.THUL9582.vppmailmx01.vip.hr@[95.168.120.40]>; Tue, 3 Nov 2009 17:58:04 +0100 Date: Tue, 03 Nov 2009 17:59:16 +0100 From: "Ivan Voras" To: weldon@excelsusphoto.com MIME-Version: 1.0 X-Mailer: LCG ProfiMail Message-ID: <9308879887.941738356@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 17:34:16 +0000 Cc: pieter@degoeje.nl, freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:08:35 -0000 Something else just occured to me - do you use ipfw? -- Sent from my p1i mobile phone ------- Original message ------- > From: Weldon S Godfrey 3 > Cc: freebsd-current@freebsd.org, ivoras@freebsd.org > Sent: 3.11.'09, 14:35 > > > > If memory serves me right, sometime around 9:37am, Pieter de Goeje told > me: > >> Are you perhaps using em(4)? There was an mbuf leak in the driver, which >> was fixed recently. >> You can check mbuf usage with netstat -m. >> > > we are using onboard NICs on the Dell using the bce driver. We did try > several times to see if using an intel PCIexpress card using the em > driver, and we had the same symptoms. > > Could the bce driver have the same leak? > > Thanks! > > Weldon From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:34:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06446106566C for ; Tue, 3 Nov 2009 17:34:17 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id B21458FC08 for ; Tue, 3 Nov 2009 17:34:16 +0000 (UTC) Received: by qyk6 with SMTP id 6so2962430qyk.3 for ; Tue, 03 Nov 2009 09:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=4Ih5xk59kwsr1aUGdYB8GEwXHN5olPNeBGVFhUtTZQ8=; b=IydRmJyVb+1vyr0X0hp4wR07DubuCSztZl89jAF2lt1WLFV+HY/A6JVSUvXv+GDB06 vv+ifDYOSMNL9LeLdXYFHlI9Ov6PV23ZWjaNoQfctgRIzjbQckYSy2G+jMt9xD4NFuRD AKkKQy1Ybxafzx4/ddFTVKna65fnZqbkpuqcE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KdVLXbqbzKUgIla6KDzR1O7OzKWj9AmTYUT2zOyyL0gdgSj3PxzX/N8sQcUk3Jyd/N dvxbN5jNCxTlJxvyb0Ws/Oj5skvBBoCzNTkrKv9EOf7H0KjnTlO7kaJjb3e/TSL526ko 8cp0Lb+2ayVLJ53IXOe/yv/DZDjagw74190ac= MIME-Version: 1.0 Received: by 10.239.168.166 with SMTP id k38mr33157hbe.63.1257269655061; Tue, 03 Nov 2009 09:34:15 -0800 (PST) In-Reply-To: <200911031746.31571.pieter@degoeje.nl> References: <4AEEDCFB.3060604@bsdforen.de> <200911031045.03823.gnemmi@gmail.com> <4AF052D4.8060401@bsdforen.de> <200911031746.31571.pieter@degoeje.nl> Date: Tue, 3 Nov 2009 18:34:14 +0100 Message-ID: <19e9a5dc0911030934r601a4f23w20b9f23b51752327@mail.gmail.com> From: Gonzalo Nemmi To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:34:17 -0000 On Tue, Nov 3, 2009 at 5:46 PM, Pieter de Goeje wrote: > On Tuesday 03 November 2009 16:57:08 Dominic Fandrey wrote: > > Gonzalo Nemmi wrote: > > > On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: > > >> Gonzalo Nemmi wrote: > > >>> On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > > >>>> It appears that my 8.0-RC2 system (notebook) forgets its mixer > > >>>> settings with every reboot. > > >>>> > > >>>> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct > > >>>> 31 02:49:30 CET 2009 > > >>>> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 > > >>>> 510 b-8 amd64 > > >>>> > > >>>> Regards > > >>> May I ask how are you setting them? > > >>> > > >>> Regards > > >>> Gonzalo > > >> With mixer(8). But now the settings are remembered. > > >> > > >> I suppose some evil app is to blame. But nothing apart from Skype > > >> comes to mind and I configured it not to touch the mixer settings. > > >> > > >> Regards > > > > > > Sorry but I have to ask ... have you tried configuring mixer settings > as > > > described in section 7.2.4 of the FreBSD handbook? > > > > > > That is to say: > > > > > > "The default values for the different mixer channels are hardcoded in > > > the sourcecode of the pcm(4) driver. There are many different > > > applications and daemons that allow you to set values for the mixer > > > that are remembered between invocations, but this is not a clean > > > solution. ... > > > > Rather outdated in my opinion. Automatic mixer remembering without > > configuring anything has ever worked since I started using FreeBSD > > (i.e. 2005). > > Perhaps you are using reboot/halt instead of shutdown? > Reboot and halt will not start the shutdown scripts. > > -- > Pieter de Goeje > yup ... I use reboot or halt -p From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:46:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A18EE106566B for ; Tue, 3 Nov 2009 17:46:25 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay1.uni-muenster.de (ZIVM-EXRELAY1.UNI-MUENSTER.DE [128.176.192.14]) by mx1.freebsd.org (Postfix) with ESMTP id 31FDE8FC12 for ; Tue, 3 Nov 2009 17:46:24 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,675,1249250400"; d="scan'208";a="287265879" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay1.uni-muenster.de with ESMTP; 03 Nov 2009 18:46:23 +0100 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id 9F6BF1B07BE; Tue, 3 Nov 2009 18:46:23 +0100 (CET) Date: Tue, 03 Nov 2009 18:46:23 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Paul G Webster , Mark Linimon , Alexander Best Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Dominic Fandrey , freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:46:25 -0000 Paul G Webster schrieb am 2009-11-03: > As an example, this is a 1GB fat32 disk. > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) > desktop1# ls /dev | grep da0~ > desktop1# ls /dev | grep da0 > da0 > desktop1# fdisk /dev/da0 > ******* Working on device /dev/da0 ******* > parameters extracted from in-core disklabel are: > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) > parameters to be used for BIOS calculations are: > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 114 (0x72),(unknown) > start 778135908, size 1141509631 (557377 Meg), flag 6f > beg: cyl 357/ head 116/ sector 40; > end: cyl 357/ head 32/ sector 45 > The data for partition 2 is: > sysid 101 (0x65),(Novell Netware/386 3.xx) > start 168689522, size 1936028240 (945326 Meg), flag 69 > beg: cyl 288/ head 115/ sector 43; > end: cyl 367/ head 114/ sector 50 > The data for partition 3 is: > sysid 121 (0x79),(QNX4.x 3rd part) > start 1869881465, size 1936028192 (945326 Meg), flag 73 > beg: cyl 366/ head 32/ sector 33; > end: cyl 357/ head 32/ sector 43 > The data for partition 4 is: > sysid 13 (0x0d),(unknown) > start 0, size 3637226496 (1775989 Meg), flag 74 > beg: cyl 372/ head 97/ sector 50; > end: cyl 0/ head 10/ sector 0 > desktop1# *lol* just tried this myself and my fdisk output looks just as bad as yours: ******* Working on device da0 ******* parameters extracted from in-core disklabel are: cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 110 (0x6e),(unknown) start 1768187213, size 1701211749 (830669 Meg), flag 65 beg: cyl 357/ head 114/ sector 46; end: cyl 10/ head 255/ sector 13 The data for partition 2 is: sysid 255 (0xff),(Xenix bad blocks table) start 1953723749, size 980709985 (478862 Meg), flag 68 beg: cyl 370/ head 108/ sector 37; end: cyl 78/ head 13/ sector 10 The data for partition 3 is: sysid 116 (0x74),(unknown) start 1801683314, size 168652389 (82349 Meg), flag 20 beg: cyl 371/ head 84/ sector 33; end: cyl 100/ head 101/ sector 32 The data for partition 4 is: sysid 0 (0000),(unused) start 2885681152, size 54212 (26 Meg), flag 0 beg: cyl 0/ head 0/ sector 0; end: cyl 0/ head 0/ sector 0 `file -s /dev/da0` reports: /dev/da0: x86 boot sector, Microsoft Windows XP Bootloader (4.german) NTLDR, code offset 0x58, OEM-ID "MSDOS5.0", sectors/cluster 8, reserved sectors 38, Media descriptor 0xf8, heads 255, sectors 3903487 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 3805, serial number 0x88e88370, unlabeled `fdisk` in general seems to need some updates. this is the output if i call `fdisk` without any args: fdisk: mounted root fs resource doesn't match expectations (regexec returned 1) alex > On Tue, 03 Nov 2009 01:28:10 -0000, Mark Linimon > wrote: > >On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: > >>i guess the freebsd-fs@ guys know about these problems but don't > >>have > >>the time to deal with it. most of them are probably working on > >>zfs. > >AFAIK there are only a handful of people working on ZFS. > >We certainly need more people willing to work on filesystems code. > >In > >general it does have a large learning curve, so it's not as > >attractive > >as some of the other areas. That's probably why, as the kernel has > >undergone radical changes (e.g. for SMP) over time, that some of the > >fs code has not kept up. > >mcl > >_______________________________________________ > >freebsd-current@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to > >"freebsd-current-unsubscribe@freebsd.org" > -- > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:55:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A809106568D; Tue, 3 Nov 2009 17:55:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 93A108FC1E; Tue, 3 Nov 2009 17:55:39 +0000 (UTC) Received: by qyk6 with SMTP id 6so2972697qyk.3 for ; Tue, 03 Nov 2009 09:55:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=uYXKSF3gM0bpjt3ju8phMG45A6y2wDefRt2xeCtaQOM=; b=oHI3FbUp6BJ7GuNU1xEszpkravfAstjNSjipgKrUdSQPfiY7nrWInRQh4oIUlCFosb sly5RimphnbmhZS6r27A3AcGbUZm/Tmxe2mstUpQ92/QtUGCk3ER1EJP7Zbg9EYki3n/ eH0WPyFLIqzvbU3phcPSdjEfWJeeQ4Ebw6Klo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=wFQbvW726QCeFhBP1cA5Swi+atAr0FwYBduAQJohc62clfJl3rQPD+sTs2h5VciMk5 yf9h8fia54TME63h7RwlFcnF9142OcdPTdZuOMjxAYyk/EVoTFmwKiT7yQ41FiMA87EC wEjInzHzroKNV2F3s+AZDmrjkb/9qmXvZ7sc4= Received: by 10.224.21.204 with SMTP id k12mr160087qab.232.1257270938817; Tue, 03 Nov 2009 09:55:38 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 21sm176643qyk.0.2009.11.03.09.55.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Nov 2009 09:55:37 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 3 Nov 2009 09:55:01 -0800 From: Pyun YongHyeon Date: Tue, 3 Nov 2009 09:55:01 -0800 To: Gavin Atkinson Message-ID: <20091103175501.GD1256@michelle.cdnetworks.com> References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1257243047.98619.8.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, hselasky@freebsd.org, freebsd-usb@freebsd.org, Rick van der Zwet Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:55:40 -0000 On Tue, Nov 03, 2009 at 10:10:47AM +0000, Gavin Atkinson wrote: > [freebsd-current cc'd, as that was where the thread started, but this > probably belongs on -usb, replies should go there] > > On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote: > > The first net interface of a aue(4) define used to be called aue0 > > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no > > sign of ue(4) btw). > > > > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and > > freebsd-current@. But I could not find the reason why the naming > > convention on this aue differs from the regular stuff, anybody? > > > > /Rick > > > > quick# dmesg | tail -8 > > ugen1.3: at usbus1 > > aue0: on usbus1 > > miibus1: on aue0 > > ukphy0: PHY 1 on miibus1 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ue0: on aue0 > > ue0: Ethernet address: 00:00:e8:00:11:36 > > ue0: link state changed to DOWN > > > > quick# ifconfig -l > > bfe0 lo0 ue0 > > Hmm, this looks like a serious bug, possibly in the new USB subsystem > (HPS CC'd). > > I've got an axe(4) device, which also does the same: > > ugen7.3: at usbus7 > axe0: on usbus7 > axe0: PHYADDR 0xe0:0x10 > miibus1: on axe0 > ukphy0: PHY 16 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on axe0 > ue0: Ethernet address: 00:50:b6:05:57:a7 > ue0: link state changed to DOWN > I'm not sure this is feature of new USB or bug. I don't have strong objections on current behavior but looks like I'm seeing Linux behavior. Traditionally all network interfaces used their own driver name. I think this change should be documented in UPDATING. > Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 18:01:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A24C51065676 for ; Tue, 3 Nov 2009 18:01:22 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 671458FC21 for ; Tue, 3 Nov 2009 18:01:22 +0000 (UTC) Received: from [192.168.1.4] (adsl-150-102-19.bna.bellsouth.net [72.150.102.19]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id nA3I1Ami037185 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 3 Nov 2009 13:01:12 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Alexander Best In-Reply-To: References: Content-Type: text/plain Organization: FreeBSD Date: Tue, 03 Nov 2009 12:01:05 -0600 Message-Id: <1257271265.18564.0.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: Mark Linimon , freebsd-current@freebsd.org, Paul G Webster , Dominic Fandrey Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 18:01:22 -0000 On Tue, 2009-11-03 at 18:46 +0100, Alexander Best wrote: > Paul G Webster schrieb am 2009-11-03: > > As an example, this is a 1GB fat32 disk. > > > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-0 device > > da0: 1.000MB/s transfers > > da0: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) > > desktop1# ls /dev | grep da0~ > > desktop1# ls /dev | grep da0 > > da0 > > desktop1# fdisk /dev/da0 > > ******* Working on device /dev/da0 ******* > > parameters extracted from in-core disklabel are: > > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) > > > parameters to be used for BIOS calculations are: > > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) > > > Media sector size is 512 > > Warning: BIOS sector numbering starts with sector 1 > > Information from DOS bootblock is: > > The data for partition 1 is: > > sysid 114 (0x72),(unknown) > > start 778135908, size 1141509631 (557377 Meg), flag 6f > > beg: cyl 357/ head 116/ sector 40; > > end: cyl 357/ head 32/ sector 45 > > The data for partition 2 is: > > sysid 101 (0x65),(Novell Netware/386 3.xx) > > start 168689522, size 1936028240 (945326 Meg), flag 69 > > beg: cyl 288/ head 115/ sector 43; > > end: cyl 367/ head 114/ sector 50 > > The data for partition 3 is: > > sysid 121 (0x79),(QNX4.x 3rd part) > > start 1869881465, size 1936028192 (945326 Meg), flag 73 > > beg: cyl 366/ head 32/ sector 33; > > end: cyl 357/ head 32/ sector 43 > > The data for partition 4 is: > > sysid 13 (0x0d),(unknown) > > start 0, size 3637226496 (1775989 Meg), flag 74 > > beg: cyl 372/ head 97/ sector 50; > > end: cyl 0/ head 10/ sector 0 > > desktop1# > > *lol* just tried this myself and my fdisk output looks just as bad as yours: > > ******* Working on device da0 ******* > parameters extracted from in-core disklabel are: > cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 110 (0x6e),(unknown) > start 1768187213, size 1701211749 (830669 Meg), flag 65 > beg: cyl 357/ head 114/ sector 46; > end: cyl 10/ head 255/ sector 13 > The data for partition 2 is: > sysid 255 (0xff),(Xenix bad blocks table) > start 1953723749, size 980709985 (478862 Meg), flag 68 > beg: cyl 370/ head 108/ sector 37; > end: cyl 78/ head 13/ sector 10 > The data for partition 3 is: > sysid 116 (0x74),(unknown) > start 1801683314, size 168652389 (82349 Meg), flag 20 > beg: cyl 371/ head 84/ sector 33; > end: cyl 100/ head 101/ sector 32 > The data for partition 4 is: > sysid 0 (0000),(unused) > start 2885681152, size 54212 (26 Meg), flag 0 > beg: cyl 0/ head 0/ sector 0; > end: cyl 0/ head 0/ sector 0 > > `file -s /dev/da0` reports: > > /dev/da0: x86 boot sector, Microsoft Windows XP Bootloader (4.german) NTLDR, > code offset 0x58, OEM-ID "MSDOS5.0", sectors/cluster 8, reserved sectors 38, > Media descriptor 0xf8, heads 255, sectors 3903487 (volumes > 32 MB) , FAT (32 > bit), sectors/FAT 3805, serial number 0x88e88370, unlabeled > > `fdisk` in general seems to need some updates. this is the output if i call > `fdisk` without any args: The important question is what does "gpart show" say about these disks.... robert. > fdisk: mounted root fs resource doesn't match expectations (regexec returned > 1) > > alex > > > On Tue, 03 Nov 2009 01:28:10 -0000, Mark Linimon > > wrote: > > > >On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: > > >>i guess the freebsd-fs@ guys know about these problems but don't > > >>have > > >>the time to deal with it. most of them are probably working on > > >>zfs. > > > >AFAIK there are only a handful of people working on ZFS. > > > >We certainly need more people willing to work on filesystems code. > > >In > > >general it does have a large learning curve, so it's not as > > >attractive > > >as some of the other areas. That's probably why, as the kernel has > > >undergone radical changes (e.g. for SMP) over time, that some of the > > >fs code has not kept up. > > > >mcl > > >_______________________________________________ > > >freebsd-current@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-current > > >To unsubscribe, send any mail to > > >"freebsd-current-unsubscribe@freebsd.org" > > > > > -- > > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Robert Noland FreeBSD From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:16:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAB6610656E0 for ; Tue, 3 Nov 2009 17:16:04 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id 7FE7C8FC16 for ; Tue, 3 Nov 2009 17:16:04 +0000 (UTC) Received: (qmail 65091 invoked by uid 89); 3 Nov 2009 17:16:02 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 17:16:02 -0000 Date: Tue, 3 Nov 2009 12:16:02 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Ivan Voras In-Reply-To: <9308879887.941738356@gmail.com> Message-ID: References: <9308879887.941738356@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 18:11:24 +0000 Cc: pieter@degoeje.nl, freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:16:04 -0000 If memory serves me right, sometime around 5:59pm, Ivan Voras told me: > Something else just occured to me - do you use ipfw? > > -- not on this server. Thanks, Weldon From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:19:36 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24CD41065693 for ; Tue, 3 Nov 2009 17:19:36 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id ACA798FC19 for ; Tue, 3 Nov 2009 17:19:35 +0000 (UTC) Received: (qmail 65274 invoked by uid 89); 3 Nov 2009 17:19:34 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 17:19:34 -0000 Date: Tue, 3 Nov 2009 12:19:33 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Gavin Atkinson In-Reply-To: <1257267727.98619.111.camel@buffy.york.ac.uk> Message-ID: References: <1257185816.44755.29.camel@buffy.york.ac.uk> <1257261214.98619.92.camel@buffy.york.ac.uk> <1257267727.98619.111.camel@buffy.york.ac.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 18:11:30 +0000 Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:19:36 -0000 If memory serves me right, sometime around 5:02pm, Gavin Atkinson told me: > On Tue, 2009-11-03 at 10:43 -0500, Weldon S Godfrey 3 wrote: >> This output was from a kernel on 12/08. The issue really came up while we >> tried to swap to 8.0-RC2. We plan to swap back sometime in the near >> future. The same symptoms happened with RC2 so I am sure it is a kmem >> exhaustion. I am guessing v3 requires a lot more. When we switch, i'll >> change to using the em card. > > Sorry, can you clarify: have you ever tested the em card with the > 8.0-RC2 kernel? > We briefly tried em card with RC2 but went back because it didn't help at the time. But we are planning to go back to RC2 soon and I also plan to use the em card instead. From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 17:36:21 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 439121065672 for ; Tue, 3 Nov 2009 17:36:21 +0000 (UTC) (envelope-from weldon@excelsusphoto.com) Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252]) by mx1.freebsd.org (Postfix) with ESMTP id CE1968FC17 for ; Tue, 3 Nov 2009 17:36:20 +0000 (UTC) Received: (qmail 66617 invoked by uid 89); 3 Nov 2009 17:36:18 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost.excelsus.com with SMTP; 3 Nov 2009 17:36:18 -0000 Date: Tue, 3 Nov 2009 12:36:18 -0500 (EST) From: Weldon S Godfrey 3 X-X-Sender: weldon@emmett.excelsus.com To: Gavin Atkinson In-Reply-To: Message-ID: References: <1257185816.44755.29.camel@buffy.york.ac.uk> <1257261214.98619.92.camel@buffy.york.ac.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 03 Nov 2009 18:11:37 +0000 Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:36:21 -0000 If memory serves me right, sometime around 10:43am, Weldon S Godfrey 3 told me: > > > If memory serves me right, sometime around 3:13pm, Gavin Atkinson told me: > >> OK, at least we've figured out what is going wrong then. As a >> workaround to get the machine to stay up longer, you should be able to >> set kern.ipc.nmbclusters=256000 in /boot/loader.conf -but hopefully we >> can resolve this soon. >> I upped it to 256K. What I am trying to wrap my head around is how it was working somewhat for so long at 24K, but it got to near 65K before I rebooted it with the higher setting. Or did I reboot too early? Is there any cleanup that isn't triggered intil it reaches max nmbclusters? I am trying to see if anything on our network has changed to cause this to become cronic. From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 18:57:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AA70106568F for ; Tue, 3 Nov 2009 18:57:51 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (mx1.utsp.utwente.nl [130.89.2.12]) by mx1.freebsd.org (Postfix) with ESMTP id 1932B8FC12 for ; Tue, 3 Nov 2009 18:57:50 +0000 (UTC) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id nA3Iojgn021062; Tue, 3 Nov 2009 19:50:46 +0100 From: Pieter de Goeje To: Gonzalo Nemmi Date: Tue, 3 Nov 2009 19:50:45 +0100 User-Agent: KMail/1.9.10 References: <4AEEDCFB.3060604@bsdforen.de> <200911031746.31571.pieter@degoeje.nl> <19e9a5dc0911030934r601a4f23w20b9f23b51752327@mail.gmail.com> In-Reply-To: <19e9a5dc0911030934r601a4f23w20b9f23b51752327@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911031950.45797.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: freebsd-current@freebsd.org Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 18:57:51 -0000 On Tuesday 03 November 2009 18:34:14 Gonzalo Nemmi wrote: > On Tue, Nov 3, 2009 at 5:46 PM, Pieter de Goeje wrote: > > On Tuesday 03 November 2009 16:57:08 Dominic Fandrey wrote: > > > Gonzalo Nemmi wrote: > > > > On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: > > > >> Gonzalo Nemmi wrote: > > > >>> On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > > > >>>> It appears that my 8.0-RC2 system (notebook) forgets its mixer > > > >>>> settings with every reboot. > > > >>>> > > > >>>> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct > > > >>>> 31 02:49:30 CET 2009 > > > >>>> root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 > > > >>>> 510 b-8 amd64 > > > >>>> > > > >>>> Regards > > > >>> > > > >>> May I ask how are you setting them? > > > >>> > > > >>> Regards > > > >>> Gonzalo > > > >> > > > >> With mixer(8). But now the settings are remembered. > > > >> > > > >> I suppose some evil app is to blame. But nothing apart from Skype > > > >> comes to mind and I configured it not to touch the mixer settings. > > > >> > > > >> Regards > > > > > > > > Sorry but I have to ask ... have you tried configuring mixer settings > > > > as > > > > > > described in section 7.2.4 of the FreBSD handbook? > > > > > > > > That is to say: > > > > > > > > "The default values for the different mixer channels are hardcoded in > > > > the sourcecode of the pcm(4) driver. There are many different > > > > applications and daemons that allow you to set values for the mixer > > > > that are remembered between invocations, but this is not a clean > > > > solution. ... > > > > > > Rather outdated in my opinion. Automatic mixer remembering without > > > configuring anything has ever worked since I started using FreeBSD > > > (i.e. 2005). > > > > Perhaps you are using reboot/halt instead of shutdown? > > Reboot and halt will not start the shutdown scripts. > > > > -- > > Pieter de Goeje > > yup ... I use reboot or halt -p Well the obvious thing to try then is to use shutdown -r or -p instead... Does it work? - Pieter From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 19:02:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 012BF106568B; Tue, 3 Nov 2009 19:02:06 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9AEEF8FC25; Tue, 3 Nov 2009 19:02:05 +0000 (UTC) Received: from desktop1.yuno ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N5OiK-000KlK-5E; Tue, 03 Nov 2009 19:06:44 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Robert Noland" , "Alexander Best" References: <1257271265.18564.0.camel@balrog.2hip.net> Date: Tue, 03 Nov 2009 19:02:03 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Message-ID: In-Reply-To: <1257271265.18564.0.camel@balrog.2hip.net> User-Agent: Opera Mail/10.00 (FreeBSD) Cc: Mark Linimon , freebsd-current@freebsd.org, Dominic Fandrey Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 19:02:06 -0000 NOTE: I apologize to Mark Linimon he will get this message twice, I accidentally hit 'reply' instead of 'reply all' Here is the comedy, I just realized... This box is FreeBSD desktop1.yuno 7.2-RELEASE-p3 not 8-BETA2 I have to many desktops got a little confused between them. Incidentally the BETA2 box shows the exact same results ill get the gpart information as soon as I can. On Tue, 03 Nov 2009 18:01:05 -0000, Robert Noland wrote: > On Tue, 2009-11-03 at 18:46 +0100, Alexander Best wrote: >> Paul G Webster schrieb am 2009-11-03: >> > As an example, this is a 1GB fat32 disk. >> >> >> > da0 at umass-sim0 bus 0 target 0 lun 0 >> > da0: Removable Direct Access SCSI-0 device >> > da0: 1.000MB/s transfers >> > da0: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) >> > desktop1# ls /dev | grep da0~ >> > desktop1# ls /dev | grep da0 >> > da0 >> > desktop1# fdisk /dev/da0 >> > ******* Working on device /dev/da0 ******* >> > parameters extracted from in-core disklabel are: >> > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) >> >> > parameters to be used for BIOS calculations are: >> > cylinders=956 heads=64 sectors/track=32 (2048 blks/cyl) >> >> > Media sector size is 512 >> > Warning: BIOS sector numbering starts with sector 1 >> > Information from DOS bootblock is: >> > The data for partition 1 is: >> > sysid 114 (0x72),(unknown) >> > start 778135908, size 1141509631 (557377 Meg), flag 6f >> > beg: cyl 357/ head 116/ sector 40; >> > end: cyl 357/ head 32/ sector 45 >> > The data for partition 2 is: >> > sysid 101 (0x65),(Novell Netware/386 3.xx) >> > start 168689522, size 1936028240 (945326 Meg), flag 69 >> > beg: cyl 288/ head 115/ sector 43; >> > end: cyl 367/ head 114/ sector 50 >> > The data for partition 3 is: >> > sysid 121 (0x79),(QNX4.x 3rd part) >> > start 1869881465, size 1936028192 (945326 Meg), flag 73 >> > beg: cyl 366/ head 32/ sector 33; >> > end: cyl 357/ head 32/ sector 43 >> > The data for partition 4 is: >> > sysid 13 (0x0d),(unknown) >> > start 0, size 3637226496 (1775989 Meg), flag 74 >> > beg: cyl 372/ head 97/ sector 50; >> > end: cyl 0/ head 10/ sector 0 >> > desktop1# >> >> *lol* just tried this myself and my fdisk output looks just as bad as >> yours: >> >> ******* Working on device da0 ******* >> parameters extracted from in-core disklabel are: >> cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) >> >> parameters to be used for BIOS calculations are: >> cylinders=242 heads=255 sectors/track=63 (16065 blks/cyl) >> >> Media sector size is 512 >> Warning: BIOS sector numbering starts with sector 1 >> Information from DOS bootblock is: >> The data for partition 1 is: >> sysid 110 (0x6e),(unknown) >> start 1768187213, size 1701211749 (830669 Meg), flag 65 >> beg: cyl 357/ head 114/ sector 46; >> end: cyl 10/ head 255/ sector 13 >> The data for partition 2 is: >> sysid 255 (0xff),(Xenix bad blocks table) >> start 1953723749, size 980709985 (478862 Meg), flag 68 >> beg: cyl 370/ head 108/ sector 37; >> end: cyl 78/ head 13/ sector 10 >> The data for partition 3 is: >> sysid 116 (0x74),(unknown) >> start 1801683314, size 168652389 (82349 Meg), flag 20 >> beg: cyl 371/ head 84/ sector 33; >> end: cyl 100/ head 101/ sector 32 >> The data for partition 4 is: >> sysid 0 (0000),(unused) >> start 2885681152, size 54212 (26 Meg), flag 0 >> beg: cyl 0/ head 0/ sector 0; >> end: cyl 0/ head 0/ sector 0 >> >> `file -s /dev/da0` reports: >> >> /dev/da0: x86 boot sector, Microsoft Windows XP Bootloader (4.german) >> NTLDR, >> code offset 0x58, OEM-ID "MSDOS5.0", sectors/cluster 8, reserved >> sectors 38, >> Media descriptor 0xf8, heads 255, sectors 3903487 (volumes > 32 MB) , >> FAT (32 >> bit), sectors/FAT 3805, serial number 0x88e88370, unlabeled >> >> `fdisk` in general seems to need some updates. this is the output if i >> call >> `fdisk` without any args: > > The important question is what does "gpart show" say about these > disks.... > > robert. > >> fdisk: mounted root fs resource doesn't match expectations (regexec >> returned >> 1) >> >> alex >> >> > On Tue, 03 Nov 2009 01:28:10 -0000, Mark Linimon >> > wrote: >> >> > >On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: >> > >>i guess the freebsd-fs@ guys know about these problems but don't >> > >>have >> > >>the time to deal with it. most of them are probably working on >> > >>zfs. >> >> > >AFAIK there are only a handful of people working on ZFS. >> >> > >We certainly need more people willing to work on filesystems code. >> > >In >> > >general it does have a large learning curve, so it's not as >> > >attractive >> > >as some of the other areas. That's probably why, as the kernel has >> > >undergone radical changes (e.g. for SMP) over time, that some of the >> > >fs code has not kept up. >> >> > >mcl >> > >_______________________________________________ >> > >freebsd-current@freebsd.org mailing list >> > >http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > >To unsubscribe, send any mail to >> > >"freebsd-current-unsubscribe@freebsd.org" >> >> >> >> > -- >> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 21:07:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B3C71065672 for ; Tue, 3 Nov 2009 21:07:33 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id E69798FC15 for ; Tue, 3 Nov 2009 21:07:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 93CDCFF75; Wed, 4 Nov 2009 10:07:31 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTC5d-j5TZGJ; Wed, 4 Nov 2009 10:07:27 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Wed, 4 Nov 2009 10:07:27 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 08EE511477; Wed, 4 Nov 2009 10:07:26 +1300 (NZDT) Date: Wed, 4 Nov 2009 10:07:25 +1300 From: Andrew Thompson To: Pyun YongHyeon Message-ID: <20091103210725.GA33086@citylink.fud.org.nz> References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> <20091103175501.GD1256@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091103175501.GD1256@michelle.cdnetworks.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Rick van der Zwet , Gavin Atkinson , hselasky@freebsd.org, freebsd-usb@freebsd.org, freebsd-current@freebsd.org Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 21:07:33 -0000 On Tue, Nov 03, 2009 at 09:55:01AM -0800, Pyun YongHyeon wrote: > On Tue, Nov 03, 2009 at 10:10:47AM +0000, Gavin Atkinson wrote: > > [freebsd-current cc'd, as that was where the thread started, but this > > Hmm, this looks like a serious bug, possibly in the new USB subsystem > > (HPS CC'd). > > > > I've got an axe(4) device, which also does the same: > > > > ugen7.3: at usbus7 > > axe0: on usbus7 > > axe0: PHYADDR 0xe0:0x10 > > miibus1: on axe0 > > ukphy0: PHY 16 on miibus1 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ue0: on axe0 > > ue0: Ethernet address: 00:50:b6:05:57:a7 > > ue0: link state changed to DOWN > > > > I'm not sure this is feature of new USB or bug. I don't have strong > objections on current behavior but looks like I'm seeing Linux > behavior. Traditionally all network interfaces used their own > driver name. I think this change should be documented in UPDATING. I have added an UPDATING entry in 198859. Andrew From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 21:37:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78D611065672 for ; Tue, 3 Nov 2009 21:37:11 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 345168FC15 for ; Tue, 3 Nov 2009 21:37:10 +0000 (UTC) Received: from gate.ipt.ru ([194.62.233.123] helo=h30.sp.ipt.ru) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1N5R3t-000G6U-45; Wed, 04 Nov 2009 00:37:09 +0300 To: Kostik Belousov References: <65275688@bb.ipt.ru> <20091103154747.GC2331@deviant.kiev.zoral.com.ua> From: Boris Samorodov Date: Wed, 04 Nov 2009 00:37:08 +0300 In-Reply-To: <20091103154747.GC2331@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Tue\, 3 Nov 2009 17\:47\:47 +0200") Message-ID: <77755531@h30.sp.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 21:37:11 -0000 On Tue, 3 Nov 2009 17:47:47 +0200 Kostik Belousov wrote: > On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > > Hello List, > > > > print/acroread8 doesn't work for me at 9-CURRENT: > > ----- > > % uname -a > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15:15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > > % sysctl compat.linux > > compat.linux.oss_version: 198144 > > compat.linux.osrelease: 2.6.16 > > compat.linux.osname: Linux > > ------ > > > > Setting security.bsd.map_at_zero to 1 doesn't change anything. There is > > nothing at console/log files. Here is the tail of linux_kdump: > > ----- > > ... > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > 78586 ld-2.9.so RET linux_open JUSTRETURN > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > 78586 ld-2.9.so RET linux_open 4 > > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > > 78586 ld-2.9.so RET linux_fstat64 0 > > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > > 78586 ld-2.9.so GIO fd 4 read 96 bytes > > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^[b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > > 78586 ld-2.9.so RET read 96/0x60 > > 78586 ld-2.9.so CALL close(0x4) > > 78586 ld-2.9.so RET close 0 > > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) > > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > > 78586 ld-2.9.so PSIG SIGSEGV caught handler=0x83814b6 mask=0x0 code=0x0 > > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0x8) > > 78586 ld-2.9.so RET linux_rt_sigaction 0 > > 78586 ld-2.9.so CALL linux_exit_group(0x1) > It would be interesting to see which address faulted. > If not, can you do search for a kernel revision that broke acroread ? > Good starting points are r198507 and r198554. Were those revisions MFCed to RELENG_8_0? I've got the same for 8.0: ----- % uname -a FreeBSD h30.sp.ipt.ru 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Nov 1 18:57:33 MSK 2009 root@h30.sp.ipt.ru:/usr/obj/usr/src/sys/IN DUS i386 ----- -- WBR, bsam From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 21:40:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8ACD9106568B for ; Tue, 3 Nov 2009 21:40:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 197378FC18 for ; Tue, 3 Nov 2009 21:40:37 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA3LeWC0059644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Nov 2009 23:40:32 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA3LeW4X035347; Tue, 3 Nov 2009 23:40:32 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA3LeWuj035346; Tue, 3 Nov 2009 23:40:32 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 3 Nov 2009 23:40:32 +0200 From: Kostik Belousov To: Boris Samorodov Message-ID: <20091103214032.GF2331@deviant.kiev.zoral.com.ua> References: <65275688@bb.ipt.ru> <20091103154747.GC2331@deviant.kiev.zoral.com.ua> <77755531@h30.sp.ipt.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3yNHWXBV/QO9xKNm" Content-Disposition: inline In-Reply-To: <77755531@h30.sp.ipt.ru> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 21:40:38 -0000 --3yNHWXBV/QO9xKNm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 04, 2009 at 12:37:08AM +0300, Boris Samorodov wrote: > On Tue, 3 Nov 2009 17:47:47 +0200 Kostik Belousov wrote: > > On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > > > Hello List, > > >=20 > > > print/acroread8 doesn't work for me at 9-CURRENT: > > > ----- > > > % uname -a > > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15= :15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > > > % sysctl compat.linux > > > compat.linux.oss_version: 198144 > > > compat.linux.osrelease: 2.6.16 > > > compat.linux.osname: Linux > > > ------ > > >=20 > > > Setting security.bsd.map_at_zero to 1 doesn't change anything. There = is > > > nothing at console/log files. Here is the tail of linux_kdump: > > > ----- > > > ... > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc= 04d93e9475cbf44698a-x86.cache-2" > > > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf= 44698a-x86.cache-2" > > > 78586 ld-2.9.so RET linux_open JUSTRETURN > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a02= 34dc04d93e9475cbf44698a-x86.cache-2" > > > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e947= 5cbf44698a-x86.cache-2" > > > 78586 ld-2.9.so RET linux_open 4 > > > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > > > 78586 ld-2.9.so RET linux_fstat64 0 > > > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > > > 78586 ld-2.9.so GIO fd 4 read 96 bytes > > > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^= [b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > > > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > > > 78586 ld-2.9.so RET read 96/0x60 > > > 78586 ld-2.9.so CALL close(0x4) > > > 78586 ld-2.9.so RET close 0 > > > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) > > > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > > > 78586 ld-2.9.so PSIG SIGSEGV caught handler=3D0x83814b6 mask=3D0x0 = code=3D0x0 > > > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0= x8) > > > 78586 ld-2.9.so RET linux_rt_sigaction 0 > > > 78586 ld-2.9.so CALL linux_exit_group(0x1) >=20 > > It would be interesting to see which address faulted. > > If not, can you do search for a kernel revision that broke acroread ? > > Good starting points are r198507 and r198554. >=20 > Were those revisions MFCed to RELENG_8_0? I've got the same for 8.0: > ----- > % uname -a > FreeBSD h30.sp.ipt.ru 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Nov 1 18:57:33 MSK= 2009 root@h30.sp.ipt.ru:/usr/obj/usr/src/sys/IN > DUS i386 > ----- No. It might be easier to bisect on releng/8.0 then. --3yNHWXBV/QO9xKNm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrwo0QACgkQC3+MBN1Mb4jLIwCglDy0BFmYSwszM+gEYYAWec69 814AoO5q9A8gdma2f+mQ8THtutpEuRWg =bqG6 -----END PGP SIGNATURE----- --3yNHWXBV/QO9xKNm-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 22:15:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D49D1065780 for ; Tue, 3 Nov 2009 22:15:23 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 09C5A8FC16 for ; Tue, 3 Nov 2009 22:15:22 +0000 (UTC) Received: by fxm27 with SMTP id 27so27017fxm.3 for ; Tue, 03 Nov 2009 14:15:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=YbRt3NpegQWcxnE5qw+OVhSjvvwdeLivHbTMDMXkb4o=; b=wW8OLLr+eZD+75AMDTal7vwu/WRdpYo+cHKkvigqCQZ6AFf0lzBboIFKEdd3vVQy4E uRX7bH/4omnJoNy6B4RKmCRhNWp5w5oMSOFUbD6dkTsHeKlp+X52Aw1hKTFbaxNKXy4d hjt1EbmViWlggguG4mpUmhhYAgPIHjnXelxlc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=c1fNzEAWxEcAyWKnvqb6bYVkx+SCikwEV5fsks4wXlQXiWFxpqA8gCKIsUVGJeIkxj 2UPzoXxhLrKC8l8xpFOzuElfAb5OycHkWZ6WFcyWYG7OpJrC7XLxsghOZ4HUL9BNJXnN C02ofIa5MWQjwA+bGj4fre9/I7CrLndshBANw= MIME-Version: 1.0 Received: by 10.239.144.102 with SMTP id n38mr73790hba.176.1257286522040; Tue, 03 Nov 2009 14:15:22 -0800 (PST) In-Reply-To: <200911031950.45797.pieter@degoeje.nl> References: <4AEEDCFB.3060604@bsdforen.de> <200911031746.31571.pieter@degoeje.nl> <19e9a5dc0911030934r601a4f23w20b9f23b51752327@mail.gmail.com> <200911031950.45797.pieter@degoeje.nl> Date: Tue, 3 Nov 2009 23:15:21 +0100 Message-ID: <19e9a5dc0911031415g7fb14eb4h37e2ccd245fdd9cf@mail.gmail.com> From: Gonzalo Nemmi To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: mixer settings on 8.0-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 22:15:23 -0000 On Tue, Nov 3, 2009 at 7:50 PM, Pieter de Goeje wrote: > On Tuesday 03 November 2009 18:34:14 Gonzalo Nemmi wrote: > > On Tue, Nov 3, 2009 at 5:46 PM, Pieter de Goeje > wrote: > > > On Tuesday 03 November 2009 16:57:08 Dominic Fandrey wrote: > > > > Gonzalo Nemmi wrote: > > > > > On Tuesday 03 November 2009 5:07:26 am Dominic Fandrey wrote: > > > > >> Gonzalo Nemmi wrote: > > > > >>> On Monday 02 November 2009 11:22:03 am Dominic Fandrey wrote: > > > > >>>> It appears that my 8.0-RC2 system (notebook) forgets its mixer > > > > >>>> settings with every reboot. > > > > >>>> > > > > >>>> FreeBSD mobileKamikaze.norad 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat O= ct > > > > >>>> 31 02:49:30 CET 2009 > > > > >>>> root@mobileKamikaze.norad > :/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6 > > > > >>>> 510 b-8 amd64 > > > > >>>> > > > > >>>> Regards > > > > >>> > > > > >>> May I ask how are you setting them? > > > > >>> > > > > >>> Regards > > > > >>> Gonzalo > > > > >> > > > > >> With mixer(8). But now the settings are remembered. > > > > >> > > > > >> I suppose some evil app is to blame. But nothing apart from Skyp= e > > > > >> comes to mind and I configured it not to touch the mixer setting= s. > > > > >> > > > > >> Regards > > > > > > > > > > Sorry but I have to ask ... have you tried configuring mixer > settings > > > > > > as > > > > > > > > described in section 7.2.4 of the FreBSD handbook? > > > > > > > > > > That is to say: > > > > > > > > > > "The default values for the different mixer channels are hardcode= d > in > > > > > the sourcecode of the pcm(4) driver. There are many different > > > > > applications and daemons that allow you to set values for the mix= er > > > > > that are remembered between invocations, but this is not a clean > > > > > solution. ... > > > > > > > > Rather outdated in my opinion. Automatic mixer remembering without > > > > configuring anything has ever worked since I started using FreeBSD > > > > (i.e. 2005). > > > > > > Perhaps you are using reboot/halt instead of shutdown? > > > Reboot and halt will not start the shutdown scripts. > > > > > > -- > > > Pieter de Goeje > > > > yup ... I use reboot or halt -p > > Well the obvious thing to try then is to use shutdown -r or -p instead... > Does > it work? > > - Pieter > That would be up to the OP .. I don=B4t have mixer problems as my mixer val= ues are set as hints :D Best Regards Gonzalo From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 22:21:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E550F106566B for ; Tue, 3 Nov 2009 22:21:42 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id 5E95C8FC1D for ; Tue, 3 Nov 2009 22:21:42 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id nA3MLRc2022086; Tue, 3 Nov 2009 22:21:27 GMT Received: from ury.york.ac.uk ([144.32.108.81]) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N5Rkl-00039r-P6; Tue, 03 Nov 2009 22:21:27 +0000 Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.14.3/8.14.3) with ESMTP id nA3MLReP081156; Tue, 3 Nov 2009 22:21:27 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.14.3/8.14.3/Submit) with ESMTP id nA3MLRC4081151; Tue, 3 Nov 2009 22:21:27 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Tue, 3 Nov 2009 22:21:27 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Tom Judge In-Reply-To: <4AF06017.6000505@tomjudge.com> Message-ID: <20091103221739.E75071@ury.york.ac.uk> References: <200911030937.11619.pieter@degoeje.nl> <4AF05177.7030705@tomjudge.com> <4AF06017.6000505@tomjudge.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: Pieter de Goeje , Weldon S Godfrey 3 , freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 22:21:43 -0000 On Tue, 3 Nov 2009, Tom Judge wrote: > Tom Judge wrote: >> Weldon S Godfrey 3 wrote: >>> we are using onboard NICs on the Dell using the bce driver. We did try >>> several times to see if using an intel PCIexpress card using the em >>> driver, and we had the same symptoms. >>> >>> Could the bce driver have the same leak? >> >> The bce driver does not have a memory leak, it does however have a bug >> which causes memory fragmentation leading to denied mbuf allocation. >> >> There is a work around for this in current, you can get the patch like >> this: >> >> http://svn.freebsd.org/viewvc/base/head/ >> > That should be: > > svn diff -r 198319:198320 http://svn.freebsd.org/base/head > >> You need to put >> >> options BCE_JUMBO_HDRSPLIT >> >> In your kernel to enable the work arround. Unless I'm missing something, these seem like they may be totally different bugs. The symptoms that Weldon S Godfrey has show the number of "mbuf clusters in use" rising to the point at which the limit is reached, whereas the thread on -stable where BCE_JUMBO_HDRSPLIT is recommended has the symptom of "requests for 9k jumbo clusters denied" increasing and the mbuf clusters not being anywhere near to the maximum. So, I think there may be some confusion here. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 22:29:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268DC106566B; Tue, 3 Nov 2009 22:29:05 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id D4E6C8FC14; Tue, 3 Nov 2009 22:29:04 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id EE44348A9A; Tue, 3 Nov 2009 22:29:03 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jd+vkNONOA46; Tue, 3 Nov 2009 22:28:59 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 9968448A93; Tue, 3 Nov 2009 22:28:58 +0000 (GMT) Message-ID: <4AF0AE70.7030004@tomjudge.com> Date: Tue, 03 Nov 2009 22:28:00 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Gavin Atkinson References: <200911030937.11619.pieter@degoeje.nl> <4AF05177.7030705@tomjudge.com> <4AF06017.6000505@tomjudge.com> <20091103221739.E75071@ury.york.ac.uk> In-Reply-To: <20091103221739.E75071@ury.york.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pieter de Goeje , Weldon S Godfrey 3 , freebsd-current@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 22:29:05 -0000 Gavin Atkinson wrote: > On Tue, 3 Nov 2009, Tom Judge wrote: >> Tom Judge wrote: >>> Weldon S Godfrey 3 wrote: >>>> we are using onboard NICs on the Dell using the bce driver. We did >>>> try several times to see if using an intel PCIexpress card using the >>>> em driver, and we had the same symptoms. >>>> >>>> Could the bce driver have the same leak? >>> >>> The bce driver does not have a memory leak, it does however have a >>> bug which causes memory fragmentation leading to denied mbuf allocation. >>> >>> There is a work around for this in current, you can get the patch >>> like this: >>> >>> http://svn.freebsd.org/viewvc/base/head/ >>> >> That should be: >> >> svn diff -r 198319:198320 http://svn.freebsd.org/base/head >> >>> You need to put >>> >>> options BCE_JUMBO_HDRSPLIT >>> >>> In your kernel to enable the work arround. > > Unless I'm missing something, these seem like they may be totally > different bugs. The symptoms that Weldon S Godfrey has show the number > of "mbuf clusters in use" rising to the point at which the limit is > reached, whereas the thread on -stable where BCE_JUMBO_HDRSPLIT is > recommended has the symptom of "requests for 9k jumbo clusters denied" > increasing and the mbuf clusters not being anywhere near to the maximum. > > So, I think there may be some confusion here. Jumbo frames are not in use what what I have read in the thread however there are denied requests for mbuf+clusters, so this could be the issue in the bce driver with standrad size frames. See: 0/201276/90662 requests for mbufs denied (mbufs/clusters/mbuf+clusters) I guess that there are 2 issues at work here, adding the bce patch should not cause any problems but may resolve the issue when using the bce driver. Is it not worth a try? Tom From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 00:17:36 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC1C81065672 for ; Wed, 4 Nov 2009 00:17:35 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 5D2398FC16 for ; Wed, 4 Nov 2009 00:17:35 +0000 (UTC) Received: (qmail 63487 invoked from network); 4 Nov 2009 01:17:33 +0100 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 4 Nov 2009 01:17:33 +0100 Date: Wed, 4 Nov 2009 01:17:16 +0100 From: Kai Gallasch To: Gavin Atkinson Message-ID: <20091104011716.768baae5@orwell.free.de> In-Reply-To: <1257244960.98619.36.camel@buffy.york.ac.uk> References: <20091031231545.493cee89@boiler.free.de> <1257244960.98619.36.camel@buffy.york.ac.uk> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.18.2; powerpc-apple-darwin9.7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 00:17:36 -0000 Am Tue, 03 Nov 2009 10:42:40 +0000 schrieb Gavin Atkinson : > On Sat, 2009-10-31 at 23:15 +0100, Kai Gallasch wrote: > > Hi. > > > > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > > > When I try to do a make buildworld or make buildkernel the server > > reboots without any message left in the logs. The same happens > > when building bigger ports (for example ruby18 or perl58) > First place I think I'd start id by running memtest86 on the machine > overnight. This sounds like possible hardware issue to me, it would > be good to see if we can confirm that that is the case. I will do so tomorrow. Following actions I have already taken to rule out a hardware problem: - ran several passes with diagnostic software from the manufacturer - reset BIOS settings to default - upgraded BIOS to newest release - booted server from 2 year old backup BIOS - took out the only pair of RAM modules that was different from the rest of the modules - installed freebsd 7.2-STABLE on the server to repeat the kernel panic (no panic with 7.2) - installed 8.0-BETA4 (crash) Besides: The server was in production with 7.2 for some time, without showing any such problems. > > Now my idea was to install the old 8.0-BETA4 and upgrade to RC2 > > through makeworld + buildkernel (gdb+witness). But no luck. When > > trying to upgrade to RC2 the 8.0-BETA4 also crashes. At least > > 8.0-BETA4 has debug > > + witness active in the GENERIC kernel.. > > > > So below some debug output of 8.0-BETA4 crashing. Has a vfs/ffs LOR > > problem with the BETA4 already been fixed? > > The debug output you included were just lock order reversals, and > don't seem to be related to your crash. Sorry for causing possible confusion about this. I realized this after my mail was already out. > I think 8.0-BETA4 still had the debugger compiled in (you can test by > pressing ctrl-alt-escape ion the console, if you do drop to the > debugger, give the "c" command to continue). > > If the debugger is compiled in, then the spontaneous reboot without > dropping to the debugger suggests even more that it may be hardware > related. If you do get to the debugger, a copy of all of the messages > on screen and the output of the "bt" command would be very useful. > When you do your kernel recompile, please include full debugging, > including WITNESS, INVARIANTS, KDB, DDB etc. In the meantime I managed it to install a RELENG_8 world + GENERIC kernel with all debug options enabled on the crashing server. (mounted /usr/src and /usr/obj on another server running 8.0RC1 through NFS and did buildworld + buildkernel over there..) So now I have a debug kernel available with dumpev + dumpdir defined. Here are my latest findings on this issue: - Running a makeworld in about 80% leads to a server crash without the server writing a crashdump to dumpdir. The server just reboots.. - In about 20% of the cases makeworld gets stuck in a not terminating process that eats up 100% cpu. This process cannot be killed. When restarting makeworld the server then reboots again - It makes no difference doing makeworld -j1 or -j8, result is the same > It depends what the bug is to be honest. So far there isn't really > enough information to determine the cause, and therefore there isn't > really enough info for a PR. Mark Atkinson also commented on my mail and he gave the hint: "If vm.pmap.pg_ps_enabled is 1 in 8.0-rc2, you might try rebooting with c in /boot/loader.conf and try another buildworld." So I thought why not and just tried it - and surprise: Disabling vm.pmap.pg_ps_enabled=1 in loader.conf resolves my problem with 8.0RC2 crashing when doing a makeworld.. After successful buildworld and buildkernel I rebooted the server again with commented out vm.pmap.pg_ps_enabled=0 and the problem was there again. And then I disabled the option again in loader.conf, rebooted + make buildworld .. no problem. Seems to be deterministic. With vm.pmap.pg_ps_enabled=1 the server crashes without being able to write crashdumps to dumpdev. (at least on this specific Proliant DL385G2 server) --Kai. -- You need more time; and you probably always will. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 09:51:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2195C106566B for ; Wed, 4 Nov 2009 09:51:10 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from web51806.mail.re2.yahoo.com (web51806.mail.re2.yahoo.com [206.190.38.237]) by mx1.freebsd.org (Postfix) with SMTP id BE2148FC1C for ; Wed, 4 Nov 2009 09:51:09 +0000 (UTC) Received: (qmail 93965 invoked by uid 60001); 4 Nov 2009 09:51:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1257328268; bh=p6pkiNQEOdDyLsCeO9xaDtHVHOmJBO2+QdusAUMdo+M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ErtrsUYevPrO9agu7nyAjFXjotiXh0UGm3TTlbSwvs3+60fJ4SbIzhi2R1JVu9+Z6T6F4VsIlTzNf0quN9N/B4s1nci+JrPpWq/eqnfS19Hn8TTNv/S1Uj84mYzhg0dMajLeYU53+qKEGEPi7b3rxNa1qc85V7/rNAvapSCTTTU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=QdKCkWqI0qDdk5cujzauOieao+yFdVrgkXfh2hRVwMBG15Oj1wpL4xAgcYDGthX0sBHnTfzkyV2GWgUiE3yqlhaoaA4VR/cDiHlCtTE60qqENZxPBXfGW59kGcturKUWWEn4l5DPwdrk39GHzZeS3RnfFMYb/K6mzBKkaR5f1Eg=; Message-ID: <950696.93705.qm@web51806.mail.re2.yahoo.com> X-YMail-OSG: re3M7gUVM1nPB5m3MNe9ag8MP3ExcF0Oyr2g6DddMzinrNXGscQL_zR52_h5p29opu5ITvOo4JKtqi2poBXXaOEygXwYzABbrXuHo1jhOsLWxoZlu4O953nkC0T1NT0MRXyEJMGrm8DKEq3ZUi31Ht0rnBwr8iu4j_4G_rCkszx9dwzD2zTXRDmXMbcCi9WiZApxu0oDzIRKeaTe7O7wFkYt9Lvbx89xNdoAQXkNEx4znxKIiK82vynImnfbbRLATkXqusdiRH3sLn8CuxqqlbSRlmWpGQrDH1g3q9nY17mr5IOZPChgDauZP6TxCVJriQMeo52845v5PJs8FbHtIEu08IeJ.n3508U7VhTG48GpJHfrl8WGr3iRdpUwz_CKMeH8zFkWfUb_iJZUjAcmaxrrvU4erVmgcZnOzffF35lb_VC_4Jw8ug_vi.AONdrkaG6zP30R5VRKAeozW6zDV8_5McRHzbV3jQREUEDXnjH4b2Y3lMRCJ94yp2O7EE9FfZ3bZjJbjTUu6I1WLCv8S45ByLbvC_wHeGx24jDLirMu7LI- Received: from [75.158.17.63] by web51806.mail.re2.yahoo.com via HTTP; Wed, 04 Nov 2009 01:51:08 PST X-Mailer: YahooMailRC/211.6 YahooMailWebService/0.7.361.4 References: <143477.23789.qm@web51804.mail.re2.yahoo.com> <3a142e750911030408t25dd59b0rcda6eccd8c24c0c9@mail.gmail.com> Date: Wed, 4 Nov 2009 01:51:08 -0800 (PST) From: PseudoCylon To: Paul B Mahol In-Reply-To: <3a142e750911030408t25dd59b0rcda6eccd8c24c0c9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: Wireless usb + wep = no usbd_do_request X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 09:51:10 -0000 ----- Original Message ---- > From: Paul B Mahol > To: PseudoCylon > Cc: freebsd-current@freebsd.org > Sent: Tue, November 3, 2009 5:08:47 AM > Subject: Re: Wireless usb + wep = no usbd_do_request > > On 11/3/09, PseudoCylon wrote: > > Hi, > > > > I'm porting a wireless usb driver (if_run) to freebsd current, and I got > > stuck. Once I "ifconfig wlan0 wepkey 1:0x... weptxkey 1" I cannot call > > usbd_do_request() any more. Even ifconfig didn't exit. Chipset supports h/w > > en/decryption, so cannot write keys on chip. (It works without encryption, > > by the way.) > > > > So, I tried the same thing on another device, linksys wusb54gc with if_rum. > > It worked fine, but about 3 to 4 min later. (Just left it alone.) It started > > giving error > > rum0: could not multi read MAC register: USB_ERR_TIMEOUT and > > rum0: device timeout > > when ifconfig wlan0 down, > > rum0: could not multi write MAC register: USB_ERR_TIMEOUT > > which means failed on usbd_do_request() (This could be totally different > > issue.) > > I get this one multiple times after card got detached but vap was not > manually destroyed. > Recently I did not used if_rum more that 5 min I think(maybe in AP > mode when I was testing hidden ssid ...) > > > Any ideas, patches, or walkaround? > > Make sure how locks are handled between net80211, usb and driver itself. Thanks for the reply. I think that's just simple lock problem, too. Just I don't know what it is. I tried IEEE80211_LOCK IEEE80211_NODE_LOCK IEEE80211_NODE_ITERATE_LOCK but I cannot lock or unlock them. (I can lock IF_LOCK.) I just get "panic: mtx_lock of spin mutex(null)" For example, IEEE80211_LOCK is sleep mutex, and I can use it in newstate() no problem, but I some how it becomes spin mutex in key_set(). Once I find what is over writing lock type, I can make it work. Wish me a luck. > > > More info > > #uname -a > > FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r198150M: Fri Oct 16 22:44:08 > > UTC 2009 amd64 > > > > ddb trace output 20+ minutes after "ifconfig wepkey" (using if_run) > > Tracing command ifconfig pid 1586 tid 100159 td 0xffffff000b3d3a80 > > sched_switch() at sched_switch+0x180 > > mi_switch() at mi_switch+0x21d > > sleepq_switch() at sleepq_switch+0x123 > > sleepq_wait() at sleepq_wait+0x4d > > _sleep() at _sleep+0x357 > > taskqueue_drain() at taskqueue_drain+0xc2 > > ieee80211_waitfor_parent() at ieee80211_waitfor_parent+0x3e > > ieee80211_ioctl() at ieee80211_ioctl+0x162 > > ifioctl() at ifioctl+0xde4 > > kern_ioctl() at kern_ioctl+0xc5 > > ioctl() at ioctl+0xfd > > syscall() at syscall+0x1af > > Xfast_syscall() at Xfast_syscall+0xe1 > > > > Also, sleep mutex became spin mutex. I get a panic > > panic: mtx_lock of spin mutex(null) > > It works fine before ifconfig wepkey. > > It is hard to tell without code example but wepkey works fine with > if_rum last time I tried, note that if_rum have done encryption in > software mode. __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 10:55:21 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4199C1065693 for ; Wed, 4 Nov 2009 10:55:21 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward7.yandex.ru (forward7.yandex.ru [77.88.61.37]) by mx1.freebsd.org (Postfix) with ESMTP id EF0B98FC1B for ; Wed, 4 Nov 2009 10:55:20 +0000 (UTC) Received: from webmail38.yandex.ru (webmail38.yandex.ru [77.88.60.17]) by forward7.yandex.ru (Yandex) with ESMTP id E60D33118FA for ; Wed, 4 Nov 2009 13:44:10 +0300 (MSK) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail38.yandex.ru (Yandex) with ESMTP id C20527E4301 for ; Wed, 4 Nov 2009 13:44:10 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail38 X-Yandex-TimeMark: 1257331450 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Wed, 04 Nov 2009 13:44:10 +0300 From: S.N.Grigoriev To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: <44591257331450@webmail38.yandex.ru> Date: Wed, 04 Nov 2009 13:44:10 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 10:55:21 -0000 Hi list, I can confirm I've seen the same problem. After upgrading from 7-stable to 8.0-RC2 my machine just reboots during 'make buildworld' without diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not work for me. My machine reboots every time I try to build world. I don't think I have a hardware problem: under 7-stable I can build world/kernel for both 7-stable and 8.0-RC2 without problems. -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 12:40:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F5821065695 for ; Wed, 4 Nov 2009 12:40:27 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 10BCF8FC1D for ; Wed, 4 Nov 2009 12:40:26 +0000 (UTC) Received: by ewy18 with SMTP id 18so497982ewy.43 for ; Wed, 04 Nov 2009 04:40:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=+vcqiNz+fkGY8ebpExucdCo1b0RRItz04K+d0La7uxw=; b=FfHCyWUNJO+Fzx0/XJNH5O1OmWekdWzPPJHjJtgOsxmjj8dlkL0A3IvpbL/WuYRaTO Gfu9VBK6F9Lt5T0hGxwhjtRxBR5YgZeVFw1YakvBnTbn7QFTFyxiD7JA5xd+06zz2rk2 Dpitk1l7hzoyMWOKuyQS2hpJKoD9y5kBiSf3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GrWnnGHWT8CbuS3XsSQzwCnanaHeg/loy4OMzVDRjtXnmQ+KqyxkInHT4aHw4D1cLA rY3gnThoy+zgCAN3IfBHcRRTTgcBtWoEwuQrVzpjjPRd1PTEyIRxJLY/bjCvM9OWrcSw nzSY3ayNHklOWszNdM6ei2PotisH3ssAL+Bbo= MIME-Version: 1.0 Received: by 10.213.2.73 with SMTP id 9mr1672129ebi.21.1257338426126; Wed, 04 Nov 2009 04:40:26 -0800 (PST) In-Reply-To: <950696.93705.qm@web51806.mail.re2.yahoo.com> References: <143477.23789.qm@web51804.mail.re2.yahoo.com> <3a142e750911030408t25dd59b0rcda6eccd8c24c0c9@mail.gmail.com> <950696.93705.qm@web51806.mail.re2.yahoo.com> Date: Wed, 4 Nov 2009 13:40:26 +0100 Message-ID: <3a142e750911040440h294da813m4b392da9c1b6e692@mail.gmail.com> From: Paul B Mahol To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: Wireless usb + wep = no usbd_do_request X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 12:40:27 -0000 On 11/4/09, PseudoCylon wrote: > ----- Original Message ---- > >> From: Paul B Mahol >> To: PseudoCylon >> Cc: freebsd-current@freebsd.org >> Sent: Tue, November 3, 2009 5:08:47 AM >> Subject: Re: Wireless usb + wep = no usbd_do_request >> >> On 11/3/09, PseudoCylon wrote: >> > Hi, >> > >> > I'm porting a wireless usb driver (if_run) to freebsd current, and I got >> > stuck. Once I "ifconfig wlan0 wepkey 1:0x... weptxkey 1" I cannot call >> > usbd_do_request() any more. Even ifconfig didn't exit. Chipset supports >> > h/w >> > en/decryption, so cannot write keys on chip. (It works without >> > encryption, >> > by the way.) >> > >> > So, I tried the same thing on another device, linksys wusb54gc with >> > if_rum. >> > It worked fine, but about 3 to 4 min later. (Just left it alone.) It >> > started >> > giving error >> > rum0: could not multi read MAC register: USB_ERR_TIMEOUT and >> > rum0: device timeout >> > when ifconfig wlan0 down, >> > rum0: could not multi write MAC register: USB_ERR_TIMEOUT >> > which means failed on usbd_do_request() (This could be totally different >> > issue.) >> >> I get this one multiple times after card got detached but vap was not >> manually destroyed. >> Recently I did not used if_rum more that 5 min I think(maybe in AP >> mode when I was testing hidden ssid ...) >> >> > Any ideas, patches, or walkaround? >> >> Make sure how locks are handled between net80211, usb and driver itself. > > Thanks for the reply. > > I think that's just simple lock problem, too. Just I don't know what it is. > I tried > IEEE80211_LOCK > IEEE80211_NODE_LOCK > IEEE80211_NODE_ITERATE_LOCK > but I cannot lock or unlock them. (I can lock IF_LOCK.) I just get "panic: > mtx_lock of spin mutex(null)" For example, IEEE80211_LOCK is sleep mutex, > and I can use it in newstate() no problem, but I some how it becomes spin > mutex in key_set(). Once I find what is over writing lock type, I can make > it work. Wish me a luck. Look other freebsd usb drivers for example when un/lock is required, also you need to have you own driver lock - and you need to really know when to use it. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 13:50:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BEF310657C1 for ; Wed, 4 Nov 2009 13:50:25 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id DAD808FC26 for ; Wed, 4 Nov 2009 13:50:24 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-163-243.rz.uni-karlsruhe.de [141.3.163.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id D06848A0DC6; Wed, 4 Nov 2009 14:50:22 +0100 (CET) Message-ID: <4AF1869D.6090304@bsdforen.de> Date: Wed, 04 Nov 2009 14:50:21 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Alexander Best References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Mark Linimon , freebsd-current@freebsd.org, Paul G Webster Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 13:50:25 -0000 Alexander Best wrote: > Paul G Webster schrieb am 2009-11-03: > *lol* just tried this myself and my fdisk output looks just as bad as yours: I think funny fdisk output is not that much of a problem. I normally put a single file system on external drives and don't bother partitioning. This is also a common default for many portable audio players. Heavy file system corruption with every write operation really renders msdosfs completely unusable. Now, I've got to rip my CDs and DVDs under FreeBSD and reboot into Windows to copy music and videos onto my player. This is really annoying for such a trivial use case. And msdosfs is still the default file system for portable devices, so it's an important desktop use case. Even in the business world, where often restrictive networks render USB sticks the only acceptable method of transporting large chunks of data. What I wonder is - are there more people who witness file system corruption upon msdosfs writes (and don't forget that either newfs_msdos or fsck_msdosfs is broken as well, and that fsck_msdosfs certainly does not recognize cross-linked files). The impact is so horrid that I had to reformat my portable player (with Windows) and reinstall the firmware to get it back going. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 13:53:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 416241065694 for ; Wed, 4 Nov 2009 13:53:05 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id F39468FC18 for ; Wed, 4 Nov 2009 13:53:04 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-163-243.rz.uni-karlsruhe.de [141.3.163.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 068B68A0DC6; Wed, 4 Nov 2009 14:53:03 +0100 (CET) Message-ID: <4AF1873F.2060705@bsdforen.de> Date: Wed, 04 Nov 2009 14:53:03 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Mark Linimon References: <4AEBFAA3.9020003@bsdforen.de> <20091103012810.GB31768@lonesome.com> In-Reply-To: <20091103012810.GB31768@lonesome.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Alexander Best , freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 13:53:05 -0000 Mark Linimon wrote: > On Tue, Nov 03, 2009 at 02:03:29AM +0100, Alexander Best wrote: >> i guess the freebsd-fs@ guys know about these problems but don't have >> the time to deal with it. most of them are probably working on zfs. > > AFAIK there are only a handful of people working on ZFS. > > We certainly need more people willing to work on filesystems code. In > general it does have a large learning curve, so it's not as attractive > as some of the other areas. That's probably why, as the kernel has > undergone radical changes (e.g. for SMP) over time, that some of the > fs code has not kept up. Is there material, apart from the code, explaining the concepts behind the FreeBSD file system code? File systems are an interesting topic for anyone who likes to get into low level stuff. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 14:19:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC44F106566B for ; Wed, 4 Nov 2009 14:19:12 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 76B768FC1B for ; Wed, 4 Nov 2009 14:19:12 +0000 (UTC) Received: from bb.ipt.ru ([194.62.233.89]) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1N5gha-0002nU-Do; Wed, 04 Nov 2009 17:19:10 +0300 To: Kostik Belousov References: <65275688@bb.ipt.ru> <20091103154747.GC2331@deviant.kiev.zoral.com.ua> <77755531@h30.sp.ipt.ru> <20091103214032.GF2331@deviant.kiev.zoral.com.ua> From: Boris Samorodov Date: Wed, 04 Nov 2009 17:19:10 +0300 In-Reply-To: <20091103214032.GF2331@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Tue\, 3 Nov 2009 23\:40\:32 +0200") Message-ID: <99188273@bb.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 14:19:12 -0000 On Tue, 3 Nov 2009 23:40:32 +0200 Kostik Belousov wrote: > On Wed, Nov 04, 2009 at 12:37:08AM +0300, Boris Samorodov wrote: > > On Tue, 3 Nov 2009 17:47:47 +0200 Kostik Belousov wrote: > > > On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > > > > Hello List, > > > > > > > > print/acroread8 doesn't work for me at 9-CURRENT: > > > > ----- > > > > % uname -a > > > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15:15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > > > > % sysctl compat.linux > > > > compat.linux.oss_version: 198144 > > > > compat.linux.osrelease: 2.6.16 > > > > compat.linux.osname: Linux > > > > ------ > > > > > > > > Setting security.bsd.map_at_zero to 1 doesn't change anything. There is > > > > nothing at console/log files. Here is the tail of linux_kdump: > > > > ----- > > > > ... > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > 78586 ld-2.9.so RET linux_open JUSTRETURN > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > 78586 ld-2.9.so RET linux_open 4 > > > > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > > > > 78586 ld-2.9.so RET linux_fstat64 0 > > > > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > > > > 78586 ld-2.9.so GIO fd 4 read 96 bytes > > > > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^[b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > > > > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > > > > 78586 ld-2.9.so RET read 96/0x60 > > > > 78586 ld-2.9.so CALL close(0x4) > > > > 78586 ld-2.9.so RET close 0 > > > > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) > > > > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > > > > 78586 ld-2.9.so PSIG SIGSEGV caught handler=0x83814b6 mask=0x0 code=0x0 > > > > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0x8) > > > > 78586 ld-2.9.so RET linux_rt_sigaction 0 > > > > 78586 ld-2.9.so CALL linux_exit_group(0x1) > > > > > It would be interesting to see which address faulted. > > > If not, can you do search for a kernel revision that broke acroread ? > > > Good starting points are r198507 and r198554. > > > > Were those revisions MFCed to RELENG_8_0? I've got the same for 8.0: > > ----- > > % uname -a > > FreeBSD h30.sp.ipt.ru 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Nov 1 18:57:33 MSK 2009 root@h30.sp.ipt.ru:/usr/obj/usr/src/sys/IN > > DUS i386 > > ----- > No. > It might be easier to bisect on releng/8.0 then. OK, I've found out that acroread works at 8-RC1 as of 2009-10-04 (with security.bsd.map_at_zero=1): ----- h31% uname -a 16:24 pts/0 FreeBSD h31.sp.ipt.ru 8.0-RC1 FreeBSD 8.0-RC1 #1: Sun Oct 4 02:19:42 MSD 2009 bsam@h31.sp.ipt.ru:/usr/obj/usr/src/sys/SHURAM i386 h31% sysctl security.bsd.map_at_zero 16:24 pts/0 security.bsd.map_at_zero: 1 ----- Can you give me suspisiuos commits to RELENG_8 to test (I don't have time ATM to do bisect builds)? -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 15:24:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A17F01065672 for ; Wed, 4 Nov 2009 15:24:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 64B8E8FC0A for ; Wed, 4 Nov 2009 15:24:02 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 8885F6D41B; Wed, 4 Nov 2009 15:24:01 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 59752844E9; Wed, 4 Nov 2009 16:24:01 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Kai Gallasch References: <20091031231545.493cee89@boiler.free.de> Date: Wed, 04 Nov 2009 16:24:01 +0100 In-Reply-To: <20091031231545.493cee89@boiler.free.de> (Kai Gallasch's message of "Sat, 31 Oct 2009 23:15:45 +0100") Message-ID: <867hu6gvou.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 15:24:02 -0000 Kai Gallasch writes: > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > When I try to do a make buildworld or make buildkernel the server > reboots without any message left in the logs. The same happens > when building bigger ports (for example ruby18 or perl58) Could it be related to this? What's your CPUID? Author: attilio Date: Wed Nov 4 01:32:59 2009 New Revision: 198868 URL: http://svn.freebsd.org/changeset/base/198868 Log: Opteron rev E family of processor expose a bug where, in very rare ocassions, memory barriers semantic is not honoured by the hardware itself. As a result, some random breakage can happen in uninvestigable ways (for further explanation see at the content of the commit itself). =20=20 As long as just a specific familly is bugged of an entire architecture is broken, a complete fix-up is impratical without harming to some extents the other correct cases. Considering that (and considering the frequency of the bug exposure) just print out a warning message if the affected machine is identified. =20=20 Pointed out by: Samy Al Bahra Help on wordings by: jeff MFC: 3 days Modified: head/sys/amd64/amd64/identcpu.c head/sys/i386/i386/identcpu.c DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 15:36:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA46A106566B for ; Wed, 4 Nov 2009 15:36:24 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 322B58FC15 for ; Wed, 4 Nov 2009 15:36:23 +0000 (UTC) Received: (qmail 16640 invoked from network); 4 Nov 2009 16:36:23 +0100 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 4 Nov 2009 16:36:23 +0100 Date: Wed, 4 Nov 2009 16:36:21 +0100 From: Kai Gallasch To: freebsd-current@freebsd.org Message-ID: <20091104163621.36943807@orwell.free.de> In-Reply-To: <867hu6gvou.fsf@ds4.des.no> References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.18.2; powerpc-apple-darwin9.7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 15:36:24 -0000 Am Wed, 04 Nov 2009 16:24:01 +0100 schrieb Dag-Erling Sm=C3=B8rgrav : > Kai Gallasch writes: > > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > > > When I try to do a make buildworld or make buildkernel the server > > reboots without any message left in the logs. The same happens > > when building bigger ports (for example ruby18 or perl58) >=20 > Could it be related to this? What's your CPUID? Found this in dmesg. Is this the CPUID? "Id =3D 0x100f23" --Kai. CPU: Quad-Core AMD Opteron(tm) Processor 2352 (2100.09-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x100f23 Stepping =3D 3 Features=3D0x178bfbff Features2=3D0x802009 AMD Features=3D0xee400800 AMD Features2=3D0x7ff TSC: P-state invariant real memory =3D 21474836480 (20480 MB) avail memory =3D 20701110272 (19742 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 --=20 If it wasn't for the last minute, nothing would get done. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 15:40:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF2261065692 for ; Wed, 4 Nov 2009 15:40:49 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 79A7F8FC1B for ; Wed, 4 Nov 2009 15:40:49 +0000 (UTC) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 933BB5BA6C; Wed, 4 Nov 2009 16:40:45 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 902F15BA5C; Wed, 4 Nov 2009 16:40:45 +0100 (CET) X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id 6CEFB5CD4A; Wed, 4 Nov 2009 16:40:45 +0100 (CET) Received: from wep4035 ([132.187.37.35]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.2FP1HF244) with ESMTP id 2009110416404428-256135 ; Wed, 4 Nov 2009 16:40:44 +0100 Received: by wep4035 (sSMTP sendmail emulation); Wed, 4 Nov 2009 16:40:44 +0100 Date: Wed, 4 Nov 2009 16:40:44 +0100 From: Alexey Shuvaev To: Dominic Fandrey Message-ID: <20091104154044.GA96964@wep4035.physik.uni-wuerzburg.de> Mail-Followup-To: Dominic Fandrey , Alexander Best , freebsd-current@freebsd.org, Paul G Webster References: <4AF1869D.6090304@bsdforen.de> Mime-Version: 1.0 In-Reply-To: <4AF1869D.6090304@bsdforen.de> User-Agent: Mutt/1.4.2.3i Organization: Universitaet Wuerzburg X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 11/04/2009 04:40:44 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 11/04/2009 04:40:44 PM, Serialize complete at 11/04/2009 04:40:44 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Alexander Best , freebsd-current@freebsd.org, Paul G Webster Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 15:40:50 -0000 On Wed, Nov 04, 2009 at 02:50:21PM +0100, Dominic Fandrey wrote: > Alexander Best wrote: > > Paul G Webster schrieb am 2009-11-03: > > *lol* just tried this myself and my fdisk output looks just as bad as yours: > > I think funny fdisk output is not that much of a problem. > > [snip] > > What I wonder is - are there more people who witness file > system corruption upon msdosfs writes (and don't forget > that either newfs_msdos or fsck_msdosfs is broken as well, > and that fsck_msdosfs certainly does not recognize > cross-linked files). The impact is so horrid that I had > to reformat my portable player (with Windows) and reinstall > the firmware to get it back going. > The relative silence on the mailing list seems to show it is not the common problem... ~> uname -a FreeBSD wep4035 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r198671: Fri Oct 30 16:12:10 CET 2009 root@wep4035:/usr/obj/usr/src/sys/GENERIC amd64 ugen7.2: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7790MB (15954944 512 byte sectors: 255H 63S/T 993C) GEOM: da0: partition 1 does not start on a track boundary. GEOM: da0: partition 1 does not end on a track boundary. ~> gpart show da0 => 63 15954876 da0 MBR (7.6G) 63 8129 - free - (4.0M) 8192 15946752 1 !11 (7.6G) ~> df [snip] /dev/da0s1 7969344 6322272 1647072 79% /home/lexx/mnt ~> mount [snip] /dev/da0s1 on /home/lexx/mnt (msdosfs, local, nosuid, mounted by lexx) This is a microSD card in a USB adaptor. Haven't any problems with it up to date. However I use it more or less carefully by: - trying to use only ASCII characters for filenames (from "C" locale) and avoiding any characters that require escaping in the shell, - never ever detaching it without prior unmount - if it matters I have never run fsck_msdosfs on it. Just 0.02$, Alexey. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 16:47:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE6FC106566C; Wed, 4 Nov 2009 16:47:50 +0000 (UTC) (envelope-from alteriks@gmail.com) Received: from mail.agora.pl (mail.agora.pl [193.42.230.53]) by mx1.freebsd.org (Postfix) with ESMTP id 1E7948FC12; Wed, 4 Nov 2009 16:47:49 +0000 (UTC) Received: from agpost.agora.pl (agpost.agora.pl [10.205.39.149]) by mail.agora.pl (8.13.8/8.11.1) with ESMTP id nA4GllP3024250; Wed, 4 Nov 2009 17:47:47 +0100 Received: from t42.localnet ([10.201.55.193]) by agpost.agora.pl with ESMTP; Wed, 04 Nov 2009 17:47:22 +0100 From: "alteriks@gmail.com" To: Radek =?iso-8859-2?q?Val=E1=B9ek?= , Robert Noland Date: Wed, 4 Nov 2009 17:47:21 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.30-1-686; KDE/4.3.2; i686; ; ) References: <200910291044.21818.alteriks@gmail.com> <4AE96CCA.2080501@buchlovice.org> In-Reply-To: <4AE96CCA.2080501@buchlovice.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: <200911041747.21514.alteriks@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable " X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 16:47:50 -0000 Yesterday I tried installing FreeBSD once more, twice to be frank. I downloaded amd64 8.0-RC2 checked md5 sum. First time I installed it on physical machine. I created script with commands pasted here: http://pastebin.com/f72813264 After that I executed: chroot /zroot mount -t devfs devfs /dev export DESTDIR="" cd /usr/src/sys/boot/ make obj make depend make cd i386/loader make install umount /dev passwd exit cp /boot/zfs/zpool.cache /zroot/boot/zfs/zpool.cache Finally I launched this script: http://pastebin.com/f1449f548 Restart gave me: >GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable I created virtual machine on linux kvm, and added three drives. After starting system boot loader failed to launch with same error. I tried to reinstall FreeBSD under kvm, but it didn't help. Anyone has succeed installing amd64 8.0-RC2 with raidz1 on gpt drives? From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:03:43 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A87310657AB; Wed, 4 Nov 2009 17:03:43 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id AB3098FC19; Wed, 4 Nov 2009 17:03:42 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA4GlMwN079176; Wed, 4 Nov 2009 11:47:22 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA4GlMG0079172; Wed, 4 Nov 2009 16:47:22 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 4 Nov 2009 16:47:22 GMT Message-Id: <200911041647.nA4GlMG0079172@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:03:43 -0000 TB --- 2009-11-04 16:20:23 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-04 16:20:23 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-11-04 16:20:23 - cleaning the object tree TB --- 2009-11-04 16:20:39 - cvsupping the source tree TB --- 2009-11-04 16:20:39 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-11-04 16:21:05 - building world TB --- 2009-11-04 16:21:05 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-04 16:21:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-04 16:21:05 - TARGET=powerpc TB --- 2009-11-04 16:21:05 - TARGET_ARCH=powerpc TB --- 2009-11-04 16:21:05 - TZ=UTC TB --- 2009-11-04 16:21:05 - __MAKE_CONF=/dev/null TB --- 2009-11-04 16:21:05 - cd /src TB --- 2009-11-04 16:21:05 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 4 16:21:07 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/scsi_cmdparse.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_all.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_da.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_sa.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/cam.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/ata/ata_all.c /src/lib/libcam/../../sys/cam/ata/ata_all.c:379: error: conflicting types for 'ata_pm_write_cmd' /src/lib/libcam/../../sys/cam/ata/ata_all.h:106: error: previous declaration of 'ata_pm_write_cmd' was here *** Error code 1 Stop in /src/lib/libcam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-04 16:47:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-04 16:47:22 - ERROR: failed to build world TB --- 2009-11-04 16:47:22 - 1150.63 user 261.07 system 1618.67 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:18:13 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F411065692; Wed, 4 Nov 2009 17:18:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id ABE218FC1B; Wed, 4 Nov 2009 17:18:12 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA4H1moF077794; Wed, 4 Nov 2009 12:01:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA4H1mBr077792; Wed, 4 Nov 2009 17:01:48 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 4 Nov 2009 17:01:48 GMT Message-Id: <200911041701.nA4H1mBr077792@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:18:13 -0000 TB --- 2009-11-04 16:37:54 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-04 16:37:54 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-11-04 16:37:54 - cleaning the object tree TB --- 2009-11-04 16:38:09 - cvsupping the source tree TB --- 2009-11-04 16:38:09 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-11-04 16:38:35 - building world TB --- 2009-11-04 16:38:35 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-04 16:38:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-04 16:38:35 - TARGET=sparc64 TB --- 2009-11-04 16:38:35 - TARGET_ARCH=sparc64 TB --- 2009-11-04 16:38:35 - TZ=UTC TB --- 2009-11-04 16:38:35 - __MAKE_CONF=/dev/null TB --- 2009-11-04 16:38:35 - cd /src TB --- 2009-11-04 16:38:35 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 4 16:38:36 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/scsi_cmdparse.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_all.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_da.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_sa.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/cam.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/ata/ata_all.c /src/lib/libcam/../../sys/cam/ata/ata_all.c:379: error: conflicting types for 'ata_pm_write_cmd' /src/lib/libcam/../../sys/cam/ata/ata_all.h:106: error: previous declaration of 'ata_pm_write_cmd' was here *** Error code 1 Stop in /src/lib/libcam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-04 17:01:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-04 17:01:48 - ERROR: failed to build world TB --- 2009-11-04 17:01:48 - 1070.16 user 255.82 system 1433.70 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:21:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDEDE106566C for ; Wed, 4 Nov 2009 17:21:04 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 7DBA98FC1D for ; Wed, 4 Nov 2009 17:21:04 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 1940C48A9A; Wed, 4 Nov 2009 17:21:03 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hPEuy0saB+Vs; Wed, 4 Nov 2009 17:20:59 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 883A348A78; Wed, 4 Nov 2009 17:20:58 +0000 (GMT) Message-ID: <4AF1B7BE.2010402@tomjudge.com> Date: Wed, 04 Nov 2009 17:19:58 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Hans Petter Selasky References: <4AE85740.8010003@tomjudge.com> <200910281723.17481.hselasky@c2i.net> In-Reply-To: <200910281723.17481.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Andrew Thompson Subject: Re: USB Attach Failures (USB_ERR_STALLED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:21:04 -0000 Hans Petter Selasky wrote: > On Wednesday 28 October 2009 15:37:52 Tom Judge wrote: >> Hi, >> >> As of yesterday (not yesterdays current) I have been having issues when >> booting my D630 on the dock and having the USB devices attach correctly, >> this was all working before the weekend and I have not changed >> anything. My src tree is at r197709. >> >> If I disconnect the usb keyboard and mouse then re attach them to the >> same ports on the dock they are detected correctly. >> >> Is this a known issue? >> >> Tom > > Hi, > > Your issue is possibly related to some recent BIOS USB handover patches. Try > disabling USB in the BIOS. Else I think Andrew has more details. > > --HPS > Sorry for the late follow up. I have not changed any settings or updated and this problem has magically gone away. For some reason it happened for 2/3 days and now it has stopped. Tom From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:26:21 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAAF31065676; Wed, 4 Nov 2009 17:26:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 58A6D8FC0A; Wed, 4 Nov 2009 17:26:21 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA4H9sje002724; Wed, 4 Nov 2009 12:09:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA4H9saj002723; Wed, 4 Nov 2009 17:09:54 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 4 Nov 2009 17:09:54 GMT Message-Id: <200911041709.nA4H9saj002723@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:26:21 -0000 TB --- 2009-11-04 16:47:22 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-04 16:47:22 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-11-04 16:47:22 - cleaning the object tree TB --- 2009-11-04 16:47:34 - cvsupping the source tree TB --- 2009-11-04 16:47:34 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-11-04 16:47:59 - building world TB --- 2009-11-04 16:47:59 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-04 16:47:59 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-04 16:47:59 - TARGET=sun4v TB --- 2009-11-04 16:47:59 - TARGET_ARCH=sparc64 TB --- 2009-11-04 16:47:59 - TZ=UTC TB --- 2009-11-04 16:47:59 - __MAKE_CONF=/dev/null TB --- 2009-11-04 16:47:59 - cd /src TB --- 2009-11-04 16:47:59 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 4 16:47:59 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/scsi_cmdparse.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_all.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_da.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/scsi/scsi_sa.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/cam.c cc -O2 -pipe -I/src/lib/libcam -I/src/lib/libcam/../../sys -std=gnu99 -fstack-protector -c /src/lib/libcam/../../sys/cam/ata/ata_all.c /src/lib/libcam/../../sys/cam/ata/ata_all.c:379: error: conflicting types for 'ata_pm_write_cmd' /src/lib/libcam/../../sys/cam/ata/ata_all.h:106: error: previous declaration of 'ata_pm_write_cmd' was here *** Error code 1 Stop in /src/lib/libcam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-04 17:09:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-04 17:09:54 - ERROR: failed to build world TB --- 2009-11-04 17:09:54 - 1060.71 user 245.90 system 1351.91 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:22:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF7AC1065697 for ; Wed, 4 Nov 2009 17:22:04 +0000 (UTC) (envelope-from nwf@cs.jhu.edu) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.freebsd.org (Postfix) with ESMTP id 95C668FC24 for ; Wed, 4 Nov 2009 17:22:04 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.3/8.14.3) with ESMTP id nA4HM37G018424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 4 Nov 2009 12:22:03 -0500 (EST) Received: from gradx.cs.jhu.edu (localhost.localdomain [127.0.0.1]) by gradx.cs.jhu.edu (8.14.2/8.13.1) with ESMTP id nA4HM37n011176 for ; Wed, 4 Nov 2009 12:22:03 -0500 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.2/8.13.8/Submit) id nA4HM3is011175 for freebsd-current@freebsd.org; Wed, 4 Nov 2009 12:22:03 -0500 Date: Wed, 4 Nov 2009 12:22:03 -0500 From: Nathaniel W Filardo To: freebsd-current@freebsd.org Message-ID: <20091104172203.GJ19125@gradx.cs.jhu.edu> References: <20091029213929.GD19125@gradx.cs.jhu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i57Ucs80xkCVE1Ce" Content-Disposition: inline In-Reply-To: <20091029213929.GD19125@gradx.cs.jhu.edu> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Wed, 04 Nov 2009 17:28:09 +0000 Subject: Re: SATA disk error and hang until "atacontrol reinit" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:22:05 -0000 --i57Ucs80xkCVE1Ce Content-Type: text/plain; charset=us-ascii Content-Disposition: inline As a follow up, I had this happen again, without rebooting after running "atacontrol reinit ata4". That worked a few times, but the interval between failed requests was very small... At some point, reiniting the channel simply said "no devices attached" and I went and bought a new disk, fearing the worst. Placing that on the channel, I attempted "atacontrol reinit" again and it still refused to see the new disk. I tested both the new and old disks with a different controller and they worked fine. On the suggestion of ##freebsd, I ran "atacontrol detach ata4" and "atacontrol attach ata4"; the former completed, the latter produced this (via serial console): hydra# atacontrol attach ata4 ata4: [ITHREAD] 60201-4533^[[2;2~Master: no device present Slave: no device present ast data access mmu miss t ra p: f cpuid = 0 which I assume really meant to be "trap: fast data access mmu miss". I amn't sure what that means, but I have this lovely multi-gig core file now... which is potentially of little utility since I get told "GDB can't read core files on this machine." but if somebody wants something out of it, just ask. In any case, I powered the machine off, put the old disk back, and rebooted and am now scrubbing the RAIDZ, but it sees the old disk just fine. Suggestions? --nwf; --i57Ucs80xkCVE1Ce Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrxuDsACgkQTeQabvr9Tc+SZgCaAzh1t0lK7kmij1nR+yIQY/3N o10An3d6hptb9u5p4mcbmGdww720oxIn =I1qj -----END PGP SIGNATURE----- --i57Ucs80xkCVE1Ce-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:29:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 681D71065676 for ; Wed, 4 Nov 2009 17:29:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id D47D18FC0A for ; Wed, 4 Nov 2009 17:29:42 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA4HTYMa046720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Nov 2009 19:29:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA4HTYst040669; Wed, 4 Nov 2009 19:29:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA4HTV93040668; Wed, 4 Nov 2009 19:29:31 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 4 Nov 2009 19:29:31 +0200 From: Kostik Belousov To: Boris Samorodov Message-ID: <20091104172931.GI2331@deviant.kiev.zoral.com.ua> References: <65275688@bb.ipt.ru> <20091103154747.GC2331@deviant.kiev.zoral.com.ua> <77755531@h30.sp.ipt.ru> <20091103214032.GF2331@deviant.kiev.zoral.com.ua> <99188273@bb.ipt.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DwoPkXS38qd3dnhB" Content-Disposition: inline In-Reply-To: <99188273@bb.ipt.ru> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:29:43 -0000 --DwoPkXS38qd3dnhB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 04, 2009 at 05:19:10PM +0300, Boris Samorodov wrote: > On Tue, 3 Nov 2009 23:40:32 +0200 Kostik Belousov wrote: > > On Wed, Nov 04, 2009 at 12:37:08AM +0300, Boris Samorodov wrote: > > > On Tue, 3 Nov 2009 17:47:47 +0200 Kostik Belousov wrote: > > > > On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > > > > > Hello List, > > > > >=20 > > > > > print/acroread8 doesn't work for me at 9-CURRENT: > > > > > ----- > > > > > % uname -a > > > > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov = 2 15:15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > > > > > % sysctl compat.linux > > > > > compat.linux.oss_version: 198144 > > > > > compat.linux.osrelease: 2.6.16 > > > > > compat.linux.osname: Linux > > > > > ------ > > > > >=20 > > > > > Setting security.bsd.map_at_zero to 1 doesn't change anything. Th= ere is > > > > > nothing at console/log files. Here is the tail of linux_kdump: > > > > > ----- > > > > > ... > > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a02= 34dc04d93e9475cbf44698a-x86.cache-2" > > > > > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e947= 5cbf44698a-x86.cache-2" > > > > > 78586 ld-2.9.so RET linux_open JUSTRETURN > > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b= 0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93= e9475cbf44698a-x86.cache-2" > > > > > 78586 ld-2.9.so RET linux_open 4 > > > > > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > > > > > 78586 ld-2.9.so RET linux_fstat64 0 > > > > > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > > > > > 78586 ld-2.9.so GIO fd 4 read 96 bytes > > > > > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0= \0\^[b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > > > > > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > > > > > 78586 ld-2.9.so RET read 96/0x60 > > > > > 78586 ld-2.9.so CALL close(0x4) > > > > > 78586 ld-2.9.so RET close 0 > > > > > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,= 0) > > > > > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > > > > > 78586 ld-2.9.so PSIG SIGSEGV caught handler=3D0x83814b6 mask=3D= 0x0 code=3D0x0 > > > > > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb= 64,0x8) > > > > > 78586 ld-2.9.so RET linux_rt_sigaction 0 > > > > > 78586 ld-2.9.so CALL linux_exit_group(0x1) > > >=20 > > > > It would be interesting to see which address faulted. > > > > If not, can you do search for a kernel revision that broke acroread= ? > > > > Good starting points are r198507 and r198554. > > >=20 > > > Were those revisions MFCed to RELENG_8_0? I've got the same for 8.0: > > > ----- > > > % uname -a > > > FreeBSD h30.sp.ipt.ru 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Nov 1 18:57:33= MSK 2009 root@h30.sp.ipt.ru:/usr/obj/usr/src/sys/IN > > > DUS i386 > > > ----- > > No. > > It might be easier to bisect on releng/8.0 then. >=20 > OK, I've found out that acroread works at 8-RC1 as of 2009-10-04 > (with security.bsd.map_at_zero=3D1): > ----- > h31% uname -a 16:24= pts/0 > FreeBSD h31.sp.ipt.ru 8.0-RC1 FreeBSD 8.0-RC1 #1: Sun Oct 4 02:19:42 MSD= 2009 bsam@h31.sp.ipt.ru:/usr/obj/usr/src/sys/SHURAM i386 > h31% sysctl security.bsd.map_at_zero 16:24= pts/0 > security.bsd.map_at_zero: 1 > ----- >=20 > Can you give me suspisiuos commits to RELENG_8 to test (I don't have > time ATM to do bisect builds)? I do not have good guess. I would put a finger in the direction of the imgact_elf.c changes. But, since the issue appears at run-time, after the binary started, I doubt it. --DwoPkXS38qd3dnhB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrxufsACgkQC3+MBN1Mb4gA+gCfUtK7eeZ1a8YK2bNDXHbBjFsJ J7kAnRhvJZixNK5VhKGqC12dIW51g6UK =VTKM -----END PGP SIGNATURE----- --DwoPkXS38qd3dnhB-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:40:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81FB21065670 for ; Wed, 4 Nov 2009 17:40:25 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 15FCA8FC1A for ; Wed, 4 Nov 2009 17:40:24 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ct4AtyFzAYoA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=gESKfaxyNQyt20MRj-kA:9 a=Bej4_5zLfvxAHl6tz3CoGy046fkA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1312328959; Wed, 04 Nov 2009 18:40:20 +0100 From: Hans Petter Selasky To: Tom Judge Date: Wed, 4 Nov 2009 18:39:25 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4AE85740.8010003@tomjudge.com> <200910281723.17481.hselasky@c2i.net> <4AF1B7BE.2010402@tomjudge.com> In-Reply-To: <4AF1B7BE.2010402@tomjudge.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911041839.25641.hselasky@c2i.net> Cc: freebsd-current@freebsd.org, Andrew Thompson Subject: Re: USB Attach Failures (USB_ERR_STALLED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:40:25 -0000 On Wednesday 04 November 2009 18:19:58 Tom Judge wrote: > Sorry for the late follow up. > > I have not changed any settings or updated and this problem has > magically gone away. For some reason it happened for 2/3 days and now > it has stopped. > > > Tom Ok. No problem. --HPS From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 21:32:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CF71106566C for ; Wed, 4 Nov 2009 21:32:03 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9F8AB8FC0C for ; Wed, 4 Nov 2009 21:32:02 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N5nSS-00082A-GI for freebsd-current@freebsd.org; Wed, 04 Nov 2009 22:32:00 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:32:00 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:32:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Wed, 04 Nov 2009 13:31:35 -0800 Lines: 44 Message-ID: <4AF1F2B7.5040803@yahoo.com> References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: <20091104163621.36943807@orwell.free.de> Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 21:32:03 -0000 Kai Gallasch wrote: > Am Wed, 04 Nov 2009 16:24:01 +0100 > schrieb Dag-Erling Smørgrav : > >> Kai Gallasch writes: >>> I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. >>> >>> When I try to do a make buildworld or make buildkernel the server >>> reboots without any message left in the logs. The same happens >>> when building bigger ports (for example ruby18 or perl58) >> Could it be related to this? What's your CPUID? > > Found this in dmesg. Is this the CPUID? "Id = 0x100f23" That's generation 16 model 2 stepping 3. This errata only effects generation 0xe or 15. BTW, I have the same processor/stepping/Mhz in my system, but only a single physical processor. > --Kai. > > > CPU: Quad-Core AMD Opteron(tm) Processor 2352 (2100.09-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 > Features=0x178bfbff > Features2=0x802009 > AMD > Features=0xee400800 > AMD > Features2=0x7ff > TSC: P-state invariant real memory = 21474836480 (20480 MB) avail > memory = 20701110272 (19742 MB) ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > FreeBSD/SMP: 2 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > > From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 21:35:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 109AA1065672 for ; Wed, 4 Nov 2009 21:35:06 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BEF988FC0C for ; Wed, 4 Nov 2009 21:35:05 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N5nVP-0000zn-Mj for freebsd-current@freebsd.org; Wed, 04 Nov 2009 22:35:03 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:35:03 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:35:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Wed, 04 Nov 2009 13:34:00 -0800 Lines: 45 Message-ID: References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: <20091104163621.36943807@orwell.free.de> Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 21:35:06 -0000 Kai Gallasch wrote: > Am Wed, 04 Nov 2009 16:24:01 +0100 > schrieb Dag-Erling Smørgrav : > >> Kai Gallasch writes: >>> I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. >>> >>> When I try to do a make buildworld or make buildkernel the server >>> reboots without any message left in the logs. The same happens >>> when building bigger ports (for example ruby18 or perl58) >> Could it be related to this? What's your CPUID? > > Found this in dmesg. Is this the CPUID? "Id = 0x100f23" That's generation 16 (0xf) model 2, stepping 3. This errata apparently only effects gen 15 (0xe) and some pre-release -- never released to public (0xf). I have the same processor in my system btw. > > --Kai. > > > CPU: Quad-Core AMD Opteron(tm) Processor 2352 (2100.09-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 > Features=0x178bfbff > Features2=0x802009 > AMD > Features=0xee400800 > AMD > Features2=0x7ff > TSC: P-state invariant real memory = 21474836480 (20480 MB) avail > memory = 20701110272 (19742 MB) ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > FreeBSD/SMP: 2 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > > From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 21:46:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B8CE106566C for ; Wed, 4 Nov 2009 21:46:15 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 162078FC08 for ; Wed, 4 Nov 2009 21:46:14 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N5ng2-0006Gu-7X for freebsd-current@freebsd.org; Wed, 04 Nov 2009 22:46:02 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:46:02 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 22:46:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Wed, 04 Nov 2009 13:45:32 -0800 Lines: 28 Message-ID: References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 21:46:15 -0000 Mark Atkinson wrote: > Kai Gallasch wrote: >> Am Wed, 04 Nov 2009 16:24:01 +0100 >> schrieb Dag-Erling Smørgrav : >> >>> Kai Gallasch writes: >>>> I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. >>>> >>>> When I try to do a make buildworld or make buildkernel the server >>>> reboots without any message left in the logs. The same happens >>>> when building bigger ports (for example ruby18 or perl58) >>> Could it be related to this? What's your CPUID? > >> Found this in dmesg. Is this the CPUID? "Id = 0x100f23" > > That's generation 16 (0xf) model 2, stepping 3. This errata apparently > only effects gen 15 (0xe) and some pre-release -- never released to > public (0xf). I have the same processor in my system btw. sorry for the double wrong posting. I see several webpages refer to 15 as f and 16 as f. usr/ports/misc/cpuid refers to it as 15. The pages referenced via the bugzilla entry in the commit refer to it as 0xf but between 32 and 63. Does the model 2 correctly put us in the range in the commit 0x20 and 0x3f? (i.e. stepping is included?) From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 21:51:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04B1C1065672 for ; Wed, 4 Nov 2009 21:51:47 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.211.178]) by mx1.freebsd.org (Postfix) with ESMTP id AE7358FC0A for ; Wed, 4 Nov 2009 21:51:46 +0000 (UTC) Received: by ywh8 with SMTP id 8so7028647ywh.3 for ; Wed, 04 Nov 2009 13:51:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=Yxd0rMlpPH2qFIYMIM/it1R1qAJsnqHEXatz5QycMNY=; b=p3s1eSKqxkNKXJUHP06uu1HqXEZQtQJJ25Rbku9d1Ujo04gvEAnuMLQc9I5y+DWGzL WksCbXuJ2fgPu88q+hZjSVwdGS7gJ3hiy6RYW+65obXyfX6FBiGleaG/DYM9PoUQJPOM S+EUShgh36ncI8qm9737v+UZarRbwU9IsnORs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=OO2OSJJiZhA7RyLQUhKom/H3Xy22EVfhUZhOWnwbjRSYYKaCpMV1CTL/KiSGj1y0Vu 599M+ZoC00TdVPzz1zwjgEX6tc2bJCoCmSfpoB2c5DvyRSj8UcZu5lar1q/hz+aRZeBk GkiNBtZjwV4eHEBBRVQ5RmRtYhZs4KjnbXBrg= Received: by 10.150.238.18 with SMTP id l18mr3753667ybh.14.1257371505883; Wed, 04 Nov 2009 13:51:45 -0800 (PST) Received: from ?10.0.3.231? (pool-173-70-28-149.nwrknj.fios.verizon.net [173.70.28.149]) by mx.google.com with ESMTPS id 15sm261562gxk.0.2009.11.04.13.51.44 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Nov 2009 13:51:45 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: "S.N.Grigoriev" In-Reply-To: <44591257331450@webmail38.yandex.ru> References: <44591257331450@webmail38.yandex.ru> Content-Type: text/plain; charset="UTF-8" Date: Wed, 04 Nov 2009 16:51:39 -0500 Message-Id: <1257371499.1624.10.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 21:51:47 -0000 On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > Hi list, > > I can confirm I've seen the same problem. After upgrading from 7-stable > to 8.0-RC2 my machine just reboots during 'make buildworld' without > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > work for me. My machine reboots every time I try to build world. > I don't think I have a hardware problem: under 7-stable I can build > world/kernel for both 7-stable and 8.0-RC2 without problems. > Is it by any chance possible that you have 'debug.debugger_on_panic' set to '0' and no valid dump device configured? -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 22:37:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59D16106566C for ; Wed, 4 Nov 2009 22:37:18 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 147078FC1A for ; Wed, 4 Nov 2009 22:37:18 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N5oTb-0004kR-RJ for freebsd-current@freebsd.org; Wed, 04 Nov 2009 23:37:15 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 23:37:15 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Nov 2009 23:37:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Wed, 04 Nov 2009 14:36:46 -0800 Lines: 36 Message-ID: References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 22:37:18 -0000 Mark Atkinson wrote: > Mark Atkinson wrote: >> Kai Gallasch wrote: >>> Am Wed, 04 Nov 2009 16:24:01 +0100 >>> schrieb Dag-Erling Smørgrav : >>> >>>> Kai Gallasch writes: >>>>> I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. >>>>> >>>>> When I try to do a make buildworld or make buildkernel the server >>>>> reboots without any message left in the logs. The same happens >>>>> when building bigger ports (for example ruby18 or perl58) >>>> Could it be related to this? What's your CPUID? >>> Found this in dmesg. Is this the CPUID? "Id = 0x100f23" >> That's generation 16 (0xf) model 2, stepping 3. This errata apparently >> only effects gen 15 (0xe) and some pre-release -- never released to >> public (0xf). I have the same processor in my system btw. > > sorry for the double wrong posting. I see several webpages refer to 15 > as f and 16 as f. usr/ports/misc/cpuid refers to it as 15. > > The pages referenced via the bugzilla entry in the commit refer to it as > 0xf but between 32 and 63. Does the model 2 correctly put us in the > range in the commit 0x20 and 0x3f? (i.e. stepping is included?) I'll answer my own question, no: http://support.amd.com/us/Processor_TechDocs/25481.pdf Although the some of the posts in http://bugzilla.kernel.org/show_bug.cgi?id=11305 indicate any model < 0x40. Someone must have actually narrowed the range. From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 23:47:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D61F6106568F for ; Wed, 4 Nov 2009 23:47:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.211.178]) by mx1.freebsd.org (Postfix) with ESMTP id 8D5258FC21 for ; Wed, 4 Nov 2009 23:47:26 +0000 (UTC) Received: by ywh8 with SMTP id 8so7107132ywh.3 for ; Wed, 04 Nov 2009 15:47:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=S2anNK55a5P0VZ2MVd7jErC5tOmDTbUst4TkQ7C6MzA=; b=xVSusNtVbUfEODdY/+f+CqCt3nXA/Wfe4uNFcYXEMDjjkkuvNsrNsWHc47KzM7qHtf I7RyIQu/2cTXwHNingqDG3Qw5NESYVVFknkQmGIvl0LQRK8h0OYWRcq1Tr8d7+cdO+kO h5fww5ccXsSKV5e1gj0xOtAgJD+ViQpcGdbvY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ZvLC7edtuYe97TGxrzkNu3fOVQBCBRrFMmm4YDYCO9eKMQAn7Qw4gYXGfNC9bxGUzd CiXrF+zZ6tQj+Tqnu6BLqqzxhyHBru30vlMrGArtJ/eCttWptmxrut1oPXanazhAD5A8 dYU5oKMhBke9ySOCgSLSOqQLzcm/RULEClwAs= MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.101.133.35 with SMTP id k35mr1959048ann.100.1257378445971; Wed, 04 Nov 2009 15:47:25 -0800 (PST) In-Reply-To: References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Date: Thu, 5 Nov 2009 07:47:25 +0800 X-Google-Sender-Auth: 01b48e4f453bfdf5 Message-ID: From: Adrian Chadd To: Mark Atkinson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 23:47:26 -0000 2009/11/5 Mark Atkinson : > > I'll answer my own question, no: > > http://support.amd.com/us/Processor_TechDocs/25481.pdf > > Although the some of the posts in > > http://bugzilla.kernel.org/show_bug.cgi?id=3D11305 > > indicate any model < 0x40. =A0Someone must have actually narrowed the ran= ge. Is there a FreeBSD PR or errata URL which can be linked to instead, complete with copies of the above in it? Adrian From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 00:03:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDDEC106566C for ; Thu, 5 Nov 2009 00:03:56 +0000 (UTC) (envelope-from joe@via.net) Received: from smtp2.via.net (smtp2.via.net [209.81.9.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8D9068FC1B for ; Thu, 5 Nov 2009 00:03:56 +0000 (UTC) Received: from mail.via.net (mail.via.net [209.81.9.12]) by smtp2.via.net (8.14.1/8.12.11-VIANET) with ESMTP id nA4NJKoH001429 for ; Wed, 4 Nov 2009 15:19:20 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.95.2 at smtp2.via.net Received: from [209.81.2.70] ([209.81.2.70]) by mail.via.net (8.14.1/8.12.11-VIANET) with ESMTP id nA4NJDjd012121 for ; Wed, 4 Nov 2009 15:19:20 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.95.2 at mail.via.net From: joe mcguckin Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 4 Nov 2009 15:19:03 -0800 Message-Id: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> To: freebsd-current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (smtp2.via.net [209.81.9.14]); Wed, 04 Nov 2009 15:19:21 -0800 (PST) Subject: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 00:03:56 -0000 I'm interested inb putting together a file server with lots of disk. What's the state of ZFS? Is it ready for production use? Thanks, Joe Joe McGuckin ViaNet Communications joe@via.net 650-207-0372 cell 650-213-1302 office 650-969-2124 fax From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 00:15:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF7EB1065679 for ; Thu, 5 Nov 2009 00:15:07 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 842FB8FC0A for ; Thu, 5 Nov 2009 00:15:06 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,682,1249250400"; d="scan'208";a="17638119" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 05 Nov 2009 01:15:05 +0100 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id B1D001B07BE; Thu, 5 Nov 2009 01:15:05 +0100 (CET) Date: Thu, 05 Nov 2009 01:15:05 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 00:15:08 -0000 should be: http://www.freebsd.org/news/status/report-2009-04-2009-09.html#FreeBSD/ZFS alex From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 00:16:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA665106566C for ; Thu, 5 Nov 2009 00:16:54 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay2.uni-muenster.de (ZIVM-EXRELAY2.UNI-MUENSTER.DE [128.176.192.15]) by mx1.freebsd.org (Postfix) with ESMTP id 709CB8FC24 for ; Thu, 5 Nov 2009 00:16:54 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,682,1249250400"; d="scan'208";a="228101154" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay2.uni-muenster.de with ESMTP; 05 Nov 2009 01:16:52 +0100 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id BBA441B07BE; Thu, 5 Nov 2009 01:16:52 +0100 (CET) Date: Thu, 05 Nov 2009 01:16:52 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: panic when mounting device >= 2 times X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 00:16:54 -0000 any recent developments concerning this problem? here's the pr btw: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139718 alex From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 03:34:41 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0958106566B for ; Thu, 5 Nov 2009 03:34:41 +0000 (UTC) (envelope-from quakelee@geekcn.org) Received: from tarsier.geekcn.org (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5DBF48FC18 for ; Thu, 5 Nov 2009 03:34:41 +0000 (UTC) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id E48CF55CD4CF; Thu, 5 Nov 2009 11:34:39 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id MC-Vs8Qevz+u; Thu, 5 Nov 2009 11:34:34 +0800 (CST) Received: from qld630 (unknown [219.142.100.195]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id F15F555CD4C6; Thu, 5 Nov 2009 11:34:33 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=geekcn.org; c=nofws; q=dns; h=content-type:to:cc:subject:references:date:mime-version: content-transfer-encoding:from:organization:message-id:in-reply-to:user-agent; b=CtUzEmfCYyyUfAEuttgvjWHJFS8z1pHYLQHTT4dy4ozytHduyZUfgQKXxk2+RwJrJ JZ9qh3DuK2peXsDCYPUAA== Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Scott Long" , "Marcel Moolenaar" References: <20091002150931.K35591@pooker.samsco.org> <200910031230.51044.hselasky@c2i.net> <200910031800.24896.hselasky@c2i.net> <30F3E66A-4A69-46CE-96F4-44B4049722E2@samsco.org> Date: Thu, 05 Nov 2009 11:34:33 +0800 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Chao Shin" Organization: GeekCN Message-ID: In-Reply-To: <30F3E66A-4A69-46CE-96F4-44B4049722E2@samsco.org> User-Agent: Opera Mail/10.01 (Win32) Cc: freebsd-current@freebsd.org, Hans Petter Selasky Subject: Re: [PATCH] Fix for USB media not found at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 03:34:42 -0000 在 Sun, 04 Oct 2009 07:52:45 +0800，Scott Long 写道: Hi all Is there any newer patch/workarounds available? > On Oct 3, 2009, at 12:51 PM, Marcel Moolenaar wrote: > >> >> On Oct 3, 2009, at 9:00 AM, Hans Petter Selasky wrote: >> >>> On Saturday 03 October 2009 17:05:35 Scott Long wrote: >>>> On Oct 3, 2009, at 4:30 AM, Hans Petter Selasky wrote: >>>>> On Saturday 03 October 2009 10:19:57 Scott Long wrote: >>>>>> config_intrhook system will sleep after all >>>>> >>>>> Then why do you need the intr hook callback? >>>> >>>> The config_intrhook lets you know that interrupts are enabled, the >>>> scheduler is running, and mountroot hasn't run yet. It provides a >>>> very convenient and standard way to do exactly what we want with USB >>>> enumeration. >>> >>> Hi, >>> >>> The root HUB attach and explore code is already running from a separate >>> thread, so won't that be superfluous? I mean, the HUB explore code for >>> any USB >>> HUB will not run until the scheduler is running anyway. >>> >>> In my opinion delaying the system until the boot disk is present is >>> just not >>> good. We should rather be event driven, so that every time a new disk >>> becomes >>> present it checks it for mountroot. >>> >>> while (1) { >>> if (mountroot is successful) >>> break; >>> if (ctrl+c is pressed) >>> manual_mountroot(); >>> printf("Waiting 1 second for root-disk to appear. Press CTRL+C to >>> abort.\n"); >>> sleep(1); >>> } >> >> Yes. >> >> The mount root code should keep a list of potential root devices to try >> and >> it should try a device as soon as it appears. The current approach to >> block >> the root mount simply because we want everything to be discovered >> before we >> try to mount the root is preventing fast boots -- such as when the root >> is >> a memory disk and you don't need to wait for anything... >> >> Put differently: it's rather odd to hold off the root mount when the >> root >> device is already present... >> >> An approach like this also allows one to indefinitely wait for the root >> device, which is a good feature to have... >> >> > > When /etc/rc tries to mount everything in the fstab, it'll fail the boot > if some of the devices haven't arrived in time. An argument can be made > for fixing that as well, but we're starting to get beyond on the scope > of fixing what is needed for 8.0-RELEASE. > > Scott > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- The Power to Serve From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 06:11:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF405106568B for ; Thu, 5 Nov 2009 06:11:29 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from mail.rubicom.hu (mail.rubicom.hu [89.147.80.28]) by mx1.freebsd.org (Postfix) with ESMTP id 77BE98FC0C for ; Thu, 5 Nov 2009 06:11:29 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.rubicom.hu) by mail.rubicom.hu with smtp (Exim 4.63) (envelope-from ) id 1N5vZ9-0007EX-75 for freebsd-current@freebsd.org; Thu, 05 Nov 2009 07:11:27 +0100 Received: from ip59935289.rubicom.hu ([89.147.82.137] helo=baranyfelhocske.buza.adamsfamily.xx) by mail.rubicom.hu with esmtp (Exim 4.63) (envelope-from ) id 1N5vZ8-0007EQ-Va for freebsd-current@freebsd.org; Thu, 05 Nov 2009 07:11:27 +0100 Received: from baranyfelhocske.buza.adamsfamily.xx (localhost [127.0.0.1]) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3) with ESMTP id nA56BQIK002228 for ; Thu, 5 Nov 2009 07:11:26 +0100 (CET) (envelope-from sziszi@bsd.hu) Received: (from sziszi@localhost) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3/Submit) id nA56BQPn002227 for freebsd-current@freebsd.org; Thu, 5 Nov 2009 07:11:26 +0100 (CET) (envelope-from sziszi@bsd.hu) X-Authentication-Warning: baranyfelhocske.buza.adamsfamily.xx: sziszi set sender to sziszi@bsd.hu using -f Date: Thu, 5 Nov 2009 07:11:26 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Message-ID: <20091105061126.GA1839@baranyfelhocske.buza.adamsfamily.xx> References: <4AF1869D.6090304@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF1869D.6090304@bsdforen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 06:11:30 -0000 Hello, On Wed, Nov 04, 2009 at 02:50:21PM +0100, Dominic Fandrey wrote: > What I wonder is - are there more people who witness file > system corruption upon msdosfs writes (and don't forget > that either newfs_msdos or fsck_msdosfs is broken as well, > and that fsck_msdosfs certainly does not recognize > cross-linked files). The impact is so horrid that I had > to reformat my portable player (with Windows) and reinstall > the firmware to get it back going. Well, this is of course only anecdotal, but I do not witness corruption with any of my USB-attached umass devices. (I no longer have a floppy drive, and I do not have a FAT partition on my HDD either, so I cannot test that). I am using 9.0-CURRENT, rev 198667 (but the problem did not show also on earlier revs) The devices that I use on and off: - Meizu M3 Music Card audio player - Cowon iaudio D2 audio player (According to user forums, this one is particularly sensitive to fs corruption) - various USB sticks, most notably a Kingston Data Traveller 4G (I believe) - Even the occasional memory stick, or SD card in card reader However, I must also state that I never used fsck_msdosfs in the last few years. Neither have I formatted any FAT file systems under FreeBSD for years. Also, I always unmount the devices before removing them. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 06:47:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01DAA106566B for ; Thu, 5 Nov 2009 06:47:25 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 888A48FC0C for ; Thu, 5 Nov 2009 06:47:24 +0000 (UTC) Received: by bwz5 with SMTP id 5so476334bwz.3 for ; Wed, 04 Nov 2009 22:47:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vJARknIf4rpbKtI/C7NiRUJsjGyfPn84ulk2t9qlvcA=; b=SThxS5bgC5jcE5MDQLgKKlKZI5FsFT2R/x3vJWievhWT5f2Ski5O3Tg5Ozj97lJtPH EBuU3yGV4Bk2uyhMQP077sKPN1LCVfYRHmQwNHANIEJJa4Kvowk95lHZ9Xxr1zxMZ+uo t9lkvpkp1m8VNkyAimwRbRtEXzQx0k0NBhsFE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ESu4o448W4rKVOFc+mC6j/T+JbOCEerydyAPvtzJby2GGrXPAKOItmtEPFH7bvaoMB GEeiUsiLGhCC2qjYSRcTPjx6YKf0bfcGasxwgahn4yVufsL7JnH+bOQRRv+tG+LN5OXO sRuy85ETaZSJaCYBgJ8LIW+ikNtL6PpoYDvYg= MIME-Version: 1.0 Received: by 10.204.32.213 with SMTP id e21mr2585904bkd.34.1257403643395; Wed, 04 Nov 2009 22:47:23 -0800 (PST) In-Reply-To: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> Date: Thu, 5 Nov 2009 08:47:23 +0200 Message-ID: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> From: Artis Caune To: joe mcguckin Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 06:47:25 -0000 2009/11/5 joe mcguckin : > I'm interested inb putting together a file server with lots of disk. > > What's the state of ZFS? Is it ready for production use? yes, please, see http://svn.freebsd.org/viewvc/base?view=revision&revision=197218 -- Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 08:19:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94D0A1065670 for ; Thu, 5 Nov 2009 08:19:26 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6B9308FC20 for ; Thu, 5 Nov 2009 08:19:26 +0000 (UTC) Received: by pxi3 with SMTP id 3so5482442pxi.29 for ; Thu, 05 Nov 2009 00:19:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=KTT0eeYHvS53lNCw4WIlkqtfxnaXKjUCxledtfYQ/8U=; b=cSkgvdBf/33VCtNltYShFpZThi3eeheRIA0bblYPA7boPjY1KVLLRiVFm8xNZ0KKX8 dbiEq/pSx2dBvEHnKS6dH6Trvc3PiX9eeaDDPwhazWznylac6wRLzFZParuoghA++uLY 0jpgR1I5JM0O6d/En3GukA+ioi/I7lwXjQA4I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lrEFX/uZrXCDlBUYnF+CeFzVQL7jTJKoj/uC/nbGLwtLTjvNTEENn14c6rJt9esHZL D2ALDzFbCEoiqQCkHytCTGNHMKFkTODeF1WrBnEDQn9vJqGqI/NWHZ519awXDRTy1TIU 0M03XB8DY5GW7+2/usDE3d9xGoQJGxYn3bf0Q= MIME-Version: 1.0 Received: by 10.143.26.41 with SMTP id d41mr261053wfj.228.1257409165863; Thu, 05 Nov 2009 00:19:25 -0800 (PST) In-Reply-To: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> Date: Thu, 5 Nov 2009 02:19:25 -0600 Message-ID: <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> From: "Sam Fourman Jr." To: Artis Caune Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 08:19:26 -0000 On Thu, Nov 5, 2009 at 12:47 AM, Artis Caune wrote: > 2009/11/5 joe mcguckin : >> I'm interested inb putting together a file server with lots of disk. >> >> What's the state of ZFS? Is it ready for production use? We are using it in production and have a 6TB RAIDZ on FreeBSD8 RC2 amd64 we are quite happy with the FreeBSD 8 setup. we tried it on FreeBSD 7.2 i386 and did not like it (we got a few panics) the only trouble we really had on FreeBSD8 is the sharenfs manpages are not updated. so we are using the classic /etc/exports instead of the zfs option. Sam Fourman Jr. Fourman Networks From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 08:23:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9F38106566C for ; Thu, 5 Nov 2009 08:23:07 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swip.net [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 4F6FD8FC19 for ; Thu, 5 Nov 2009 08:23:06 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=aQey1_VUwUUA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=-o65W9qwAAAA:8 a=6I5d2MoRAAAA:8 a=OwP0SP-sF6umdFmdu08A:9 a=4feMDSS3fg_F5bqao2wA:7 a=fQuIEd6tWuuh7cEHHVSJtwLauOoA:4 a=HRJsq0TPXRMA:10 a=SV7veod9ZcQA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 587155258; Thu, 05 Nov 2009 09:23:05 +0100 From: Hans Petter Selasky To: "Chao Shin" Date: Thu, 5 Nov 2009 09:22:09 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20091002150931.K35591@pooker.samsco.org> <30F3E66A-4A69-46CE-96F4-44B4049722E2@samsco.org> In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpO< =?utf-8?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t; @ =?utf-8?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",; u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200911050922.10205.hselasky@c2i.net> Cc: Marcel Moolenaar , freebsd-current@freebsd.org Subject: Re: [PATCH] Fix for USB media not found at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 08:23:08 -0000 Hi, There is a newer patch in USB P4. The problem is when the /usr partition for example is not residing on the r= oot=20 disk, which is the only disk the code is waiting for. Then the patch will m= ake=20 the bootup fail. =2D-HPS On Thursday 05 November 2009 04:34:33 Chao Shin wrote: > =E5=9C=A8 Sun, 04 Oct 2009 07:52:45 +0800=EF=BC=8CScott Long =E5=86=99=E9=81=93: > > Hi all > > Is there any newer patch/workarounds available? > > > On Oct 3, 2009, at 12:51 PM, Marcel Moolenaar wrote: > >> On Oct 3, 2009, at 9:00 AM, Hans Petter Selasky wrote: > >>> On Saturday 03 October 2009 17:05:35 Scott Long wrote: > >>>> On Oct 3, 2009, at 4:30 AM, Hans Petter Selasky wrote: > >>>>> On Saturday 03 October 2009 10:19:57 Scott Long wrote: > >>>>>> config_intrhook system will sleep after all > >>>>> > >>>>> Then why do you need the intr hook callback? > >>>> > >>>> The config_intrhook lets you know that interrupts are enabled, the > >>>> scheduler is running, and mountroot hasn't run yet. It provides a > >>>> very convenient and standard way to do exactly what we want with USB > >>>> enumeration. > >>> > >>> Hi, > >>> > >>> The root HUB attach and explore code is already running from a separa= te > >>> thread, so won't that be superfluous? I mean, the HUB explore code for > >>> any USB > >>> HUB will not run until the scheduler is running anyway. > >>> > >>> In my opinion delaying the system until the boot disk is present is > >>> just not > >>> good. We should rather be event driven, so that every time a new disk > >>> becomes > >>> present it checks it for mountroot. > >>> > >>> while (1) { > >>> if (mountroot is successful) > >>> break; > >>> if (ctrl+c is pressed) > >>> manual_mountroot(); > >>> printf("Waiting 1 second for root-disk to appear. Press CTRL+C to > >>> abort.\n"); > >>> sleep(1); > >>> } > >> > >> Yes. > >> > >> The mount root code should keep a list of potential root devices to try > >> and > >> it should try a device as soon as it appears. The current approach to > >> block > >> the root mount simply because we want everything to be discovered > >> before we > >> try to mount the root is preventing fast boots -- such as when the root > >> is > >> a memory disk and you don't need to wait for anything... > >> > >> Put differently: it's rather odd to hold off the root mount when the > >> root > >> device is already present... > >> > >> An approach like this also allows one to indefinitely wait for the root > >> device, which is a good feature to have... > > > > When /etc/rc tries to mount everything in the fstab, it'll fail the boot > > if some of the devices haven't arrived in time. An argument can be made > > for fixing that as well, but we're starting to get beyond on the scope > > of fixing what is needed for 8.0-RELEASE. > > > > Scott > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 08:35:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5077106566B for ; Thu, 5 Nov 2009 08:35:15 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 43F808FC18 for ; Thu, 5 Nov 2009 08:35:15 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id nA58JcuO008135 for ; Thu, 5 Nov 2009 09:19:39 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 790E624 for ; Thu, 5 Nov 2009 09:19:38 +0100 (CET) Date: Thu, 5 Nov 2009 09:19:38 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-current@freebsd.org Message-Id: <20091105091938.8a27caac.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.5.80320 Subject: zfs panic mounting fs after crash with RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 08:35:15 -0000 Hi, since I got no further reaction on this on -stable, I'm trying it here on -current as some discussion of RC2-issues seems to go on here, too. Any help is -of course- very much appreciated: Begin forwarded message: Date: Wed, 4 Nov 2009 09:29:00 +0100 From: Gerrit K=FChn To: freebsd-stable@FreeBSD.ORG Cc:=20 Subject: zfs panic mounting fs after crash with RC2 Hi, Yesterday I had the opportunity to play around with my yet-to-become new fileserver a bit more. Originally I had installed 7.2-R, which I upgraded to 8-0-RC2 yesterday. After that I upgraded my zpool consisting of 4 disks in raidz1 constallation to v13. Some time later I tried to use powerd which was obviously a bad idea: it crashed the machine immediately. I will give a separate report on that later as it is probably related to the hardware, which is a bit exotic (VIA VB8001 board with 64bit Via Nano processor). However, the worst thing for me is, that after rebooting from that crash, one of my zfs fs cannot be mounted anymore. As soon as I try to mount it I get a kernel panic. I can still access the properties (I made use of "canmount=3Dnoauto" for the first time :-), but I cannot do a snapshot of the fs (funny enough, zfs complains that the fs is busy, while in reality it is not even mounted - so how could it be busy?). I took a picture of the kernel panic and put it here (don't know if there is any useful information in it): The pool as such seems to be fine, all other fs in it can be mounted and used, only trying to mount tank/sys/var triggers this panic. Are there any suggestions what I could do to get my fs back? Please let me know if (and how) I can provide more debugging information. cu Gerrit From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 10:51:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E0F41065670 for ; Thu, 5 Nov 2009 10:51:38 +0000 (UTC) (envelope-from oliver@namp.de) Received: from grisu.qmail-ldap.de (grisu.qmail-ldap.de [78.46.218.233]) by mx1.freebsd.org (Postfix) with ESMTP id DC4CE8FC0C for ; Thu, 5 Nov 2009 10:51:37 +0000 (UTC) Received: (qmail 99057 invoked from network); 5 Nov 2009 10:59:34 -0000 Received: from unknown (HELO [172.16.208.128]) (oliver@namp.de@[78.46.218.233]) (envelope-sender ) by grisu.qmail-ldap.de (qmail-ldap-1.03) with SMTP for ; 5 Nov 2009 10:59:34 -0000 Received: from: unknown ([195.180.14.14]) by HSF smtp proxy Message-ID: <4AF2AE34.6000009@namp.de> Date: Thu, 05 Nov 2009 11:51:32 +0100 From: Oliver Fakler User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> In-Reply-To: <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: oliver@namp.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 10:51:38 -0000 Hi, may you can give me a tip for the speed tuning. i tested 8 rc1 with a 3 tb raidz and samba on a 100 mbit network i got 4 mb/s which is quite slow i think. May you have a idea for me Greets Oliver Sam Fourman Jr. schrieb: > On Thu, Nov 5, 2009 at 12:47 AM, Artis Caune wrote: > >> 2009/11/5 joe mcguckin : >> >>> I'm interested inb putting together a file server with lots of disk. >>> >>> What's the state of ZFS? Is it ready for production use? >>> > > We are using it in production and have a 6TB RAIDZ on FreeBSD8 RC2 amd64 > we are quite happy with the FreeBSD 8 setup. > we tried it on FreeBSD 7.2 i386 and did not like it (we got a few panics) > > the only trouble we really had on FreeBSD8 is the sharenfs manpages > are not updated. > so we are using the classic /etc/exports instead of the zfs option. > > Sam Fourman Jr. > Fourman Networks > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 11:02:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB11B106566C; Thu, 5 Nov 2009 11:02:42 +0000 (UTC) (envelope-from giovanni.trematerra@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 6D85C8FC15; Thu, 5 Nov 2009 11:02:41 +0000 (UTC) Received: by ewy18 with SMTP id 18so1457381ewy.43 for ; Thu, 05 Nov 2009 03:02:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=UAyqcWrIgqr7Kn6os316WNnxxay6mVKEkj1YMNRu1zA=; b=MPH8qAvOSYKeW6aGZC5giLRu1II6QniC2Kbt/kPOU/jbh6OG7l02OVNBlxrg5+A1o5 irPdVwB7EyHh/52cXCfJaZeCmwVPxtaCy0NR1VhDus4oWY3L2it/IpHKrmQmeD9LH4xv kMMiAC5InnjPkAeJUho37ASjwbB0E32DsDa5o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=qnI7RHaJgqmnYcBNWKfLmXq6N0pJTWefMJP1B2kol291b4qPfFUtCN5Svti2pUjZg5 a3C9Ho3MlG8PZ+sAFrdqugJIAQFrAZ5bCI4q/nGAoqjeUmom5RDWH+aUHmFwFk4Ieyxr mjdO8oPLeflMZj3P7Q2BvOX3TNBwTNjjCRJdc= MIME-Version: 1.0 Received: by 10.216.85.138 with SMTP id u10mr1028688wee.185.1257418959868; Thu, 05 Nov 2009 03:02:39 -0800 (PST) Date: Thu, 5 Nov 2009 12:02:39 +0100 Message-ID: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> From: Giovanni Trematerra To: FreeBSD Current Content-Type: multipart/mixed; boundary=0016e6dab6fb6fd5e204779daa49 Cc: Attilio Rao , des@des.no Subject: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 11:02:42 -0000 --0016e6dab6fb6fd5e204779daa49 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a quick and dirty patch to address the problem as discussed on commit r198868 in svn-src-head@ I introduced BROKEN_OPTERON_E kernel option for i386/amd64 arch. The patch isn't tested yet, I only successfully compiled on i386. Can you let me know if the patch is on the right direction to resolve the issue? style(9) tips are welcomed. Thank you -- Giovanni Trematerra --0016e6dab6fb6fd5e204779daa49 Content-Type: application/octet-stream; name="opteronhack.diff" Content-Disposition: attachment; filename="opteronhack.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g1nehl710 ZGlmZiAtciA3NWQzNWQ4ZTdmZTEgc3lzL2FtZDY0L2FtZDY0L2lkZW50Y3B1LmMKLS0tIGEvc3lz L2FtZDY0L2FtZDY0L2lkZW50Y3B1LmMJVGh1IE5vdiAwNSAxMToxODozNSAyMDA5ICswMTAwCisr KyBiL3N5cy9hbWQ2NC9hbWQ2NC9pZGVudGNwdS5jCVRodSBOb3YgMDUgMTI6NDI6MzUgMjAwOSAr MDEwMApAQCAtNDA0LDYgKzQwNCwxMCBAQAogCiAJaWYgKGNwdV92ZW5kb3JfaWQgPT0gQ1BVX1ZF TkRPUl9BTUQpCiAJCXByaW50X0FNRF9pbmZvKCk7CisjaWYgZGVmaW5lZChCUk9LRU5fT1BURVJP Tl9FKQorCWVsc2UKKwkJcHJpbnRmKCJCUk9LRU5fT1BURVJPTl9FIG9wdGlvbiBpbiB5b3VyIGtl cm5lbCBpcyB1c2VsZXNzIHdpdGggeW91ciBDUFVcbiIpOworI2VuZGlmCiB9CiAKIHZvaWQKQEAg LTYyMCwxMCArNjI0LDE3IEBACiAJICovCiAJaWYgKENQVUlEX1RPX0ZBTUlMWShjcHVfaWQpID09 IDB4ZiAmJiBDUFVJRF9UT19NT0RFTChjcHVfaWQpID49IDB4MjAgJiYKIAkgICAgQ1BVSURfVE9f TU9ERUwoY3B1X2lkKSA8PSAweDNmKSB7CisjaWYgIWRlZmluZWQoQlJPS0VOX09QVEVST05fRSkK IAkJcHJpbnRmKCJXQVJOSU5HOiBUaGlzIGFyY2hpdGVjdHVyZSByZXZpc2lvbiBoYXMga25vd24g U01QICIKIAkJICAgICJoYXJkd2FyZSBidWdzIHdoaWNoIG1heSBjYXVzZSByYW5kb20gaW5zdGFi aWxpdHlcbiIpOwotCQlwcmludGYoIldBUk5JTkc6IEZvciBkZXRhaWxzIHNlZTogIgotCQkgICAg Imh0dHA6Ly9idWd6aWxsYS5rZXJuZWwub3JnL3Nob3dfYnVnLmNnaT9pZD0xMTMwNVxuIik7Cisj ZWxzZQorCQlwcmludGYoIldBUk5JTkc6IG9wdGlvbnMgQlJPS0VOX09QVEVST05fRSBpcyBpbiB5 b3VyIGtlcm5lbC4gIgorCQkJCSJFeHBlY3QgcGVyZm9ybWFuY2UgcGVuYWx0aWVzXG4iKTsKKwll bHNlCisKKwkJcHJpbnRmKCJXQVJOSU5HOiBvcHRpb25zIEJST0tFTl9PUFRFUk9OX0UgaXMgdXNl bGVzcyB3aXRoIHlvdXIgQ1BVLiIKKwkJCQkiRXhwZWN0IHBlcmZvcm1hbmNlIHBlbmFsdGllc1xu Iik7CisjZW5kaWYKIAl9CiB9CiAKZGlmZiAtciA3NWQzNWQ4ZTdmZTEgc3lzL2FtZDY0L2luY2x1 ZGUvYXRvbWljLmgKLS0tIGEvc3lzL2FtZDY0L2luY2x1ZGUvYXRvbWljLmgJVGh1IE5vdiAwNSAx MToxODozNSAyMDA5ICswMTAwCisrKyBiL3N5cy9hbWQ2NC9pbmNsdWRlL2F0b21pYy5oCVRodSBO b3YgMDUgMTI6NDI6MzUgMjAwOSArMDEwMApAQCAtMzYsNiArMzYsMTQgQEAKICNkZWZpbmUJd21i KCkJX19hc20gX192b2xhdGlsZSgic2ZlbmNlOyIgOiA6IDogIm1lbW9yeSIpCiAjZGVmaW5lCXJt YigpCV9fYXNtIF9fdm9sYXRpbGUoImxmZW5jZTsiIDogOiA6ICJtZW1vcnkiKQogCisjaW5jbHVk ZSAib3B0X2NwdS5oIgorCisjaWYgZGVmaW5lZChCUk9LRU5fT1BURVJPTl9FKSAmJiAoZGVmaW5l ZChTTVApIHx8ICFkZWZpbmVkKF9LRVJORUwpKQorCSNkZWZpbmUgT1BURVJPTl9FX0hBQ0soKSBy bWIoKQorI2Vsc2UKKwkjZGVmaW5lIE9QVEVST05fRV9IQUNLKCkKKyNlbmRpZgorCiAvKgogICog VmFyaW91cyBzaW1wbGUgb3BlcmF0aW9ucyBvbiBtZW1vcnksIGVhY2ggb2Ygd2hpY2ggaXMgYXRv bWljIGluIHRoZQogICogcHJlc2VuY2Ugb2YgaW50ZXJydXB0cyBhbmQgbXVsdGlwbGUgcHJvY2Vz c29ycy4KQEAgLTE0Nyw2ICsxNTUsOCBAQAogCSAgIm0iICgqZHN0KQkJCS8qIDQgKi8KIAk6ICJt ZW1vcnkiKTsKIAorCU9QVEVST05fRV9IQUNLKCk7CisKIAlyZXR1cm4gKHJlcyk7CiB9CiAKQEAg LTE2OCw2ICsxNzgsOCBAQAogCSAgIm0iICgqZHN0KQkJCS8qIDQgKi8KIAk6ICJtZW1vcnkiKTsK IAorCU9QVEVST05fRV9IQUNLKCk7CisKIAlyZXR1cm4gKHJlcyk7CiB9CiAKQEAgLTI1MSw2ICsy NjMsOCBAQAogCTogIm0iICgqcCkJCQkvKiAyICovCQlcCiAJOiAibWVtb3J5Iik7CQkJCQlcCiAJ CQkJCQkJXAorCU9QVEVST05fRV9IQUNLKCk7CQlcCisJCQkJCQkJXAogCXJldHVybiAocmVzKTsJ CQkJCVwKIH0JCQkJCQkJXAogCQkJCQkJCVwKZGlmZiAtciA3NWQzNWQ4ZTdmZTEgc3lzL2NvbmYv b3B0aW9ucy5hbWQ2NAotLS0gYS9zeXMvY29uZi9vcHRpb25zLmFtZDY0CVRodSBOb3YgMDUgMTE6 MTg6MzUgMjAwOSArMDEwMAorKysgYi9zeXMvY29uZi9vcHRpb25zLmFtZDY0CVRodSBOb3YgMDUg MTI6NDI6MzUgMjAwOSArMDEwMApAQCAtNDksNiArNDksNyBAQAogIyBFT0YKICMgLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogSEFNTUVSCQkJb3B0X2NwdS5oCitCUk9LRU5fT1BURVJP Tl9FCW9wdF9jcHUuaAogUFNNX0hPT0tSRVNVTUUJCW9wdF9wc20uaAogUFNNX1JFU0VUQUZURVJT VVNQRU5ECW9wdF9wc20uaAogUFNNX0RFQlVHCQlvcHRfcHNtLmgKZGlmZiAtciA3NWQzNWQ4ZTdm ZTEgc3lzL2NvbmYvb3B0aW9ucy5pMzg2Ci0tLSBhL3N5cy9jb25mL29wdGlvbnMuaTM4NglUaHUg Tm92IDA1IDExOjE4OjM1IDIwMDkgKzAxMDAKKysrIGIvc3lzL2NvbmYvb3B0aW9ucy5pMzg2CVRo dSBOb3YgMDUgMTI6NDI6MzUgMjAwOSArMDEwMApAQCAtMzcsNiArMzcsNyBAQAogVElNRVJfRlJF UQkJCW9wdF9jbG9jay5oCiAKIENQVV9BVEhMT05fU1NFX0hBQ0sJCW9wdF9jcHUuaAorQlJPS0VO X09QVEVST05fRQlvcHRfY3B1LmgKIENQVV9CTFVFTElHSFROSU5HXzNYCQlvcHRfY3B1LmgKIENQ VV9CTFVFTElHSFROSU5HX0ZQVV9PUF9DQUNIRQlvcHRfY3B1LmgKIENQVV9CVEJfRU4JCQlvcHRf Y3B1LmgKZGlmZiAtciA3NWQzNWQ4ZTdmZTEgc3lzL2kzODYvaTM4Ni9pZGVudGNwdS5jCi0tLSBh L3N5cy9pMzg2L2kzODYvaWRlbnRjcHUuYwlUaHUgTm92IDA1IDExOjE4OjM1IDIwMDkgKzAxMDAK KysrIGIvc3lzL2kzODYvaTM4Ni9pZGVudGNwdS5jCVRodSBOb3YgMDUgMTI6NDI6MzUgMjAwOSAr MDEwMApAQCAtOTA0LDYgKzkwNCwxMSBAQAogCQlwcmludF9JTlRFTF9pbmZvKCk7CiAJZWxzZSBp ZiAoY3B1X3ZlbmRvcl9pZCA9PSBDUFVfVkVORE9SX1RSQU5TTUVUQSkKIAkJcHJpbnRfdHJhbnNt ZXRhX2luZm8oKTsKKworI2lmIGRlZmluZWQoQlJPS0VOX09QVEVST05fRSkKKwlpZiAoY3B1X3Zl bmRvcl9pZCAhPSBDUFVfVkVORE9SX0FNRCkKKwkJcHJpbnRmKCJCUk9LRU5fT1BURVJPTl9FIG9w dGlvbiBpbiB5b3VyIGtlcm5lbCBpcyB1c2VsZXNzIHdpdGggeW91ciBDUFVcbiIpOworI2VuZGlm CiB9CiAKIHZvaWQKQEAgLTEzMTUsMTIgKzEzMjAsMTggQEAKIAkgKiBtb2RlbCBhbmQgZmFtaWx5 IGFyZSBpZGVudGlmaWVkLgogCSAqLwogCWlmIChDUFVJRF9UT19GQU1JTFkoY3B1X2lkKSA9PSAw eGYgJiYgQ1BVSURfVE9fTU9ERUwoY3B1X2lkKSA+PSAweDIwICYmCi0JICAgIENQVUlEX1RPX01P REVMKGNwdV9pZCkgPD0gMHgzZikgeworCSAgICBDUFVJRF9UT19NT0RFTChjcHVfaWQpIDw9IDB4 M2YpIAorI2lmICFkZWZpbmVkKEJST0tFTl9PUFRFUk9OX0UpCiAJCXByaW50ZigiV0FSTklORzog VGhpcyBhcmNoaXRlY3R1cmUgcmV2aXNpb24gaGFzIGtub3duIFNNUCAiCiAJCSAgICAiaGFyZHdh cmUgYnVncyB3aGljaCBtYXkgY2F1c2UgcmFuZG9tIGluc3RhYmlsaXR5XG4iKTsKLQkJcHJpbnRm KCJXQVJOSU5HOiBGb3IgZGV0YWlscyBzZWU6ICIKLQkJICAgICJodHRwOi8vYnVnemlsbGEua2Vy bmVsLm9yZy9zaG93X2J1Zy5jZ2k/aWQ9MTEzMDVcbiIpOwotCX0KKyNlbHNlCisJCXByaW50Zigi V0FSTklORzogb3B0aW9ucyBCUk9LRU5fT1BURVJPTl9FIGlzIGluIHlvdXIga2VybmVsLiAiCisJ CQkJIkV4cGVjdCBwZXJmb3JtYW5jZSBwZW5hbHRpZXNcbiIpOworCWVsc2UKKworCQlwcmludGYo IldBUk5JTkc6IG9wdGlvbnMgQlJPS0VOX09QVEVST05fRSBpcyB1c2VsZXNzIHdpdGggeW91ciBD UFUuIgorCQkJCSJFeHBlY3QgcGVyZm9ybWFuY2UgcGVuYWx0aWVzXG4iKTsKKyNlbmRpZgogfQog CiBzdGF0aWMgdm9pZApkaWZmIC1yIDc1ZDM1ZDhlN2ZlMSBzeXMvaTM4Ni9pbmNsdWRlL2F0b21p Yy5oCi0tLSBhL3N5cy9pMzg2L2luY2x1ZGUvYXRvbWljLmgJVGh1IE5vdiAwNSAxMToxODozNSAy MDA5ICswMTAwCisrKyBiL3N5cy9pMzg2L2luY2x1ZGUvYXRvbWljLmgJVGh1IE5vdiAwNSAxMjo0 MjozNSAyMDA5ICswMTAwCkBAIC0zNiw2ICszNiwxNCBAQAogI2RlZmluZQl3bWIoKQlfX2FzbSBf X3ZvbGF0aWxlKCJsb2NrOyBhZGRsICQwLCglJWVzcCkiIDogOiA6ICJtZW1vcnkiKQogI2RlZmlu ZQlybWIoKQlfX2FzbSBfX3ZvbGF0aWxlKCJsb2NrOyBhZGRsICQwLCglJWVzcCkiIDogOiA6ICJt ZW1vcnkiKQogCisjaW5jbHVkZSAib3B0X2NwdS5oIgorCisjaWYgZGVmaW5lZChCUk9LRU5fT1BU RVJPTl9FKSAmJiAoZGVmaW5lZChTTVApIHx8ICFkZWZpbmVkKF9LRVJORUwpKQorCSNkZWZpbmUg T1BURVJPTl9FX0hBQ0soKSBybWIoKQorI2Vsc2UKKwkjZGVmaW5lIE9QVEVST05fRV9IQUNLKCkK KyNlbmRpZgorCiAvKgogICogVmFyaW91cyBzaW1wbGUgb3BlcmF0aW9ucyBvbiBtZW1vcnksIGVh Y2ggb2Ygd2hpY2ggaXMgYXRvbWljIGluIHRoZQogICogcHJlc2VuY2Ugb2YgaW50ZXJydXB0cyBh bmQgbXVsdGlwbGUgcHJvY2Vzc29ycy4KQEAgLTE3NCw2ICsxODIsOCBAQAogCSAgIm0iICgqZHN0 KQkJCS8qIDQgKi8KIAk6ICJtZW1vcnkiKTsKIAorCU9QVEVST05fRV9IQUNLKCk7CisKIAlyZXR1 cm4gKHJlcyk7CiB9CiAKQEAgLTI0MCw2ICsyNTAsOCBAQAogCTogIm0iICgqcCkJCQkvKiAyICov CQlcCiAJOiAibWVtb3J5Iik7CQkJCQlcCiAJCQkJCQkJXAorCU9QVEVST05fRV9IQUNLKCk7CQlc CisJCQkJCQkJXAogCXJldHVybiAocmVzKTsJCQkJCVwKIH0JCQkJCQkJXAogCQkJCQkJCVwK --0016e6dab6fb6fd5e204779daa49-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 11:18:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B2AC1065693; Thu, 5 Nov 2009 11:18:56 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 271E98FC16; Thu, 5 Nov 2009 11:18:55 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 220CC6D41C; Thu, 5 Nov 2009 11:18:54 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id E516C84503; Thu, 5 Nov 2009 12:18:53 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Giovanni Trematerra References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> Date: Thu, 05 Nov 2009 12:18:53 +0100 In-Reply-To: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> (Giovanni Trematerra's message of "Thu, 5 Nov 2009 12:02:39 +0100") Message-ID: <86k4y5fcde.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Attilio Rao , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 11:18:56 -0000 Giovanni Trematerra writes: > I have a quick and dirty patch to address the problem as discussed on > commit r198868 in svn-src-head@ > I introduced BROKEN_OPTERON_E kernel option for i386/amd64 arch. > The patch isn't tested yet, I only successfully compiled on i386. > Can you let me know if the patch is on the right direction to resolve the= issue? > style(9) tips are welcomed. We should probably call it OPTERON_E_LFENCE_HACK or something, cf. NO_F00F_HACK (which has the opposite semantics - the f00f hack is enabled by default, though at this point we should probably reverse it and just print a warning if we detect a vulnerable CPU), and the wording of those printfs needs work, but it looks OK overall. BTW, you should use the text/x-patch MIME type for patches, instead of application/octet-stream. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 11:28:41 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 097F7106566B; Thu, 5 Nov 2009 11:28:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 6D56C8FC0A; Thu, 5 Nov 2009 11:28:40 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA5BSZjh053318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Nov 2009 13:28:35 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA5BSZUG086711; Thu, 5 Nov 2009 13:28:35 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA5BSYCF086686; Thu, 5 Nov 2009 13:28:34 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Nov 2009 13:28:34 +0200 From: Kostik Belousov To: Giovanni Trematerra Message-ID: <20091105112834.GR2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bi+HF1AHjw0mn3zx" Content-Disposition: inline In-Reply-To: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Attilio Rao , des@des.no, FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 11:28:41 -0000 --Bi+HF1AHjw0mn3zx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 05, 2009 at 12:02:39PM +0100, Giovanni Trematerra wrote: > Hi, > I have a quick and dirty patch to address the problem as discussed on > commit r198868 in svn-src-head@ > I introduced BROKEN_OPTERON_E kernel option for i386/amd64 arch. > The patch isn't tested yet, I only successfully compiled on i386. > Can you let me know if the patch is on the right direction to resolve the issue? > style(9) tips are welcomed. I think there is no much sense in printing that hack in unused; instead, you should print info when option is enabled and vulnerable CPU is detected. Aren't atomic_readandclear need the same workaround ? It would be much easier to read the patch if you generated it with analog of "svn diff -x -p" for your VCS. --Bi+HF1AHjw0mn3zx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrytuIACgkQC3+MBN1Mb4gcAwCeLgX6gTbM3CP7fSNxc82yjP95 PFkAnRWduCsbqL7cdEs31CURhh6RIv0N =GUh7 -----END PGP SIGNATURE----- --Bi+HF1AHjw0mn3zx-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 11:52:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06C05106568F; Thu, 5 Nov 2009 11:52:04 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id BAD268FC18; Thu, 5 Nov 2009 11:52:03 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id E3A586D41C; Thu, 5 Nov 2009 11:52:00 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id BE6FD84503; Thu, 5 Nov 2009 12:52:00 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Kostik Belousov References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> Date: Thu, 05 Nov 2009 12:52:00 +0100 In-Reply-To: <20091105112834.GR2331@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Thu, 5 Nov 2009 13:28:34 +0200") Message-ID: <86fx8tfau7.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Attilio Rao , Giovanni Trematerra , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 11:52:04 -0000 Kostik Belousov writes: > I think there is no much sense in printing that hack in unused; > instead, you should print info when option is enabled and vulnerable > CPU is detected. We should *definitely* print a warninhg when a vulnerable CPU is detected and the option is *not* enabled. How do you justify not telling the user that you know the machine will crash as soon as he runs 'make buildworld' with a high -j value? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 12:00:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4603F10656C3; Thu, 5 Nov 2009 12:00:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id A98838FC2B; Thu, 5 Nov 2009 12:00:41 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA5C0bCA056191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Nov 2009 14:00:37 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA5C0amd095061; Thu, 5 Nov 2009 14:00:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA5C0YF2095060; Thu, 5 Nov 2009 14:00:34 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Nov 2009 14:00:34 +0200 From: Kostik Belousov To: Dag-Erling Sm??rgrav Message-ID: <20091105120034.GS2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <86fx8tfau7.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p2u4WfPhYOuYlOsk" Content-Disposition: inline In-Reply-To: <86fx8tfau7.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Attilio Rao , Giovanni Trematerra , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 12:00:42 -0000 --p2u4WfPhYOuYlOsk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 05, 2009 at 12:52:00PM +0100, Dag-Erling Sm??rgrav wrote: > Kostik Belousov writes: > > I think there is no much sense in printing that hack in unused; > > instead, you should print info when option is enabled and vulnerable > > CPU is detected. >=20 > We should *definitely* print a warninhg when a vulnerable CPU is > detected and the option is *not* enabled. How do you justify not > telling the user that you know the machine will crash as soon as he runs > 'make buildworld' with a high -j value? We do not do this for other cpu bugs workarounds, why this should be different. Besides, there were no confirmed reports of this happening in field (I mean the bug manifestation, not make -j panicing or hanging machine :). --p2u4WfPhYOuYlOsk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEUEARECAAYFAkryvmIACgkQC3+MBN1Mb4hCnwCgy/Qo4SIoQBb2rL6D1Ga+BUHu SAoAl3mN/bYQdjidwDCNYBUKxQpKM9E= =n2li -----END PGP SIGNATURE----- --p2u4WfPhYOuYlOsk-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 12:24:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B64910656C5; Thu, 5 Nov 2009 12:24:56 +0000 (UTC) (envelope-from giovanni.trematerra@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id 72CDB8FC08; Thu, 5 Nov 2009 12:24:55 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 25so952eya.9 for ; Thu, 05 Nov 2009 04:24:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=e2dLRh/5W6x31WoxQ18lO0cgDRyeXnXiaZl4GH+1HRI=; b=KD0dMQ0cQYMlDd9iBlSBjSQBXJFZLArZlRhs4nrcCQOZolRyWEqE4+6WPTyTVLrZoH qiXZAR+MEvgCGotDZg5ZloiIv8yY0EKQiB2QIeevxVBwMHJIzB7g2IZA0t2yGQxsTrPg u041YH+R7EBJa4BiHqGdNOGKTOPCsYJsicbE8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tMmz3nwiO51uhfbENhwA0t7BecOjzWIYG33B+b7wGtZKfSqxmvzaEMXCm7XiFICX/i BG0tsfdCzgjJYC+nY0RReQ0qpBR1LV7xQZvgLynRrTs6wegjQ4vfw7+sLYxssUdbyuic X0oD8sJLNhWaO30oJiDsxoBJCOOpknuSuZerg= MIME-Version: 1.0 Received: by 10.216.90.21 with SMTP id d21mr895394wef.85.1257423893918; Thu, 05 Nov 2009 04:24:53 -0800 (PST) In-Reply-To: <20091105112834.GR2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> Date: Thu, 5 Nov 2009 13:24:53 +0100 Message-ID: <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> From: Giovanni Trematerra To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: Attilio Rao , des@des.no, FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 12:24:56 -0000 On Thu, Nov 5, 2009 at 12:28 PM, Kostik Belousov wrote: > > Aren't atomic_readandclear need the same workaround ? > I understood that the bug manifests itself only when lock instruction is used. atomic_readandclear doesn't use lock. I think i386/linux/linux_support.s and amd64/linux32/linux32_support.s need the work-around too. > It would be much easier to read the patch if you generated it > with analog of "svn diff -x -p" for your VCS. > I'm sorry, I'll do my best next time. -- Giovanni Trematerra From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 12:30:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D08F106568F for ; Thu, 5 Nov 2009 12:30:31 +0000 (UTC) (envelope-from mdounin@mdounin.ru) Received: from mdounin.cust.ramtel.ru (mdounin.cust.ramtel.ru [81.19.69.81]) by mx1.freebsd.org (Postfix) with ESMTP id 12C338FC13 for ; Thu, 5 Nov 2009 12:30:30 +0000 (UTC) Received: from mdounin.ru (mdounin.cust.ramtel.ru [81.19.69.81]) by mdounin.cust.ramtel.ru (Postfix) with ESMTP id 2B39317038; Thu, 5 Nov 2009 15:30:29 +0300 (MSK) Date: Thu, 5 Nov 2009 15:30:29 +0300 From: Maxim Dounin To: Kostik Belousov Message-ID: <20091105123028.GK1144@mdounin.ru> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <86fx8tfau7.fsf@ds4.des.no> <20091105120034.GS2331@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091105120034.GS2331@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Attilio Rao , Dag-Erling Sm??rgrav , Giovanni Trematerra , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 12:30:31 -0000 Hello! On Thu, Nov 05, 2009 at 02:00:34PM +0200, Kostik Belousov wrote: > On Thu, Nov 05, 2009 at 12:52:00PM +0100, Dag-Erling Sm??rgrav wrote: > > Kostik Belousov writes: > > > I think there is no much sense in printing that hack in unused; > > > instead, you should print info when option is enabled and vulnerable > > > CPU is detected. > > > > We should *definitely* print a warninhg when a vulnerable CPU is > > detected and the option is *not* enabled. How do you justify not > > telling the user that you know the machine will crash as soon as he runs > > 'make buildworld' with a high -j value? > > We do not do this for other cpu bugs workarounds, why this should be > different. Well, probably is't a good idea to do so? Something like NetBSD's sys/arch/x86/x86/errata.c seems to be right way to go. > Besides, there were no confirmed reports of this happening > in field (I mean the bug manifestation, not make -j panicing or hanging > machine :). http://bugs.mysql.com/bug.php?id=26081 Maxim Dounin From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 12:45:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38DE9106568D; Thu, 5 Nov 2009 12:45:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 85B9B8FC16; Thu, 5 Nov 2009 12:45:11 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA5Cj6hi059969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Nov 2009 14:45:06 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA5Cj6WI052781; Thu, 5 Nov 2009 14:45:06 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA5Cj508052780; Thu, 5 Nov 2009 14:45:05 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Nov 2009 14:45:05 +0200 From: Kostik Belousov To: Giovanni Trematerra Message-ID: <20091105124505.GT2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h1wVxq8aeHrvhZJz" Content-Disposition: inline In-Reply-To: <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Attilio Rao , des@des.no, FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 12:45:12 -0000 --h1wVxq8aeHrvhZJz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 05, 2009 at 01:24:53PM +0100, Giovanni Trematerra wrote: > On Thu, Nov 5, 2009 at 12:28 PM, Kostik Belousov wr= ote: >=20 > > > > Aren't atomic_readandclear need the same workaround ? > > >=20 > I understood that the bug manifests itself only when lock instruction is = used. > atomic_readandclear doesn't use lock. xchgl uses lock implicitely: If a memory operand is referenced, the processor's locking protocol is automatically implemented for the duration of the exchange operation, regardless of the presence or absence of the LOCK prefix or of the value of the IOPL. > I think i386/linux/linux_support.s and amd64/linux32/linux32_support.s > need the work-around too. What about casuword32 ? It is actually unclear from the bug description whether we need it there. Description states "a locked instruction doesn't act as a read-acquire barrier if followed by a non-locked read-modify-write instruction." casuword32 for amd64, for instance, does movq immediately after cmpxchgl, that is a store op, not read-modify-store. So, does it need a workaround ? Similar stores are performed in linux32_support.s. atomic.h functions definitely need your workaround since they are inlined. Also, I remember that bind(8) provides its own atomic implementation. --h1wVxq8aeHrvhZJz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkryyNEACgkQC3+MBN1Mb4hspgCff9idBrWHCe9mfaMcwdDu6CXR 8dgAn1/b9bcdImR6tghAD8Z3FuipfyVx =Lc6x -----END PGP SIGNATURE----- --h1wVxq8aeHrvhZJz-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 13:01:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33A721065676 for ; Thu, 5 Nov 2009 13:01:09 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.211.178]) by mx1.freebsd.org (Postfix) with ESMTP id DF6C98FC17 for ; Thu, 5 Nov 2009 13:01:08 +0000 (UTC) Received: by ywh8 with SMTP id 8so7508017ywh.3 for ; Thu, 05 Nov 2009 05:01:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=9PkUxcosQx06vpwPTl1waPznQwhLiruonmFepVCv9Lo=; b=AhCjVtwua+a/6mK0H8yetAFqVC5/mKH+9SxdSkbFAFzpkJkRWzQK2s9Asvtd5m9Znr KtIJospl37G6v4mCf2IDOtpKn9S72YyDo6FuwA9rSGIx596fQtAs1Xme9qJ0b4qSI+nf lJAeqXpX1km9i8BDaJipaOUb4Q3hIvT8HKXKA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=sj9ZJE8bOAk2/cpBBrevWGDsvMRm8gdhs4ibt5278bpGpcPwag0MSyHfosEo0mIg3H b6STu282hq3QySIT5DJLgzA1Dgxh6smJy9MIAuZQ9JlIgz+Akv669icLTZsk00Dn3dwg Rcwexeazitiem8uSTpH905gqfUVmcdcxT4RWM= Received: by 10.101.29.9 with SMTP id g9mr148280anj.123.1257426067902; Thu, 05 Nov 2009 05:01:07 -0800 (PST) Received: from ?10.0.3.231? (pool-173-70-28-149.nwrknj.fios.verizon.net [173.70.28.149]) by mx.google.com with ESMTPS id 7sm942241yxg.50.2009.11.05.05.01.06 (version=SSLv3 cipher=RC4-MD5); Thu, 05 Nov 2009 05:01:06 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Thu, 05 Nov 2009 08:00:23 -0500 Message-Id: <1257426023.1436.18.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Subject: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 13:01:09 -0000 It seems that 8.0 discussion is still going on on @current... if I should have posted this on @stable, please, feel free to chastise me as appropriate. After updating to r198831 my laptop no longer associates with either of two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the problem. Working system: FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 r198443M: Sat Oct 24 14:03:30 EDT 2009 root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 Non-working system: FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 r198931: Wed Nov 4 20:56:16 EST 2009 root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 APs are is: SSID/MESH ID BSSID CHAN RATE S:N INT CAPS AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS WME AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA ATH Relevant piece of wpa_supplicant.conf is: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel eapol_version=2 network={ ssid="AP_SSID" scan_ssid=1 priority=1 proto=WPA key_mgmt=WPA-PSK psk="Really secure something" } APs are set not to broadcast SSID, but enabling broadcast does not change much. Running wpa_supplicant with -d shows that it could not match AP_SSID. If there is anything else I can provide, please, let me know. -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 13:18:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA8B81065695 for ; Thu, 5 Nov 2009 13:18:40 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 98E1F8FC14 for ; Thu, 5 Nov 2009 13:18:40 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-161-151.rz.uni-karlsruhe.de [141.3.161.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 158EE8A0E42; Thu, 5 Nov 2009 14:18:38 +0100 (CET) Message-ID: <4AF2D0AA.2020809@bsdforen.de> Date: Thu, 05 Nov 2009 14:18:34 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Szilveszter Adam References: <4AF1869D.6090304@bsdforen.de> <20091105061126.GA1839@baranyfelhocske.buza.adamsfamily.xx> In-Reply-To: <20091105061126.GA1839@baranyfelhocske.buza.adamsfamily.xx> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 13:18:40 -0000 Szilveszter Adam wrote: > Well, this is of course only anecdotal, but I do not witness corruption > with any of my USB-attached umass devices. A friend tried to reproduce my problem to no avail, so it appears to be a rare issue. But I also can produce the problems with with file system backed md devices, so it's not a USB issue. I've first run into it on RC1, so rebuilding is not a solution, either. > (I no longer have a floppy > drive, and I do not have a FAT partition on my HDD either, so I cannot > test that). I am using 9.0-CURRENT, rev 198667 (but the problem did not > show also on earlier revs) > > The devices that I use on and off: > > - Meizu M3 Music Card audio player > - Cowon iaudio D2 audio player (According to user forums, this one is > particularly sensitive to fs corruption) I'm using a Cowon S9. When I added a couple of new songs to the device, it complained about them to be corrupted (despite a proper umount). So I ran fsck_msdosfs, which found quite a number of problems and recopied the files. After turning the device back on I only got random coloured garbage on the screen, whenever I tried to access something. I booted Windows and chkdsk reported all these problems (cross-linked files and the like). But the player didn't recover until I reformatted the whole mess. > - various USB sticks, most notably a Kingston Data Traveller 4G (I > believe) > - Even the occasional memory stick, or SD card in card reader > > However, I must also state that I never used fsck_msdosfs in the last > few years. Neither have I formatted any FAT file systems under FreeBSD for > years. Also, I always unmount the devices before removing them. > So do I. This didn't safe me, though. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 13:52:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 156E8106566B; Thu, 5 Nov 2009 13:52:06 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 727DB8FC15; Thu, 5 Nov 2009 13:52:05 +0000 (UTC) Received: by bwz5 with SMTP id 5so886641bwz.3 for ; Thu, 05 Nov 2009 05:52:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=jmRRuzAgonIxozEnt3AfLqjTl9Mj44YfX/X0acV6Puc=; b=fjqBMHZI3JjqKs7baB4iXeBetEq+d6lEE0hdsxLrW8RM11Ekm8eeK5M3fy4GsvG9wa 4Ky7RmRrTwUdwliZqadR4aYMOO/q1cxB1dv7g6yQGHQUpuDFEZ3FotwQybs5MQ12Vx/W 6nVn6sh3HSpFgmQuegjFnrfpdxpJ2ycwpNMtU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=SLC7CjseP803lUViNwOdQfNNZNQSq2HoxzL9/b2aU64EGoJOmgo5oSczSRkND6oiso Uu43JyEzOzUYgRvSqLQSFK4rAa+LpVnNoegzBlpLvyShCMPmUrNdkcXzX3EdxpmlNazS cl2g7g3r04gNKliQTFfAmOhb0bZ4EIKwkRlz8= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.2.199 with SMTP id 7mr398438fak.107.1257429124419; Thu, 05 Nov 2009 05:52:04 -0800 (PST) In-Reply-To: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> Date: Thu, 5 Nov 2009 14:52:04 +0100 X-Google-Sender-Auth: cfb9ef2b875caf1c Message-ID: <3bbf2fe10911050552k3f9396feu8f4b9ed7a8dda81b@mail.gmail.com> From: Attilio Rao To: Giovanni Trematerra Content-Type: text/plain; charset=UTF-8 Cc: des@des.no, FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 13:52:06 -0000 2009/11/5 Giovanni Trematerra : > Hi, > I have a quick and dirty patch to address the problem as discussed on > commit r198868 in svn-src-head@ > I introduced BROKEN_OPTERON_E kernel option for i386/amd64 arch. > The patch isn't tested yet, I only successfully compiled on i386. > Can you let me know if the patch is on the right direction to resolve the issue? > style(9) tips are welcomed. > diff -r 75d35d8e7fe1 sys/amd64/amd64/identcpu.c > --- a/sys/amd64/amd64/identcpu.c Thu Nov 05 11:18:35 2009 +0100 > +++ b/sys/amd64/amd64/identcpu.c Thu Nov 05 12:42:35 2009 +0100 > @@ -404,6 +404,10 @@ > > if (cpu_vendor_id == CPU_VENDOR_AMD) > print_AMD_info(); > +#if defined(BROKEN_OPTERON_E) > + else > + printf("BROKEN_OPTERON_E option in your kernel is useless with y > our CPU\n"); > +#endif > } > > void > @@ -620,10 +624,17 @@ > */ > if (CPUID_TO_FAMILY(cpu_id) == 0xf && CPUID_TO_MODEL(cpu_id) >= 0x20 && > CPUID_TO_MODEL(cpu_id) <= 0x3f) { > +#if !defined(BROKEN_OPTERON_E) > printf("WARNING: This architecture revision has known SMP " > "hardware bugs which may cause random instability\n"); > - printf("WARNING: For details see: " > - "http://bugzilla.kernel.org/show_bug.cgi?id=11305\n"); > +#else > + printf("WARNING: options BROKEN_OPTERON_E is in your kernel. " > + "Expect performance penalties\n"); > + else > + > + printf("WARNING: options BROKEN_OPTERON_E is useless with your C > PU." > + "Expect performance penalties\n"); > +#endif > } > } I would leave the whole logic within print_AMD_info() and not pollute external code and I would not print a string if the fix is in. > diff -r 75d35d8e7fe1 sys/amd64/include/atomic.h > --- a/sys/amd64/include/atomic.h Thu Nov 05 11:18:35 2009 +0100 > +++ b/sys/amd64/include/atomic.h Thu Nov 05 12:42:35 2009 +0100 > @@ -36,6 +36,14 @@ > #define wmb() __asm __volatile("sfence;" : : : "memory") > #define rmb() __asm __volatile("lfence;" : : : "memory") > > +#include "opt_cpu.h" > + > +#if defined(BROKEN_OPTERON_E) && (defined(SMP) || !defined(_KERNEL)) > + #define OPTERON_E_HACK() rmb() > +#else > + #define OPTERON_E_HACK() > +#endif > + > /* > * Various simple operations on memory, each of which is atomic in the > * presence of interrupts and multiple processors. > @@ -147,6 +155,8 @@ > "m" (*dst) /* 4 */ > : "memory"); > > + OPTERON_E_HACK(); > + > return (res); > } You need to override the whole barrier IMHO and not add this new stub. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 14:10:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9B6106568B for ; Thu, 5 Nov 2009 14:10:40 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id BBA2C8FC26 for ; Thu, 5 Nov 2009 14:10:39 +0000 (UTC) Received: by bwz5 with SMTP id 5so15627bwz.3 for ; Thu, 05 Nov 2009 06:10:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=g64zbdbVoogsZ2YiNuGF9wpCt/qit8ckhr5A7rfxb0Y=; b=XFsnDrfy0a0/LmfxuLZ/UWRo5fokhQOa9bm7BQsG1Zu18axRY7JrHMHqFQ+WwZT+Dc gdg1ZmkyTMjIvvfIEgf/ZoZwYA55+8N1DAEe68hmpgVyBf+m7wYG6CM3n7miBHQ8Dh+R v/W4UW6CqR+p5exc61EGvbfXNbOKPc+g2y8QY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=tCuLAAv0n12HU1tmTvHlVVj48lADFjvWyb7fpZA3WAv0wX65nMTdjo56Eaj3ADFyfo G+BjVe7pxLCwCdcA/614RQRWiCtSGWbrL8QMBursCnzi8cir26ycHObXzJN3QOL9P/hU X8p1e5NC1d5/aoQGYsfTDgF2iOKHW/Jmglk0o= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.161.215 with SMTP id s23mr420189fax.44.1257430238639; Thu, 05 Nov 2009 06:10:38 -0800 (PST) In-Reply-To: <20091105124505.GT2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> <20091105124505.GT2331@deviant.kiev.zoral.com.ua> Date: Thu, 5 Nov 2009 15:10:38 +0100 X-Google-Sender-Auth: d5522211783dd626 Message-ID: <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> From: Attilio Rao To: Kostik Belousov Content-Type: text/plain; charset=UTF-8 Cc: des@des.no, Giovanni Trematerra , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 14:10:40 -0000 2009/11/5 Kostik Belousov : > On Thu, Nov 05, 2009 at 01:24:53PM +0100, Giovanni Trematerra wrote: >> On Thu, Nov 5, 2009 at 12:28 PM, Kostik Belousov wrote: >> >> > >> > Aren't atomic_readandclear need the same workaround ? >> > >> >> I understood that the bug manifests itself only when lock instruction is used. >> atomic_readandclear doesn't use lock. > xchgl uses lock implicitely: > > If a memory operand is referenced, the processor's locking protocol is > automatically implemented for the duration of the exchange operation, > regardless of the presence or absence of the LOCK prefix or of the value > of the IOPL. > >> I think i386/linux/linux_support.s and amd64/linux32/linux32_support.s >> need the work-around too. > What about casuword32 ? > It is actually unclear from the bug description whether we need it there. > Description states "a locked instruction doesn't act as a read-acquire > barrier if followed by a non-locked read-modify-write instruction." > > casuword32 for amd64, for instance, does movq immediately after > cmpxchgl, that is a store op, not read-modify-store. So, does it need a > workaround ? Similar stores are performed in linux32_support.s. > > atomic.h functions definitely need your workaround since they are inlined. > > Also, I remember that bind(8) provides its own atomic implementation. However, that fix is not simple to got as one would think. Our atomics implementation on ia32 and amd64 assume rel/acq barriers aims for the same code but this problem introduces asymmetric behaviour between them. The good way to fix this is to offer an lfence on acq barriers and leave the other cases untouched, but this could be meaning re-structure out atomic.h a lot. I will try to think to a good way to do that when I have more available time. In the while the WARNING msg will do its job (I can still trimm the URL path however). Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 14:21:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF7441065670; Thu, 5 Nov 2009 14:21:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 496EC8FC17; Thu, 5 Nov 2009 14:21:49 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id nA5ELghc068178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Nov 2009 16:21:42 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id nA5ELgGs013740; Thu, 5 Nov 2009 16:21:42 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id nA5ELgm4013739; Thu, 5 Nov 2009 16:21:42 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Nov 2009 16:21:42 +0200 From: Kostik Belousov To: Attilio Rao Message-ID: <20091105142142.GV2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> <20091105124505.GT2331@deviant.kiev.zoral.com.ua> <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9o1Xi4ZMQ45MudWG" Content-Disposition: inline In-Reply-To: <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: des@des.no, Giovanni Trematerra , FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 14:21:51 -0000 --9o1Xi4ZMQ45MudWG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 05, 2009 at 03:10:38PM +0100, Attilio Rao wrote: > The good way to fix this is to offer an lfence on acq barriers and > leave the other cases untouched, but this could be meaning > re-structure out atomic.h a lot. I will try to think to a good way to > do that when I have more available time. > In the while the WARNING msg will do its job (I can still trimm the > URL path however). For 8.0, please strip URL at least. --9o1Xi4ZMQ45MudWG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkry33UACgkQC3+MBN1Mb4hK7ACfcR2Qd+Gs13pUoT8LkobMQloI sPoAnRfim40U2zNBrrCn6D18c50JkOxJ =2c/c -----END PGP SIGNATURE----- --9o1Xi4ZMQ45MudWG-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 14:25:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44D8510656AC for ; Thu, 5 Nov 2009 14:25:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9EB8FC18 for ; Thu, 5 Nov 2009 14:25:00 +0000 (UTC) Received: by ewy18 with SMTP id 18so20995ewy.43 for ; Thu, 05 Nov 2009 06:24:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=fM5JUitwisftWnGsHTZbvGdWGJFnrRUIQbIHO69GElY=; b=rwbrLkXmdbRxTdWTWYL61xAmEU8e6ljSDUwe0oBWwwV0RLcgOuQMZx16BZPUuaWVvW x94jsd6bvHpfCA7HBAoY/XwbkT2izWI/B5t9+63O8Imr6yotgl5QMyHU6UgC0OVjK7IM lyLEj5AcMb805OLo1nXa5HgavfysDr+jwM6AY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SQvDlvhj9dJPPDGWbpjDP8NOriUkelRCLbmSHNXGhjy41XxGZdLzLUcOymn7y+bUU0 n84/yROQVhArnuq3tRbeVL9yXo04jKvUwzGdZAxYnVfdR+8SDASjnD4jrMdAORT3I+nV 8i2HScCPENwLUd6JeLfYIxeOezJwTv7ZF78wI= MIME-Version: 1.0 Received: by 10.213.0.132 with SMTP id 4mr1243375ebb.8.1257431099184; Thu, 05 Nov 2009 06:24:59 -0800 (PST) In-Reply-To: <1257426023.1436.18.camel@RabbitsDen> References: <1257426023.1436.18.camel@RabbitsDen> Date: Thu, 5 Nov 2009 15:24:59 +0100 Message-ID: <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> From: Paul B Mahol To: "Alexandre \"Sunny\" Kovalenko" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 14:25:01 -0000 On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > It seems that 8.0 discussion is still going on on @current... if I > should have posted this on @stable, please, feel free to chastise me as > appropriate. > > After updating to r198831 my laptop no longer associates with either of > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the > problem. > > Working system: > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 > r198443M: Sat Oct 24 14:03:30 EDT 2009 > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > Non-working system: > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 > r198931: Wed Nov 4 20:56:16 EST 2009 > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > APs are is: > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS > WME > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA > ATH > > Relevant piece of wpa_supplicant.conf is: > > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > eapol_version=2 > > network={ > ssid="AP_SSID" > scan_ssid=1 > priority=1 > proto=WPA > key_mgmt=WPA-PSK > psk="Really secure something" > } > > APs are set not to broadcast SSID, but enabling broadcast does not > change much. > > Running wpa_supplicant with -d shows that it could not match AP_SSID. > > If there is anything else I can provide, please, let me know. What driver are you using? Looking into net80211 svn log for that time period I only see mesh hacks ... From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 15:21:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC6301065679 for ; Thu, 5 Nov 2009 15:21:22 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 1A0B68FC08 for ; Thu, 5 Nov 2009 15:21:21 +0000 (UTC) Received: (qmail 96033 invoked from network); 5 Nov 2009 16:21:20 +0100 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 5 Nov 2009 16:21:20 +0100 Date: Thu, 5 Nov 2009 16:21:18 +0100 From: Kai Gallasch To: freebsd-current@freebsd.org Message-ID: <20091105162118.1a5d8fa5@orwell.free.de> In-Reply-To: <1257244960.98619.36.camel@buffy.york.ac.uk> References: <20091031231545.493cee89@boiler.free.de> <1257244960.98619.36.camel@buffy.york.ac.uk> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.18.2; powerpc-apple-darwin9.7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 15:21:22 -0000 Am Tue, 03 Nov 2009 10:42:40 +0000 schrieb Gavin Atkinson : > On Sat, 2009-10-31 at 23:15 +0100, Kai Gallasch wrote: > > Hi. > > > > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > > > When I try to do a make buildworld or make buildkernel the server > > reboots without any message left in the logs. The same happens > > when building bigger ports (for example ruby18 or perl58) > > > > With 8.0-RC2 debug flags and witness seem to be disabled in the > > standard GENERIC kernel, so unfortunately it is not possible for me > > to build a debug kernel without my server crashing.. > > First place I think I'd start id by running memtest86 on the machine > overnight. This sounds like possible hardware issue to me, it would > be good to see if we can confirm that that is the case. Gavin. memtest86 ran for 18 hours and showed no problem with RAM. --Kai. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 16:29:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3586106566C for ; Thu, 5 Nov 2009 16:28:59 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id A5ACC8FC17 for ; Thu, 5 Nov 2009 16:28:59 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAFuM8kqDaFvH/2dsb2JhbADgPIQ9BIFm X-IronPort-AV: E=Sophos;i="4.44,687,1249272000"; d="scan'208";a="52636101" Received: from danube.cs.uoguelph.ca ([131.104.91.199]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 05 Nov 2009 11:28:58 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id BE6EA1084587 for ; Thu, 5 Nov 2009 11:28:58 -0500 (EST) X-Virus-Scanned: amavisd-new at danube.cs.uoguelph.ca Received: from danube.cs.uoguelph.ca ([127.0.0.1]) by localhost (danube.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4KSiIlVH7p7 for ; Thu, 5 Nov 2009 11:28:57 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id C152E1084525 for ; Thu, 5 Nov 2009 11:28:57 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nA5GaN808229 for ; Thu, 5 Nov 2009 11:36:23 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 5 Nov 2009 11:36:23 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: freebsd-current@freebsd.org In-Reply-To: <4AF0B7DF.9030405@freebsd.org> Message-ID: References: <4AF0B7DF.9030405@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 16:29:00 -0000 Rick Macklem wrote: > I can now reproduce what I think others were seeing as slow reconnects > when using NFSv3 over TCP against a server that disconnects inactive > TCP connections. I have had some luck figuring out what is going on > and can reproduce it fairly easily, but I really need help from someone > who understands the FreeBSD TCP stack. > Ok, I haven't made much progress on this, but here's what little I currently know about it. The problem occurs after a server has dropped an inactive TCP connection for an NFS over TCP mount (in my case a Solaris10 server). When the client does a new connection it, for some reason, sends a RST at almost exactly the same time as the first RPC request on the new TCP connection, causing the server to shut it down. Ok, things I now know don't affect this are: - doing the soshutdown(), soclose() on the old connection. I commented them out and it still happened. - Avoiding the sobind() on the new connection, done before the soconnect(). - Using a non-reserved port#. (The above tests shot down pretty well all the "theories" I could come up with.) The only thing I've found that avoids the problem: - putting a 2sec delay right before the soconnect() call. (A 1sec delay made it hard to reproduce and I've never reproduced it yet with a 2sec delay.) Not much of a fix, though. Now, here's where someone may be able to help? Grep'ng around, I found 4 places where the TCP stack called ip_output() (one in each of tcp_output.c, tcp_subr.c, tcp_timewait.c and tcp_syncache.c) and I put a printf like this just before them: if (flags & TH_RST) printf("sent a reset\n"); (The exact format varies for each, because of where the TCP header flags are and have different printf messages.) Now, the weird part is, that when the extraneous RST is sent to the server, I don't get any printf. (I do get a few of these, but at other times for what appear to be legitimate RSTs.) I can't see anywhere else that the TCP stack would send an RST and, so, I'm stuck w.r.t. figuring out what is sending them? Anyone know of another place the TCP stack would make the send happen? (Or is it queued earlier when I see the printf message, and then the send is "triggered" inside the ip layer when the first data is sent on the new connection?) rick, who is getting sick of looking at this:-) From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 16:35:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7590106566B; Thu, 5 Nov 2009 16:35:18 +0000 (UTC) (envelope-from giovanni.trematerra@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id CCEB48FC1F; Thu, 5 Nov 2009 16:35:17 +0000 (UTC) Received: by ewy18 with SMTP id 18so153676ewy.43 for ; Thu, 05 Nov 2009 08:35:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=DXimuPzMrfOMq0j/spqvK2XT3qrxsIE64kQcycB+jkE=; b=pxdV80apCTx8Wn+7dvR0JM5Wu/SXT9z2GcA8NzlcB/0EmrUGE0NpNR/gI3DTayXYXL +jUJ4J2Hyybv+65HConS29+Lw0GqIvmiJFlQfjBCpsKemoGX6tIvOtf26REfUhvl6++j ColL//ABW9fBQLEqlWR2hR6X0ISITimBoxC5c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=X9+05W4mpmbLwy+fi4T/a/2epfnf6Yu3Srh1FFxXlZGtWKthuqiiMP4wrhliyaACuz DIL1aQ4lFuwyf3JV73yUxdt16UiND82wGhbb/pyZn9fs2wI9a2CBqHiIONSlzLggY55i NWWQzboe8LvV0yAbDd2FiAhS5P3m2dRH2xrDo= MIME-Version: 1.0 Received: by 10.216.89.210 with SMTP id c60mr977754wef.149.1257438916292; Thu, 05 Nov 2009 08:35:16 -0800 (PST) In-Reply-To: <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> <20091105124505.GT2331@deviant.kiev.zoral.com.ua> <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> Date: Thu, 5 Nov 2009 17:35:16 +0100 Message-ID: <4e6cba830911050835uc04023ds91fef552788dfe73@mail.gmail.com> From: Giovanni Trematerra To: Attilio Rao Content-Type: text/plain; charset=ISO-8859-1 Cc: Kostik Belousov , des@des.no, FreeBSD Current Subject: Re: [PATCH] AMD Opteron Rev. E hack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 16:35:18 -0000 On Thu, Nov 5, 2009 at 3:10 PM, Attilio Rao wrote: > > The good way to fix this is to offer an lfence on acq barriers and > leave the other cases untouched, but this could be meaning > re-structure out atomic.h a lot. I will try to think to a good way to > do that when I have more available time. > In the while the WARNING msg will do its job (I can still trimm the > URL path however). > Well, That's not so easy to fix as I thought. Thanks Attilio to point me out. -- Gianni From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 16:40:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AE9E1065670 for ; Thu, 5 Nov 2009 16:40:06 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward8.yandex.ru (forward8.yandex.ru [77.88.61.38]) by mx1.freebsd.org (Postfix) with ESMTP id C7DC58FC1B for ; Thu, 5 Nov 2009 16:40:05 +0000 (UTC) Received: from webmail57.yandex.ru (webmail57.yandex.ru [77.88.61.2]) by forward8.yandex.ru (Yandex) with ESMTP id F191DEF8039 for ; Thu, 5 Nov 2009 19:40:03 +0300 (MSK) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail57.yandex.ru (Yandex) with ESMTP id CA5AA5B8004 for ; Thu, 5 Nov 2009 19:40:03 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail57 X-Yandex-TimeMark: 1257439203 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Thu, 05 Nov 2009 19:40:02 +0300 From: S.N.Grigoriev To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: <1031257439203@webmail57.yandex.ru> Date: Thu, 05 Nov 2009 19:40:03 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 16:40:06 -0000 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" wrote: > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > Hi list, > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > work for me. My machine reboots every time I try to build world. > > I don't think I have a hardware problem: under 7-stable I can build > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > to '0' and no valid dump device configured? Hi Alexandre, I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' output. Where cat I find it? All my sysctl variables are set by default. -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 16:58:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 583AB106568B for ; Thu, 5 Nov 2009 16:58:56 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id C3BD28FC0C for ; Thu, 5 Nov 2009 16:58:55 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id nA5GwgDJ019682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Nov 2009 17:58:42 +0100 (CET) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by acme.spoerlein.net (8.14.3/8.14.3/Submit) id nA5Gwg95019681; Thu, 5 Nov 2009 17:58:42 +0100 (CET) (envelope-from uqs@spoerlein.net) Date: Thu, 5 Nov 2009 17:58:42 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Dominic Fandrey , Alexander Best , freebsd-current@freebsd.org, Paul G Webster Message-ID: <20091105165842.GC34407@acme.spoerlein.net> Mail-Followup-To: Dominic Fandrey , Alexander Best , freebsd-current@freebsd.org, Paul G Webster References: <4AF1869D.6090304@bsdforen.de> <20091104154044.GA96964@wep4035.physik.uni-wuerzburg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091104154044.GA96964@wep4035.physik.uni-wuerzburg.de> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 16:58:56 -0000 On Wed, 04.11.2009 at 16:40:44 +0100, Alexey Shuvaev wrote: > On Wed, Nov 04, 2009 at 02:50:21PM +0100, Dominic Fandrey wrote: > > Alexander Best wrote: > > > Paul G Webster schrieb am 2009-11-03: > > > *lol* just tried this myself and my fdisk output looks just as bad as yours: > > > > I think funny fdisk output is not that much of a problem. > > > > [snip] > > > > What I wonder is - are there more people who witness file > > system corruption upon msdosfs writes (and don't forget > > that either newfs_msdos or fsck_msdosfs is broken as well, > > and that fsck_msdosfs certainly does not recognize > > cross-linked files). The impact is so horrid that I had > > to reformat my portable player (with Windows) and reinstall > > the firmware to get it back going. > > > The relative silence on the mailing list seems to show it is not > the common problem... Indeed, on my main desktop, running 8.0something I regularly copy MP3/OGG files to a FAT16 (!) MP3-Player and albeit the copying is slow and produces "funny" dmesg output, I have yet to observe a corruption of the FS. Bye, Uli From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 17:21:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80338106566C for ; Thu, 5 Nov 2009 17:21:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-px0-f190.google.com (mail-px0-f190.google.com [209.85.216.190]) by mx1.freebsd.org (Postfix) with ESMTP id 564198FC08 for ; Thu, 5 Nov 2009 17:21:29 +0000 (UTC) Received: by pxi28 with SMTP id 28so120571pxi.7 for ; Thu, 05 Nov 2009 09:21:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=qYN4F9EShCVJmLympw65oTz9iIHrzxgwiBI7cEa+83s=; b=AXHuf7K2ZaXHEuK/cfKbaIb+n2I/HKky2eRSS5rbRp3QmStpRVEaw4ljIpUdaU0vpe gmLA88RWecKuFM81LClcFPLzhl9BwouT83IugfWbdSdu9nTtOz+gM55pbhyRDi7YSgi0 4tQtRCf58aQL7QJuBkUhnop2LFS/1VXyvRbQY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Vd9SGE0WZOvrKcowfYQqVhcP8RPq92lgeriCNeptrYIDJ+msc4YREKFzD9WYmL3VG9 Ke3hZG/LB2Dd/5yCN3fKaU7D6C0EnlwfFMCf+njk8OzK6U+reQzHEJyoInyoLqdWsF8m tYbYw377tsVc1bk3PRLj4Z5IlZgdIwTY+0peg= MIME-Version: 1.0 Received: by 10.142.59.18 with SMTP id h18mr355789wfa.121.1257441688888; Thu, 05 Nov 2009 09:21:28 -0800 (PST) In-Reply-To: <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> Date: Thu, 5 Nov 2009 09:21:28 -0800 Message-ID: From: Freddie Cash To: "Sam Fourman Jr." Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 17:21:29 -0000 On Thu, Nov 5, 2009 at 12:19 AM, Sam Fourman Jr. wrote: > On Thu, Nov 5, 2009 at 12:47 AM, Artis Caune wrote: >> 2009/11/5 joe mcguckin : >>> I'm interested inb putting together a file server with lots of disk. >>> >>> What's the state of ZFS? Is it ready for production use? > > We are using it in production and have a 6TB RAIDZ on FreeBSD8 RC2 amd64 > we are quite happy with the FreeBSD 8 setup. > we tried it on FreeBSD 7.2 i386 and did not like it (we got a few panics) > > the only trouble we really had on FreeBSD8 is the sharenfs manpages > are not updated. so we are using the classic /etc/exports instead of the zfs option. The syntax is the same. Anything you can put into /etc/exports you can put into the sharenfs property. In fact, behind the scenes, the sharenfs property is just copied into a private exports file, and the nfs daemon uses that in addition to /etc/exports. The man pages for ZFS are just dumps of the Solaris ones, so a lot of the info is not quite right for a FreeBSD system. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 17:43:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E060A106566B for ; Thu, 5 Nov 2009 17:43:25 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6F88FC18 for ; Thu, 5 Nov 2009 17:43:25 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N66Mk-00022l-Tb for freebsd-current@freebsd.org; Thu, 05 Nov 2009 18:43:22 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Nov 2009 18:43:22 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Nov 2009 18:43:22 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Thu, 05 Nov 2009 09:43:00 -0800 Lines: 82 Message-ID: References: <20091031231545.493cee89@boiler.free.de> <867hu6gvou.fsf@ds4.des.no> <20091104163621.36943807@orwell.free.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: Sender: news Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 17:43:26 -0000 Adrian Chadd wrote: > 2009/11/5 Mark Atkinson : > >> I'll answer my own question, no: >> >> http://support.amd.com/us/Processor_TechDocs/25481.pdf >> >> Although the some of the posts in >> >> http://bugzilla.kernel.org/show_bug.cgi?id=11305 >> >> indicate any model < 0x40. Someone must have actually narrowed the range. > > Is there a FreeBSD PR or errata URL which can be linked to instead, > complete with copies of the above in it? If you read the mysql related blog post on it: http://timetobleed.com/mysql-doesnt-always-suck-this-time-its-amd/ Someone in the comments suggests this is AMD errata 147 and quotes the text. I'll include a copy of the comment here below for the mail archives (and since urls tend to disappear). # silverjam The kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=11305 Which references an AMD "errata 147" from "Revision Guide for AMD Athlon 64 and AMD Opteron Processors." http://support.amd.com/us/Processor_TechDocs/25759.pdf Which says: """ Potential Violation of Read Ordering Rules Between Semaphore Operations and Unlocked Read-Modify-Write Instructions Description Under a highly specific set of internal timing circumstances, the memory read ordering between a semaphore operation and a subsequent read-modify-write instruction (an instruction that uses the same memory location as both a source and destination) may be incorrect and allow the read-modifywrite instruction to operate on the memory location ahead of the completion of the semaphore operation. The erratum will not occur if there is a LOCK prefix on the read-modify-write instruction. This erratum does not apply if the read-only value in MSRC001_1023h[33] is 1b. Potential Effect on System In the unlikely event that the condition described above occurs, the read-modify-write instruction (in the critical section) may operate on data that existed prior to the semaphore operation. This erratum can only occur in multiprocessor or multicore configurations. Suggested Workaround To provide a workaround for this unlikely event, software can perform any of the following actions for multiprocessor or multicore systems: Place a LFENCE instruction between the semaphore operation and any subsequent read-modifywrite instruction(s) in the critical section. Use a LOCK prefix with the read-modify-write instruction. Decompose the read-modify-write instruction into separate instructions. No workaround is necessary if software checks that MSRC001_1023h[33] is set on all processors that may execute the code. The value in MSRC001_1023h[33] may not be the same on all processors in a multi-processor system. Fix Planned: Yes """ From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 17:49:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 303E61065692 for ; Thu, 5 Nov 2009 17:49:28 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout6.freenet.de (mout6.freenet.de [IPv6:2001:748:100:40::2:8]) by mx1.freebsd.org (Postfix) with ESMTP id BF91B8FC1A for ; Thu, 5 Nov 2009 17:49:27 +0000 (UTC) Received: from [195.4.92.22] (helo=12.mx.freenet.de) by mout6.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #92) id 1N66Sc-00011Y-Ew; Thu, 05 Nov 2009 18:49:26 +0100 Received: from tbfde.t.pppool.de ([89.55.191.222]:12788 helo=ernst.jennejohn.org) by 12.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1N66Sc-00064k-7m; Thu, 05 Nov 2009 18:49:26 +0100 Date: Thu, 5 Nov 2009 18:49:25 +0100 From: Gary Jennejohn To: S.N.Grigoriev Message-ID: <20091105184925.16b55c43@ernst.jennejohn.org> In-Reply-To: <1031257439203@webmail57.yandex.ru> References: <1031257439203@webmail57.yandex.ru> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 17:49:28 -0000 On Thu, 05 Nov 2009 19:40:03 +0300 S.N.Grigoriev wrote: > > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > wrote: > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > Hi list, > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > work for me. My machine reboots every time I try to build world. > > > I don't think I have a hardware problem: under 7-stable I can build > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > to '0' and no valid dump device configured? > > Hi Alexandre, > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > output. Where cat I find it? All my sysctl variables are set by > default. Do you have "options DDB" in your kernel config file? --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 18:34:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 511EF10656C5 for ; Thu, 5 Nov 2009 18:34:26 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward10.yandex.ru (forward10.yandex.ru [77.88.61.49]) by mx1.freebsd.org (Postfix) with ESMTP id 088338FC1E for ; Thu, 5 Nov 2009 18:34:25 +0000 (UTC) Received: from webmail71.yandex.ru (webmail71.yandex.ru [77.88.60.175]) by forward10.yandex.ru (Yandex) with ESMTP id 61A921320AA9; Thu, 5 Nov 2009 21:34:24 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by webmail71.yandex.ru (Yandex) with ESMTP id 430A29C43EE; Thu, 5 Nov 2009 21:34:24 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail71 X-Yandex-TimeMark: 1257446064 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Thu, 05 Nov 2009 21:34:23 +0300 From: S.N.Grigoriev To: gary.jennejohn@freenet.de In-Reply-To: <20091105184925.16b55c43@ernst.jennejohn.org> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> MIME-Version: 1.0 Message-Id: <31221257446063@webmail71.yandex.ru> Date: Thu, 05 Nov 2009 21:34:23 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 18:34:26 -0000 05.11.09, 18:49, "Gary Jennejohn" : > On Thu, 05 Nov 2009 19:40:03 +0300 > S.N.Grigoriev wrote: > > > > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > > wrote: > > > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > > Hi list, > > > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > > work for me. My machine reboots every time I try to build world. > > > > I don't think I have a hardware problem: under 7-stable I can build > > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > > to '0' and no valid dump device configured? > > > > Hi Alexandre, > > > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > > output. Where cat I find it? All my sysctl variables are set by > > default. > Do you have "options DDB" in your kernel config file? > --- > Gary Jennejohn Hi Gary, my current kernel is GENERIC, so I don't have "options DDB". -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 19:01:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E97C7106566B for ; Thu, 5 Nov 2009 19:01:40 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by mx1.freebsd.org (Postfix) with ESMTP id 809228FC23 for ; Thu, 5 Nov 2009 19:01:40 +0000 (UTC) Received: by iwn27 with SMTP id 27so243579iwn.7 for ; Thu, 05 Nov 2009 11:01:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=TbG3fxLOXd5GAQyUrFdnWRA6WaerwoTzEU1iAT4gf1o=; b=APbQbgHDZONCtJNitH4L5Y8YjYLIiHtzAeoFGUjh3yU17oHuC7sQhGNe3GJ3GVYiTv 1ouBboabmrU0yW95s5cJDetGQtEEmHcxl+gRIilR3BmDgda37dk84bA5t88X95QTNObh LJ7ab8ElF/OHs0Mf3igkn3fACM/De57v4D5wk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BM9g2wcdKAbvoLI5R53S8hV0R9GFFcjyeIqs6df+7URQwR+SgVqH210bNQqI6/Io8T baXG/d6kQMlHZp5iQHXj4oDY5APp+XMPEz9dj1VoYLS19R795I9Yo4UJu9OQCbd2j+FB vItcQDbR7dFUesq4Rxf0uPsGM8/KMBI/lsuUU= MIME-Version: 1.0 Received: by 10.231.20.230 with SMTP id g38mr2286915ibb.49.1257447699934; Thu, 05 Nov 2009 11:01:39 -0800 (PST) In-Reply-To: <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> References: <1257426023.1436.18.camel@RabbitsDen> <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> Date: Thu, 5 Nov 2009 14:01:39 -0500 Message-ID: From: "Alexandre \"Sunny\" Kovalenko" To: Paul B Mahol Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 19:01:41 -0000 On Thu, Nov 5, 2009 at 9:24 AM, Paul B Mahol wrote: > On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > > It seems that 8.0 discussion is still going on on @current... if I > > should have posted this on @stable, please, feel free to chastise me as > > appropriate. > > > > After updating to r198831 my laptop no longer associates with either of > > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the > > problem. > > > > Working system: > > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 > > r198443M: Sat Oct 24 14:03:30 EDT 2009 > > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > > > Non-working system: > > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 > > r198931: Wed Nov 4 20:56:16 EST 2009 > > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > > > APs are is: > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS > > WME > > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA > > ATH > > > > Relevant piece of wpa_supplicant.conf is: > > > > ctrl_interface=/var/run/wpa_supplicant > > ctrl_interface_group=wheel > > eapol_version=2 > > > > network={ > > ssid="AP_SSID" > > scan_ssid=1 > > priority=1 > > proto=WPA > > key_mgmt=WPA-PSK > > psk="Really secure something" > > } > > > > APs are set not to broadcast SSID, but enabling broadcast does not > > change much. > > > > Running wpa_supplicant with -d shows that it could not match AP_SSID. > > > > If there is anything else I can provide, please, let me know. > > What driver are you using? > Looking into net80211 svn log for that time period I only see mesh hacks > ... > I am using ath (I am away from my laptop ATM -- I could provide part number later today). I have seen mesh changes in there and that's when I gave up and posted -- I am not nearly enough qualified to figure out which ones could or could not impact normal operation. -- Alexandre "Sunny" Kovalenko. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 19:08:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B9771065693 for ; Thu, 5 Nov 2009 19:08:19 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward10.yandex.ru (forward10.yandex.ru [77.88.61.49]) by mx1.freebsd.org (Postfix) with ESMTP id 1F12D8FC2E for ; Thu, 5 Nov 2009 19:08:18 +0000 (UTC) Received: from webmail75.yandex.ru (webmail75.yandex.ru [77.88.60.179]) by forward10.yandex.ru (Yandex) with ESMTP id 8F0A11320BA5; Thu, 5 Nov 2009 22:08:14 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by webmail75.yandex.ru (Yandex) with ESMTP id 6DBADA803EA; Thu, 5 Nov 2009 22:08:14 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail75 X-Yandex-TimeMark: 1257448094 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Thu, 05 Nov 2009 22:08:13 +0300 From: S.N.Grigoriev To: Etienne Robillard In-Reply-To: <4AF31D87.9000207@gmail.com> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> <4AF31D87.9000207@gmail.com> MIME-Version: 1.0 Message-Id: <40521257448093@webmail75.yandex.ru> Date: Thu, 05 Nov 2009 22:08:13 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 19:08:19 -0000 05.11.09, 13:46, "Etienne Robillard" : > S.N.Grigoriev wrote: > > > > 05.11.09, 18:49, "Gary Jennejohn" : > > > >> On Thu, 05 Nov 2009 19:40:03 +0300 > >> S.N.Grigoriev wrote: > >>> 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > >>> wrote: > >>> > >>>> On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > >>>>> Hi list, > >>>>> > >>>>> I can confirm I've seen the same problem. After upgrading from 7-stable > >>>>> to 8.0-RC2 my machine just reboots during 'make buildworld' without > >>>>> diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > >>>>> work for me. My machine reboots every time I try to build world. > >>>>> I don't think I have a hardware problem: under 7-stable I can build > >>>>> world/kernel for both 7-stable and 8.0-RC2 without problems. > >>>>> > >>>> Is it by any chance possible that you have 'debug.debugger_on_panic' set > >>>> to '0' and no valid dump device configured? > >>> Hi Alexandre, > >>> > >>> I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > >>> output. Where cat I find it? All my sysctl variables are set by > >>> default. > >> Do you have "options DDB" in your kernel config file? > >> --- > >> Gary Jennejohn > > > > Hi Gary, > > > > my current kernel is GENERIC, so I don't have "options DDB". > I have RC2 with amd64 and buildworld/installworld runs fine. > Maybe you memory (ram) problems ? I had to remove one 512mb clib > in order to boot... ;-) > Hope this helps, > Etienne Hi Etienne, I think it is unlikely. I've done on this machine (under FreeBSD 7.1 and 7.2 and some Linux versions) very much compilations without issues. -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 19:45:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A71FC1065676 for ; Thu, 5 Nov 2009 19:45:02 +0000 (UTC) (envelope-from robillard.etienne@gmail.com) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 7CCA28FC15 for ; Thu, 5 Nov 2009 19:45:02 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=UTF-8 Received: from [192.168.0.100] ([70.82.236.228]) by VL-MR-MR002.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0KSN00AICG31JA10@VL-MR-MR002.ip.videotron.ca> for freebsd-current@freebsd.org; Thu, 05 Nov 2009 13:45:02 -0500 (EST) Message-id: <4AF31D87.9000207@gmail.com> Date: Thu, 05 Nov 2009 13:46:31 -0500 From: Etienne Robillard Organization: Green Tea Hackers Club User-Agent: Thunderbird 2.0.0.23 (X11/20090817) To: "S.N.Grigoriev" References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> In-reply-to: <31221257446063@webmail71.yandex.ru> X-Enigmail-Version: 0.95.0 Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 19:45:02 -0000 S.N.Grigoriev wrote: > > 05.11.09, 18:49, "Gary Jennejohn" : > >> On Thu, 05 Nov 2009 19:40:03 +0300 >> S.N.Grigoriev wrote: >>> 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" >>> wrote: >>> >>>> On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: >>>>> Hi list, >>>>> >>>>> I can confirm I've seen the same problem. After upgrading from 7-stable >>>>> to 8.0-RC2 my machine just reboots during 'make buildworld' without >>>>> diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not >>>>> work for me. My machine reboots every time I try to build world. >>>>> I don't think I have a hardware problem: under 7-stable I can build >>>>> world/kernel for both 7-stable and 8.0-RC2 without problems. >>>>> >>>> Is it by any chance possible that you have 'debug.debugger_on_panic' set >>>> to '0' and no valid dump device configured? >>> Hi Alexandre, >>> >>> I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' >>> output. Where cat I find it? All my sysctl variables are set by >>> default. >> Do you have "options DDB" in your kernel config file? >> --- >> Gary Jennejohn > > Hi Gary, > > my current kernel is GENERIC, so I don't have "options DDB". I have RC2 with amd64 and buildworld/installworld runs fine. Maybe you memory (ram) problems ? I had to remove one 512mb clib in order to boot... ;-) Hope this helps, Etienne -- Etienne Robillard Green Tea Hackers Club Blog: PGP Fingerprint: 178A BF04 23F0 2BF5 535D 4A57 FD53 FD31 98DC 4E57 From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 23:17:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD8E91065676 for ; Thu, 5 Nov 2009 23:17:24 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 588F68FC17 for ; Thu, 5 Nov 2009 23:17:24 +0000 (UTC) Received: by fxm27 with SMTP id 27so100121fxm.3 for ; Thu, 05 Nov 2009 15:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=GEM23oGB7EPkAe7cmzvJ4TWZQqcD1qsskdm5rhlnagI=; b=tFIQthOQwycPrAk9jWSaUnypn1bJ/WaZ61koPoZuK1r+L0bioPsi+6XJhJZShKYusY 9UB+adJNNGelsEIPALeSyZOgCKfHym8RWbmZ05O0VamFr4lyqg8hlqMxcQpk5jzi299K OAVWuoWk4hYIKSHgz5IlBMXsZT7E9+MSdznLM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TJvX03rKAbPjO60Z0TyM+QIXQ55A9X6+AE9ulj1Ta0vgxugMfYMKGJOzFxL6Gf2Hiz mdHaVq9qYVlpiYzHzkV/+epiSZjnb5JJkFCAi5INuGj09ShcdTT1pf8MzdgfJFxDExFN Zq8CB10QxjeekL9B6bfHOXLfe1YevYt9dRqbA= MIME-Version: 1.0 Received: by 10.239.168.144 with SMTP id k16mr367307hbe.103.1257463043350; Thu, 05 Nov 2009 15:17:23 -0800 (PST) In-Reply-To: References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> Date: Thu, 5 Nov 2009 23:17:23 +0000 Message-ID: From: krad To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Sam Fourman Jr." , freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 23:17:24 -0000 2009/11/5 Freddie Cash > On Thu, Nov 5, 2009 at 12:19 AM, Sam Fourman Jr. > wrote: > > On Thu, Nov 5, 2009 at 12:47 AM, Artis Caune > wrote: > >> 2009/11/5 joe mcguckin : > >>> I'm interested inb putting together a file server with lots of disk. > >>> > >>> What's the state of ZFS? Is it ready for production use? > > > > We are using it in production and have a 6TB RAIDZ on FreeBSD8 RC2 amd64 > > we are quite happy with the FreeBSD 8 setup. > > we tried it on FreeBSD 7.2 i386 and did not like it (we got a few panics) > > > > the only trouble we really had on FreeBSD8 is the sharenfs manpages > > are not updated. so we are using the classic /etc/exports instead of the > zfs option. > > The syntax is the same. Anything you can put into /etc/exports you > can put into the sharenfs property. In fact, behind the scenes, the > sharenfs property is just copied into a private exports file, and the > nfs daemon uses that in addition to /etc/exports. > > The man pages for ZFS are just dumps of the Solaris ones, so a lot of > the info is not quite right for a FreeBSD system. > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > unless im missing something you have to do it the legacy way (root@carrera)-(23:13:05)-(~) 0 $ zfs set sharenfs=yes zdump/web (root@carrera)-(23:13:23)-(~) 0 $ showmount -e 127.0.0.1 Exports list on 127.0.0.1: /videos Everyone (root@carrera)-(23:13:26)-(~) 0 $ From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 23:33:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66C10106566C for ; Thu, 5 Nov 2009 23:33:26 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-px0-f190.google.com (mail-px0-f190.google.com [209.85.216.190]) by mx1.freebsd.org (Postfix) with ESMTP id 3C4CA8FC1C for ; Thu, 5 Nov 2009 23:33:25 +0000 (UTC) Received: by pxi28 with SMTP id 28so327177pxi.7 for ; Thu, 05 Nov 2009 15:33:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=pPdU2m57Sgmqb4CpajEvjDz0bYp84TrJ0JtKOSK1Xjg=; b=DuTG90rjUmJZWAukif5N3RGOOVxo60Cm+wJjRRfsJy14SJ8JGVw6P1yqr88eBxVUza psqvR6XcA1/WrgVZiQe+PdLbrHI96pyBgiYPBY1l9A7UmQQLgg2mzdkJPKy5jPUDcRLi ZiHPtzbYMRc9lSZI2YcX9CJZU50Tu+MhBQgEo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=W13WuCQFJByI3OCbM31Nv3OhbNKN/GxiOzIcXn020F4LT4D6bOvS5OMysgQ2ESaapC PkIOIcvQ/E2zexUgirFg/3Dg/f3DcWmiiBatAn6Kx37f5FzRvwNLG1723nWjDdha4D7P 5DQ7u38UON6Yc9sn6TEQhgpnq3hsUcE9u81wM= MIME-Version: 1.0 Received: by 10.142.247.6 with SMTP id u6mr383321wfh.181.1257464005561; Thu, 05 Nov 2009 15:33:25 -0800 (PST) In-Reply-To: References: <17E3C299-725B-434E-805D-CA0C1EA9C8B9@via.net> <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <11167f520911050019k17137f3q6e36614e2178b12d@mail.gmail.com> Date: Thu, 5 Nov 2009 15:33:25 -0800 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 23:33:26 -0000 On Thu, Nov 5, 2009 at 3:17 PM, krad wrote: > 2009/11/5 Freddie Cash >> The syntax is the same. Anything you can put into /etc/exports you >> can put into the sharenfs property. In fact, behind the scenes, the >> sharenfs property is just copied into a private exports file, and the >> nfs daemon uses that in addition to /etc/exports. >> >> The man pages for ZFS are just dumps of the Solaris ones, so a lot of >> the info is not quite right for a FreeBSD system. > > unless im missing something you have to do it the legacy way > > (root@carrera)-(23:13:05)-(~) 0 > $ zfs set sharenfs=yes zdump/web > (root@carrera)-(23:13:23)-(~) 0 > $ showmount -e 127.0.0.1 > Exports list on 127.0.0.1: > /videos Everyone > (root@carrera)-(23:13:26)-(~) 0 > $ Put the settings you would normally put into /etc/exports into the sharenfs property: [fcash@megadrive ~]$ zfs get sharenfs storage/backup NAME PROPERTY VALUE SOURCE storage/backup sharenfs -maproot=root 192.168.0.12 local [fcash@megadrive ~]$ showmount -e Exports list on localhost: /storage/backup 192.168.0.12 -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 5 23:49:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 093BE1065692 for ; Thu, 5 Nov 2009 23:49:13 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7AC8FC0A for ; Thu, 5 Nov 2009 23:49:12 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 25so147326eya.9 for ; Thu, 05 Nov 2009 15:49:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=Ij/Vh9mDZ073OcAcMaVYezenCb2B6dAL9jHJ2A0Fo+c=; b=W/Xt7YSwLD97eid+ZnZ54rjEufRAowc7CwSXiFxBvTtFexFFJb3mHOen1vW/sgjreW e7NCZ5oG/fVF074EgKNwykC40qcJiJQBcXH/L0HEva6M7kFobR84DsTeGPl2oPTzKmYj UkD85jlT9g2DRPmaNxlkXjmDilvkQCtefatcw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=noQqNYB0jqSDMH1SNpybElunHtauFr62MfaS6WWQId/zW6OZ0QEYAtWdrCa9sRdM17 Q9rkqiXaH3yN9KjwhmGGJlv/TbbDexTWlhRlApLSTEJgw+O75f+FBk63GaazYSMF80/w FeaeQrwETKMnJdpgIlGpLmaHwgWMUd2F9t7vU= Received: by 10.213.24.20 with SMTP id t20mr2169356ebb.49.1257464951343; Thu, 05 Nov 2009 15:49:11 -0800 (PST) Received: from rui-macbook.lan (bl7-119-248.dsl.telepac.pt [85.240.119.248]) by mx.google.com with ESMTPS id 5sm501419eyf.39.2009.11.05.15.49.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 05 Nov 2009 15:49:09 -0800 (PST) Sender: Rui Paulo References: <4AF0B7DF.9030405@freebsd.org> In-Reply-To: Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Message-Id: <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Rui Paulo Date: Thu, 5 Nov 2009 23:49:08 +0000 To: Rick Macklem X-Mailer: Apple Mail (2.1076) Cc: freebsd-current@freebsd.org Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 23:49:13 -0000 On 5 Nov 2009, at 16:36, Rick Macklem wrote: > > > Rick Macklem wrote: >> I can now reproduce what I think others were seeing as slow >> reconnects >> when using NFSv3 over TCP against a server that disconnects inactive >> TCP connections. I have had some luck figuring out what is going on >> and can reproduce it fairly easily, but I really need help from >> someone >> who understands the FreeBSD TCP stack. >> > Ok, I haven't made much progress on this, but here's what little I > currently know about it. > > The problem occurs after a server has dropped an inactive TCP > connection > for an NFS over TCP mount (in my case a Solaris10 server). When the > client > does a new connection it, for some reason, sends a RST at almost > exactly > the same time as the first RPC request on the new TCP connection, > causing > the server to shut it down. > > Ok, things I now know don't affect this are: > - doing the soshutdown(), soclose() on the old connection. I commented > them out and it still happened. > - Avoiding the sobind() on the new connection, done before the > soconnect(). > - Using a non-reserved port#. > (The above tests shot down pretty well all the "theories" I could > come up > with.) > > The only thing I've found that avoids the problem: > - putting a 2sec delay right before the soconnect() call. (A 1sec > delay > made it hard to reproduce and I've never reproduced it yet with a > 2sec > delay.) > Not much of a fix, though. > > Now, here's where someone may be able to help? > > Grep'ng around, I found 4 places where the TCP stack called ip_output > () > (one in each of tcp_output.c, tcp_subr.c, tcp_timewait.c and > tcp_syncache.c) and I put a printf like this just before them: > if (flags & TH_RST) > printf("sent a reset\n"); > > (The exact format varies for each, because of where the TCP > header flags are and have different printf messages.) > > Now, the weird part is, that when the extraneous RST is sent to the > server, I don't get any printf. (I do get a few of these, but at other > times for what appear to be legitimate RSTs.) > > I can't see anywhere else that the TCP stack would send an RST and, > so, > I'm stuck w.r.t. figuring out what is sending them? > > Anyone know of another place the TCP stack would make the send happen? > (Or is it queued earlier when I see the printf message, and then the > send is "triggered" inside the ip layer when the first data is sent on > the new connection?) Are you running TSO? -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 00:40:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A1F6106566B for ; Fri, 6 Nov 2009 00:40:13 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id CAD358FC0C for ; Fri, 6 Nov 2009 00:40:12 +0000 (UTC) Received: by ewy18 with SMTP id 18so386034ewy.43 for ; Thu, 05 Nov 2009 16:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=bTJj3cFAyKCsnc7xIy7xG3uyPi65cCBRESYvykeaFX0=; b=rnMkSkoUiL3+quYbhqDpsTT/q+PmzDTgj+MHtZhAFEDnt8DC1aZStrNueucm1sEKO5 yoe7NXga4s+QzsEhArVO6cjf1F6LXDlx/iWBKlvkjNmU2eRorx+pKX+SeiqTmxTbdjGq nFMh1tVSqPrmOr+v8w/ZvYElPdwJ/RkCZOIxs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=o9SUnUVJTe71n3M7SQiQxqrK2lIqVG4OTRdin16bWj1JeayUp3OEU6dlyCetyav4kf ef/M8NB45Gmo42vcm7JVDG4fpWE4zUMSuguEoP8GCXQ0I5s3xNk92TjS+gZm167dmASF e8IWKTOB4Qbe2QDPDAF+FDMHL6VSJcFIoUYqc= Received: by 10.213.0.152 with SMTP id 24mr4458374ebb.52.1257468011786; Thu, 05 Nov 2009 16:40:11 -0800 (PST) Received: from rui-macbook.lan (bl7-119-248.dsl.telepac.pt [85.240.119.248]) by mx.google.com with ESMTPS id 5sm4784574eyf.23.2009.11.05.16.39.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 05 Nov 2009 16:39:57 -0800 (PST) Sender: Rui Paulo References: <4AF0B7DF.9030405@freebsd.org> In-Reply-To: Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Message-Id: <912FE42D-F2A2-422B-8681-AE27CA428DD5@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Rui Paulo Date: Fri, 6 Nov 2009 00:39:47 +0000 To: Rick Macklem X-Mailer: Apple Mail (2.1076) Cc: freebsd-current@freebsd.org Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 00:40:13 -0000 On 5 Nov 2009, at 16:36, Rick Macklem wrote: > Rick Macklem wrote: >> I can now reproduce what I think others were seeing as slow >> reconnects >> when using NFSv3 over TCP against a server that disconnects inactive >> TCP connections. I have had some luck figuring out what is going on >> and can reproduce it fairly easily, but I really need help from >> someone >> who understands the FreeBSD TCP stack. >> > Ok, I haven't made much progress on this, but here's what little I > currently know about it. > > The problem occurs after a server has dropped an inactive TCP > connection > for an NFS over TCP mount (in my case a Solaris10 server). When the > client > does a new connection it, for some reason, sends a RST at almost > exactly > the same time as the first RPC request on the new TCP connection, > causing > the server to shut it down. > > Ok, things I now know don't affect this are: > - doing the soshutdown(), soclose() on the old connection. I commented > them out and it still happened. > - Avoiding the sobind() on the new connection, done before the > soconnect(). > - Using a non-reserved port#. > (The above tests shot down pretty well all the "theories" I could > come up > with.) > > The only thing I've found that avoids the problem: > - putting a 2sec delay right before the soconnect() call. (A 1sec > delay > made it hard to reproduce and I've never reproduced it yet with a 2sec > delay.) > Not much of a fix, though. > > Now, here's where someone may be able to help? > > Grep'ng around, I found 4 places where the TCP stack called ip_output > () > (one in each of tcp_output.c, tcp_subr.c, tcp_timewait.c and > tcp_syncache.c) and I put a printf like this just before them: > if (flags & TH_RST) > printf("sent a reset\n"); > > (The exact format varies for each, because of where the TCP > header flags are and have different printf messages.) > > Now, the weird part is, that when the extraneous RST is sent to the > server, I don't get any printf. (I do get a few of these, but at other > times for what appear to be legitimate RSTs.) > > I can't see anywhere else that the TCP stack would send an RST and, > so, > I'm stuck w.r.t. figuring out what is sending them? > > Anyone know of another place the TCP stack would make the send happen? > (Or is it queued earlier when I see the printf message, and then the > send is "triggered" inside the ip layer when the first data is sent on > the new connection?) > > rick, who is getting sick of looking at this:-) One option would be trying to calling ddb on top of ip_output() and checking the backtrace. -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 04:52:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB9431065670; Fri, 6 Nov 2009 04:52:54 +0000 (UTC) (envelope-from bland@bbnest.net) Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id AFD078FC17; Fri, 6 Nov 2009 04:52:54 +0000 (UTC) Received: from hub.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id 072588FF67; Fri, 6 Nov 2009 13:52:52 +0900 (JST) Received: from hub.bbnest.net (localhost [127.0.0.1]) by hub.bbnest.net (8.14.3/8.14.3) with ESMTP id nA64qnIu001567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Nov 2009 13:52:49 +0900 (JST) (envelope-from bland@bbnest.net) Received: (from www@localhost) by hub.bbnest.net (8.14.3/8.14.3/Submit) id nA64qmLU001565; Fri, 6 Nov 2009 13:52:48 +0900 (JST) (envelope-from bland@bbnest.net) X-Authentication-Warning: hub.bbnest.net: www set sender to bland@bbnest.net using -f To: Alexander Nedotsukov MIME-Version: 1.0 Date: Fri, 06 Nov 2009 13:52:48 +0900 From: Alexander Nedotsukov In-Reply-To: <202969100caf7f0bb8098572b0dad622@mail> References: <202969100caf7f0bb8098572b0dad622@mail> Message-ID: <20d8e6193795d83f9ffa30ab94bf86eb@mail> X-Sender: bland@bbnest.net User-Agent: RoundCube Webmail/0.2a Content-Type: multipart/mixed; boundary="=_958d35a45c231854b4ffb480c87eec69" X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Fri Nov 6 13:52:52 2009 X-DSPAM-Confidence: 0.9991 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4af3aba415681856066157 X-Mailman-Approved-At: Fri, 06 Nov 2009 05:00:22 +0000 Cc: current@freebsd.org, Andrew Thompson , Hans Petter Selasky Subject: Re: umass problem. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 04:52:55 -0000 --=_958d35a45c231854b4ffb480c87eec69 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Well I do. This is a regression in EHCI driver introduced along the new usb stack. Please review patch attached. Thanks, Alexander. On Tue, 20 Oct 2009 10:53:36 +0900, Alexander Nedotsukov wrote: > Hi, > > I can reproduce this reliably with simple dd if=/dev/da0. At the end > external USB drive turns off the lights (tough it still spinning) and > system fall into the state where it is impossible to reboot it cleanly. I > can get drive back only after full power cycle (simple reboot is not > enough). Using same drive under moderate load seems mostly to work. It also > is used to work under 7.2. > > Anyone have an idea what this could be? --=_958d35a45c231854b4ffb480c87eec69 Content-Transfer-Encoding: base64 Content-Type: application/octet-stream; charset=UTF-8; name=ehci-lostintr.patch; Content-Disposition: attachment; filename=ehci-lostintr.patch; SW5kZXg6IGNvbnRyb2xsZXIvZWhjaV9wY2kuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBjb250cm9sbGVyL2Vo Y2lfcGNpLmMJKHJldmlzaW9uIDE5ODk2NikKKysrIGNvbnRyb2xsZXIvZWhjaV9wY2kuYwkod29y a2luZyBjb3B5KQpAQCAtNDE0LDYgKzQxNCwyMCBAQAogCQlzYy0+c2NfaW50cl9oZGwgPSBOVUxM OwogCQlnb3RvIGVycm9yOwogCX0KKworCS8qIEVuYWJsZSB3b3JrYXJvdW5kIGZvciBkcm9wcGVk IGludGVycnVwdHMgYXMgcmVxdWlyZWQgKi8KKwlzd2l0Y2ggKHBjaV9nZXRfdmVuZG9yKHNlbGYp KSB7CisJY2FzZSBQQ0lfRUhDSV9WRU5ET1JJRF9BVEk6CisJY2FzZSBQQ0lfRUhDSV9WRU5ET1JJ RF9WSUE6CisJCXNjLT5zY19mbGFncyB8PSBFSENJX1NDRkxHX0xPU1RJTlRSQlVHOworCQlpZiAo Ym9vdHZlcmJvc2UpCisJCQlkZXZpY2VfcHJpbnRmKHNlbGYsCisJCQkgICAgIkRyb3BwZWQgaW50 ZXJydXB0cyB3b3JrYXJvdW5kIGVuYWJsZWRcbiIpOworCQlicmVhazsKKwlkZWZhdWx0OgorCQli cmVhazsKKwl9CisKIAllaGNpX3BjaV90YWtlY29udHJvbGxlcihzZWxmKTsKIAogCS8qIFVuZG9j dW1lbnRlZCBxdWlya3MgdGFrZW4gZnJvbSBMaW51eCAqLwpJbmRleDogY29udHJvbGxlci9laGNp LmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PQotLS0gY29udHJvbGxlci9laGNpLmMJKHJldmlzaW9uIDE5ODk2NikKKysr IGNvbnRyb2xsZXIvZWhjaS5jCSh3b3JraW5nIGNvcHkpCkBAIC0xMTcsNiArMTE3LDcgQEAKIHN0 YXRpYyB2b2lkIGVoY2lfZGV2aWNlX2RvbmUoc3RydWN0IHVzYl94ZmVyICp4ZmVyLCB1c2JfZXJy b3JfdCBlcnJvcik7CiBzdGF0aWMgdWludDhfdCBlaGNpX2NoZWNrX3RyYW5zZmVyKHN0cnVjdCB1 c2JfeGZlciAqeGZlcik7CiBzdGF0aWMgdm9pZCBlaGNpX3RpbWVvdXQodm9pZCAqYXJnKTsKK3N0 YXRpYyB2b2lkIGVoY2lfaW50cnFfdGltZW91dCh2b2lkICphcmcpOwogc3RhdGljIHZvaWQgZWhj aV9yb290X2ludHIoZWhjaV9zb2Z0Y190ICpzYyk7CiAKIHN0cnVjdCBlaGNpX3N0ZF90ZW1wIHsK QEAgLTI0Myw2ICsyNDQsNyBAQAogCURQUklOVEYoInN0YXJ0XG4iKTsKIAogCXVzYl9jYWxsb3V0 X2luaXRfbXR4KCZzYy0+c2NfdG1vX3BjZCwgJnNjLT5zY19idXMuYnVzX210eCwgMCk7CisJdXNi X2NhbGxvdXRfaW5pdF9tdHgoJnNjLT5zY190bW9faW50cnEsICZzYy0+c2NfYnVzLmJ1c19tdHgs IDApOwogCiAjaWYgVVNCX0RFQlVHCiAJaWYgKGVoY2lkZWJ1ZyA+IDIpIHsKQEAgLTUxOSw2ICs1 MjEsNyBAQAogewogCVVTQl9CVVNfTE9DSygmc2MtPnNjX2J1cyk7CiAKKwl1c2JfY2FsbG91dF9z dG9wKCZzYy0+c2NfdG1vX2ludHJxKTsKIAl1c2JfY2FsbG91dF9zdG9wKCZzYy0+c2NfdG1vX3Bj ZCk7CiAKIAlFT1dSSVRFNChzYywgRUhDSV9VU0JJTlRSLCBzYy0+c2NfZWludHJzKTsKQEAgLTE0 NzIsNiArMTQ3NSwyNiBAQAogCX0KIH0KIAorLyoKKyAqIFNvbWUgRUhDSSBjaGlwcyBmcm9tIFZJ QSAvIEFUSSBzZWVtIHRvIHRyaWdnZXIgaW50ZXJydXB0cyBiZWZvcmUgd3JpdGluZworICogYmFj ayB0aGUgcVREIHN0YXR1cywgb3IgbWlzcyBzaWduYWxsaW5nIG9jY2FzaW9uYWxseSB1bmRlciBo ZWF2eSBsb2FkLgorICogSWYgdGhlIGhvc3QgbWFjaGluZSBpcyB0b28gZmFzdCwgd2UgY2FuIG1p c3MgdHJhbnNhY3Rpb24gY29tcGxldGlvbiAtIHdoZW4KKyAqIHdlIHNjYW4gdGhlIGFjdGl2ZSBs aXN0IHRoZSB0cmFuc2FjdGlvbiBzdGlsbCBzZWVtcyB0byBiZSBhY3RpdmUuIFRoaXMKKyAqIGdl bmVyYWxseSBleGhpYml0cyBpdHNlbGYgYXMgYSB1bWFzcyBzdGFsbCB0aGF0IG5ldmVyIHJlY292 ZXJzLgorICoKKyAqIFdlIHdvcmsgYXJvdW5kIHRoaXMgYmVoYXZpb3VyIGJ5IHNldHRpbmcgdXAg dGhpcyBjYWxsYmFjayBhZnRlciBhbnkgc29mdGludHIKKyAqIHRoYXQgY29tcGxldGVzIHdpdGgg dHJhbnNhY3Rpb25zIHN0aWxsIHBlbmRpbmcsIGdpdmluZyB1cyBhbm90aGVyIGNoYW5jZSB0bwor ICogY2hlY2sgZm9yIGNvbXBsZXRpb24gYWZ0ZXIgdGhlIHdyaXRlYmFjayBoYXMgdGFrZW4gcGxh Y2UuCisgKi8KK3ZvaWQKK2VoY2lfaW50cnFfdGltZW91dCh2b2lkKiBhcmcpCit7CisJZWhjaV9z b2Z0Y190ICpzYyA9IGFyZzsKKworCURQUklOVEZOKDMsICJlaGNpX2ludHJxX3RpbWVvdXRcbiIp OworCWVoY2lfaW50ZXJydXB0X3BvbGwoc2MpOworfQorCiAvKi0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSoKICAq CWVoY2lfaW50ZXJydXB0IC0gRUhDSSBpbnRlcnJ1cHQgaGFuZGxlcgogICoKQEAgLTE1MzksNiAr MTU2MiwxMSBAQAogCS8qIHBvbGwgYWxsIHRoZSBVU0IgdHJhbnNmZXJzICovCiAJZWhjaV9pbnRl cnJ1cHRfcG9sbChzYyk7CiAKKwlpZiAoKHNjLT5zY19mbGFncyAmIEVIQ0lfU0NGTEdfTE9TVElO VFJCVUcpICYmCisJICAgICFUQUlMUV9FTVBUWSgmc2MtPnNjX2J1cy5pbnRyX3EuaGVhZCkpCisJ CXVzYl9jYWxsb3V0X3Jlc2V0KCZzYy0+c2NfdG1vX2ludHJxLCBoeiAvIDUsICh2b2lkICopJmVo Y2lfaW50cnFfdGltZW91dCwKKwkJCXNjKTsKKwogZG9uZToKIAlVU0JfQlVTX1VOTE9DSygmc2Mt PnNjX2J1cyk7CiB9CkluZGV4OiBjb250cm9sbGVyL2VoY2kuaAo9PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBjb250 cm9sbGVyL2VoY2kuaAkocmV2aXNpb24gMTk4OTY2KQorKysgY29udHJvbGxlci9laGNpLmgJKHdv cmtpbmcgY29weSkKQEAgLTMyMSw2ICszMjEsNyBAQAogCXN0cnVjdCBlaGNpX2h3X3NvZnRjIHNj X2h3OwogCXN0cnVjdCB1c2JfYnVzIHNjX2J1czsJCS8qIGJhc2UgZGV2aWNlICovCiAJc3RydWN0 IHVzYl9jYWxsb3V0IHNjX3Rtb19wY2Q7CisJc3RydWN0IHVzYl9jYWxsb3V0IHNjX3Rtb19pbnRy cTsKIAl1bmlvbiBlaGNpX2h1Yl9kZXNjIHNjX2h1Yl9kZXNjOwogCiAJc3RydWN0IHVzYl9kZXZp Y2UgKnNjX2RldmljZXNbRUhDSV9NQVhfREVWSUNFU107CkBAIC0zNDgsNiArMzQ5LDcgQEAKICNk ZWZpbmUJRUhDSV9TQ0ZMR19CSUdFREVTQwkweDAwMDgJLyogYmlnLWVuZGlhbiBieXRlIG9yZGVy IGRlc2NyaXB0b3JzICovCiAjZGVmaW5lCUVIQ0lfU0NGTEdfQklHRU1NSU8JMHgwMDEwCS8qIGJp Zy1lbmRpYW4gYnl0ZSBvcmRlciBNTUlPICovCiAjZGVmaW5lCUVIQ0lfU0NGTEdfVFQJCTB4MDAy MAkvKiB0cmFuc2FjdGlvbiB0cmFuc2xhdG9yIHByZXNlbnQgKi8KKyNkZWZpbmUJRUhDSV9TQ0ZM R19MT1NUSU5UUkJVRwkweDAwNDAgIC8qIHdvcmthcm91bmQgZm9yIFZJQSAvIEFUSSBjaGlwc2V0 cyAqLwogCiAJdWludDhfdAlzY19vZmZzOwkJLyogb2Zmc2V0IHRvIG9wZXJhdGlvbmFsIHJlZ2lz dGVycyAqLwogCXVpbnQ4X3QJc2NfZG9vcmJlbGxfZGlzYWJsZTsJLyogc2V0IG9uIGRvb3JiZWxs IGZhaWx1cmUgKi8K --=_958d35a45c231854b4ffb480c87eec69-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 08:40:27 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 944AF1065702 for ; Fri, 6 Nov 2009 08:40:27 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net [41.161.16.135]) by mx1.freebsd.org (Postfix) with ESMTP id C4E078FC1B for ; Fri, 6 Nov 2009 08:40:26 +0000 (UTC) Received: from [41.154.0.9] (helo=clue.co.za) by inbound01.jnb1.gp-online.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1N6KMp-0000VD-8B; Fri, 06 Nov 2009 10:40:23 +0200 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N6KMm-000AGE-QC; Fri, 06 Nov 2009 10:40:20 +0200 To: Weldon S Godfrey 3 From: Ian FREISLICH In-Reply-To: References: <1257185816.44755.29.camel@buffy.york.ac.uk> <1257261214.98619.92.camel@buffy.york.ac.uk> X-Attribution: BOFH Date: Fri, 06 Nov 2009 10:40:20 +0200 Message-Id: Cc: freebsd-current@FreeBSD.org, Gavin Atkinson Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 08:40:27 -0000 Weldon S Godfrey 3 wrote: > >> OK, at least we've figured out what is going wrong then. As a > >> workaround to get the machine to stay up longer, you should be able to > >> set kern.ipc.nmbclusters=256000 in /boot/loader.conf -but hopefully we > >> can resolve this soon. > >> > > I upped it to 256K. What I am trying to wrap my head around is how it was > working somewhat for so long at 24K, but it got to near 65K before I > rebooted it with the higher setting. Or did I reboot too early? Is > there any cleanup that isn't triggered intil it reaches max nmbclusters? > I am trying to see if anything on our network has changed to cause this to > become cronic. We have a ngaios server which handles up to 5000 concurrent nsca daemons and connections which manifested a similar problem on a Dell R905 (4x4core AMD, 16GB RAM, bce). Setting the following in /boot/loader.conf sorted out the problem for us: kern.ipc.nmbclusters="131072" kern.maxusers="1024" mbuf usage is pretty static at: $ netstat -m 40165/16220/56385 mbufs in use (current/cache/total) 40154/10500/50654/131072 mbuf clusters in use (current/cache/total/max) 40154/3359 mbuf+clusters out of packet secondary zone in use (current/cache) 0/1493/1493/65536 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/32768 9k jumbo clusters in use (current/cache/total/max) 0/0/0/16384 16k jumbo clusters in use (current/cache/total/max) 90349K/31027K/121376K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 246 requests for I/O initiated by sendfile 0 calls to protocol drain routines Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 08:49:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D75F1065692; Fri, 6 Nov 2009 08:49:43 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe16.swipnet.se [212.247.155.225]) by mx1.freebsd.org (Postfix) with ESMTP id 937138FC08; Fri, 6 Nov 2009 08:49:42 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=ZtuwNLKmslsCXcbmmnkA:9 a=xnIUZ_Mzj00j0BEqK5xlQ2SmOhgA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe16.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 577851680; Fri, 06 Nov 2009 09:49:41 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 6 Nov 2009 09:48:45 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <202969100caf7f0bb8098572b0dad622@mail> <20d8e6193795d83f9ffa30ab94bf86eb@mail> In-Reply-To: <20d8e6193795d83f9ffa30ab94bf86eb@mail> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911060948.45790.hselasky@c2i.net> Cc: Andrew Thompson , Alexander Nedotsukov , Alexander Nedotsukov Subject: Re: umass problem. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 08:49:43 -0000 On Friday 06 November 2009 05:52:48 Alexander Nedotsukov wrote: > Well I do. This is a regression in EHCI driver introduced along the new > usb stack. Please review patch attached. > > Thanks, > Alexander. Hi, Your patch looks good. I will go through it later today. One little issue. There is no callout_drain() call for the new callout. Look for existing callout_drain() calls for the pcd timer. --HPS From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 09:14:36 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F31B21065676; Fri, 6 Nov 2009 09:14:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id CB55C8FC16; Fri, 6 Nov 2009 09:14:35 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA68kCIi073954; Fri, 6 Nov 2009 03:46:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA68kCbH073944; Fri, 6 Nov 2009 08:46:12 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 08:46:12 GMT Message-Id: <200911060846.nA68kCbH073944@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 09:14:36 -0000 TB --- 2009-11-06 06:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 06:50:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-11-06 06:50:00 - cleaning the object tree TB --- 2009-11-06 06:50:27 - cvsupping the source tree TB --- 2009-11-06 06:50:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-11-06 06:56:28 - building world TB --- 2009-11-06 06:56:28 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 06:56:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 06:56:28 - TARGET=i386 TB --- 2009-11-06 06:56:28 - TARGET_ARCH=i386 TB --- 2009-11-06 06:56:28 - TZ=UTC TB --- 2009-11-06 06:56:28 - __MAKE_CONF=/dev/null TB --- 2009-11-06 06:56:28 - cd /src TB --- 2009-11-06 06:56:28 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 06:56:29 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 07:55:06 UTC 2009 TB --- 2009-11-06 07:55:06 - generating LINT kernel config TB --- 2009-11-06 07:55:06 - cd /src/sys/i386/conf TB --- 2009-11-06 07:55:06 - /usr/bin/make -B LINT TB --- 2009-11-06 07:55:06 - building LINT kernel TB --- 2009-11-06 07:55:06 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 07:55:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 07:55:06 - TARGET=i386 TB --- 2009-11-06 07:55:06 - TARGET_ARCH=i386 TB --- 2009-11-06 07:55:06 - TZ=UTC TB --- 2009-11-06 07:55:06 - __MAKE_CONF=/dev/null TB --- 2009-11-06 07:55:06 - cd /src TB --- 2009-11-06 07:55:06 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 07:55:06 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 6 08:19:50 UTC 2009 TB --- 2009-11-06 08:19:50 - building GENERIC kernel TB --- 2009-11-06 08:19:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 08:19:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 08:19:50 - TARGET=i386 TB --- 2009-11-06 08:19:50 - TARGET_ARCH=i386 TB --- 2009-11-06 08:19:50 - TZ=UTC TB --- 2009-11-06 08:19:50 - __MAKE_CONF=/dev/null TB --- 2009-11-06 08:19:50 - cd /src TB --- 2009-11-06 08:19:50 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 6 08:19:50 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Nov 6 08:38:43 UTC 2009 TB --- 2009-11-06 08:38:43 - building PAE kernel TB --- 2009-11-06 08:38:43 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 08:38:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 08:38:43 - TARGET=i386 TB --- 2009-11-06 08:38:43 - TARGET_ARCH=i386 TB --- 2009-11-06 08:38:43 - TZ=UTC TB --- 2009-11-06 08:38:43 - __MAKE_CONF=/dev/null TB --- 2009-11-06 08:38:43 - cd /src TB --- 2009-11-06 08:38:43 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Nov 6 08:38:43 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for PAE completed on Fri Nov 6 08:43:39 UTC 2009 TB --- 2009-11-06 08:43:39 - building XEN kernel TB --- 2009-11-06 08:43:39 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 08:43:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 08:43:39 - TARGET=i386 TB --- 2009-11-06 08:43:39 - TARGET_ARCH=i386 TB --- 2009-11-06 08:43:39 - TZ=UTC TB --- 2009-11-06 08:43:39 - __MAKE_CONF=/dev/null TB --- 2009-11-06 08:43:39 - cd /src TB --- 2009-11-06 08:43:39 - /usr/bin/make -B buildkernel KERNCONF=XEN >>> Kernel build for XEN started on Fri Nov 6 08:43:39 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] linking kernel.debug vga_pci.o(.text+0xbf3): In function `vga_pci_resume': /src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0xc3e):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0xd15): In function `vga_pci_suspend': /src/sys/dev/pci/vga_pci.c:140: undefined reference to `vidsw' vga_pci.o(.text+0xd81):/src/sys/dev/pci/vga_pci.c:148: undefined reference to `vidsw' vga_pci.o(.text+0xe1c):/src/sys/dev/pci/vga_pci.c:163: undefined reference to `vidsw' *** Error code 1 Stop in /obj/i386/src/sys/XEN. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 08:46:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 08:46:10 - ERROR: failed to build XEN kernel TB --- 2009-11-06 08:46:10 - 5083.66 user 940.98 system 6970.05 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 09:19:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05508106566C for ; Fri, 6 Nov 2009 09:19:46 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout7.freenet.de (mout7.freenet.de [IPv6:2001:748:100:40::2:9]) by mx1.freebsd.org (Postfix) with ESMTP id 932A08FC0A for ; Fri, 6 Nov 2009 09:19:45 +0000 (UTC) Received: from [195.4.92.27] (helo=17.mx.freenet.de) by mout7.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #92) id 1N6Kyu-0000f5-8U; Fri, 06 Nov 2009 10:19:44 +0100 Received: from tc89e.t.pppool.de ([89.55.200.158]:12522 helo=ernst.jennejohn.org) by 17.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1N6Kyu-0004gR-0n; Fri, 06 Nov 2009 10:19:44 +0100 Date: Fri, 6 Nov 2009 10:19:43 +0100 From: Gary Jennejohn To: S.N.Grigoriev Message-ID: <20091106101943.5a763f43@ernst.jennejohn.org> In-Reply-To: <31221257446063@webmail71.yandex.ru> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 09:19:46 -0000 On Thu, 05 Nov 2009 21:34:23 +0300 S.N.Grigoriev wrote: > > > 05.11.09, 18:49, "Gary Jennejohn" : > > > On Thu, 05 Nov 2009 19:40:03 +0300 > > S.N.Grigoriev wrote: > > > > > > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > > > wrote: > > > > > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > > > Hi list, > > > > > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > > > work for me. My machine reboots every time I try to build world. > > > > > I don't think I have a hardware problem: under 7-stable I can build > > > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > > > to '0' and no valid dump device configured? > > > > > > Hi Alexandre, > > > > > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > > > output. Where cat I find it? All my sysctl variables are set by > > > default. > > Do you have "options DDB" in your kernel config file? > > --- > > Gary Jennejohn > > Hi Gary, > > my current kernel is GENERIC, so I don't have "options DDB". > Well, you need that option to see the DDB (debug) sysctl's. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 09:57:21 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14A54106566C; Fri, 6 Nov 2009 09:57:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E22D68FC12; Fri, 6 Nov 2009 09:57:20 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA69Sj5n092244; Fri, 6 Nov 2009 04:28:45 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA69SiY3092243; Fri, 6 Nov 2009 09:28:44 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 09:28:44 GMT Message-Id: <200911060928.nA69SiY3092243@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 09:57:21 -0000 TB --- 2009-11-06 07:38:14 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 07:38:14 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-11-06 07:38:14 - cleaning the object tree TB --- 2009-11-06 07:38:30 - cvsupping the source tree TB --- 2009-11-06 07:38:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-11-06 07:39:17 - building world TB --- 2009-11-06 07:39:17 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 07:39:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 07:39:17 - TARGET=ia64 TB --- 2009-11-06 07:39:17 - TARGET_ARCH=ia64 TB --- 2009-11-06 07:39:17 - TZ=UTC TB --- 2009-11-06 07:39:17 - __MAKE_CONF=/dev/null TB --- 2009-11-06 07:39:17 - cd /src TB --- 2009-11-06 07:39:17 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 07:39:18 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 08:55:46 UTC 2009 TB --- 2009-11-06 08:55:46 - generating LINT kernel config TB --- 2009-11-06 08:55:46 - cd /src/sys/ia64/conf TB --- 2009-11-06 08:55:46 - /usr/bin/make -B LINT TB --- 2009-11-06 08:55:46 - building LINT kernel TB --- 2009-11-06 08:55:46 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 08:55:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 08:55:46 - TARGET=ia64 TB --- 2009-11-06 08:55:46 - TARGET_ARCH=ia64 TB --- 2009-11-06 08:55:46 - TZ=UTC TB --- 2009-11-06 08:55:46 - __MAKE_CONF=/dev/null TB --- 2009-11-06 08:55:46 - cd /src TB --- 2009-11-06 08:55:46 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 08:55:46 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 6 09:22:11 UTC 2009 TB --- 2009-11-06 09:22:11 - building GENERIC kernel TB --- 2009-11-06 09:22:11 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 09:22:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 09:22:11 - TARGET=ia64 TB --- 2009-11-06 09:22:11 - TARGET_ARCH=ia64 TB --- 2009-11-06 09:22:11 - TZ=UTC TB --- 2009-11-06 09:22:11 - __MAKE_CONF=/dev/null TB --- 2009-11-06 09:22:11 - cd /src TB --- 2009-11-06 09:22:11 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 6 09:22:12 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] vga_pci.o(.text+0x1ad2): In function `vga_pci_resume': /src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0x1ae0):/src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0x1bc2):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0x1bd0):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0x1de2): In function `vga_pci_suspend': /src/sys/dev/pci/vga_pci.c:140: undefined reference to `vidsw' vga_pci.o(.text+0x1df0):/src/sys/dev/pci/vga_pci.c:140: more undefined references to `vidsw' follow *** Error code 1 Stop in /obj/ia64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 09:28:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 09:28:44 - ERROR: failed to build GENERIC kernel TB --- 2009-11-06 09:28:44 - 5290.95 user 780.90 system 6630.45 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 10:49:40 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BC64106568B; Fri, 6 Nov 2009 10:49:40 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3C68FC1F; Fri, 6 Nov 2009 10:49:40 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA6AKmcT074519; Fri, 6 Nov 2009 05:20:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA6AKmJQ074518; Fri, 6 Nov 2009 10:20:48 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 10:20:48 GMT Message-Id: <200911061020.nA6AKmJQ074518@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 10:49:40 -0000 TB --- 2009-11-06 09:15:28 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 09:15:28 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-11-06 09:15:28 - cleaning the object tree TB --- 2009-11-06 09:15:40 - cvsupping the source tree TB --- 2009-11-06 09:15:40 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-11-06 09:16:22 - building world TB --- 2009-11-06 09:16:22 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 09:16:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 09:16:22 - TARGET=sun4v TB --- 2009-11-06 09:16:22 - TARGET_ARCH=sparc64 TB --- 2009-11-06 09:16:22 - TZ=UTC TB --- 2009-11-06 09:16:22 - __MAKE_CONF=/dev/null TB --- 2009-11-06 09:16:22 - cd /src TB --- 2009-11-06 09:16:22 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 09:16:22 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 10:09:50 UTC 2009 TB --- 2009-11-06 10:09:50 - generating LINT kernel config TB --- 2009-11-06 10:09:50 - cd /src/sys/sun4v/conf TB --- 2009-11-06 10:09:50 - /usr/bin/make -B LINT TB --- 2009-11-06 10:09:50 - building LINT kernel TB --- 2009-11-06 10:09:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 10:09:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 10:09:50 - TARGET=sun4v TB --- 2009-11-06 10:09:50 - TARGET_ARCH=sparc64 TB --- 2009-11-06 10:09:50 - TZ=UTC TB --- 2009-11-06 10:09:50 - __MAKE_CONF=/dev/null TB --- 2009-11-06 10:09:50 - cd /src TB --- 2009-11-06 10:09:50 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 10:09:50 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] : undefined reference to `vidsw' vga_pci.o(.text+0xe7c): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xe8c): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xedc): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xee4): more undefined references to `vidsw' follow *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 10:20:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 10:20:48 - ERROR: failed to build lint kernel TB --- 2009-11-06 10:20:48 - 3100.82 user 604.19 system 3920.05 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 12:55:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A09D81065672 for ; Fri, 6 Nov 2009 12:55:54 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id 56EA08FC18 for ; Fri, 6 Nov 2009 12:55:54 +0000 (UTC) Received: by yxe1 with SMTP id 1so910830yxe.3 for ; Fri, 06 Nov 2009 04:55:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=TbRFvYsEMZF4fYLIUGCxvDz8QZxkzgiAAPJenyqStM0=; b=VqGVqdcaG+WG9YL2tn4MuyXL2dYwzg08gpVD6VnB0vUD77yLmdsAkjSQB/DU9DdddK a6niqypxxdpDnTNXvs6R/M3st6KdeqMFop7GCbLDwwpXPZof6YaVWAP1EsDqZMpJ8qj0 KX09ZrDW3J6YkcRMBQEHDHMeHvNew31/CS3bQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=TlOcvEjjZScv67/wrt2G7sQx+5ZHRbGCEF6LzJ3GN+9TWgdTcsSx0pWxqUkm1AdAxg rVDZ4xjkx7RXHOV/azDieXJt88pCG/4cM5OdgenwLtpJrgTKnuhi1JlqTaAMPp9lhsjx li1roR0ipYpXil2LcjVG/36EP8m/lMI7A58gE= Received: by 10.150.46.38 with SMTP id t38mr7720636ybt.121.1257512153559; Fri, 06 Nov 2009 04:55:53 -0800 (PST) Received: from ?10.0.3.231? (pool-173-70-28-149.nwrknj.fios.verizon.net [173.70.28.149]) by mx.google.com with ESMTPS id 20sm14212ywh.47.2009.11.06.04.55.51 (version=SSLv3 cipher=RC4-MD5); Fri, 06 Nov 2009 04:55:52 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: "S.N.Grigoriev" In-Reply-To: <1031257439203@webmail57.yandex.ru> References: <1031257439203@webmail57.yandex.ru> Content-Type: text/plain; charset="UTF-8" Date: Fri, 06 Nov 2009 07:55:51 -0500 Message-Id: <1257512151.1434.13.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 12:55:54 -0000 On Thu, 2009-11-05 at 19:40 +0300, S.N.Grigoriev wrote: > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > wrote: > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > Hi list, > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > work for me. My machine reboots every time I try to build world. > > > I don't think I have a hardware problem: under 7-stable I can build > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > to '0' and no valid dump device configured? > > Hi Alexandre, > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > output. Where cat I find it? All my sysctl variables are set by > default. If your system does not have "option DDB", it would not have sysctl above, which might be just as well. Does savecore -v output makes sense? Where I am heading with all of that is the possibility that your system panic(9)'ed and saved no core, hence, looking like it just rebooted. -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 13:10:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4475106566B for ; Fri, 6 Nov 2009 13:10:10 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 647A48FC20 for ; Fri, 6 Nov 2009 13:10:09 +0000 (UTC) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Nov 2009 08:10:09 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.7-GA) with ESMTP id LFR89501; Fri, 6 Nov 2009 08:09:18 -0500 (EST) Received: from 209-6-22-227.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.227]) by smtp01.lnh.mail.rcn.net with ESMTP; 06 Nov 2009 08:09:18 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19188.8189.660106.589512@jerusalem.litteratus.org> Date: Fri, 6 Nov 2009 08:09:17 -0500 To: Artis Caune In-Reply-To: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> References: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Cc: freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 13:10:10 -0000 Artis Caune writes: > > I'm interested inb putting together a file server with lots of disk. > > > > What's the state of ZFS? Is it ready for production use? > > yes, please, see > http://svn.freebsd.org/viewvc/base?view=revision&revision=197218 I'd say it's a matter of individual risk tolerance and how well one knows ZFS. Reading questions@, current@, and hackers@, there are many people happily running ZFS. But it's also generating _at least_ 10x the queries and problems of ufs, ext?fs, ntfs/msdosfs, and nfs put together. Much of that is "Can I X?" or "How do I X?" ... and the rest isn't. My personal take: ZFS has been out there for less than five years (according to Wikipedia) and is still in the steep part of the development curve. I'll wait until it has a few more gigadays under its belt before betting the ranch. Robert Huff From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 14:43:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6CD4106566B; Fri, 6 Nov 2009 14:43:07 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1115C8FC14; Fri, 6 Nov 2009 14:43:06 +0000 (UTC) Received: by fxm27 with SMTP id 27so250203fxm.3 for ; Fri, 06 Nov 2009 06:43:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=5SvhB21QZLPmS/sXStyhEVIOv6R/UckiBQbr0rqBE38=; b=sENFJQgbwoDL2cQcUzoUX1L5T9kL3Z526bGBZMFPKyNGirRt7vikC10uOU5M+MTg1B KAJiV8718aPa3sLZ3uAfpWsqlD6IQZBtW7QZ1BqYG9z10mOxBFMkzKVcwBBAs72eNjMh kDLjfFx00upvvbOh69djWdGB3eE1qWssxxlwE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=M7dpVMjcaUeu+dBY+vBmra59EHuLqAeohnWF8Kk58WOMtTf8rZ0/fJmndmhh11qs2v Xa0YqJx0KTxjmSMrzzYKL+Bjs92QU8Wmoqw5MBHEJgQwcltBDxYAt4noky/CyxqfQT5V c8GXiOjMdtEdApp2Mr+EEjso686+TzbAk/dGM= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.7.21 with SMTP id b21mr601668fab.104.1257518585910; Fri, 06 Nov 2009 06:43:05 -0800 (PST) Date: Fri, 6 Nov 2009 15:43:05 +0100 X-Google-Sender-Auth: 75aa04608c45c92f Message-ID: <3bbf2fe10911060643g60079e31y7679b32dac670fd8@mail.gmail.com> From: Attilio Rao To: freebsd-current@freebsd.org, Ed Maste , Scott Long , gibbs@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: [PATCH] Adding sysctl for errors statistics to ahd(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 14:43:07 -0000 This patch introduces some mechanisms for collecting informations on errors frequency and debugging (and relative sysctls for printing them out) for the ahd(4) driver: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/ahd/ahd-current2.diff The usage of array for sysctls is a bit too paranoid but it allows for further extendibility of the code and doesn't loose of cleaness. This code has been contributed back by Sandvine Incorporated with some cleanups. Please review. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 15:13:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3B07106566C; Fri, 6 Nov 2009 15:13:00 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 45FD98FC17; Fri, 6 Nov 2009 15:12:59 +0000 (UTC) Received: by fxm27 with SMTP id 27so261058fxm.3 for ; Fri, 06 Nov 2009 07:12:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=SaMLhYpU7urmH96oMLzSjC4yJRhdPb+4E/eqtrntWDQ=; b=Vr4ZHYMKVrKw0GhFw/4BIKFU5Vj88CzAa866SZ88Gt6WeItqwIDv6XxkBBiaCWLkMP HVFauLCyxofspjoU1LlwTLUVPR9Wz91aXF+8Q3O/MJ4M69ql+PaBSlMgbKBjcthIiozf EVNIok53l/z5HGIovhVawWIy8zITDtZ7y5ISE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=jn+oVXSan2/bW5eb8NfbDWzVcFT9VNL8ozG4txYN5P5/XSMbdoO3KRTaTRJ2b47LXi jebmrM5zjncfgcbft3j4EngnoXgmClqzUTO9jcyTQ6aTV1C+agpKu0dtFTI59YThDSTC A0Ehos1HH2t83GYZQB2vAJFgrIN06odzXdv8A= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.7.21 with SMTP id b21mr606292fab.104.1257520379195; Fri, 06 Nov 2009 07:12:59 -0800 (PST) Date: Fri, 6 Nov 2009 16:12:59 +0100 X-Google-Sender-Auth: 534ecf7aa2ec89d8 Message-ID: <3bbf2fe10911060712y46684f76sefe195a62083c15@mail.gmail.com> From: Attilio Rao To: freebsd-current@freebsd.org, Ed Maste , John Baldwin Content-Type: text/plain; charset=UTF-8 Cc: Subject: [PATCH] Boot-time entering prompt by typing "123" sequence rather than any button X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 15:13:00 -0000 This patch adds the possibility to enter the prompt at boot time by typing the sequence of buttons "123" rather than a single button: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/boot123/boot123.diff This is useful in the cases where a serial console is likely going to be used which can carry on spourious character, leding to the prompt erroneously. This option is wrappered into the BOOT_PROMPT_123 option, in order to maintain the current POLA. This patch has been contributed back by Sandvine Incorporated. Please review. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 15:51:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4682E1065670; Fri, 6 Nov 2009 15:51:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 176858FC1A; Fri, 6 Nov 2009 15:51:08 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BDBB146B0D; Fri, 6 Nov 2009 10:51:07 -0500 (EST) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 051918A01F; Fri, 6 Nov 2009 10:51:04 -0500 (EST) From: John Baldwin To: Attilio Rao Date: Fri, 6 Nov 2009 10:50:50 -0500 User-Agent: KMail/1.9.7 References: <3bbf2fe10911060712y46684f76sefe195a62083c15@mail.gmail.com> In-Reply-To: <3bbf2fe10911060712y46684f76sefe195a62083c15@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911061050.50873.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 06 Nov 2009 10:51:04 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00,RDNS_NONE, SUBJECT_FUZZY_TION autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-current@freebsd.org, Ed Maste Subject: Re: [PATCH] Boot-time entering prompt by typing "123" sequence rather than any button X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 15:51:08 -0000 On Friday 06 November 2009 10:12:59 am Attilio Rao wrote: > This patch adds the possibility to enter the prompt at boot time by > typing the sequence of buttons "123" rather than a single button: > http://www.freebsd.org/~attilio/Sandvine/STABLE_8/boot123/boot123.diff > > This is useful in the cases where a serial console is likely going to > be used which can carry on spourious character, leding to the prompt > erroneously. > This option is wrappered into the BOOT_PROMPT_123 option, in order to > maintain the current POLA. > This patch has been contributed back by Sandvine Incorporated. > Please review. This seems a bit hackish, but the patch is fine on technical grounds. On machines where I have a serial console I tend to put "-Dh" in /boot.config (so I can choose an alternate loader if need be) and in that case boot2 would eat the extra input and pause during the boot process (I've had this happen occasionally). This patch wouldn't help with that case. Another suggestion made on IRC was to simply drain input at the start of boot2 or loader to avoid accepting early spurious input. This won't help if you are dealing with noisy serial lines that are just spewing random garbage during the boot process however. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 16:26:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A719E106568F for ; Fri, 6 Nov 2009 16:26:18 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward8.yandex.ru (forward8.yandex.ru [77.88.61.38]) by mx1.freebsd.org (Postfix) with ESMTP id 609F48FC1F for ; Fri, 6 Nov 2009 16:26:18 +0000 (UTC) Received: from webmail58.yandex.ru (webmail58.yandex.ru [77.88.61.3]) by forward8.yandex.ru (Yandex) with ESMTP id 4B78C1430D3A; Fri, 6 Nov 2009 19:24:25 +0300 (MSK) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail58.yandex.ru (Yandex) with ESMTP id 8204C6DC2F0; Fri, 6 Nov 2009 19:24:24 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail58 X-Yandex-TimeMark: 1257524664 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Fri, 06 Nov 2009 19:24:23 +0300 From: S.N.Grigoriev To: "Alexandre \"Sunny\" Kovalenko" MIME-Version: 1.0 Message-Id: <5761257524664@webmail58.yandex.ru> Date: Fri, 06 Nov 2009 19:24:24 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 16:26:18 -0000 06.11.09, 07:55, "Alexandre \"Sunny\" Kovalenko" : > On Thu, 2009-11-05 at 19:40 +0300, S.N.Grigoriev wrote: > > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > > wrote: > > > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > > Hi list, > > > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > > work for me. My machine reboots every time I try to build world. > > > > I don't think I have a hardware problem: under 7-stable I can build > > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > > to '0' and no valid dump device configured? > > > > Hi Alexandre, > > > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > > output. Where cat I find it? All my sysctl variables are set by > > default. > If your system does not have "option DDB", it would not have sysctl > above, which might be just as well. > Does savecore -v output makes sense? This is 'savecore -v' output on my machine: unable to open bounds file, using 0 checking for kernel dump on device /dev/ad8s1b mediasize = 4294967296 sectorsize = 512 magic mismatch on last dump header on /dev/ad8s1b savecore: no dumps found -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 16:41:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A0C1106566B; Fri, 6 Nov 2009 16:41:56 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from mail2.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by mx1.freebsd.org (Postfix) with ESMTP id 410F38FC21; Fri, 6 Nov 2009 16:41:55 +0000 (UTC) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by mail2.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Nov 2009 11:29:52 -0500 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 10332) id BE2D011652; Fri, 6 Nov 2009 11:29:51 -0500 (EST) Date: Fri, 6 Nov 2009 11:29:51 -0500 From: Ed Maste To: John Baldwin Message-ID: <20091106162951.GA77255@sandvine.com> References: <3bbf2fe10911060712y46684f76sefe195a62083c15@mail.gmail.com> <200911061050.50873.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200911061050.50873.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 06 Nov 2009 16:29:52.0233 (UTC) FILETIME=[5DD38D90:01CA5EFE] Cc: Attilio Rao , freebsd-current@freebsd.org Subject: Re: [PATCH] Boot-time entering prompt by typing "123" sequence rather than any button X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 16:41:56 -0000 On Fri, Nov 06, 2009 at 10:50:50AM -0500, John Baldwin wrote: > On Friday 06 November 2009 10:12:59 am Attilio Rao wrote: > > This patch adds the possibility to enter the prompt at boot time by > > typing the sequence of buttons "123" rather than a single button: > > http://www.freebsd.org/~attilio/Sandvine/STABLE_8/boot123/boot123.diff > > > > This is useful in the cases where a serial console is likely going to > > be used which can carry on spourious character, leding to the prompt > > erroneously. > > This option is wrappered into the BOOT_PROMPT_123 option, in order to > > maintain the current POLA. > > This patch has been contributed back by Sandvine Incorporated. > > Please review. > > This seems a bit hackish, but the patch is fine on technical grounds. On > machines where I have a serial console I tend to put "-Dh" in /boot.config > (so I can choose an alternate loader if need be) and in that case boot2 would > eat the extra input and pause during the boot process (I've had this happen > occasionally). This patch wouldn't help with that case. Another suggestion > made on IRC was to simply drain input at the start of boot2 or loader to > avoid accepting early spurious input. This won't help if you are dealing > with noisy serial lines that are just spewing random garbage during the boot > process however. In a specific case we encountered, an unterminated cable plugged into a serial port caused enough signal to be reflected to produce a lossy loopback. This is a similar case to the random garbage case you suggest. My first stage loader isn't using the serial console, it's only when loader(8) starts that it switches. -Ed From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 19:26:53 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3CD31065676; Fri, 6 Nov 2009 19:26:53 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 9CAA88FC25; Fri, 6 Nov 2009 19:26:53 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA6ItQpP040243; Fri, 6 Nov 2009 13:55:26 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA6ItQ5a040232; Fri, 6 Nov 2009 18:55:26 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 18:55:26 GMT Message-Id: <200911061855.nA6ItQ5a040232@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 19:26:53 -0000 TB --- 2009-11-06 17:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 17:00:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-11-06 17:00:00 - cleaning the object tree TB --- 2009-11-06 17:00:29 - cvsupping the source tree TB --- 2009-11-06 17:00:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-11-06 17:06:08 - building world TB --- 2009-11-06 17:06:08 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 17:06:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 17:06:08 - TARGET=i386 TB --- 2009-11-06 17:06:08 - TARGET_ARCH=i386 TB --- 2009-11-06 17:06:08 - TZ=UTC TB --- 2009-11-06 17:06:08 - __MAKE_CONF=/dev/null TB --- 2009-11-06 17:06:08 - cd /src TB --- 2009-11-06 17:06:08 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 17:06:08 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 18:04:51 UTC 2009 TB --- 2009-11-06 18:04:51 - generating LINT kernel config TB --- 2009-11-06 18:04:51 - cd /src/sys/i386/conf TB --- 2009-11-06 18:04:51 - /usr/bin/make -B LINT TB --- 2009-11-06 18:04:51 - building LINT kernel TB --- 2009-11-06 18:04:51 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 18:04:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 18:04:51 - TARGET=i386 TB --- 2009-11-06 18:04:51 - TARGET_ARCH=i386 TB --- 2009-11-06 18:04:51 - TZ=UTC TB --- 2009-11-06 18:04:51 - __MAKE_CONF=/dev/null TB --- 2009-11-06 18:04:51 - cd /src TB --- 2009-11-06 18:04:51 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 18:04:51 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 6 18:28:58 UTC 2009 TB --- 2009-11-06 18:28:58 - building GENERIC kernel TB --- 2009-11-06 18:28:58 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 18:28:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 18:28:58 - TARGET=i386 TB --- 2009-11-06 18:28:58 - TARGET_ARCH=i386 TB --- 2009-11-06 18:28:58 - TZ=UTC TB --- 2009-11-06 18:28:58 - __MAKE_CONF=/dev/null TB --- 2009-11-06 18:28:58 - cd /src TB --- 2009-11-06 18:28:58 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 6 18:28:59 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Nov 6 18:48:07 UTC 2009 TB --- 2009-11-06 18:48:07 - building PAE kernel TB --- 2009-11-06 18:48:07 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 18:48:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 18:48:07 - TARGET=i386 TB --- 2009-11-06 18:48:07 - TARGET_ARCH=i386 TB --- 2009-11-06 18:48:07 - TZ=UTC TB --- 2009-11-06 18:48:07 - __MAKE_CONF=/dev/null TB --- 2009-11-06 18:48:07 - cd /src TB --- 2009-11-06 18:48:07 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Nov 6 18:48:07 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for PAE completed on Fri Nov 6 18:52:53 UTC 2009 TB --- 2009-11-06 18:52:53 - building XEN kernel TB --- 2009-11-06 18:52:53 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 18:52:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 18:52:53 - TARGET=i386 TB --- 2009-11-06 18:52:53 - TARGET_ARCH=i386 TB --- 2009-11-06 18:52:53 - TZ=UTC TB --- 2009-11-06 18:52:53 - __MAKE_CONF=/dev/null TB --- 2009-11-06 18:52:53 - cd /src TB --- 2009-11-06 18:52:53 - /usr/bin/make -B buildkernel KERNCONF=XEN >>> Kernel build for XEN started on Fri Nov 6 18:52:53 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] linking kernel.debug vga_pci.o(.text+0xbf3): In function `vga_pci_resume': /src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0xc3e):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0xd15): In function `vga_pci_suspend': /src/sys/dev/pci/vga_pci.c:140: undefined reference to `vidsw' vga_pci.o(.text+0xd81):/src/sys/dev/pci/vga_pci.c:148: undefined reference to `vidsw' vga_pci.o(.text+0xe1c):/src/sys/dev/pci/vga_pci.c:163: undefined reference to `vidsw' *** Error code 1 Stop in /obj/i386/src/sys/XEN. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 18:55:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 18:55:26 - ERROR: failed to build XEN kernel TB --- 2009-11-06 18:55:26 - 5079.17 user 939.11 system 6926.51 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 20:08:40 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEDE0106566C; Fri, 6 Nov 2009 20:08:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A31398FC21; Fri, 6 Nov 2009 20:08:40 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 26F1D46B09; Fri, 6 Nov 2009 15:08:40 -0500 (EST) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A37898A01B; Fri, 6 Nov 2009 15:08:39 -0500 (EST) From: John Baldwin To: current@FreeBSD.org Date: Fri, 6 Nov 2009 15:08:22 -0500 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911061508.22482.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 06 Nov 2009 15:08:39 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: net@FreeBSD.org Subject: [PATCH] Remove if_watchdog use X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 20:08:40 -0000 I have a patchset that converts all the remaining users of if_watchdog to using a private callout instead. In some cases the the driver already used a private timer to drive a stats timer and I merely hooked into that timer. In other cases a new callout needed to be added to the driver. Some drivers even abused the if_watchdog interface to provide a stats timer that fired every second. :) For a few drivers I also fixed other things such as busted locking, order-of-operations issues in detach, or just completely busted drivers (fea(4) and fpa(4) which share the pdq backend). Please test. Barring any major screaming and shouting I plan to commit this in a week or so and after that to work on removing the if_watchdog/if_timer stuff from the network stack. The patch is at http://www.FreeBSD.org/~jhb/patches/cleanup.patch Driver details: - an(4) - Locking fixes to not do silly things like drop the lock only to call a function that immediately reacquires the lock. Also removes recursive locking. - Hooks into the stat timer to drive the watchdog timer. - bwi(4), cm(4), ep(4), fatm(4), malo(4), mwl(4), vx(4) - Adds a new private timer to drive the watchdog timer. - ce(4), cp(4), ctau(4), cx(4), lmc(4) - These drivers have two modes, a netgraph mode and an ifnet mode. In the netgraph mode they used a private timer to drive the watchdog. In the ifnet mode they used if_watchdog. Now they just always use the private timer. - de(4) - This driver abused the watchdog interface to manage its once-a-second stat timer. It uses a callout to manage this now instead. - ed(4) - This driver used to provide a hook to allow individual attachments to provide a 'tick' event to be called from an optional stats timer. The stats timer only ran if the tick function pointer was non-NULL and the attachment's tick routine had to call callout_reset(), etc. Now the driver always schedules a stat timer and manages the callout_reset() internally. This timer is used to drive the watchdog and will also call the attachment's 'tick' handler if one is provided. - ixgb(4) - Uses callout_init_mtx() instead of callout_init(..., CALLOUT_MPSAFE). - Remove silly callout handling in a few places (cancelling the callout only to rescheduled it again immediately afterwards). - Hooks into the stat timer to drive the watchdog timer. - lge(4), nve(4), pcn(4) - Hooks into the stat timer to drive the watchdog timer. - my(4) - This driver used the watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. - fea(4), fpa(4) - These two drivers share a common backend, pdq, which was plagued with several issues. I'm quite confident no one has used these drivers in years since the are guaranteed to panic during attach. - Add real locking. Previously these drivers only acquired their lock in their interrupt handler or in the ioctl routine (but too broadly in the latter). No locking was used for the stack calling down into the driver via if_init() or if_start(), for device shutdown or detach. Also, the interrupt handler held the driver lock while calling if_input(). All this stuff should be fixed in the locking changes. - Really fix these drivers to handle if_alloc(). The front-end attachments were using if_initname() before the ifnet was allocated. Fix this by moving some of the duplicated logic from each driver into pdq_ifattach(). While here, make pdq_ifattach() return an error so that the driver just fails to attach if if_alloc() fails rather than panic'ing. - Adds a new private timer to drive the watchdog timer. - sn(4) - Use bus_*() rather than bus_space_*(). - Adds a new private timer to drive the watchdog timer. - Fixup detach. - ste(4), ti(4) - Adds a new private timer to drive the watchdog timer. - Fixup detach. - tl(4), wb(4) - Use bus_*() rather than bus_space_*(). - Hooks into the stat timer to drive the watchdog timer. - Fixup detach. - vge(4) - Overhaul the locking to avoid recursion and add missing locking in a few places. - Don't schedule a task to call vge_start() from contexts that are safe to call vge_start() directly. Just invoke the routine directly instead (this is what all of the other NIC drivers I am familiar with do). Note that vge(4) does not use an interrupt filter handler which is the primary reason some other drivers use tasks. - Adds a new private timer to drive the watchdog timer. - Use bus_*() rather than bus_space_*(). - Fixup detach. - netfront(4) - This doesn't actually implement a watchdog, it just sets if_watchdog to a non-existent function under '#ifdef notyet'. - admsw(4) - This driver is a bit special in that it has no locking at all, not even a poor attempt. :) It also appears to be for a specific MIPS board of some sort. - It has multiple ifnet's for multiple ports, but it only used if_timer and if_watchdog from the first ifnet. For this driver I added a single private timer to replace the if_timer use on the first ifnet. I marked the callout MPSAFE, but the driver really needs to have locking added at which point it could use callout_init_mtx(). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 20:09:26 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A31610656BF; Fri, 6 Nov 2009 20:09:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 33ACA8FC22; Fri, 6 Nov 2009 20:09:26 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA6JbkAW058850; Fri, 6 Nov 2009 14:37:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA6JbkgE058846; Fri, 6 Nov 2009 19:37:46 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 19:37:46 GMT Message-Id: <200911061937.nA6JbkgE058846@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 20:09:26 -0000 TB --- 2009-11-06 17:48:19 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 17:48:19 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-11-06 17:48:19 - cleaning the object tree TB --- 2009-11-06 17:48:33 - cvsupping the source tree TB --- 2009-11-06 17:48:33 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-11-06 17:49:04 - building world TB --- 2009-11-06 17:49:04 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 17:49:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 17:49:04 - TARGET=ia64 TB --- 2009-11-06 17:49:04 - TARGET_ARCH=ia64 TB --- 2009-11-06 17:49:04 - TZ=UTC TB --- 2009-11-06 17:49:04 - __MAKE_CONF=/dev/null TB --- 2009-11-06 17:49:04 - cd /src TB --- 2009-11-06 17:49:04 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 17:49:04 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 19:04:54 UTC 2009 TB --- 2009-11-06 19:04:54 - generating LINT kernel config TB --- 2009-11-06 19:04:54 - cd /src/sys/ia64/conf TB --- 2009-11-06 19:04:54 - /usr/bin/make -B LINT TB --- 2009-11-06 19:04:54 - building LINT kernel TB --- 2009-11-06 19:04:54 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 19:04:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 19:04:54 - TARGET=ia64 TB --- 2009-11-06 19:04:54 - TARGET_ARCH=ia64 TB --- 2009-11-06 19:04:54 - TZ=UTC TB --- 2009-11-06 19:04:54 - __MAKE_CONF=/dev/null TB --- 2009-11-06 19:04:54 - cd /src TB --- 2009-11-06 19:04:54 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 19:04:54 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 6 19:31:25 UTC 2009 TB --- 2009-11-06 19:31:25 - building GENERIC kernel TB --- 2009-11-06 19:31:25 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 19:31:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 19:31:25 - TARGET=ia64 TB --- 2009-11-06 19:31:25 - TARGET_ARCH=ia64 TB --- 2009-11-06 19:31:25 - TZ=UTC TB --- 2009-11-06 19:31:25 - __MAKE_CONF=/dev/null TB --- 2009-11-06 19:31:25 - cd /src TB --- 2009-11-06 19:31:25 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 6 19:31:25 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] vga_pci.o(.text+0x1ad2): In function `vga_pci_resume': /src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0x1ae0):/src/sys/dev/pci/vga_pci.c:189: undefined reference to `vidsw' vga_pci.o(.text+0x1bc2):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0x1bd0):/src/sys/dev/pci/vga_pci.c:195: undefined reference to `vidsw' vga_pci.o(.text+0x1de2): In function `vga_pci_suspend': /src/sys/dev/pci/vga_pci.c:140: undefined reference to `vidsw' vga_pci.o(.text+0x1df0):/src/sys/dev/pci/vga_pci.c:140: more undefined references to `vidsw' follow *** Error code 1 Stop in /obj/ia64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 19:37:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 19:37:46 - ERROR: failed to build GENERIC kernel TB --- 2009-11-06 19:37:46 - 5286.66 user 776.19 system 6567.26 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 20:23:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A4C4106566B for ; Fri, 6 Nov 2009 20:23:12 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id B9E5F8FC18 for ; Fri, 6 Nov 2009 20:23:11 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAPoT9EqDaFvI/2dsb2JhbADdUoQ+BA X-IronPort-AV: E=Sophos;i="4.44,695,1249272000"; d="scan'208";a="54365427" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 06 Nov 2009 15:23:10 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id BA7DC940078; Fri, 6 Nov 2009 15:23:10 -0500 (EST) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DisPL1DhbDnA; Fri, 6 Nov 2009 15:23:09 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id A7DD5940062; Fri, 6 Nov 2009 15:23:09 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nA6KUdX28168; Fri, 6 Nov 2009 15:30:39 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 6 Nov 2009 15:30:39 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Rui Paulo In-Reply-To: <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> Message-ID: References: <4AF0B7DF.9030405@freebsd.org> <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 20:23:12 -0000 On Thu, 5 Nov 2009, Rui Paulo wrote: > > Are you running TSO? > Wow, I owe you a beer:-) That was the magic bullet... I'm a dinosaur, so when I first saw this, I thought of that wonderful time sharing front end to IBM mainframes I had the priviledge of using in the 70s. (There was also a TSO emulator in the early Unix releases, which set your terminal to the worst possible setting imaginable and introduced delays of seconds when you tried to do anything. It was pretty funny for those of us who had experienced the real thing.) Anyhow, I figured you probably didn't mean this so I grep'd around and found net.inet.tcp.tso, set it to 0 and...the problem went away. (I have gotten a RST for the new port# once since then, but it was in the middle of the 3way handshake instead of after it, so it didn't cause any grief, just another 3way handshake right away.) I have no idea if the problem is something generic w.r.t. TSO or specific to the Intel 82801BA/CAM and/or the fxp driver for it. (I checked and none of the other net cards I have lying around have TSO support, so I can't test this by replacing the net card/driver.) Does anyone know enough about TSO to know if the problem is net chip specific of generic to using it? Thanks for the help. I don't think I would have ever found that, rick From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 20:31:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D38B106568F for ; Fri, 6 Nov 2009 20:31:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f202.google.com (mail-pz0-f202.google.com [209.85.222.202]) by mx1.freebsd.org (Postfix) with ESMTP id 349478FC1E for ; Fri, 6 Nov 2009 20:31:52 +0000 (UTC) Received: by pzk40 with SMTP id 40so903142pzk.7 for ; Fri, 06 Nov 2009 12:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=cw+YdmMP+I79bF6j7qd4VGQ8Mu7Mtg/HnE7N74J6KRs=; b=h726e7ulArq2kW+H2BsrQ/xn5BgbqMbU5jrxomEJxU5OOlN74WPCGjEvhXalTjf5TW Isp0V8Wkev2BsitM0nYhXUuuRBbDaTiHCeXtxrn6MfWMb3gt4hJHoEPsS3fz/wNtxeHA 7phD2G/3N1Ho7It4tk3Pbphjj++1qAGk5nZ4o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sRyBm6eSiixKajXuIqmUxGnNG6hPN9aq3SKTEoktRdVaQBRgXDKFz2TFS+gAO6S5lN D7FaSGK2S3PW7tw53ErK643J6qJ+NFxIuMZfvbHeJbGjXeomDe9zeNIl69cPY+pGQWo1 KmjornOFV7yRNwFv4ax2tYy8yEypilIbneCqU= Received: by 10.115.151.8 with SMTP id d8mr7134307wao.180.1257539511319; Fri, 06 Nov 2009 12:31:51 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 23sm208121pxi.9.2009.11.06.12.31.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 06 Nov 2009 12:31:50 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 6 Nov 2009 12:31:16 -0800 From: Pyun YongHyeon Date: Fri, 6 Nov 2009 12:31:16 -0800 To: Rick Macklem Message-ID: <20091106203116.GZ1256@michelle.cdnetworks.com> References: <4AF0B7DF.9030405@freebsd.org> <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, Rui Paulo Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 20:31:52 -0000 On Fri, Nov 06, 2009 at 03:30:39PM -0500, Rick Macklem wrote: > > > On Thu, 5 Nov 2009, Rui Paulo wrote: > > > > >Are you running TSO? > > > Wow, I owe you a beer:-) That was the magic bullet... > > I'm a dinosaur, so when I first saw this, I thought of that wonderful > time sharing front end to IBM mainframes I had the priviledge of using > in the 70s. (There was also a TSO emulator in the early Unix releases, > which set your terminal to the worst possible setting imaginable and > introduced delays of seconds when you tried to do anything. It was > pretty funny for those of us who had experienced the real thing.) > > Anyhow, I figured you probably didn't mean this so I grep'd around > and found net.inet.tcp.tso, set it to 0 and...the problem went away. > (I have gotten a RST for the new port# once since then, but it was > in the middle of the 3way handshake instead of after it, so it didn't > cause any grief, just another 3way handshake right away.) > > I have no idea if the problem is something generic w.r.t. TSO or specific > to the Intel 82801BA/CAM and/or the fxp driver for it. (I checked and none fxp(4) has TSO support but I don't think 82801BA has TSO capability. Only i82550 and i82551 support TSO. You can check it with ifconfig if fxp(4) think the controller supports TSO. > of the other net cards I have lying around have TSO support, so I can't > test this by replacing the net card/driver.) > > Does anyone know enough about TSO to know if the problem is net chip > specific of generic to using it? > > Thanks for the help. I don't think I would have ever found that, rick > From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 21:00:21 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E672106566C; Fri, 6 Nov 2009 21:00:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id C3C628FC0A; Fri, 6 Nov 2009 21:00:20 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nA6KSPYH036298; Fri, 6 Nov 2009 15:28:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nA6KSPWw036294; Fri, 6 Nov 2009 20:28:25 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 6 Nov 2009 20:28:25 GMT Message-Id: <200911062028.nA6KSPWw036294@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 21:00:21 -0000 TB --- 2009-11-06 19:22:33 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-06 19:22:33 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-11-06 19:22:33 - cleaning the object tree TB --- 2009-11-06 19:22:44 - cvsupping the source tree TB --- 2009-11-06 19:22:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-11-06 19:23:55 - building world TB --- 2009-11-06 19:23:55 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 19:23:55 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 19:23:55 - TARGET=sun4v TB --- 2009-11-06 19:23:55 - TARGET_ARCH=sparc64 TB --- 2009-11-06 19:23:55 - TZ=UTC TB --- 2009-11-06 19:23:55 - __MAKE_CONF=/dev/null TB --- 2009-11-06 19:23:55 - cd /src TB --- 2009-11-06 19:23:55 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 6 19:23:56 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 6 20:17:25 UTC 2009 TB --- 2009-11-06 20:17:25 - generating LINT kernel config TB --- 2009-11-06 20:17:25 - cd /src/sys/sun4v/conf TB --- 2009-11-06 20:17:25 - /usr/bin/make -B LINT TB --- 2009-11-06 20:17:25 - building LINT kernel TB --- 2009-11-06 20:17:25 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-06 20:17:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-06 20:17:25 - TARGET=sun4v TB --- 2009-11-06 20:17:25 - TARGET_ARCH=sparc64 TB --- 2009-11-06 20:17:25 - TZ=UTC TB --- 2009-11-06 20:17:25 - __MAKE_CONF=/dev/null TB --- 2009-11-06 20:17:25 - cd /src TB --- 2009-11-06 20:17:25 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 6 20:17:25 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] : undefined reference to `vidsw' vga_pci.o(.text+0xe7c): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xe8c): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xedc): In function `vga_pci_resume': : undefined reference to `vidsw' vga_pci.o(.text+0xee4): more undefined references to `vidsw' follow *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-06 20:28:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-06 20:28:25 - ERROR: failed to build lint kernel TB --- 2009-11-06 20:28:25 - 3103.78 user 602.09 system 3952.77 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 21:04:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B84B106566C for ; Fri, 6 Nov 2009 21:04:33 +0000 (UTC) (envelope-from konfer@mikulas.com) Received: from parez.praha12.net (parez.6.praha12.net [IPv6:2a01:490:16:130a:219:d1ff:fee3:1b92]) by mx1.freebsd.org (Postfix) with ESMTP id AE2EB8FC17 for ; Fri, 6 Nov 2009 21:04:32 +0000 (UTC) Received: from mech.mikulas.com (mech.platan.praha12.czf [10.27.66.11]) by parez.praha12.net (Postfix) with ESMTPS id 49B26C2502 for ; Fri, 6 Nov 2009 22:04:30 +0100 (CET) Message-ID: <4AF48F5D.4020400@mikulas.com> Date: Fri, 06 Nov 2009 22:04:29 +0100 From: Jiri Mikulas User-Agent: Thunderbird 2.0.0.19 (X11/20090215) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: arcmsr 1.20.00.16-91010 update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 21:04:33 -0000 Hello Would anybody merge and MFC bugfix for ARC-1200 in driver please? ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/FreeBSD/DRIVER/SourceCode/arcmsr-freebsd-1.20.00.16-91010.zip There were bug (only for ARC-1200 model) in memory space overlaping with other drivers. I can provide closer comunication with Erich Chen from Areca, if needed. Please don't forget to update version string ARCMSR_DRIVER_VERSION in arcmsr.h (isn't included in this "FTP" version of arcmsr.h) Thanks for help Jiri From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 00:08:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E09D81065676; Sat, 7 Nov 2009 00:08:08 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swipnet.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 1D9EB8FC17; Sat, 7 Nov 2009 00:08:07 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=RERtC8nhXGhYvIZhK0yWrQ==:17 a=6I5d2MoRAAAA:8 a=ZtuwNLKmslsCXcbmmnkA:9 a=LcWZ9EvHqk0A5NtHMR4A:7 a=KrOCB_Px9AqRCX44nSl3PYZL__wA:4 Received: from [90.149.203.35] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1160174733; Sat, 07 Nov 2009 01:08:06 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 7 Nov 2009 01:09:27 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <202969100caf7f0bb8098572b0dad622@mail> <20d8e6193795d83f9ffa30ab94bf86eb@mail> In-Reply-To: <20d8e6193795d83f9ffa30ab94bf86eb@mail> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911070109.28595.hselasky@c2i.net> Cc: Andrew Thompson , Alexander Nedotsukov , Alexander Nedotsukov Subject: Re: umass problem. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 00:08:09 -0000 On Friday 06 November 2009 05:52:48 Alexander Nedotsukov wrote: > Well I do. This is a regression in EHCI driver introduced along the new > usb stack. Please review patch attached. > > Thanks, > Alexander. > Hi, Your patch has been committed to USB P4 with some modifications. Please test! http://p4web.freebsd.org/chv.cgi?CH=170302 --HPS From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 02:34:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE83B106566C for ; Sat, 7 Nov 2009 02:34:12 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail3.es.net [IPv6:2001:400:4c01::2]) by mx1.freebsd.org (Postfix) with ESMTP id AF7C68FC0C for ; Sat, 7 Nov 2009 02:34:12 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id nA72YAPL003866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 6 Nov 2009 18:34:11 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 940601CC0E; Fri, 6 Nov 2009 18:34:10 -0800 (PST) To: Paul B Mahol In-reply-to: Your message of "Thu, 05 Nov 2009 15:24:59 +0100." <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> Date: Fri, 06 Nov 2009 18:34:10 -0800 From: "Kevin Oberman" Message-Id: <20091107023410.940601CC0E@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-11-06_11:2009-10-29, 2009-11-06, 2009-11-06 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0911060303 Cc: freebsd-current@freebsd.org, "Alexandre \"Sunny\" Kovalenko" Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 02:34:13 -0000 > Date: Thu, 5 Nov 2009 15:24:59 +0100 > From: Paul B Mahol > Sender: owner-freebsd-current@freebsd.org > > On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > > It seems that 8.0 discussion is still going on on @current... if I > > should have posted this on @stable, please, feel free to chastise me as > > appropriate. > > > > After updating to r198831 my laptop no longer associates with either of > > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the > > problem. > > > > Working system: > > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 > > r198443M: Sat Oct 24 14:03:30 EDT 2009 > > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > > > Non-working system: > > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 > > r198931: Wed Nov 4 20:56:16 EST 2009 > > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > > > APs are is: > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS > > WME > > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA > > ATH > > > > Relevant piece of wpa_supplicant.conf is: > > > > ctrl_interface=/var/run/wpa_supplicant > > ctrl_interface_group=wheel > > eapol_version=2 > > > > network={ > > ssid="AP_SSID" > > scan_ssid=1 > > priority=1 > > proto=WPA > > key_mgmt=WPA-PSK > > psk="Really secure something" > > } > > > > APs are set not to broadcast SSID, but enabling broadcast does not > > change much. > > > > Running wpa_supplicant with -d shows that it could not match AP_SSID. > > > > If there is anything else I can provide, please, let me know. > > What driver are you using? > Looking into net80211 svn log for that time period I only see mesh hacks ... I am seeing exactly the same issue. Atheros 5212 with a non-broadcast SSID. Similar wpa_supplicant.conf including 'scan_ssid=1'. 'ifconfig wlan0' shows no ssid. Every time I boot my laptop at home, I need to enter 'ifconfig wlan0 ssid MySSID'. As soon as I do this, it immediately associates correctly. This was never a problem when I was running V7.0. Again, it only is an issue when I am associating with my non-broadcast SSID at home. When at work or traveling where the SSID is broadcast, wpa_supplicant works just fine. If I ever get more time, I'll try to run wpa_supplicant with gdb and see what is happenning, but I may not get a chance any time soon. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 03:19:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD411106566C; Sat, 7 Nov 2009 03:19:10 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 572368FC15; Sat, 7 Nov 2009 03:19:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAHV29EqDaFvK/2dsb2JhbADcFoQ+BA X-IronPort-AV: E=Sophos;i="4.44,698,1249272000"; d="scan'208";a="54397964" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 06 Nov 2009 22:19:09 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 64879109C270; Fri, 6 Nov 2009 22:19:09 -0500 (EST) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UVhpFt0bSaC; Fri, 6 Nov 2009 22:19:09 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id E4B7C109C25D; Fri, 6 Nov 2009 22:19:08 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nA73Qc217337; Fri, 6 Nov 2009 22:26:38 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 6 Nov 2009 22:26:38 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Rui Paulo In-Reply-To: <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> Message-ID: References: <4AF0B7DF.9030405@freebsd.org> <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 03:19:10 -0000 On Thu, 5 Nov 2009, Rui Paulo wrote: > > Are you running TSO? > I spoke too soon the last time. It appears that the setting of net.inet.tcp.tso does not have any effect and that the Intel chip on this machine doesn't do TSO. (I tried swapping it for a 3C905 and the RSTs are showing up.) I guess it was just coincidence that the RSTs seemed to stop happening for a while after I flipped the sysctl. I think the problem is related to the fact that the server end has started to close down the connection (send a FIN), but the client doesn't do anything until an RPC shows up and then tried to do a new connection right after shutting down the old one. (Solaris10 generates RSTs on the old connection and it seems that somehow triggers one being sent to the server with the new port# instead of the old port#.) I'm about to try doing a soshutdown() at the time the server sends the FIN to the client, to see what effect that has. I still can't figure out where the pesky RST gets sent or I could get a stack trace at that point and see what is doing it. Having lottsa fun with it, rick From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 03:49:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B097E106566B for ; Sat, 7 Nov 2009 03:49:36 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7456C8FC08 for ; Sat, 7 Nov 2009 03:49:36 +0000 (UTC) Received: from Macintosh-4.local ([10.0.0.198]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id nA73nYZE083704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Nov 2009 19:49:34 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4AF4EE4D.70508@freebsd.org> Date: Fri, 06 Nov 2009 19:49:33 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kevin Oberman References: <20091107023410.940601CC0E@ptavv.es.net> In-Reply-To: <20091107023410.940601CC0E@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: "Alexandre \"Sunny\" Kovalenko" , freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 03:49:36 -0000 Kevin Oberman wrote: >> Date: Thu, 5 Nov 2009 15:24:59 +0100 >> From: Paul B Mahol >> Sender: owner-freebsd-current@freebsd.org >> >> On 11/5/09, Alexandre "Sunny" Kovalenko wrote: >>> It seems that 8.0 discussion is still going on on @current... if I >>> should have posted this on @stable, please, feel free to chastise me as >>> appropriate. >>> >>> After updating to r198831 my laptop no longer associates with either of >>> two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the >>> problem. >>> >>> Working system: >>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 >>> r198443M: Sat Oct 24 14:03:30 EDT 2009 >>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >>> >>> Non-working system: >>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 >>> r198931: Wed Nov 4 20:56:16 EST 2009 >>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >>> >>> APs are is: >>> SSID/MESH ID BSSID CHAN RATE S:N INT CAPS >>> AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS >>> WME >>> AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA >>> ATH >>> >>> Relevant piece of wpa_supplicant.conf is: >>> >>> ctrl_interface=/var/run/wpa_supplicant >>> ctrl_interface_group=wheel >>> eapol_version=2 >>> >>> network={ >>> ssid="AP_SSID" >>> scan_ssid=1 >>> priority=1 >>> proto=WPA >>> key_mgmt=WPA-PSK >>> psk="Really secure something" >>> } >>> >>> APs are set not to broadcast SSID, but enabling broadcast does not >>> change much. >>> >>> Running wpa_supplicant with -d shows that it could not match AP_SSID. >>> >>> If there is anything else I can provide, please, let me know. >> What driver are you using? >> Looking into net80211 svn log for that time period I only see mesh hacks ... > > I am seeing exactly the same issue. Atheros 5212 with a non-broadcast > SSID. Similar wpa_supplicant.conf including 'scan_ssid=1'. 'ifconfig > wlan0' shows no ssid. Every time I boot my laptop at home, I need to > enter 'ifconfig wlan0 ssid MySSID'. As soon as I do this, it immediately > associates correctly. > > This was never a problem when I was running V7.0. Again, it only is an > issue when I am associating with my non-broadcast SSID at home. When at > work or traveling where the SSID is broadcast, wpa_supplicant works just > fine. > > If I ever get more time, I'll try to run wpa_supplicant with gdb and see > what is happenning, but I may not get a chance any time soon. I believe your problem is unrelated. I traced it to wpa_supplicant not doing the right thing--it doesn't pass the ssid's of ap into the code that issues scan requests so it's not possible for the 802.11 stack to send directed probe request frames (to elicit a response from the ap hiding it's ssid). You can verify this by sniffing packets during a scan. I have no idea why it works for you on 7.x as that code is woefully less capable than what's in 8.x. Fixing wpa_supplicant request architectural changes to the code. I can't recall if Jouni did this is in his devel branch. Sam From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 04:57:24 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB851065676 for ; Sat, 7 Nov 2009 04:57:24 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 006C98FC1B for ; Sat, 7 Nov 2009 04:57:23 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 2FD4B14DE38; Fri, 6 Nov 2009 20:57:24 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 1301E2D6019; Fri, 6 Nov 2009 20:57:23 -0800 (PST) Message-ID: <4AF4FE32.5030501@elischer.org> Date: Fri, 06 Nov 2009 20:57:22 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Rick Macklem References: <4AF0B7DF.9030405@freebsd.org> <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Rui Paulo Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 04:57:24 -0000 Rick Macklem wrote: > > > On Thu, 5 Nov 2009, Rui Paulo wrote: > >> >> Are you running TSO? >> > I spoke too soon the last time. It appears that the setting of > net.inet.tcp.tso does not have any effect and that the Intel chip > on this machine doesn't do TSO. (I tried swapping it for a 3C905 and > the RSTs are showing up.) > > I guess it was just coincidence that the RSTs seemed to stop happening > for a while after I flipped the sysctl. > > I think the problem is related to the fact that the server end has > started to close down the connection (send a FIN), but the client > doesn't do anything until an RPC shows up and then tried to do a > new connection right after shutting down the old one. (Solaris10 > generates RSTs on the old connection and it seems that somehow > triggers one being sent to the server with the new port# instead > of the old port#.) > > I'm about to try doing a soshutdown() at the time the server sends > the FIN to the client, to see what effect that has. > > I still can't figure out where the pesky RST gets sent or I could > get a stack trace at that point and see what is doing it. > > Having lottsa fun with it, rick not as much fun as we are watching. :-) > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 05:26:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6DF41065670; Sat, 7 Nov 2009 05:26:12 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail2.es.net [IPv6:2001:400:107:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8618FC08; Sat, 7 Nov 2009 05:26:12 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id nA75Q9jk018189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 6 Nov 2009 21:26:09 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 486B81CC0E; Fri, 6 Nov 2009 21:26:09 -0800 (PST) To: Sam Leffler In-reply-to: Your message of "Fri, 06 Nov 2009 19:49:33 PST." <4AF4EE4D.70508@freebsd.org> Date: Fri, 06 Nov 2009 21:26:09 -0800 From: "Kevin Oberman" Message-Id: <20091107052609.486B81CC0E@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-11-06_11:2009-10-29, 2009-11-06, 2009-11-06 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0911060342 Cc: "Alexandre \"Sunny\" Kovalenko" , freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 05:26:12 -0000 > Date: Fri, 06 Nov 2009 19:49:33 -0800 > From: Sam Leffler > > Kevin Oberman wrote: > >> Date: Thu, 5 Nov 2009 15:24:59 +0100 > >> From: Paul B Mahol > >> Sender: owner-freebsd-current@freebsd.org > >> > >> On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > >>> It seems that 8.0 discussion is still going on on @current... if I > >>> should have posted this on @stable, please, feel free to chastise me as > >>> appropriate. > >>> > >>> After updating to r198831 my laptop no longer associates with either of > >>> two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the > >>> problem. > >>> > >>> Working system: > >>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 > >>> r198443M: Sat Oct 24 14:03:30 EDT 2009 > >>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > >>> > >>> Non-working system: > >>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 > >>> r198931: Wed Nov 4 20:56:16 EST 2009 > >>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > >>> > >>> APs are is: > >>> SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > >>> AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS > >>> WME > >>> AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA > >>> ATH > >>> > >>> Relevant piece of wpa_supplicant.conf is: > >>> > >>> ctrl_interface=/var/run/wpa_supplicant > >>> ctrl_interface_group=wheel > >>> eapol_version=2 > >>> > >>> network={ > >>> ssid="AP_SSID" > >>> scan_ssid=1 > >>> priority=1 > >>> proto=WPA > >>> key_mgmt=WPA-PSK > >>> psk="Really secure something" > >>> } > >>> > >>> APs are set not to broadcast SSID, but enabling broadcast does not > >>> change much. > >>> > >>> Running wpa_supplicant with -d shows that it could not match AP_SSID. > >>> > >>> If there is anything else I can provide, please, let me know. > >> What driver are you using? > >> Looking into net80211 svn log for that time period I only see mesh hacks ... > > > > I am seeing exactly the same issue. Atheros 5212 with a non-broadcast > > SSID. Similar wpa_supplicant.conf including 'scan_ssid=1'. 'ifconfig > > wlan0' shows no ssid. Every time I boot my laptop at home, I need to > > enter 'ifconfig wlan0 ssid MySSID'. As soon as I do this, it immediately > > associates correctly. > > > > This was never a problem when I was running V7.0. Again, it only is an > > issue when I am associating with my non-broadcast SSID at home. When at > > work or traveling where the SSID is broadcast, wpa_supplicant works just > > fine. > > > > If I ever get more time, I'll try to run wpa_supplicant with gdb and see > > what is happenning, but I may not get a chance any time soon. > > I believe your problem is unrelated. I traced it to wpa_supplicant not > doing the right thing--it doesn't pass the ssid's of ap into the code > that issues scan requests so it's not possible for the 802.11 stack to > send directed probe request frames (to elicit a response from the ap > hiding it's ssid). You can verify this by sniffing packets during a > scan. I have no idea why it works for you on 7.x as that code is > woefully less capable than what's in 8.x. > > Fixing wpa_supplicant request architectural changes to the code. I > can't recall if Jouni did this is in his devel branch. Yes, I guess so, although the symptoms are very similar, his worked on RC1 and failed on RC2. Mine has not worked since I moved from 7-Stable to head (before 8 was branched). Guess I'll have to keep kicking it or turn on broadcast on my AP. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 09:20:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E06B01065672 for ; Sat, 7 Nov 2009 09:20:54 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward9.yandex.ru (forward9.yandex.ru [77.88.61.48]) by mx1.freebsd.org (Postfix) with ESMTP id 974FE8FC19 for ; Sat, 7 Nov 2009 09:20:54 +0000 (UTC) Received: from webmail39.yandex.ru (webmail39.yandex.ru [77.88.60.18]) by forward9.yandex.ru (Yandex) with ESMTP id EE65846822A; Sat, 7 Nov 2009 12:20:52 +0300 (MSK) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail39.yandex.ru (Yandex) with ESMTP id CFAA710481D6; Sat, 7 Nov 2009 12:20:52 +0300 (MSK) X-Yandex-Spam: 1 X-Yandex-Front: webmail39 X-Yandex-TimeMark: 1257585652 Received: from [89.223.19.70] ([89.223.19.70]) by mail.yandex.ru with HTTP; Sat, 07 Nov 2009 12:20:51 +0300 From: S.N.Grigoriev To: gary.jennejohn@freenet.de In-Reply-To: <20091106101943.5a763f43@ernst.jennejohn.org> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> <20091106101943.5a763f43@ernst.jennejohn.org> MIME-Version: 1.0 Message-Id: <41361257585651@webmail39.yandex.ru> Date: Sat, 07 Nov 2009 12:20:51 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 09:20:55 -0000 06.11.09, 10:19, "Gary Jennejohn" wrote: > On Thu, 05 Nov 2009 21:34:23 +0300 > S.N.Grigoriev wrote: > > > > > > 05.11.09, 18:49, "Gary Jennejohn" : > > > > > On Thu, 05 Nov 2009 19:40:03 +0300 > > > S.N.Grigoriev wrote: > > > > > > > > 04.11.09, 16:51, "Alexandre \"Sunny\" Kovalenko" > > > > wrote: > > > > > > > > > On Wed, 2009-11-04 at 13:44 +0300, S.N.Grigoriev wrote: > > > > > > Hi list, > > > > > > > > > > > > I can confirm I've seen the same problem. After upgrading from 7-stable > > > > > > to 8.0-RC2 my machine just reboots during 'make buildworld' without > > > > > > diagnostics. But switching vm.pmap.pg_ps_enabled on/off does not > > > > > > work for me. My machine reboots every time I try to build world. > > > > > > I don't think I have a hardware problem: under 7-stable I can build > > > > > > world/kernel for both 7-stable and 8.0-RC2 without problems. > > > > > > > > > > > Is it by any chance possible that you have 'debug.debugger_on_panic' set > > > > > to '0' and no valid dump device configured? > > > > > > > > Hi Alexandre, > > > > > > > > I've not found 'debug.debugger_on_panic' variable in 'sysctl -a' > > > > output. Where cat I find it? All my sysctl variables are set by > > > > default. > > > Do you have "options DDB" in your kernel config file? > > > --- > > > Gary Jennejohn > > > > Hi Gary, > > > > my current kernel is GENERIC, so I don't have "options DDB". > > > Well, you need that option to see the DDB (debug) sysctl's. > --- I've recompiled the kernel with 'options DDB' (using 7-stable). The sysctl variable 'debug.debugger_on_panic' is now set to '1'. But I still have silent reboots every time I try to build world/kernel. 'savecore -v' reports: 'no dumps found'. What did I do incorrectly? -- Regards, S.Grigoriev. From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 09:45:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6772A106566B for ; Sat, 7 Nov 2009 09:45:08 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3258FC0C for ; Sat, 7 Nov 2009 09:45:07 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-123.hsd1.ms.comcast.net [75.65.60.123]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id C704437B631; Sat, 7 Nov 2009 03:45:06 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 09AB561C43; Sat, 7 Nov 2009 03:45:06 -0600 (CST) Date: Sat, 7 Nov 2009 03:45:06 -0600 From: "Matthew D. Fuller" To: Robert Huff Message-ID: <20091107094506.GQ59090@over-yonder.net> References: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <19188.8189.660106.589512@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19188.8189.660106.589512@jerusalem.litteratus.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.20-fullermd.4 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.2 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org, Artis Caune Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 09:45:08 -0000 On Fri, Nov 06, 2009 at 08:09:17AM -0500 I heard the voice of Robert Huff, and lo! it spake thus: > > I'll wait until it has a few more gigadays under its belt before > betting the ranch. A gigaday is 2.74 million years 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 10:52:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D57C31065676 for ; Sat, 7 Nov 2009 10:52:58 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id 6EBFB8FC14 for ; Sat, 7 Nov 2009 10:52:58 +0000 (UTC) Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1N6iuf-0004Va-FQ; Sat, 07 Nov 2009 11:52:57 +0100 Received: from tb7ea.t.pppool.de ([89.55.183.234]:29723 helo=ernst.jennejohn.org) by 7.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1N6iuf-0005ig-4n; Sat, 07 Nov 2009 11:52:57 +0100 Date: Sat, 7 Nov 2009 11:52:56 +0100 From: Gary Jennejohn To: S.N.Grigoriev Message-ID: <20091107115256.3df62bc3@ernst.jennejohn.org> In-Reply-To: <41361257585651@webmail39.yandex.ru> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> <20091106101943.5a763f43@ernst.jennejohn.org> <41361257585651@webmail39.yandex.ru> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 10:52:58 -0000 On Sat, 07 Nov 2009 12:20:51 +0300 S.N.Grigoriev wrote: > I've recompiled the kernel with 'options DDB' (using 7-stable). > The sysctl variable 'debug.debugger_on_panic' is now set to '1'. > But I still have silent reboots every time I try to build world/kernel. > 'savecore -v' reports: 'no dumps found'. What did I do incorrectly? > It could be that you also need "options KDB" for the kernel to enter ddb on panic, but I'm not 100% sure about that. Can't hurt to try it. Do you also have dumpdev defined in /etc/rc.conf? It's set to AUTO by default, but who knows whether that really works? --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 12:58:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AC20106566C for ; Sat, 7 Nov 2009 12:58:34 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 1579D8FC08 for ; Sat, 7 Nov 2009 12:58:33 +0000 (UTC) Received: from bb.ipt.ru ([194.62.233.89]) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1N6ksC-0003mL-08; Sat, 07 Nov 2009 15:58:32 +0300 To: Kostik Belousov References: <65275688@bb.ipt.ru> <20091103154747.GC2331@deviant.kiev.zoral.com.ua> <77755531@h30.sp.ipt.ru> <20091103214032.GF2331@deviant.kiev.zoral.com.ua> <99188273@bb.ipt.ru> <20091104172931.GI2331@deviant.kiev.zoral.com.ua> From: Boris Samorodov Date: Sat, 07 Nov 2009 15:58:31 +0300 In-Reply-To: <20091104172931.GI2331@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Wed\, 4 Nov 2009 19\:29\:31 +0200") Message-ID: <20586408@bb.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: [current] acroread: SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 12:58:34 -0000 On Wed, 4 Nov 2009 19:29:31 +0200 Kostik Belousov wrote: > On Wed, Nov 04, 2009 at 05:19:10PM +0300, Boris Samorodov wrote: > > On Tue, 3 Nov 2009 23:40:32 +0200 Kostik Belousov wrote: > > > On Wed, Nov 04, 2009 at 12:37:08AM +0300, Boris Samorodov wrote: > > > > On Tue, 3 Nov 2009 17:47:47 +0200 Kostik Belousov wrote: > > > > > On Tue, Nov 03, 2009 at 05:05:11PM +0300, Boris Samorodov wrote: > > > > > > Hello List, > > > > > > > > > > > > print/acroread8 doesn't work for me at 9-CURRENT: > > > > > > ----- > > > > > > % uname -a > > > > > > FreeBSD host.ipt.ru 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon Nov 2 15:15:13 MSK 2009 root@host.ipt.ru:/usr/obj/usr/src/sys/HOST > > > > > > % sysctl compat.linux > > > > > > compat.linux.oss_version: 198144 > > > > > > compat.linux.osrelease: 2.6.16 > > > > > > compat.linux.osname: Linux > > > > > > ------ > > > > > > > > > > > > Setting security.bsd.map_at_zero to 1 doesn't change anything. There is > > > > > > nothing at console/log files. Here is the tail of linux_kdump: > > > > > > ----- > > > > > > ... > > > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > > > 78586 ld-2.9.so NAMI "/compat/linux/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > > > 78586 ld-2.9.so NAMI "/var/db/fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > > > 78586 ld-2.9.so RET linux_open JUSTRETURN > > > > > > 78586 ld-2.9.so CALL linux_open(0x16fcd80,0,0x80d93000) > > > > > > 78586 ld-2.9.so NAMI "/compat/linux/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > > > 78586 ld-2.9.so NAMI "/home/bsam/.fontconfig/bde7b0a0234dc04d93e9475cbf44698a-x86.cache-2" > > > > > > 78586 ld-2.9.so RET linux_open 4 > > > > > > 78586 ld-2.9.so CALL linux_fstat64(0x4,0xbfbfcf8c,0x2e482ff4) > > > > > > 78586 ld-2.9.so RET linux_fstat64 0 > > > > > > 78586 ld-2.9.so CALL read(0x4,0x16fe160,0x60) > > > > > > 78586 ld-2.9.so GIO fd 4 read 96 bytes > > > > > > "\^D\M-|\^B\M-|\^B\0\0\0`\0\0\0 \0\0\0P\0\0\0\0\0\0\0P\0\0\0\^[b\M-TJ/usr/local/lib/X11/fonts/encodings/large\0\0\0\0\0\0\0\0\0\0\ > > > > > > \0\0\0\0\0\0\^Q\0\0\0\0\0\0\000" > > > > > > 78586 ld-2.9.so RET read 96/0x60 > > > > > > 78586 ld-2.9.so CALL close(0x4) > > > > > > 78586 ld-2.9.so RET close 0 > > > > > > 78586 ld-2.9.so CALL linux_mmap2(0,0x25000,0x3,0x22,0xffffffff,0) > > > > > > 78586 ld-2.9.so RET linux_mmap2 833982464/0x31b59000 > > > > > > 78586 ld-2.9.so PSIG SIGSEGV caught handler=0x83814b6 mask=0x0 code=0x0 > > > > > > 78586 ld-2.9.so CALL linux_rt_sigaction(0x6,0xbfbfcbf0,0xbfbfcb64,0x8) > > > > > > 78586 ld-2.9.so RET linux_rt_sigaction 0 > > > > > > 78586 ld-2.9.so CALL linux_exit_group(0x1) > > > > > > > > > It would be interesting to see which address faulted. > > > > > If not, can you do search for a kernel revision that broke acroread ? > > > > > Good starting points are r198507 and r198554. > > > > > > > > Were those revisions MFCed to RELENG_8_0? I've got the same for 8.0: > > > > ----- > > > > % uname -a > > > > FreeBSD h30.sp.ipt.ru 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Nov 1 18:57:33 MSK 2009 root@h30.sp.ipt.ru:/usr/obj/usr/src/sys/IN > > > > DUS i386 > > > > ----- > > > No. > > > It might be easier to bisect on releng/8.0 then. > > > > OK, I've found out that acroread works at 8-RC1 as of 2009-10-04 > > (with security.bsd.map_at_zero=1): > > ----- > > h31% uname -a 16:24 pts/0 > > FreeBSD h31.sp.ipt.ru 8.0-RC1 FreeBSD 8.0-RC1 #1: Sun Oct 4 02:19:42 MSD 2009 bsam@h31.sp.ipt.ru:/usr/obj/usr/src/sys/SHURAM i386 > > h31% sysctl security.bsd.map_at_zero 16:24 pts/0 > > security.bsd.map_at_zero: 1 > > ----- > > > > Can you give me suspisiuos commits to RELENG_8 to test (I don't have > > time ATM to do bisect builds)? > I do not have good guess. I would put a finger in the direction of the > imgact_elf.c changes. But, since the issue appears at run-time, after > the binary started, I doubt it. With the help from mezz@ it was found out that it's not a kernel but a new fontconfig (from marcurcom site) is to blame. Downgrading of fontconfig from 2.7.3 to 2.6.0 (from current ports tree) made acroread to work again. Seems not to be a kernel fault. Thanks for your help. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 14:21:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B2671065670 for ; Sat, 7 Nov 2009 14:21:04 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id E7FEC8FC0A for ; Sat, 7 Nov 2009 14:21:03 +0000 (UTC) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 07 Nov 2009 09:21:03 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.10.7-GA) with ESMTP id QHK58100; Sat, 7 Nov 2009 09:20:09 -0500 (EST) Received: from 209-6-22-227.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.227]) by smtp01.lnh.mail.rcn.net with ESMTP; 07 Nov 2009 09:20:09 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19189.33305.72539.876729@jerusalem.litteratus.org> Date: Sat, 7 Nov 2009 09:20:09 -0500 To: "Matthew D. Fuller" In-Reply-To: <20091107094506.GQ59090@over-yonder.net> References: <9e20d71e0911042247n216e9b02t7b317a55a9bbe131@mail.gmail.com> <19188.8189.660106.589512@jerusalem.litteratus.org> <20091107094506.GQ59090@over-yonder.net> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr02.lnh.mail.rcn.net) Cc: freebsd-current@freebsd.org Subject: Re: What is the state of ZFS on FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 14:21:04 -0000 Matthew D. Fuller writes: > On Fri, Nov 06, 2009 at 08:09:17AM -0500 I heard the voice of > Robert Huff, and lo! it spake thus: > > > > I'll wait until it has a few more gigadays under its belt before > > betting the ranch. > > A gigaday is 2.74 million years 8-} I didn't say "on a single amchine". Robert Huff From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 14:57:57 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B3B0106566C for ; Sat, 7 Nov 2009 14:57:57 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 168258FC13 for ; Sat, 7 Nov 2009 14:57:56 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id nA7EvtGl003427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 7 Nov 2009 15:57:55 +0100 (CET) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by acme.spoerlein.net (8.14.3/8.14.3/Submit) id nA7EvtLI003426 for current@FreeBSD.org; Sat, 7 Nov 2009 15:57:55 +0100 (CET) (envelope-from uqs@spoerlein.net) Date: Sat, 7 Nov 2009 15:57:54 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: current@FreeBSD.org Message-ID: <20091107145754.GG34407@acme.spoerlein.net> Mail-Followup-To: current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Wanted: CVS repository before the SVN switch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 14:57:57 -0000 Hi, current@ is probably the wrong place to ask, but I can't think of a better mailing list. What I'm looking for (and failed to secure myself) is a copy of the CVS repository (the ,v files) with the last non-subversion commit in it. Also, which revision number was the very first subversion commit? Thanks for any pointers! Uli From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 15:25:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5515106566C for ; Sat, 7 Nov 2009 15:25:05 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id 569D78FC12 for ; Sat, 7 Nov 2009 15:25:05 +0000 (UTC) Received: from vampire.homelinux.org (dslb-088-067-224-015.pools.arcor-ip.net [88.67.224.15]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Luahc-1M7A6B2joW-010LFk; Sat, 07 Nov 2009 16:25:03 +0100 Received: (qmail 24119 invoked from network); 7 Nov 2009 15:25:02 -0000 Received: from kvm.laiers.local (HELO kvm.localnet) (192.168.4.188) by laiers.local with SMTP; 7 Nov 2009 15:25:02 -0000 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 7 Nov 2009 16:25:00 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.31-ARCH; KDE/4.3.2; x86_64; ; ) References: <20091107145754.GG34407@acme.spoerlein.net> In-Reply-To: <20091107145754.GG34407@acme.spoerlein.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200911071625.01596.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1/3ROju4MIlX5OFS2FAzIAeCXGReQKzXaCkQB4 RNOQ1HI+Oeo937r/vXIeIgRizquIBE4Zytc9rXLxy5YOyoXOCA UolwiUcAB4PAMl4cSq9xg== Cc: Subject: Re: Wanted: CVS repository before the SVN switch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 15:25:05 -0000 On Saturday 07 November 2009 15:57:54 Ulrich Sp=F6rlein wrote: > Hi, >=20 > current@ is probably the wrong place to ask, but I can't think of a > better mailing list. >=20 > What I'm looking for (and failed to secure myself) is a copy of the CVS > repository (the ,v files) with the last non-subversion commit in it. > Also, which revision number was the very first subversion commit? r179451 Date: Sat May 31 08:13:58 2008 There is a backup of the old ncvs repo on the FreeBSD infrastructure, but I= 'm=20 not sure how to best make is available. Maybe somebody else can jump in. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 17:19:57 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFCA7106568B for ; Sat, 7 Nov 2009 17:19:57 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 44CFE8FC15 for ; Sat, 7 Nov 2009 17:19:56 +0000 (UTC) Received: by ewy18 with SMTP id 18so1694838ewy.43 for ; Sat, 07 Nov 2009 09:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=n22BxNWbU2ylWS3wsVqEgOOaTjTWZ/PB+KP7CKSwAzk=; b=YmXY+p9XtEfrCBxPF+6+FY6MCrTTaSansdSCf91J8giUkfNMqPVtMzW6NvMhXLM17W V/rEjqYifaxOXCewfnQcXum/5Sgh9stm9P5WFHrhVZ5zGfZFO1x2LqakJ8acwRlwBzVU bvni7oSLLavY3wZKbF7nTYr6l/cbwiH4OvAIg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xGGUK5nPcRm7H0Oah11dwDByOSFndfXEQzFnUXbym218D68XyIE2Z2qVH+WPFfAGos DseRXKbK0k5O6y7/d4acSQcYIoSRSPXjkKiO+iW+8UMdw1u0Jkftadgl3Z50hoL3jnYE WU7I63h/ySsCf32X2aTGQ30xo0P4Gn1ZSlGRA= MIME-Version: 1.0 Received: by 10.213.23.80 with SMTP id q16mr992440ebb.3.1257614396256; Sat, 07 Nov 2009 09:19:56 -0800 (PST) In-Reply-To: References: <1257426023.1436.18.camel@RabbitsDen> <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> Date: Sat, 7 Nov 2009 18:19:56 +0100 Message-ID: <3a142e750911070919s592980e1yfa420ea1d2654d52@mail.gmail.com> From: Paul B Mahol To: "Alexandre \"Sunny\" Kovalenko" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 17:19:57 -0000 On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > On Thu, Nov 5, 2009 at 9:24 AM, Paul B Mahol wrote: > >> On 11/5/09, Alexandre "Sunny" Kovalenko wrote: >> > It seems that 8.0 discussion is still going on on @current... if I >> > should have posted this on @stable, please, feel free to chastise me as >> > appropriate. >> > >> > After updating to r198831 my laptop no longer associates with either of >> > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the >> > problem. >> > >> > Working system: >> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 >> > r198443M: Sat Oct 24 14:03:30 EDT 2009 >> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >> > >> > Non-working system: >> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 >> > r198931: Wed Nov 4 20:56:16 EST 2009 >> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >> > >> > APs are is: >> > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS >> > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS >> > WME >> > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA >> > ATH >> > >> > Relevant piece of wpa_supplicant.conf is: >> > >> > ctrl_interface=/var/run/wpa_supplicant >> > ctrl_interface_group=wheel >> > eapol_version=2 >> > >> > network={ >> > ssid="AP_SSID" >> > scan_ssid=1 >> > priority=1 >> > proto=WPA >> > key_mgmt=WPA-PSK >> > psk="Really secure something" >> > } >> > >> > APs are set not to broadcast SSID, but enabling broadcast does not >> > change much. >> > >> > Running wpa_supplicant with -d shows that it could not match AP_SSID. >> > >> > If there is anything else I can provide, please, let me know. >> >> What driver are you using? >> Looking into net80211 svn log for that time period I only see mesh hacks >> ... >> > I am using ath (I am away from my laptop ATM -- I could provide part number > later today). > > I have seen mesh changes in there and that's when I gave up and posted -- I > am not > nearly enough qualified to figure out which ones could or could not impact > normal operation. You could track which commit introduced bug and/or use wlandebug and/or athdebug to see what is going on. From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 17:45:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA941106566C for ; Sat, 7 Nov 2009 17:45:07 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id 9DC418FC18 for ; Sat, 7 Nov 2009 17:45:07 +0000 (UTC) Received: by yxe1 with SMTP id 1so1775327yxe.3 for ; Sat, 07 Nov 2009 09:45:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=7lIIRkPb4Fa3Zg/ukRn/S5Cd5h+yNSQW8TB05T/ejGE=; b=U3dHQCsaB18Ta04yzAi4d0uYvR/K3gllrPjX362hJeKIE84eU+RYdjtRGSijda42qg tz2B0QaVfjos49BVPvJh6BR6kwOcrHcUUiItG8E8E/fvxOP8lr4W3A9e+RFMJpBCsgG9 /VxGgh63gGjwcA1JSSZlMBv0kbbdDV0ZBxiG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=q89/VOO5R0eoCdRGxcnviqwn/9+UD2Lub8DlZkXmcna+12hONzkqDIEXKVxpKD8aiI P4lOchYlXc4hAmh/mtFloh0Z94cKPuQQOhQa1Mfpq13tfZA/gZkfq0R3nV/UdcaPU6xk EP1sfQ5mzEaAvtCWW5kXyEzM8GOfYLB7ctER4= Received: by 10.90.42.9 with SMTP id p9mr98191agp.4.1257615906339; Sat, 07 Nov 2009 09:45:06 -0800 (PST) Received: from ?10.0.3.231? (pool-173-70-28-149.nwrknj.fios.verizon.net [173.70.28.149]) by mx.google.com with ESMTPS id 4sm528792yxd.16.2009.11.07.09.45.04 (version=SSLv3 cipher=RC4-MD5); Sat, 07 Nov 2009 09:45:05 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: Paul B Mahol In-Reply-To: <3a142e750911070919s592980e1yfa420ea1d2654d52@mail.gmail.com> References: <1257426023.1436.18.camel@RabbitsDen> <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> <3a142e750911070919s592980e1yfa420ea1d2654d52@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 07 Nov 2009 12:45:03 -0500 Message-Id: <1257615903.1438.15.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 17:45:08 -0000 On Sat, 2009-11-07 at 18:19 +0100, Paul B Mahol wrote: > On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > > On Thu, Nov 5, 2009 at 9:24 AM, Paul B Mahol wrote: > > > >> On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > >> > It seems that 8.0 discussion is still going on on @current... if I > >> > should have posted this on @stable, please, feel free to chastise me as > >> > appropriate. > >> > > >> > After updating to r198831 my laptop no longer associates with either of > >> > two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the > >> > problem. > >> > > >> > Working system: > >> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 > >> > r198443M: Sat Oct 24 14:03:30 EDT 2009 > >> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > >> > > >> > Non-working system: > >> > FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 > >> > r198931: Wed Nov 4 20:56:16 EST 2009 > >> > root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > >> > > >> > APs are is: > >> > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > >> > AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS > >> > WME > >> > AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA > >> > ATH > >> > > >> > Relevant piece of wpa_supplicant.conf is: > >> > > >> > ctrl_interface=/var/run/wpa_supplicant > >> > ctrl_interface_group=wheel > >> > eapol_version=2 > >> > > >> > network={ > >> > ssid="AP_SSID" > >> > scan_ssid=1 > >> > priority=1 > >> > proto=WPA > >> > key_mgmt=WPA-PSK > >> > psk="Really secure something" > >> > } > >> > > >> > APs are set not to broadcast SSID, but enabling broadcast does not > >> > change much. > >> > > >> > Running wpa_supplicant with -d shows that it could not match AP_SSID. > >> > > >> > If there is anything else I can provide, please, let me know. > >> > >> What driver are you using? > >> Looking into net80211 svn log for that time period I only see mesh hacks > >> ... > >> > > I am using ath (I am away from my laptop ATM -- I could provide part number > > later today). > > > > I have seen mesh changes in there and that's when I gave up and posted -- I > > am not > > nearly enough qualified to figure out which ones could or could not impact > > normal operation. > > You could track which commit introduced bug and/or use wlandebug > and/or athdebug to see what is going on. After doing revison-by-revision upgrade from r198443 to r198931, with the help from Rui Paulo, I am at r198931 and happily associated with the AP. Looks like a case of PEBKAC... I do apologize for the noise. -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 17:50:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AB151065679 for ; Sat, 7 Nov 2009 17:50:32 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2398FC21 for ; Sat, 7 Nov 2009 17:50:32 +0000 (UTC) Received: from ice.local ([10.0.0.115]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id nA7HoT4t087489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 Nov 2009 09:50:30 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4AF5B365.8030508@errno.com> Date: Sat, 07 Nov 2009 09:50:29 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kevin Oberman References: <20091107052609.486B81CC0E@ptavv.es.net> In-Reply-To: <20091107052609.486B81CC0E@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-x.dcc-servers-Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: After sys/net80211 changes in r198931 laptop is no longer associating with AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 17:50:32 -0000 Kevin Oberman wrote: >> Date: Fri, 06 Nov 2009 19:49:33 -0800 >> From: Sam Leffler >> >> Kevin Oberman wrote: >>>> Date: Thu, 5 Nov 2009 15:24:59 +0100 >>>> From: Paul B Mahol >>>> Sender: owner-freebsd-current@freebsd.org >>>> >>>> On 11/5/09, Alexandre "Sunny" Kovalenko wrote: >>>>> It seems that 8.0 discussion is still going on on @current... if I >>>>> should have posted this on @stable, please, feel free to chastise me as >>>>> appropriate. >>>>> >>>>> After updating to r198831 my laptop no longer associates with either of >>>>> two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the >>>>> problem. >>>>> >>>>> Working system: >>>>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0 >>>>> r198443M: Sat Oct 24 14:03:30 EDT 2009 >>>>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >>>>> >>>>> Non-working system: >>>>> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 >>>>> r198931: Wed Nov 4 20:56:16 EST 2009 >>>>> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 >>>>> >>>>> APs are is: >>>>> SSID/MESH ID BSSID CHAN RATE S:N INT CAPS >>>>> AP_SSID 00:1f:33:3b:xx:xx 3 54M -68:-96 100 EP RSN WPS >>>>> WME >>>>> AP_SSID 00:1f:90:cb:xx:xx 8 54M -73:-96 100 EPS RSN WPA >>>>> ATH >>>>> >>>>> Relevant piece of wpa_supplicant.conf is: >>>>> >>>>> ctrl_interface=/var/run/wpa_supplicant >>>>> ctrl_interface_group=wheel >>>>> eapol_version=2 >>>>> >>>>> network={ >>>>> ssid="AP_SSID" >>>>> scan_ssid=1 >>>>> priority=1 >>>>> proto=WPA >>>>> key_mgmt=WPA-PSK >>>>> psk="Really secure something" >>>>> } >>>>> >>>>> APs are set not to broadcast SSID, but enabling broadcast does not >>>>> change much. >>>>> >>>>> Running wpa_supplicant with -d shows that it could not match AP_SSID. >>>>> >>>>> If there is anything else I can provide, please, let me know. >>>> What driver are you using? >>>> Looking into net80211 svn log for that time period I only see mesh hacks ... >>> I am seeing exactly the same issue. Atheros 5212 with a non-broadcast >>> SSID. Similar wpa_supplicant.conf including 'scan_ssid=1'. 'ifconfig >>> wlan0' shows no ssid. Every time I boot my laptop at home, I need to >>> enter 'ifconfig wlan0 ssid MySSID'. As soon as I do this, it immediately >>> associates correctly. >>> >>> This was never a problem when I was running V7.0. Again, it only is an >>> issue when I am associating with my non-broadcast SSID at home. When at >>> work or traveling where the SSID is broadcast, wpa_supplicant works just >>> fine. >>> >>> If I ever get more time, I'll try to run wpa_supplicant with gdb and see >>> what is happenning, but I may not get a chance any time soon. >> I believe your problem is unrelated. I traced it to wpa_supplicant not >> doing the right thing--it doesn't pass the ssid's of ap into the code >> that issues scan requests so it's not possible for the 802.11 stack to >> send directed probe request frames (to elicit a response from the ap >> hiding it's ssid). You can verify this by sniffing packets during a >> scan. I have no idea why it works for you on 7.x as that code is >> woefully less capable than what's in 8.x. >> >> Fixing wpa_supplicant request architectural changes to the code. I >> can't recall if Jouni did this is in his devel branch. > > Yes, I guess so, although the symptoms are very similar, his worked on > RC1 and failed on RC2. Mine has not worked since I moved from 7-Stable > to head (before 8 was branched). Guess I'll have to keep kicking it or > turn on broadcast on my AP. Hiding ssid has zero security benefit and just causes extra traffic on the channel as stations must use directed probe requests to find your ap. Sam From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 18:32:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D5111065693 for ; Sat, 7 Nov 2009 18:32:43 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id F101D8FC0A for ; Sat, 7 Nov 2009 18:32:42 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 9so376438qwb.7 for ; Sat, 07 Nov 2009 10:32:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=a+bXcE+zpXGVUaNfOETqG8y5vdyArspJzfgQ20dLc30=; b=xAThZbIgq5W1F1wj16seiGGvM9Uo0ygYnbHa4B0uDqE1btZVFK1NNAK22tuJI1WCab 6IwUR+8+vjaYX7EEKtyP50uGsLsT4F1ar1YcvTYt3D1KL8eHa8bngfQSydVth0scP+aM BFKcIjFi17NLkljjqKNLdnNLWJAqVxpJYvzXw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=OjTG4CHmyTA4DAROVHRR9XYOSa3fZhI77R9Ode92EX725u2+l76Votrv6tJuKhrVBN rxUdnYSlyWiyi9qxNk2oTNc/FdaMIxAGXkVAw+ngEYhQeSnfFllJhw4VMsUZp5An57dl ekQaRccdWuPIff8FXAZ9Gyzj++QimtKl+DO68= Received: by 10.224.34.3 with SMTP id j3mr3132237qad.315.1257618761755; Sat, 07 Nov 2009 10:32:41 -0800 (PST) Received: from ?10.0.3.231? (pool-173-70-28-149.nwrknj.fios.verizon.net [173.70.28.149]) by mx.google.com with ESMTPS id 20sm1031399qyk.13.2009.11.07.10.32.40 (version=SSLv3 cipher=RC4-MD5); Sat, 07 Nov 2009 10:32:41 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: "S.N.Grigoriev" In-Reply-To: <20091107115256.3df62bc3@ernst.jennejohn.org> References: <1031257439203@webmail57.yandex.ru> <20091105184925.16b55c43@ernst.jennejohn.org> <31221257446063@webmail71.yandex.ru> <20091106101943.5a763f43@ernst.jennejohn.org> <41361257585651@webmail39.yandex.ru> <20091107115256.3df62bc3@ernst.jennejohn.org> Content-Type: text/plain; charset="UTF-8" Date: Sat, 07 Nov 2009 13:32:38 -0500 Message-Id: <1257618758.1511.14.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 18:32:43 -0000 On Sat, 2009-11-07 at 11:52 +0100, Gary Jennejohn wrote: > On Sat, 07 Nov 2009 12:20:51 +0300 > S.N.Grigoriev wrote: > > > I've recompiled the kernel with 'options DDB' (using 7-stable). > > The sysctl variable 'debug.debugger_on_panic' is now set to '1'. > > But I still have silent reboots every time I try to build world/kernel. > > 'savecore -v' reports: 'no dumps found'. What did I do incorrectly? > > > > It could be that you also need "options KDB" for the kernel to enter > ddb on panic, but I'm not 100% sure about that. > > Can't hurt to try it. > > Do you also have dumpdev defined in /etc/rc.conf? It's set to AUTO > by default, Apparently not on 8.0RC... RabbitsDen# grep dumpdev defaults/rc.conf dumpdev="NO" # Device to crashdump to (device name, AUTO, or NO). savecore_flags="" # Used if dumpdev is enabled above, and present. RabbitsDen# uname -a FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0 r198931: Sat Nov 7 12:07:32 EST 2009 root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 while on 7.2 twinhead# grep dumpdev defaults/rc.conf dumpdev="AUTO" # Device to crashdump to (device name, AUTO, or NO). savecore_flags="" # Used if dumpdev is enabled above, and present. twinhead# uname -a FreeBSD twinhead.rabbitslawn.verizon.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Sat Aug 22 12:43:26 EDT 2009 root@twinhead.rabbitslawn.verizon.net:/usr/obj/usr/src/sys/TWINHEAD amd64 So one needs explicit dumpdev="AUTO" in the /etc/rc.conf. That caught me by surprise too... Sergey, I think it would be best if you follow http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN and the do an ultimate test: * quiesce your system * switch to the console * sync (few times, if you are really old school ;) * sysctl debug.kdb.panic=1 (this would *panic* the system and, given everything is set-up properly, produce the crash dump) if you do not have debug.kdb.panic sysctl, please, add option KDB to your kernel configuration. If you get crash dump from the kernel-induced panic and your system keeps rebooting without a trace, I would suspect some hardware testing might be in order. -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 19:59:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97034106566B for ; Sat, 7 Nov 2009 19:59:39 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 2908E8FC16 for ; Sat, 7 Nov 2009 19:59:38 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,700,1249250400"; d="txt'?scan'208";a="17876620" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER03.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 07 Nov 2009 20:59:37 +0100 Received: by ZIVMAILUSER03.UNI-MUENSTER.DE (Postfix, from userid 149459) id 7040F1B0751; Sat, 7 Nov 2009 20:59:37 +0100 (CET) Date: Sat, 07 Nov 2009 20:59:30 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=+permail-200911071959301e86ffa8000032f8-a_best01+ Cc: Subject: [patch] stop kdump from segfaulting with a linuxulator ktrace.out X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 19:59:39 -0000 This is a MIME encoded multipart message. --+permail-200911071959301e86ffa8000032f8-a_best01+ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit could somebody please commit this very simple patch to HEAD which has been around for almost 2 years, but never got committed (bin/120055). thanks in advance. alex --+permail-200911071959301e86ffa8000032f8-a_best01+ Content-Type: text/plain Content-Transfer-Encoding: Base64 Content-Disposition: attachment; filename="kdump.c.patch.txt" SW5kZXg6IGtkdW1wLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0ga2R1bXAuYwkocmV2aXNpb24gMTk5MDE2KQor Kysga2R1bXAuYwkod29ya2luZyBjb3B5KQpAQCAtNzk5LDcgKzc5OSw3IEBACiAJCQkJbmFyZy0t OwogCQkJfQogCQl9Ci0JCXdoaWxlIChuYXJnKSB7CisJCXdoaWxlIChuYXJnID4gMCkgewogCQkJ cHJpbnRfbnVtYmVyKGlwLG5hcmcsYyk7CiAJCX0KIAkJKHZvaWQpcHV0Y2hhcignKScpOwo= --+permail-200911071959301e86ffa8000032f8-a_best01+-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 20:59:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68DF1106566B for ; Sat, 7 Nov 2009 20:59:58 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id F0F278FC16 for ; Sat, 7 Nov 2009 20:59:57 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id d23so869788fga.13 for ; Sat, 07 Nov 2009 12:59:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=Up/dOiQPsh9i4O59I6VawxkqlGM3MBKs3PVwQtWmqzM=; b=ND+c3otX0laI7lz6WDQiBhnqglj1e6ZUcWIoTAgkq+58ByjCF2kg/I5BCCH54rabWD Nyk4I41ZE2JlshxRxD8tjBgYZ75GrgEp/ynRTmqwmYzuZF6AiRc8oK7AV2EepCH4rHNL S8YvohnZ2X9iEOY2FdDU38hCJSa8MfddNpjeI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=kMpAcT3cufQy0tKMuLJtsKwcf6lgOu9puMNczWuR2bumdCPJVcP8FpYjCmTSAsR5wZ oKlCFZkr7Oo/GvquF2XGxmTj/rX4b1FM0NWyhd01tlubb4c+s60JcIIo2ENAeJVtXX+n efKeSGApHC1bH7Oz+BZnCGZWeW3DutpRxSwWA= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.132.207 with SMTP id c15mr864412fat.56.1257627597038; Sat, 07 Nov 2009 12:59:57 -0800 (PST) In-Reply-To: References: Date: Sat, 7 Nov 2009 21:59:57 +0100 X-Google-Sender-Auth: d49c4e3218115459 Message-ID: <3bbf2fe10911071259u47c18642x3259c9c4898f7ff0@mail.gmail.com> From: Attilio Rao To: Alexander Best Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: [patch] stop kdump from segfaulting with a linuxulator ktrace.out X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 20:59:58 -0000 2009/11/7 Alexander Best : > could somebody please commit this very simple patch to HEAD which has been > around for almost 2 years, but never got committed (bin/120055). Can you fill a PR with details and assign to me? Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 21:47:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F2941065696 for ; Sat, 7 Nov 2009 21:47:55 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 1171E8FC15 for ; Sat, 7 Nov 2009 21:47:54 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id d23so877467fga.13 for ; Sat, 07 Nov 2009 13:47:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=i2UxRhVWgptwpcw7A/z0jP9W/Lga5UG27mNUreRuDfU=; b=VJauGk9kLY/j7icp4R53J3USfTG/exQ9aDakvfX8S9m/i7318aGxKuQ9oYZiWn3j/x oqPFmRgTHUteGO1VUQurvp/fEsOr0pCOe8kpeWFy3/qy6itA+mqIrS02VxhUkA4/JL/R dka0rk5Y2IT6QXymfumT/PK5nwOIKBeCXP94w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=w2/ZFZnXxDfW/NCDYuolxM1jziS8vHiGu3p4Sxw57I9llafijQMif2lA9hPcVC2b1+ HvOvDoOaFvuBT75sv7DWkiI5svPk1hrzmNCXv6mse9NgmWbDDL+p1p2uzN1sDmuXUPLA bsjBQyVWLixZ0+Xo9kicIEBb5BNSvTR15+B/U= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.4.137 with SMTP id 9mr911259far.95.1257630473948; Sat, 07 Nov 2009 13:47:53 -0800 (PST) In-Reply-To: <3bbf2fe10911071259u47c18642x3259c9c4898f7ff0@mail.gmail.com> References: <3bbf2fe10911071259u47c18642x3259c9c4898f7ff0@mail.gmail.com> Date: Sat, 7 Nov 2009 22:47:53 +0100 X-Google-Sender-Auth: 4d32a05962b49bfb Message-ID: <3bbf2fe10911071347q18414334xf73597d948ed717f@mail.gmail.com> From: Attilio Rao To: Alexander Best Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: [patch] stop kdump from segfaulting with a linuxulator ktrace.out X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 21:47:55 -0000 2009/11/7 Attilio Rao : > 2009/11/7 Alexander Best : >> could somebody please commit this very simple patch to HEAD which has been >> around for almost 2 years, but never got committed (bin/120055). > > Can you fill a PR with details and assign to me? > Sorry, I didn't notice we already have 2 PRs on it. Fix committed as r199024. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 22:05:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F07B7106566C for ; Sat, 7 Nov 2009 22:05:43 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay2.uni-muenster.de (ZIVM-EXRELAY2.UNI-MUENSTER.DE [128.176.192.15]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0B88FC13 for ; Sat, 7 Nov 2009 22:05:42 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,700,1249250400"; d="scan'208";a="228356779" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER01.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay2.uni-muenster.de with ESMTP; 07 Nov 2009 23:05:29 +0100 Received: by ZIVMAILUSER01.UNI-MUENSTER.DE (Postfix, from userid 149459) id 794AD1B0766; Sat, 7 Nov 2009 23:05:29 +0100 (CET) Date: Sat, 07 Nov 2009 23:05:28 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Attilio Rao , Alexander Best Message-ID: In-Reply-To: <3bbf2fe10911071347q18414334xf73597d948ed717f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [patch] stop kdump from segfaulting with a linuxulator ktrace.out X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 22:05:44 -0000 Attilio Rao schrieb am 2009-11-07: > 2009/11/7 Attilio Rao : > > 2009/11/7 Alexander Best : > >> could somebody please commit this very simple patch to HEAD which > >> has been > >> around for almost 2 years, but never got committed (bin/120055). > > Can you fill a PR with details and assign to me? > Sorry, I didn't notice we already have 2 PRs on it. > Fix committed as r199024. > Thanks, > Attilio thanks a lot for committing this fix. :) i'll try to find some time and come up with patches for 8-,7- and 6-stable as well so this can get mfc'ed. cheers. alex