From owner-freebsd-stable@FreeBSD.ORG Sun Oct 26 06:36:27 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F783F20 for ; Sun, 26 Oct 2014 06:36:27 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E727A119 for ; Sun, 26 Oct 2014 06:36:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s9Q6aD2H076142; Sun, 26 Oct 2014 17:36:14 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 26 Oct 2014 17:36:13 +1100 (EST) From: Ian Smith To: Lyndon Nerenberg Subject: Re: File system issues In-Reply-To: <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> Message-ID: <20141026170011.M74058@sola.nimnet.asn.au> References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 06:36:27 -0000 On Sat, 25 Oct 2014 12:11:16 -0700, Lyndon Nerenberg wrote: > On Oct 25, 2014, at 11:36 AM, Kurt Jaeger wrote: > > > I always disable journaling, because I had many failures with that > > in the past: > > > > tunefs -j disable > > I turn it off because you cannot snapshot a journaled filesystem, > which breaks live dumps. > > It would be helpful if there was a way in the installer to toggle the > default setting for 'journaled' before carving out the filesystems. > It's moderately annoying to have to go through the option settings > for all the filesystems to turn this off. And if you do go back into the options settings for a filesystem, the options you have changed, like turning off journaling, have been (or at least, appear to have been) reset to defaults, so you can't just check what you've already set, but have to start again. What I _really_ miss from sysinstall(8) is the ability to toggle the newfs flag. What you need to do now if you wish to preserve an existing filesystem - quite commonly /home - is very deliberately NOT select that filesystem from those detected, finish the install then manually, later, readd that fs to /etc/fstab AND remove the created symlink from /home to /usr/home, recreate /home as a directory, AFTER moving created dotfiles if you forgot to NOT create a non-root user during install. Relatively new users wouldn't have the slightest clue about needing to do that. But then, the general expectation that new users will want a linux-style single / directory - sure, fine for VM use - cruels the potential to use dump and restore anyway. It's a bit sad that this is still outstanding. cheers anyway, Ian From owner-freebsd-stable@FreeBSD.ORG Sun Oct 26 08:27:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 031F8C4E for ; Sun, 26 Oct 2014 08:27:26 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id B5901BC1 for ; Sun, 26 Oct 2014 08:27:25 +0000 (UTC) Received: from AprilRyan.norad (HSI-KBW-46-223-128-94.hsi.kabel-badenwuerttemberg.de [46.223.128.94]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 11A0C88776; Sun, 26 Oct 2014 09:27:15 +0100 (CET) Message-ID: <544CB063.3020002@bsdforen.de> Date: Sun, 26 Oct 2014 09:27:15 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ian Smith , Lyndon Nerenberg Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> In-Reply-To: <20141026170011.M74058@sola.nimnet.asn.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 08:27:26 -0000 On 26/10/2014 07:36, Ian Smith wrote: > On Sat, 25 Oct 2014 12:11:16 -0700, Lyndon Nerenberg wrote: > > On Oct 25, 2014, at 11:36 AM, Kurt Jaeger wrote: > > > > > I always disable journaling, because I had many failures with that > > > in the past: > > > > > > tunefs -j disable > > > > I turn it off because you cannot snapshot a journaled filesystem, > > which breaks live dumps. > > > > It would be helpful if there was a way in the installer to toggle the > > default setting for 'journaled' before carving out the filesystems. > > It's moderately annoying to have to go through the option settings > > for all the filesystems to turn this off. > > And if you do go back into the options settings for a filesystem, the > options you have changed, like turning off journaling, have been (or at > least, appear to have been) reset to defaults, so you can't just check > what you've already set, but have to start again. > > What I _really_ miss from sysinstall(8) is the ability to toggle the > newfs flag. What you need to do now if you wish to preserve an existing > filesystem - quite commonly /home - is very deliberately NOT select that > filesystem from those detected, finish the install then manually, later, > readd that fs to /etc/fstab AND remove the created symlink from /home to > /usr/home, recreate /home as a directory, AFTER moving created dotfiles > if you forgot to NOT create a non-root user during install. Relatively > new users wouldn't have the slightest clue about needing to do that. > > But then, the general expectation that new users will want a linux-style > single / directory - sure, fine for VM use - cruels the potential to use > dump and restore anyway. It's a bit sad that this is still outstanding. You can use dump from anywhere in the file system by way of nullfs mounts. -- 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-stable@FreeBSD.ORG Sun Oct 26 09:55:01 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7ABFFB6C; Sun, 26 Oct 2014 09:55:01 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3952B367; Sun, 26 Oct 2014 09:55:00 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3jQZKP0v2qzb0g; Sun, 26 Oct 2014 10:54:49 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 8XLrlYF-z2dL; Sun, 26 Oct 2014 10:54:34 +0100 (CET) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Sun, 26 Oct 2014 10:54:28 +0100 (CET) Message-ID: <544CC4D4.7040203@FreeBSD.org> Date: Sun, 26 Oct 2014 10:54:28 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: FreeBSD FS Subject: Re: panic: detach with active requests on 10.1-RC3 References: <544A538F.6060202@FreeBSD.org> <544BBB85.2020909@madpilot.net> <544BC990.4030700@madpilot.net> In-Reply-To: <544BC990.4030700@madpilot.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Glen Barber , freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 09:55:01 -0000 On 10/25/14 18:02, Guido Falsi wrote: > On 10/25/14 17:02, Guido Falsi wrote: >> On 10/24/14 15:26, Guido Falsi wrote: >>> Hi, >>> >>> I'm making some experiments with 10.1-RC3 on alix boards as hardware >>> using NanoBSD. >>> >>> By mounting and umounting UFS filesystems I have seen umount constantly >>> hanging hard in a deadlock. I have tested on two boards with two >>> distinct compactflash disks with same results. This was not happening >>> with 10.0-RELEASE. >>> >>> I have build a 10.1-RC3 kernel with full debugging and caused the >>> problem to happen, I got this: >>> >>> root@qtest:~ [0]# umount /cfg >>> panic: detach with active requests >>> KDB: stack backtrace: [...] > I must admit I am out of ideas. > I bisected commits and finally found out this happens starting with r268815, which MFCed r268205. It is related to trim support, in fact disabling trim on the filesystm "fixes" it. I filed bug #194606 on bugzilla [1] to further track this issue, if anyone is interested. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194606 -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Sun Oct 26 18:01:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A413D4E for ; Sun, 26 Oct 2014 18:01:40 +0000 (UTC) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11AE7347 for ; Sun, 26 Oct 2014 18:01:39 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id h11so2640531wiw.8 for ; Sun, 26 Oct 2014 11:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6Av6zb+7QnIgpIOBDWdbRmcPKVS1hofcTQUwtX+oivw=; b=v3L2PqphbXwk/XZbPtRPMH26uVrPYY+qtw2n/i14tzYtCXCQVSEJ0VPsxYJqb9VTfj V54VrD21oXbgUDGGSYwd/Lus39fmPcS9wp19rifl4G7u38chfcHm3VM1EGHpRSB3dOCe Dc1h6zlZ0Ki303H+9ccCH32TuVuGXqfM9Qn9bfJYRUTViM9O68AWHjwzMd9HJ2ut7x7A +BFJRl6vGx8F0SnEZhRZkMjHe/rxCUjOdgvyvrAR8SwYLXxBj6dZonBBUFfiHmNChu3R Ji4RsVOnyGmfHXDgWljjL31bCjFhl2RSpdYvpzu0iYH2keHfn5SrnZixE/R+plI6X6aB MS6g== MIME-Version: 1.0 X-Received: by 10.194.94.132 with SMTP id dc4mr18375464wjb.56.1414346498090; Sun, 26 Oct 2014 11:01:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Sun, 26 Oct 2014 11:01:37 -0700 (PDT) In-Reply-To: <20141026170011.M74058@sola.nimnet.asn.au> References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> Date: Sun, 26 Oct 2014 11:01:37 -0700 X-Google-Sender-Auth: NJemMUSN2u7wEe7i50YRVF_JgQs Message-ID: Subject: Re: File system issues From: Adrian Chadd To: Ian Smith Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable Mailing List , Lyndon Nerenberg X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 18:01:40 -0000 I think the main reason this happened is that there wasn't a nice consensus on what made sense for the disk layout. The existing rules weren't going to cut it for TB+ sized disks. What good is having a small root, a small swap and an /enormous/ /usr that took up the whole disk anyway? If someone wants to come up with patches to the installer to let us do this in a more sane way with the larger number of gpt partitions we get - then please by all means submit patches. Same goes for the newfs flag. Same goes for toggling on/off soft-updates and/or journaling. -adrian On 25 October 2014 23:36, Ian Smith wrote: > On Sat, 25 Oct 2014 12:11:16 -0700, Lyndon Nerenberg wrote: > > On Oct 25, 2014, at 11:36 AM, Kurt Jaeger wrote: > > > > > I always disable journaling, because I had many failures with that > > > in the past: > > > > > > tunefs -j disable > > > > I turn it off because you cannot snapshot a journaled filesystem, > > which breaks live dumps. > > > > It would be helpful if there was a way in the installer to toggle the > > default setting for 'journaled' before carving out the filesystems. > > It's moderately annoying to have to go through the option settings > > for all the filesystems to turn this off. > > And if you do go back into the options settings for a filesystem, the > options you have changed, like turning off journaling, have been (or at > least, appear to have been) reset to defaults, so you can't just check > what you've already set, but have to start again. > > What I _really_ miss from sysinstall(8) is the ability to toggle the > newfs flag. What you need to do now if you wish to preserve an existing > filesystem - quite commonly /home - is very deliberately NOT select that > filesystem from those detected, finish the install then manually, later, > readd that fs to /etc/fstab AND remove the created symlink from /home to > /usr/home, recreate /home as a directory, AFTER moving created dotfiles > if you forgot to NOT create a non-root user during install. Relatively > new users wouldn't have the slightest clue about needing to do that. > > But then, the general expectation that new users will want a linux-style > single / directory - sure, fine for VM use - cruels the potential to use > dump and restore anyway. It's a bit sad that this is still outstanding. > > cheers anyway, Ian > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun Oct 26 19:08:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9463E192; Sun, 26 Oct 2014 19:08:51 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 54477B40; Sun, 26 Oct 2014 19:08:51 +0000 (UTC) Message-ID: <68735655d3728032a68942cc493ac3e7.squirrel@s4bysmmsnraf7eut.onion> In-Reply-To: References: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> <3d80542ccc73686094ddde4e18465e4a.squirrel@s4bysmmsnraf7eut.onion> Date: Sun, 26 Oct 2014 19:59:28 +0100 Subject: Re: vt(4) "newcons" and 80x25 vty? (tested: 10.1-BETA2) From: beeessdee@ruggedinbox.com To: "Ed Maste" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 19:08:51 -0000 On Mon, 20 Oct 2014 10:59:27 -0400, Ed Maste wrote: > In fact, good documentation is even more important for new subsystems. > Anyhow, as a result of your comment I noticed that a vtfontcvt(8) > cross-reference was missing from vt(4); it's now added to HEAD in > r273332. THANK YOU! Comprehensive and well-written manuals are one of best aspects of FreeBSD. I like "RTFM", but so many others (ahem) say "check the wiki (yawn)" or "JFGY". So please do know, some of us appreciate those manual pages very much! Convenient link for those not want check out HEAD: https://www.freebsd.org/cgi/man.cgi?query=vtfontcvt&apropos=0&sektion=8&manpath=FreeBSD+11-current&arch=default&format=html > I've also put a quick example in the wiki > (https://wiki.freebsd.org/Newcons) of using vtfontcvt(8) to create a > larger console font, and include it here for feedback: > > 1. Fetch the Terminus font distribution and unpack it. It's available from > http://sourceforge.net/projects/terminus-font/files/latest/download?source=files The Sourceforge link give .exe file (self-extracting? !?!?). Try this: http://sourceforge.net/projects/terminus-font/files/terminus-font-4.39/terminus-font-4.39.tar.gz/download Of course this link is 4.39 only, not tracking later version. > 2. Convert the 16x32 bitmap .bdf files to a vt(4) .fnt file: > % vtfontcvt -w 16 -h 32 ter-u32n.bdf ter-u32b.bdf ter-u32.fnt > > 3. Load it from a console window to test: > % vidcontrol -f ter-u32.fnt > > On my 1920x1200 LCD this font gives me a 120x37 terminal. I intend try this and explore different options when I have test system available, then report back to this thread. Maybe a few days, sorry. As I understand, is the format one bit per pixel, high bit to low bit? I previously played with this, wrote some C code to draw simple graphics on screen by loading 256 char font with shapes as a kludge. I lost sources in a disk crash - but if vt(4) has same format, it will be easy to enjoy tinkering with it for actual fonts, as time permits! > A variant of Terminus is used as the default vt(4) console font, but > only the 8x16 size is available to us under a BSD license. A future > task is to integrate this with the terminus-font port, so that > installing the port or package is sufficient to make the full set of > sizes available to vt(4). I am not familiar with Terminus. Too bad the licence issue. It's good for base system to have these things. Any chance to use TeX fonts? IIRC many have liberal licensing. Metafont give bitmap, but I don't remember its output format. These tend to be print-oriented (not good for screen view), but also I think many people made Metafonts for different languages and scripts. This is the older fonts, some from 1980s; nowadays most TeX system take OpenType and similar, to make the PDF. Just another thing I just need time to try! Thanks also to others who replied. I want reply in this thread when I have some substance result, maybe helpful to others. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 26 21:23:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7BEBD689 for ; Sun, 26 Oct 2014 21:23:12 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 391FA9AF for ; Sun, 26 Oct 2014 21:23:11 +0000 (UTC) Received: from AprilRyan.norad (HSI-KBW-46-223-128-94.hsi.kabel-badenwuerttemberg.de [46.223.128.94]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id EB45288776; Sun, 26 Oct 2014 22:22:55 +0100 (CET) Message-ID: <544D6628.60904@bsdforen.de> Date: Sun, 26 Oct 2014 22:22:48 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ian Smith , freebsd-stable@freebsd.org Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> <544CB063.3020002@bsdforen.de> <20141027042350.M74058@sola.nimnet.asn.au> In-Reply-To: <20141027042350.M74058@sola.nimnet.asn.au> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 21:23:12 -0000 On 26/10/2014 18:37, Ian Smith wrote: > On Sun, 26 Oct 2014 09:27:15 +0100, Dominic Fandrey wrote: > > On 26/10/2014 07:36, Ian Smith wrote: > > > > But then, the general expectation that new users will want a linux-style > > > single / directory - sure, fine for VM use - cruels the potential to use > > > dump and restore anyway. It's a bit sad that this is still outstanding. > > > > You can use dump from anywhere in the file system by way of nullfs > > mounts. > > Thanks Dominic, I wasn't aware of that. Not that it makes up for not > being able to not newfs filesystems you want to keep, and in fstab, but > it's definitely worth exploring as a workaround. I have to withdraw my statement. I thought I had done it before, but I cannot get it to work. I suppose that leaves us with tar. -- 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-stable@FreeBSD.ORG Sun Oct 26 23:55:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53316589 for ; Sun, 26 Oct 2014 23:55:35 +0000 (UTC) Received: from mail-01.thismonkey.com (220-245-31-196.static.tpgi.com.au [220.245.31.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail-01.thismonkey.com", Issuer "Thismonkey IT Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1F488B5 for ; Sun, 26 Oct 2014 23:55:33 +0000 (UTC) X-TM-Via-MX: mail-01.thismonkey.com Received: from utility-01.thismonkey.com (utility-01.thismonkey.com [10.1.1.32]) by mail-01.thismonkey.com (8.14.5/8.14.5) with ESMTP id s9QNh0mD035208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 27 Oct 2014 10:43:04 +1100 (EST) (envelope-from freebsd-lists-4@thismonkey.com) Received: from utility-01.thismonkey.com (localhost [127.0.0.1]) by utility-01.thismonkey.com (8.14.5/8.14.5) with ESMTP id s9QNh0k9052704 for ; Mon, 27 Oct 2014 10:43:00 +1100 (EST) (envelope-from freebsd-lists-4@thismonkey.com) Received: (from root@localhost) by utility-01.thismonkey.com (8.14.5/8.14.5/Submit) id s9QNgvYK052697 for freebsd-stable@freebsd.org; Mon, 27 Oct 2014 10:42:57 +1100 (EST) (envelope-from freebsd-lists-4@thismonkey.com) Date: Mon, 27 Oct 2014 10:42:57 +1100 From: Scott To: freebsd-stable@freebsd.org Subject: Compiling projects into stable or release Message-ID: <20141026234256.GA52142@utility-01.thismonkey.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (mail-01.thismonkey.com [10.1.2.50]); Mon, 27 Oct 2014 10:43:04 +1100 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 23:55:35 -0000 Hi all, I'm interested in VXLan and want to compile the project (http://svnweb.freebsd.org/base/projects/vxlan/) into 10.x-RELEASE or -STABLE. Is this possible? Or must I download 11-CURRENT and install that? I've done some searching and can't find an easy way to pick a project and compile it in. Thanks in advance, Scott From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 06:47:23 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFABBB0 for ; Mon, 27 Oct 2014 06:47:23 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BDDD11AE for ; Mon, 27 Oct 2014 06:47:23 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s9R6lLwO065086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Oct 2014 23:47:22 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s9R6lLF2065085; Sun, 26 Oct 2014 23:47:21 -0700 (PDT) (envelope-from jmg) Date: Sun, 26 Oct 2014 23:47:21 -0700 From: John-Mark Gurney To: Scott Subject: Re: Compiling projects into stable or release Message-ID: <20141027064721.GD82214@funkthat.com> Mail-Followup-To: Scott , freebsd-stable@freebsd.org References: <20141026234256.GA52142@utility-01.thismonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141026234256.GA52142@utility-01.thismonkey.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sun, 26 Oct 2014 23:47:22 -0700 (PDT) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 06:47:24 -0000 Scott wrote this message on Mon, Oct 27, 2014 at 10:42 +1100: > I'm interested in VXLan and want to compile the project > (http://svnweb.freebsd.org/base/projects/vxlan/) into 10.x-RELEASE or > -STABLE. Is this possible? Or must I download 11-CURRENT and install that? > > I've done some searching and can't find an easy way to pick a project and > compile it in. So the code in vxlan is a copy of HEAD plus additional patches that add the vxlan code. So, if you check out the code, and compile it as you would HEAD, you will get the feature... If you want to use it on a previous branch, you'll need to either use svn to possibly merge these chagnes to 10stable (I don't know how one would go about doing it, or even if it is possible to do), or to generate a patch against HEAD, and apply it to 10stable... You could also ask the author if they have a version that applies to 10stable... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 08:49:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D896956 for ; Mon, 27 Oct 2014 08:49:28 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3C9FF72 for ; Mon, 27 Oct 2014 08:49:27 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XifzL-0001RT-D7 for freebsd-stable@freebsd.org; Mon, 27 Oct 2014 09:49:24 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <544C0DA3.1060201@bsdforen.de> Date: Mon, 27 Oct 2014 09:49:18 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <544C0DA3.1060201@bsdforen.de> User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: a350ae07b5350cdad28cef237d2e7179 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 08:49:28 -0000 On Sat, 25 Oct 2014 22:52:51 +0200, Dominic Fandrey wrote: > On 25/10/2014 20:36, Kurt Jaeger wrote: >> Hi! >> >>> Two or 3 days ago, after an update to stable/10 my UFS file system >>> started acting weird. I have freezes and files disappearing from the >>> system. >>> >>> The first time that happened SU+J failed me. >> >> I always disable journaling > > I think that's just a symptom here. The issue is stuff mysteriously > disappearing from my file system on a running system. > > Hi, Weird stuff. If you read the following mail thread there is a confirmed problem with fsck on ARM systems with disappearing files. http://lists.freebsd.org/pipermail/freebsd-arm/2014-September/009168.html It also states that the same problem does not occur on other platforms (and I can fsck my ARM systems usb-stick on a amd64 system successfully), but I thought it is worth mentioning. Regards, Ronald. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 09:26:53 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3614B2F2; Mon, 27 Oct 2014 09:26:53 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE5C63EF; Mon, 27 Oct 2014 09:26:52 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XigZe-000IY6-RT; Mon, 27 Oct 2014 10:26:51 +0100 Message-ID: <544E0FC8.8090605@FreeBSD.org> Date: Mon, 27 Oct 2014 10:26:32 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: CFT: Update to xf86-video-ati 7.5.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3oi0gWCsGPSvODn09TucdXurITVpIJSpp" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 09:26:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3oi0gWCsGPSvODn09TucdXurITVpIJSpp Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi! Before updating xf86-video-ati to 7.5.0, we would like some people to try it out. The reason is that 7.4.0 was crashing for several users, so we want to be sure it's fixed in 7.5.0. Here's patch: https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.= patch To apply it: cd /usr/ports patch -p1 < /path/to/ports-xf86-video-ati-7.5.0.patch Then update x11-drivers/xf86-video-ati with your method of choice. What we're especially looking for is report of successful or failed startup of the X server. With 7.4.0, the server would crash during startup. But with 7.5.0, none of us could reproduce the problem. When you're finished, you may restore your vanilla ports tree: cd /usr/ports patch -p1 -R < /path/to/ports-xf86-video-ati-7.5.0.patch find x11-drivers/xf86-video-ati -name "*.orig" -delete Thank you for your help! --=20 Jean-S=C3=A9bastien P=C3=A9dron --3oi0gWCsGPSvODn09TucdXurITVpIJSpp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUTg/aXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMq18QAMz1ZUMPGGrLAQh3zeGIIRUc mwgMAifWupwpZQfFLig+3HvtPbtq6x49a5RlZvESkfSJnI0CSXgI8YZRNj/32EUN SekhwHCngggSVCke8lt/LglVGJ/RWSZbqaWnZ+DLjW+H41uIoozGHyWmSwamth3a sX5QDjMcI6LRIoLtjjo1QB1FvzFZRI0vqB4rcx0ILW+C54YWvJyaSM4MBmdkH385 5HtEsUWJtufJ8WNSoJXv+/ItqT4rSMy3rE/l+kG1As38wr21xV3rUHd8I6Ypmsen zKQsahAgQU6U9/8pH3OmQS1K+UTxgznqatX/hndWEJE4JqMRw+yt0UoIkWw/iypY Ecrhx5tX8GOWNKJjvPseB1qgavJfNneVwLjw9RpaEU6XErZV2iaSWr6OvvJ7jj5g Ng+ZB8oSEryJ9dzDykpSC+ansfy2xLa605f9ARQC9Q+WFIzarWgVz0uy8Ku20kpe jtZKQsHVxvkC5Tbsm1bJOH2+yLNr4gmb+OB8OHOkWk5S7lxFXq9ads2c658Sk5cq Zrau3Oj63yMthrxS0lsW/KVZj/ko5ks0UAS0hKmN1/AkwRyH3zsmoye72tuZgcoA ddPZBkZNEQCCA2UUoKkrl1bFg+Gl5HK9321uv4PqqgpfLdYhmYF3CLpJx/f9Demt /112lTjBbVrYPae238/9 =8/I2 -----END PGP SIGNATURE----- --3oi0gWCsGPSvODn09TucdXurITVpIJSpp-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 10:07:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3E934A8; Mon, 27 Oct 2014 10:07:50 +0000 (UTC) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E67C5BA0; Mon, 27 Oct 2014 10:07:49 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id q5so5894212wiv.5 for ; Mon, 27 Oct 2014 03:07:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Oihd0LTg4cFVI6IDA+uJZDc0nKz/Pd5LpllVQhUVo4Q=; b=JvYGnPj1h0C5kK1PQ1dqOYd2eBIXZzN8eF+SsY94N/SLFXMhxuGBRVfh9hQwpigFoJ W7usb/Ne0GXg+7SsErD0kSnoe5KzHNu744wxKq2tEw9RfTvTAMikBWLSj0VuDcAxlyKU lAYllU0BqSHtZfgrdbQTB4WjyRzsWZLt3VmLH7D9ikyp9eIDYRolJqg8Zo8Pk1NSSq5Q CGAbzT3O7+sADCVMGD9oC1faXCWi67tXJ7MFeLuQM11TUVTw6YP82+sbmJbs0BAngvMU KGC2v3jMtDhhSP491CINcXeuFsmK0pHscmnOq+NaBDP4Bjj7VolGYjYJ+OcKN2OwK0Jk gD0Q== MIME-Version: 1.0 X-Received: by 10.194.104.170 with SMTP id gf10mr2008007wjb.88.1414404468002; Mon, 27 Oct 2014 03:07:48 -0700 (PDT) Received: by 10.194.90.212 with HTTP; Mon, 27 Oct 2014 03:07:47 -0700 (PDT) In-Reply-To: <544E0FC8.8090605@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> Date: Mon, 27 Oct 2014 11:07:47 +0100 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-x11@freebsd.org, FreeBSD stable , freebsd-ports@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 10:07:50 -0000 2014-10-27 10:26 GMT+01:00 Jean-S=C3=A9bastien P=C3=A9dron : > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. Hi, Works fine here (RV610 video device [Radeon HD 2400 PRO]) Thanks! Mika=C3=ABl From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 10:24:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF5F5BBD; Mon, 27 Oct 2014 10:24:52 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2706DAB; Mon, 27 Oct 2014 10:24:51 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XihTf-0004vf-Jt; Mon, 27 Oct 2014 11:24:48 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: certificate error - (was: Re: CFT: Update to xf86-video-ati 7.5.0) References: <544E0FC8.8090605@FreeBSD.org> Date: Mon, 27 Oct 2014 11:24:42 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: <544E0FC8.8090605@FreeBSD.org> User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: 7006e789400ccdeb5065f5d065827fb5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 10:24:53 -0000 On Mon, 27 Oct 2014 10:26:32 +0100, Jean-S=E9bastien P=E9dron = wrote: > Hi! > > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. The reason is that 7.4.0 was crashing for several users, s= o > we want to be sure it's fixed in 7.5.0. > > Here's patch: > https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5= .0.patch > > To apply it: > cd /usr/ports > patch -p1 < /path/to/ports-xf86-video-ati-7.5.0.patch > > Then update x11-drivers/xf86-video-ati with your method of choice. > > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. > > When you're finished, you may restore your vanilla ports tree: > cd /usr/ports > patch -p1 -R < /path/to/ports-xf86-video-ati-7.5.0.patch > find x11-drivers/xf86-video-ati -name "*.orig" -delete > > Thank you for your help! > fetch = 'https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.= 0. patch' Certificate verification failed for /C=3DUS/ST=3DUT/L=3DSalt Lake City/O= =3DThe = USERTRUST Network/OU=3Dhttp://www.usertrust.com/CN=3DUTN-USERFirst-Hardware 34380950936:error:14090086:SSL = routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify = failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:= 1 180: fetch: = https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0= . patch: Authentication error Using the option '--ca-cert=3D/usr/local/share/certs/ca-root-nss.crt' fr= om = port ca_root_nss for fetch helps. Something wrong in my setup, that default certs of 10.1-STABLE are not = enough? Regards, Ronald. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 10:39:32 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0247495; Mon, 27 Oct 2014 10:39:32 +0000 (UTC) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BED44EE8; Mon, 27 Oct 2014 10:39:31 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1Xihhw-00082K-JF; Mon, 27 Oct 2014 10:39:28 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xihhw-0000i0-Gu; Mon, 27 Oct 2014 10:39:28 +0000 To: dumbbell@FreeBSD.org, freebsd-ports@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-x11@FreeBSD.org Subject: Re: CFT: Update to xf86-video-ati 7.5.0 In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Message-Id: From: Pete French Date: Mon, 27 Oct 2014 10:39:28 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 10:39:32 -0000 > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. Works fine here - I had to update libdrm as well to get it to build. The devise is 'RV620 LE [Radeon HD 3450]' -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 11:35:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EC968EA for ; Mon, 27 Oct 2014 11:35:54 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB30B8F1 for ; Mon, 27 Oct 2014 11:35:53 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id w7so897300lbi.24 for ; Mon, 27 Oct 2014 04:35:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+CFPQKJdAVThVFALWnBSUJR893HELvRVq0VRUt8UaxM=; b=S9gPxg76kP/ZPte3ze6KTEAkr7PSdITUEpiGHOmJ8KcNLHXpNV3+So7OlXsTN8qgh2 vgbq1nGT4xj9u90IaDAd//UlquGBng3jSadkI1MnNOSSXSNJVRkKw7LrIW+Sqzdkbzfm zRNt/f5KBugtCNV9/YA1iL2dS5sbOXcgCmuCCsN7hLNA6xm/uGvx4Kyi+8WjD27chLMF IDuzI0VwsNl618q5apOVNYWSMZxQBjjyW/Z4UjRC3M6j5/0FKkNVNuoKmmZpic+BetQE lptIvptjzyVw1CmoTmSUaOh+64/P6+K2lcCX3R6Q1791KyterDYccSfspr8goCRG4Y8g nfLA== X-Received: by 10.112.169.6 with SMTP id aa6mr23274864lbc.29.1414409751692; Mon, 27 Oct 2014 04:35:51 -0700 (PDT) Received: from blazon-pc.rw.local ([78.84.244.14]) by mx.google.com with ESMTPSA id sd10sm4878294lbb.8.2014.10.27.04.35.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Oct 2014 04:35:51 -0700 (PDT) Message-ID: <544E2E16.9020008@gmail.com> Date: Mon, 27 Oct 2014 13:35:50 +0200 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: "msk0: watchdog timeout" still present in 10.1-RC2 References: <543FD1BB.9010501@gmail.com> In-Reply-To: <543FD1BB.9010501@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 11:35:54 -0000 For me, this problem has gone away in RC3 (10.1-RC3 FreeBSD 10.1-RC3 #0 r273437: Tue Oct 21 23:55:15 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64) I hope it will stay that way in 10.1-RELEASE... On 10/16/2014 17:10, Alnis Morics wrote: > Hello, > > Several months ago we were talking about Marvell NIC not working, and > the problem remained unsolved. So far, I have experienced it only in > FreeBSD 10 (no problem in 9.X-RELEASE or 11-CURRENT), and only in > amd64. So I hoped in 10.1 it would be solved but no: suffice to scp a > 5MB file through this interface, and the "watchdog timeout" is there. > > uname -a: > FreeBSD myhost.mydomain.tld 10.1-RC2 FreeBSD 10.1-RC2 #0 r272876: Fri > Oct 10 01:12:21 UTC 2014 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > pciconf -lv: > [..] > mskc0@pci0:9:0:0: class=0x020000 card=0xc072144d chip=0x435411ab > rev=0x00 hdr=0x00 > vendor = 'Marvell Technology Group Ltd.' > device = '88E8040 PCI-E Fast Ethernet Controller' > class = network > subclass = ethernet > > _____ > Alnis From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 12:00:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88ED629C for ; Mon, 27 Oct 2014 12:00:52 +0000 (UTC) Received: from mail14.tpgi.com.au (smtp-out14.tpgi.com.au [220.244.226.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.tpg.com.au", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1345BB88 for ; Mon, 27 Oct 2014 12:00:51 +0000 (UTC) X-TPG-Junk-Status: Message not scanned X-TPG-Antivirus: Passed X-TPG-Abuse: host=[202.161.115.54]; ip=202.161.115.54; date=Mon, 27 Oct 2014 22:34:12 +1100 Received: from fish.ish.com.au (202-161-115-54.static.tpgi.com.au [202.161.115.54] (may be forged)) by mail14.tpgi.com.au (envelope-from ari@ish.com.au) (8.14.3/8.14.3) with ESMTP id s9RBYAmh019745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Oct 2014 22:34:12 +1100 Received: from ip-211.ish.com.au ([203.29.62.211]:15128 helo=ish.com.au) by fish.ish.com.au with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XiiYn-0004f4-1N; Mon, 27 Oct 2014 22:34:06 +1100 Received: from [203.29.62.136] (HELO ip-136.ish.com.au) by ish.com.au (CommuniGate Pro SMTP 6.0.9) with ESMTPS id 17790641; Mon, 27 Oct 2014 22:34:05 +1100 Message-ID: <544E2DAB.2090309@ish.com.au> Date: Mon, 27 Oct 2014 22:34:03 +1100 From: Aristedes Maniatis User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Thunderbird/33.0 MIME-Version: 1.0 To: John Nielsen , freebsd-stable Subject: Re: pkgng upgrade -> force upgrade of dependencies References: <5448A373.1070707@ish.com.au> <97F5BECA-C7D0-49EE-AC91-7B87A990307D@jnielsen.net> In-Reply-To: <97F5BECA-C7D0-49EE-AC91-7B87A990307D@jnielsen.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 12:00:52 -0000 On 26/10/2014 1:57am, John Nielsen wrote: >> On Oct 23, 2014, at 12:42 AM, Aristedes Maniatis wrote: >> >> I've scoured the documentation, but I cannot for the life of me figure how to do this. Let's say I want to upgrade a package "apache22" without upgrading everything on the system. Now I want to ensure I get enough of the dependencies into the upgrade that apache will actually work. So I try this: >> >> # pkg upgrade apache22-worker-mpm >> Installed packages to be UPGRADED: >> apache22-worker-mpm: 2.2.27_6 -> 2.2.29_2 >> >> Hmmm, that doesn't seem right. >> >> # pkg upgrade | grep openssl >> openssl: 1.0.1_15 -> 1.0.1_16 >> >> # pkg info -d apache22-worker-mpm >> apache22-worker-mpm-2.2.27_6: >> expat-2.1.0_1 >> openssl-1.0.1_15 >> perl5-5.16.3_11 >> pcre-8.34_2 >> apr-1.5.1.1.5.3_4 >> libiconv-1.14_3 >> >> So, a new version of openssl is needed and is linked to the new binary. But it will not be installed when I upgrade apache. >> >> >> Before I moved to pkgng/poudriere I used to use portmaster. That would more thoroughly examine the dependencies and make sure everything that was inter-related (both as parent and child dependencies) was upgraded together. But it did not force me to upgrade Java when I just wanted to get the new version of bash installed. > > I'm not certain that it handles dependencies (it ought to), but the documented way to upgrade selectively is via "pkg install pkgname ..." For anyone following along, I found a bug report for this problem in pkgng. It isn't where I was originally looking (bugzilla) since it seems they use github for development: https://github.com/freebsd/pkg/issues/964 -- --------------------------> Aristedes Maniatis ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 13:58:45 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BA9EF22 for ; Mon, 27 Oct 2014 13:58:45 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2AF4AC2 for ; Mon, 27 Oct 2014 13:58:44 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Xikof-000DKe-3t; Mon, 27 Oct 2014 13:58:37 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s9RDwZeL076363; Mon, 27 Oct 2014 07:58:35 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Gx8weFR4NTyyPJH7B9dgn X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: File system issues From: Ian Lepore To: Ronald Klop In-Reply-To: References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <544C0DA3.1060201@bsdforen.de> Content-Type: text/plain; charset="us-ascii" Date: Mon, 27 Oct 2014 07:58:34 -0600 Message-ID: <1414418314.17308.2.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 13:58:45 -0000 On Mon, 2014-10-27 at 09:49 +0100, Ronald Klop wrote: > On Sat, 25 Oct 2014 22:52:51 +0200, Dominic Fandrey > wrote: > > > On 25/10/2014 20:36, Kurt Jaeger wrote: > >> Hi! > >> > >>> Two or 3 days ago, after an update to stable/10 my UFS file system > >>> started acting weird. I have freezes and files disappearing from the > >>> system. > >>> > >>> The first time that happened SU+J failed me. > >> > >> I always disable journaling > > > > I think that's just a symptom here. The issue is stuff mysteriously > > disappearing from my file system on a running system. > > > > > > Hi, > > Weird stuff. If you read the following mail thread there is a confirmed > problem with fsck on ARM systems with disappearing files. > http://lists.freebsd.org/pipermail/freebsd-arm/2014-September/009168.html > It also states that the same problem does not occur on other platforms > (and I can fsck my ARM systems usb-stick on a amd64 system successfully), > but I thought it is worth mentioning. > It seems unlikely to be related, but it would be easy to test: mdconfig -a -t malloc -s 64m # assume that created unit 0 newfs /dev/md0 fsck -t ffs /dev/md0 If that reports errors, you've got the problem. If it doesn't, it's some other problem. So far the problem exposed by the sequence above happens only on one specific type of old low-end arm system; it hasn't yet been reproduced on even other arm systems, let alone other arches. -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 14:07:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68E52170; Mon, 27 Oct 2014 14:07:46 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB48FBB5; Mon, 27 Oct 2014 14:07:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s9RE7QfZ040575; Tue, 28 Oct 2014 01:07:27 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 28 Oct 2014 01:07:26 +1100 (EST) From: Ian Smith To: Dominic Fandrey Subject: Re: File system issues In-Reply-To: <544D6628.60904@bsdforen.de> Message-ID: <20141027214537.X74058@sola.nimnet.asn.au> References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> <544CB063.3020002@bsdforen.de> <20141027042350.M74058@sola.nimnet.asn.au> <544D6628.60904@bsdforen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Adrian Chadd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 14:07:46 -0000 On Sun, 26 Oct 2014 22:22:48 +0100, Dominic Fandrey wrote: > On 26/10/2014 18:37, Ian Smith wrote: > > On Sun, 26 Oct 2014 09:27:15 +0100, Dominic Fandrey wrote: > > > On 26/10/2014 07:36, Ian Smith wrote: > > > > > > But then, the general expectation that new users will want a linux-style > > > > single / directory - sure, fine for VM use - cruels the potential to use > > > > dump and restore anyway. It's a bit sad that this is still outstanding. > > > > > > You can use dump from anywhere in the file system by way of nullfs > > > mounts. > > > > Thanks Dominic, I wasn't aware of that. Not that it makes up for not > > being able to not newfs filesystems you want to keep, and in fstab, but > > it's definitely worth exploring as a workaround. > > I have to withdraw my statement. I thought I had done it before, but I > cannot get it to work. I suppose that leaves us with tar. I spent some time exploring trying to dump a nullfs-mounted (copy of) /etc last night, to no avail. I finally managed to make a snapshot of that with mksnap_ffs, mounted it as an md, but it turned out to be just a snapshot of / and not dumpable anyway. tar is generally useful, especially with trees like /home where there tend not to be any hard-linked files, here anyway. But I'd miss dump. I learned some new things, but C wasn't one of them (sorry, Adrian :) cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 16:24:11 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84EEBA43 for ; Mon, 27 Oct 2014 16:24:11 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A8FCE1C for ; Mon, 27 Oct 2014 16:24:11 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id s9RGPLZq021399; Mon, 27 Oct 2014 09:25:21 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: David Wolfskill , Alban Hertroys , freebsd-stable , Kevin Oberman In-Reply-To: References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org>, From: "Chris H" Subject: Re: Dump time issues Date: Mon, 27 Oct 2014 09:25:21 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 16:24:11 -0000 On Sat, 25 Oct 2014 11:26:44 -0700 Kevin Oberman wrote > On Sat, Oct 25, 2014 at 4:38 AM, David Wolfskill > wrote: > > > On Sat, Oct 25, 2014 at 01:26:43PM +0200, Alban Hertroys wrote: > > > I?m seeing something odd in my dump output that I didn?t notice before: > > > > > > Dumping /root... > > > DUMP: WARNING: should use -L when dumping live read-write filesystems! > > > > (That, by the way, is pretty good advice in my experience.) > > > > As long as the volume is not SU+J. Then, in my experience, it's very bad > advice. This reminds me of a question that I've been meaning to ask for some time now; Why is the FreeBSD install media using SU+J by default? While I understand Journaling reduces retrieve times, which makes it all seem more responsive. IMHO the consequences, and limitations it imposes, seem to outweigh the pro's. Just wondering... --Chris > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 17:05:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B69B32B9; Mon, 27 Oct 2014 17:05:32 +0000 (UTC) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D90DB381; Mon, 27 Oct 2014 17:05:31 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id x13so1821347wgg.5 for ; Mon, 27 Oct 2014 10:05:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=d8pi9dqZx/IbvlDU+sy1wAIWeFf5/enYGv41Y6zpAmg=; b=DSstWkSQqLiKLmOqiy0H8461ITfOYsfNp/uruHq27EsjFMUzxSCc7mEsYPhcyEVEi3 dr298p6/O3Wr4iaoItCihd/FQhS6CgpVW+FdB1IqmAzRNUF/kqexN1aSWZcypzupPtsh X7gr0Vj7avtnxYTuhAFe8JcTFM3rkKEdhw4eCtAYkUyBMgbXAJFhPcff2ZzRLnlRfO2v 9UQ4Ib9saV/rrhOOmNMrTQHpHVaBCn97N1FO/x9Orl2En8hm8BoBWsfBX1idHevZ14QK Iisyak/ms/y2ORerRzqbZPWcOtqnrqQIcISFI8PU/Hb+A71cKA3R5w34A56j3S0PJyNv QUaw== MIME-Version: 1.0 X-Received: by 10.194.104.170 with SMTP id gf10mr4528248wjb.88.1414429530056; Mon, 27 Oct 2014 10:05:30 -0700 (PDT) Received: by 10.194.90.212 with HTTP; Mon, 27 Oct 2014 10:05:30 -0700 (PDT) In-Reply-To: <544E0FC8.8090605@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> Date: Mon, 27 Oct 2014 18:05:30 +0100 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-x11@freebsd.org, FreeBSD stable , freebsd-ports@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 17:05:32 -0000 2014-10-27 10:26 GMT+01:00 Jean-S=C3=A9bastien P=C3=A9dron : > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. It works fine on this gpu: FirePro V4800 From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 17:10:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F38F6760; Mon, 27 Oct 2014 17:10:54 +0000 (UTC) Received: from mithlond.kdm.org (mithlond.kdm.org [70.56.43.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BC10264E; Mon, 27 Oct 2014 17:10:54 +0000 (UTC) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.14.9/8.14.9) with ESMTP id s9RHAqiM092448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Oct 2014 11:10:52 -0600 (MDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.14.9/8.14.9/Submit) id s9RHAq14092447; Mon, 27 Oct 2014 11:10:52 -0600 (MDT) (envelope-from ken) Date: Mon, 27 Oct 2014 11:10:52 -0600 From: "Kenneth D. Merry" To: Konstantin Belousov Subject: Re: sa(4) 9.2->10.1, nsa0.0: request ptr 0x803135040 is not on a page boundary; cannot split request Message-ID: <20141027171052.GA92347@mithlond.kdm.org> References: <54494E92.5010007@omnilan.de> <20141024230725.GA50845@mithlond.kdm.org> <20141025175350.GK1877@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141025175350.GK1877@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Mon, 27 Oct 2014 11:10:52 -0600 (MDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mithlond.kdm.org Cc: Harald Schmalzbauer , royger@freebsd.org, FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 17:10:55 -0000 On Sat, Oct 25, 2014 at 20:53:50 +0300, Konstantin Belousov wrote: > On Fri, Oct 24, 2014 at 05:07:26PM -0600, Kenneth D. Merry wrote: > > On Thu, Oct 23, 2014 at 20:53:06 +0200, Harald Schmalzbauer wrote: > > > Hello, > > > > > > I read about the changes in sa(4) regarding large-block-split changes > > > and the transitional 'kern.cam.sa.allow_io_split' workarround. > > > > > > I'm using bacula (7.0.5) and my previous neccessarry multi-blocking > > > adjustmets like "Minimum block size = 2097152" obviously didn't work > > > with FreebSD 10.1 anymore. > > > Good news is, they are not needed any more! > > > With the default of 126 blocks (64512) I get 60-140MB/s with btape(8)'s > > > speed test on my LTO4 (HH) drive and another quick test showed that > > > using mbuffer(1) for zfs(8) 'send' isn't needed anymore (| dd > > > of=/dev/nsa0 bs=64512 seems to max out LTO4 speed). [with FreeBSD 9 the > > > transfer rates were some magnitudes lower with these block size settings!] > > > > > > Not so good news is, that bacula can't read the tape's label. > > > 'Labeling a tape (with 'label' at bconsole(8) or btape(8)) is > > > successful, and btape(8)'s 'readlabel' partially displays the correct > > > label, but not the very beginning of the label: > > > Volume Label: > > > Id : **error**VerNo > > > ?rest OK > > > > > > While it should read: > > > Volume Label: > > > Id : Bacula 1.0 immortal > > > VerNo : 11 > > > ? > > > > > > When btape(8) starts to read the label, the _subject's error is reported_: > > > *nsa0.0: request ptr 0x803135040 is not on a page boundary; cannot split > > > request* > > > > What blocksize are you using with btape(8)? > > > > What kind of controller are you using? > > > > The reason you get that error message is that the sa(4) driver goes through > > physio(9) to get buffers from userland into the kernel. physio(9) relies > > on the vmapbuf()/vunmapbuf() routines to map buffers in and out of the > > kernel. > > > > vmapbuf() operates with a page granularity. The address to be mapped has > > to start on a page boundary. It also uses kernel virtual address segments > > that are MAXPHYS in size. On x86 boxes at least, MAXPHYS is 128KB. > > > > So if you use a blocksize of 128KB, but pass in a pointer that doesn't > > start on a page boundary, vmapbuf() will have to map 33 pages instead of > > 32. In your case, it will have to start at page address 0x803135000, and > > will need 33 4KB pages, which is greater than 128KB. > I want to disable unaligned physio at all. > > See https://reviews.freebsd.org/D888 for yet another case where this beats. > > Obvious thing which stops us from doing this is binary compatibility. > I need some form of wide support to make this change. I don't see how we can remove support for non-page-aligned I/O through the various block and character devices. It would break all kinds of things, and Bacula is just the start. Perhaps another way to handle it would be that requests with unaligned buffers would just go through a non-optimal path. We could just malloc buffers and copy the data in and out. If the application sends in aligned buffers, it can go through the optimal path. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 17:26:49 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 468D2B62 for ; Mon, 27 Oct 2014 17:26:49 +0000 (UTC) Received: from mx12-out5.antispamcloud.com (mx12-out5.antispamcloud.com [46.165.232.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6C437D9 for ; Mon, 27 Oct 2014 17:26:48 +0000 (UTC) Received: from net06.redwood.com ([91.233.6.246] helo=mail.redwood.com) by mx12.antispamcloud.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1XihNV-0004CB-RF; Mon, 27 Oct 2014 11:18:25 +0100 Received: from exceu2.rwd.lan ([fe80::e42a:a959:5640:381a]) by exceu2.rwd.lan ([fe80::e42a:a959:5640:381a%10]) with mapi id 14.01.0438.000; Mon, 27 Oct 2014 11:18:21 +0100 From: Maikel Verheijen To: Jim Harris Subject: Re: nvd disk on nvme controller not detected at boot-time Thread-Topic: nvd disk on nvme controller not detected at boot-time Thread-Index: AQHP54ttNqAodkLuEEmDqzIhnS+RzpwzAKSAgAAz24D//+tugIAQnuCA Date: Mon, 27 Oct 2014 10:18:21 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.5.141003 x-originating-ip: [10.31.1.9] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Filter-ID: s0sct1PQhAABKnZB5plbIV6jvtGXzsRLyDxHGPnOSosTzNYXe+HZr4WowsEZlxIc1tZWiYINMnD4 agKXMg0NtBlCFCOA7kScelqCJFYKursKpTLhc3scs8lIU/v8u+rLonq0jcl6y1B4xrk1sOdNSWS2 BpcZp5MieEYXpn6TUALZI/Mr0BskU9hAYZ3Ymm+Y77VjOXfkZEVwPyGgPVOYnglmrUSy8PYPTMnz Rh7I8ipQDYBOio8xLA3W1+wcW/TfBIIZGAiIku3Cx523pDpt3x48vBcmKs9GYcu0FLW7EWPlgTl6 fJxyntEfhZCKje4Zx0bFDp3mGK8Y7ug+kgE2tol2UKe9D6SGnFl2eHdGD56roVjH0lzFpZqUycuK 16uwBmJ8Q0iagechgWqTL3vIA1Jh9nHh5xBVP9pvcu1pgYqSoC5VPlOdrUr8E6UB0EPg3VyTyNUA us5wK5dhtldfyDQttY3c9bWbvNE9580khkH/asDO0V6SUvEY03codo+QZd7VZNM714SJ3DaW+K4f VsdxRa5Rvm6JFujnJaOZwdtixEWhmbBXdtEvx2xJnvEp4oIKD0HBt4sWrEIlE8VJalYFvf25LVON YbYifH5OzZANAwxW2AvNktcRxKgEznEpH50YYHE3/09I4g/iRQecfi+orTeREDUbREcPuO+7veLj r9jD+xEtCAUWMNpEVddcVmUctY5jL1s3weViixsNRA== X-Report-Abuse-To: spam@mx99.antispamcloud.com X-Filter-Fingerprint: IFrWXGses7OKB5S5G8/dJfl+3wvwn7+SNaMrU0HGnonJUWjZ8+qhjyB23tbDuyLOYL8Ff78gYsez 4Rl08xudmXi4esCQ0R1MchVjt7wblGlvhFgW0MjUMRkF5sMCDfftTXNFDzN17hnrWeZYOJvLq0Ic WjZ+XcEjj/7Pkld0zkmvziDInX9WdMov2kn2yXjdwv61T+KDYyYtREgszdyFwv8IxCB3p/oCKvxr eyISh3JGb7OS5oVgiO+kDxZrVPLz3MmEGC2PrUKqLq5WmHK+Nw== X-Originating-IP: 91.233.6.246 X-Spampanel-Domain: freebsd.org X-Spampanel-Username: sysadmin Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=sysadmin X-Spampanel-Outgoing-Class: ham X-Spampanel-Outgoing-Evidence: Combined (0.01) X-Recommended-Action: accept Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 17:26:49 -0000 Hi Jim, From: Jim Harris Date: Thursday 16 October 2014 21:29 To: Maikel Cc: "freebsd-stable@freebsd.org" Subject: Re: nvd disk on nvme controller not detected at boot-time > >I cannot recommend whether 10.1-RC would be safe for a production >environment, but you could certainly use 10.1-RC to at least confirm it >fixes the issues described. We=B9re currently running the system with 10.1-rc2 and we can confirm your fix works perfectly. Thanks a lot for your effort and for replying to me. >Best regards, > >-Jim Thanks again, Kind regards, Maikel Verheijen From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 17:30:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93F2BE27 for ; Mon, 27 Oct 2014 17:30:32 +0000 (UTC) Received: from mail.thecoffinclub.com (thecoffinclub.com [200.46.208.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5FE85810 for ; Mon, 27 Oct 2014 17:30:31 +0000 (UTC) Received: from localhost (mx2.hub.org [200.46.204.254]) by mail.thecoffinclub.com (Postfix) with ESMTP id 632B523BA45 for ; Mon, 27 Oct 2014 10:20:45 -0700 (PDT) Received: from mail.thecoffinclub.com ([200.46.208.155]) by localhost (maia.hub.org [200.46.204.254]) (maiad, port 10024) with ESMTP id 83136-05 for ; Mon, 27 Oct 2014 14:20:45 -0300 (ADT) Received: from [140.107.157.127] (DHCP157127.FHCRC.ORG [140.107.157.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.thecoffinclub.com (Postfix) with ESMTPSA id BD41023BA44 for ; Mon, 27 Oct 2014 10:20:44 -0700 (PDT) Message-ID: <544E7EEF.5060600@thecoffinclub.com> Date: Mon, 27 Oct 2014 10:20:47 -0700 From: Jacob Frelinger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-stable Subject: Issues with file backed swap in recent 10-stable. Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 17:30:32 -0000 I've been running with a file backed md swap on 10-stable, and after a recent update (updated to revision 273709) swap is no longer automatically added at boot time. The md device is created, but swapinfo shows it has not been added as a swap device. If I remove the device (via mdconfig -d) I can run /etc/rc.d/swap and the device is properly recreated and added as a swap device. I don't think anything has changed in my setup, and I have no error messages in dmesg/boot log explaining why it doesn't work. Anyone else have similar problem or advice on troubleshooting? relevant line in my fstab is below: md99 none swap sw,file=/usr/swap/swap 0 0 -- Jacob Frelinger jolly@thecoffinclub.com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 18:09:41 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74469A91 for ; Mon, 27 Oct 2014 18:09:41 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F6BBC3C for ; Mon, 27 Oct 2014 18:09:41 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id tp5so4885733ieb.36 for ; Mon, 27 Oct 2014 11:09:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WhsIMpGbc7ZKcpB1TXIAmEhEKlO1hAo5N92q+h4n4Ko=; b=JjRcu8Cp+mCWVzqGNCXeerpz5lfEz8Szi+mm3xftaX509W03pJE0V+ItsuJYmL1bXo odBQ05Ei/XPS87Nuyrm/BPxAZ5XH5K3wB8dEMYjwqnc7iqNL1HNtaC5D4iSdnVQNn/08 enI8O5HVJbmoA7H12ieNwx2bB6Z2gFsW/f3SneVgzvDoKiaFyzDpQjkgwkqXC1QRRCL3 iZITAE57/fiTk3GNEZfv7hTiL2zNimVoApm+B1noj3BPFn1Fv876xTGX5zJ0Dxi3IqrL LeQWlxDKbe0yqQMj6h30Dk1STuTIkaTyy9VxsmWutPau6tYWQniomQzuZ6tRjAMBm/YB KN/g== MIME-Version: 1.0 X-Received: by 10.50.128.137 with SMTP id no9mr24099194igb.0.1414433380503; Mon, 27 Oct 2014 11:09:40 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Mon, 27 Oct 2014 11:09:40 -0700 (PDT) In-Reply-To: <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> Date: Mon, 27 Oct 2014 11:09:40 -0700 X-Google-Sender-Auth: 7pfDLyIOw-aTeM4qTZOFg4TVkzc Message-ID: Subject: Re: Dump time issues From: Kevin Oberman To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 18:09:41 -0000 On Mon, Oct 27, 2014 at 9:25 AM, Chris H wrote: > On Sat, 25 Oct 2014 11:26:44 -0700 Kevin Oberman > wrote > > > On Sat, Oct 25, 2014 at 4:38 AM, David Wolfskill > > wrote: > > > > > On Sat, Oct 25, 2014 at 01:26:43PM +0200, Alban Hertroys wrote: > > > > I?m seeing something odd in my dump output that I didn?t notice > before: > > > > > > > > Dumping /root... > > > > DUMP: WARNING: should use -L when dumping live read-write > filesystems! > > > > > > (That, by the way, is pretty good advice in my experience.) > > > > > > > As long as the volume is not SU+J. Then, in my experience, it's very bad > > advice. > This reminds me of a question that I've been meaning to ask for some > time now; > Why is the FreeBSD install media using SU+J by default? > While I understand Journaling reduces retrieve times, which makes it > all seem more responsive. IMHO the consequences, and limitations it > imposes, seem to outweigh the pro's. > Just wondering... > > --Chris > > I'm aware of two issues with SU+J, one of which is annoying and the other is worse. 1. If the journal is not fully written on power fail or some other reason, you may need to do a full fsck of the volume and the behavior of the system until this is done can be very unpredictable. 2. You can't safely snapshot the system. This is what 'dump -L' does. This means that some files dumped from a live FS may not be consistent (not good!) or, if '-L' is used, the system may well hang. While I love the fast fsck times (2 or 3 seconds) after a crash, I also question the default. Still, it may be a preferred choice be used for very large file systems where a full fsck would take a very long time as long as the risks are understood. For these systems, ZFS might be a better choice. These arguments do NOT favor it being the default, IMHO. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 19:14:07 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 638B8D1E for ; Mon, 27 Oct 2014 19:14:07 +0000 (UTC) Received: from nmsh3.e.nsc.no (nmsh3.e.nsc.no [193.213.121.74]) by mx1.freebsd.org (Postfix) with ESMTP id C353A635 for ; Mon, 27 Oct 2014 19:14:06 +0000 (UTC) Received: from terraplane.org (ti0027a400-0787.bb.online.no [85.164.10.23]) by nmsh3.nsc.no (8.14.7/8.14.7) with ESMTP id s9RImAVH016272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 27 Oct 2014 19:48:11 +0100 (MET) Received: from terraplane.org (localhost [127.0.0.1]) by terraplane.org (8.14.5/8.14.5) with ESMTP id s9RIu08J032549 for ; Mon, 27 Oct 2014 19:56:00 +0100 (CET) (envelope-from rumrunner@terraplane.org) Received: (from rumrunner@localhost) by terraplane.org (8.14.5/8.13.8/Submit) id s9RIu04g032548 for freebsd-stable@freebsd.org; Mon, 27 Oct 2014 19:56:00 +0100 (CET) (envelope-from rumrunner) Date: Mon, 27 Oct 2014 19:56:00 +0100 From: Eivind Evensen To: freebsd-stable@freebsd.org Subject: XDM authorization key matches an existing client Message-ID: <20141027185600.GC32314@klump.hjerdalen.lokalnett> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 19:14:07 -0000 Hello. On FreeBSD elg.hjerdalen.lokalnett 10.0-STABLE FreeBSD 10.0-STABLE, I have a problem running certain X programs. They tell me: .milkytracker XDM authorization key matches an existing client!Couldn't initialize SDL: Couldn't open X11 display Using xhost +localhost works around the problem, but I'd rather not have to do that if avoidable. I can't really see anything in the options for sdl that seems to have an impact. Does anybody have any ideas where I can start to look? -- Eivind From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 19:25:06 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABC87F74 for ; Mon, 27 Oct 2014 19:25:06 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 89BAE7A6 for ; Mon, 27 Oct 2014 19:25:05 +0000 (UTC) Received: from [10.10.1.196] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by webmail2.jnielsen.net (8.14.9/8.14.9) with ESMTP id s9RJOuKl084190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Oct 2014 13:24:59 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host office.betterlinux.com [199.58.199.60] claimed to be [10.10.1.196] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: XDM authorization key matches an existing client From: John Nielsen In-Reply-To: <20141027185600.GC32314@klump.hjerdalen.lokalnett> Date: Mon, 27 Oct 2014 13:24:55 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20141027185600.GC32314@klump.hjerdalen.lokalnett> To: Eivind Evensen X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 19:25:06 -0000 On Oct 27, 2014, at 12:56 PM, Eivind Evensen = wrote: >=20 > Hello. On FreeBSD elg.hjerdalen.lokalnett 10.0-STABLE FreeBSD = 10.0-STABLE, > I have a problem running certain X programs. >=20 > They tell me: > .milkytracker > XDM authorization key matches an existing client!Couldn't initialize = SDL: > Couldn't open X11 display >=20 >=20 > Using xhost +localhost works around the problem, but I'd rather not > have to do that if avoidable. >=20 > I can't really see anything in the options for sdl that seems to > have an impact. Does anybody have any ideas where I can start to look? I had a similar (IIRC) problem recently. Try appending DisplayManager*authName: MIT-MAGIC-COOKIE-1 to /usr/local/lib/X11/xdm/xdm-config and restart xdm and your session. = That disables the XDM-AUTHORIZATION-1 authentication which, in my case, = solved the problem. JN From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 19:58:56 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B83839ED; Mon, 27 Oct 2014 19:58:56 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 529E9B25; Mon, 27 Oct 2014 19:58:55 +0000 (UTC) Received: from [192.168.178.20] ([93.134.92.151]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MD9NE-1Xsjv20Xue-00GbCg; Mon, 27 Oct 2014 20:58:48 +0100 Message-ID: <544EA3F6.9040602@gmx.de> Date: Mon, 27 Oct 2014 20:58:46 +0100 From: =?UTF-8?B?Q2Fyc3RlbiBCw6Rja2Vy?= User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= , freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:fOR9ytE+NzqV0fMGvzQXGNdj+lccaT7IeHvDDN7Zeu+PBmlHy4i a34g3xKpaWixXfLZMVEHd0ztJZj4J3zOrir9jxU/1t57QymMBO+h3c/D2iFHYVjZCW8jbS+ kBO1FiEaheNq0gYJ4+MY/b/QZI/0rOkjaSMsfba5bDmce+8+k+tI87koGFQfSmjurlwTUPR /vl2csZvENjORJ8bssTjQ== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 19:58:56 -0000 Works fine for Radeon HD 6850M. Thanks! Am 27.10.2014 um 10:26 schrieb Jean-SĂŠbastien PĂŠdron: > Hi! > > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. The reason is that 7.4.0 was crashing for several users, so > we want to be sure it's fixed in 7.5.0. > > Here's patch: > https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.patch > > To apply it: > cd /usr/ports > patch -p1 < /path/to/ports-xf86-video-ati-7.5.0.patch > > Then update x11-drivers/xf86-video-ati with your method of choice. > > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. > > When you're finished, you may restore your vanilla ports tree: > cd /usr/ports > patch -p1 -R < /path/to/ports-xf86-video-ati-7.5.0.patch > find x11-drivers/xf86-video-ati -name "*.orig" -delete > > Thank you for your help! > From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 20:16:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDF0DFC for ; Mon, 27 Oct 2014 20:16:39 +0000 (UTC) Received: from nmsh3.e.nsc.no (nmsh3.e.nsc.no [193.213.121.74]) by mx1.freebsd.org (Postfix) with ESMTP id 28150D5C for ; Mon, 27 Oct 2014 20:16:38 +0000 (UTC) Received: from terraplane.org (ti0027a400-0787.bb.online.no [85.164.10.23]) by nmsh3.nsc.no (8.14.7/8.14.7) with ESMTP id s9RKGaaS011592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Oct 2014 21:16:37 +0100 (MET) Received: from terraplane.org (localhost [127.0.0.1]) by terraplane.org (8.14.5/8.14.5) with ESMTP id s9RKOQFT032965; Mon, 27 Oct 2014 21:24:26 +0100 (CET) (envelope-from rumrunner@terraplane.org) Received: (from rumrunner@localhost) by terraplane.org (8.14.5/8.13.8/Submit) id s9RKOQsL032964; Mon, 27 Oct 2014 21:24:26 +0100 (CET) (envelope-from rumrunner) Date: Mon, 27 Oct 2014 21:24:26 +0100 From: Eivind Evensen To: John Nielsen Subject: Re: XDM authorization key matches an existing client Message-ID: <20141027202426.GA32910@klump.hjerdalen.lokalnett> References: <20141027185600.GC32314@klump.hjerdalen.lokalnett> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 20:16:39 -0000 On Mon, Oct 27, 2014 at 01:24:55PM -0600, John Nielsen wrote: > On Oct 27, 2014, at 12:56 PM, Eivind Evensen wrote: > > > > Hello. On FreeBSD elg.hjerdalen.lokalnett 10.0-STABLE FreeBSD 10.0-STABLE, > > I have a problem running certain X programs. > > > > They tell me: > > .milkytracker > > XDM authorization key matches an existing client!Couldn't initialize SDL: > > Couldn't open X11 display > > > > > > Using xhost +localhost works around the problem, but I'd rather not > > have to do that if avoidable. > > > > I can't really see anything in the options for sdl that seems to > > have an impact. Does anybody have any ideas where I can start to look? > > I had a similar (IIRC) problem recently. Try appending > DisplayManager*authName: MIT-MAGIC-COOKIE-1 > to /usr/local/lib/X11/xdm/xdm-config and restart xdm and your session. > That disables the XDM-AUTHORIZATION-1 authentication which, in my case, > solved the problem. Thank you, that solves the problem here aswell. I didn't make the connection between the section describing this setting in man xdm and my problem. Eivind > JN From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 21:33:06 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1D6163D; Mon, 27 Oct 2014 21:33:06 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 967E0832; Mon, 27 Oct 2014 21:33:06 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9RLX5OW014643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Oct 2014 15:33:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9RLX5cF014640; Mon, 27 Oct 2014 15:33:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 27 Oct 2014 15:33:05 -0600 (MDT) From: Warren Block To: =?ISO-8859-15?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Message-ID: References: <544E0FC8.8090605@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 27 Oct 2014 15:33:05 -0600 (MDT) Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 21:33:07 -0000 On Mon, 27 Oct 2014, Jean-SĂŠbastien PĂŠdron wrote: > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. Working here on a Radeon 5750. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 22:12:52 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by hub.freebsd.org (Postfix) with ESMTP id 5C64D6BD; Mon, 27 Oct 2014 22:12:51 +0000 (UTC) Message-ID: <544EC35A.2050401@FreeBSD.org> Date: Mon, 27 Oct 2014 18:12:42 -0400 From: Jung-uk Kim User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= , freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 22:12:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-27 05:26:32 -0400, Jean-sĂŠbastien PĂŠdron wrote: > What we're especially looking for is report of successful or > failed startup of the X server. With 7.4.0, the server would crash > during startup. But with 7.5.0, none of us could reproduce the > problem. Working fine with Radeon HD 4650 (RV730). Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUTsNVAAoJEHyflib82/FG7yEH/2gGETWn7ho4q9c2TIOF9ELW dA9JlCmG09ZZRY4R3sr3LpwmxFFm3h/nRclbWnn5QuPTTI/1d3tNRHLcV0bw8ax4 Ck7/nPwwMOLSS2muE6SrHNWvO39x8OzsTylLiJEYDoePUkmrHCOyR7DX4zh+Rr4J JU2bKOX9rFTSE36z+818mDltqwL+r8m7uFgDWkol4eL48Iu+LluGw/IKPjQzX7C1 9ZAst5X1lUKjU+hzRyfTRt5zkkcQOHgbSHy0S+qmZ8XD8lcalsjN3/27If9z7E4u DVtLFhlhocQNF8IUrGQRmDn8k19/0JBxnn8MYcTrO7rAeGJYqZx+I0o88YcsxT0= =cPcN -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 22:18:06 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD64C91D for ; Mon, 27 Oct 2014 22:18:06 +0000 (UTC) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailhost.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 72227CB3 for ; Mon, 27 Oct 2014 22:18:06 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 2FB24B8090; Mon, 27 Oct 2014 23:18:03 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id 1B90C28494; Mon, 27 Oct 2014 23:18:03 +0100 (CET) Date: Mon, 27 Oct 2014 23:18:03 +0100 From: Jilles Tjoelker To: Eivind Evensen Subject: Re: XDM authorization key matches an existing client Message-ID: <20141027221802.GA32726@stack.nl> References: <20141027185600.GC32314@klump.hjerdalen.lokalnett> <20141027202426.GA32910@klump.hjerdalen.lokalnett> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141027202426.GA32910@klump.hjerdalen.lokalnett> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 22:18:06 -0000 On Mon, Oct 27, 2014 at 09:24:26PM +0100, Eivind Evensen wrote: > On Mon, Oct 27, 2014 at 01:24:55PM -0600, John Nielsen wrote: > > On Oct 27, 2014, at 12:56 PM, Eivind Evensen wrote: > > > Hello. On FreeBSD elg.hjerdalen.lokalnett 10.0-STABLE FreeBSD 10.0-STABLE, > > > I have a problem running certain X programs. > > > They tell me: > > > .milkytracker > > > XDM authorization key matches an existing client!Couldn't initialize SDL: > > > Couldn't open X11 display > > > Using xhost +localhost works around the problem, but I'd rather not > > > have to do that if avoidable. > > > I can't really see anything in the options for sdl that seems to > > > have an impact. Does anybody have any ideas where I can start to look? > > I had a similar (IIRC) problem recently. Try appending > > DisplayManager*authName: MIT-MAGIC-COOKIE-1 > > to /usr/local/lib/X11/xdm/xdm-config and restart xdm and your session. > > That disables the XDM-AUTHORIZATION-1 authentication which, in my case, > > solved the problem. > Thank you, that solves the problem here aswell. I didn't make the connection > between the section describing this setting in man xdm and my problem. In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154502 I proposed to compile xdm without XDM-AUTHORIZATION-1 at all (configure --disable-xdm-auth). There is no real benefit to XDM-AUTHORIZATION-1 and it sometimes breaks things (most annoyingly, it may break logging in). Debian did the same thing years ago. -- Jilles Tjoelker From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 00:36:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E63E4AD for ; Tue, 28 Oct 2014 00:36:59 +0000 (UTC) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA3F0EC2 for ; Tue, 28 Oct 2014 00:36:59 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id bj1so2968602pad.1 for ; Mon, 27 Oct 2014 17:36:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=GxKo1lTLbuv8VUsz0z9m+4BnfvH+58U4ppuNnNotDyI=; b=YPVUF1AeAu8/qZXwTCtWQsprZDZdZceFehBGxE4evzUvGSoo1SUjcSGVysD2qPNCK0 G3shT7EYs5oBYOirzBAn/IRLtNhc5dt+TetUGodIgYjRqX4vYIKwW1BOyXsle6x18SUI BCt5S2KdKoXJZLNDpNrNNL+nPnOMFLx5mEemOmqKFBXTjdKtZ0G0NiZ0ScrhUkG8VLDY rTPebjKlqIq329EdyHg8iZwjcV3aWZ0ajG6c97uiGHGV7obNKGNWBZewNoxL+6KbFv6h BUdPL6noeIkTicFVfxCsNqWD53L05PiOSWIfwaTWFz2j/a1aATnqcvqSKR2QbKBsjWrz FlBg== X-Received: by 10.66.194.102 with SMTP id hv6mr27415547pac.109.1414456619305; Mon, 27 Oct 2014 17:36:59 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id o4sm682pdj.2.2014.10.27.17.36.55 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 27 Oct 2014 17:36:57 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 28 Oct 2014 09:36:48 +0900 Date: Tue, 28 Oct 2014 09:36:48 +0900 To: Alnis Morics Subject: Re: "msk0: watchdog timeout" still present in 10.1-RC2 Message-ID: <20141028003648.GA1054@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <543FD1BB.9010501@gmail.com> <544E2E16.9020008@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <544E2E16.9020008@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 00:37:00 -0000 On Mon, Oct 27, 2014 at 01:35:50PM +0200, Alnis Morics wrote: > For me, this problem has gone away in RC3 (10.1-RC3 FreeBSD 10.1-RC3 #0 > r273437: Tue Oct 21 23:55:15 UTC 2014 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64) I hope > it will stay that way in 10.1-RELEASE... There was no code change for msk(4) so other changes in RC3 may have addressed it. > > On 10/16/2014 17:10, Alnis Morics wrote: > >Hello, > > > >Several months ago we were talking about Marvell NIC not working, and > >the problem remained unsolved. So far, I have experienced it only in > >FreeBSD 10 (no problem in 9.X-RELEASE or 11-CURRENT), and only in > >amd64. So I hoped in 10.1 it would be solved but no: suffice to scp a > >5MB file through this interface, and the "watchdog timeout" is there. > > > >uname -a: > >FreeBSD myhost.mydomain.tld 10.1-RC2 FreeBSD 10.1-RC2 #0 r272876: Fri > >Oct 10 01:12:21 UTC 2014 > >root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > >pciconf -lv: > >[..] > >mskc0@pci0:9:0:0: class=0x020000 card=0xc072144d chip=0x435411ab > >rev=0x00 hdr=0x00 > > vendor = 'Marvell Technology Group Ltd.' > > device = '88E8040 PCI-E Fast Ethernet Controller' > > class = network > > subclass = ethernet > > > >_____ > >Alnis > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 01:54:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0829DC2; Tue, 28 Oct 2014 01:54:12 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01A77855; Tue, 28 Oct 2014 01:54:10 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id ex7so202180wid.16 for ; Mon, 27 Oct 2014 18:54:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TGcQi6dautUewWf+4b2EOUAVC689nWl/gygwPdWWMaQ=; b=hL949uJCHN/8dkcOBfMIVdw/i9+lHJGD8q7ksdLoEoG6fWnEPEoehhfIhPjPArQuxY qHO2ZdwTXKCRFtMSbvF31iGb2a3c/BPpC0c6ULyKZ74MAgzoWXwZAfJTzLgLKP2KTfLe wRuvkH7k1WLbUI/Gstmx6NgNWnFsYlicqjXvqRNoBXyOrSqpuOFpdQf2wXqhv6vNvh+0 LledeMd1VuvUs7QTP4ObeZ1tifXI040YDR8As6tjjBOS9gw7HVduV82gLZDL05bXEtxe 9YISANnRJVMDg/anQ5s2jUYAlGKSp9oacRasu2OYYQ0DuTV2W9C7rtGSyRbghJ7Hl8sn fI+Q== X-Received: by 10.180.149.169 with SMTP id ub9mr893192wib.73.1414461249355; Mon, 27 Oct 2014 18:54:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Mon, 27 Oct 2014 18:53:49 -0700 (PDT) In-Reply-To: <544EC35A.2050401@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 01:53:49 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: Jung-uk Kim Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List , =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 01:54:12 -0000 Not working for me on current. dmesg: http://pastebin.com/N49hZnGS Xorg.0.log: http://pastebin.com/Mn3svFjC Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Mon, Oct 27, 2014 at 10:12 PM, Jung-uk Kim wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2014-10-27 05:26:32 -0400, Jean-s=C3=A9bastien P=C3=A9dron wrote: > > What we're especially looking for is report of successful or > > failed startup of the X server. With 7.4.0, the server would crash > > during startup. But with 7.5.0, none of us could reproduce the > > problem. > > Working fine with Radeon HD 4650 (RV730). > > Jung-uk Kim > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBAgAGBQJUTsNVAAoJEHyflib82/FG7yEH/2gGETWn7ho4q9c2TIOF9ELW > dA9JlCmG09ZZRY4R3sr3LpwmxFFm3h/nRclbWnn5QuPTTI/1d3tNRHLcV0bw8ax4 > Ck7/nPwwMOLSS2muE6SrHNWvO39x8OzsTylLiJEYDoePUkmrHCOyR7DX4zh+Rr4J > JU2bKOX9rFTSE36z+818mDltqwL+r8m7uFgDWkol4eL48Iu+LluGw/IKPjQzX7C1 > 9ZAst5X1lUKjU+hzRyfTRt5zkkcQOHgbSHy0S+qmZ8XD8lcalsjN3/27If9z7E4u > DVtLFhlhocQNF8IUrGQRmDn8k19/0JBxnn8MYcTrO7rAeGJYqZx+I0o88YcsxT0=3D > =3DcPcN > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 02:59:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4062CCC5; Tue, 28 Oct 2014 02:59:40 +0000 (UTC) Received: from mail.samsco.org (suzy.samsco.org [168.103.85.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18842D8E; Tue, 28 Oct 2014 02:59:39 +0000 (UTC) Received: from localhost (localhost [192.168.254.3]) by mail.samsco.org (Postfix) with ESMTP id D042E15C1A688; Tue, 28 Oct 2014 02:51:30 +0000 (UTC) Received: from mail.samsco.org ([192.168.254.3]) by localhost (mail.samsco.org [192.168.254.3]) (maiad, port 10024) with ESMTP id 49447-03; Tue, 28 Oct 2014 02:51:30 +0000 (UTC) Received: from [10.5.50.47] (173-14-63-77-Michigan.hfc.comcastbusiness.net [173.14.63.77]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: scottl@samsco.org) by mail.samsco.org (Postfix) with ESMTPSA id 4097415C1867C; Tue, 28 Oct 2014 02:51:30 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: File system issues From: Scott Long In-Reply-To: <544BC863.2040607@bsdforen.de> Date: Mon, 27 Oct 2014 22:50:14 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <544BC863.2040607@bsdforen.de> To: Dominic Fandrey X-Mailer: Apple Mail (2.1990.1) Cc: Alexander Motin , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 02:59:40 -0000 > On Oct 25, 2014, at 11:57 AM, Dominic Fandrey = wrote: >=20 > Two or 3 days ago, after an update to stable/10 my UFS file system > started acting weird. I have freezes and files disappearing from the > system. >=20 > The first time that happened SU+J failed me. I.e. I went into single > user mode and on the second fsck run it would still find errors that > weren't successfully corrected due to the journal. That was the first > time with the Samsung 840 PRO SSD. >=20 > I rebuilt kernel/world, turned off journaling and rebooted, but the > problems persisted. Yesterday I updated again: > FreeBSD AprilRyan.norad 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 = r273588: Fri Oct 24 17:18:14 CEST 2014 = root@AprilRyan.norad:/usr/obj/S403/amd64/usr/src/sys/S403 amd64 >=20 > Today I suddenly couldn't use sysctl any more. It turned out /sbin was > suddenly empty. A couple of minutes later the system froze. After the > hard reset it came up like this (shortened to relevant bits): > http://pastebin.com/kXLtg3JR >=20 > As you can see I'm using geli for everything but /boot. After a hard > reset I usually go into single user mode and run fsck twice (ever = since > I had some really bad experiences). >=20 > It doesn't come up clean, but what turns up in lost+found are just > files from the browser cache and /sbin is back. >=20 > What terrifies me (apart from disappearing files) is what happens > after the system goes through a suspend and resume cycle, starting > at line 258 in the pastebin. The harddisk comes back up with new > errors! >=20 > I cannot pin down which version was the one last working for me, but > it's uname already said something about 10.1-PRERELEASE. >=20 Your symptoms sound very much like what we experienced with a recent merge of code to 10-STABLE. We don=E2=80=99t completely understand the = problem, but backing out r273272 avoids the problem, though it=E2=80=99s = suspected that there=E2=80=99s a bigger problem. r273638 in HEAD backs out everything suspect, and = we=E2=80=99ve been running for several days now with no problems with it. I believe = that it=E2=80=99ll be committed to 10-STABLE in the next day or two. Scott From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 07:13:10 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7979FE5B for ; Tue, 28 Oct 2014 07:13:10 +0000 (UTC) Received: from nmsh4.e.nsc.no (nmsh4.e.nsc.no [193.213.121.75]) by mx1.freebsd.org (Postfix) with ESMTP id C6108D4D for ; Tue, 28 Oct 2014 07:13:08 +0000 (UTC) Received: from terraplane.org (ti0027a400-0787.bb.online.no [85.164.10.23]) by nmsh4.nsc.no (8.14.7/8.14.7) with ESMTP id s9S6cE4Z003701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Oct 2014 07:38:15 +0100 (MET) Received: from terraplane.org (localhost [127.0.0.1]) by terraplane.org (8.14.5/8.14.5) with ESMTP id s9S6k6cb035696; Tue, 28 Oct 2014 07:46:06 +0100 (CET) (envelope-from rumrunner@terraplane.org) Received: (from rumrunner@localhost) by terraplane.org (8.14.5/8.13.8/Submit) id s9S6k5Vs035695; Tue, 28 Oct 2014 07:46:06 +0100 (CET) (envelope-from rumrunner) Date: Tue, 28 Oct 2014 07:46:05 +0100 From: Eivind Evensen To: Jilles Tjoelker Subject: Re: XDM authorization key matches an existing client Message-ID: <20141028064605.GB32910@klump.hjerdalen.lokalnett> References: <20141027185600.GC32314@klump.hjerdalen.lokalnett> <20141027202426.GA32910@klump.hjerdalen.lokalnett> <20141027221802.GA32726@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141027221802.GA32726@stack.nl> Cc: freebsd-stable@freebsd.org, Eivind Evensen X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 07:13:10 -0000 On Mon, Oct 27, 2014 at 11:18:03PM +0100, Jilles Tjoelker wrote: > On Mon, Oct 27, 2014 at 09:24:26PM +0100, Eivind Evensen wrote: > > On Mon, Oct 27, 2014 at 01:24:55PM -0600, John Nielsen wrote: > > > On Oct 27, 2014, at 12:56 PM, Eivind Evensen wrote: > > > > > Hello. On FreeBSD elg.hjerdalen.lokalnett 10.0-STABLE FreeBSD 10.0-STABLE, > > > > I have a problem running certain X programs. > > > > > They tell me: > > > > .milkytracker > > > > XDM authorization key matches an existing client!Couldn't initialize SDL: > > > > Couldn't open X11 display > > > > > Using xhost +localhost works around the problem, but I'd rather not > > > > have to do that if avoidable. > > > > > I can't really see anything in the options for sdl that seems to > > > > have an impact. Does anybody have any ideas where I can start to look? > > > > I had a similar (IIRC) problem recently. Try appending > > > DisplayManager*authName: MIT-MAGIC-COOKIE-1 > > > to /usr/local/lib/X11/xdm/xdm-config and restart xdm and your session. > > > That disables the XDM-AUTHORIZATION-1 authentication which, in my case, > > > solved the problem. > > > Thank you, that solves the problem here aswell. I didn't make the connection > > between the section describing this setting in man xdm and my problem. > > In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154502 I proposed > to compile xdm without XDM-AUTHORIZATION-1 at all (configure > --disable-xdm-auth). There is no real benefit to XDM-AUTHORIZATION-1 and > it sometimes breaks things (most annoyingly, it may break logging in). > Debian did the same thing years ago. It sounds to me that that would be a win. Or at the least, if there's ever hope XDM_AUTHORIZATION-1 to give some value, write about it in the ports/package readmes so it's a bit simpler to know what to do. Eivind > Jilles Tjoelker From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 09:08:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00A878EF; Tue, 28 Oct 2014 09:08:37 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BA9DBA8; Tue, 28 Oct 2014 09:08:37 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id d1so5071015wiv.5 for ; Tue, 28 Oct 2014 02:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3F5jwNAeaYpSazSj2lLlJ3wfWLOxFIonpuB4EJIOd7Q=; b=C6/qoOHN4l0MoqexoKPsMGsnQDcghdmlDzmFLcyzUPUvpJVr8VnkEZUVEUGp2Xljaa a7OzEF2QMVlry4KY5K2fJHhLRqWjm4UvFzv9RAX0M5bZhYoJpwKBEIQDUD7TU1wtLR9M Ygop5IsGzJS2pjz61EK1mrreWjHfZOcnrn/98FENtN0MubKy1dHms1ALjPSlR5237TUY z4pjmN5pdF1lp51vWG+lAxiIV1JaciFZdn6lWYwNrsijkW37G4syv4/b17VHCetABeUn Jm+eNHmdvIv2UD0J7EYYcElXrODSJC5A4EtcS+MmLicvDsONL6DepTqCKxQV9grlf8CU kTEA== MIME-Version: 1.0 X-Received: by 10.181.13.208 with SMTP id fa16mr26127137wid.61.1414487315692; Tue, 28 Oct 2014 02:08:35 -0700 (PDT) Received: by 10.194.223.1 with HTTP; Tue, 28 Oct 2014 02:08:35 -0700 (PDT) Date: Tue, 28 Oct 2014 10:08:35 +0100 Message-ID: Subject: Error in frontpage From: Cristiano Deana To: freebsd-doc@FreeBSD.org, FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 09:08:38 -0000 Hi, from today(?) in www.freebsd.org names of releases in the "LATEST RELEASES" section are missing: Code:

LATEST RELEASES

Screenshot: http://i.imgur.com/gNz8bm2.png -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 09:29:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50BF0DD5; Tue, 28 Oct 2014 09:29:50 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A541D5B; Tue, 28 Oct 2014 09:29:50 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xj363-00082s-Fw; Tue, 28 Oct 2014 10:29:47 +0100 Message-ID: <544F61F9.6040408@FreeBSD.org> Date: Tue, 28 Oct 2014 10:29:29 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="S18FHNAIiDGIp3CWijRgiIlFH8r6itgcu" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 09:29:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --S18FHNAIiDGIp3CWijRgiIlFH8r6itgcu Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 02:53, Miguel Clara wrote: > Not working for me on current. >=20 > dmesg: http://pastebin.com/N49hZnGS Could you please rebuild x11-servers/xorg-server and x11-drivers/xf86-video-ati like this: make WITH_DEBUG=3D1 all deinstall install Then, run Xorg from gdb (pkg install gdb) as root: gdb78 /usr/local/bin/Xorg At the "(gdb)" prompt, you can type the "r" command to execute Xorg. gdb will tell you if Xorg crashed or terminated normally. If it crashed, run the "bt" command at the (gdb) prompt and post your whole gdb session. Thank you! --=20 Jean-S=C3=A9bastien P=C3=A9dron --S18FHNAIiDGIp3CWijRgiIlFH8r6itgcu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT2ILXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM49QQAMjsMUVlW/S6PoePaBfqm+9v weg+5yi8QAIk4yagZOREnOw3wo1hpWUcZwSsCXJF4BZNdPjz2KQ8zMUPuTu4yI0Y xlbvlwuHVCuzvG57KBNlVYeQAtf2Q8Wlmj6UVRkStYcfDoLFFnAXBXpUnsi+fcVb /B8fba2oy8RZze7v0vzjwULNT9Wyzcrr9MRyZMwf4ARPZU6mBVqW+Y3Jup0QjRRy pQoWIy3vQsRJ4NOrGgQP5x9ZhoErpaamtNdrO/b275J9k1bt45flcQAJR6+RPqnM kxOoqfGUfUe6DOED4mMZqkYbvX79cPRyJROthhplv/9vjWbca07kjP6tc2gbiVjM 6mE0aTxC9ZMGaaPK2dDN8Apu8uiFcMfBolju72aJwHGGOtZw0qauilZ3jKrpGFOI tOhqP22CwgQIc6MWOgN/zMQW1CTcOr7+o3BemWFetHLxtnKh//w3U7sFErDqBL1Q 4/9KgIqfXV43SgsNXr/kyj+LeJVrzcPfO4uc0I0/b4pSArq2LkSfdagnG7YQ5xoc U45/eVjWuRJJglYWvxqYTLd5NEJ+I2S4RrgjFYSNMKFhUbKLma8sd13stzenIGBy pKFcgWMZxwQM5ZCNu7rJQel/jGnYekGid1Tch+ipZOmrSRCdgLkWnUOrQZ8U+nbW 2RWJwytvPaupy8+JuWS+ =p1Hx -----END PGP SIGNATURE----- --S18FHNAIiDGIp3CWijRgiIlFH8r6itgcu-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 10:10:42 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B82AF912 for ; Tue, 28 Oct 2014 10:10:42 +0000 (UTC) Received: from mail-yh0-f51.google.com (mail-yh0-f51.google.com [209.85.213.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E5AE1F7 for ; Tue, 28 Oct 2014 10:10:41 +0000 (UTC) Received: by mail-yh0-f51.google.com with SMTP id c41so141456yho.10 for ; Tue, 28 Oct 2014 03:10:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bXLSXi+zA1VZTwLWs0zzpWYEoNM5j5yEf/x179+2LQk=; b=CWYwGmcJFQFZpU7Z4Emio7kT6E6nIxMhTUSYV5a0k/s+mJoHtS0HbZdawLp8X5BE/a e3M/0yC0htZT3jXjImp+yNm3/CLOVLqb1JqnZlKrFuIxdtVThco9vBOrqZLjbJVLQvMf mrHbDEp366ZpvMwbgC7CgZtoO5UDRG0M8z8tUZb88RwcMN+jlRNCPm1CiHXYkvlXrUF0 gbquaYI8j1qNmQPG3wDWbkjBCAKBqn/FwwWn45jEAaE6t1+JUEG3UEmVUvGGFKZqGnPK u1IEToRNYHU8QUrUKFozv+5gtXrKeIrZBSLTmBZVum6qYt5brw1SAgXV3dcrQG/tui2O 1O/g== X-Gm-Message-State: ALoCoQmgNLgQ8q5SgTOlsvIaA9lPDq/VHZ07/SpmDU8lOnCh4HcccZdTI98XhrpreIbnVZYHiiqq MIME-Version: 1.0 X-Received: by 10.170.204.84 with SMTP id v81mr2000062yke.115.1414491040557; Tue, 28 Oct 2014 03:10:40 -0700 (PDT) Received: by 10.170.46.203 with HTTP; Tue, 28 Oct 2014 03:10:40 -0700 (PDT) X-Originating-IP: [62.165.198.134] In-Reply-To: <544F61F9.6040408@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> Date: Tue, 28 Oct 2014 11:10:40 +0100 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 From: Oliver Pinter To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org, Miguel Clara X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 10:10:42 -0000 On Tue, Oct 28, 2014 at 10:29 AM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 28.10.2014 02:53, Miguel Clara wrote: >> Not working for me on current. >> >> dmesg: http://pastebin.com/N49hZnGS > > Could you please rebuild x11-servers/xorg-server and > x11-drivers/xf86-video-ati like this: > make WITH_DEBUG=3D1 all deinstall install > > Then, run Xorg from gdb (pkg install gdb) as root: > gdb78 /usr/local/bin/Xorg > > At the "(gdb)" prompt, you can type the "r" command to execute Xorg. gdb > will tell you if Xorg crashed or terminated normally. > > If it crashed, run the "bt" command at the (gdb) prompt and post your > whole gdb session. > > Thank you! Btw, It's possible to exists a coredump in / directory, namely Xorg.core. > > -- > Jean-S=C3=A9bastien P=C3=A9dron > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 11:12:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D434894; Tue, 28 Oct 2014 11:12:52 +0000 (UTC) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A103ABF; Tue, 28 Oct 2014 11:12:51 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id E03469DF1A9; Tue, 28 Oct 2014 12:12:46 +0100 (CET) Subject: Re: File system issues Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Borja Marcos In-Reply-To: Date: Tue, 28 Oct 2014 12:12:45 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5640FB23-4ABA-415D-B9BA-C0835978EB0D@sarenet.es> References: <544BC863.2040607@bsdforen.de> To: Scott Long X-Mailer: Apple Mail (2.1283) Cc: Dominic Fandrey , Alexander Motin , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 11:12:52 -0000 On Oct 28, 2014, at 3:50 AM, Scott Long wrote: > Your symptoms sound very much like what we experienced with a recent > merge of code to 10-STABLE. We don=92t completely understand the = problem, > but backing out r273272 avoids the problem, though it=92s suspected = that there=92s > a bigger problem. r273638 in HEAD backs out everything suspect, and = we=92ve > been running for several days now with no problems with it. I believe = that it=92ll > be committed to 10-STABLE in the next day or two. Will it be committed to RELENG-10.1 as well?=20 Borja. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 14:02:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86F9B33F for ; Tue, 28 Oct 2014 14:02:59 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AB4FF4B for ; Tue, 28 Oct 2014 14:02:58 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id w7so672266lbi.12 for ; Tue, 28 Oct 2014 07:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dgpm6NdLSjjaoxT+MrgnN/huA8ZAd1f+6A7+Jb4R+UI=; b=o9JrYwb7IINztzZ37zmlZGBHXYnOQ+hcJqloswRHwwYvgMAafIMLjTQD5stBYboVgK R6WW73vOLWUjOPWblqaT6HVR4lVtbF/nzhaXDQ4OWm6p9ssk26LE5IPXg66EPEkGd7P5 UF5s4dF+nMGG3p7GXzvQDPQcLjghczWbbGs+QGwl1IqcKTDEt8Sb9xxA4R0dFs/zLkmC ndr91rwBIZJSvs/Z67OcKGWszjncplXb/60uL8b3CZoPai0/XhUPJFClw8tmAUe2Z/Kh IgSjmVy9+NJOdhrQ6PuWf4ORXg2sF8uwNWoB0BAXh/mMbiTP1THU91qZ4V+UYEMKyy5y Hf+Q== X-Received: by 10.112.63.70 with SMTP id e6mr4075882lbs.93.1414504976776; Tue, 28 Oct 2014 07:02:56 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([134.249.139.101]) by mx.google.com with ESMTPSA id f6sm654493lbh.10.2014.10.28.07.02.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Oct 2014 07:02:55 -0700 (PDT) Sender: Alexander Motin Message-ID: <544FA20D.9020303@FreeBSD.org> Date: Tue, 28 Oct 2014 16:02:53 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Borja Marcos , Scott Long Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <5640FB23-4ABA-415D-B9BA-C0835978EB0D@sarenet.es> In-Reply-To: <5640FB23-4ABA-415D-B9BA-C0835978EB0D@sarenet.es> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: Dominic Fandrey , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 14:02:59 -0000 On 28.10.2014 13:12, Borja Marcos wrote: > On Oct 28, 2014, at 3:50 AM, Scott Long wrote: > >> Your symptoms sound very much like what we experienced with a recent >> merge of code to 10-STABLE. We don’t completely understand the problem, >> but backing out r273272 avoids the problem, though it’s suspected that there’s >> a bigger problem. r273638 in HEAD backs out everything suspect, and we’ve >> been running for several days now with no problems with it. I believe that it’ll >> be committed to 10-STABLE in the next day or two. > > Will it be committed to RELENG-10.1 as well? It is committed just now at r273776. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 14:13:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10CDE90C; Tue, 28 Oct 2014 14:13:46 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0499310A; Tue, 28 Oct 2014 14:13:44 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id f15so743857lbj.27 for ; Tue, 28 Oct 2014 07:13:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=A62QI7zRnbYkh+yKBIPtCCHon6PG1TQmosP8WtbGFEI=; b=S/bBeh8tOMMMZmG0kYDEI066GHBnIMj5KlpkBJYYj+cGJtN394XIO3eNZu4vDaKhJ/ BLWgeKr62AZdF6Xs01ATMkbAlF6XFh1u3e81jOqXZ2hntxkCXvGWEBrDnabqBtigx1E3 Bp761zyFRiZhEiXGpoJ0uCzxoNpu/xl6G+p986pJlQGxAbLXOjR86Jdrf7GboMVjmzVo wfnPebxGf/hXUjMgRhWRprJa9DnuDqVhUkJWYBKzF41Xm2Ceow/bmaRHQwjtT622rceM EcniN+Hmf8VQEJLbv6PARI5wSBzAScwQY5uqZqqxc4V9Xg+MK1GLBNFLFc/d1mp46T+E Re9g== X-Received: by 10.113.5.7 with SMTP id ci7mr4418546lbd.9.1414505622869; Tue, 28 Oct 2014 07:13:42 -0700 (PDT) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id v7sm653128lbp.44.2014.10.28.07.13.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Oct 2014 07:13:42 -0700 (PDT) From: Volodymyr Kostyrko X-Google-Original-From: Volodymyr Kostyrko Message-ID: <544FA494.9000605@b1t.name> Date: Tue, 28 Oct 2014 16:13:40 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= , freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 14:13:46 -0000 On 27.10.2014 11:26, Jean-SĂŠbastien PĂŠdron wrote: > Hi! > > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. The reason is that 7.4.0 was crashing for several users, so > we want to be sure it's fixed in 7.5.0. > > What we're especially looking for is report of successful or failed > startup of the X server. With 7.4.0, the server would crash during > startup. But with 7.5.0, none of us could reproduce the problem. kernel: drmn0: on vgapci0 Success, works like it should. -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 14:32:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC0081CB; Tue, 28 Oct 2014 14:32:59 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id AAF4B366; Tue, 28 Oct 2014 14:32:58 +0000 (UTC) Received: from AprilRyan.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 8768F8618E; Tue, 28 Oct 2014 15:32:44 +0100 (CET) Message-ID: <544FA907.4070003@bsdforen.de> Date: Tue, 28 Oct 2014 15:32:39 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ian Smith Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> <544CB063.3020002@bsdforen.de> <20141027042350.M74058@sola.nimnet.asn.au> <544D6628.60904@bsdforen.de> <20141027214537.X74058@sola.nimnet.asn.au> In-Reply-To: <20141027214537.X74058@sola.nimnet.asn.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 14:33:00 -0000 Hello, On 27/10/2014 15:07, Ian Smith wrote: > On Sun, 26 Oct 2014 22:22:48 +0100, Dominic Fandrey wrote: > > On 26/10/2014 18:37, Ian Smith wrote: > > > On Sun, 26 Oct 2014 09:27:15 +0100, Dominic Fandrey wrote: > > > > On 26/10/2014 07:36, Ian Smith wrote: > > > > > > > > But then, the general expectation that new users will want a linux-style > > > > > single / directory - sure, fine for VM use - cruels the potential to use > > > > > dump and restore anyway. It's a bit sad that this is still outstanding. > > > > > > > > You can use dump from anywhere in the file system by way of nullfs > > > > mounts. > > > > > > Thanks Dominic, I wasn't aware of that. Not that it makes up for not > > > being able to not newfs filesystems you want to keep, and in fstab, but > > > it's definitely worth exploring as a workaround. > > > > I have to withdraw my statement. I thought I had done it before, but I > > cannot get it to work. I suppose that leaves us with tar. > > I spent some time exploring trying to dump a nullfs-mounted (copy of) > /etc last night, to no avail. I finally managed to make a snapshot of > that with mksnap_ffs, mounted it as an md, but it turned out to be just > a snapshot of / and not dumpable anyway. I'm sorry for the false hope. :( -- 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-stable@FreeBSD.ORG Tue Oct 28 14:36:42 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19CEA4E7; Tue, 28 Oct 2014 14:36:42 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id CD5113A0; Tue, 28 Oct 2014 14:36:41 +0000 (UTC) Received: from AprilRyan.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id B28DB860F2; Tue, 28 Oct 2014 15:36:40 +0100 (CET) Message-ID: <544FA9F4.1040309@bsdforen.de> Date: Tue, 28 Oct 2014 15:36:36 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ian Lepore , Ronald Klop Subject: Re: File system issues References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <544C0DA3.1060201@bsdforen.de> <1414418314.17308.2.camel@revolution.hippie.lan> In-Reply-To: <1414418314.17308.2.camel@revolution.hippie.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 14:36:42 -0000 On 27/10/2014 14:58, Ian Lepore wrote: > On Mon, 2014-10-27 at 09:49 +0100, Ronald Klop wrote: >> On Sat, 25 Oct 2014 22:52:51 +0200, Dominic Fandrey >> wrote: >> >>> On 25/10/2014 20:36, Kurt Jaeger wrote: >>>> Hi! >>>> >>>>> Two or 3 days ago, after an update to stable/10 my UFS file system >>>>> started acting weird. I have freezes and files disappearing from the >>>>> system. >>>>> >>>>> The first time that happened SU+J failed me. >>>> >>>> I always disable journaling >>> >>> I think that's just a symptom here. The issue is stuff mysteriously >>> disappearing from my file system on a running system. >>> >>> >> >> Hi, >> >> Weird stuff. If you read the following mail thread there is a confirmed >> problem with fsck on ARM systems with disappearing files. >> http://lists.freebsd.org/pipermail/freebsd-arm/2014-September/009168.html >> It also states that the same problem does not occur on other platforms >> (and I can fsck my ARM systems usb-stick on a amd64 system successfully), >> but I thought it is worth mentioning. >> > > It seems unlikely to be related, but it would be easy to test: > > mdconfig -a -t malloc -s 64m > # assume that created unit 0 > newfs /dev/md0 > fsck -t ffs /dev/md0 > > If that reports errors, you've got the problem. If it doesn't, it's > some other problem. So far the problem exposed by the sequence above > happens only on one specific type of old low-end arm system; it hasn't > yet been reproduced on even other arm systems, let alone other arches. Thanks, I ran it and I didn't get any errors. By now I decided to implement desperate measures. dump -0;newfs;restore No more problems so far. I didn't have the spare space to make a complete FS image. :( So whatever the cause, it will remain undiscovered. 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-stable@FreeBSD.ORG Tue Oct 28 16:50:15 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F56114A; Tue, 28 Oct 2014 16:50:15 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CED675C; Tue, 28 Oct 2014 16:50:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s9SGKHDi094543; Wed, 29 Oct 2014 03:20:18 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 29 Oct 2014 03:20:17 +1100 (EST) From: Ian Smith To: Dominic Fandrey Subject: Re: File system issues In-Reply-To: <544FA907.4070003@bsdforen.de> Message-ID: <20141029031225.P74058@sola.nimnet.asn.au> References: <544BC863.2040607@bsdforen.de> <20141025183600.GG66862@home.opsec.eu> <50056B15-83F4-4524-995E-6486959C027C@orthanc.ca> <20141026170011.M74058@sola.nimnet.asn.au> <544CB063.3020002@bsdforen.de> <20141027042350.M74058@sola.nimnet.asn.au> <544D6628.60904@bsdforen.de> <20141027214537.X74058@sola.nimnet.asn.au> <544FA907.4070003@bsdforen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Adrian Chadd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 16:50:15 -0000 On Tue, 28 Oct 2014 15:32:39 +0100, Dominic Fandrey wrote: > I'm sorry for the false hope. :( No problem; as I said, I learned some new stuff; played with nullfs, reexplored dump(8) and mksnap_ffs(8) and did some overdue backups :) cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 18:33:53 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B0635AB; Tue, 28 Oct 2014 18:33:53 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 054BB34F; Tue, 28 Oct 2014 18:33:53 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjBaX-000EGX-0J; Tue, 28 Oct 2014 19:33:49 +0100 Message-ID: <544FE187.3030404@FreeBSD.org> Date: Tue, 28 Oct 2014 19:33:43 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara , Oliver Pinter Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NrPn1povSfwJPaQ9igJbJFIRVmLVKiHeH" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 18:33:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NrPn1povSfwJPaQ9igJbJFIRVmLVKiHeH Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 19:18, Miguel Clara wrote: > I should had that after rebooting the laptop, when it starts, with > should start "slim" and all I see is a mouse in the middle and a "promp= t > square" (not sure what to call it :P ) in the top left... The prompt square (I call it "text cursor" :) and the mouse are from vt(4), so it means the X server didn't acquire the display yet. When running Xorg alone, you should see nothing on the screen. In the dmesg and Xorg.log you posted previously, the card appears to have no CRTC or output connector: dmesg: No connectors reported connected with modes Does your computer have another video card, ie. an integrated one? Can you give more information about your hardware? > # gdb /usr/local/bin/Xorg=20 > ... > Starting program: /usr/local/bin/Xorg=20 > (no debugging symbols found)...(no debugging symbols found)... Can you rebuild x11-servers/xorg-server with WITH_DEBUG=3D1 too? --=20 Jean-S=C3=A9bastien P=C3=A9dron --NrPn1povSfwJPaQ9igJbJFIRVmLVKiHeH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT+GMXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMS+kP/1yb4iQMK6ya3BplRsJ1QISS 4tvLAH63ehQpQzZDzWd/4CFp5ilpMrZpJynsnboQFsc4DqZUgfUZRQOplM7IHnTX lEJWf6Yzif2/HRwme9R2z9WtLmSuUg8bJAoVGWtSbIJsoA/vcU3GNqyy7SK5eFtV cwMnXH9dTaUZYaG2pjGifoZTkNcvjLkzasurOfgAbQTqFlOYTYZabKIX98ycjNGC Rb1Icvs91EC+4A+rTzMZqzrSrg21rgiPv/k1nXweQJR7vkCSQ9A4yo6u2m0cpT9a RGW8xKSbSJ8CGBU7ybK7d+uPPhTPsXMcW/QiBobp35TXdKbxmlaz/Gq81GV1yj72 Zf/djyN4L+4l3CZTyBp8/IxoXkdZkUqFlzbwozSceksxeA1e+yg89dvUfz0gZ2V4 rW6WDiJDhcJDtmZzdEm8DvNipiIKxDCUv1RVKRdZ/Db6wBZluGBAjU1bVmvpoSgl 0R4mleUSvuCJP6RXOyVFIO8MTxI0WcT2IAnqGsWZUtkdE8vRjIeqig5QO8gkEtwE 3d6zVN0jTpSf64jJZ1DsZ7oTMuUVBxzw3bP2JrdjaZ2ylImJEoShTp9AJ5gr/qbD Xyd3nl1E3AvzZuy10QfUVabebfhd9XpK/3hLJAlAWO/2LtaCbn3mI5TbaWKUE1TB 0powHv4dwurPDb/7sL9D =APHP -----END PGP SIGNATURE----- --NrPn1povSfwJPaQ9igJbJFIRVmLVKiHeH-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 18:41:16 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19E16957; Tue, 28 Oct 2014 18:41:16 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C848627; Tue, 28 Oct 2014 18:41:15 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id q5so9669594wiv.0 for ; Tue, 28 Oct 2014 11:41:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FvPfJo2RMQm04iSjIg/ZQSjMoJZ1xY7W6/e4vb/OOTU=; b=A54lZyjNSyp1wwMIkCtQPfcwUSUeohJluR1EWRhCxlyv21RBCZ9+/Rx8BoZmwvB1oS 9dnlJ+3dRfriSrTi/oj6o7Ydalt/vlMBUyVmScnXo6wxAvU9V0xDbKrvayGBYs6ZDig4 Gd/Xhngn3p44ZACNvXYESrd1+P/ATEXZaLSVSkfvTRKmTp60Q6RbWw02v8ZmO6Gtu+Lp NQKRM+QdW4Ciz8+bk6YRV8VTRJFH1J7o1L3fHZL6vdIT3o2yUbttyixOEWh63UNZwWkE r+EQuFsrVPcNzMZl9tvXrqTRHqmJHkOXwduRIh/ivNbanyVMjinjn6Zac3vluk48Gs8+ Y4NQ== X-Received: by 10.180.104.198 with SMTP id gg6mr30771473wib.76.1414521673325; Tue, 28 Oct 2014 11:41:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 28 Oct 2014 11:40:53 -0700 (PDT) In-Reply-To: <544FE187.3030404@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 18:40:53 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List , Oliver Pinter X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 18:41:16 -0000 On Tue, Oct 28, 2014 at 6:33 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 28.10.2014 19:18, Miguel Clara wrote: > > I should had that after rebooting the laptop, when it starts, with > > should start "slim" and all I see is a mouse in the middle and a "promp= t > > square" (not sure what to call it :P ) in the top left... > > The prompt square (I call it "text cursor" :) and the mouse are from > vt(4), so it means the X server didn't acquire the display yet. When > running Xorg alone, you should see nothing on the screen. > > In the dmesg and Xorg.log you posted previously, the card appears to > have no CRTC or output connector: > dmesg: No connectors reported connected with modes > > Does your computer have another video card, ie. an integrated one? Can > you give more information about your hardware? > Yes, it does, and Intel card. pciconf -lv output: http://filebin.ca/1fJdai9k7d85/pciconf.txt > > # gdb /usr/local/bin/Xorg > > ... > > Starting program: /usr/local/bin/Xorg > > (no debugging symbols found)...(no debugging symbols found)... > > Can you rebuild x11-servers/xorg-server with WITH_DEBUG=3D1 too? > > Will do! > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 18:55:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 663D3D57; Tue, 28 Oct 2014 18:55:44 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1ECBB7B5; Tue, 28 Oct 2014 18:55:44 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjBvi-000EWA-BH; Tue, 28 Oct 2014 19:55:42 +0100 Message-ID: <544FE6AD.1030503@FreeBSD.org> Date: Tue, 28 Oct 2014 19:55:41 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="i0lEi9qVcKLT1a7Q1Miehbn7nKr2AordU" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 18:55:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --i0lEi9qVcKLT1a7Q1Miehbn7nKr2AordU Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 19:40, Miguel Clara wrote: >> Does your computer have another video card, ie. an integrated one? Can= >> you give more information about your hardware? >> >=20 > Yes, it does, and Intel card. >=20 > pciconf -lv output: http://filebin.ca/1fJdai9k7d85/pciconf.txt I assume you use the Intel card only? Before trying this update, did you have xf86-video-ati-7.2.0 installed? --=20 Jean-S=C3=A9bastien P=C3=A9dron --i0lEi9qVcKLT1a7Q1Miehbn7nKr2AordU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT+auXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMyIsQAI+2D73HepMCO8F/5Z01leFa 2iPxgH4pdK++kuyQ1VeoQUyYJV/h12dTzclnleUf9nepTXxUERxV4pJUMHu0I9zM T+nV0plNBfRNV1Q5pMjqRqZOYBojvqJQowbYfK1CTk2WA/XZnumvKICFNv2D2nn6 t477KnmqTri0I3A6ShVxG9gUPXdaTcZ7LDIRrXX1oyoUAQEarHcXPF/qPQ1LKo5j 49yxB8GSqlOJNZJJy+6i3y27Dl7BOGpk0adHXHMQ8MCte2uycn0wn2la3bjkt26A pkQGD8yN0gwj8C5AVxjODvqHwcqFbF3oDcVonz2OWBNmCh21XjjeoT2VSh9QlcMp OQemsJc/EjtM0yXvpJvUKHjSOId5/zX/1uPovc+JCVt+NcC25ZpVUnbpO8bMiSMl bJR1i15yRlQm7j6Ivwl1jpuUuDt0E3jDrkMaCD5qnjXnIj2Z0qCZclIMJEOq/L7E r6kAVivlRCe0hsa+3sFPtMJbOnOne5z2RLvCXKq76dwRBPFjwsI8t2xqAyTAie5L OpPMuakwWLwg9dvUPyWXbvmyG+pn3fzIBLyM1JFCgiMl5b1ggv/TuWyPtec7KkDx rM5/P+7f+b6HE6cnyNFL/Ntx1q+UpH42iRXmGQXIZbFRJEc4gyH9uUcmPfciDFwy TDbX9/TmwB07ijWvv7bn =1Qxm -----END PGP SIGNATURE----- --i0lEi9qVcKLT1a7Q1Miehbn7nKr2AordU-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:20:05 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B18F54BF for ; Tue, 28 Oct 2014 19:20:05 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 438FB9BB for ; Tue, 28 Oct 2014 19:20:05 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id n3so2647142wiv.8 for ; Tue, 28 Oct 2014 12:20:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/iX7ZuCDKcR8dul11lB+WuDkApq5OaUbI0YWLIChetk=; b=SSQLMVW6tWQDO96F4n+iSiWpNNtSxGyjyIu9tpNbhP4HYt9EL4MKm55tD756zeBs5V 31L8SviCyaDNRa1ixIuUIxZDqAA0fGg7nQXreNx5WI0W2vWjKRI0XkYI8+r3ZCybJqOu ntklIDLCysecnrlIU9XbFm7CL9jXNkPVeVilBd2u+PQLWdp7L9Y4nRPTZ9Jg2b2fl+qP lJ8XkJ9uMJTKWk0WLFd965nyX99jn58s/1yiswJhN8e6ks1XrwH0P2bd+ybD5xR15ty4 NpFx0ImDpeD+nAPWwT8it83McZYYz+POz+KMCXEZ6LHwGnCoJjWKXygGDsGDnQ0oNAQd C5pw== MIME-Version: 1.0 X-Received: by 10.194.216.162 with SMTP id or2mr6847303wjc.68.1414524002044; Tue, 28 Oct 2014 12:20:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Tue, 28 Oct 2014 12:20:01 -0700 (PDT) In-Reply-To: References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> Date: Tue, 28 Oct 2014 12:20:01 -0700 X-Google-Sender-Auth: 61AubFvqaS5UeO05OI452K-Jh0Q Message-ID: Subject: Re: Dump time issues From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable , Chris H X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:20:05 -0000 On 27 October 2014 11:09, Kevin Oberman wrote: >> I'm aware of two issues with SU+J, one of which is annoying and the other > is worse. > 1. If the journal is not fully written on power fail or some other reason, > you may need to do a full fsck of the volume and the behavior of the system > until this is done can be very unpredictable. > 2. You can't safely snapshot the system. This is what 'dump -L' does. This > means that some files dumped from a live FS may not be consistent (not > good!) or, if '-L' is used, the system may well hang. > > While I love the fast fsck times (2 or 3 seconds) after a crash, I also > question the default. Still, it may be a preferred choice be used for very > large file systems where a full fsck would take a very long time as long as > the risks are understood. For these systems, ZFS might be a better choice. > These arguments do NOT favor it being the default, IMHO. If people can reproduce SU+J problems then please file bugs. There have been some fixes with the journal handling over the last year or so and I haven't had this problem on -HEAD any longer, but it doesn't mean it's there. -adrian From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:20:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4FEF5B5; Tue, 28 Oct 2014 19:20:43 +0000 (UTC) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B02C79CC; Tue, 28 Oct 2014 19:20:42 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id n12so234177wgh.30 for ; Tue, 28 Oct 2014 12:20:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=MA8YLRZ/qEv0HnAL9viHh2P+yYscRc+wk7qmvXkpMcE=; b=Bc0FmDJ42yuItWUXCqJ4vf4+Xg5RHLYNntoaZGRCsSOqnUvokIdsFeAxg5IviYV7Tm haYQRzrc3WGevpOtR8/QJfwgi2Q4q7LUzYd9ujhwpI+s/wpNX36uvx/UT3JVH+wBGGWI 3SkZg2GDfi3jAi32xdz6qvn67ntnmhSg3ydDziLPyYbQm/VRTVIAtc3Vqd/j6s/JRRfE 0ecE7zavs3AC1HV4qTwArjlAyDKqiMVTKrXtG+TP7am9od0/mf+Xd0Hfd/NcpphpKtB/ slMN+Rz5wcAJMI53Y0JKvEy27PgxV47S5G2+BHWb19LH9QlCAWV7wMBsTf40C+tLFudh dLTg== X-Received: by 10.194.209.230 with SMTP id mp6mr7011367wjc.2.1414524041067; Tue, 28 Oct 2014 12:20:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 28 Oct 2014 12:20:20 -0700 (PDT) In-Reply-To: <544FE6AD.1030503@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 19:20:20 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:20:43 -0000 On Tue, Oct 28, 2014 at 6:55 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 28.10.2014 19:40, Miguel Clara wrote: > >> Does your computer have another video card, ie. an integrated one? Can > >> you give more information about your hardware? > >> > > > > Yes, it does, and Intel card. > > > > pciconf -lv output: http://filebin.ca/1fJdai9k7d85/pciconf.txt > > I assume you use the Intel card only? > > Before trying this update, did you have xf86-video-ati-7.2.0 installed? > > I have both installed, always had, but so far could only use intel, (I reported issue with the card before, but eventually got no reply back) > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:27:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2B9A964; Tue, 28 Oct 2014 19:27:34 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFD45AEA; Tue, 28 Oct 2014 19:27:33 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id q5so9794462wiv.4 for ; Tue, 28 Oct 2014 12:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=gAEhUSLrNALiOnWHTukTk7BwAoRxeG4skbB7KpShR1k=; b=LsiTCJlEVKAvr4sI38YUl01F4gGhvCarSuPxoD887KKZz4+uN0AHO9P4bZA/DLUG6B YKFvTS4LELlMjx3cwWQG996Xh2g6+53iV46UixAvB8fgq+N03LF16pxas4f37yEnVGrH HDm8Y9RBGIJQXzqdLDch900S7TZwZfz79XhMMLIQRf0SWhMUZfs8I43MmB4ex35WtX+a XsjznNJgD88ALBHZn8rRSI2c5AcO3wguaj0bjAhY0W3X7rQILYi68ESysQ5kecs75C8d LqbfEhCIdQxjP3iZd62IKDCd5xmhJOxpggKJNPzMR1w/8DygDT7yUAfGsWS+2GqF/ElQ kOhw== X-Received: by 10.194.81.70 with SMTP id y6mr5940664wjx.113.1414524452317; Tue, 28 Oct 2014 12:27:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 28 Oct 2014 12:27:11 -0700 (PDT) In-Reply-To: References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 19:27:11 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:27:35 -0000 On Tue, Oct 28, 2014 at 7:20 PM, Miguel Clara wrote: > > > On Tue, Oct 28, 2014 at 6:55 PM, Jean-S=C3=A9bastien P=C3=A9dron < > dumbbell@freebsd.org> wrote: > >> On 28.10.2014 19:40, Miguel Clara wrote: >> >> Does your computer have another video card, ie. an integrated one? Ca= n >> >> you give more information about your hardware? >> >> >> > >> > Yes, it does, and Intel card. >> > >> > pciconf -lv output: http://filebin.ca/1fJdai9k7d85/pciconf.txt >> >> I assume you use the Intel card only? >> >> Before trying this update, did you have xf86-video-ati-7.2.0 installed? >> >> I have both installed, always had, but so far could only use intel, (I > reported issue with the card before, but eventually got no reply back) > > > >> -- >> Jean-S=C3=A9bastien P=C3=A9dron >> >> > reinstalled xorg-server with debug, this is what I get with gdb: [New Thread 803406400 (LWP 101234/Xorg)] (gdb) r Starting program: /usr/local/bin/Xorg X.Org X Server 1.12.4 Release Date: 2012-08-27 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 11.0-CURRENT amd64 Current Operating System: FreeBSD hpbsd 11.0-CURRENT FreeBSD 11.0-CURRENT #2 7951248(master): Wed Oct 22 17:11:52 WEST 2014 root@hpbsd:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 Build Date: 28 October 2014 06:40:36PM Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 28 20:21:57 2014 (=3D=3D) Using config directory: "/usr/local/etc/X11/xorg.conf.d" (=3D=3D) Using system config directory "/usr/local/share/X11/xorg.conf.d" (II) [KMS] Kernel modesetting enabled. Program received signal SIGSEGV, Segmentation fault. 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e12c0) at xf86Crtc.c:1829 1829 output =3D config->output[config->compat_output]; Current language: auto; currently minimal (gdb) bt #0 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e12c0) at xf86Crtc.c:1829 #1 0x00000000004eb1ea in xf86SetScrnInfoModes (scrn=3D0x803510400) at xf86Crtc.c:1843 #2 0x00000000004ebf13 in xf86InitialConfiguration (scrn=3D0x803510400, canGrow=3D1) at xf86Crtc.c:2503 #3 0x000000080474153e in drmmode_pre_init (pScrn=3D0x803510400, drmmode=3D0x8034e5258, cpp=3D4) at drmmode_display.c:1757 #4 0x000000080473c89a in RADEONPreInit_KMS (pScrn=3D0x803510400, flags=3D0= ) at radeon_kms.c:946 #5 0x00000000004a4e19 in InitOutput (pScreenInfo=3D0x8acdb0, argc=3D1, argv=3D0x7fffffffeac0) at xf86Init.c:586 #6 0x0000000000424c66 in main (argc=3D1, argv=3D0x7fffffffeac0, envp=3D0x7fffffffead0) at main.c:203 (gdb) new xorg.core: http://filebin.ca/1fJrlIDKd2i8/Xorg.core From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:30:11 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1AF46C54; Tue, 28 Oct 2014 19:30:11 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC8A6B24; Tue, 28 Oct 2014 19:30:10 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjCT2-000EzW-Uj; Tue, 28 Oct 2014 20:30:09 +0100 Message-ID: <544FEEBC.2030208@FreeBSD.org> Date: Tue, 28 Oct 2014 20:30:04 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6CI2nrh4FmIJmSBqoxa7kugWL0tF4hh1D" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:30:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6CI2nrh4FmIJmSBqoxa7kugWL0tF4hh1D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 20:20, Miguel Clara wrote: >> Before trying this update, did you have xf86-video-ati-7.2.0 installed= ? >> > I have both installed, always had, Just to be sure, you mean you have both xf86-video-ati and x86-video-intel installed, right? > but so far could only use intel, (I reported issue with the card > before, but eventually got no reply back) FreeBSD doesn't support video cards which don't have their own output connectors yet. However, I suppose the Intel should work properly. Can you point me to the thread (in the mailing-list archive) where you reported your problem with the Intel card? --=20 Jean-S=C3=A9bastien P=C3=A9dron --6CI2nrh4FmIJmSBqoxa7kugWL0tF4hh1D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT+7AXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM+SgQAN1epSWP1f73ju6uuV57mt6G l6LSfMUtGAuhkiEKFxCLABltPn+PZZMnvApcb8+IzJJwJi5bRwbUpCRO4zk1HI1a SS1DruBIcphpHxIU8rYdGTOHqNaAw9ADO0Pb/eNbcmQWfHwwYJMQ2+BxcWoTYCUU HHSZdbiU34qYl0OjN+DxQKBa+wcp8FpYTOyO/cW1TTPgStXIIat+0aAOjCrr6YcT tauE4M/mxnOYPAlbPjGoj6S5cfaiXCOzkNA6ljQRR7ADPJIdCS1LQRMd3f/OloFQ fKBJ2Lq/a1sXjtGVWo6plhZs8UKJfKySrdD5pe756tPFQO77cqarKsLoXY3VECSF S4rGCg+xwGU7O2ZGRqtPEneeJ0vFDP91UUaVqeKXv8HZESHCmL/wSSn2vfR4NWir hw5jRkQ2YAveTL0Ay6lQ5mNeNIMkyT98fILN2LTaiX9Xjy7ficSkhT7XyshgpdmD ywyQgIXT4/gz46TDtYUs5l4cLjxdmPIkLfObnnRoV1w+B1lKWIqZ/YIswBSBYS/I EvvssBBk++y0WThYg/PwoKtlcif3ArXMWTlH9cFuNVobPcKZe+GgP0/p+kEDwDlk OeA7BJzFOGG8c81hXqez2VbXilL+FCYRWWEpTgF+KQAflNuWK3ha1WdJMt7m9Dj7 Yj/re2Lon2RLRCY4jAFb =K5nq -----END PGP SIGNATURE----- --6CI2nrh4FmIJmSBqoxa7kugWL0tF4hh1D-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:36:00 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7FE9CF52; Tue, 28 Oct 2014 19:36:00 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 976D8C11; Tue, 28 Oct 2014 19:35:59 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id n3so9802655wiv.5 for ; Tue, 28 Oct 2014 12:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=QjQtpU1NL9C/0n4xCti/WjbdbnTR6kOABHciWAzS4zw=; b=pWFurMKLvp0ofE2xxO+DNTi6947kL2hETVuv/Hthgg6CV9qsWO0ocvB9VIfAkggUGE 5Z6jlfRAIRZQmdXuFgUDpcFDquwJVPz2kgO0twct7tBy9SMu8S3zuE13kq+q+f//brTY 1ucQDUjM79ETRDBBfkY2o/sAzVfzpPDo79EmQCwiOnQZFSdS3zzYKC1drOGHE9bGo3Sv ltySQkmKJOYPQHJIOr8AuNqgyTo6oXJh3P02KSLKT73znd3rnK73cYk0XRo60bRshm9A BdlGX5S4ETeaVz731q0xNqmpZvfRgcl73X5XkGh39xWduZe5tsVHWkrXtHMEpduCs1wA h35w== X-Received: by 10.180.149.169 with SMTP id ub9mr7430026wib.73.1414524957878; Tue, 28 Oct 2014 12:35:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 28 Oct 2014 12:35:36 -0700 (PDT) In-Reply-To: <544FEEBC.2030208@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> <544FEEBC.2030208@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 19:35:36 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:36:00 -0000 On Tue, Oct 28, 2014 at 7:30 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 28.10.2014 20:20, Miguel Clara wrote: > >> Before trying this update, did you have xf86-video-ati-7.2.0 installed= ? > >> > > I have both installed, always had, > > Just to be sure, you mean you have both xf86-video-ati and > x86-video-intel installed, right? > Yes, but only used the intel in xorg.conf since radeaon failed > > > but so far could only use intel, (I reported issue with the card > > before, but eventually got no reply back) > > FreeBSD doesn't support video cards which don't have their own output > connectors yet. However, I suppose the Intel should work properly. > > Can you point me to the thread (in the mailing-list archive) where you > reported your problem with the Intel card? > The intel works indeed, the problem as always radeon, and now that you mention that, in the list the discussion lead to the same conclusion about the output. here: https://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014111.html I wonder tough... what if I connect it to a HDMI output? should it work or the same applies? > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:38:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 325931A3; Tue, 28 Oct 2014 19:38:12 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF714C38; Tue, 28 Oct 2014 19:38:11 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjCao-000F77-1n; Tue, 28 Oct 2014 20:38:10 +0100 Message-ID: <544FF09D.5080702@FreeBSD.org> Date: Tue, 28 Oct 2014 20:38:05 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HAVFkKrX13mo4lb9gw4i9v0ReLteBh7EP" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:38:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HAVFkKrX13mo4lb9gw4i9v0ReLteBh7EP Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 20:27, Miguel Clara wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e12c0) at > xf86Crtc.c:1829 > 1829 output =3D config->output[config->compat_output]; > Current language: auto; currently minimal > (gdb) bt > #0 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e12c0) at > xf86Crtc.c:1829 > #1 0x00000000004eb1ea in xf86SetScrnInfoModes (scrn=3D0x803510400) at > xf86Crtc.c:1843 > #2 0x00000000004ebf13 in xf86InitialConfiguration (scrn=3D0x803510400,= > canGrow=3D1) at xf86Crtc.c:2503 > #3 0x000000080474153e in drmmode_pre_init (pScrn=3D0x803510400, > drmmode=3D0x8034e5258, cpp=3D4) at drmmode_display.c:1757 > #4 0x000000080473c89a in RADEONPreInit_KMS (pScrn=3D0x803510400, flags= =3D0) at > radeon_kms.c:946 > #5 0x00000000004a4e19 in InitOutput (pScreenInfo=3D0x8acdb0, argc=3D1,= > argv=3D0x7fffffffeac0) at xf86Init.c:586 > #6 0x0000000000424c66 in main (argc=3D1, argv=3D0x7fffffffeac0, > envp=3D0x7fffffffead0) at main.c:203 > (gdb) >=20 > new xorg.core: http://filebin.ca/1fJrlIDKd2i8/Xorg.core Can you post /usr/local/bin/Xorg as well, please? --=20 Jean-S=C3=A9bastien P=C3=A9dron --HAVFkKrX13mo4lb9gw4i9v0ReLteBh7EP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT/ChXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMxQ4P/iBLIXPbLM5Coq4BIQoGDdZc ir3JWbxOjx0qHMVBOgDJRT87wt17fI/x4apw9Tv8XBbLwNuDW4gq/EvNqWekXUri gdlHQVfGyw6fIgKnUOO82G0ziMjHxtDRa2XWdbkGCUJsBvyr0E2brHpknd2qyQmh D4S2YeIo0Jm7TYw4Jo28g6AOSdOt2kODXW/tyG0gkvZXBxoOKT9oq5QOwkY4q3Rz cvfJKftBQrqzOydfatLPXwtPDpqFFV/uluIfdHlJGjlqm3rrfBnIE9UfIqNUgwH3 IaUnG0PCDKuwz/3l8YVn6d4ea3hv+najnlspAMr4oGdYLRs0nFRVj8b8eKx72lJ3 wFEemWcLnLSiiABirGFhdAHvI21sKSCUJ0a4SkwXTHkyPEH19jW4kTXxswGVYaYv ghrx+vd/puNSsk98dkWBC4/8y7T9uFADr5CjOP2bRfmEVvYmYPrHdPwbqSJcsxZj otpRCFDGfBAh3ulUxMDrQ3RexkSvAEjYq3AY9fNRqpnPnVxLGW4W9J7CfWXnp0tg ZM7wiHViuwr6AHK22VpgNbU2UuvzmGDSlPmVVvZY6GJnQRSv3QYvhyaYLINsLaZA 7whQ/JY07nfKjVjPYSuLR/wxSFhkiW333ptrmx9Pzdhqxoba9xy0dt/2BnFC3nzN DxKPZeflQK7X9XowPtOa =RZuS -----END PGP SIGNATURE----- --HAVFkKrX13mo4lb9gw4i9v0ReLteBh7EP-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:42:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79A1B514; Tue, 28 Oct 2014 19:42:51 +0000 (UTC) Received: from smtp-vbr5.xs4all.nl (smtp-vbr5.xs4all.nl [194.109.24.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DABE0D07; Tue, 28 Oct 2014 19:42:50 +0000 (UTC) Received: from slackbox.erewhon.home (slackbox.xs4all.nl [83.162.243.5]) by smtp-vbr5.xs4all.nl (8.13.8/8.13.8) with ESMTP id s9SJggN5095518; Tue, 28 Oct 2014 20:42:42 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.erewhon.home (Postfix, from userid 1001) id 4CCD3123EC; Tue, 28 Oct 2014 20:42:42 +0100 (CET) Date: Tue, 28 Oct 2014 20:42:42 +0100 From: Roland Smith To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 Message-ID: <20141028194242.GA91528@slackbox.erewhon.home> Mail-Followup-To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= , freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org References: <544E0FC8.8090605@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <544E0FC8.8090605@FreeBSD.org> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.23 (2014-03-12) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:42:51 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 27, 2014 at 10:26:32AM +0100, Jean-S=C3=A9bastien P=C3=A9dron w= rote: > Hi! >=20 > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. The reason is that 7.4.0 was crashing for several users, so > we want to be sure it's fixed in 7.5.0. >=20 > Here's patch: > https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.= patch >=20 > To apply it: > cd /usr/ports > patch -p1 < /path/to/ports-xf86-video-ati-7.5.0.patch >=20 > Then update x11-drivers/xf86-video-ati with your method of choice. Works fine with Radeon X1650 (ChipID =3D 0x71c1) on FreeBSD 10.1-PRERELEASE= #0 r273434 (amd64, GENERIC kernel). All ports updated on 2014-10-26. Roland --=20 R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0) --9amGYk9869ThD9tj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUT/GyAAoJEED21dyjijPgjOwP/2q+55RZKtHJwHe2QfALXkKm xfnSwQbCevDDNTQvQv3G59XGyDEaEA08chH27XptWbCbVp/ikEva7U9ixTta5hki p8Y7R8jNhEAa5VSjPcaoFLcoxZ72ZDxRGSkPFB4DMAllSuUpMUEcyvJCPyABUHL7 lEgu//8v0/EuQY/H8kkKs+nlfIyHOIiXJdmmizf0NI11b6cKuxwAUlcQHu3BUOVQ pKvVSvGXH/mdbVguhQ7e5BQ8/Yp6/AX26CNLTN08fQdynQTV2ZILeVMdz94AWJw5 ddkIvtWRoTOPDr9FWasR4c7zVfw8mq3JhNbZVZu6H4lSgzzDhqPnMOzDahoJPyx3 nLXAIgAQpzjCHhOJNAI9fJYy4h9NfODv9S2bQz1kzkFyS56jDbEvTu7iaqOZ1PA8 W9t4jdlbBLA1VazXP76egARq1jK0A1LEhT3fwIgiDnhEwzhgMuudp4itZnsRhCou nUe3eQP+vNL6XGlKK4LS79zhtpVs/CRlt3sFbG8WqaVy5EIJKoEk5Mcr6CxCoq1c RHBOCc5qraPZ4X3ECcDLwd3tGxRzzbyev1lBkhM7DAxsQyK+xsdzmRDkNrkVg6Lb XOuZ5cDwzJci8lUejg8EKWdmX2fDlM5v2F0aQRJSHzpvvLD87wgbaIWJ33KyBb3M vl3dC+3pZvfZSQmombcb =BsFD -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:44:25 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 682106CA; Tue, 28 Oct 2014 19:44:25 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 122D5D1E; Tue, 28 Oct 2014 19:44:25 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjCgp-000FGz-7o; Tue, 28 Oct 2014 20:44:23 +0100 Message-ID: <544FF20C.1010003@FreeBSD.org> Date: Tue, 28 Oct 2014 20:44:12 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> <544FEEBC.2030208@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="iQAvI6f3WGurlUS5RIet2Fog0gj0t0uJk" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:44:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iQAvI6f3WGurlUS5RIet2Fog0gj0t0uJk Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 20:35, Miguel Clara wrote: > The intel works indeed, the problem as always radeon, and now that you > mention that, in the list the discussion lead to the same conclusion ab= out > the output. >=20 > here: > https://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014111.htm= l >=20 > I wonder tough... what if I connect it to a HDMI output? should it work= or > the same applies? The HDMI output should work, though it's drived by the Intel GPU, not the Radeon. Your type of hardware configuration is meant to only use the Radeon GPU (more powerful, less battery friendly) when the extra power is needed/useful. In this case, the Radeon card is used to render a 3D image for instance, and the Intel card is still used to display the result on the screen. In FreeBSD, we lack the infrastructure to move data between both cards. --=20 Jean-S=C3=A9bastien P=C3=A9dron --iQAvI6f3WGurlUS5RIet2Fog0gj0t0uJk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT/IXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMSdoP/0PIFo7OrbWGr/ba8qpe5mYk vQ/1LoxftndtjayIF0yP00TIV3SxwQJBy0Tl7lifopB3WkVg0ZTKkbE99VB7LEpB 2xapstDMdnG+vHkvVyngrltue0oGhkfOeGzPN5IPd+u5r03E665GprKrJjC3pltM 4UO1dj3htmLInyfBsZb/RyPxe8fB3TOHFAG6XsF2gk2XrUofU/G3f6l+WbY5DfL4 uEYeJRdWfIcR2Jum+WqwsRrikTXD8m5ylIWH6VYBBEzebO2dxP22SU04+UgRlpko HpVfmAgA5eX9lduwl+xm+B8pdtG1v6x4wSJvCZHozwV2AEGJkij2pfwf+EYW5Avh TcXvy/NJQZZcubiA7beIWW8X6XW57LwE0blfq2uh3Unp2crohjD5zDlzSDENXw7+ 77FKTA5RwWOEmP95Fvi2YpZw5bQVwBsRYErfD0eae10Us7bO7hjBabl0SQqbIntE J/01MdoMuLW1hfn/ywLBegq5n/kSwyegcDJ1xXE71nbKKqnmDPJwcsRZtaUJGDAr Ho82kPHjujW7gGCe5vfQ4VjQlnqJDDspfUPqgggFS9OLeySfEdfaqtPcVj5Y590w oG3D3G3fCvqZloEgGClpku9nojnC8KYTemue3EYCVyzSsrp2jlY3WajJNC5A0H3G 014dflhsUlE1cH6lrxDb =QhGn -----END PGP SIGNATURE----- --iQAvI6f3WGurlUS5RIet2Fog0gj0t0uJk-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:46:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 174C4896; Tue, 28 Oct 2014 19:46:01 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A60C1D43; Tue, 28 Oct 2014 19:46:00 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjCiM-000FJ1-O8; Tue, 28 Oct 2014 20:45:58 +0100 Message-ID: <544FF276.5000809@FreeBSD.org> Date: Tue, 28 Oct 2014 20:45:58 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gLJU1cfHXlcNL4gJrsEj8rObWclRJxUUj" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:46:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gLJU1cfHXlcNL4gJrsEj8rObWclRJxUUj Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 20:27, Miguel Clara wrote: > new xorg.core: http://filebin.ca/1fJrlIDKd2i8/Xorg.core I'm interested in the two files too: /usr/local/lib/xorg/modules/drivers/ati_drv.so /usr/local/lib/xorg/modules/drivers/radeon_drv.so --=20 Jean-S=C3=A9bastien P=C3=A9dron --gLJU1cfHXlcNL4gJrsEj8rObWclRJxUUj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUT/J2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM35IP/RFcVLUJbsKO5sc8oGP06BaG BXcHbc5DLuEtVEnzfMw/dDsv3qk3eUt8VDWoD6qlqM6KIeot+0yY5kGWSmJEIZoj htnlCmeuPuSFc28y7i4ZuHJV2+VgafxsptuE3riWWK4EJn3O2/Gb/A/7hfmUlzzr r5Uhx5qFoV844CAgt8cwfMnYeetpGImBzag/rj4c6oY35AsJe7UneHAkjnpD+1NU aud1JfjIlr/jd+lYarw03UQmSeOn1xbhfL5m+4lw2tDF+VHL/Ce75gECnnBn0XP1 WRuz8ukBVvU9rKvWtWuZpUR7aw6/9syMeYGGfW4GnGhOseAYrSEktEouHQjgnWw7 AKDv84RyxApCcjKrAMXky73vowKsm56LisSpDvroKUdvQp7TjPfFxtXyN7xqX5wZ xk4+2baX/N+5i1btBA3Cnmbs87+mua1U0gXcO8KVOnY/DGbiBfM9ztz/wbsvt5q5 VV9e867VVgnAaBeKQ4peOqBxY4CphOWvBRNj8ok9F0yP4cuGpT5M18w9Oq3dYh2X 45MsRyY6v27yd0TzE8gf11vBlECwdIhMBs6MPg1RWV/eLsAqBNJ95Dz/ZmNRH2Oq zw3Kw6x7bh86Eui4Mdc3ODrMKAZhcvfTwkS9M1UifNLnLRyXAKNfEcWxNPkIrESg RCdPZxyLAbEhpPKs/J8R =tLwJ -----END PGP SIGNATURE----- --gLJU1cfHXlcNL4gJrsEj8rObWclRJxUUj-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:52:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2ADFAC2; Tue, 28 Oct 2014 19:52:02 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACF0BE26; Tue, 28 Oct 2014 19:52:01 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id a1so313001wgh.20 for ; Tue, 28 Oct 2014 12:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=v0nMBf305ag+bLEVKvLWb+tFCQxVPvDRJllaSqpd1jM=; b=CyStyGfTeu6n/q5/ysc8Z4upQShGHTNJ86p0EeLAkAJlAqB4NuQ8oxGomS6MTQTfDV H9fm37bkhGXZlpmQ7Vx6FJyUvXahHzPySCS2D6Ju9rWVQtWueQB2+IRzmyM02mK3DlLV wByzpmx3MVZC6ikVF2nw5edB515gxlftsmT2TLh/Mai86F1/EPeFczD409NG77tP60/e NOvEC9Or868fJxM865VyclBdtJO2fReXWvCUwnNU+nPDtUYf1kDM5B1MhfkwiuyCk6nJ 1OuXgIRghjVTRqp4Lw67clNEsMr9EOW9rr0Y14NuXGkHXb2Jt+qw/U/0j+tMyDuyRU9o 9Ekw== X-Received: by 10.180.104.198 with SMTP id gg6mr31202266wib.76.1414525919843; Tue, 28 Oct 2014 12:51:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 28 Oct 2014 12:51:39 -0700 (PDT) In-Reply-To: <544FF276.5000809@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <544FE6AD.1030503@FreeBSD.org> <544FF276.5000809@FreeBSD.org> From: Miguel Clara Date: Tue, 28 Oct 2014 19:51:39 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:52:02 -0000 On Tue, Oct 28, 2014 at 7:45 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 28.10.2014 20:27, Miguel Clara wrote: > > new xorg.core: http://filebin.ca/1fJrlIDKd2i8/Xorg.core > > I'm interested in the two files too: > /usr/local/lib/xorg/modules/drivers/ati_drv.so > /usr/local/lib/xorg/modules/drivers/radeon_drv.so > > -- > Jean-S=C3=A9bastien P=C3=A9dron > > http://filebin.ca/1fJyganoD7cx/Xorg http://filebin.ca/1fJywW2Hcpa0/ati_drv.so http://filebin.ca/1fJzBoYQR2dY/radeon_drv.so From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 19:52:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60BF0C75; Tue, 28 Oct 2014 19:52:54 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17EFFE3F; Tue, 28 Oct 2014 19:52:54 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id rl12so1487811iec.17 for ; Tue, 28 Oct 2014 12:52:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=G7VvvGQriRVuQYUiQfdVUtqVcQFtGuU6J24FllvAYMs=; b=Ic1i38c4/yL2ujKoNhXu878ASqgXrGS0vKwWlFCAzIqGlEXA4+AhjakE5qn/dsUIdc 0KE6DZVPoDO97tP/CJDEnR34jyc+IlmN82jjMSHxnTt6KB63pk4c+uyl892cl0P8F8Pz KATElkU5xhiqLCOquqkZ+hR694NH1/FRIYrqlXZ6qwV8tvWf/qtmGKVZUIBtk1K7mN4y GavK42WqqwAZmtNe2tWtJKgq8Sne3oaS0zRzppRD4hVhNYkCfrQlG23uBgVXtsBImxmU pCB0UxvaPc8Om2+bKNuBFq4qi6JFS4p7i2dOXq8uqAANqirtCxmoa3Ju5i7PQcI/a3ow uhCg== MIME-Version: 1.0 X-Received: by 10.50.142.71 with SMTP id ru7mr32462818igb.32.1414525973398; Tue, 28 Oct 2014 12:52:53 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Tue, 28 Oct 2014 12:52:53 -0700 (PDT) In-Reply-To: References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> Date: Tue, 28 Oct 2014 12:52:53 -0700 X-Google-Sender-Auth: 3fMZJlAKsZyBTFiQQEfNMsE4T_k Message-ID: Subject: Re: Dump time issues From: Kevin Oberman To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-stable , Chris H X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 19:52:54 -0000 On Tue, Oct 28, 2014 at 12:20 PM, Adrian Chadd wrote: > On 27 October 2014 11:09, Kevin Oberman wrote: > > >> I'm aware of two issues with SU+J, one of which is annoying and the > other > > is worse. > > 1. If the journal is not fully written on power fail or some other > reason, > > you may need to do a full fsck of the volume and the behavior of the > system > > until this is done can be very unpredictable. > > 2. You can't safely snapshot the system. This is what 'dump -L' does. > This > > means that some files dumped from a live FS may not be consistent (not > > good!) or, if '-L' is used, the system may well hang. > > > > While I love the fast fsck times (2 or 3 seconds) after a crash, I also > > question the default. Still, it may be a preferred choice be used for > very > > large file systems where a full fsck would take a very long time as long > as > > the risks are understood. For these systems, ZFS might be a better > choice. > > These arguments do NOT favor it being the default, IMHO. > > If people can reproduce SU+J problems then please file bugs. There > have been some fixes with the journal handling over the last year or > so and I haven't had this problem on -HEAD any longer, but it doesn't > mean it's there. > > > > > -adrian > The snapshot issue has been submitted to bugzilla several times. One is 173301. If it has been fixed, great, but the bug has not been touched and I have not seen any reports of it being fixed. Guess I could try a "dump -L" on my server and see, but I would hate to see it down for very long if the problem has not been fixed in 10.1-RC3-p1. Ihave no system running HEAD ATM, so If any fix has not made it to 10.1, I will not be able to test. The first issue is probably not a bug, but just very unlucky timing and does not damage the file system.I have seen many reports with the standard answer of "run a full fsck" which seems to fix it. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 22:09:17 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 262E07A3 for ; Tue, 28 Oct 2014 22:09:17 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7A60E17 for ; Tue, 28 Oct 2014 22:09:16 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id A753D89299 for ; Tue, 28 Oct 2014 23:09:12 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id 7DDF29C09084 for ; Tue, 28 Oct 2014 23:09:12 +0100 (CET) From: Walter Hop Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: System hang on shutdown when running freebsd-update Message-Id: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> Date: Tue, 28 Oct 2014 23:09:12 +0100 To: freebsd-stable@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 22:09:17 -0000 [Apologies for not replying directly to the thread; I found it at = https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080595.htm= l ] I noticed this same hang after upgrading from 10.0-RELEASE to 10.1-RC3 = in a VM running under VMware Fusion, so the problem appears still = present. I could only make it happen in the single uptime just after the system = was freebsd-updated from FreeBSD 10.0 to 10.1-RC3. Here is a screenshot: http://lf.ms/wait-for-reboot.png It did not make any progress after 2 hours of waiting. When restarting = the VM, the disk was dirty. Some interesting facts: - Note "swapoff: /dev/da0p2: Cannot allocate memory" in the screenshot = which might pose a clue. I haven=E2=80=99t seen this normally. - FreeBSD does respond to ping while it is busy, so it is not a complete = "freeze". - The VM is at 100% CPU while this is going on. I have created a snapshot of the VM in the failed state, so maybe some = useful information could be retrieved from it, although I don=E2=80=99t = have any experience with kernel debugging over VMware. Cheers, WH --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 03:21:10 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 662D9EA1 for ; Wed, 29 Oct 2014 03:21:10 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29783215 for ; Wed, 29 Oct 2014 03:21:10 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id rl12so2180129iec.9 for ; Tue, 28 Oct 2014 20:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZBJndOMGYP3EJg5XgTy6Sgu8zPu9Ncl/a3K+9Wdxp4o=; b=n+rF9c42QHTMcoNEyE41GueeVlWIpvODMjUY6V/QsMqFV75OlAEgb+AHK8S4XuhpQM hp4kxUcp5MhJBkzuy1bdQXjwdqAENjCf/ALPhk91cj814osk7uEcvQ6pvLfOe3/CEZfe wFnedZ27DA5nv2wQeNLz3Q2FiXgXxZaNg/AL33GtkvAECfYMV+mQ+IQ0wchceNQax3dr esKRR0tQFkO6OgRYgJkd9U+syv0TjTOk/Ijmq15XWTIZ3brpxGahvie1JO+dniTpOLyh HuQO73Ww43Tb2LKaUAKzEWM36b8Z6q4r+hH/pB4G0wirN04J3D6pjijRo/ML/15467RU pBTQ== MIME-Version: 1.0 X-Received: by 10.50.50.2 with SMTP id y2mr16601287ign.1.1414552868944; Tue, 28 Oct 2014 20:21:08 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Tue, 28 Oct 2014 20:21:08 -0700 (PDT) In-Reply-To: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> References: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> Date: Tue, 28 Oct 2014 20:21:08 -0700 X-Google-Sender-Auth: mODA1C69_Fz1z773ExziVt83w2E Message-ID: Subject: Re: System hang on shutdown when running freebsd-update From: Kevin Oberman To: Walter Hop Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 03:21:10 -0000 On Tue, Oct 28, 2014 at 3:09 PM, Walter Hop wrote: > [Apologies for not replying directly to the thread; I found it at > https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080595.ht= ml > ] > > I noticed this same hang after upgrading from 10.0-RELEASE to 10.1-RC3 in > a VM running under VMware Fusion, so the problem appears still present. > > I could only make it happen in the single uptime just after the system wa= s > freebsd-updated from FreeBSD 10.0 to 10.1-RC3. > > Here is a screenshot: http://lf.ms/wait-for-reboot.png > > It did not make any progress after 2 hours of waiting. When restarting th= e > VM, the disk was dirty. > > Some interesting facts: > - Note "swapoff: /dev/da0p2: Cannot allocate memory" in the screenshot > which might pose a clue. I haven=E2=80=99t seen this normally. > - FreeBSD does respond to ping while it is busy, so it is not a complete > "freeze". > - The VM is at 100% CPU while this is going on. > > I have created a snapshot of the VM in the failed state, so maybe some > useful information could be retrieved from it, although I don=E2=80=99t h= ave any > experience with kernel debugging over VMware. > > Cheers, > WH > > -- > Walter Hop | PGP key: https://lifeforms.nl/pgp > > I am starting to suspect that some code that is needed to flush a resourc= e that is blocking the complete shutdown is no longer available so waiting is not going to work. I tried a simple "shutdown now" and waited in single user mode for a minute before "reboot". It worked fine. This is based on guesswork, but seems to fit the symptoms. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 03:38:24 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CFF7D144; Wed, 29 Oct 2014 03:38:24 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EC305E7; Wed, 29 Oct 2014 03:38:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9T3cGEp004900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 28 Oct 2014 21:38:16 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9T3cGb5004897; Tue, 28 Oct 2014 21:38:16 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 28 Oct 2014 21:38:16 -0600 (MDT) From: Warren Block To: =?ISO-8859-15?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 In-Reply-To: <544E0FC8.8090605@FreeBSD.org> Message-ID: References: <544E0FC8.8090605@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 28 Oct 2014 21:38:16 -0600 (MDT) Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 03:38:24 -0000 On Mon, 27 Oct 2014, Jean-Sébastien Pédron wrote: > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. The reason is that 7.4.0 was crashing for several users, so > we want to be sure it's fixed in 7.5.0. Additional tests. All of these worked: Radeon HD 6550D (AMD A8-3850 APU) Radeon X300 PCIe Radeon HD 4350 PCIe From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 05:44:08 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3127B5C8; Wed, 29 Oct 2014 05:44:08 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41AA9199; Wed, 29 Oct 2014 05:44:07 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id z12so2504578wgg.9 for ; Tue, 28 Oct 2014 22:44:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=wD9/ZBSYbsqHP+ml+7rtKw/NTuD/0yHRNj0snrwI1sU=; b=CdzH2wYy6BOns1gDm4ruWrqO6R/xnGVodAa+B1PtpkI43BXb1h3XPr7Uvmv+rQbWbl 8s/02edfnka8NFjgmG3w4GPLoAr9wQVDvh2r1t0X4YRn+jAmlCA+1llSIbyz02vq50BA j/xwmHJhtVd/tXDjNF6CVKBhnXgwHIMJFi7eWNKPdadwzEHBGL6fVaPKy0yN/W3B9s4f KpKFpGOiW8tfTOKu/klCegsi1JhCmqotxFQN4zK/tkaBsJjfg2lzjGDQncBqk6ttsKfz hX1bv9lFNZG2yvgPy+FuJfC5ehysyz+ciG42KNjI/bA0nrj0O6B1HArAoQmSe7M5kOYi emmg== X-Received: by 10.180.221.229 with SMTP id qh5mr21827079wic.25.1414561445403; Tue, 28 Oct 2014 22:44:05 -0700 (PDT) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPSA id n4sm7490100wiz.17.2014.10.28.22.44.03 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 28 Oct 2014 22:44:04 -0700 (PDT) Date: Wed, 29 Oct 2014 06:44:02 +0100 From: Mateusz Guzik To: Craig Rodrigues Subject: Re: Automatically running /usr/tests on stable/10 branch under Jenkins Message-ID: <20141029054401.GC12014@dft-labs.eu> References: <20141024053636.GH11222@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-testing@freebsd.org" , FreeBSD stable , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 05:44:08 -0000 On Fri, Oct 24, 2014 at 09:09:48PM -0700, Craig Rodrigues wrote: > On Thu, Oct 23, 2014 at 10:36 PM, Mateusz Guzik wrote: > > > > (1) does a buildworld/buildkernel on amd64 when someone checks new > > > code into the stable/10 branch > > > > Is not this excessive? > > > It has not been a problem. For example, when a build occurs on the HEAD in > svn, > if further commits come in on HEAD, we have Jenkins configured so that it > will not trigger another build on HEAD until the build in progress is done. > It has been working fine. > Ok. > If no commits > > > > > (2) Creates a bootable UFS image with makefs > > > > any chance zfs will be used as well? > > > > Sure, we can look at that as well, but as I said earlier, > there need to be more bodies working on setting up builds and > configurations for this > to happen. > I can't help with that, sorry. > > > > > would be nice to run some kind of stress testing. buildworld with a high > > -j is an example of a general purpose test. This could be done with > > different frequency than regular tests. > > > > > Are you volunteering to write the scripts that incorporate any stress > testing > that you think should be done? We would welcome any contributions. > > Are you aware of e.g. stress2 by pho? https://people.freebsd.org/~pho/stress/index.html Plugging this in should not be hard for someone who knows jenkins. That's not me though. :) > > Do you have crashdumps configured in case stuff goes wrong? > > > > > > No. > > You can look at our scripts used to build and boot the various VM's: > > https://wiki.freebsd.org/Jenkins#Repositories > > It's all on github, so if you think you have new scripts to add, or fixes > to existing scripts, > you can feel free to do a github pull request to contribute. > > -- > Craig -- Mateusz Guzik From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 05:49:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D76B770; Wed, 29 Oct 2014 05:49:43 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07EC01C6; Wed, 29 Oct 2014 05:49:43 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id l13so2717845iga.2 for ; Tue, 28 Oct 2014 22:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ir3Q46OOKAlwXJ2n3Bugq5nAv+kFjDdrDo2MxU/ex0g=; b=zxJb+cjJ59EmtqgoOahQfJgzcvBE8KxH5zuBYBY5t1fCSO6C34iH50LQlDlgG53GBZ keyWxCsr20zt2HRlVn4DNgfYttXNTV35DdEzyeRWxgVHEQk3PYoRay3lsdPUJp6C2m5j mOhHnBlDItehkLEvKmOnGm45EJpYVCMO2m+dBYUYJ1z9fipuphz2vsW6euu5xFruMuNm nSJ9QFnRPoPgu+yARwEfg4cQDu9J1wKckGQLFwbH4Pt4Y9d839O7aFq8tAA+1fMqXNj0 dg+espyw/gFr3f6Gyv55Z4nmum1iqjkmpmds4df2m8I+xD+MR7fCdvZcrNWeWKGnDPvS 0x4A== MIME-Version: 1.0 X-Received: by 10.50.78.195 with SMTP id d3mr35194340igx.26.1414561782250; Tue, 28 Oct 2014 22:49:42 -0700 (PDT) Received: by 10.50.193.135 with HTTP; Tue, 28 Oct 2014 22:49:42 -0700 (PDT) In-Reply-To: <20141029054401.GC12014@dft-labs.eu> References: <20141024053636.GH11222@dft-labs.eu> <20141029054401.GC12014@dft-labs.eu> Date: Tue, 28 Oct 2014 22:49:42 -0700 Message-ID: Subject: Re: Automatically running /usr/tests on stable/10 branch under Jenkins From: NGie Cooper To: Mateusz Guzik Content-Type: text/plain; charset=UTF-8 Cc: Craig Rodrigues , "freebsd-testing@freebsd.org" , FreeBSD stable , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 05:49:43 -0000 On Tue, Oct 28, 2014 at 10:44 PM, Mateusz Guzik wrote: ... > Are you aware of e.g. stress2 by pho? > > https://people.freebsd.org/~pho/stress/index.html +1 for this, but I don't have cycles to implement it in Jenkins. All I'll say is that using stress2 won't work with your existing preconditions based on how it gathers crash dumps, how long some of the tests may take, etc. But you could effectively script pho's magic to some degree. > Plugging this in should not be hard for someone who knows jenkins. Plugging it in should be relatively easy. Babysitting it will be a lot more entertaining. There's a reason why we don't run it in our default test runs at Isilon ;)... From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 09:36:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8CF0FE99 for ; Wed, 29 Oct 2014 09:36:46 +0000 (UTC) Received: from sinkng.sics.se (unknown [IPv6:2001:6b0:3a:1:c654:44ff:fe45:117c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C086C53 for ; Wed, 29 Oct 2014 09:36:45 +0000 (UTC) Received: from P142s.sics.se (P142s.sics.se [193.10.66.127]) by sinkng.sics.se (8.14.9/8.14.9) with ESMTP id s9T9ag1t064652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Oct 2014 10:36:42 +0100 (CET) (envelope-from bengta@P142s.sics.se) Received: from P142s.sics.se (localhost [127.0.0.1]) by P142s.sics.se (8.14.9/8.14.9) with ESMTP id s9T9adK3002084; Wed, 29 Oct 2014 10:36:39 +0100 (CET) (envelope-from bengta@P142s.sics.se) Received: (from bengta@localhost) by P142s.sics.se (8.14.9/8.14.9/Submit) id s9T9acw7002083; Wed, 29 Oct 2014 10:36:38 +0100 (CET) (envelope-from bengta@P142s.sics.se) From: Bengt Ahlgren To: Kevin Oberman Subject: Re: System hang on shutdown when running freebsd-update In-Reply-To: (Kevin Oberman's message of "Tue, 28 Oct 2014 20:21:08 -0700") References: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) Date: Wed, 29 Oct 2014 10:36:38 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-STABLE Mailing List , Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 09:36:46 -0000 Kevin Oberman writes: > On Tue, Oct 28, 2014 at 3:09 PM, Walter Hop > wrote: > >> [Apologies for not replying directly to the thread; I found it at >> https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080595.h= tml >> ] >> >> I noticed this same hang after upgrading from 10.0-RELEASE to 10.1-RC3 in >> a VM running under VMware Fusion, so the problem appears still present. >> >> I could only make it happen in the single uptime just after the system w= as >> freebsd-updated from FreeBSD 10.0 to 10.1-RC3. >> >> Here is a screenshot: http://lf.ms/wait-for-reboot.png >> >> It did not make any progress after 2 hours of waiting. When restarting t= he >> VM, the disk was dirty. >> >> Some interesting facts: >> - Note "swapoff: /dev/da0p2: Cannot allocate memory" in the screenshot >> which might pose a clue. I haven=E2=80=99t seen this normally. >> - FreeBSD does respond to ping while it is busy, so it is not a complete >> "freeze". >> - The VM is at 100% CPU while this is going on. >> >> I have created a snapshot of the VM in the failed state, so maybe some >> useful information could be retrieved from it, although I don=E2=80=99t = have any >> experience with kernel debugging over VMware. >> >> Cheers, >> WH >> >> -- >> Walter Hop | PGP key: https://lifeforms.nl/pgp >> >> I am starting to suspect that some code that is needed to flush a resour= ce > that is blocking the complete shutdown is no longer available so waiting = is > not going to work. I tried a simple "shutdown now" and waited in single > user mode for a minute before "reboot". It worked fine. > > This is based on guesswork, but seems to fit the symptoms. Some more guesswork that better fit Walter's symtom than Kevin's... I have noticed that our server with large amounts of disk (three ZFS pools with 22x4TB disks) and 128GB RAM, often takes quite some time to shut down after syncing the disks. The last time it was in the order of 10 mins, but it has always completed. It seems to be related to swap. Swap is on dedicated GPT partitions on two system disks, and during the 10mins, it first accesses the first of these disks, then the other. I know for sure that the second must be accesses to swap, because this is the only partition currently used on this disk. I believe that it had in the order of 6GB pushed out to swap the last time. It is running 9.3-REL without Denninger's ZFS patches, so it tends to push some stuff to swap. Is there some swap GC going on before shutdown that can take this time? Bengt From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 11:41:56 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14283CC0; Wed, 29 Oct 2014 11:41:56 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5A92BA2; Wed, 29 Oct 2014 11:41:55 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjRdR-000501-UA; Wed, 29 Oct 2014 12:41:54 +0100 Message-ID: <5450D27D.4080508@FreeBSD.org> Date: Wed, 29 Oct 2014 12:41:49 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LcGAP4bCLCQdVp4hTNjqspK9u3sspcXRK" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 11:41:56 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LcGAP4bCLCQdVp4hTNjqspK9u3sspcXRK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 28.10.2014 19:40, Miguel Clara wrote: > On Tue, Oct 28, 2014 at 6:33 PM, Jean-S=C3=A9bastien P=C3=A9dron > wrote: >=20 >> On 28.10.2014 19:18, Miguel Clara wrote: >>> I should had that after rebooting the laptop, when it starts, with >>> should start "slim" and all I see is a mouse in the middle and a "pro= mpt >>> square" (not sure what to call it :P ) in the top left... >> >> The prompt square (I call it "text cursor" :) and the mouse are from >> vt(4), so it means the X server didn't acquire the display yet. When >> running Xorg alone, you should see nothing on the screen. >> >> In the dmesg and Xorg.log you posted previously, the card appears to >> have no CRTC or output connector: >> dmesg: No connectors reported connected with modes >> >> Does your computer have another video card, ie. an integrated one? Can= >> you give more information about your hardware? >=20 > Yes, it does, and Intel card. Ok, thanks to the code dump you provided, I found that xorg-server 1.12 expects to have output connectors. This was changed in xorg-server 1.15 to support connector-less cards: http://cgit.freedesktop.org/xorg/xserver/commit/?id=3Dd1440783a7367ff0d0c= 47d256bbca3b3cf8a5034 However, I see no change in the output connectors handling code in xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it works for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-ati 7.2.0 installed? --=20 Jean-S=C3=A9bastien P=C3=A9dron --LcGAP4bCLCQdVp4hTNjqspK9u3sspcXRK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUUNKBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMw4QQALvMqhpOzD05Zpotkiuks+d7 kAwcQASmKx+WCBV78JGHpJ5wxIKqLWxOFZDoZ0h3g/Z56/sSPPfMxhCCuMzgSBQ1 3TpMn2mkcCeWh/3H3DSKQolIhKl/Z0368EhnNz7LV/s9XXLkSzRmhXigsZU8Nwta HVXZRqMv0/iKIAvhQ2CV3bxtfE/CgprObFBlxwOcGMIKHFmE1R8cXooyvzpTlfTh ja0JhceMNoW8MID55gXNMENxfIzBwNeYMBG6WYM5+wGbiYVrjRAn1KxpWvxOgll1 NrP2/WujNnkL2NIsi7l2UkqzEp+ZNWDuj1fMoM1IhR+Ahun5ZdLUS8RKHE+hnmXz HAwOKjf2IzOlO0mN1LsJ15u3jmWJe3zuhUu9DvioyBKN4IiePEKIHMZ9iQ3iNN9u qCstivxm6ms47BFbkNvRZFmlbRWdEBjS3g/6Zqh2Jz0QMM9XdzqcPnS4BOE+jtws RTGXDego/RA/JqDdP6YSg4L8Za4fm8Kynsx//ivOka4ZjH0md8+IYMOyy4m97KXq 11nocbTSyk1wJM698xw+YLDQgYCvBXOMGrLqYBJ2mZA+1ZBTtiyEdG3S5jRfqFun RRebOW5+T/5VHLKQJCj3iNBSkTrcdsQE/fScsrUeaMt7AwRXyjr0LdM9Zc1/1pJ4 jjgUYTs3Fodkv7SmOYoj =4Txw -----END PGP SIGNATURE----- --LcGAP4bCLCQdVp4hTNjqspK9u3sspcXRK-- From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 13:05:03 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08E26AE3 for ; Wed, 29 Oct 2014 13:05:03 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 881C06E2 for ; Wed, 29 Oct 2014 13:05:02 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id f15so2677313lbj.27 for ; Wed, 29 Oct 2014 06:05:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DaT95CaYDKXzT4UuFpPxHlnweHuujNqqwbDKquX7Ueg=; b=JIyWKkQa0fmMMKZVAslBVii5SDYkZr84Izf47GGiVp6GqqmhhhqmIMS/YunnzyiGvh BK+qxuznxy1bXBV2DD6bN2TQWgNTmtFzaMBthhQ9t+xb9KnPqHYpgB264nrNnpid23P2 rsLjLFjUIu5F142OYkkMvoR7HtWXp1ZhbXwtRNmLRuyAsCfvFotOikqwc9pn/cBZNMCb OQFSdbXRjRnLyS7ghfTzFrcxj10ksZAd1nwN6H5/Fd+YbOa53CrUj9llyreehphzQhMn cFBq5S8o+V6rN+XrDtjKAB3VhEK0zypVX7Mufd3BzyZhLtopYMuPitzk8biRB1tC/ISw EvEw== MIME-Version: 1.0 X-Received: by 10.112.36.197 with SMTP id s5mr11467704lbj.30.1414587900310; Wed, 29 Oct 2014 06:05:00 -0700 (PDT) Received: by 10.152.210.197 with HTTP; Wed, 29 Oct 2014 06:05:00 -0700 (PDT) Date: Wed, 29 Oct 2014 14:05:00 +0100 Message-ID: Subject: 10.1RC1 armv6 RPI-B stuck in single user mode From: Alban Hertroys To: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 13:05:03 -0000 We have a Raspberry Pi here that was working fine, but because my colleagues tend to reboot the thing by unplugging the power, the root file-system got dirty. To fsck the root file-system, I attempted to boot it into single-user mode using nextboot -o "-s" -k kernel. Unfortunately, it never shows the single user mode prompt. The system gets stuck trying to mount root from ufs:/dev/mmcsd0s2a And it does that every time I attempt to boot it, because that nextboot flag never gets cleared! There doesn't appear to be any method of interrupting the boot loader on the Pi either. How do I get out of this pickle? -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 13:09:08 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F244C9C for ; Wed, 29 Oct 2014 13:09:08 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2FAB077F for ; Wed, 29 Oct 2014 13:09:08 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XjSzq-000Bgt-7n; Wed, 29 Oct 2014 14:09:06 +0100 Date: Wed, 29 Oct 2014 14:09:06 +0100 From: Kurt Jaeger To: Alban Hertroys Subject: Re: 10.1RC1 armv6 RPI-B stuck in single user mode Message-ID: <20141029130906.GI66862@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 13:09:08 -0000 Hi! > We have a Raspberry Pi here that was working fine, but because my > colleagues tend to reboot the thing by unplugging the power, the root > file-system got dirty. > To fsck the root file-system, I attempted to boot it into single-user > mode using nextboot -o "-s" -k kernel. > > Unfortunately, it never shows the single user mode prompt. The system > gets stuck trying to mount root from ufs:/dev/mmcsd0s2a > > And it does that every time I attempt to boot it, because that > nextboot flag never gets cleared! > There doesn't appear to be any method of interrupting the boot loader > on the Pi either. > > How do I get out of this pickle? Put the SD card into some other device, e.g. some laptop with FreeBSD, run the fsck there ? -- pi@opsec.eu +49 171 3101372 6 years to go ! From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 13:44:03 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B0CC696 for ; Wed, 29 Oct 2014 13:44:03 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8B04B58 for ; Wed, 29 Oct 2014 13:44:02 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id f15so2753578lbj.27 for ; Wed, 29 Oct 2014 06:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=okJSeTLyudcTbveOiZwGU8L/bEDUmYVSf93NsUngnIE=; b=qYaO/XoxsQiut7FBuW80VogkoJ7F+w58/1mO/xngX/EkZckXWTjFtKeI1K297iJoFu O+Nrnu2PV8Xd6/lJT4BHlJzvyE+THno9iowkX967A9k8zbaxhQEpXLZVLyakiRUviOGH hOH3sn1aSAqfCdOQ+SMG+HF/mqb9si81YZfuWMImQ4IvW9QIXg5d39hx4HVNKfFnCxbm ML4mhhlACRhj6WQXKqv+aeq127BIAv7bVRBOKouA2FuR5GBZq11sXtEVm3UEDV/bck53 eQ8esjmUjS/aGW+03i43EOfUAXyNKhPYW1HMshLqT1/uEUT9ub6miaStR6VXp/0w8Ez5 Lbpw== MIME-Version: 1.0 X-Received: by 10.152.27.134 with SMTP id t6mr11433301lag.17.1414590240850; Wed, 29 Oct 2014 06:44:00 -0700 (PDT) Received: by 10.152.210.197 with HTTP; Wed, 29 Oct 2014 06:44:00 -0700 (PDT) In-Reply-To: <20141029130906.GI66862@home.opsec.eu> References: <20141029130906.GI66862@home.opsec.eu> Date: Wed, 29 Oct 2014 14:44:00 +0100 Message-ID: Subject: Re: 10.1RC1 armv6 RPI-B stuck in single user mode From: Alban Hertroys To: Kurt Jaeger Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 13:44:03 -0000 On 29 October 2014 14:09, Kurt Jaeger wrote: > Hi! > >> We have a Raspberry Pi here that was working fine, but because my >> colleagues tend to reboot the thing by unplugging the power, the root >> file-system got dirty. >> To fsck the root file-system, I attempted to boot it into single-user >> mode using nextboot -o "-s" -k kernel. >> >> Unfortunately, it never shows the single user mode prompt. The system >> gets stuck trying to mount root from ufs:/dev/mmcsd0s2a >> >> And it does that every time I attempt to boot it, because that >> nextboot flag never gets cleared! >> There doesn't appear to be any method of interrupting the boot loader >> on the Pi either. >> >> How do I get out of this pickle? > > Put the SD card into some other device, e.g. some laptop with FreeBSD, > run the fsck there ? I was afraid that would be the answer; card readers are a bit hard to find here at the office. For example; to create the current SD card I had to "borrow" a laptop that someone had brought in to our helpdesk. Obviously, I'll need an SD cardreader at some point anyway, but I was hoping for a quick workaround. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 22:35:35 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4CCCE4F; Wed, 29 Oct 2014 22:35:35 +0000 (UTC) Received: from mail-in-13.arcor-online.net (mail-in-13.arcor-online.net [151.189.21.53]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6836A1BD; Wed, 29 Oct 2014 22:35:35 +0000 (UTC) Received: from mail-in-14-z2.arcor-online.net (mail-in-14-z2.arcor-online.net [151.189.8.31]) by mx.arcor.de (Postfix) with ESMTP id ED9702123D6; Wed, 29 Oct 2014 23:01:28 +0100 (CET) Received: from mail-in-16.arcor-online.net (mail-in-16.arcor-online.net [151.189.21.56]) by mail-in-14-z2.arcor-online.net (Postfix) with ESMTP id EB8CD18E12; Wed, 29 Oct 2014 23:01:28 +0100 (CET) X-Greylist: Passed host: 188.98.183.1 X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-16.arcor-online.net B0A84852C X-Greylist: Passed host: 188.98.183.1 X-Greylist: Passed host: 188.98.183.1 X-Greylist: Passed host: 188.98.183.1 Received: from lorvorc.mips.inka.de (dslb-188-098-183-001.188.098.pools.vodafone-ip.de [188.98.183.1]) by mail-in-16.arcor-online.net (Postfix) with ESMTPS id B0A84852C; Wed, 29 Oct 2014 23:01:28 +0100 (CET) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.9/8.14.7) with ESMTP id s9TM1Scs008926; Wed, 29 Oct 2014 23:01:28 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.14.9/8.14.9/Submit) id s9TM1SdX008925; Wed, 29 Oct 2014 23:01:28 +0100 (CET) (envelope-from naddy) Date: Wed, 29 Oct 2014 23:01:28 +0100 From: Christian Weisgerber To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 Message-ID: <20141029220128.GA8896@lorvorc.mips.inka.de> References: <544E0FC8.8090605@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <544E0FC8.8090605@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 22:35:35 -0000 Jean-Sébastien Pédron: > Before updating xf86-video-ati to 7.5.0, we would like some people to > try it out. Works fine for desktop use and Xvideo) with a Radeon HD 5450 on 10.1-PRERELEASE/amd64. > What we're especially looking for is report of successful or failed > startup of the X server. Well, terminating the old X server, updating xf86-video-ati to 7.5.0, and re-starting the X server led to this failure: [351790.259] (--) RADEON(0): Chipset: "ATI Radeon HD 5450" (ChipID = 0x68f9) [351790.259] drmOpenDevice: node name is /dev/dri/card0 [351790.259] drmOpenDevice: open result is 10, (OK) [351790.259] drmOpenByBusid: Searching for BusID pci:0000:01:00.0 [351790.259] drmOpenDevice: node name is /dev/dri/card0 [351790.259] drmOpenDevice: open result is 10, (OK) [351790.259] drmOpenByBusid: drmOpenMinor returns 10 [351790.259] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [351790.259] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 [351790.259] (EE) RADEON(0): [drm] failed to set drm interface version. [351790.259] (EE) RADEON(0): Kernel modesetting setup failed [351790.259] (II) UnloadModule: "radeon" [351790.259] (EE) Screen(s) found, but none have a usable configuration. [351790.259] Fatal server error: [351790.259] no screens found Rebooting the machine and restarting everything from scratch worked fine, though. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 22:49:56 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7297B718 for ; Wed, 29 Oct 2014 22:49:56 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3530D363 for ; Wed, 29 Oct 2014 22:49:56 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id B4E308928D for ; Wed, 29 Oct 2014 23:49:46 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id 8DC9C9C09084 for ; Wed, 29 Oct 2014 23:49:46 +0100 (CET) From: Walter Hop Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Small motd nit in 10.1 Message-Id: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> Date: Wed, 29 Oct 2014 23:49:46 +0100 To: freebsd-stable@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 22:49:56 -0000 I noticed that the motd has been updated, which is great. = https://svnweb.freebsd.org/base/releng/10.1/etc/motd?revision=3D272461&vie= w=3Dmarkup However, the following line could be improved: Show the version of FreeBSD installed: uname -a I would recommend changing the line to: Show the version of FreeBSD installed: freebsd-version Users often confuse the kernel version (uname -a) with the actual = FreeBSD version from the freebsd-version(1) command. Because of this, = people needlessly worry whether their system was updated correctly after = freebsd-update has run, because they erroneously check this with = =E2=80=98uname -a=E2=80=99. A small motd change will hopefully prevent = that. Cheers, WH --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 23:15:18 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D260736A; Wed, 29 Oct 2014 23:15:18 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1C288B9; Wed, 29 Oct 2014 23:15:17 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id ex7so5940178wid.4 for ; Wed, 29 Oct 2014 16:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=y2K98mLM76qVp7wNl/WG7iDmo4JtBOmSTKAAgYtV2Zo=; b=TV8owhwQI0bSP3iVP53SHR+9+RXZ4x9TBYkwAKBd9J0VCrN9h99kk1Ahw2B6PpnDTL MOD6eonyh1bNo3HClUDaJFSE4WBBCl2p23IdWCyQMtKB5zWS9HSHbiUy/RN0abzvHBsW /zuJBteSytdebtIjNkxJJ8cCc0DCtljZfsMn7E0RUbScKAhW1O9MsL2KQV62wMAe6TG0 KK9YJcaXvQW+gruI1uqloNJbAdRIq2RD27194XbkeIO4V50Engw51dUm9ajcylgP44wA O9XtabN44grAhalaURyi3RtniDILik5NPB7RwqvPPd29bJtcJLWOoK8uAi9P9ZROkyDm FLoQ== X-Received: by 10.194.190.130 with SMTP id gq2mr15852251wjc.18.1414624516245; Wed, 29 Oct 2014 16:15:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Wed, 29 Oct 2014 16:14:55 -0700 (PDT) In-Reply-To: <5450D27D.4080508@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> From: Miguel Clara Date: Wed, 29 Oct 2014 23:14:55 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 23:15:19 -0000 On Wed, Oct 29, 2014 at 11:41 AM, Jean-S=C3=A9bastien P=C3=A9dron < dumbbell@freebsd.org> wrote: > On 28.10.2014 19:40, Miguel Clara wrote: > > On Tue, Oct 28, 2014 at 6:33 PM, Jean-S=C3=A9bastien P=C3=A9dron < > dumbbell@freebsd.org > >> wrote: > > > >> On 28.10.2014 19:18, Miguel Clara wrote: > >>> I should had that after rebooting the laptop, when it starts, with > >>> should start "slim" and all I see is a mouse in the middle and a > "prompt > >>> square" (not sure what to call it :P ) in the top left... > >> > >> The prompt square (I call it "text cursor" :) and the mouse are from > >> vt(4), so it means the X server didn't acquire the display yet. When > >> running Xorg alone, you should see nothing on the screen. > >> > >> In the dmesg and Xorg.log you posted previously, the card appears to > >> have no CRTC or output connector: > >> dmesg: No connectors reported connected with modes > >> > >> Does your computer have another video card, ie. an integrated one? Can > >> you give more information about your hardware? > > > > Yes, it does, and Intel card. > > Ok, thanks to the code dump you provided, I found that xorg-server 1.12 > expects to have output connectors. This was changed in xorg-server 1.15 > to support connector-less cards: > > http://cgit.freedesktop.org/xorg/xserver/commit/?id=3Dd1440783a7367ff0d0c= 47d256bbca3b3cf8a5034 > > However, I see no change in the output connectors handling code in > xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it works > for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-ati > 7.2.0 installed? > It doens't work for the ati one... as I've reported in the mailing list I've posted, but you say the connector behaviour changed in xorg-server 1.15, so maybe I should install that version and test!? > > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 00:09:08 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2EECE86 for ; Thu, 30 Oct 2014 00:09:08 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 83DB3DFC for ; Thu, 30 Oct 2014 00:09:08 +0000 (UTC) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 6D9EE17 for ; Thu, 30 Oct 2014 10:09:01 +1000 (EST) Date: Thu, 30 Oct 2014 10:08:53 +1000 From: Paul Koch To: freebsd-stable@FreeBSD.org Subject: Suspected kernel memory leak with mmap/sha1 ? Message-ID: <20141030100853.65a62326@akips.com> Organization: AKIPS X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 00:09:08 -0000 Hi, We have been trying to track down an odd problem with what appears to be a kernel memory leak, but are at a complete loss of what is going on. We have a cut down test program that reproduces the problem. FreeBSD shed62.akips.com 10.1-RC3 FreeBSD 10.1-RC3 #0 r273491: Thu Oct 23 05:08:22 UTC 2014 root@shed31.akips.com:/usr/obj/usr/src/sys/GENERIC amd64 Basically our app mmap's large data files (eg. 250M) which contain blocks of compressed data. Our uncompress runs the data through SHA1 before uncompressing it. What we see is active memory being consumed, but can't figure out what is consuming it as our process size stays constant. When our process exits, active memory stays high and is never freed. If enough memory leaks, then the machine starts swapping and game over for our application. We've tried it on both ufs and zfs with the same results. Interestingly if you umount the zfs file system the active memory immediately disappears. Without the SHA1_xxx it runs fine. It's almost like a denial of service problem. To show the problem, run top and watch active memory. Compile the test program below cc -o leaktest -O2 leaktest.c find /usr -type f | xargs ./leaktest For some reason, active memory skyrockets, especially when it encounters large files. Running the program does not reproduce the problem 100% of the time, but close to it. Any suggestions ?? ----------------------------------------------- #include #include #include #include #include #include #include #include #include #include #define BUFSIZE (1 * 1024 * 1024) #define TMIN(a,b) ({ \ typeof (a) _a = (a); \ typeof (b) _b = (b); \ _a < _b ? _a : _b; \ }) int main (int argc, char **argv) { int i, j, fd = -1, open_flags = O_RDONLY, prot_flags = PROT_READ, mmap_flags = 0; char *filename, *data = NULL, *buf = NULL, *p; size_t len, rlen; struct stat s; u_char md[20]; SHA_CTX SD; if ((buf = malloc ((size_t) BUFSIZE)) == NULL) { fprintf (stderr, "malloc: %s\n", strerror (errno)); goto END; } for (i = 1; i < argc; i++) { filename = argv[i]; if (stat (filename, &s) != 0) fprintf (stderr, "stat: %s %s\n", filename, strerror (errno)); else if ((fd = open (filename, open_flags)) == -1) fprintf (stderr, "open: %s %s\n", filename, strerror (errno)); else if ((data = mmap (NULL, (size_t) s.st_size, prot_flags, mmap_flags, fd, (off_t) 0)) == MAP_FAILED) { fprintf (stderr, "mmap: %s %s\n", filename, strerror (errno)); close (fd); fd = -1; } else { printf ("%s: %zd bytes\n", filename, s.st_size); p = data; len = s.st_size; while (len > 0) { rlen = TMIN (BUFSIZE, len); /* Copy BUFSIZE lumps into buf and modify it so the compiler * doesn't optimise it out */ memcpy (buf, p, rlen); for (j = 0; j < BUFSIZE; j += 1024) buf[j]++; SHA1_Init (&SD); SHA1_Update (&SD, p, rlen); SHA1_Final (md, &SD); p += rlen; len -= rlen; } if (munmap (data, (size_t) s.st_size) == -1) { fprintf (stderr, "munmap: %s %s\n", filename, strerror (errno)); goto END; } if (close (fd) == -1) { fprintf (stderr, "close: %s %s\n", filename, strerror (errno)); goto END; } } } END: free (buf); exit (0); } -- Paul Koch | Founder, CEO AKIPS Network Monitor http://www.akips.com Brisbane, Australia From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 00:14:05 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B69BBFA8 for ; Thu, 30 Oct 2014 00:14:05 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DD11EAD for ; Thu, 30 Oct 2014 00:14:04 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9U0E3vb054872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Oct 2014 18:14:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9U0E33p054869; Wed, 29 Oct 2014 18:14:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 29 Oct 2014 18:14:02 -0600 (MDT) From: Warren Block To: Walter Hop Subject: Re: Small motd nit in 10.1 In-Reply-To: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> Message-ID: References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 29 Oct 2014 18:14:03 -0600 (MDT) Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 00:14:05 -0000 On Wed, 29 Oct 2014, Walter Hop wrote: > I noticed that the motd has been updated, which is great. > https://svnweb.freebsd.org/base/releng/10.1/etc/motd?revision=272461&view=markup > > However, the following line could be improved: > Show the version of FreeBSD installed: uname -a > > I would recommend changing the line to: > Show the version of FreeBSD installed: freebsd-version > > Users often confuse the kernel version (uname -a) with the actual FreeBSD version from the freebsd-version(1) command. Because of this, people needlessly worry whether their system was updated correctly after freebsd-update has run, because they erroneously check this with ?uname -a?. A small motd change will hopefully prevent that. Sorry, I don't understand the source of confusion. Besides the version, uname(1) also shows the architecture and kernel config file name. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 00:29:52 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8EEB82B7 for ; Thu, 30 Oct 2014 00:29:52 +0000 (UTC) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6046FBC for ; Thu, 30 Oct 2014 00:29:51 +0000 (UTC) Received: (qmail 12848 invoked by uid 89); 30 Oct 2014 00:25:58 -0000 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 30 Oct 2014 00:25:58 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: Small motd nit in 10.1 From: Rainer Duffner In-Reply-To: Date: Thu, 30 Oct 2014 01:25:45 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> To: Warren Block X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-stable@FreeBSD.org, Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 00:29:52 -0000 > Am 30.10.2014 um 01:14 schrieb Warren Block : >=20 > On Wed, 29 Oct 2014, Walter Hop wrote: >=20 >> I noticed that the motd has been updated, which is great. >> = https://svnweb.freebsd.org/base/releng/10.1/etc/motd?revision=3D272461&vie= w=3Dmarkup >>=20 >> However, the following line could be improved: >> Show the version of FreeBSD installed: uname -a >>=20 >> I would recommend changing the line to: >> Show the version of FreeBSD installed: freebsd-version >>=20 >> Users often confuse the kernel version (uname -a) with the actual = FreeBSD version from the freebsd-version(1) command. Because of this, = people needlessly worry whether their system was updated correctly after = freebsd-update has run, because they erroneously check this with ?uname = -a?. A small motd change will hopefully prevent that. >=20 > Sorry, I don't understand the source of confusion. >=20 > Besides the version, uname(1) also shows the architecture and kernel = config file name. If you use binary updates (which is the preferred method these days, if = I=E2=80=99m not wrong), and the update doesn=E2=80=99t touch the kernel, = the patch-level is subsequently not reflected in the output of uname -a. That=E2=80=99s why this isn=E2=80=99t a bad idea per-se. freebsd-version doesn=E2=80=99t show architecture, though, which might = be of interest. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 00:55:14 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C789909 for ; Thu, 30 Oct 2014 00:55:14 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FEC02DF for ; Thu, 30 Oct 2014 00:55:14 +0000 (UTC) Received: from gromit.chumby.lan (c-71-63-94-21.hsd1.va.comcast.net [71.63.94.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id CFBB15AC; Wed, 29 Oct 2014 20:47:43 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Small motd nit in 10.1 From: Paul Mather In-Reply-To: Date: Wed, 29 Oct 2014 20:47:42 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <93E9657A-737E-4705-A0E5-01F9E9110261@gromit.dlib.vt.edu> References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> To: Warren Block X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-stable@FreeBSD.org, Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 00:55:14 -0000 On Oct 29, 2014, at 8:14 PM, Warren Block wrote: > On Wed, 29 Oct 2014, Walter Hop wrote: >=20 >> I noticed that the motd has been updated, which is great. >> = https://svnweb.freebsd.org/base/releng/10.1/etc/motd?revision=3D272461&vie= w=3Dmarkup >>=20 >> However, the following line could be improved: >> Show the version of FreeBSD installed: uname -a >>=20 >> I would recommend changing the line to: >> Show the version of FreeBSD installed: freebsd-version >>=20 >> Users often confuse the kernel version (uname -a) with the actual = FreeBSD version from the freebsd-version(1) command. Because of this, = people needlessly worry whether their system was updated correctly after = freebsd-update has run, because they erroneously check this with ?uname = -a?. A small motd change will hopefully prevent that. >=20 > Sorry, I don't understand the source of confusion. The potential confusion arises because freebsd-version agrees with freebsd-update, but uname doesn't always. If you track FreeBSD via freebsd-update, uname only gets bumped when the kernel is updated. If you want to know which version of FreeBSD you're running, which command is more accurate: freebsd-version or uname -a? I would argue the former (freebsd-version). If you track FreeBSD via source updates, freebsd-version and uname -a match each other, so long as you update kernel and world together. Consider the system below, updated using freebsd-update after the last advisory causing an update to 10.0-RELEASE: =3D=3D=3D=3D=3D % freebsd-version=20 10.0-RELEASE-p11 % uname -a FreeBSD chumby.dlib.vt.edu 10.0-RELEASE-p10 FreeBSD 10.0-RELEASE-p10 #0: = Mon Oct 20 12:38:37 UTC 2014 = root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 =3D=3D=3D=3D=3D When you run freebsd-update on that system it considers itself currently as being a 10.0-RELEASE-p11 system when checking for updates. Cheers, Paul.= From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 02:44:06 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 627CD5C7 for ; Thu, 30 Oct 2014 02:44:06 +0000 (UTC) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1CF1E96 for ; Thu, 30 Oct 2014 02:44:05 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id gm9so3665002lab.18 for ; Wed, 29 Oct 2014 19:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lk5cUGthcwRePY1fqvlYvt5mUBGSNcywqx+Fndcapns=; b=Zs5CpCoJKgSQJf8Y36rP/8ggPw8QjSyymMYcjmIm0QRgMAmnE/4bOEudNlb8QcwS14 ATlefggDitrmGPXuYTjTjN3VB2FXj0WXPykQ0wTd4zlhek11zBlR0YC+d0krZ8gqj0BI vABGABO75lbkv4wBYqCQiMG0AHVu+CBlgfE4wAggHhSo8rk5+NYzLqOwLJt3VC7Io/XX WsFWpXVoXjz5aejXfReDKiLL2+8Uw1n5cXcyasd2WOiyPNoXQeH/S+b55ioB+kb4yBcR Jw31QNjsaEX7MwLeY/QqxRNQN7I/QALRoNXYh/Gqbc5GitZuvyOcVHUO+mQs+3R3WdEv XGbg== MIME-Version: 1.0 X-Received: by 10.152.9.201 with SMTP id c9mr15335285lab.38.1414637043277; Wed, 29 Oct 2014 19:44:03 -0700 (PDT) Received: by 10.25.0.6 with HTTP; Wed, 29 Oct 2014 19:44:03 -0700 (PDT) In-Reply-To: <20141030100853.65a62326@akips.com> References: <20141030100853.65a62326@akips.com> Date: Wed, 29 Oct 2014 22:44:03 -0400 Message-ID: Subject: Re: Suspected kernel memory leak with mmap/sha1 ? From: Ryan Stone To: Paul Koch Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 02:44:06 -0000 This is normal behaviour. Active (and inactive) memory comprises both application memory and system disk cache. By reading in all of those files, you have loaded the contents of those files into the cache, which is counted as active memory. The kernel has no preference between disk cache or application memory. Its decisions as to whether to swap application data out to disk or discard a page of disk cache are mainly based on the VM system's estimates of how often that data is being read. One test that you could perform is to run your app with swap disabled. If your application runs faster with swap disabled, that indicates that the VM subsystem's heuristics are suboptimal for your workload and some tuning might be necessary. If your application runs at the same speed or slower, then the VM subsystem is making correct (if counter-intuitive) decisions performance-wise. In that case, if your performance is still unacceptable then your options are either to tune your app's algorithm to reduce its working set (including application and file data) to fit into memory, or install more memory in the machine. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 04:21:03 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D1D1710; Thu, 30 Oct 2014 04:21:03 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F53FB3A; Thu, 30 Oct 2014 04:21:02 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id gq15so3724207lab.29 for ; Wed, 29 Oct 2014 21:21:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Xb+reV2cXXpFJcNCEEM6/jQa/9gUXVaNXlvyJNNFLtA=; b=R+v95IQ7lJX6QtjEIkU5OlTzqOGYdNd4a/BnFURKSmMhOJ6jj/bhSa1w0EXpWqZJDn o6P9TiyiNvdn9+BTk+39+SCcgMxhkpRcUQdD22YxBNntjYDbEQvamj+eowH5wjXCYGZ9 rx5SNoG5k6mvefvcVBF7j6pDI/1KZmI30GxHug5OXmdwsAY0ioVaogiSql3Eb0jBf6qp DwRO3yvkSBAp2SiJkM+bV7HsbFXShulpVa9Vz5ucVXdFHVeuQoKOMuUtTXc/uQHL882S sk6F+u1KKrRMvnQnDkLpyslArHT/7Su/0l14vgOor7LVJYgGpxjYKsnOOJ6EUBznmSrh SO6A== MIME-Version: 1.0 X-Received: by 10.152.27.134 with SMTP id t6mr15751207lag.17.1414642860351; Wed, 29 Oct 2014 21:21:00 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.84.197 with HTTP; Wed, 29 Oct 2014 21:21:00 -0700 (PDT) In-Reply-To: <20141029054401.GC12014@dft-labs.eu> References: <20141024053636.GH11222@dft-labs.eu> <20141029054401.GC12014@dft-labs.eu> Date: Wed, 29 Oct 2014 21:21:00 -0700 X-Google-Sender-Auth: 6xfKa9OZrLvSrURca6Nj-oKjoGM Message-ID: Subject: Re: Automatically running /usr/tests on stable/10 branch under Jenkins From: Craig Rodrigues To: Mateusz Guzik Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD stable , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 04:21:03 -0000 On Tue, Oct 28, 2014 at 10:44 PM, Mateusz Guzik wrote: > On Fri, Oct 24, 2014 at 09:09:48PM -0700, Craig Rodrigues wrote: > > Are you aware of e.g. stress2 by pho? > > https://people.freebsd.org/~pho/stress/index.html > > Plugging this in should not be hard for someone who knows jenkins. > > That's not me though. :) > Since you are making some good suggestions, would you be interested in learning enough about Jenkins on your own machine first, and and see if you can get a successful integration of stress2? Setting up Jenkins is quite easy under FreeBSD. There are a lot of howto's on the web for how to do it, and I have given multiple presentations: https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups I don't mind when people make good suggestions, but when the good suggestions are not backed up by concrete offers to help out, then that doesn't look so good. We need more people contributing actual scripts and tests. There are plenty of people contributing suggestions. :) -- Craig From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 04:37:16 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DDFCA18 for ; Thu, 30 Oct 2014 04:37:16 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 08942C49 for ; Thu, 30 Oct 2014 04:37:15 +0000 (UTC) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 814D517; Thu, 30 Oct 2014 14:37:13 +1000 (EST) Date: Thu, 30 Oct 2014 14:37:05 +1000 From: Paul Koch To: Ryan Stone Subject: Re: Suspected kernel memory leak with mmap/sha1 ? Message-ID: <20141030143705.22a7bd0e@akips.com> In-Reply-To: References: <20141030100853.65a62326@akips.com> Organization: AKIPS X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 04:37:16 -0000 On Wed, 29 Oct 2014 22:44:03 -0400 Ryan Stone wrote: > This is normal behaviour. Active (and inactive) memory comprises both > application memory and system disk cache. By reading in all of those > files, you have loaded the contents of those files into the cache, > which is counted as active memory. The kernel has no preference > between disk cache or application memory. Its decisions as to whether > to swap application data out to disk or discard a page of disk cache > are mainly based on the VM system's estimates of how often that data > is being read. > > One test that you could perform is to run your app with swap disabled. > If your application runs faster with swap disabled, that indicates > that the VM subsystem's heuristics are suboptimal for your workload > and some tuning might be necessary. If your application runs at the > same speed or slower, then the VM subsystem is making correct (if > counter-intuitive) decisions performance-wise. In that case, if your > performance is still unacceptable then your options are either to tune > your app's algorithm to reduce its working set (including application > and file data) to fit into memory, or install more memory in the > machine. Ok, we've done a bit more playing. Appears that if you touch the mmap'ed pages twice, it triggers the kernel to be much more aggressive at caching the file in active memory. This is occurring because we always validate the data with SHA1 before uncompressing it. Because we always read through the mmap'ed data sequentially, adding madvise() with the MADV_DONTNEED flag after each block stops the kernel from unnecessarily caching data we don't want. Also added a madvise() before munmap(). This has fixed the behaviour of the test program and also our application. The default behaviour of the kernel appears to be rather aggressive in trying to keep the file in active memory, but since it doesn't know what is cached data and application data, there's probably not much else it can do ? -------------------------------- #include #include #include #include #include #include #include #include #include #include #define BUFSIZE (1 * 1024 * 1024) #define TMIN(a,b) ({ \ typeof (a) _a = (a); \ typeof (b) _b = (b); \ _a < _b ? _a : _b; \ }) int main (int argc, char **argv) { int i, j, fd = -1, open_flags = O_RDONLY, prot_flags = PROT_READ, mmap_flags = MADV_SEQUENTIAL; char *filename, *data = NULL, *buf = NULL, *p; size_t len, rlen; struct stat s; u_char md[20]; SHA_CTX SD; if ((buf = malloc ((size_t) BUFSIZE)) == NULL) { fprintf (stderr, "malloc: %s\n", strerror (errno)); goto END; } for (i = 1; i < argc; i++) { filename = argv[i]; if (stat (filename, &s) != 0) fprintf (stderr, "stat: %s %s\n", filename, strerror (errno)); else if ((fd = open (filename, open_flags)) == -1) fprintf (stderr, "open: %s %s\n", filename, strerror (errno)); else if ((data = mmap (NULL, (size_t) s.st_size, prot_flags, mmap_flags, fd, (off_t) 0)) == MAP_FAILED) { fprintf (stderr, "mmap: %s %s\n", filename, strerror (errno)); close (fd); fd = -1; } else { printf ("%s: %zd bytes\n", filename, s.st_size); p = data; len = s.st_size; while (len > 0) { rlen = TMIN (BUFSIZE, len); /* Copy BUFSIZE lumps into buf and modify it so the * compiler doesn't optimise it out */ memcpy (buf, p, rlen); for (j = 0; j < BUFSIZE; j += 1024) buf[j]++; /* Doing a second pass triggers the kernel to be * aggressive in its file caching. */ memcpy (buf, p, rlen); for (j = 0; j < BUFSIZE; j += 1024) buf[j]++; /* Tell the kernel we don't need this region anymore */ madvise (p, rlen, MADV_DONTNEED); p += rlen; len -= rlen; } /* Tell the kernel we don't need this file anymore */ madvise (data, s.st_size, MADV_DONTNEED); if (munmap (data, (size_t) s.st_size) == -1) { fprintf (stderr, "munmap: %s %s\n", filename, strerror (errno)); goto END; } if (close (fd) == -1) { fprintf (stderr, "close: %s %s\n", filename, strerror (errno)); goto END; } } } END: free (buf); exit (0); } -- Paul Koch | Founder, CEO AKIPS Network Monitor http://www.akips.com Brisbane, Australia From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 07:35:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FAB5B3C; Thu, 30 Oct 2014 07:35:14 +0000 (UTC) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49A467D; Thu, 30 Oct 2014 07:35:13 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id q5so6534438wiv.17 for ; Thu, 30 Oct 2014 00:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=1OVcV3o3amhGah0EZA93W3O2AFxGgWrNdyjbg0qzaBk=; b=sXHgV8hohzbaQmfFx7jnVaaBFSqUUN14v4Ks4EiIg1K3D81l/fP4S8iDJ4glXx/EKi saCaEPqT18iRl95tSD/pyMBYlbkd27QPKQqj3ONVd2Dj6g0SdOSnPaUYfCEW1EKbvqCL Bot3nCsA9t6z584l239WaKCAvGafd5FPm8V0infEKgGSOl6OimsfNABkBaYUYJU43rOz N+h4y8EZFX+vrkJDgbtbUkVFfP+YTjyYqrIOGXG/ItREirQo15plW2Zn2qd18o33Vpap sJOMmm7KvBcX15PMHCtc4uf4RUkUZgmQh/JNT8ZZaS4E2PRZ6fsAKvcyn1eQCu7GLUDK kNtw== X-Received: by 10.180.77.170 with SMTP id t10mr8645341wiw.57.1414654511050; Thu, 30 Oct 2014 00:35:11 -0700 (PDT) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPSA id q5sm21223109wiy.16.2014.10.30.00.35.09 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 30 Oct 2014 00:35:10 -0700 (PDT) Date: Thu, 30 Oct 2014 08:35:07 +0100 From: Mateusz Guzik To: Craig Rodrigues Subject: Re: Automatically running /usr/tests on stable/10 branch under Jenkins Message-ID: <20141030073507.GA24415@dft-labs.eu> References: <20141024053636.GH11222@dft-labs.eu> <20141029054401.GC12014@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-testing@freebsd.org" , FreeBSD stable , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 07:35:14 -0000 On Wed, Oct 29, 2014 at 09:21:00PM -0700, Craig Rodrigues wrote: > On Tue, Oct 28, 2014 at 10:44 PM, Mateusz Guzik wrote: > > > On Fri, Oct 24, 2014 at 09:09:48PM -0700, Craig Rodrigues wrote: > > > > Are you aware of e.g. stress2 by pho? > > > > https://people.freebsd.org/~pho/stress/index.html > > > > Plugging this in should not be hard for someone who knows jenkins. > > > > That's not me though. :) > > > > > Since you are making some good suggestions, would you be interested > in learning enough about Jenkins on your own machine first, > and and see if you can get a successful integration of stress2? > Setting up Jenkins is quite easy under FreeBSD. There are a lot of howto's > on the web for > how to do it, and I have given multiple presentations: > https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups > > I don't mind when people make good suggestions, but > when the good suggestions are not backed up by concrete offers to > help out, then that doesn't look so good. We need more people contributing > actual scripts > and tests. There are plenty of people contributing suggestions. :) > I'm not really interested in learning jenkins, got enough backlog as it is. I'm just putting stuff out in case it sounds ok and someone wants to do it. -- Mateusz Guzik From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 08:13:37 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 51233895 for ; Thu, 30 Oct 2014 08:13:37 +0000 (UTC) Received: from umail.aei.mpg.de (umail.aei.mpg.de [194.94.224.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0343661 for ; Thu, 30 Oct 2014 08:13:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by umail.aei.mpg.de (Postfix) with ESMTP id 7FCD4200C46; Thu, 30 Oct 2014 09:07:04 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at aei.mpg.de Received: from umail.aei.mpg.de ([127.0.0.1]) by localhost (umail.aei.mpg.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kfNj7B-ZuCft; Thu, 30 Oct 2014 09:07:04 +0100 (CET) Received: from mailgate.aei.mpg.de (mailgate.aei.mpg.de [194.94.224.5]) by umail.aei.mpg.de (Postfix) with ESMTP id 66DDF200BC0; Thu, 30 Oct 2014 09:07:04 +0100 (CET) Received: from mailgate.aei.mpg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 571C8405889; Thu, 30 Oct 2014 09:07:04 +0100 (CET) Received: from intranet.aei.uni-hannover.de (ahin1.aei.uni-hannover.de [130.75.117.40]) by mailgate.aei.mpg.de (Postfix) with ESMTP id C1181406AF1; Thu, 30 Oct 2014 09:07:03 +0100 (CET) Received: from arc.aei.uni-hannover.de ([10.117.15.110]) by intranet.aei.uni-hannover.de (Lotus Domino Release 8.5.3FP6) with ESMTP id 2014103009065333-16681 ; Thu, 30 Oct 2014 09:06:53 +0100 Date: Thu, 30 Oct 2014 09:06:53 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Aristedes Maniatis Subject: Re: pkgng upgrade -> force upgrade of dependencies Message-Id: <20141030090653.18e71d09460a19c4aaf6a20f@aei.mpg.de> In-Reply-To: <544E2DAB.2090309@ish.com.au> References: <5448A373.1070707@ish.com.au> <97F5BECA-C7D0-49EE-AC91-7B87A990307D@jnielsen.net> <544E2DAB.2090309@ish.com.au> Organization: Max Planck Gesellschaft X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on intranet/aei-hannover(Release 8.5.3FP6|November 21, 2013) at 30.10.2014 09:06:53, Serialize by Router on intranet/aei-hannover(Release 8.5.3FP6|November 21, 2013) at 30.10.2014 09:07:02, Serialize complete at 30.10.2014 09:07:02 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-PMX-Version: 6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.10.30.75420 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, MIME_LOWER_CASE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_500_599 0, BODY_SIZE_7000_LESS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS ' Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 08:13:37 -0000 On Mon, 27 Oct 2014 22:34:03 +1100 Aristedes Maniatis wrote about Re: pkgng upgrade -> force upgrade of dependencies: > For anyone following along, I found a bug report for this problem in > pkgng. It isn't where I was originally looking (bugzilla) since it > seems they use github for development: > > https://github.com/freebsd/pkg/issues/964 Thanks for sharing this, I was already wondering if I was doing something terribly wrong here as I see the same issue for several weeks now. cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 08:15:28 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0C14990; Thu, 30 Oct 2014 08:15:28 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72CB167A; Thu, 30 Oct 2014 08:15:28 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjktC-0001j2-E9; Thu, 30 Oct 2014 09:15:26 +0100 Message-ID: <5451F399.2050105@FreeBSD.org> Date: Thu, 30 Oct 2014 09:15:21 +0100 From: =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Christian Weisgerber Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> In-Reply-To: <20141029220128.GA8896@lorvorc.mips.inka.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JXmp8dS1jPRp3haPtoXOukmPdAOlijrBv" Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 08:15:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JXmp8dS1jPRp3haPtoXOukmPdAOlijrBv Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 29.10.2014 23:01, Christian Weisgerber wrote: > Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > and re-starting the X server led to this failure: What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14= =2E6? If that's true, then the failure is expected because xf86-video-ati 6.14.6 will have loaded the old non-KMS kernel Radeon driver (radeondrm.ko). xf86-video-ati 7.5.0 can't work this old module and failed to load the new one because they conflict. That would explain why a reboot fixed the problem: radeondrm.ko wasn't loaded anymore. --=20 Jean-S=E9bastien P=E9dron --JXmp8dS1jPRp3haPtoXOukmPdAOlijrBv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUUfOeXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMGSwQAILWbSXKmLxhBE8Cyg4Hp3A0 +P7l3SQL6jmpFSkFG9PnydiHXKqPwGReAl6GGA6f6n8snQd7Brti/T7NzuebXT4H 1R8mtTfgptT48q2egP6iVd5N4Bok0uV4xA6ydb25hQTaJaBxVZCT9GU1ZbaMIiOK P4VqGZ0mvdMPFkXsjPulbkRM2BZ3+Cjjm/XHWF64bjxfLwlPgOjzGJq3sX3dFVVd UTEZg/oZcumhVoH97jcjrt78n3bSUX9Dm76KjAoOh2SczCuWSZwrebPbMRZ2kQqq WMb1E4GQzYxNpglkmSTCZkeSQSttmFVPE10y+s8f4DWr+aSSvDbgYwwQQXOBR094 8InsCTurhpZgp3TBgVTO7PO8DCfyBmnRd8Bvqm4jWvnsknIijFA8GYR23WJzSB37 0bAC895jhoNS2ZnWvhLtxAOVUD39TRmho3brMFMu0I4Lxwlb334YWPnKvTmS/8RZ 70oaXSa82gB1q7h4pUZmSHMBP3Bjxl1QSVL7eUDEE97mq805CVNxdpf9xKjgJqdr Xy+DSw9IzbAS84Ma2PN/qN2ve/Gzjwkuj2oznsdbi1y0XmcYtkhuv5Q6tfjx5x7b x2pt9vQH5C+SJRxcDECDOEL0StmRzahZS2Y3ULEQqVGf6DEu7dQwYDg9eoZUjo/i 8HN9z/R9dQW7/ihRJqSZ =jB3J -----END PGP SIGNATURE----- --JXmp8dS1jPRp3haPtoXOukmPdAOlijrBv-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 08:17:49 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8592B91; Thu, 30 Oct 2014 08:17:49 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 94AB86A8; Thu, 30 Oct 2014 08:17:49 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjkvT-0001kU-Qk; Thu, 30 Oct 2014 09:17:48 +0100 Message-ID: <5451F42B.5020805@FreeBSD.org> Date: Thu, 30 Oct 2014 09:17:47 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nIRSQ6IwcG9nV9IH1hkSukgF8gGXUc9pt" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 08:17:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nIRSQ6IwcG9nV9IH1hkSukgF8gGXUc9pt Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 30.10.2014 00:14, Miguel Clara wrote: >> However, I see no change in the output connectors handling code in >> xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it wor= ks >> for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-a= ti >> 7.2.0 installed? >=20 > It doens't work for the ati one... as I've reported in the mailing list= > I've posted, but you say the connector behaviour changed in xorg-server= > 1.15, so maybe I should install that version and test!? I understand that you can't use the Radeon card, but if xf86-video-ati 7.2.0 is installed, does the X server start correctly (instead of crashing, like with 7.5.0)? I suppose it does. In this case, could you please post Xorg.0.log with 7.2.0 installed? You don't need to update to xorg-server 1.15. --=20 Jean-S=C3=A9bastien P=C3=A9dron --nIRSQ6IwcG9nV9IH1hkSukgF8gGXUc9pt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUUfQrXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMVDYQAMpWOCJOJCbOAgmEBDlw+EJn tu1Mooq9VFIm2dN1meSsZ1v/b5Rj+rMoR+qU+94uUHMAMnro2EzOWENHM0SolF8G Vgb656s98qpXaVm4FN6+Jiuj2koVy7joGAGHQKl4icxa1fkM0mDogYrpe64jjYEi eiMz/xXkPach4M9aT/UZ2a5cI/hhDbJCp81Po4vHDeBQm3Tjp3AJUhFc9JP1Qdtx 0rOyN+SXLbN8pVn+L7Jz0ldrHAqGiehJrWkTfxN66TsfXmIzBmnQPqw59p2eReTy 7lVKkSUP6eNzHaNpGCq+Gz3zatchUNNHA2BqXYvgC5V9PkylKCzuECL7FR3KuByt lSIfCf/piWYpgtgLcTjiY5o0jwkDo3zhA/JmlW56QXrvaArezSmIqusXCfVEblt1 3JxBvWJOWETq23psklkqvACeWwpPPSxarCqDguJQZ0bLFKCZsbp5Y5Og17+nUlBC mgF2DfYdiCGrbP1PhQW2X2rX2Vi8aRNW4TRitgy90wwMDwAPMAEUTRQqnFNynycs 2JB21+ZfSuZS9RNr2Q4ktDzYs2LEv5E+D/Enqge2+WjOouOC6nG5F1qAfTPI47bk xdUp+660vMTyqKydCaaKFSfZ1+67PCP84xU+QC0GI/5F/Lwi3+HL6A2EM2S0VxP6 Yc25Tf5YhhQ1HPzad6Dy =zKOv -----END PGP SIGNATURE----- --nIRSQ6IwcG9nV9IH1hkSukgF8gGXUc9pt-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 12:21:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7492C1A for ; Thu, 30 Oct 2014 12:21:54 +0000 (UTC) Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B237284 for ; Thu, 30 Oct 2014 12:21:54 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id hy4so2559231vcb.28 for ; Thu, 30 Oct 2014 05:21:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=bu8+SN60SgfLkwAXz6yaFE8BRUEtE993uWfM2Zdxtxc=; b=jvLOJxMlhUlTyb/WGRohpErJ0EMYvzZDTB8ofa9xtRQ31GbciFDacy6zNsHippb4H8 ckhHqW3oh7S27BV2H7+SSPYsGtMFxBfLgesQimVN0WgWctXi1Jlw9nuapOiiyUUrF5Oa icKlTmcON9NzTnPC/uP4ZtC/Di0f1qatlTJseWybMXoBet/L+F68D4+tcmhdes53HmST 6kfKYJmEOcjqIQjAoGKqRECw86xOc9ewCNuQV0mUriH38skF0B8axda9qCMo+zvG3x5X 4ddq1l7uMCqmc81LhCxznTUx9xPVUetSrNLrspR2Tom1kAlB3F6DqWbA/9qFxNfHXoH5 NPVQ== MIME-Version: 1.0 X-Received: by 10.52.29.131 with SMTP id k3mr6745974vdh.2.1414671713676; Thu, 30 Oct 2014 05:21:53 -0700 (PDT) Received: by 10.220.168.199 with HTTP; Thu, 30 Oct 2014 05:21:53 -0700 (PDT) Date: Thu, 30 Oct 2014 13:21:53 +0100 Message-ID: Subject: JDK crash in JVM_handle_bsd_signal when starting Cassandra From: Nikolay Denev To: FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 12:21:54 -0000 Hi, When trying to start latest cassandra 2.1.1 (which I've succesfully built first), JDK crashes with SIGSEGV: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000000080241e045, pid=4107, tid=34384931840 # # JRE version: OpenJDK Runtime Environment (7.0-b17) (build 1.7.0_65-b17) # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode bsd-amd64 compressed oops) # Problematic frame: # V [libjvm.so+0x81e045] JVM_handle_bsd_signal+0x10ae75 # # Core dump written. Default location: /cores/core or core.4107 # # An error report file with more information is saved as: # /opt/apache-cassandra-2.1.1-src/hs_err_pid4107.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # zsh: abort (core dumped) CASSANDRA_CONF=`pwd`/conf JAVA_HOME=/usr/local/openjdk7 ./bin/cassandra -f Same thing happens when I try openjdk8 I'm running FreeBSD 10.0-STABLE #13 r270295M: Thu Aug 21 22:05:37 UTC 2014 --Nikolay From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 12:29:09 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4D73D95 for ; Thu, 30 Oct 2014 12:29:09 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9633D2FC for ; Thu, 30 Oct 2014 12:29:09 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XjoqE-0002P7-8w for freebsd-stable@freebsd.org; Thu, 30 Oct 2014 13:29:01 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: JDK crash in JVM_handle_bsd_signal when starting Cassandra References: Date: Thu, 30 Oct 2014 13:28:37 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_40 autolearn=disabled version=3.3.2 X-Scan-Signature: 1fac81774939798d1cdb19633eb460de X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 12:29:09 -0000 On Thu, 30 Oct 2014 13:21:53 +0100, Nikolay Denev wrote: > Hi, > > When trying to start latest cassandra 2.1.1 (which I've succesfully > built first), > JDK crashes with SIGSEGV: > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000080241e045, pid=4107, tid=34384931840 > # > # JRE version: OpenJDK Runtime Environment (7.0-b17) (build 1.7.0_65-b17) > # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode bsd-amd64 > compressed oops) > # Problematic frame: > # V [libjvm.so+0x81e045] JVM_handle_bsd_signal+0x10ae75 > # > # Core dump written. Default location: /cores/core or core.4107 > # > # An error report file with more information is saved as: > # /opt/apache-cassandra-2.1.1-src/hs_err_pid4107.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # > zsh: abort (core dumped) CASSANDRA_CONF=`pwd`/conf > JAVA_HOME=/usr/local/openjdk7 ./bin/cassandra -f > > Same thing happens when I try openjdk8 > > I'm running FreeBSD 10.0-STABLE #13 r270295M: Thu Aug 21 22:05:37 UTC > 2014 > > --Nikolay # An error report file with more information is saved as: # /opt/apache-cassandra-2.1.1-src/hs_err_pid4107.log It is helpful to others to include this file in your report. Ronald. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 12:29:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A09EAE87 for ; Thu, 30 Oct 2014 12:29:40 +0000 (UTC) Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62795308 for ; Thu, 30 Oct 2014 12:29:40 +0000 (UTC) Received: by mail-vc0-f174.google.com with SMTP id im17so169216vcb.33 for ; Thu, 30 Oct 2014 05:29:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=v/i8lnyBK/VaLmXiUQpbF5RdL+cJutS0AWrfQJ4Bzts=; b=KlobYrdKBtQGFNtqI6fuGE1+OeW8fPOxZ7pvnWtaUgPslWDt2Sz1bVKxE4Hum5sl5F M7JsdI3pfQdMRmvYQn4KLAJSG8cqP6z1Aqhx/5t5l6gCYycQLw9jlArVpNNMSvhK6Fm9 xUmxfq2jhUBEcnfyIdkDueknFL/1HrnXvZvwoG6I7vxBJ/NabPmQsjYsxwnMPdmjxQAQ v0Ib4er3VoYey1EhlQKtDCiznJPmZFuYTHQhUuu3w3dOSvhowxZi7HKxE3Ak2MU/4zG3 5SR3kxAOVAaIkkACku1OC6qLGrkRJ6V6GeS+ovUFosvviKw18LKi8ikGHKziULRwRLXh HeTg== MIME-Version: 1.0 X-Received: by 10.52.26.140 with SMTP id l12mr10772693vdg.12.1414672179326; Thu, 30 Oct 2014 05:29:39 -0700 (PDT) Received: by 10.220.168.199 with HTTP; Thu, 30 Oct 2014 05:29:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Oct 2014 13:29:39 +0100 Message-ID: Subject: Re: JDK crash in JVM_handle_bsd_signal when starting Cassandra From: Nikolay Denev To: FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 12:29:40 -0000 On Thu, Oct 30, 2014 at 1:21 PM, Nikolay Denev wrote: > Hi, > > When trying to start latest cassandra 2.1.1 (which I've succesfully > built first), > JDK crashes with SIGSEGV: > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000080241e045, pid=4107, tid=34384931840 > # > # JRE version: OpenJDK Runtime Environment (7.0-b17) (build 1.7.0_65-b17) > # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode bsd-amd64 > compressed oops) > # Problematic frame: > # V [libjvm.so+0x81e045] JVM_handle_bsd_signal+0x10ae75 > # > # Core dump written. Default location: /cores/core or core.4107 > # > # An error report file with more information is saved as: > # /opt/apache-cassandra-2.1.1-src/hs_err_pid4107.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # > zsh: abort (core dumped) CASSANDRA_CONF=`pwd`/conf > JAVA_HOME=/usr/local/openjdk7 ./bin/cassandra -f > > Same thing happens when I try openjdk8 > > I'm running FreeBSD 10.0-STABLE #13 r270295M: Thu Aug 21 22:05:37 UTC 2014 > > --Nikolay Looks like it might be cassandra bug, as it's calling sun.misc.Unsafe.getByte() which can crash the JVM with bad addresses. Stack: [0x00007fffffbbe000,0x00007fffffbfe000], sp=0x00007fffffbfcdf0, free space=251k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.so+0x81e045] JVM_handle_bsd_signal+0x10ae75 j sun.misc.Unsafe.getByte(Ljava/lang/Object;J)B+0 j org.apache.cassandra.utils.FastByteOperations$UnsafeOperations.copy(Ljava/lang/Object;J[BII)V+35 j org.apache.cassandra.io.util.Memory.getBytes(J[BII)V+78 j org.apache.cassandra.io.sstable.IndexSummary.getKey(I)[B+37 --Nikolay From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 13:21:37 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D42A7AEE; Thu, 30 Oct 2014 13:21:37 +0000 (UTC) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E510DAC8; Thu, 30 Oct 2014 13:21:36 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id q5so4503020wiv.10 for ; Thu, 30 Oct 2014 06:21:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pDsE9OCOajinH0CIPoX7PbABsItgwf18jADt/yEleFo=; b=bKuwBsGSQ1GVXzSuj6jU78UjIUrJ2Ho4HXoMCe5wNlyeMC2ppAszLH2GQ9Yf8FuUv0 ij/kGU4V6d/4vP0NApobJEs2oDeK9ScdjkK26U6HHWreadz/DXptCi6VefkFQzgn700l VdlBn/CIiIEKiHg896WjwmdjVOmOze9Uirt7onKEYIBPWLDBczoJA9zjggHF5dpsDUtl 9RyTwwSX5zoxzke+f2OjjTUcVhNQvS7Ac8IQ4jBsqKEf2rsiZUPg+1fEvyi0uVJymAgH tu+hSh0NLwagtzEHnpzrHgCqAujvvb0Pq+idpmgFJznY1tkTNWhDIoeMzkDSkExcnHOD YQ5Q== X-Received: by 10.180.12.136 with SMTP id y8mr29901164wib.73.1414675295214; Thu, 30 Oct 2014 06:21:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Thu, 30 Oct 2014 06:21:14 -0700 (PDT) In-Reply-To: <5451F42B.5020805@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> From: Miguel Clara Date: Thu, 30 Oct 2014 13:21:14 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 13:21:37 -0000 On Thu, Oct 30, 2014 at 8:17 AM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 30.10.2014 00:14, Miguel Clara wrote: > >> However, I see no change in the output connectors handling code in > >> xf86-video-ati between 7.2.0 and 7.5.0. Therefore, I wonder why it wor= ks > >> for you with 7.2.0. Could you please post Xorg.0.log with xf86-video-a= ti > >> 7.2.0 installed? > > > > It doens't work for the ati one... as I've reported in the mailing list > > I've posted, but you say the connector behaviour changed in xorg-server > > 1.15, so maybe I should install that version and test!? > > I understand that you can't use the Radeon card, but if xf86-video-ati > 7.2.0 is installed, does the X server start correctly (instead of > crashing, like with 7.5.0)? I suppose it does. In this case, could you > please post Xorg.0.log with 7.2.0 installed? > > You don't need to update to xorg-server 1.15. > Ah I see now, I misunderstood what you meant the first time. Would pkg remove -f xf86-video-ati, and pkg install xf86-video-ati (since its the 7.2 package version) be enough or do I need to reinstall xorg-server from pkg to make sure dependencies are linked properly? Fro the record, with just remove 7.5 and install 7.2 I get this in gdb: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 2014 (=3D=3D) Using config directory: "/usr/local/etc/X11/xorg.conf.d" (=3D=3D) Using system config directory "/usr/local/share/X11/xorg.conf.d" [New Thread 803406400 (LWP 101070/Xorg)] (II) [KMS] Kernel modesetting enabled. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 803406400 (LWP 101070/Xorg)] 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at xf86Crtc.c:1829 1829 xf86Crtc.c: No such file or directory. in xf86Crtc.c Current language: auto; currently minimal (gdb) bt #0 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at xf86Crtc.c:1829 #1 0x00000000004eb1ea in xf86SetScrnInfoModes (scrn=3D0x803512400) at xf86Crtc.c:1843 #2 0x00000000004ebf13 in xf86InitialConfiguration (scrn=3D0x803512400, canGrow=3D1) at xf86Crtc.c:2503 #3 0x00000008047234a7 in ?? () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #4 0x000000080472090b in ?? () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #5 0x00000000004a4e19 in InitOutput (pScreenInfo=3D0x8acdb0, argc=3D1, argv=3D0x7fffffffead8) at xf86Init.c:586 #6 0x0000000000424c66 in main (argc=3D1, argv=3D0x7fffffffead8, envp=3D0x7fffffffeae8) at main.c:203 Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 14:03:12 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0AA70553; Thu, 30 Oct 2014 14:03:12 +0000 (UTC) Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFAB0EAD; Thu, 30 Oct 2014 14:03:11 +0000 (UTC) Received: from mail-in-17-z2.arcor-online.net (mail-in-17-z2.arcor-online.net [151.189.8.34]) by mx.arcor.de (Postfix) with ESMTP id 3921435A9B1; Thu, 30 Oct 2014 14:31:14 +0100 (CET) Received: from mail-in-06.arcor-online.net (mail-in-06.arcor-online.net [151.189.21.46]) by mail-in-17-z2.arcor-online.net (Postfix) with ESMTP id 30BE7367311; Thu, 30 Oct 2014 14:31:14 +0100 (CET) X-Greylist: Passed host: 188.98.183.190 X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-06.arcor-online.net E67B110BF68 X-Greylist: Passed host: 188.98.183.190 X-Greylist: Passed host: 188.98.183.190 X-Greylist: Passed host: 188.98.183.190 Received: from lorvorc.mips.inka.de (dslb-188-098-183-190.188.098.pools.vodafone-ip.de [188.98.183.190]) by mail-in-06.arcor-online.net (Postfix) with ESMTPS id E67B110BF68; Thu, 30 Oct 2014 14:31:13 +0100 (CET) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.9/8.14.7) with ESMTP id s9UDVD6I026610; Thu, 30 Oct 2014 14:31:13 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.14.9/8.14.9/Submit) id s9UDVCMm026609; Thu, 30 Oct 2014 14:31:12 +0100 (CET) (envelope-from naddy) Date: Thu, 30 Oct 2014 14:31:12 +0100 From: Christian Weisgerber To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 Message-ID: <20141030133112.GA26588@lorvorc.mips.inka.de> References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5451F399.2050105@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 14:03:12 -0000 Jean-Sébastien Pédron: > > Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > > and re-starting the X server led to this failure: > > What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14.6? No, just the instance I had running before: X server 1.12.4 and xf86-video-ati 7.2.0. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 17:09:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A30A874; Thu, 30 Oct 2014 17:09:02 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2498968F; Thu, 30 Oct 2014 17:09:02 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjtDX-0008B0-DS; Thu, 30 Oct 2014 18:08:59 +0100 Message-ID: <545270A7.6030807@FreeBSD.org> Date: Thu, 30 Oct 2014 18:08:55 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VvbTTjlnlanVLRH84wXrEarVr2ULr0O3j" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 17:09:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VvbTTjlnlanVLRH84wXrEarVr2ULr0O3j Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 30.10.2014 14:21, Miguel Clara wrote: > Fro the record, with just remove 7.5 and install 7.2 I get this in gdb:= > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 201= 4 > (=3D=3D) Using config directory: "/usr/local/etc/X11/xorg.conf.d" > (=3D=3D) Using system config directory "/usr/local/share/X11/xorg.conf.= d" > [New Thread 803406400 (LWP 101070/Xorg)] > (II) [KMS] Kernel modesetting enabled. >=20 > Program received signal SIGSEGV, Segmentation fault. > (...) > (gdb) bt > #0 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at > xf86Crtc.c:1829 > (...) >=20 > Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log Ok, so the problem is exactly the same with either 7.2.0 and 7.5.0. I "prefer" that, because I didn't see the difference between both versions in this particular code :) We'll add the fix from xserver 1.15 in our xorg-server port, it should fix that crash. What I don't understand is how could this could work before. Are you sure you had xf86-video-ati 7.2.0 installed? Can you check your logs (/var/log/messages) and look for lines like these: pkg-static: pkg-1.3.8_3 deinstalled pkg-static: pkg-1.4.0.a3 installed The program could be "pkg" or "pkg-static". And it should say that a package was installed/deinstalled/upgraded, with the version of the package. Can you check the first time you installed xf86-video-ati 7.5.0 if it actually replaced 7.2.0 or something else? --=20 Jean-S=C3=A9bastien P=C3=A9dron --VvbTTjlnlanVLRH84wXrEarVr2ULr0O3j Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUUnCrXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMyW4QAKVJbOm0qB8Eh/VzgaYbr6Ck Qs6C32mhMrfYjXzbJrPayJnNiLbJzPxDWJg1nnz1DxtX+497rwpe5/0Oljar+Us1 QH5CLfWdA9Vxe+QU9eE4pyM9jQ7GHfB1AGLiDQRLOf6OVYDnDhs/pzhot6TxgzGl n5py7yw810R7nruSOKvhQQBS1e3j2Ar76p7ULq8D8pP4Rm7UY9j4ZyrToGbDLU16 nsN6Ctf1q0nsN/EVzzmcM94qP0ijhJzR+lLFh9kbouwWp6Hah2JgTf+wbEvB7V/q VMwUqg2VO5f+zZ57sw4jXmdN3BUL+i1cOuZJ/Fc0dPcLmHyunLVokdQ0CqGZcErq rfzWSL43JyoEF7ctXl3gYm0Y69yJYgcgjxl6lPbSMj6xkKzX6OzASyjlT/Dy3gjJ +pZn5GE33dVlUk0ZCADNCHCBTV42L7yfAEzmx+PZ2jyM5LQliRL2btykkJ6q14of zcl7ZyerR4hr/iQ/lNo4Is04G1J0o+m0Ot2cs5z/X9f1vFkHN0CcmDHyTYrk9Gmi SQOMBV84KDQB60Vktky21PwLE8rbbAgr8Iro3/Ckfn4R2H7bsEnyPiA55FvafdP6 HfofmpDjIWu6NvUWk2rqe1rSfn1ociPufAzo8uC2xEwfD89Z5iI00GFC/ZKjIgxK fatn9Ahd1C5Kk+cOTLI2 =inhQ -----END PGP SIGNATURE----- --VvbTTjlnlanVLRH84wXrEarVr2ULr0O3j-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 17:10:08 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B301BA3B; Thu, 30 Oct 2014 17:10:08 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 738D66B8; Thu, 30 Oct 2014 17:10:08 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XjtEc-0008CF-Lq; Thu, 30 Oct 2014 18:10:06 +0100 Message-ID: <545270EE.3090405@FreeBSD.org> Date: Thu, 30 Oct 2014 18:10:06 +0100 From: =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Christian Weisgerber Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> <20141030133112.GA26588@lorvorc.mips.inka.de> In-Reply-To: <20141030133112.GA26588@lorvorc.mips.inka.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GBEpodS4O2TDe2j3XcOGMAHjjM8MRw7HF" Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 17:10:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GBEpodS4O2TDe2j3XcOGMAHjjM8MRw7HF Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 30.10.2014 14:31, Christian Weisgerber wrote: > Jean-S=E9bastien P=E9dron: >=20 >>> Well, terminating the old X server, updating xf86-video-ati to 7.5.0,= >>> and re-starting the X server led to this failure: >> >> What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6= =2E14.6? >=20 > No, just the instance I had running before: X server 1.12.4 and > xf86-video-ati 7.2.0. Ok. Does the problem still happen now? --=20 Jean-S=E9bastien P=E9dron --GBEpodS4O2TDe2j3XcOGMAHjjM8MRw7HF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUUnDuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM//EP/2RuKwc4eqhRRqA3bYiB4N42 rBv2jtojvtGcmdLRX4Y8EhLwkPLAAXpSMB9yaDeMkuBjxe8YYmlw49X/XxtZ9P9S QQrYpyaiHNmjmeJgD+ltNYVH95/xJpnLG8zZtuYYWecRKrWDzgBmEdJEa6SILn5a 48dD1E+0Tbpdq6MM1TVF19qXZLnYCEKqgcMRVwkNQW45ofjgqDMc2562lUHcrWMx F++HIUqt59XQrJbZOukG2lmCJjyWWsERA+8pez+Rh1XR0o4mTe+OpaeSxYn0SY0l aWHCMbgP4XRrgWEXzTXR6qTt0Dk5bZ+cm2UGnl+trh7VfN/IViTBjH1DJg8RuHZ5 3YWhx7lYETT/ZbkTxuaLLAUIUGcavmm2M7brMYGgx1Heay+/RY5YTQ2lMlaEJ7cY IQ4Qa2OIvp3Hf14B+FU5c+tFPOaeTKGQoRVxd3wuHCqnryndGcpVdSIWke/FJUKN Jeo/vvl4mKm4L/LddYstT9j33nLaCK7hLVukovFp7Bs4TrJMYmtsjXsHiwyzMOZZ K5/1DM5GbFgI5jjksnJ7CvdZUh2LWQz4L24So4/IsNXmaE5XHOMUDTVYA/e+P2IY CmmFzwuDpAJm0b42rwqtItrkxIis+3o1eC2oxwXI+QVkJPP/NzkPIQEu699dqRko 5I/1GnCNz8DRLgdnUOTr =Ocmx -----END PGP SIGNATURE----- --GBEpodS4O2TDe2j3XcOGMAHjjM8MRw7HF-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 19:58:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 009A65BE for ; Thu, 30 Oct 2014 19:58:58 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCA40B1E for ; Thu, 30 Oct 2014 19:58:58 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B8B4DB939; Thu, 30 Oct 2014 15:58:57 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: Small motd nit in 10.1 Date: Thu, 30 Oct 2014 15:54:03 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> <93E9657A-737E-4705-A0E5-01F9E9110261@gromit.dlib.vt.edu> In-Reply-To: <93E9657A-737E-4705-A0E5-01F9E9110261@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201410301554.03504.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 30 Oct 2014 15:58:57 -0400 (EDT) Cc: Warren Block , Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 19:58:59 -0000 On Wednesday, October 29, 2014 8:47:42 pm Paul Mather wrote: > On Oct 29, 2014, at 8:14 PM, Warren Block wrote: > > > On Wed, 29 Oct 2014, Walter Hop wrote: > > > >> I noticed that the motd has been updated, which is great. > >> https://svnweb.freebsd.org/base/releng/10.1/etc/motd?revision=272461&view=markup > >> > >> However, the following line could be improved: > >> Show the version of FreeBSD installed: uname -a > >> > >> I would recommend changing the line to: > >> Show the version of FreeBSD installed: freebsd-version > >> > >> Users often confuse the kernel version (uname -a) with the actual FreeBSD version from the freebsd-version(1) command. Because of this, people needlessly worry whether their system was updated correctly after freebsd- update has run, because they erroneously check this with ?uname -a?. A small motd change will hopefully prevent that. > > > > Sorry, I don't understand the source of confusion. > > The potential confusion arises because freebsd-version agrees with > freebsd-update, but uname doesn't always. If you track FreeBSD via > freebsd-update, uname only gets bumped when the kernel is updated. If > you want to know which version of FreeBSD you're running, which command > is more accurate: freebsd-version or uname -a? I would argue the former > (freebsd-version). A fact I continue to bemoan. :( > If you track FreeBSD via source updates, freebsd-version and uname -a > match each other, so long as you update kernel and world together. > > Consider the system below, updated using freebsd-update after the last > advisory causing an update to 10.0-RELEASE: > > ===== > % freebsd-version > 10.0-RELEASE-p11 > % uname -a > FreeBSD chumby.dlib.vt.edu 10.0-RELEASE-p10 FreeBSD 10.0-RELEASE-p10 #0: Mon Oct 20 12:38:37 UTC 2014 root@amd64- builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 > ===== The problem, of course, is that if you are obtaining the version for a bug report or an e-mail to the lists, the latter output provides more details (e.g. architecture as Warren noted) even though it is stale due to implementation details of freebsd-update. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 20:03:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DEAC8738; Thu, 30 Oct 2014 20:03:13 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 90B0ABEA; Thu, 30 Oct 2014 20:03:13 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9UK3BSI055334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 Oct 2014 14:03:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9UK3BoK055331; Thu, 30 Oct 2014 14:03:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 30 Oct 2014 14:03:11 -0600 (MDT) From: Warren Block To: John Baldwin Subject: Re: Small motd nit in 10.1 In-Reply-To: <201410301554.03504.jhb@freebsd.org> Message-ID: References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> <93E9657A-737E-4705-A0E5-01F9E9110261@gromit.dlib.vt.edu> <201410301554.03504.jhb@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Thu, 30 Oct 2014 14:03:11 -0600 (MDT) Cc: freebsd-stable@freebsd.org, Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 20:03:14 -0000 On Thu, 30 Oct 2014, John Baldwin wrote: > On Wednesday, October 29, 2014 8:47:42 pm Paul Mather wrote: >> >> The potential confusion arises because freebsd-version agrees with >> freebsd-update, but uname doesn't always. If you track FreeBSD via >> freebsd-update, uname only gets bumped when the kernel is updated. If >> you want to know which version of FreeBSD you're running, which command >> is more accurate: freebsd-version or uname -a? I would argue the former >> (freebsd-version). > > A fact I continue to bemoan. :( > >> If you track FreeBSD via source updates, freebsd-version and uname -a >> match each other, so long as you update kernel and world together. >> >> Consider the system below, updated using freebsd-update after the last >> advisory causing an update to 10.0-RELEASE: >> >> ===== >> % freebsd-version >> 10.0-RELEASE-p11 >> % uname -a >> FreeBSD chumby.dlib.vt.edu 10.0-RELEASE-p10 FreeBSD 10.0-RELEASE-p10 #0: Mon > Oct 20 12:38:37 UTC 2014 root@amd64- > builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >> ===== > > The problem, of course, is that if you are obtaining the version for a bug > report or an e-mail to the lists, the latter output provides more details > (e.g. architecture as Warren noted) even though it is stale due to > implementation details of freebsd-update. There is room on that line to show both: Show details of the FreeBSD installation: uname -a ; freebsd-version Or some combination like that. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 20:12:59 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02A309E8; Thu, 30 Oct 2014 20:12:59 +0000 (UTC) Received: from mail-in-12.arcor-online.net (mail-in-12.arcor-online.net [151.189.21.52]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7425CE8; Thu, 30 Oct 2014 20:12:58 +0000 (UTC) Received: from mail-in-20-z2.arcor-online.net (mail-in-20-z2.arcor-online.net [151.189.8.85]) by mx.arcor.de (Postfix) with ESMTP id DF5B326413; Thu, 30 Oct 2014 21:12:49 +0100 (CET) Received: from mail-in-07.arcor-online.net (mail-in-07.arcor-online.net [151.189.21.47]) by mail-in-20-z2.arcor-online.net (Postfix) with ESMTP id E0A576FA387; Thu, 30 Oct 2014 21:12:49 +0100 (CET) X-Greylist: Passed host: 188.98.183.190 X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-07.arcor-online.net ABCAD107F3D X-Greylist: Passed host: 188.98.183.190 X-Greylist: Passed host: 188.98.183.190 X-Greylist: Passed host: 188.98.183.190 Received: from lorvorc.mips.inka.de (dslb-188-098-183-190.188.098.pools.vodafone-ip.de [188.98.183.190]) by mail-in-07.arcor-online.net (Postfix) with ESMTPS id ABCAD107F3D; Thu, 30 Oct 2014 21:12:49 +0100 (CET) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.9/8.14.7) with ESMTP id s9UKCnck034448; Thu, 30 Oct 2014 21:12:49 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.14.9/8.14.9/Submit) id s9UKCm2L034447; Thu, 30 Oct 2014 21:12:48 +0100 (CET) (envelope-from naddy) Date: Thu, 30 Oct 2014 21:12:48 +0100 From: Christian Weisgerber To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 Message-ID: <20141030201248.GA34433@lorvorc.mips.inka.de> References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> <20141030133112.GA26588@lorvorc.mips.inka.de> <545270EE.3090405@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <545270EE.3090405@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 20:12:59 -0000 Jean-Sébastien Pédron: > >>> Well, terminating the old X server, updating xf86-video-ati to 7.5.0, > >>> and re-starting the X server led to this failure: > >> > >> What do you mean by "old X server"? xserver 1.7.7 and xf86-video-ati 6.14.6? > > > > No, just the instance I had running before: X server 1.12.4 and > > xf86-video-ati 7.2.0. > > Ok. Does the problem still happen now? What do you mean? Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was a one-time event. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 22:21:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1619E577; Thu, 30 Oct 2014 22:21:51 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28566B84; Thu, 30 Oct 2014 22:21:50 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id m15so5283609wgh.21 for ; Thu, 30 Oct 2014 15:21:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Xpjo/4QzG6TTTB88ph/ZJFaLOesEOGNVTfDYRyybFN0=; b=Z5BMc/Zqhz4m1U1LaWYrSZ6+yxZLD0dMSkn8cI/9w7mMrDRqOpQ5yNvzQYIBbSqNKg GCIIySqKO5WJD3lG96IAEuCQbFPkRk0zxNQyFdTVO611R3Z6aeT6jXvjr8J68hjRwWgO 9ke6g/oOmKyLiYwE4k+49UtQAUb6ChF2Qwm80Xn3YkTWmRiNy3z3BQdYOhI45f+OsS3K UBTr3N7IYJXL9ATUPOoL2bDrtiW2v82wwnexkmB460m+4/8J+eYhik6XVERvhYzgIq9t Zk/4TzY0QSiDLSV04XxWZkGJ9SKm2zJpmwSogTDNNGoY1d6uDc5bdhbi39GyycgFxdf3 xY0Q== X-Received: by 10.194.133.229 with SMTP id pf5mr23937328wjb.73.1414707708104; Thu, 30 Oct 2014 15:21:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Thu, 30 Oct 2014 15:21:27 -0700 (PDT) In-Reply-To: <545270A7.6030807@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> From: Miguel Clara Date: Thu, 30 Oct 2014 22:21:27 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 22:21:51 -0000 On Thu, Oct 30, 2014 at 5:08 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 30.10.2014 14:21, Miguel Clara wrote: > > Fro the record, with just remove 7.5 and install 7.2 I get this in gdb: > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 14:13:25 201= 4 > > (=3D=3D) Using config directory: "/usr/local/etc/X11/xorg.conf.d" > > (=3D=3D) Using system config directory "/usr/local/share/X11/xorg.conf.= d" > > [New Thread 803406400 (LWP 101070/Xorg)] > > (II) [KMS] Kernel modesetting enabled. > > > > Program received signal SIGSEGV, Segmentation fault. > > (...) > > (gdb) bt > > #0 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at > > xf86Crtc.c:1829 > > (...) > > > > Xorg.0.log --> http://filebin.net/ovtqn7qt19/Xorg.0.log > > Ok, so the problem is exactly the same with either 7.2.0 and 7.5.0. I > "prefer" that, because I didn't see the difference between both versions > in this particular code :) > > We'll add the fix from xserver 1.15 in our xorg-server port, it should > fix that crash. > > What I don't understand is how could this could work before. Are you > sure you had xf86-video-ati 7.2.0 installed? Can you check your logs > (/var/log/messages) and look for lines like these: > pkg-static: pkg-1.3.8_3 deinstalled > pkg-static: pkg-1.4.0.a3 installed > > The program could be "pkg" or "pkg-static". And it should say that a > package was installed/deinstalled/upgraded, with the version of the > package. Can you check the first time you installed xf86-video-ati 7.5.0 > if it actually replaced 7.2.0 or something else? > > [miguelc@hpbsd]~% cat /var/log/messages | grep xf86 Oct 28 18:09:38 hpbsd pkg-static: xf86-video-ati-7.5.0 deinstalled Oct 28 18:09:39 hpbsd pkg-static: xf86-video-ati-7.5.0 installed Oct 30 14:09:33 hpbsd pkg: xf86-video-ati-7.5.0 deinstalled Oct 30 14:09:54 hpbsd pkg: xf86-video-ati-7.2.0_4 installed [miguelc@hpbsd]~% bzcat /var/log/messages.1.bz2 | grep xf86 Oct 27 13:58:24 hpbsd pkg: xf86-video-ati-7.2.0_4 deinstalled Oct 27 13:58:24 hpbsd pkg-static: xf86-video-ati-7.5.0 installed However I don't understand why you say "it worked before" cause what I've reported before and now is that It didn't work (with ATI) I still have the old xorg log, from back when I reported this in the list, if I'm not mistaken this is the one: http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log So It was not working with ATI even before 7.2,a and with 7.2 I also can't get xorg to start, although I was getting a black screen at some point, but the log states Xorg crashed! maybe in this new report I've somehow gave the impression that It worked, but I only works with the Intel card! Or, I'm not getting what you mean by "it worked" :P -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Thu Oct 30 22:44:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88CC4CA1; Thu, 30 Oct 2014 22:44:40 +0000 (UTC) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "khavrinen.csail.mit.edu", Issuer "Client CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 30D58D8B; Thu, 30 Oct 2014 22:44:40 +0000 (UTC) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.9/8.14.9) with ESMTP id s9UMicgI034127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Thu, 30 Oct 2014 18:44:38 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.9/8.14.9/Submit) id s9UMic4t034124; Thu, 30 Oct 2014 18:44:38 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <21586.48982.64913.250497@khavrinen.csail.mit.edu> Date: Thu, 30 Oct 2014 18:44:38 -0400 From: Garrett Wollman To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org Subject: Definite NFS bug X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 30 Oct 2014 18:44:38 -0400 (EDT) Cc: rmacklem@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 22:44:40 -0000 Like many other users, I upgrade my FreeBSD servers by NFS-mounting /usr/src and /usr/obj from a shared build server.[1] Since I upgraded the build server to 9.3, clients running 9.3 kernels have been randomly erroring out during installkernel and installworld. Today I had some time to look more closely into this and found that the error is definitely coming from the server: at some point, it just randomly starts returning errors to client ACCESS and GETATTR operations. The errors are a mix of NFS3ERR_IO and NFS3ERR_ACCES, but there is nothing on the server to indicate any kind of error, and restarting the operation on the client causes it to fail in a different place. With enough patients and restarts, it's possible to complete the installation in just four or five passes. Needless to say this is a bit worrying. Strangely, 9.1 and 9.2 clients don't see this issue at all; it's only 9.3 clients that break. It's easy to reproduce, just 'cd /usr/sc && find . -type f >/dev/null'. It does not seem to depend on the client NFS version (3 or 4) or implementation ("old" or "new"). I haven't tried the "old" server yet -- I'll need to figure out how to do that first. If anyone is willing to help debug this, I can share a packet trace, but I don't think it's very informative. Also, if anyone has a good dtrace script that I could run on the server that would report what's going on when that first NFS3ERR_IO is returned, that would be great. -GAWollman [1] I'd run my own freebsd-update server but unfortunately it is too tied to building things that look like official FreeBSD security updates, and isn't really designed for (e.g.) updating kernels when we change a configuration option. It also doesn't have any obvious knobs for building with anything other than a default {make,src}.conf. And with a pkg-able base just around the corner I don't really want to put much effort into making freebsd-update do what I want. NFS, on the other hand, is a big deal and so I need to track down and fix these bugs. From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 00:32:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D59C9227; Fri, 31 Oct 2014 00:32:32 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EE6EA1A; Fri, 31 Oct 2014 00:32:32 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9V0WTuw061868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 Oct 2014 18:32:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9V0WSLK061865; Thu, 30 Oct 2014 18:32:28 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 30 Oct 2014 18:32:28 -0600 (MDT) From: Warren Block To: John Baldwin Subject: Re: Small motd nit in 10.1 In-Reply-To: Message-ID: References: <8C81A636-D2B5-4EFB-9EA3-58E88E16CA94@spam.lifeforms.nl> <93E9657A-737E-4705-A0E5-01F9E9110261@gromit.dlib.vt.edu> <201410301554.03504.jhb@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Thu, 30 Oct 2014 18:32:30 -0600 (MDT) Cc: freebsd-stable@freebsd.org, Walter Hop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 00:32:32 -0000 On Thu, 30 Oct 2014, Warren Block wrote: > There is room on that line to show both: > > Show details of the FreeBSD installation: uname -a ; freebsd-version > > Or some combination like that. Actually, I think the output from 'freebsd-version ; uname -a' is less ambiguous. From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 01:31:36 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C60ECDB; Fri, 31 Oct 2014 01:31:36 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 41141F37; Fri, 31 Oct 2014 01:31:35 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0EAHzlUlSDaFve/2dsb2JhbABcDoQwgwLRaAKBMgEBAQEBfYQCAQEBAwEjBFIFFhgCAg0ZAlkGiEsJtVWUaAEBAQEGAQEBAQEBHIEsjyEONAeCd4FUBZ8hjWaHLYM4XCGBN0CBAwEBAQ X-IronPort-AV: E=Sophos;i="5.07,290,1413259200"; d="scan'208";a="163577126" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 30 Oct 2014 21:31:34 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 11382AE92D; Thu, 30 Oct 2014 21:31:34 -0400 (EDT) Date: Thu, 30 Oct 2014 21:31:34 -0400 (EDT) From: Rick Macklem To: Garrett Wollman Message-ID: <1902145956.2676513.1414719094052.JavaMail.root@uoguelph.ca> In-Reply-To: <21586.48982.64913.250497@khavrinen.csail.mit.edu> Subject: Re: Definite NFS bug MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org, rmacklem@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 01:31:36 -0000 Garrett Wollman wrote: > Like many other users, I upgrade my FreeBSD servers by NFS-mounting > /usr/src and /usr/obj from a shared build server.[1] Since I > upgraded > the build server to 9.3, clients running 9.3 kernels have been > randomly erroring out during installkernel and installworld. Today I > had some time to look more closely into this and found that the error > is definitely coming from the server: at some point, it just randomly > starts returning errors to client ACCESS and GETATTR operations. The > errors are a mix of NFS3ERR_IO and NFS3ERR_ACCES, but there is > nothing > on the server to indicate any kind of error, and restarting the > operation on the client causes it to fail in a different place. With > enough patients and restarts, it's possible to complete the > installation in just four or five passes. > > Needless to say this is a bit worrying. Strangely, 9.1 and 9.2 > clients don't see this issue at all; it's only 9.3 clients that > break. > > It's easy to reproduce, just 'cd /usr/sc && find . -type f > >/dev/null'. > It does not seem to depend on the client NFS version (3 or 4) or > implementation ("old" or "new"). I haven't tried the "old" server > yet > -- I'll need to figure out how to do that first. > Well, I took a quick look and, if I got it correct, there is one single line change in the "old" client between 9.2 and 9.3, which defined an otherwise unused mount flag called NFSMNT_NONCONTIGWR. (It is only used by the new client when "nocontigwr" is specified.) However, there was some fairly extensive changes done (mostly by mav@) to the kernel rpc (sys/rpc), which is used by both clients and both servers. Most of these changes were committed to stable/9 as r261057, r261058. If you could build a kernel from stable/9 just prior to r261057 and see if that client runs into the problem, it could help determine if these changes are causing the problem. Alternately, running the 9.3 system with a 9.2 sys/rpc (if it links/runs), that could also help see if the kernel rpc is the culprit. (You can load the kernel rpc as a module, but it's linked into most kernels.) If it doesn't turn out to be in the kernel rpc, my next guess would be changes to the net device driver (to check for this you could use a different type of hardware device or the 9.2 driver on the 9.3 system. maybe?). The "new" client has some changes 9.2->9.3, but since nothing changed for the "old" client and you see the problem with the "old" one, I think the NFS client is not the culprit. rick > If anyone is willing to help debug this, I can share a packet trace, > but I don't think it's very informative. Also, if anyone has a good > dtrace script that I could run on the server that would report what's > going on when that first NFS3ERR_IO is returned, that would be great. > > -GAWollman > > [1] I'd run my own freebsd-update server but unfortunately it is too > tied to building things that look like official FreeBSD security > updates, and isn't really designed for (e.g.) updating kernels when > we > change a configuration option. It also doesn't have any obvious > knobs > for building with anything other than a default {make,src}.conf. > And with a pkg-able base just around the corner I don't really want > to > put much effort into making freebsd-update do what I want. NFS, on > the other hand, is a big deal and so I need to track down and fix > these bugs. > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 01:49:49 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 023EEED2; Fri, 31 Oct 2014 01:49:49 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9ABCABC; Fri, 31 Oct 2014 01:49:48 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ar0EAB/qUlSDaFve/2dsb2JhbABcDoNUWASDAsoRCoZ5VAKBMgEBAQEBfYQCAQEBAwEBAQEgBCcgCwUWGAICDRkCKQEJJgYIBwQBHASIFwkNtUyUZgEBAQEGAQEBAQEBARuBLI8SAQENDjQHgneBVAWWWoQShDU8jSqHLYM4XCEvB4EBBxcigQMBAQE X-IronPort-AV: E=Sophos;i="5.07,290,1413259200"; d="scan'208";a="163580651" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 30 Oct 2014 21:49:47 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 3E53FB4082; Thu, 30 Oct 2014 21:49:47 -0400 (EDT) Date: Thu, 30 Oct 2014 21:49:47 -0400 (EDT) From: Rick Macklem To: Garrett Wollman Message-ID: <928219131.2682604.1414720187244.JavaMail.root@uoguelph.ca> In-Reply-To: <1902145956.2676513.1414719094052.JavaMail.root@uoguelph.ca> Subject: Re: Definite NFS bug MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.209] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org, rmacklem@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 01:49:49 -0000 I wrote: > Garrett Wollman wrote: > > Like many other users, I upgrade my FreeBSD servers by NFS-mounting > > /usr/src and /usr/obj from a shared build server.[1] Since I > > upgraded > > the build server to 9.3, clients running 9.3 kernels have been > > randomly erroring out during installkernel and installworld. Today > > I > > had some time to look more closely into this and found that the > > error > > is definitely coming from the server: at some point, it just > > randomly > > starts returning errors to client ACCESS and GETATTR operations. > > The > > errors are a mix of NFS3ERR_IO and NFS3ERR_ACCES, but there is > > nothing > > on the server to indicate any kind of error, and restarting the > > operation on the client causes it to fail in a different place. > > With > > enough patients and restarts, it's possible to complete the > > installation in just four or five passes. > > > > Needless to say this is a bit worrying. Strangely, 9.1 and 9.2 > > clients don't see this issue at all; it's only 9.3 clients that > > break. > > > > It's easy to reproduce, just 'cd /usr/sc && find . -type f > > >/dev/null'. > > It does not seem to depend on the client NFS version (3 or 4) or > > implementation ("old" or "new"). I haven't tried the "old" server > > yet > > -- I'll need to figure out how to do that first. > > Oh, and it wasn't clear to me if you are seeing this on a 9.3 server only? (If you get the same outcome testing against an older server, then it seems it is a client side issue.) If that is the case, I'd suggest you try a pre-r261056 (one of the changes was r261056, not r261057) stable/9 kernel. At a closer look, most of the kernel rpc changes are for the server side. (Most of the client side commits just change the copyright, but there are a couple of client side changes beyond that.) > Well, I took a quick look and, if I got it correct, there is one > single > line change in the "old" client between 9.2 and 9.3, which defined > an otherwise unused mount flag called NFSMNT_NONCONTIGWR. (It is > only used by the new client when "nocontigwr" is specified.) > > However, there was some fairly extensive changes done (mostly by > mav@) > to the kernel rpc (sys/rpc), which is used by both clients and both > servers. > Most of these changes were committed to stable/9 as r261057, r261058. > If you could build a kernel from stable/9 just prior to r261057 and > see > if that client runs into the problem, it could help determine if > these > changes are causing the problem. > Alternately, running the 9.3 system with a 9.2 sys/rpc (if it > links/runs), > that could also help see if the kernel rpc is the culprit. (You can > load the kernel rpc as a module, but it's linked into most kernels.) > > If it doesn't turn out to be in the kernel rpc, my next guess would > be changes to the net device driver (to check for this you could use > a different type of hardware device or the 9.2 driver on the 9.3 > system. maybe?). > > The "new" client has some changes 9.2->9.3, but since nothing changed > for the "old" client and you see the problem with the "old" one, I > think the NFS client is not the culprit. > > rick > > > If anyone is willing to help debug this, I can share a packet > > trace, > > but I don't think it's very informative. Also, if anyone has a > > good > > dtrace script that I could run on the server that would report > > what's > > going on when that first NFS3ERR_IO is returned, that would be > > great. > > > > -GAWollman > > > > [1] I'd run my own freebsd-update server but unfortunately it is > > too > > tied to building things that look like official FreeBSD security > > updates, and isn't really designed for (e.g.) updating kernels when > > we > > change a configuration option. It also doesn't have any obvious > > knobs > > for building with anything other than a default {make,src}.conf. > > And with a pkg-able base just around the corner I don't really want > > to > > put much effort into making freebsd-update do what I want. NFS, on > > the other hand, is a big deal and so I need to track down and fix > > these bugs. > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 09:01:10 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 142FBC7B; Fri, 31 Oct 2014 09:01:10 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C77D2ED2; Fri, 31 Oct 2014 09:01:09 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xk84x-000NZ0-QM; Fri, 31 Oct 2014 10:01:07 +0100 Message-ID: <54534FCF.7070400@FreeBSD.org> Date: Fri, 31 Oct 2014 10:01:03 +0100 From: =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Christian Weisgerber Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> <20141030133112.GA26588@lorvorc.mips.inka.de> <545270EE.3090405@FreeBSD.org> <20141030201248.GA34433@lorvorc.mips.inka.de> In-Reply-To: <20141030201248.GA34433@lorvorc.mips.inka.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dG9i3dEFlp6m4rC6pRQWvMIHOHB0dgH6O" Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 09:01:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dG9i3dEFlp6m4rC6pRQWvMIHOHB0dgH6O Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 30.10.2014 21:12, Christian Weisgerber wrote: > What do you mean? Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was > a one-time event. Yes, but I was wondering if your problem was still there from time to time (ie. not related to the update). --=20 Jean-S=E9bastien P=E9dron --dG9i3dEFlp6m4rC6pRQWvMIHOHB0dgH6O Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU0/TXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMzCkQAIjHWwgszJ8vLt8NcVfmrK/u r2zD9mlaU6J+5S1RffKGDRI3w/dxlWXTP//Xw3CGDiNme1c100KjEuDhRsW8n29X YPRriwdYrvz755KqLg2V3BED2oPduzSBGtyOQvTwxwmwvusGo3uyBV8QY1GDD0Ou 5zyHwhu6I+auNcmLzEjgX2SFbudk20tiWVuNuFA3Slq9vZEroB0H9dZySIPSukfq fILhC0bNvzrUw3YtcTN4RL+cAgfV+8MZ1WoSO3Y0bJXI7+YVvjuv6ULa0s/Q6v8q IauuVlvGX5ebTVUB4MzI0VXoeozWEI37lY1SWQb/Z0DYPBjVLvwapHBTcQqVaorm 1PsLtRt1A6Y0wcQ9FObT6rD8aPltan/pdornMto8aYXBuZV3irxgMIbrTqlzW+SG WN596o32ENBztDgOD6U8W9Wt+U+bt4WTB0L/XX9nmEwlJKt32147WTTtp/O7xf+f /kKlkxTpbNnLfPWwA+l9ELdJ8mbqdvjJ+7axnjd5uN9hvAGnfYb3W5SkI7OzB0ri wR/TiA7+q955zgeiyTK3lGBtC8GKIA/6ZdgjlZ8g4P/d7WKdC5736mCmgJE8suAI UAmJImuTMmH/GELAWSD8aN4behDpBHdnKiETGNOE6E0wCv6BZc4V75Vcg16HK0Qv XFxAeP/bsrG+RrX0zKsh =G798 -----END PGP SIGNATURE----- --dG9i3dEFlp6m4rC6pRQWvMIHOHB0dgH6O-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 09:08:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7755FD7; Fri, 31 Oct 2014 09:08:14 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 80775F5C; Fri, 31 Oct 2014 09:08:14 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xk8Bo-000NdH-Mg; Fri, 31 Oct 2014 10:08:12 +0100 Message-ID: <54535178.8040706@FreeBSD.org> Date: Fri, 31 Oct 2014 10:08:08 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GBFBCCBoJKD4DgBuUEPEllbKTwbTixwqT" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 09:08:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GBFBCCBoJKD4DgBuUEPEllbKTwbTixwqT Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 30.10.2014 23:21, Miguel Clara wrote: >> What I don't understand is how could this could work before. Are you >> sure you had xf86-video-ati 7.2.0 installed? >=20 > However I don't understand why you say "it worked before" cause what I'= ve > reported before and now is that It didn't work (with ATI) >=20 > I still have the old xorg log, from back when I reported this in the li= st, > if I'm not mistaken this is the one: > http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log >=20 > So It was not working with ATI even before 7.2,a and with 7.2 I also ca= n't > get xorg to start, although I was getting a black screen at some point,= but > the log states Xorg crashed! >=20 > maybe in this new report I've somehow gave the impression that It worke= d, > but I only works with the Intel card! That's my fault, I understood that it was working, then you upgraded to 7.5.0 and X broke. But no, as you say, your older log shows that the same problem existed before the upgrade. Sorry :) Could you please download the following file: https://raw.githubusercontent.com/freebsd/freebsd-ports-graphics/xserver-= 1.14/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c Put it here: /usr/ports/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.= c And rebuild xorg-server 1.12 with WITH_DEBUG=3D1 and test again (with xf86-video-ati 7.5.0 installed)? --=20 Jean-S=C3=A9bastien P=C3=A9dron --GBFBCCBoJKD4DgBuUEPEllbKTwbTixwqT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU1F8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMtuEP/il3irl6Rk4cNRDM0rwFaIfv vrqyHKIBRpPjdE8x+88Yh+bSd4UjUt7hg4I4Z0wP+gCMY38g3k5tNth6T466RN5t xOc2s/hD/MPYHiPvKHaAfugVWufzNNNesWYfYqcG0O0Abe0N1GLFxvXSUNkuBQS5 LhR2iyEWbvzEbm20QtwUP0H/mFbfspbCGyFg2t3PZLul5PBIa13vPhSThAqN1SWO DIJcQ3AZ8pKUua2pQJZulTuqAcqHjfzA3Lb/v8ey/PkB4mwlATb7xPPHPLZK5H9C ee2ogR8l4i18LZgf0Ah2Ud8BZmbh3LdC14OSu1kGX+E4wlLtfj1OlE0gIaJgRxez Lx0P7zKpljmyN7eO2h8mpPqiWdSzsLBGAenKlLEwPNCYJjjO+x2xJR9QP10U2f4Z 6VeWJcEOzL5fbbO1dOF/XIeu2r9o6J8V1l6vEZQzXEH/U5KyGky9E2Y8AYyrqFjh FFVm9Mvd1lR2nEng237oq8kwFR21W4tx4AU9cmRr/tXz94SFiq0drZL1lBcvM/SJ RKqyzVuqzWRy/FxlaNl2AUA64PqtiX0eA/7YkuVOkT1VYo/BnTjFoK9ZW0q+oekB 33sOJHrZjMmwqxIVKa/yVQOL8ZKB4KuNonYfROO4nX34q7JTwAqVhCdbgFHiUX82 HI2EaeLww6UGEOwzl0Bo =BPMh -----END PGP SIGNATURE----- --GBFBCCBoJKD4DgBuUEPEllbKTwbTixwqT-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 10:35:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D3C8CFE; Fri, 31 Oct 2014 10:35:02 +0000 (UTC) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 813CCC4B; Fri, 31 Oct 2014 10:35:01 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id n12so804534wgh.41 for ; Fri, 31 Oct 2014 03:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CsU6gErPPwuxAPojFazdlqxXdbcVqsvo2ZjoiJMAsGE=; b=ej2wGTtJK0A5bJSjhu845WAZQPmt/GLD4gMnTdU5w6j/n2NeG8xTyFZlb+166BAXxr YWdTHz7EIb4MBEXAmEPv7J86gCp4m1gEPB29JDtmhTpn4NtoFrAWgHR7/xiDaHhO1kZ3 ZbDuJk0gBWR7bMz64N9W73DW8Kbe+C3KhW20nmg6OuGxE020/u+WTHw57tEXZOwBAA3K KHrBjnIu/hmnxoh5+mjxkaad41R/KGrwgJp8iuJ6CDBkpuqpq70rQFkdH8dHbkOGsuVA En3351SRTTj/MmR5BBlB50Pvt7g3MePrl1ogKtPe/jBd+lSwmOLvjme+8CCOBjRiaimP TZBw== X-Received: by 10.180.12.136 with SMTP id y8mr2908728wib.73.1414751699591; Fri, 31 Oct 2014 03:34:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 31 Oct 2014 03:34:39 -0700 (PDT) In-Reply-To: <54535178.8040706@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> From: Miguel Clara Date: Fri, 31 Oct 2014 10:34:39 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 10:35:02 -0000 On Fri, Oct 31, 2014 at 9:08 AM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 30.10.2014 23:21, Miguel Clara wrote: > >> What I don't understand is how could this could work before. Are you > >> sure you had xf86-video-ati 7.2.0 installed? > > > > However I don't understand why you say "it worked before" cause what I'= ve > > reported before and now is that It didn't work (with ATI) > > > > I still have the old xorg log, from back when I reported this in the > list, > > if I'm not mistaken this is the one: > > http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log > > > > So It was not working with ATI even before 7.2,a and with 7.2 I also > can't > > get xorg to start, although I was getting a black screen at some point, > but > > the log states Xorg crashed! > > > > maybe in this new report I've somehow gave the impression that It worke= d, > > but I only works with the Intel card! > > That's my fault, I understood that it was working, then you upgraded to > 7.5.0 and X broke. But no, as you say, your older log shows that the > same problem existed before the upgrade. Sorry :) > > Could you please download the following file: > > https://raw.githubusercontent.com/freebsd/freebsd-ports-graphics/xserver-= 1.14/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c > > Put it here: > /usr/ports/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.= c > > And rebuild xorg-server 1.12 with WITH_DEBUG=3D1 and test again (with > xf86-video-ati 7.5.0 installed)? > > Ok using xorg-1.12, and xf86-video-ati-7.5 (both WITH_DEBUG) Still fails, sudo gdb Xorg Xorg.core shows: [....] #0 0x000000080205ccaa in thr_kill () from /lib/libc.so.7 #1 0x0000000802133f09 in abort () from /lib/libc.so.7 #2 0x000000000062e4be in OsAbort () at utils.c:1198 #3 0x00000000004a6880 in ddxGiveUp (error=3DEXIT_ERR_ABORT) at xf86Init.c:1009 #4 0x00000000004a6998 in AbortDDX (error=3DEXIT_ERR_ABORT) at xf86Init.c:1= 053 #5 0x0000000000637ae6 in AbortServer () at log.c:476 #6 0x00000000006367fd in FatalError (f=3D0x659396 "Caught signal %d (%s). Server aborting\n") at log.c:611 #7 0x000000000062b9d8 in OsSigHandler (signo=3D11, sip=3D0x7fffffffe570, unused=3D0x7fffffffe200) at osinit.c:146 #8 0x00000008010b84f6 in swapcontext () from /lib/libthr.so.3 #9 0x00000008010b80ec in sigaction () from /lib/libthr.so.3 #10 #11 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at xf86Crtc.c:1829 #12 0x00000000004eb1ea in xf86SetScrnInfoModes (scrn=3D0x803512400) at xf86Crtc.c:1843 #13 0x00000000004ebf13 in xf86InitialConfiguration (scrn=3D0x803512400, canGrow=3D1) at xf86Crtc.c:2503 #14 0x000000080474153e in drmmode_pre_init (pScrn=3D0x803512400, drmmode=3D0x8034c7258, cpp=3D4) at drmmode_display.c:1757 #15 0x000000080473c89a in RADEONPreInit_KMS (pScrn=3D0x803512400, flags=3D0= ) at radeon_kms.c:946 #16 0x00000000004a4e19 in InitOutput (pScreenInfo=3D0x8acdb0, argc=3D1, argv=3D0x7fffffffec18) at xf86Init.c:586 #17 0x0000000000424c66 in main (argc=3D1, argv=3D0x7fffffffec18, envp=3D0x7fffffffec28) at main.c:20 last lines of Xorg.0.log tail -20 /var/log/Xorg.0.log [ 77453.777] ABI class: X.Org Video Driver, version 12.1 [ 77453.777] (II) RADEON(0): KMS Color Tiling: enabled [ 77453.777] (II) RADEON(0): KMS Color Tiling 2D: enabled [ 77453.777] (II) RADEON(0): KMS Pageflipping: enabled [ 77453.777] (II) RADEON(0): SwapBuffers wait for vsync: enabled [ 77453.778] (WW) RADEON(0): No outputs definitely connected, trying again... [ 77453.778] (WW) RADEON(0): Unable to find connected outputs - setting 1024x768 initial framebuffer [ 77453.778] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [ 77453.778] Segmentation fault at address 0x0 [ 77453.778] Fatal server error: [ 77453.778] Caught signal 11 (Segmentation fault). Server aborting [ 77453.778] [ 77453.778] Please consult the The X.Org Foundation support at http://wiki.x.org for help. -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 10:46:48 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 748AE826; Fri, 31 Oct 2014 10:46:48 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 62C67D9E; Fri, 31 Oct 2014 10:46:48 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id CCBA24D6; Fri, 31 Oct 2014 10:46:47 +0000 (UTC) Date: Fri, 31 Oct 2014 10:46:37 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, hselasky@FreeBSD.org Message-ID: <435710951.16.1414752407546.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_stable_10 #917 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: FAILURE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 10:46:48 -0000 See Changes: [hselasky] MFC r264801, r264802, r264934, r273181, r273216 and r273252: Add more USB IDs. [hselasky] MFC r269575, r269576 and r269578: - Add a second Huawei SCSI eject command as USB mode switch config files sometimes use one or the other. Maybe newer Huawei modems switched. - Return USB_ERR_INVAL if the eject method is not known. PR:=09=09145319 [hselasky] MFC r264923: Remove device type from the uftdi_devs table, enhance the jtag-skip feature= . [hselasky] MFC r269569: Remove unused defines. Fix some device_printf's that were missing '\n' at the end or had spelling errors. PR:=09=09145319 [hselasky] MFC r271159, r271168 and r271680: Add USB LED driver for the Dream Cheeky WebMail Notifier. [hselasky] MFC r273867: Fix compile warning by removing unused variable. Sponsored by:=09Mellanox Technologies [hselasky] MFC r273593: Update the network interface baudrate integer according to the actual line rate. Sponsored by:=09Mellanox Technologies ------------------------------------------ [...truncated 280521 lines...] --- vmm_host.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_usb --- --- xhci.o --- --- all_subdir_sound --- --- snd_maestro.ko.debug --- ld -d -warn-common -r -d -o snd_maestro.ko.debug maestro.o --- all_subdir_usb --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_sound --- ctfmerge -L VERSION -g -o snd_maestro.ko.debug maestro.o :> export_syms awk -f snd_maestro.ko.debug export_syms | xargs -J% objcopy % s= nd_maestro.ko.debug --- snd_maestro.ko.symbols --- objcopy --only-keep-debug snd_maestro.ko.debug snd_maestro.ko.symbols --- snd_maestro.ko --- objcopy --strip-debug --add-gnu-debuglink=3Dsnd_maestro.ko.symbols snd_maes= tro.ko.debug snd_maestro.ko --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_host.o --- all_subdir_sound --- =3D=3D=3D> sound/driver/maestro3 (all) --- all_subdir_vmware --- =3D=3D=3D> vmware (all) --- _sub.all --- =3D=3D=3D> vmware/vmxnet3 (all) --- all_subdir_sound --- --- maestro3.o --- cc -O2 -pipe -Wall -DM3_DEBUG_LEVEL=3D-1 -fno-strict-aliasing -Werror -D_= KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/= obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-poi= nter -mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dk= ernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwin= d-tables -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qu= nused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs= -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-= qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs= -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empt= y-body -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_vmware --- --- if_vmx.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_vmm --- --- vmm_dev.o --- ctfconvert -L VERSION -g vmm_dev.o --- vmm_instruction_emul.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c ctfconvert -L VERSION -g vmm_instruction_emul.o --- vmm_ioport.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_usb --- ctfconvert -L VERSION -g xhci.o --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_ioport.o --- vmm_lapic.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_usb --- --- xhci_pci.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_sound --- ctfconvert -L VERSION -g maestro3.o --- snd_maestro3.ko.debug --- ld -d -warn-common -r -d -o snd_maestro3.ko.debug maestro3.o ctfmerge -L VERSION -g -o snd_maestro3.ko.debug maestro3.o :> export_syms awk -f snd_maestro3.ko.debug export_syms | xargs -J% objcopy % = snd_maestro3.ko.debug --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_lapic.o --- vmm_mem.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_sound --- --- snd_maestro3.ko.symbols --- objcopy --only-keep-debug snd_maestro3.ko.debug snd_maestro3.ko.symbols --- snd_maestro3.ko --- objcopy --strip-debug --add-gnu-debuglink=3Dsnd_maestro3.ko.symbols snd_mae= stro3.ko.debug snd_maestro3.ko =3D=3D=3D> sound/driver/neomagic (all) --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_mem.o --- vmm_msr.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_sound --- --- neomagic.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_usb --- ctfconvert -L VERSION -g xhci_pci.o --- xhci.ko.debug --- ld -d -warn-common -r -d -o xhci.ko.debug xhci_pci.o xhci.o ctfmerge -L VERSION -g -o xhci.ko.debug xhci_pci.o xhci.o --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_msr.o --- all_subdir_usb --- :> export_syms awk -f xhci.ko.debug export_syms | xargs -J% objcopy % xhci.ko.= debug --- all_subdir_vmm --- --- vmm_stat.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_vmware --- ctfconvert -L VERSION -g if_vmx.o --- all_subdir_usb --- --- xhci.ko.symbols --- objcopy --only-keep-debug xhci.ko.debug xhci.ko.symbols --- all_subdir_vmware --- --- if_vmx.ko.debug --- ld -d -warn-common -r -d -o if_vmx.ko.debug if_vmx.o --- all_subdir_usb --- --- xhci.ko --- objcopy --strip-debug --add-gnu-debuglink=3Dxhci.ko.symbols xhci.ko.debug x= hci.ko --- all_subdir_vmware --- ctfmerge -L VERSION -g -o if_vmx.ko.debug if_vmx.o --- all_subdir_usb --- =3D=3D=3D> usb/rsu (all) --- all_subdir_vmware --- :> export_syms awk -f if_vmx.ko.debug export_syms | xargs -J% objcopy % if_vmx= .ko.debug --- if_vmx.ko.symbols --- objcopy --only-keep-debug if_vmx.ko.debug if_vmx.ko.symbols --- if_vmx.ko --- objcopy --strip-debug --add-gnu-debuglink=3Dif_vmx.ko.symbols if_vmx.ko.deb= ug if_vmx.ko --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_stat.o --- all_subdir_usb --- --- if_rsu.o --- --- all_subdir_vmm --- --- vmm_util.o --- --- all_subdir_vpo --- --- all_subdir_usb --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_vmm --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_vpo --- =3D=3D=3D> vpo (all) --- immio.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_util.o --- x86.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_vpo --- ctfconvert -L VERSION -g immio.o --- vpo.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/= contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-po= inter -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx= -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fst= ack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-pro= tector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmiss= ing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-s= ign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option = -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parenthes= es-equality -Wno-error-unused-function -c --- all_subdir_vmm --- ctfconvert -L VERSION -g x86.o --- vmm_support.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_usb --- :105:2: error: use of undeclared iden= tifier 'USB_PRODUCT_EDIMAX_RTL8192SU_3' RSU_DEV_HT(EDIMAX, RTL8192SU_3), ^ :81:52: note: expanded from macro 'RS= U_DEV_HT' #define RSU_DEV_HT(v,p) { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, \ ^ :113:1: note: expanded from here USB_PRODUCT_EDIMAX_RTL8192SU_3 ^ @/dev/usb/usbdi.h:330:33: note: expanded from macro 'USB_VPI' USB_VENDOR(vend), USB_PRODUCT(prod), USB_DRIVER_INFO(info) --- all_subdir_sound --- ctfconvert -L VERSION -g neomagic.o --- all_subdir_vmm --- ctfconvert -L VERSION -g vmm_support.o --- all_subdir_usb --- ^ @/dev/usb/usbdi.h:324:42: note: expanded from macro 'USB_PRODUCT' .match_flag_product =3D 1, .idProduct =3D (prod) ^ :278:48: error: invalid application o= f 'sizeof' to an incomplete type 'const struct usb_device_id []' return (usbd_lookup_id_by_uaa(rsu_devs, sizeof(rsu_devs), uaa)); ^~~~~~~~~~ --- all_subdir_vmm --- --- vatpic.o --- cc -O2 -pipe -DVMM_KEEP_STATS -DSMP -fno-strict-aliasing -Werror -D_KERNE= L -DKLD_MODULE -nostdinc -I -I -I= -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -= mno-omit-leaf-frame-pointer -I/usr/obj -mno-aes -mno-avx -mcmodel=3Dkernel = -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tabl= es -ffreestanding -fstack-protector -gdwarf-2 -std=3Diso9899:1999 -Qunused-= arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual = -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdia= gnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body= -Wno-error-parentheses-equality -Wno-error-unused-function -c --- all_subdir_sound --- --- snd_neomagic.ko.debug --- ld -d -warn-common -r -d -o snd_neomagic.ko.debug neomagic.o ctfmerge -L VERSION -g -o snd_neomagic.ko.debug neomagic.o :> export_syms awk -f snd_neomagic.ko.debug export_syms | xargs -J% objcopy % = snd_neomagic.ko.debug --- all_subdir_usb --- 2 errors generated. --- all_subdir_sound --- --- snd_neomagic.ko.symbols --- objcopy --only-keep-debug snd_neomagic.ko.debug snd_neomagic.ko.symbols --- all_subdir_usb --- *** [if_rsu.o] Error code 1 make[5]: stopped in 1 error make[5]: stopped in *** [_sub.all] Error code 2 make[4]: stopped in 1 error make[4]: stopped in --- all_subdir_sound --- --- snd_neomagic.ko --- --- all_subdir_usb --- *** [all_subdir_usb] Error code 2 make[3]: stopped in --- all_subdir_sound --- objcopy --strip-debug --add-gnu-debuglink=3Dsnd_neomagic.ko.symbols snd_neo= magic.ko.debug snd_neomagic.ko A failure has been detected in another branch of the parallel make make[6]: stopped in *** [_sub.all] Error code 2 make[5]: stopped in 1 error make[5]: stopped in *** [_sub.all] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [all_subdir_sound] Error code 2 make[3]: stopped in --- all_subdir_vpo --- ctfconvert -L VERSION -g vpo.o A failure has been detected in another branch of the parallel make make[4]: stopped in *** [all_subdir_vpo] Error code 2 make[3]: stopped in --- all_subdir_vmm --- ctfconvert -L VERSION -g vatpic.o A failure has been detected in another branch of the parallel make make[4]: stopped in *** [all_subdir_vmm] Error code 2 make[3]: stopped in 4 errors make[3]: stopped in *** [modules-all] Error code 2 make[2]: stopped in /usr/obj 1 error make[2]: stopped in /usr/obj *** [buildkernel] Error code 2 make[1]: stopped in 1 error make[1]: stopped in *** [buildkernel] Error code 2 make: stopped in 1 error make: stopped in Build step 'Execute shell' marked build as failure From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 11:00:07 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD88AB8A; Fri, 31 Oct 2014 11:00:07 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 761B2EBA; Fri, 31 Oct 2014 11:00:07 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xk9w5-000P3l-Nx; Fri, 31 Oct 2014 12:00:05 +0100 Message-ID: <54536BB1.6060001@FreeBSD.org> Date: Fri, 31 Oct 2014 12:00:01 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RmEkQB2PesNCquCekQWjDgS9M5GRwJrOX" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 11:00:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RmEkQB2PesNCquCekQWjDgS9M5GRwJrOX Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 31.10.2014 11:34, Miguel Clara wrote: > #11 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at > xf86Crtc.c:1829 A crash on line 1829 means that the patch was not applied. With the patch, the same line is at 1832. Double-check how you named the new file in the /usr/ports/x11-servers/xorg-server/files directory. It must start with the "patch-" prefix. --=20 Jean-S=C3=A9bastien P=C3=A9dron --RmEkQB2PesNCquCekQWjDgS9M5GRwJrOX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU2u1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM0RkP/jqEbvwia8r3ACRAwea9EZ0v FmNlm0kIpLFSdzYiH8mwYDqwa/XiZBJQPFfXniaAR31HZkxuX/NnZg4D0LQBSDSM 2DlujOTQ6J+BBk4lufeGuesPA5nXsNkewa5nBDMiWpXsaXx3cQd2qETdThaD+D8j jsn9z7yoFUADEhDj6hYvWI2A0DJ4Vyld6HFa7bv3DoCkAglMvgy96FtUmcGCMgGO Ab76RGHHgpkVqY2FYTfMvAJDaa9XF3Uebefq3Ha5bsf4fmK2MS7aUeqdGs8ZeL8O iWlmNbCKNB39eI+Rgu0kNtBARNCVXcGXm7HmhDZV512uukoizIxve31VmzLmtLX/ JyzCb2Y1YNtVfTHOaCB1cRy+OOmtXi8+rXlbD2RCp9S2tKH3Sc1D3bANBn/QBA9b d1uMp6T0+AnLIcreuz/HfopkwZfjCH+rKjnXXVetq7Z2/zWJTlS1k2Tzue07lKUQ T/r4fwQZDYs5BDwoFUL/p6epMren7GO1a+NX+DpGEY0YcMT619QKjGoHb5zt1S5k BbnIzblafNPoSg/OKZFEh1yf9A+lFn4iPEnaXHF/QdQnaGGIZlfm7Nt8W66cO098 TreZFCVhELSAqaSc7WFscNrjKIJNQ550+hnVj8saoMGc+62aP3ZAW5LyXFYqX0AV XoDJN4feKmsunnJx0/5N =RCw4 -----END PGP SIGNATURE----- --RmEkQB2PesNCquCekQWjDgS9M5GRwJrOX-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 11:08:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6EE3AF00; Fri, 31 Oct 2014 11:08:46 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30BA6FB9; Fri, 31 Oct 2014 11:08:45 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id ECAE31FE022; Fri, 31 Oct 2014 12:08:42 +0100 (CET) Message-ID: <54536DC4.3060401@selasky.org> Date: Fri, 31 Oct 2014 12:08:52 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: jenkins-admin@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Build failed in Jenkins: FreeBSD_stable_10 #917 References: <435710951.16.1414752407546.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <435710951.16.1414752407546.JavaMail.jenkins@jenkins-9.freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 11:08:46 -0000 On 10/31/14 11:46, jenkins-admin@freebsd.org wrote: > See > This compile issue should already be fixed. Sorry. Slipped through my fingers when integrating ... --HPS From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 11:51:49 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD471BC8 for ; Fri, 31 Oct 2014 11:51:49 +0000 (UTC) Received: from artif-webmail.de (artif-webmail.de [144.76.156.78]) by mx1.freebsd.org (Postfix) with ESMTP id 3B22574B for ; Fri, 31 Oct 2014 11:51:48 +0000 (UTC) Received: from [192.168.178.21] (port-92-193-114-196.dynamic.qsc.de [92.193.114.196]) (Authenticated sender: huerter) by artif-webmail.de (Postfix) with ESMTPA id DA7BB2E152B for ; Fri, 31 Oct 2014 12:51:40 +0100 (CET) Message-ID: <545377CC.8060706@guckux.de> Date: Fri, 31 Oct 2014 12:51:40 +0100 From: Stefan Huerter Reply-To: maulwurf@guckux.de User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LSI 1030 and LTO-3 won't work References: <54358D99.5090403@guckux.de> <20141009034819.GA30406@mithlond.kdm.org> In-Reply-To: <20141009034819.GA30406@mithlond.kdm.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 11:51:49 -0000 Guckux It seems, the problem was the syntax and wrong device. I've set the default tape-device in the env as TAPE=/dev/nsa0 I've set the blocksize before via mt blocksize 0 -> using /dev/nsa0 So, since I set the blocksize with: mt -f /dev/sa0 blocksize 0 it works could this really be so? Bye Stefan On 10/09/14 05:48, Kenneth D. Merry wrote: > On Wed, Oct 08, 2014 at 21:16:41 +0200, Stefan Huerter wrote: >> Guckux >> >> I have problems with following configuration: >> FreeBSD whisky 10.1-RC1 FreeBSD 10.1-RC1 #0 r272711M: Tue Oct 7, >> LSILogic 1030 Ultra4 Adapter >> Sun StorEdge C2 - LTO-3 library >> >> I've included the mpt-module to load at boot time in loader.conf. >> >> part from dmesg: >> mpt0: port 0xc400-0xc4ff mem >> 0xff9a0000-0xff9bffff,0xff980000-0xff99ffff irq 23 at device 2.0 on pci5 >> mpt0: MPI Version=1.2.14.0 >> mpt1: port 0xc800-0xc8ff mem >> 0xff9c0000-0xff9dffff irq 20 at device 2.1 on pci5 >> mpt1: MPI Version=1.2.14.0 >> >> (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer >> (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer >> >> I've tried to resize the blocksize to 10240 via mt blocksize 10240. >> >> Nothing works - dump and tar... >> dump reports shortly, that the End of tape is detected, tar reports >> "write error". >> >> With the same controller no Problem with Backup Exec under Windows, or >> Solaris with EMC networker. >> >> Hugh? >> Any hints for me? Or can I give you some other informations, which you need? > The error messages above usually indicate that you're trying to read a > block from the tape (in this case a 32K block) that is bigger than the > blocksize that you specified. But it can also happen on a write to a tape > when you're in fixed block mode and you try to write less than the > blocksize. > > What does 'mt status' show? If it shows 32KB blocks, then that may be your > problem. > > What blocksize are you using with tar and dump? (I believe they default to > 10240 bytes.) > > It's generally easier to run in variable blocksize mode. You can specify > variable blocksize with 'mt blocksize 0'. You can verify which mode you're > in with 'mt status'. For instance, this tape drive is in variable block > mode: > > Mode Density Blocksize bpi Compression > Current: 0x5a:LTO-6 variable 384607 0xff > ---------available modes--------- > 0: 0x5a:LTO-6 variable 384607 0xff > 1: 0x5a:LTO-6 variable 384607 0xff > 2: 0x5a:LTO-6 variable 384607 0xff > 3: 0x5a:LTO-6 variable 384607 0xff > --------------------------------- > Current Driver State: at rest. > --------------------------------- > File Number: 0 Record Number: 0 Residual Count -1 > > I would try something like this: > > mt rewind > mt blocksize 0 > mt status > (verify that it says variable block mode) > dump -C 16 -b 64 -0ua -f /dev/nsa0 / > > That specifies: > - 16MB read cache size (for reading the disk) > - 64K output blocksize > - level 0 dump > - update /etc/dumpdates > - write until the end of tape > - use the non-rewound tape device > - dump the root partition > > It is generally better to write to the tape drive with the largest > blocksize that your tape drive and controller support. You'll get better > throughput that way. > > The tape driver in FreeBSD 10 will not allow you to read or write a > blocksize that your drive and controller don't support. To see what they > support, try: > > sysctl kern.cam.sa.0 > > maxio is the what we think you can effectively write given the limits of > the system and the controller. cpi_maxio is what the controller claims to > support. > > Ken From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 12:19:42 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34EA6618 for ; Fri, 31 Oct 2014 12:19:42 +0000 (UTC) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ACB4099C for ; Fri, 31 Oct 2014 12:19:41 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.9/8.14.9) with ESMTP id s9VCJZII061478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 31 Oct 2014 13:19:35 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.9/8.14.9/Submit) with ESMTP id s9VCJYkm061475; Fri, 31 Oct 2014 13:19:35 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 31 Oct 2014 13:19:34 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Stefan Huerter Subject: Re: LSI 1030 and LTO-3 won't work In-Reply-To: <545377CC.8060706@guckux.de> Message-ID: References: <54358D99.5090403@guckux.de> <20141009034819.GA30406@mithlond.kdm.org> <545377CC.8060706@guckux.de> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.fig.ol.no Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 12:19:42 -0000 On Fri, 31 Oct 2014 12:51+0100, Stefan Huerter wrote: > Guckux > > It seems, the problem was the syntax and wrong device. > I've set the default tape-device in the env as TAPE=/dev/nsa0 > I've set the blocksize before via > mt blocksize 0 -> using /dev/nsa0 > > So, since I set the blocksize with: > mt -f /dev/sa0 blocksize 0 > it works > > > could this really be so? > > Bye > Stefan You may even use /dev/sa0.ctl for control operations, e.g. mt commands. > On 10/09/14 05:48, Kenneth D. Merry wrote: > > On Wed, Oct 08, 2014 at 21:16:41 +0200, Stefan Huerter wrote: > >> Guckux > >> > >> I have problems with following configuration: > >> FreeBSD whisky 10.1-RC1 FreeBSD 10.1-RC1 #0 r272711M: Tue Oct 7, > >> LSILogic 1030 Ultra4 Adapter > >> Sun StorEdge C2 - LTO-3 library > >> > >> I've included the mpt-module to load at boot time in loader.conf. > >> > >> part from dmesg: > >> mpt0: port 0xc400-0xc4ff mem > >> 0xff9a0000-0xff9bffff,0xff980000-0xff99ffff irq 23 at device 2.0 on pci5 > >> mpt0: MPI Version=1.2.14.0 > >> mpt1: port 0xc800-0xc8ff mem > >> 0xff9c0000-0xff9dffff irq 20 at device 2.1 on pci5 > >> mpt1: MPI Version=1.2.14.0 > >> > >> (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer > >> (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer > >> > >> I've tried to resize the blocksize to 10240 via mt blocksize 10240. > >> > >> Nothing works - dump and tar... > >> dump reports shortly, that the End of tape is detected, tar reports > >> "write error". > >> > >> With the same controller no Problem with Backup Exec under Windows, or > >> Solaris with EMC networker. > >> > >> Hugh? > >> Any hints for me? Or can I give you some other informations, which you need? > > The error messages above usually indicate that you're trying to read a > > block from the tape (in this case a 32K block) that is bigger than the > > blocksize that you specified. But it can also happen on a write to a tape > > when you're in fixed block mode and you try to write less than the > > blocksize. > > > > What does 'mt status' show? If it shows 32KB blocks, then that may be your > > problem. > > > > What blocksize are you using with tar and dump? (I believe they default to > > 10240 bytes.) > > > > It's generally easier to run in variable blocksize mode. You can specify > > variable blocksize with 'mt blocksize 0'. You can verify which mode you're > > in with 'mt status'. For instance, this tape drive is in variable block > > mode: > > > > Mode Density Blocksize bpi Compression > > Current: 0x5a:LTO-6 variable 384607 0xff > > ---------available modes--------- > > 0: 0x5a:LTO-6 variable 384607 0xff > > 1: 0x5a:LTO-6 variable 384607 0xff > > 2: 0x5a:LTO-6 variable 384607 0xff > > 3: 0x5a:LTO-6 variable 384607 0xff > > --------------------------------- > > Current Driver State: at rest. > > --------------------------------- > > File Number: 0 Record Number: 0 Residual Count -1 > > > > I would try something like this: > > > > mt rewind > > mt blocksize 0 > > mt status > > (verify that it says variable block mode) > > dump -C 16 -b 64 -0ua -f /dev/nsa0 / > > > > That specifies: > > - 16MB read cache size (for reading the disk) > > - 64K output blocksize > > - level 0 dump > > - update /etc/dumpdates > > - write until the end of tape > > - use the non-rewound tape device > > - dump the root partition > > > > It is generally better to write to the tape drive with the largest > > blocksize that your tape drive and controller support. You'll get better > > throughput that way. > > > > The tape driver in FreeBSD 10 will not allow you to read or write a > > blocksize that your drive and controller don't support. To see what they > > support, try: > > > > sysctl kern.cam.sa.0 > > > > maxio is the what we think you can effectively write given the limits of > > the system and the controller. cpi_maxio is what the controller claims to > > support. > > > > Ken -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestřl, | Trond Endrestřl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjřvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 13:39:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D11B1C8; Fri, 31 Oct 2014 13:39:26 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 1BAF91D3; Fri, 31 Oct 2014 13:39:26 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 5BDDD517; Fri, 31 Oct 2014 13:39:26 +0000 (UTC) Date: Fri, 31 Oct 2014 13:39:25 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, hselasky@FreeBSD.org Message-ID: <1886160452.18.1414762766342.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <435710951.16.1414752407546.JavaMail.jenkins@jenkins-9.freebsd.org> References: <435710951.16.1414752407546.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : FreeBSD_stable_10 #918 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 13:39:26 -0000 See From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 14:35:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D59AE4B; Fri, 31 Oct 2014 14:35:35 +0000 (UTC) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0F16A22; Fri, 31 Oct 2014 14:35:34 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id n12so1278759wgh.13 for ; Fri, 31 Oct 2014 07:35:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ykUaPfqu1yzxcuOiWG3ovEDN7bo0giyU4zBH9aWlgAg=; b=dHV4tJnY5bSEKMUVRGdH8eEBWm8/vygLdzB+G04DqqftKHOreqfCx/c/TqugWwjoRf 43DP2jx+ZBuctzuYCN2ttEGCe00YpX3IlXkVKaIDrhQg0skeAUogLd/JTzsAXNdXMtUx HSaKanJJgKPcTvb7Iz3e6CYkpdOBHezCofWybyP+j4B32lyZ7BKgRqd8fANXmHSB+XGL SSbEasUZgOqiuHzvyzZM3LC6zVwhZw4FmK1eRU7KZao5fUVzQm89VB1CrdRONlhCMtX3 BttcmXqOkR3yfzSsZ8QVZUwcDgwl1QeAXv1hw7MfCsvnGqcKZDZtEAEojuBVNR7S2PX1 edjw== X-Received: by 10.194.209.230 with SMTP id mp6mr28471938wjc.2.1414766132920; Fri, 31 Oct 2014 07:35:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 31 Oct 2014 07:35:12 -0700 (PDT) In-Reply-To: <54536BB1.6060001@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> From: Miguel Clara Date: Fri, 31 Oct 2014 14:35:12 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 14:35:35 -0000 On Fri, Oct 31, 2014 at 11:00 AM, Jean-S=C3=A9bastien P=C3=A9dron < dumbbell@freebsd.org> wrote: > On 31.10.2014 11:34, Miguel Clara wrote: > > #11 0x00000000004eb710 in SetCompatOutput (config=3D0x8034e32c0) at > > xf86Crtc.c:1829 > > A crash on line 1829 means that the patch was not applied. With the > patch, the same line is at 1832. > > Double-check how you named the new file in the > /usr/ports/x11-servers/xorg-server/files directory. It must start with > the "patch-" prefix. > Xorg.0.log: % tail -40 /var/log/Xorg.0.log [ 207.575] compiled for 1.12.4, module version =3D 2.5.0 [ 207.575] ABI class: X.Org Video Driver, version 12.1 [ 207.575] (II) RADEON(0): KMS Color Tiling: enabled [ 207.575] (II) RADEON(0): KMS Color Tiling 2D: enabled [ 207.575] (II) RADEON(0): KMS Pageflipping: enabled [ 207.575] (II) RADEON(0): SwapBuffers wait for vsync: enabled [ 207.576] (WW) RADEON(0): No outputs definitely connected, trying again... [ 207.576] (WW) RADEON(0): Unable to find connected outputs - setting 1024x768 initial framebuffer [ 207.576] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [ 207.576] (II) RADEON(0): mem size init: gart size :1fdef000 vram size: s:40000000 visible:3fcc0000 [ 207.576] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM [ 207.576] (=3D=3D) RADEON(0): DPI set to (96, 96) [ 207.576] (II) Loading sub module "fb" [ 207.576] (II) LoadModule: "fb" [ 207.576] (II) Loading /usr/local/lib/xorg/modules/libfb.so [ 207.576] (II) Module fb: vendor=3D"X.Org Foundation" [ 207.576] compiled for 1.12.4, module version =3D 1.0.0 [ 207.576] ABI class: X.Org ANSI C Emulation, version 0.4 [ 207.576] (II) Loading sub module "ramdac" [ 207.577] (II) LoadModule: "ramdac" [ 207.577] (II) Module "ramdac" already built-in [ 207.577] (EE) RADEON(0): No modes. [ 207.577] (II) UnloadModule: "radeon" [ 207.577] (II) UnloadSubModule: "fb" [ 207.577] (II) Unloading fb [ 207.577] (II) UnloadSubModule: "exa" [ 207.577] (II) Unloading exa [ 207.577] (II) UnloadSubModule: "dri2" [ 207.577] (II) Unloading dri2 [ 207.577] (EE) Screen(s) found, but none have a usable configuration. [ 207.577] Fatal server error: [ 207.577] no screens found [ 207.577] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 207.577] Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 207.577] [ 207.580] Server terminated with error (1). Closing log file. dmesg: iic7: on iicbus7 info: [drm] Radeon Display Connectors info: [drm] Internal thermal controller with fan control info: [drm] radeon: power management initialized No connectors reported connected with modes info: [drm] Cannot find any crtc or sizes - going 1024x768 info: [drm] fb mappable at 0xA0142000 info: [drm] vram apper at 0xA0000000 info: [drm] size 3145728 info: [drm] fb depth is 24 info: [drm] pitch is 4096 fbd0 on drmn0 VT: Replacing driver "vga" with new "fb". info: [drm] Initialized radeon 2.29.0 2008052 > > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 14:41:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5698DE0; Fri, 31 Oct 2014 14:41:13 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DB13A66; Fri, 31 Oct 2014 14:41:13 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XkDO2-0001bk-8F; Fri, 31 Oct 2014 15:41:10 +0100 Message-ID: <54539F7F.3070901@FreeBSD.org> Date: Fri, 31 Oct 2014 15:41:03 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hCW0hNdgxXa7quFnvi5QxpoWcEd9osN7n" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 14:41:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hCW0hNdgxXa7quFnvi5QxpoWcEd9osN7n Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 31.10.2014 15:35, Miguel Clara wrote: > [ 207.577] (EE) RADEON(0): No modes. > [ 207.577] (II) UnloadModule: "radeon" > [ 207.577] (II) UnloadSubModule: "fb" > [ 207.577] (II) Unloading fb > [ 207.577] (II) UnloadSubModule: "exa" > [ 207.577] (II) Unloading exa > [ 207.577] (II) UnloadSubModule: "dri2" > [ 207.577] (II) Unloading dri2 > [ 207.577] (EE) Screen(s) found, but none have a usable configuration= =2E Cool, the crash is fixed. Could you please post the whole Xorg.log? --=20 Jean-S=C3=A9bastien P=C3=A9dron --hCW0hNdgxXa7quFnvi5QxpoWcEd9osN7n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU5+GXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMFtoQAJNHKYOuV+GsXkztmaHVDO12 QLS9og0mAw9N1q7cnvUytjJyDWQx8nqgAZFCBpI3oNaUpkai/xBZYPrxkYsng/C+ KoCvHKkwVmPCxKliRqV9Wg0QNdZwOb6yLfZrOp1GpjbQ86YYayABP0eguKxwB9lO vDCbnYZfewGUfefDTHcE634cPGfaxGvcyGq0BuejaQs7joGG5g6Jm9Nyvogd3kAs lW07mekxcGpz3p4WN/ZwFmfUd9xUa/VkzCJyd9fhk3pGeD8DnE2zOymB4eBlfzgT NsHaS/S+9F/AoEZyJESKVUUafzikzmhPt63AE0qTf2y1CJO9Sq9SRfXBlixdOfLH Be266KN+v9QDV8SxS3Qs4AmFLs9R1ceAmjij8AnQniWPrCOQLxvTp1gQOLqKrO7r TxfMtD8rI909T2Fl3FvtywZ4FPQ5ncH1u39loy2OqjGQGmW66cG1Bg5ZPk10pjca 6/5BNine+mNRAeN2K+AgXm8ySCQ1wufS5KfXCUBZPGMzQRud8U7cSS6UFYpU/8KV zs6GEoaYALu4lKKHsv8vqVlsTMykHdCV5MewyeVRxTRu2QavrYXYmHee7v10id1k BzeRNWRaDocTYG27OfaSU/VkwkFNBn81FsXGLno3OogcR4P7Bl2EIuj3B1QTtftb WQEad2Iw+WRvIQkAhbFI =CL3t -----END PGP SIGNATURE----- --hCW0hNdgxXa7quFnvi5QxpoWcEd9osN7n-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 14:56:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 01F2AF2F; Fri, 31 Oct 2014 14:56:51 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17EB0C43; Fri, 31 Oct 2014 14:56:49 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so6105053wgh.25 for ; Fri, 31 Oct 2014 07:56:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nzS1K91ZmNucfJNiroOTgfVuRDRzFln4ocRxIGtjaUw=; b=Wys5aL6Dw6ZQrRdvIucLoJO45+bG+ruWlsUN9GUDv0NMzdk7P3SG5v5ZCFNY/d2zK7 9oAPEdnTL+RFu/PAWyEHtjAK5jiPA9886BND6VnvXRmo/knm3WKQavDjPhA6zpnp5hys PgOLP0OVHLWagMWylVPwxjHldiDUvTf+b/nxLMZgxcG16ZtJ5Uprrz9o9KdJTUp9kLca fYyNKsATgoUBbwVwVUa1cOlY5q/43SDGb2d8QB+lGuoZ4jjN0MdCbDb69s2uVYGCkx2S zmmbqgbSZsk6LiM7cArF2f1MM8KrgUlktbL5PofeCukcMB5KyXZBjF785eQckJthrBtV PTrA== X-Received: by 10.194.242.4 with SMTP id wm4mr27714753wjc.61.1414767407985; Fri, 31 Oct 2014 07:56:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 31 Oct 2014 07:56:27 -0700 (PDT) In-Reply-To: <54539F7F.3070901@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544EC35A.2050401@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> <54539F7F.3070901@FreeBSD.org> From: Miguel Clara Date: Fri, 31 Oct 2014 14:56:27 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 14:56:51 -0000 On Fri, Oct 31, 2014 at 2:41 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 31.10.2014 15:35, Miguel Clara wrote: > > [ 207.577] (EE) RADEON(0): No modes. > > [ 207.577] (II) UnloadModule: "radeon" > > [ 207.577] (II) UnloadSubModule: "fb" > > [ 207.577] (II) Unloading fb > > [ 207.577] (II) UnloadSubModule: "exa" > > [ 207.577] (II) Unloading exa > > [ 207.577] (II) UnloadSubModule: "dri2" > > [ 207.577] (II) Unloading dri2 > > [ 207.577] (EE) Screen(s) found, but none have a usable configuration= . > > Cool, the crash is fixed. > > Could you please post the whole Xorg.log? > > http://filebin.ca/1fdab69tzLua/Xorg.0.log About the "but none have a usable configuration" does this mean I can have a xorg.conf that would work with the ati card, or does it simple mean we are one step closer? -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 15:08:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A78265DC; Fri, 31 Oct 2014 15:08:51 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6360FD8B; Fri, 31 Oct 2014 15:08:51 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id s9VFAMKl010253; Fri, 31 Oct 2014 08:10:22 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Kevin Oberman , Adrian Chadd In-Reply-To: References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> , From: "Chris H" Subject: Re: Dump time issues Date: Fri, 31 Oct 2014 08:10:22 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <9c5f3b0230bf63d32ee8a83e81b1f167@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 15:08:51 -0000 On Tue, 28 Oct 2014 12:20:01 -0700 Adrian Chadd wrote > On 27 October 2014 11:09, Kevin Oberman wrote: > > >> I'm aware of two issues with SU+J, one of which is annoying and the other > > is worse. > > 1. If the journal is not fully written on power fail or some other reason, > > you may need to do a full fsck of the volume and the behavior of the system > > until this is done can be very unpredictable. > > 2. You can't safely snapshot the system. This is what 'dump -L' does. This > > means that some files dumped from a live FS may not be consistent (not > > good!) or, if '-L' is used, the system may well hang. > > > > While I love the fast fsck times (2 or 3 seconds) after a crash, I also > > question the default. Still, it may be a preferred choice be used for very > > large file systems where a full fsck would take a very long time as long as > > the risks are understood. For these systems, ZFS might be a better choice. > > These arguments do NOT favor it being the default, IMHO. > > If people can reproduce SU+J problems then please file bugs. There > have been some fixes with the journal handling over the last year or > so and I haven't had this problem on -HEAD any longer, but it doesn't > mean it's there. Problem existed on RELENG_9 as of 1 mos, and 1 wk. ago. I don't have any useful output to provide (I simply blew away the system && re-installed w/o SU+J). --Chris > > > > > -adrian From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 15:25:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25650BBA; Fri, 31 Oct 2014 15:25:31 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFF3EF8F; Fri, 31 Oct 2014 15:25:30 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XkE4v-0002BT-2M; Fri, 31 Oct 2014 16:25:29 +0100 Message-ID: <5453A9E4.6040702@FreeBSD.org> Date: Fri, 31 Oct 2014 16:25:24 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> <54539F7F.3070901@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tF1C9DMfU4NqGIjwf635M7MwbGtElWmfD" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 15:25:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --tF1C9DMfU4NqGIjwf635M7MwbGtElWmfD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 31.10.2014 15:56, Miguel Clara wrote: > About the "but none have a usable configuration" does this mean I can= > have a xorg.conf that would work with the ati card, or does it simple m= ean > we are one step closer? Currently, no update to xorg-server or xf86-video-ati will make your card work, because we lack the support in the kernel. However, now you can keep both xf86-video-ati and xf86-video-intel installed and the server won't crash :) And one day in the future, the Radeon card will come to life, though definitely not for today's Halloween :) With power consumption in mind, I would probably don't install xf86-video-ati at all for now, so radeonkms isn't loaded. --=20 Jean-S=C3=A9bastien P=C3=A9dron --tF1C9DMfU4NqGIjwf635M7MwbGtElWmfD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU6noXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMTSMP/0kgv+iuLe1IK+DoT6O1p1eF f7e1Qsh/L5QVJI/PfbloCKBjLRSdkgngoSgQIDtPAle0UPcX+j8exCdvrZrVOlnS 0T3E/QaAxAqRLSx4+nhbB6kRkNlXjEFXuGvn2w8fjH2sbD+aEdgdmgJOwZ3M7tju 8uggjgS00+GHrbxUlKPBeqZJ4g2rSnOKp0zDH/9oVgumsVN8UmtIDWgGan3KFPKS 6EmcspXEYbsADm2/QCXICAZ+6QYGYChxo8KNcExvqsPqFB6Ms/EWdQXpBeulTY6i c64HDSsymmw4eZ+YNp7RTG/sPIO1YzemytCw73qn1+h5pszD35ne6itn4UtdagKj QJ4dP1neP3Wh0Bl+5FlyjJUkE1+pfllF/tuvcpCMaKL2WCQ5Inv4YaaMyQqNGQ3S x2A7M4NS2Euhe+jNT+Dffc7j4e+GkFrx8pmkgM5MFFsbpsuyRpoIMulaxMQQiHcu VR1SUKjmSSaC1GGkRhzbYGun5CdHx7+oRxgerZG7irLBZtUFMMYjLszGfLdKZJ3T sth4htMziPcdCOlgWRqZeVSXYpJhJh4BdgT3IyV7TxRnowvumPuVrMCi08uKlOAo JDtOhqXakYfNzXM+2P/F7JlrT0xyjAF+YqOK9X8t8xieMBtT4WlK9PqCmApLZhDz 7KvYSvCzk9oFt49v0NLi =fVAP -----END PGP SIGNATURE----- --tF1C9DMfU4NqGIjwf635M7MwbGtElWmfD-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 15:53:48 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD75F460; Fri, 31 Oct 2014 15:53:48 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3CA238A; Fri, 31 Oct 2014 15:53:47 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id n3so1623798wiv.2 for ; Fri, 31 Oct 2014 08:53:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=erdWnNErJr//unLU9dzok8cRIdqeAlUFOjOe5FnJkUo=; b=gAYqJzVpcPZna6FGJh30cVA0QaoBCPQUPdg3bfceopmpGPBR0+Kf8H5PV66IGQCT4H SCmqaGFOgKI+GU88JK6HMrPa+PeaI8FWR3RmOMXVAbhsOczzFvLJc6gQ4LtJqCzHoqG2 BSQJrLZyi7vasNNtt0Nb6qsrqJMP6/ZPFvzHm6By8EcQxCFBuugTcjDv0ySLr0u3kpkX Uha2N2Mo4VqjcN0YgCFnLVXgFlUT7If/U1dMLmtEPbABc7JG6l/492Esk12/IdMcgBH5 N0Pep5UZc4SBS/RY3bwBS2pRSG/jZzFUgw7710ocOhfLXb5rtpDNstxBEiz+WxB98IUx YDEQ== X-Received: by 10.194.209.230 with SMTP id mp6mr28978177wjc.2.1414770826128; Fri, 31 Oct 2014 08:53:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 31 Oct 2014 08:53:25 -0700 (PDT) In-Reply-To: <5453A9E4.6040702@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544F61F9.6040408@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> <54539F7F.3070901@FreeBSD.org> <5453A9E4.6040702@FreeBSD.org> From: Miguel Clara Date: Fri, 31 Oct 2014 15:53:25 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 15:53:48 -0000 On Fri, Oct 31, 2014 at 3:25 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 31.10.2014 15:56, Miguel Clara wrote: > > About the "but none have a usable configuration" does this mean I can > > have a xorg.conf that would work with the ati card, or does it simple > mean > > we are one step closer? > > Currently, no update to xorg-server or xf86-video-ati will make your > card work, because we lack the support in the kernel. > > However, now you can keep both xf86-video-ati and xf86-video-intel > installed and the server won't crash :) And one day in the future, the > Radeon card will come to life, though definitely not for today's > Halloween :) > > With power consumption in mind, I would probably don't install > xf86-video-ati at all for now, so radeonkms isn't loaded. > > Agreed, but ideally one could change as needed... ofc it will always mean restart Xorg... IFAIK you can do it in Linux. In any case this laptop has the battery dead already so its AC always. On another note, as I've refereed in the other report, my perfect scenario for this laptop would be using the intel on host and pass-trough the ati to virtualized guest... vbox is not and option and AFAIK bhyve is far from that too, but maybe Xen will be a solution soon :) But for now I'll just keep testing with this one ;) thanks for you're time on this btw, please continue the good work -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 16:24:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E57C504; Fri, 31 Oct 2014 16:24:43 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14A8B98E; Fri, 31 Oct 2014 16:24:43 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XkF0D-0002sN-7U; Fri, 31 Oct 2014 17:24:41 +0100 Message-ID: <5453B7C5.7090409@FreeBSD.org> Date: Fri, 31 Oct 2014 17:24:37 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> <54539F7F.3070901@FreeBSD.org> <5453A9E4.6040702@FreeBSD.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="I1LDVAl75u5CWdpORlQOx4pJjTlcBDKkR" Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 16:24:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --I1LDVAl75u5CWdpORlQOx4pJjTlcBDKkR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 31.10.2014 16:53, Miguel Clara wrote: > Agreed, but ideally one could change as needed... ofc it will always me= an > restart Xorg... IFAIK you can do it in Linux. Yes, when we grow support for video cards only used to render things, you won't have to restart anything. > On another note, as I've refereed in the other report, my perfect scena= rio > for this laptop would be using the intel on host and pass-trough the at= i to > virtualized guest... vbox is not and option and AFAIK bhyve is far from= > that too, but maybe Xen will be a solution soon :) I don't know for Xen, but even on Linux, GPU virtualization in KVM isn't for tomorrow. Red Hat is working on the subject through the Virgil project[1]. > thanks for you're time on this btw, please continue the good work You're welcome :) You helped a lot to diagnose the problem and test the patch! An update to xserver 1.14 is almost ready for a CFT. This will include the patch you tested. [1] https://virgil3d.github.io/ --=20 Jean-S=C3=A9bastien P=C3=A9dron --I1LDVAl75u5CWdpORlQOx4pJjTlcBDKkR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUU7fJXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMSZQQAN561yugNIaCrUYpUY+rbtPR Lg1z1hEs/N8pPnHbLtk7cKM8j2SVfcYaXVB3KhDqagrze3MTbYzgc5R8ihjzKK45 J84ADUQHlrF1LRkdeudTdIenQYXO2VsfW/eN2/dJsMHZLLeqnvyXNSIIXmUi1EpB TLaKfWheS1fSLwJ7GXkVl8woB5hVBEfX8nwAGoPaOt5VPp1fXsFUwxAzkH7yYbqC fGz5vSN9qIUFVXyQWV2D/M2luEPfO9GSwZPF9NOLx6kWAybKg0DclO+IT2kvJEz1 8oDTRjO0usNEBCAQsWjOvpSfiTSFGlPA3vXVjd2Adcln17nGmKub7YTL1pyjMrf8 +DDVx33sM19tlSDsE/0QTaI+cIhQYYwbGQcovDOOGAPW7SPmh4leiyObQU1X8Ycy SRFz6u6AWvzrMDIgx23LvI0moGg6FD+62HmEwKRfdGOukpp21Rob9T16hARhKQte oJK/uAK7+kEQV56Bv4XKh14YYpy/6wrA8wflHKKACGkO0IKMCFQWhKw2xUNQMh0B nu1x2M28vyDsOOUA8CtDlivOSh2bNe6lTm8uhaI9zS90my6zrjAQ54ghiOKZKhd2 yTSmdwwXXOrVyxog1RJO/GeVh4mLzw+FewASPHCmBSccaeGL5nnYKMV2p3f3misy K6gbo831fmHnMqPkooFP =J9Iu -----END PGP SIGNATURE----- --I1LDVAl75u5CWdpORlQOx4pJjTlcBDKkR-- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 16:49:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8103DD1; Fri, 31 Oct 2014 16:49:28 +0000 (UTC) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB758C2B; Fri, 31 Oct 2014 16:49:27 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id ex7so1844526wid.2 for ; Fri, 31 Oct 2014 09:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4zPn9lSnXa3kJY7MqJOBPrUefKZgMxwIv0PVxz5mUMQ=; b=U+oNV+ijqT9kMw6RjdLlZjNZOYCJMmB68WfJza3yb6HkdFyULcREe5ektkoZK4VtWy TNyut/ZNiKb9Z70jtMwzlOJ+k1p/rQrW/qWlfP4s1dpOGCMd0gVat2FD6dDc23VF2QpY FHECexTS6nA0PxBMKtmshVyzXmHn5FMjPUmYS3cudpnKli7IPQnIKT1Ii7+4rdFSGo9A /C60ubyXLAcpBKk9HLWL0IG+4M0i3qhAwjKxabUzaiNmN6ErTrhqkPbVzGQre+/smExQ yuUERDxzDUuhebhGOvFytYNq56Cet/Rf/gI3M9CyNTfLT1IvlHngAbLoOxQADzhV28cC AE3g== X-Received: by 10.194.81.70 with SMTP id y6mr3946401wjx.113.1414774166072; Fri, 31 Oct 2014 09:49:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 31 Oct 2014 09:49:05 -0700 (PDT) In-Reply-To: <5453B7C5.7090409@FreeBSD.org> References: <544E0FC8.8090605@FreeBSD.org> <544FE187.3030404@FreeBSD.org> <5450D27D.4080508@FreeBSD.org> <5451F42B.5020805@FreeBSD.org> <545270A7.6030807@FreeBSD.org> <54535178.8040706@FreeBSD.org> <54536BB1.6060001@FreeBSD.org> <54539F7F.3070901@FreeBSD.org> <5453A9E4.6040702@FreeBSD.org> <5453B7C5.7090409@FreeBSD.org> From: Miguel Clara Date: Fri, 31 Oct 2014 16:49:05 +0000 Message-ID: Subject: Re: CFT: Update to xf86-video-ati 7.5.0 To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 16:49:28 -0000 On Fri, Oct 31, 2014 at 4:24 PM, Jean-S=C3=A9bastien P=C3=A9dron wrote: > On 31.10.2014 16:53, Miguel Clara wrote: > > Agreed, but ideally one could change as needed... ofc it will always me= an > > restart Xorg... IFAIK you can do it in Linux. > > Yes, when we grow support for video cards only used to render things, > you won't have to restart anything. > > > On another note, as I've refereed in the other report, my perfect > scenario > > for this laptop would be using the intel on host and pass-trough the at= i > to > > virtualized guest... vbox is not and option and AFAIK bhyve is far from > > that too, but maybe Xen will be a solution soon :) > > I don't know for Xen, but even on Linux, GPU virtualization in KVM isn't > for tomorrow. Red Hat is working on the subject through the Virgil > project[1]. > Just to add some info on this about xen: http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Tested_Adapters > > > thanks for you're time on this btw, please continue the good work > > You're welcome :) You helped a lot to diagnose the problem and test the > patch! An update to xserver 1.14 is almost ready for a CFT. This will > include the patch you tested. > > [1] https://virgil3d.github.io/ > > -- > Jean-S=C3=A9bastien P=C3=A9dron > > From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 20:36:32 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1F5E928; Fri, 31 Oct 2014 20:36:32 +0000 (UTC) Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71280DEC; Fri, 31 Oct 2014 20:36:31 +0000 (UTC) Received: from mail-in-05-z2.arcor-online.net (mail-in-05-z2.arcor-online.net [151.189.8.17]) by mx.arcor.de (Postfix) with ESMTP id 1BC0235A514; Fri, 31 Oct 2014 21:36:23 +0100 (CET) Received: from mail-in-14.arcor-online.net (mail-in-14.arcor-online.net [151.189.21.54]) by mail-in-05-z2.arcor-online.net (Postfix) with ESMTP id 0F0856F250E; Fri, 31 Oct 2014 21:36:23 +0100 (CET) X-Greylist: Passed host: 94.217.98.220 X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-14.arcor-online.net CDC659BE06 X-Greylist: Passed host: 94.217.98.220 X-Greylist: Passed host: 94.217.98.220 X-Greylist: Passed host: 94.217.98.220 Received: from lorvorc.mips.inka.de (dslb-094-217-098-220.094.217.pools.vodafone-ip.de [94.217.98.220]) by mail-in-14.arcor-online.net (Postfix) with ESMTPS id CDC659BE06; Fri, 31 Oct 2014 21:36:22 +0100 (CET) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.9/8.14.7) with ESMTP id s9VKaMMl066595; Fri, 31 Oct 2014 21:36:22 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.14.9/8.14.9/Submit) id s9VKaMiG066594; Fri, 31 Oct 2014 21:36:22 +0100 (CET) (envelope-from naddy) Date: Fri, 31 Oct 2014 21:36:22 +0100 From: Christian Weisgerber To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: CFT: Update to xf86-video-ati 7.5.0 Message-ID: <20141031203622.GA66405@lorvorc.mips.inka.de> References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> <20141030133112.GA26588@lorvorc.mips.inka.de> <545270EE.3090405@FreeBSD.org> <20141030201248.GA34433@lorvorc.mips.inka.de> <54534FCF.7070400@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <54534FCF.7070400@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 20:36:32 -0000 Jean-Sébastien Pédron: > > What do you mean? Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was > > a one-time event. > > Yes, but I was wondering if your problem was still there from time to > time (ie. not related to the update). I don't know, I haven't restarted the X server since. I guess I shouldn't have brought it up in the first place. It's not important, possibly a fluke, and has just caused confusion. Maybe it wasn't clear in the Xorg.0.log snippet I sent, but from comparing log files, the actual error was this: [351790.259] drmOpenByBusid: Interface 1.4 failed, trying 1.1 ... [351790.259] (EE) RADEON(0): [drm] failed to set drm interface version. [351790.259] (EE) RADEON(0): Kernel modesetting setup failed To me this means nothing, but I thought it might be something obvious for the people working on X11. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 21:14:11 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69E4C654 for ; Fri, 31 Oct 2014 21:14:11 +0000 (UTC) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D58527A for ; Fri, 31 Oct 2014 21:14:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=USOhYJPKBHWUCr0xC5BeaIbx01KAjCo6pEi5QztSwAo=; b=gGGklv3ebobVrZPyz44+rQCGMc+WBWnI7RAyDPVWP6JcyxBERbKlSCB3qerXyjPcxR7ln1Cw/auxzRXcJXyd3IkNLKQSCpL7Ebvhp/YOMax56+8ZVCELWGpJlHEvOOQaBsjRMRk798Dsb66wATfR7SAS3blO7RNEqQ61geaDHVU=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:22332) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XkJWK-0000LJ-Oz for freebsd-stable@freebsd.org; Fri, 31 Oct 2014 16:14:10 -0500 Date: Fri, 31 Oct 2014 16:14:07 -0500 From: Larry Rosenman To: freebsd-stable@freebsd.org Subject: 10.1-RC: ARC Page Fault Panic Message-ID: <20141031211407.GA1267@thebighonker.lerctr.org> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -3.5 (---) X-LERCTR-Spam-Score: -3.5 (---) X-Spam-Report: SpamScore (-3.5/5.0) ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594 X-LERCTR-Spam-Report: SpamScore (-3.5/5.0) ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 21:14:11 -0000 Rebooted the router in front of this server, and when all was said and done, I found this panic. VMCore available. I *DID* do a svn up AFTER this to: FreeBSD thebighonker.lerctr.org 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #6 r273918: Fri Oct 31 16:00:24 CDT 2014 root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 thebighonker.lerctr.org dumped core - see /var/crash/vmcore.0 Fri Oct 31 15:41:41 CDT 2014 FreeBSD thebighonker.lerctr.org 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #5 r273589: Fri Oct 24 10:50:58 CDT 2014 root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols Reading symbols from /boot/kernel/if_lagg.ko.symbols...done. Loaded symbols for /boot/kernel/if_lagg.ko.symbols Reading symbols from /boot/kernel/ipmi.ko.symbols...done. Loaded symbols for /boot/kernel/ipmi.ko.symbols Reading symbols from /boot/kernel/smbus.ko.symbols...done. Loaded symbols for /boot/kernel/smbus.ko.symbols Reading symbols from /boot/kernel/crypto.ko.symbols...done. Loaded symbols for /boot/kernel/crypto.ko.symbols Reading symbols from /boot/kernel/cryptodev.ko.symbols...done. Loaded symbols for /boot/kernel/cryptodev.ko.symbols Reading symbols from /boot/kernel/hwpmc.ko.symbols...done. Loaded symbols for /boot/kernel/hwpmc.ko.symbols Reading symbols from /boot/kernel/dtraceall.ko.symbols...done. Loaded symbols for /boot/kernel/dtraceall.ko.symbols Reading symbols from /boot/kernel/profile.ko.symbols...done. Loaded symbols for /boot/kernel/profile.ko.symbols Reading symbols from /boot/kernel/cyclic.ko.symbols...done. Loaded symbols for /boot/kernel/cyclic.ko.symbols Reading symbols from /boot/kernel/dtrace.ko.symbols...done. Loaded symbols for /boot/kernel/dtrace.ko.symbols Reading symbols from /boot/kernel/systrace_freebsd32.ko.symbols...done. Loaded symbols for /boot/kernel/systrace_freebsd32.ko.symbols Reading symbols from /boot/kernel/systrace.ko.symbols...done. Loaded symbols for /boot/kernel/systrace.ko.symbols Reading symbols from /boot/kernel/sdt.ko.symbols...done. Loaded symbols for /boot/kernel/sdt.ko.symbols Reading symbols from /boot/kernel/lockstat.ko.symbols...done. Loaded symbols for /boot/kernel/lockstat.ko.symbols Reading symbols from /boot/kernel/fasttrap.ko.symbols...done. Loaded symbols for /boot/kernel/fasttrap.ko.symbols Reading symbols from /boot/kernel/fbt.ko.symbols...done. Loaded symbols for /boot/kernel/fbt.ko.symbols Reading symbols from /boot/kernel/dtnfscl.ko.symbols...done. Loaded symbols for /boot/kernel/dtnfscl.ko.symbols Reading symbols from /boot/kernel/dtmalloc.ko.symbols...done. Loaded symbols for /boot/kernel/dtmalloc.ko.symbols Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. Loaded symbols for /boot/kernel/fdescfs.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols Reading symbols from /boot/kernel/uplcom.ko.symbols...done. Loaded symbols for /boot/kernel/uplcom.ko.symbols Reading symbols from /boot/kernel/ucom.ko.symbols...done. Loaded symbols for /boot/kernel/ucom.ko.symbols Reading symbols from /boot/kernel/linux.ko.symbols...done. Loaded symbols for /boot/kernel/linux.ko.symbols Reading symbols from /boot/kernel/cpuctl.ko.symbols...done. Loaded symbols for /boot/kernel/cpuctl.ko.symbols #0 doadump (textdump=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:219 #1 0xffffffff809282a2 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:452 #2 0xffffffff80928664 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80d25f7f in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:865 #4 0xffffffff80d26298 in trap_pfault (frame=0xfffffe0468f9c750, usermode=) at /usr/src/sys/amd64/amd64/trap.c:676 #5 0xffffffff80d258fa in trap (frame=0xfffffe0468f9c750) at /usr/src/sys/amd64/amd64/trap.c:440 #6 0xffffffff80d0b6a2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0x0000000000001000 in ?? () #8 0xffffffff81975286 in arc_read_done (zio=0xfffff8034033b730) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:3191 #9 0xffffffff819f40de in zio_done (zio=0xfffff8034033b730) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3316 #10 0xffffffff819effd2 in zio_execute (zio=0xfffff8034033b730) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1414 #11 0xffffffff819f423f in zio_done (zio=0xfffff8021d2d3000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3326 #12 0xffffffff819effd2 in zio_execute (zio=0xfffff8021d2d3000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1414 #13 0xffffffff819f423f in zio_done (zio=0xfffff8030cf85ac8) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3326 #14 0xffffffff819effd2 in zio_execute (zio=0xfffff8030cf85ac8) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1414 #15 0xffffffff809719b5 in taskqueue_run_locked (queue=0xfffff8000f626b00) at /usr/src/sys/kern/subr_taskqueue.c:342 #16 0xffffffff80972448 in taskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_taskqueue.c:563 #17 0xffffffff808f906a in fork_exit ( callout=0xffffffff809723a0 , arg=0xfffff8000f0c3270, frame=0xfffffe0468f9cc00) at /usr/src/sys/kern/kern_fork.c:996 #18 0xffffffff80d0bbde in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:606 #19 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From owner-freebsd-stable@FreeBSD.ORG Sat Nov 1 10:44:48 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71AE18EF; Sat, 1 Nov 2014 10:44:48 +0000 (UTC) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 305BE793; Sat, 1 Nov 2014 10:44:48 +0000 (UTC) Received: from 2a02-8428-011b-e000-0290-f5ff-fe9d-b78c.rev.sfr.net ([2a02:8428:11b:e000:290:f5ff:fe9d:b78c] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XkWAn-000EZI-2B; Sat, 01 Nov 2014 11:44:45 +0100 Message-ID: <5454B998.8090209@FreeBSD.org> Date: Sat, 01 Nov 2014 11:44:40 +0100 From: =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Christian Weisgerber Subject: Re: CFT: Update to xf86-video-ati 7.5.0 References: <544E0FC8.8090605@FreeBSD.org> <20141029220128.GA8896@lorvorc.mips.inka.de> <5451F399.2050105@FreeBSD.org> <20141030133112.GA26588@lorvorc.mips.inka.de> <545270EE.3090405@FreeBSD.org> <20141030201248.GA34433@lorvorc.mips.inka.de> <54534FCF.7070400@FreeBSD.org> <20141031203622.GA66405@lorvorc.mips.inka.de> In-Reply-To: <20141031203622.GA66405@lorvorc.mips.inka.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6NmgNcp3SMXBaMG3CCOdUQLLEtRuT5QfI" Cc: freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 10:44:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6NmgNcp3SMXBaMG3CCOdUQLLEtRuT5QfI Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 31.10.2014 21:36, Christian Weisgerber wrote: > Maybe it wasn't clear in the Xorg.0.log snippet I sent, but from > comparing log files, the actual error was this: >=20 > [351790.259] drmOpenByBusid: Interface 1.4 failed, trying 1.1 > ... > [351790.259] (EE) RADEON(0): [drm] failed to set drm interface version.= > [351790.259] (EE) RADEON(0): Kernel modesetting setup failed It made me think that somehow, radeondrm, the old kernel non-KMS module, was loaded. That's why I asked about xf86-video-ati{,-ums} 6.14.6. I don't know how this happened. --=20 Jean-S=E9bastien P=E9dron --6NmgNcp3SMXBaMG3CCOdUQLLEtRuT5QfI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUVLmcXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMHT4P/3vSxsP4/w8OHCPb62p0P3Go XWQThlMxypLO6g+hs1BOpruMoTpxuXutOq2+8rB2NIwFy96qhL4ot9/OCVmfsgyq 4SEQzHKj/1ttxM867ppHeZQtgPCepMWKPaYcacPrhm6t4Z3wmcV4atLpQjr+hGtS 5rCe4Cf1EzojG7NjzVBAK6IhMCCgt6TYTiKTBQDsfOvGn4A+eMg6BkxeWbxjksQI weYYqc3QwasDVlSsk2Yd92gAXs85sCtxvn0nNKmLEKhFUgZJM9dccNOaKfpH12Ji mRQRo1YA7Mf7uzOCcNIpZPlpqcKBa2URg9XoAEr92OBUGpj7KE+h0Jq/7k4iq7mj uBjrlRhOEdihAoveAi2I5cgtm5eeJwTT5jgya79dc9Lwqa43QF/B2BqHhIBUoG3n k7MAmlEQYFNAMXGdfdMA+oLpqk5m6ZLbo9shIT23i1b3iPdPODmJaNZfK/j64oJr nl8eenMUhr7sfmwBopNGgUgwsvvN6d8SH8LNUY65rpVNYiIY+N3+NxsmXHz8yLAQ 2Of4g5bMtHYDh/j1dv63AkAVOJS51hpUDNCPsBcVXaGTu0URM4cYzlqIHVtyiR89 2K6OYSJG/qgWM44P0pOzVY4vCuKuzTqXkO9T/UkcqOYIDM94+WW3wNhksMNbpN6j mIor1tOQXBtYfNrNZQb/ =bSLr -----END PGP SIGNATURE----- --6NmgNcp3SMXBaMG3CCOdUQLLEtRuT5QfI-- From owner-freebsd-stable@FreeBSD.ORG Sat Nov 1 18:47:24 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40E9BA0B; Sat, 1 Nov 2014 18:47:24 +0000 (UTC) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07198829; Sat, 1 Nov 2014 18:47:24 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id tr6so3221757ieb.28 for ; Sat, 01 Nov 2014 11:47:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xVPnOG4RxIucGnQJJoqZbED2UlV373QqHOnp9P4XwG8=; b=ZFS4T6NH4BUiDTxmLeeAm44ZuLwh5GKLlLCVb8tRWNuF4k9pojjOc7bLMWkhhkIYSg xsh4uY7qhNRkygjTWFuKKCeJecrnBmvGSRUWv0bdZNg3eDtJDTaal8vjKQZ6du9dnBvq RXs4h9BXPy7oZMMumfmwSB0cP5UiFwbXyzX5Mo7pBUPYGYIJdu4zkcKv++GmeViuL02i pBVUZXhrpDk7I6K3b4pVOLN6P5cypANP8xrTekTwMpI21MwwLn6aSl5olla7Kmhri8Vv cOZZWo6ZoyySPSX9xXsemACHDiHv11HtN2N/u9qbsYu1ByKh3YJRteQ+dJjTilRCd6jI e2jA== MIME-Version: 1.0 X-Received: by 10.42.25.204 with SMTP id b12mr31046992icc.14.1414867643259; Sat, 01 Nov 2014 11:47:23 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Sat, 1 Nov 2014 11:47:23 -0700 (PDT) In-Reply-To: <9c5f3b0230bf63d32ee8a83e81b1f167@ultimatedns.net> References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> <9c5f3b0230bf63d32ee8a83e81b1f167@ultimatedns.net> Date: Sat, 1 Nov 2014 11:47:23 -0700 X-Google-Sender-Auth: 8wmA8putkKjEUrjjPUuOpjIFsOg Message-ID: Subject: Re: Dump time issues From: Kevin Oberman To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Adrian Chadd , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 18:47:24 -0000 On Fri, Oct 31, 2014 at 8:10 AM, Chris H wrote: > On Tue, 28 Oct 2014 12:20:01 -0700 Adrian Chadd wrote > > > On 27 October 2014 11:09, Kevin Oberman wrote: > > > > >> I'm aware of two issues with SU+J, one of which is annoying and the > other > > > is worse. > > > 1. If the journal is not fully written on power fail or some other > reason, > > > you may need to do a full fsck of the volume and the behavior of the > system > > > until this is done can be very unpredictable. > > > 2. You can't safely snapshot the system. This is what 'dump -L' does. > This > > > means that some files dumped from a live FS may not be consistent (not > > > good!) or, if '-L' is used, the system may well hang. > > > > > > While I love the fast fsck times (2 or 3 seconds) after a crash, I also > > > question the default. Still, it may be a preferred choice be used for > very > > > large file systems where a full fsck would take a very long time as > long as > > > the risks are understood. For these systems, ZFS might be a better > choice. > > > These arguments do NOT favor it being the default, IMHO. > > > > If people can reproduce SU+J problems then please file bugs. There > > have been some fixes with the journal handling over the last year or > > so and I haven't had this problem on -HEAD any longer, but it doesn't > > mean it's there. > Problem existed on RELENG_9 as of 1 mos, and 1 wk. ago. I don't > have any useful output to provide (I simply blew away the system > && re-installed w/o SU+J). > > --Chris > You should be to deal with that using "tunefs -j disable". Much easier than re-installing. Would disabling soft updates journaling, snapshotting, and re-enabling would work around the issue? I might play with this when I get a chance. If it works, perhaps tools (mostly dump -L) could check for SU+J and turn it off for the time to snapshot the file system. I'm just not sure how well re-enabling works. Certainly some journal data would be lost, but the snapshot operation should make that irrelevant. I just don't know that I understand the details of SU+J well enough to know whether this would make sense. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sat Nov 1 18:52:30 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78542D4A; Sat, 1 Nov 2014 18:52:30 +0000 (UTC) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 383478FD; Sat, 1 Nov 2014 18:52:30 +0000 (UTC) Received: by mail-ig0-f172.google.com with SMTP id a13so2692773igq.17 for ; Sat, 01 Nov 2014 11:52:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=gZrgM9n7+X7udI18yJtIy9BrYql3fzFLhh2ui3p+IMw=; b=sz8pT5XW4XOvecc2rANRUOjlKvtgba7iXPlcKrEyD70sNQu7OFK6T7vEsU7YDTINZz g0o4j5/3bgOLpqRyjo0xKGeB/eXNlWAR++IY9Sx9eElcfCVkrOSTQ/axnLU4rwdhkxiL UxH2q6uw7kumcTEa8M4v9mOx+/ikHw9AEueNIrtfVfiCJQqbQ/zrdhTz+Mu8OskBAO1J UKSZTBhDqZmkCsyznjBltKjU9aCVhfUcttHZHKQPGN0UtsczwJGXd3XaSC5Cqcy/VlGc kX4sTpT7YkHYtHv3g/4ldlIEoiql2Z6a/i2FFsGloZgQxWwypQ4TlCkms2uxwfVWemRZ oB/A== MIME-Version: 1.0 X-Received: by 10.50.117.71 with SMTP id kc7mr5497282igb.35.1414867949559; Sat, 01 Nov 2014 11:52:29 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Sat, 1 Nov 2014 11:52:29 -0700 (PDT) In-Reply-To: References: <6978A7BF-3CB7-4088-904D-5A60D755A04C@gmail.com> <20141025113846.GY1235@albert.catwhisker.org> <6bb4cda435fb420fb663fa1d47b85a08@ultimatedns.net> <9c5f3b0230bf63d32ee8a83e81b1f167@ultimatedns.net> Date: Sat, 1 Nov 2014 11:52:29 -0700 X-Google-Sender-Auth: nZxglLNgTZ3saa3hFizfj4ymWSk Message-ID: Subject: Re: Dump time issues From: Kevin Oberman To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Adrian Chadd , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 18:52:30 -0000 On Sat, Nov 1, 2014 at 11:47 AM, Kevin Oberman wrote > On Fri, Oct 31, 2014 at 8:10 AM, Chris H wrote: > >> On Tue, 28 Oct 2014 12:20:01 -0700 Adrian Chadd >> wrote >> >> > On 27 October 2014 11:09, Kevin Oberman wrote: >> > >> > >> I'm aware of two issues with SU+J, one of which is annoying and the >> other >> > > is worse. >> > > 1. If the journal is not fully written on power fail or some other >> reason, >> > > you may need to do a full fsck of the volume and the behavior of the >> system >> > > until this is done can be very unpredictable. >> > > 2. You can't safely snapshot the system. This is what 'dump -L' does. >> This >> > > means that some files dumped from a live FS may not be consistent (not >> > > good!) or, if '-L' is used, the system may well hang. >> > > >> > > While I love the fast fsck times (2 or 3 seconds) after a crash, I >> also >> > > question the default. Still, it may be a preferred choice be used for >> very >> > > large file systems where a full fsck would take a very long time as >> long as >> > > the risks are understood. For these systems, ZFS might be a better >> choice. >> > > These arguments do NOT favor it being the default, IMHO. >> > >> > If people can reproduce SU+J problems then please file bugs. There >> > have been some fixes with the journal handling over the last year or >> > so and I haven't had this problem on -HEAD any longer, but it doesn't >> > mean it's there. >> Problem existed on RELENG_9 as of 1 mos, and 1 wk. ago. I don't >> have any useful output to provide (I simply blew away the system >> && re-installed w/o SU+J). >> >> --Chris >> > > You should be to deal with that using "tunefs -j disable". Much easier > than re-installing. > > Would disabling soft updates journaling, snapshotting, and re-enabling > would work around the issue? I might play with this when I get a chance. If > it works, perhaps tools (mostly dump -L) could check for SU+J and turn it > off for the time to snapshot the file system. I'm just not sure how well > re-enabling works. Certainly some journal data would be lost, but the > snapshot operation should make that irrelevant. I just don't know that I > understand the details of SU+J well enough to know whether this would make > sense. > Memo to self: Don't type stupid responses while watching football games! Enabling/disabling soft updates journaling requires unmounting the file system, and re-mounting after the change. In the case of root (or a single file system), it would require a reboot. A bit too intrusive for many cases. Why do I realize these things a few seconds AFTER hitting "Send"? -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com