From owner-freebsd-hackers@freebsd.org Tue Apr 19 10:19:21 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F541B1435E for ; Tue, 19 Apr 2016 10:19:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 1204112AE for ; Tue, 19 Apr 2016 10:19:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3JAJKsv075922 for ; Tue, 19 Apr 2016 10:19:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-hackers@FreeBSD.org Subject: [Bug 204716] boot loader bcache is trashed by larger sequential reads from zfs/ufs Date: Tue, 19 Apr 2016 10:19:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: tsoome@me.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-hackers@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 19 Apr 2016 11:37:35 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 10:19:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204716 Toomas Soome changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #4 from Toomas Soome --- fix implemented as https://svnweb.freebsd.org/base?view=3Drevision&revision=3D298230 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-hackers@freebsd.org Tue Apr 19 12:49:51 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21A57B1311C; Tue, 19 Apr 2016 12:49:51 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF6BA18A6; Tue, 19 Apr 2016 12:49:50 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id n3so27896432wmn.0; Tue, 19 Apr 2016 05:49:50 -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; bh=zy2HrFFzM9gHWymH4CXb2AUCo3ApgxNdonvFdA1XSmo=; b=OQf7TZn/RQWEZMTCkZVjoGslq3itUCnQCEVNGUg0fWDktQtPzGcLMovMFqBO7T02Tk YhY5tKTIWdp4aiL7Wqs+v+Ls8cr+9znLicojWy8eMr1uP8YLPcx8H7nbawAiF3Zaif9M kDfbL/5EM3dgweMwet+vnwPLConUfui7XS+cW1aXTP53cgLnkote2yXzdI6vJD7o9M8l CWxJbjg5VG4LYC609zMZnRZXDfSXYwSuri+xJLdi1HW5Cl+0RvTZLDARLAmwJGU9UoCG AeGBH7qSuuL66UETqUtp0ebM9Lgkb9V1OsmOE2xsp+JUE5pBV7WezwiundyJsDB2yy0R dmYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=zy2HrFFzM9gHWymH4CXb2AUCo3ApgxNdonvFdA1XSmo=; b=PdZtCHUh6A5OteWkMN9eSc3utBUZlzokYn8IcnmJYOddZZ9T2l0X/IMVTBRpVR9DM8 bkdBVJocRKf3Lc3m6PE7GIeivzmpogA0zKaiD9J6SXGEWJ7VXmnL6I7c93QN1PQkQNwe mAvo1t7Z4BYRcp/8mvo3J/WY1bt0bSomkRm7YB2vzFJzhrfI0M2Dlg8otoX9CEqfmH8W jGmi/fR2F1WdznLZw/YdYAW3mmwSrcS7Pz0Nuf6SUJlOfZE403Ngf6AfOjrdqKxSqizn 1azvCdqkNY3A6gqLMetCrsvU6ebVtwqNNu9gfRExaNyTSE2xM4QnY4+bK/OgpVF5zd2z 7T6g== X-Gm-Message-State: AOPr4FUt/LEHNqrNMUzLfLshpc7W9Wd1KpmaV/QXd07wZcAxIbpw+FNSuoUdim5urYwIrEwHnmAJ20kf8rV2sg== MIME-Version: 1.0 X-Received: by 10.28.51.5 with SMTP id z5mr3727707wmz.101.1461070188325; Tue, 19 Apr 2016 05:49:48 -0700 (PDT) Received: by 10.194.21.162 with HTTP; Tue, 19 Apr 2016 05:49:48 -0700 (PDT) Date: Tue, 19 Apr 2016 18:19:48 +0530 Message-ID: Subject: Toggling between remote KGDB and local DDB within a debugging session From: Aijaz Baig To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 19 Apr 2016 13:42:56 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 12:49:51 -0000 Hello I think the title says it all!! :) I would like to know if there is indeed a way to toggle between gdb and ddb while debugging a remote kernel. I am already at the gdb (or rather kgdb) prompt. From here how do I switch to local ddb on the debugged machine?? My kernel configuration file already contains 'options BREAK_TO_DEBUGGER' and I have BOTH GDB and DDB configured aka: options GDB options DDB I tried adding 'options KDB_UNATTENDED' but that does not make any difference. As per the developer's handbook, "Every time you type gdb, the mode will be toggled between remote GDB and local DDB. In order to force a next trap immediately, simply type s (step). Your hosting GDB will now gain control over the target kernel:" Now when you type 'gdb' at the DDB prompt, KGDB takes over remotely. On continuing at the KGDB prompt, you arrive back at the debugged machine but it is not longer under the control of DDB. My question is, how do I drop to DDB from within a running machine whose serial ports (albeit virtual ones) are remotely attached to another machine? When remote remote KGDB is listening and I force a panic using 'sysctl debug.kdb.enter=1', it drops into remote KGDB. However, when it is NOT listening on the serial port, the local system just freezes What I want, is to enter ddb on the local machine. Do some debugging using it; drop to remote KGDB for things that are best done using KGDB, then switch back to local DDB when I'm done. Is there a way to do that? If yes please do let me know -- Best Regards, Aijaz Baig From owner-freebsd-hackers@freebsd.org Tue Apr 19 13:59:04 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF6C5B14C1A for ; Tue, 19 Apr 2016 13:59:04 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from rayleigh.systella.fr (newton-ipv6.systella.fr [IPv6:2001:7a8:a8ed:253::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rayleigh.systella.fr", Issuer "rayleigh.systella.fr" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 86FDB1707 for ; Tue, 19 Apr 2016 13:59:04 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from [192.168.2.3] (schroedinger.eikeo.com [192.168.2.3]) (authenticated bits=0) by rayleigh.systella.fr (8.15.2/8.15.2/Debian-4) with ESMTPSA id u3JDwgVR012833 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Tue, 19 Apr 2016 15:58:46 +0200 To: freebsd-hackers@freebsd.org From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= Subject: Diskless workstation and some minor issues Message-ID: <57163991.4000100@systella.fr> Date: Tue, 19 Apr 2016 15:58:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99.1 at rayleigh X-Virus-Status: Clean X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 13:59:04 -0000 Hello, I have installed a diskless workstation (10.2-RELEASE-p14) that mounts its rootfs from a NetBSD nfs server. My fstab is : root@pythagore:~ # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# 192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw 0 0 ... 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw 0 0 root@pythagore:~ # First question. I have installed this diskless workstation with an USB stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first time, it tries to mount usbus0 (!) : Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 usbus0 Apr 9 10:48:00 pythagore kernel: uhub0: 2 ports with 2 removable, self powered Apr 9 10:48:00 pythagore kernel: uhub2: 2 ports with 2 removable, self powered Apr 9 10:48:00 pythagore kernel: uhub1: 21 ports with 21 removable, self powered Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 usbus0 Apr 9 10:48:00 pythagore kernel: ugen0.2: at usbus0 Apr 9 10:48:00 pythagore kernel: ugen2.2: at usbus2 Apr 9 10:48:00 pythagore kernel: uhub3: on usbus2 Apr 9 10:48:00 pythagore kernel: ugen1.2: at usbus1 Apr 9 10:48:01 pythagore kernel: uhub4: on usbus1 Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus2 usbus1 usbus0 Apr 9 10:48:01 pythagore kernel: uhub4: 6 ports with 6 removable, self powered Apr 9 10:48:01 pythagore kernel: uhub3: 8 ports with 8 removable, self powered Apr 9 10:48:01 pythagore kernel: ugen0.3: at usbus0 Apr 9 10:48:01 pythagore kernel: ukbd0: on usbus0 Apr 9 10:48:01 pythagore kernel: kbd2 at ukbd0 Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_IOERROR Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_IOERROR Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_IOERROR Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_IOERROR Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_IOERROR Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 (disconnected) Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not allocate new device Apr 9 10:48:02 pythagore kernel: Trying to mount root from nfs:192.168.10.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... Apr 9 10:48:02 pythagore kernel: NFS ROOT: 192.168.10.128:/srv/pythagore I don't understand why kernel tries to mount an USB rootfs... And I haven't found how fix this trouble. Second trouble. /var/log/message contains a lot of : Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: Permission denied Of course, lockd and statd are running on nfs server. Permission on /var/at are : root@pythagore:/var/at # ls -al total 8 drwxr-xr-x 4 root wheel 512 Aug 12 2015 . drwxr-xr-x 28 root wheel 512 Apr 15 09:14 .. drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 jobs drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 spool root@pythagore:/var/at # I don't understand where is the mistake. An third trouble, this workstation runs cupsd. When I send a job to printer, cupsd run as expected but aborts after job is completed. In /var/log/cups/error_log, I have : E [19/Apr/2016:12:44:34 +0200] Unable to create "/usr/local/etc/cups/printers.conf.N": Operation not permitted E [19/Apr/2016:12:45:12 +0200] Unable to create "/var/cache/cups/job.cache.N": Operation not permitted E [19/Apr/2016:12:45:12 +0200] Unable to create "/var/spool/cups/c00032.N": Operation not permitted I have checked permissions on directories (and config file) without any result, but I have seen that permissions on /var/spool/cups are overwrittem by cups (to drwx--x---). All help will be welcome. Thanks in advance, JB From owner-freebsd-hackers@freebsd.org Tue Apr 19 14:14:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B66C2B13398 for ; Tue, 19 Apr 2016 14:14:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 9421711C6 for ; Tue, 19 Apr 2016 14:14:06 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: ff8fff3b-0638-11e6-8bda-c73aafa13d19 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 19 Apr 2016 14:14:15 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u3JEE3qe035745; Tue, 19 Apr 2016 08:14:03 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1461075243.1232.9.camel@freebsd.org> Subject: Re: Diskless workstation and some minor issues From: Ian Lepore To: BERTRAND =?ISO-8859-1?Q?Jo=EBl?= , freebsd-hackers@freebsd.org Date: Tue, 19 Apr 2016 08:14:03 -0600 In-Reply-To: <57163991.4000100@systella.fr> References: <57163991.4000100@systella.fr> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:14:06 -0000 On Tue, 2016-04-19 at 15:58 +0200, BERTRAND Joël wrote: > > Hello, > > > I have installed a diskless workstation (10.2-RELEASE-p14) that mounts > its rootfs from a NetBSD nfs server. My fstab is : > > root@pythagore:~ # cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > 192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw > 0 0 > ... > 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw > 0 0 > root@pythagore:~ # > > > First question. I have installed this diskless workstation with an USB > stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first time, > it tries to mount usbus0 (!) : > > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 > usbus0 > Apr 9 10:48:00 pythagore kernel: uhub0: 2 ports with 2 removable, self > powered > Apr 9 10:48:00 pythagore kernel: uhub2: 2 ports with 2 removable, self > powered > Apr 9 10:48:00 pythagore kernel: uhub1: 21 ports with 21 removable, > self powered > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 > usbus0 > Apr 9 10:48:00 pythagore kernel: ugen0.2: at usbus0 > Apr 9 10:48:00 pythagore kernel: ugen2.2: at usbus2 > Apr 9 10:48:00 pythagore kernel: uhub3: > class 9/0, rev 2.00/0.00, addr 2> on usbus2 > Apr 9 10:48:00 pythagore kernel: ugen1.2: at usbus1 > Apr 9 10:48:01 pythagore kernel: uhub4: > class 9/0, rev 2.00/0.00, addr 2> on usbus1 > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus2 usbus1 > usbus0 > Apr 9 10:48:01 pythagore kernel: uhub4: 6 ports with 6 removable, self > powered > Apr 9 10:48:01 pythagore kernel: uhub3: 8 ports with 8 removable, self > powered > Apr 9 10:48:01 pythagore kernel: ugen0.3: at usbus0 > Apr 9 10:48:01 pythagore kernel: ukbd0: > 0/0, rev 1.10/1.12, addr 2> on usbus0 > Apr 9 10:48:01 pythagore kernel: kbd2 at ukbd0 > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_IOERROR > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_IOERROR > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_IOERROR > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_IOERROR > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_IOERROR > Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 > (disconnected) > Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not allocate > new device > Apr 9 10:48:02 pythagore kernel: Trying to mount root from > nfs:192.168.10.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... > Apr 9 10:48:02 pythagore kernel: NFS ROOT: 192.168.10.128:/srv/pythagore > > > I don't understand why kernel tries to mount an USB rootfs... And I > haven't found how fix this trouble. > At this point during booting, the system doesn't know what physical device may hold the rootfs, so it waits until it has enumerated all the devices on all the USB busses, in case one of them is required to mount root (even in the NFS case, it could require a USB network device). To disable this wait, put hw.usb.no_boot_wait=1 in loader.conf. > Second trouble. /var/log/message contains a lot of : > Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: > Permission denied > > > Of course, lockd and statd are running on nfs server. Permission on > /var/at are : > > root@pythagore:/var/at # ls -al > total 8 > drwxr-xr-x 4 root wheel 512 Aug 12 2015 . > drwxr-xr-x 28 root wheel 512 Apr 15 09:14 .. > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 jobs > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 spool > root@pythagore:/var/at # > > > I don't understand where is the mistake. > This is a more serious problem. I have found it to be impossible to run a diskless workstation with a persistant /var mounted via NFS (either by itself or as a directory within the nfs rootfs). It's been this way for several years. You can add varmfs=yes to your rc.conf to get a working system, but then you have a non-persistant /var which really isn't very useful. Hmm, but the problems I usually have are with /var/run and pidfiles. I've never noticed this /var/at problem (maybe just because I gave up trying to run with an nfs-mounted /var before I noticed them). > An third trouble, this workstation runs cupsd. When I send a job to > printer, cupsd run as expected but aborts after job is completed. In > /var/log/cups/error_log, I have : > > E [19/Apr/2016:12:44:34 +0200] Unable to create > "/usr/local/etc/cups/printers.conf.N": Operation not permitted > E [19/Apr/2016:12:45:12 +0200] Unable to create > "/var/cache/cups/job.cache.N": Operation not permitted > E [19/Apr/2016:12:45:12 +0200] Unable to create > "/var/spool/cups/c00032.N": Operation not permitted > > > I have checked permissions on directories (and config file) without any > result, but I have seen that permissions on /var/spool/cups are > overwrittem by cups (to drwx--x---). > This one I can't help with at all, because I gave up on trying to get printers to work on freebsd about 10 years ago and haven't had the energy to ever try again. :( -- Ian From owner-freebsd-hackers@freebsd.org Tue Apr 19 14:16:03 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFD37B134EB for ; Tue, 19 Apr 2016 14:16:03 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A33BA1389; Tue, 19 Apr 2016 14:16:03 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x235.google.com with SMTP id k142so10037739oib.1; Tue, 19 Apr 2016 07:16:03 -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; bh=QgsobtqvT5EXu+0LHN3Fi/6SYIb4cBZmF27TdNQil5Q=; b=SQ5cR2eWH8SIk1TN083lIgS5Yeq0aaj+WIquEN8kSQSEN7xpqjbhouvE8lDtdFd0XZ KZWeZ28ysmbG+OzRW23b55EQ/sWJaBpOuSz+MOJigazHtzDreUlLvijiD34H/lGqgaSe FXIDscXmFt0MSo5i6tKWm7Vb/5CdJhjzQl6YGjvls89Fu+1gWfBJ3aLUDozfuWl5swN4 AYE8dFroXJw8ubID+ox/dTzvOWoGAbnY7p2d8GOqGUV8bznItfORozONW7eG+HSaE5mT frE7Rm/nNuEKqie8z/QVaJ087yzCBX+cF7urEQV188vJPYKqP0c54ZlSUIjO8ZqQyN6w OXzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=QgsobtqvT5EXu+0LHN3Fi/6SYIb4cBZmF27TdNQil5Q=; b=mk+87tAj75+GnfiSWzGdzx2cmAryLduNCIZyGyrxgsD6XceW8cMuxXn82HFsOFu/Xn T8uJsYESsv1l7dxG8lxFT4vNoNVS2iIT2iq/jpZP51o/JK7mEa+eBzjZnXS+4EC5XY++ F7ywufme3lC/U9gJpkOv3ZrK+PjZHyDdQnTqj5ip65e3jbE6Lh2lUimZngDwzEDShC5Z iru/lAK+sFK6sGUwl4LBkjhg/CkhR1G5BcX5/KVL/lt0lnPFJ0oS52cBDdDiWN2vAzkP SKUjXczl5W7k7fsOMxR4dzMbHAZQdC57+prE1G8/ToaQ1dvLgOiY3QoNvBIqzd5OnyIv VPpw== X-Gm-Message-State: AOPr4FXJmHfoRZmL9dCaEZOH0Kbu2YUuJIBWU0z/Xp2Ciwxx+22D9T3AeiUmz+MrsHbqPcqFNUJ4I05JJf8VXQ== MIME-Version: 1.0 X-Received: by 10.202.77.146 with SMTP id a140mr528765oib.86.1461075363047; Tue, 19 Apr 2016 07:16:03 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Tue, 19 Apr 2016 07:16:02 -0700 (PDT) In-Reply-To: <1461075243.1232.9.camel@freebsd.org> References: <57163991.4000100@systella.fr> <1461075243.1232.9.camel@freebsd.org> Date: Tue, 19 Apr 2016 08:16:02 -0600 X-Google-Sender-Auth: di_G7w0CWi2mOBfJhfzuyxSj_Ic Message-ID: Subject: Re: Diskless workstation and some minor issues From: Alan Somers To: Ian Lepore Cc: =?UTF-8?Q?BERTRAND_Jo=C3=ABl?= , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:16:04 -0000 On Tue, Apr 19, 2016 at 8:14 AM, Ian Lepore wrote: > On Tue, 2016-04-19 at 15:58 +0200, BERTRAND Jo=C3=ABl wrote: > > > Hello, > > > > > I have installed a diskless workstation (10.2-RELEASE-p14) that > mounts > > its rootfs from a NetBSD nfs server. My fstab is : > > > > root@pythagore:~ # cat /etc/fstab > > # Device Mountpoint FStype Options Dump Pass# > > 192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw > > 0 0 > > ... > > 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw > > 0 0 > > root@pythagore:~ # > > > > > First question. I have installed this diskless workstation with > an USB > > stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first time, > > it tries to mount usbus0 (!) : > > > > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 > > usbus0 > > Apr 9 10:48:00 pythagore kernel: uhub0: 2 ports with 2 removable, self > > powered > > Apr 9 10:48:00 pythagore kernel: uhub2: 2 ports with 2 removable, self > > powered > > Apr 9 10:48:00 pythagore kernel: uhub1: 21 ports with 21 removable, > > self powered > > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 > > usbus0 > > Apr 9 10:48:00 pythagore kernel: ugen0.2: at usbus0 > > Apr 9 10:48:00 pythagore kernel: ugen2.2: at usbus2 > > Apr 9 10:48:00 pythagore kernel: uhub3: > > class 9/0, rev 2.00/0.00, addr 2> on usbus2 > > Apr 9 10:48:00 pythagore kernel: ugen1.2: at usbus1 > > Apr 9 10:48:01 pythagore kernel: uhub4: > > class 9/0, rev 2.00/0.00, addr 2> on usbus1 > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus2 usbus1 > > usbus0 > > Apr 9 10:48:01 pythagore kernel: uhub4: 6 ports with 6 removable, self > > powered > > Apr 9 10:48:01 pythagore kernel: uhub3: 8 ports with 8 removable, self > > powered > > Apr 9 10:48:01 pythagore kernel: ugen0.3: at usbus0 > > Apr 9 10:48:01 pythagore kernel: ukbd0: > > 0/0, rev 1.10/1.12, addr 2> on usbus0 > > Apr 9 10:48:01 pythagore kernel: kbd2 at ukbd0 > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting devic= e > > descriptor at addr 3 failed, USB_ERR_IOERROR > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting devic= e > > descriptor at addr 3 failed, USB_ERR_IOERROR > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting devic= e > > descriptor at addr 3 failed, USB_ERR_IOERROR > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting devic= e > > descriptor at addr 3 failed, USB_ERR_IOERROR > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting devic= e > > descriptor at addr 3 failed, USB_ERR_IOERROR > > Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 > > (disconnected) > > Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not allocat= e > > new device > > Apr 9 10:48:02 pythagore kernel: Trying to mount root from > > nfs:192.168.10.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... > > Apr 9 10:48:02 pythagore kernel: NFS ROOT: 192.168.10.128: > /srv/pythagore > > > > > I don't understand why kernel tries to mount an USB rootfs... > And I > > haven't found how fix this trouble. > > > > At this point during booting, the system doesn't know what physical > device may hold the rootfs, so it waits until it has enumerated all the > devices on all the USB busses, in case one of them is required to mount > root (even in the NFS case, it could require a USB network device). > > To disable this wait, put hw.usb.no_boot_wait=3D1 in loader.conf. > > > Second trouble. /var/log/message contains a lot of : > > Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: > > Permission denied > > > > > Of course, lockd and statd are running on nfs server. Permissio= n > on > > /var/at are : > > > > root@pythagore:/var/at # ls -al > > total 8 > > drwxr-xr-x 4 root wheel 512 Aug 12 2015 . > > drwxr-xr-x 28 root wheel 512 Apr 15 09:14 .. > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 jobs > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 spool > > root@pythagore:/var/at # > > > > > I don't understand where is the mistake. > > > > This is a more serious problem. I have found it to be impossible to > run a diskless workstation with a persistant /var mounted via NFS > (either by itself or as a directory within the nfs rootfs). It's been > this way for several years. You can add varmfs=3Dyes to your rc.conf to > get a working system, but then you have a non-persistant /var which > really isn't very useful. > > Hmm, but the problems I usually have are with /var/run and pidfiles. > I've never noticed this /var/at problem (maybe just because I gave up > trying to run with an nfs-mounted /var before I noticed them). > > > An third trouble, this workstation runs cupsd. When I send a job = to > > printer, cupsd run as expected but aborts after job is completed. In > > /var/log/cups/error_log, I have : > > > > E [19/Apr/2016:12:44:34 +0200] Unable to create > > "/usr/local/etc/cups/printers.conf.N": Operation not permitted > > E [19/Apr/2016:12:45:12 +0200] Unable to create > > "/var/cache/cups/job.cache.N": Operation not permitted > > E [19/Apr/2016:12:45:12 +0200] Unable to create > > "/var/spool/cups/c00032.N": Operation not permitted > > > > > I have checked permissions on directories (and config file) > without any > > result, but I have seen that permissions on /var/spool/cups are > > overwrittem by cups (to drwx--x---). > > > > This one I can't help with at all, because I gave up on trying to get > printers to work on freebsd about 10 years ago and haven't had the > energy to ever try again. :( > > -- Ian > Check your /etc/exports on the server. Both of these problems could be explained if your server has -maproot set (or whatever NetBSD calls it). For diskless workstations, you must turn that off at the server. -Alan From owner-freebsd-hackers@freebsd.org Tue Apr 19 14:32:30 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB5C0B13DAB for ; Tue, 19 Apr 2016 14:32:30 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (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 674CF1326 for ; Tue, 19 Apr 2016 14:32:29 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.30] ([194.32.164.30]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id u3JEN8w1090359; Tue, 19 Apr 2016 15:23:08 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Diskless workstation and some minor issues From: Bob Bishop In-Reply-To: <57163991.4000100@systella.fr> Date: Tue, 19 Apr 2016 15:23:08 +0100 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <57163991.4000100@systella.fr> To: =?utf-8?Q?BERTRAND_Jo=C3=ABl?= X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:32:30 -0000 Hi, > On 19 Apr 2016, at 14:58, BERTRAND Jo=C3=ABl = wrote: >=20 > Hello, >=20 > I have installed a diskless workstation (10.2-RELEASE-p14) that = mounts its rootfs from a NetBSD nfs server. My fstab is : >=20 > root@pythagore:~ # cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > 192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw = 0 0 > ... > 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw = 0 0 > root@pythagore:~ # >=20 > First question. I have installed this diskless workstation with = an USB stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first = time, it tries to mount usbus0 (!) : >=20 > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 = usbus1 usbus0 [snip] > Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 = (disconnected) > Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not = allocate new device > Apr 9 10:48:02 pythagore kernel: Trying to mount root from = nfs:192.168.10.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... > Apr 9 10:48:02 pythagore kernel: NFS ROOT: = 192.168.10.128:/srv/pythagore >=20 > I don't understand why kernel tries to mount an USB rootfs... = And I haven't found how fix this trouble. It doesn=E2=80=99t. It waits for USB just in case the root is on USB, I = assume this isn=E2=80=99t optimised to keep things simple. > Second trouble. /var/log/message contains a lot of : > Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: = Permission denied [etc] I suspect the rest of your troubles are due to the usual default NFS = root =3D> nobody mapping. You probably need something like -maproot=3D0 = somewhere in /etc/exports on the server; RTFM exports(5). -- Bob Bishop rb@gid.co.uk From owner-freebsd-hackers@freebsd.org Tue Apr 19 14:32:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E9D5B13DE4 for ; Tue, 19 Apr 2016 14:32:43 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 456A6143B for ; Tue, 19 Apr 2016 14:32:43 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 96a757f1-063b-11e6-9fea-b54670b854a5 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 19 Apr 2016 14:32:47 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u3JEWZvL035783; Tue, 19 Apr 2016 08:32:35 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1461076355.1232.17.camel@freebsd.org> Subject: Re: Diskless workstation and some minor issues From: Ian Lepore To: Alan Somers Cc: "freebsd-hackers@freebsd.org" , BERTRAND =?ISO-8859-1?Q?Jo=EBl?= Date: Tue, 19 Apr 2016 08:32:35 -0600 In-Reply-To: References: <57163991.4000100@systella.fr> <1461075243.1232.9.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:32:43 -0000 On Tue, 2016-04-19 at 08:16 -0600, Alan Somers wrote: > On Tue, Apr 19, 2016 at 8:14 AM, Ian Lepore wrote: > > > On Tue, 2016-04-19 at 15:58 +0200, BERTRAND Joël wrote: > > > > Hello, > > > > > > > I have installed a diskless workstation (10.2-RELEASE > > > -p14) that > > mounts > > > its rootfs from a NetBSD nfs server. My fstab is : > > > > > > root@pythagore:~ # cat /etc/fstab > > > # Device Mountpoint FStype Options Dump Pass# > > > 192.168.10.128:/srv/pythagore / nfs > > > nfsv3,tcp,soft,intr,rw > > > 0 0 > > > ... > > > 192.168.10.128:/home /home nfs > > > nfsv3,tcp,soft,intr,rw > > > 0 0 > > > root@pythagore:~ # > > > > > > > First question. I have installed this diskless > > > workstation with > > an USB > > > stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first > > > time, > > > it tries to mount usbus0 (!) : > > > > > > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 > > > usbus1 > > > usbus0 > > > Apr 9 10:48:00 pythagore kernel: uhub0: 2 ports with 2 > > > removable, self > > > powered > > > Apr 9 10:48:00 pythagore kernel: uhub2: 2 ports with 2 > > > removable, self > > > powered > > > Apr 9 10:48:00 pythagore kernel: uhub1: 21 ports with 21 > > > removable, > > > self powered > > > Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 > > > usbus1 > > > usbus0 > > > Apr 9 10:48:00 pythagore kernel: ugen0.2: at usbus0 > > > Apr 9 10:48:00 pythagore kernel: ugen2.2: at usbus2 > > > Apr 9 10:48:00 pythagore kernel: uhub3: > > > class 9/0, rev 2.00/0.00, addr 2> on usbus2 > > > Apr 9 10:48:00 pythagore kernel: ugen1.2: at usbus1 > > > Apr 9 10:48:01 pythagore kernel: uhub4: > > > class 9/0, rev 2.00/0.00, addr 2> on usbus1 > > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus2 > > > usbus1 > > > usbus0 > > > Apr 9 10:48:01 pythagore kernel: uhub4: 6 ports with 6 > > > removable, self > > > powered > > > Apr 9 10:48:01 pythagore kernel: uhub3: 8 ports with 8 > > > removable, self > > > powered > > > Apr 9 10:48:01 pythagore kernel: ugen0.3: at usbus0 > > > Apr 9 10:48:01 pythagore kernel: ukbd0: > > > 0/0, rev 1.10/1.12, addr 2> on usbus0 > > > Apr 9 10:48:01 pythagore kernel: kbd2 at ukbd0 > > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting > > > device > > > descriptor at addr 3 failed, USB_ERR_IOERROR > > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting > > > device > > > descriptor at addr 3 failed, USB_ERR_IOERROR > > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:01 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:01 pythagore kernel: usbd_setup_device_desc: getting > > > device > > > descriptor at addr 3 failed, USB_ERR_IOERROR > > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting > > > device > > > descriptor at addr 3 failed, USB_ERR_IOERROR > > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:02 pythagore kernel: Root mount waiting for: usbus0 > > > Apr 9 10:48:02 pythagore kernel: usbd_setup_device_desc: getting > > > device > > > descriptor at addr 3 failed, USB_ERR_IOERROR > > > Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 > > > (disconnected) > > > Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not > > > allocate > > > new device > > > Apr 9 10:48:02 pythagore kernel: Trying to mount root from > > > nfs:192.168.10.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... > > > Apr 9 10:48:02 pythagore kernel: NFS ROOT: 192.168.10.128: > > /srv/pythagore > > > > > > > I don't understand why kernel tries to mount an USB > > > rootfs... > > And I > > > haven't found how fix this trouble. > > > > > > > At this point during booting, the system doesn't know what physical > > device may hold the rootfs, so it waits until it has enumerated all > > the > > devices on all the USB busses, in case one of them is required to > > mount > > root (even in the NFS case, it could require a USB network device). > > > > To disable this wait, put hw.usb.no_boot_wait=1 in loader.conf. > > > > > Second trouble. /var/log/message contains a lot of : > > > Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: > > > Permission denied > > > > > > > Of course, lockd and statd are running on nfs server. > > > Permission > > on > > > /var/at are : > > > > > > root@pythagore:/var/at # ls -al > > > total 8 > > > drwxr-xr-x 4 root wheel 512 Aug 12 2015 . > > > drwxr-xr-x 28 root wheel 512 Apr 15 09:14 .. > > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 jobs > > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 spool > > > root@pythagore:/var/at # > > > > > > > I don't understand where is the mistake. > > > > > > > This is a more serious problem. I have found it to be impossible > > to > > run a diskless workstation with a persistant /var mounted via NFS > > (either by itself or as a directory within the nfs rootfs). It's > > been > > this way for several years. You can add varmfs=yes to your rc.conf > > to > > get a working system, but then you have a non-persistant /var which > > really isn't very useful. > > > > Hmm, but the problems I usually have are with /var/run and > > pidfiles. > > I've never noticed this /var/at problem (maybe just because I gave > > up > > trying to run with an nfs-mounted /var before I noticed them). > > > > > An third trouble, this workstation runs cupsd. When I send > > > a job to > > > printer, cupsd run as expected but aborts after job is completed. > > > In > > > /var/log/cups/error_log, I have : > > > > > > E [19/Apr/2016:12:44:34 +0200] Unable to create > > > "/usr/local/etc/cups/printers.conf.N": Operation not permitted > > > E [19/Apr/2016:12:45:12 +0200] Unable to create > > > "/var/cache/cups/job.cache.N": Operation not permitted > > > E [19/Apr/2016:12:45:12 +0200] Unable to create > > > "/var/spool/cups/c00032.N": Operation not permitted > > > > > > > I have checked permissions on directories (and config > > > file) > > without any > > > result, but I have seen that permissions on /var/spool/cups are > > > overwrittem by cups (to drwx--x---). > > > > > > > This one I can't help with at all, because I gave up on trying to > > get > > printers to work on freebsd about 10 years ago and haven't had the > > energy to ever try again. :( > > > > -- Ian > > > > Check your /etc/exports on the server. Both of these problems could > be > explained if your server has -maproot set (or whatever NetBSD calls > it). > For diskless workstations, you must turn that off at the server. > > -Alan This sounds backwards. With no -maproot, the default is to use a uid/gid of -2/-2; how would the rc scripts be able to create files in /var and manipulate entropy files and all the other root-y things they do? All my nfsroot exports use -maproot 0. Hmmm, I wonder if -maproot 0:0 would be better (not that I expect that change alone to make diskless /var start working again). -- Ian From owner-freebsd-hackers@freebsd.org Tue Apr 19 14:37:34 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB71CB141CB for ; Tue, 19 Apr 2016 14:37:34 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from rayleigh.systella.fr (newton-ipv6.systella.fr [IPv6:2001:7a8:a8ed:253::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rayleigh.systella.fr", Issuer "rayleigh.systella.fr" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A14491B28; Tue, 19 Apr 2016 14:37:34 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from [192.168.2.3] (schroedinger.eikeo.com [192.168.2.3]) (authenticated bits=0) by rayleigh.systella.fr (8.15.2/8.15.2/Debian-4) with ESMTPSA id u3JEbGHw022011 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 19 Apr 2016 16:37:19 +0200 Subject: Re: Diskless workstation and some minor issues To: Alan Somers , Ian Lepore Cc: "freebsd-hackers@freebsd.org" References: <57163991.4000100@systella.fr> <1461075243.1232.9.camel@freebsd.org> From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= Message-ID: <5716429C.9000907@systella.fr> Date: Tue, 19 Apr 2016 16:37:16 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.99.1 at rayleigh X-Virus-Status: Clean X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:37:35 -0000 Alan Somers a écrit : > > Check your /etc/exports on the server. Both of these problems could be > explained if your server has -maproot set (or whatever NetBSD calls it). > For diskless workstations, you must turn that off at the server. Thanks for your answer. Of course, it's the first file I have checked. Here is my configuration on NFS server side : legendre# cat exports /home -network 192.168.10.0 -mask 255.255.255.0 \ -maproot=nobody /srv/pythagore -network 192.168.10.0 -mask 255.255.255.0 \ -maproot=root legendre# Best regards, JB From owner-freebsd-hackers@freebsd.org Tue Apr 19 15:10:58 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A952B13547; Tue, 19 Apr 2016 15:10:58 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FA001A11; Tue, 19 Apr 2016 15:10:57 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-252-92.lns20.per4.internode.on.net [121.45.252.92]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u3JFAq6i017989 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 19 Apr 2016 08:10:55 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: Toggling between remote KGDB and local DDB within a debugging session To: Aijaz Baig , freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org References: From: Julian Elischer Message-ID: <57164A76.4050403@freebsd.org> Date: Tue, 19 Apr 2016 23:10:46 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 15:10:58 -0000 On 19/04/2016 8:49 PM, Aijaz Baig wrote: > Hello > > I think the title says it all!! :) > > I would like to know if there is indeed a way to toggle between gdb > and ddb while debugging a remote kernel. I am already at the gdb (or > rather kgdb) prompt. From here how do I switch to local ddb on the > debugged machine?? you don't .. at teh moment I think it' s a one way street, but at one stage you could "detach" and it wuld switch back to ddb.. I don't think that works any more.. I've looked at making it work more than once but never got enough of an understanding to make it work, I suspect that it is a case of setting the appropriate word somewhere to teh appropriate value. How to find that location from gdb is the hard part. > My kernel configuration file already contains 'options > BREAK_TO_DEBUGGER' and I have BOTH GDB and DDB configured aka: > options GDB > options DDB > > I tried adding 'options KDB_UNATTENDED' but that does not make any difference. > > As per the developer's handbook, "Every time you type gdb, the mode > will be toggled between remote GDB and local DDB. In order to force a > next trap immediately, simply type s (step). Your hosting GDB will now > gain control over the target kernel:" Now when you type 'gdb' at the > DDB prompt, KGDB takes over remotely. On continuing at the KGDB > prompt, you arrive back at the debugged machine but it is not longer > under the control of DDB. > > My question is, how do I drop to DDB from within a running machine > whose serial ports (albeit virtual ones) are remotely attached to > another machine? When remote remote KGDB is listening and I force a > panic using 'sysctl debug.kdb.enter=1', it drops into remote KGDB. > However, when it is NOT listening on the serial port, the local system > just freezes > > What I want, is to enter ddb on the local machine. Do some debugging > using it; drop to remote KGDB for things that are best done using > KGDB, then switch back to local DDB when I'm done. > > Is there a way to do that? If yes please do let me know > From owner-freebsd-hackers@freebsd.org Tue Apr 19 16:12:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 659A5B143E4 for ; Tue, 19 Apr 2016 16:12:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 DAC4C1C25; Tue, 19 Apr 2016 16:12:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u3JGC1TO037594 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 19 Apr 2016 19:12:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u3JGC1TO037594 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u3JGC1x9037593; Tue, 19 Apr 2016 19:12:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 19 Apr 2016 19:12:01 +0300 From: Konstantin Belousov To: Ian Lepore Cc: BERTRAND Jo?l , freebsd-hackers@freebsd.org Subject: Re: Diskless workstation and some minor issues Message-ID: <20160419161201.GZ2422@kib.kiev.ua> References: <57163991.4000100@systella.fr> <1461075243.1232.9.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1461075243.1232.9.camel@freebsd.org> User-Agent: Mutt/1.6.0 (2016-04-01) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:12:06 -0000 On Tue, Apr 19, 2016 at 08:14:03AM -0600, Ian Lepore wrote: > On Tue, 2016-04-19 at 15:58 +0200, BERTRAND Jo?l wrote: > > Second trouble. /var/log/message contains a lot of : > > Apr 9 10:50:00 pythagore atrun[862]: cannot lock /var/at/jobs/: > > Permission denied > > > > > Of course, lockd and statd are running on nfs server. Permission on > > /var/at are : > > > > root@pythagore:/var/at # ls -al > > total 8 > > drwxr-xr-x 4 root wheel 512 Aug 12 2015 . > > drwxr-xr-x 28 root wheel 512 Apr 15 09:14 .. > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 jobs > > drwxr-xr-x 2 daemon wheel 512 Aug 12 2015 spool > > root@pythagore:/var/at # > > > > > I don't understand where is the mistake. > > > > This is a more serious problem. I have found it to be impossible to > run a diskless workstation with a persistant /var mounted via NFS > (either by itself or as a directory within the nfs rootfs). It's been > this way for several years. You can add varmfs=yes to your rc.conf to > get a working system, but then you have a non-persistant /var which > really isn't very useful. > > Hmm, but the problems I usually have are with /var/run and pidfiles. > I've never noticed this /var/at problem (maybe just because I gave up > trying to run with an nfs-mounted /var before I noticed them). I successfully run with nfs-mounted /var (actually, part of the nfs-mounted root) on my test machines, with the following boot setting: boot.nfsroot.options="nolockd" What you need is the working advisory locks, but since /var is by its structure, private, there is no need to share locking with the server or other clients. nolockd makes the client kernel to handle adv locks autonomously, without lockd/statd protocol. From owner-freebsd-hackers@freebsd.org Tue Apr 19 16:35:58 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 999C0B14EDA; Tue, 19 Apr 2016 16:35:58 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E87F1CE1; Tue, 19 Apr 2016 16:35:58 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id n3so39565751wmn.0; Tue, 19 Apr 2016 09:35:58 -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; bh=xzajR6WxyLvNbF3AbZYgAQ3tAL4xF7A3YcB3Wc43oqg=; b=UkSZZgVJDpDdoz0vSqqOyVWPUbjbaMw706V+dE1uIWfAtxTX4m9jost6liwTvGuWCX +YJDhtqe2VuEdwQrgrECCjwEVrKzMbPl+FPV0fhvFs4MZpVU6YYDxq3XcTDPGkn1lDCh QMiApTcIy5vu28SKAfaqCVzSktNPVOdQF8zlMXlTZYYv946rsLfPIxaLjXP2eZgqo5f1 LzunQjrS4t1oy9mFSjJwDy8JQJmZ3OrNTy7XkgfvPQ8JJpvCVAPv4yIUMByAMo1okF7B TSxSC6+Q8oxfn+JKJZuhqOCFFA/XEs6mlH/8aRruvGlA0erKwTpBB95romsOnl43keif Yy+g== 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; bh=xzajR6WxyLvNbF3AbZYgAQ3tAL4xF7A3YcB3Wc43oqg=; b=kjqhKylfZ6UCcXZjXRTToJU9M68zIaycsMNc5MkYV6bMlfr6Jvp8MAyyqTRPx+mAqp rINn4kVbiRNLchjBRQyvr6TINW+P8CI2NVIVX905IliES7whDm9mc1vH/a9uz6Sua2TB EBQjSVIsRFRHuxWNHIpnWpWlkBLkjOZitlbbi5njZCFOXw4ZixMJGP/MFFWSiB4VQOTk QTSe61aj8tvZPd8Rpux5NHav5XZR0VCFpxzeRy6zbMdI497JijEa24WGq8VwIEMs/7P3 D/J6SH5AttUCnBgFdr/Ls0LkGRek5pnAq7Cl3YdS0qrRpN5LsO+v66HCRb4kbOMgwCwL TYfg== X-Gm-Message-State: AOPr4FWZYGMdkuJf8KcluGkh/DDyRy2tvPuPDzZMynat7IWJtiKUj61fFfLgs/jpiiCtbdlFnFkS4Mm0AZb2bw== MIME-Version: 1.0 X-Received: by 10.194.184.38 with SMTP id er6mr3924030wjc.93.1461083755747; Tue, 19 Apr 2016 09:35:55 -0700 (PDT) Received: by 10.194.21.162 with HTTP; Tue, 19 Apr 2016 09:35:55 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 22:05:55 +0530 Message-ID: Subject: Re: Toggling between remote KGDB and local DDB within a debugging session From: Aijaz Baig To: cem@freebsd.org Cc: FreeBSD Hackers , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 19 Apr 2016 16:42:57 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:35:58 -0000 On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote: > On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote: >> I would like to know if there is indeed a way to toggle between gdb >> and ddb while debugging a remote kernel. I am already at the gdb (or >> rather kgdb) prompt. From here how do I switch to local ddb on the >> debugged machine?? > > Ctrl-c on the serial console. For me I merely see 'Quit' being spat out when I do a ctrl-c > >> When remote remote KGDB is listening and I force a >> panic using 'sysctl debug.kdb.enter=1', it drops into remote KGDB. >> However, when it is NOT listening on the serial port, the local system >> just freezes > > Are you sure ddb just doesn't run on the serial port? For the very first time, a manual panic does indeed bring up the ddb prompt. However it is only AFTER I've attached kgdb to it, does this start happening, namely not going back ever to ddb (with 'Quit' being displayed instead and with the control still with KGDB) > >> What I want, is to enter ddb on the local machine. Do some debugging >> using it; drop to remote KGDB for things that are best done using >> KGDB, then switch back to local DDB when I'm done. > > Yes. I regularly do this with ctrl-c (gdb->ddb) / "gdb" (ddb->gdb). If it'd help, I'm using VMs. So my serial console is actually the VM console. Now just to be on the safe side I tried putting "comconsole" into '/boot/loader.conf'. However now, with the aforementioned sysctl, it doesn't drop to ddb even for the very first time unlike previous trials where. dropping into DDB was smooth as long as KGDB was not attached to it ever. > > Best, > Conrad Keen to hear from you -- Best Regards, Aijaz Baig From owner-freebsd-hackers@freebsd.org Tue Apr 19 16:47:22 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CBEFB134B2; Tue, 19 Apr 2016 16:47:22 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com [209.85.218.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9F61168E; Tue, 19 Apr 2016 16:47:21 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f65.google.com with SMTP id r186so2002610oie.2; Tue, 19 Apr 2016 09:47:21 -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:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=plKItJ4SwUszM7mWddeQoN/3iytUwLj2y1QSjZGtfRc=; b=YWkbXxGkUInOR125+A/mdjoAaUlKzEV4uemlcdY2/MAKRXUuP45AKRvZTPaABneuGR wRS9DU8Vd3z2wfzMg57+1FAID7o2wrSo34CDQak8KEKJ65JJ9apGf6w1pv1WzMCTU1tc Zb4MoRs5FWF0h0SAKsPgpQ8TyOGksM6MJS/ZPfOb8HZrVRmz6EFAZtkhWnPsSj6PO7mr Ma3Z4HOE8/UJwuSHdgDIQd2sx2c0M9443DNjUAnbzNIE6om2Efz+DXYaGvNb+ihBIFtO kkRgvIYLk8BCYV7dcLR2t8CqP4GppqxK2cRjyhtsktxAajeGDC6dwxfJW0/Y3qJDxjtn svMQ== X-Gm-Message-State: AOPr4FWmcawpBCqm+B9wIbYYYm+TjmsVnYfUDhCPW2GxmhBsk9yh7FVg6DWEPxdPia6vnQ== X-Received: by 10.202.57.133 with SMTP id g127mr1616077oia.120.1461084435530; Tue, 19 Apr 2016 09:47:15 -0700 (PDT) Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com. [209.85.218.47]) by smtp.gmail.com with ESMTPSA id 40sm21288241otg.28.2016.04.19.09.47.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Apr 2016 09:47:15 -0700 (PDT) Received: by mail-oi0-f47.google.com with SMTP id p188so16645699oih.2; Tue, 19 Apr 2016 09:47:14 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.157.6.65 with SMTP id 59mr1840353otn.39.1461084434580; Tue, 19 Apr 2016 09:47:14 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.22.215 with HTTP; Tue, 19 Apr 2016 09:47:14 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 09:47:14 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Toggling between remote KGDB and local DDB within a debugging session From: Conrad Meyer To: Aijaz Baig Cc: FreeBSD Hackers , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:47:22 -0000 On Tue, Apr 19, 2016 at 9:35 AM, Aijaz Baig wrote: > On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote: >> On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote: >>> I would like to know if there is indeed a way to toggle between gdb >>> and ddb while debugging a remote kernel. I am already at the gdb (or >>> rather kgdb) prompt. From here how do I switch to local ddb on the >>> debugged machine?? >> >> Ctrl-c on the serial console. > For me I merely see 'Quit' being spat out when I do a ctrl-c Ctrl-C on the serial console, not in GDB. It looks like this: # sysctl debug.kdb.enter=1 debug.kdb.enter:KDB: enter: sysctl debug.kdb.enter [ thread pid 21907 tid 102340 ] Stopped at kdb_sysctl_enter+0x87: movq $0,kdb_why db> gdb (ctrl-c will return control to ddb) Switching to gdb back-end Received ^C; trying to switch back to ddb. using longjmp, hope it works! KDB: reentering KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffea79d0e6140 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffea79d0e61f0 kdb_reenter() at kdb_reenter+0x33/frame 0xfffffea79d0e6200 gdb_tx_end() at gdb_tx_end+0x28a/frame 0xfffffea79d0e6240 gdb_trap() at gdb_trap+0x1f9/frame 0xfffffea79d0e6390 kdb_trap() at kdb_trap+0x169/frame 0xfffffea79d0e63f0 trap() at trap+0x71d/frame 0xfffffea79d0e6600 calltrap() at calltrap+0x8/frame 0xfffffea79d0e6600 --- trap 0x3, rip = 0xffffffff8058f177, rsp = 0xfffffea79d0e66c0, rbp = 0xfffffea79d0e66f0 --- kdb_sysctl_enter() at kdb_sysctl_enter+0x87/frame 0xfffffea79d0e66f0 sysctl_root() at sysctl_root+0x24a/frame 0xfffffea79d0e6740 userland_sysctl() at userland_sysctl+0x1d2/frame 0xfffffea79d0e67f0 sys___sysctl() at sys___sysctl+0x74/frame 0xfffffea79d0e68a0 amd64_syscall() at amd64_syscall+0x397/frame 0xfffffea79d0e6ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffea79d0e6ab0 --- syscall (202, FreeBSD ELF64, sys___sysctl), rip = 0x80095ed4a, rsp = 0x7fffffffc948, rbp = 0x7fffffffc980 --- gdb_trap bailing, hopefully back to ddb! Switching to ddb back-end [ thread pid 21907 tid 102340 ] Stopped at kdb_sysctl_enter+0x87: movq $0,kdb_why db> c 0 -> 0 Best, Conrad From owner-freebsd-hackers@freebsd.org Tue Apr 19 17:19:17 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CF4DB145D9; Tue, 19 Apr 2016 17:19:17 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E19731F92; Tue, 19 Apr 2016 17:19:16 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id v188so171277871wme.1; Tue, 19 Apr 2016 10:19: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:date:message-id:subject:from:to :cc; bh=E0liS+HEFC7I/YmWoZCnxIKMEjXn7ltj53KdAqJw7lY=; b=LF9ULmGYEJn51kwdzTHeJzb5gIsx4IVRTupv3csxrWbvfoQUYJCK7zzFWwNw2tmYeC Ws1M4aGWwV5Eer+STlNzHsgM0HX6bToPWq0WECnm7X6klSKzkgc8dBvagmyCyOoAlTJ7 Fatm0K9wzTEJIVVXtq/G7tTg+IEPErsy7DPrHCc69pZGvffHhWKQPsY5uwIJBGJmjqvL Fx31YwbtMMcO5fSj4u27fQjukJE1lHxXNKH2kVM2dFdEKbnChZf1hBwSk4KoOs7d0UqY W33NMtXz+iJVW2yd9notCBV1ynPZaIj1aXBftjCDiUsGzdcFbhJCse0AtEENdSHtrrPj bJWA== 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; bh=E0liS+HEFC7I/YmWoZCnxIKMEjXn7ltj53KdAqJw7lY=; b=DiJbhP2ESAgu12y4CdWvLsfCT7rn1KrTBoabUVW73Lrac8QfsyU7EXr+mO842gdonY 2hePYxhW3ZJPhPiLmOIwwtheX8Dt1Gjol7k+0CDJriCyIe1dtA7LGDRHWJNTeLuNd9bE YzAPhR+JMaA/Xy4RVmaauqfP9x1sJvBxODwEuhXYQn7wQjeLAaGiVhNWbo5FywlC6W1w CLLj0rlGkcNMF03OyshrbCovkirhgKnu3QZqsIglsJHnbtPoqod8VY8CTYsHQ0al8LQp oCvObPzXFM0ZaBOB1ks2NB19xwlk5UrPx76uK7Lp1Xbo1FtZIdsatnaHgEOVFki2z3mK W94w== X-Gm-Message-State: AOPr4FXjYR3Fr+OY2y7Rsg2u8M+6WChmrdW9/zo+4g6sjVrTzFdG8MygJC1cNfWVwbcojVHhEYfzUniakqg2cw== MIME-Version: 1.0 X-Received: by 10.194.77.42 with SMTP id p10mr4218921wjw.111.1461086355463; Tue, 19 Apr 2016 10:19:15 -0700 (PDT) Received: by 10.194.21.162 with HTTP; Tue, 19 Apr 2016 10:19:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 22:49:15 +0530 Message-ID: Subject: Re: Toggling between remote KGDB and local DDB within a debugging session From: Aijaz Baig To: cem@freebsd.org Cc: FreeBSD Hackers , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 17:19:17 -0000 On Tue, Apr 19, 2016 at 10:17 PM, Conrad Meyer wrote: > On Tue, Apr 19, 2016 at 9:35 AM, Aijaz Baig wrote: >> On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote: >>> On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote: >>>> I would like to know if there is indeed a way to toggle between gdb >>>> and ddb while debugging a remote kernel. I am already at the gdb (or >>>> rather kgdb) prompt. From here how do I switch to local ddb on the >>>> debugged machine?? >>> >>> Ctrl-c on the serial console. >> For me I merely see 'Quit' being spat out when I do a ctrl-c > > Ctrl-C on the serial console, not in GDB. It looks like this: Yes I tried ctrl-c on the serial console (in-fact it even says so at the ddb promp) but it doesn't work I find the control still with the kgdb Has it got anything to do with the fact that I am on a VM? Has anyone been successful in doing this with VMs? > > # sysctl debug.kdb.enter=1 > debug.kdb.enter:KDB: enter: sysctl debug.kdb.enter > [ thread pid 21907 tid 102340 ] > Stopped at kdb_sysctl_enter+0x87: movq $0,kdb_why > db> gdb > (ctrl-c will return control to ddb) > Switching to gdb back-end > Received ^C; trying to switch back to ddb. > using longjmp, hope it works! > KDB: reentering > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffea79d0e6140 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffea79d0e61f0 > kdb_reenter() at kdb_reenter+0x33/frame 0xfffffea79d0e6200 > gdb_tx_end() at gdb_tx_end+0x28a/frame 0xfffffea79d0e6240 > gdb_trap() at gdb_trap+0x1f9/frame 0xfffffea79d0e6390 > kdb_trap() at kdb_trap+0x169/frame 0xfffffea79d0e63f0 > trap() at trap+0x71d/frame 0xfffffea79d0e6600 > calltrap() at calltrap+0x8/frame 0xfffffea79d0e6600 > --- trap 0x3, rip = 0xffffffff8058f177, rsp = 0xfffffea79d0e66c0, rbp > = 0xfffffea79d0e66f0 --- > kdb_sysctl_enter() at kdb_sysctl_enter+0x87/frame 0xfffffea79d0e66f0 > sysctl_root() at sysctl_root+0x24a/frame 0xfffffea79d0e6740 > userland_sysctl() at userland_sysctl+0x1d2/frame 0xfffffea79d0e67f0 > sys___sysctl() at sys___sysctl+0x74/frame 0xfffffea79d0e68a0 > amd64_syscall() at amd64_syscall+0x397/frame 0xfffffea79d0e6ab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffea79d0e6ab0 > --- syscall (202, FreeBSD ELF64, sys___sysctl), rip = 0x80095ed4a, rsp > = 0x7fffffffc948, rbp = 0x7fffffffc980 --- > gdb_trap bailing, hopefully back to ddb! > Switching to ddb back-end > [ thread pid 21907 tid 102340 ] > Stopped at kdb_sysctl_enter+0x87: movq $0,kdb_why > db> c > 0 -> 0 > > Best, > Conrad -- Best Regards, Aijaz Baig From owner-freebsd-hackers@freebsd.org Tue Apr 19 17:53:23 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55153B1526D; Tue, 19 Apr 2016 17:53:23 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-ob0-f194.google.com (mail-ob0-f194.google.com [209.85.214.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EEA016C1; Tue, 19 Apr 2016 17:53:22 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-ob0-f194.google.com with SMTP id tz8so2445479obc.1; Tue, 19 Apr 2016 10:53:22 -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:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=lvw/CNlij/shp17eZKlavW7U8LHOhZ+aqpfX6rVg4fs=; b=ZmH1w1ije49MJRJ4xd37UsUIGu6jq8VCf08qBAP7nCBuWolhhm5Wk0bRadVVPyxwvb nRPBakwm4VZt+W1Mpz70VXRliFIm88KCiXDEniJ8Kysg263gBRqPl/LkjAtlqBrodXmI ABFmboGa1j6H73AKtGd9pFxxwJnn6xU7893FZlNcRr0L3itz+KvYj0uKYqwsX5wGxx7p BGd36rVa0jFayFZDMcBlaMVA4h01EtC3YS0WwjWXeKeIb24RFtfiaFirA6bjDtUeF4ar fQSEnzPcEBXIhy9EpNfy3ZSNZOSOQS2wfkb5uZCsxMxcMcFJSnCPskFyH4npdVf7nueY hWHA== X-Gm-Message-State: AOPr4FW2MmkJ35rb2Sfh5CSYOsqiId4Whvh/kG9xwtFqb2UAB6T03mONFGlwF2F7p9BpBA== X-Received: by 10.60.230.104 with SMTP id sx8mr1596880oec.61.1461080310154; Tue, 19 Apr 2016 08:38:30 -0700 (PDT) Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com. [209.85.218.45]) by smtp.gmail.com with ESMTPSA id dn8sm14101868oeb.15.2016.04.19.08.38.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Apr 2016 08:38:29 -0700 (PDT) Received: by mail-oi0-f45.google.com with SMTP id r78so12840346oie.0; Tue, 19 Apr 2016 08:38:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.203.14 with SMTP id b14mr1525482oig.56.1461080309400; Tue, 19 Apr 2016 08:38:29 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.22.215 with HTTP; Tue, 19 Apr 2016 08:38:29 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 08:38:29 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Toggling between remote KGDB and local DDB within a debugging session From: Conrad Meyer To: Aijaz Baig Cc: FreeBSD Hackers , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 17:53:23 -0000 On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote: > I would like to know if there is indeed a way to toggle between gdb > and ddb while debugging a remote kernel. I am already at the gdb (or > rather kgdb) prompt. From here how do I switch to local ddb on the > debugged machine?? Ctrl-c on the serial console. > When remote remote KGDB is listening and I force a > panic using 'sysctl debug.kdb.enter=1', it drops into remote KGDB. > However, when it is NOT listening on the serial port, the local system > just freezes Are you sure ddb just doesn't run on the serial port? > What I want, is to enter ddb on the local machine. Do some debugging > using it; drop to remote KGDB for things that are best done using > KGDB, then switch back to local DDB when I'm done. Yes. I regularly do this with ctrl-c (gdb->ddb) / "gdb" (ddb->gdb). Best, Conrad From owner-freebsd-hackers@freebsd.org Tue Apr 19 18:15:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB1F4B15B27 for ; Tue, 19 Apr 2016 18:15:43 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 539B113AD for ; Tue, 19 Apr 2016 18:15:43 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id e201so4916106wme.2 for ; Tue, 19 Apr 2016 11:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l/56HYk3U9Y4LV+2FmZVDHqpDTYCIi9PrEWu1pOBxZw=; b=LfrNsJSi3bPsrC7H9eRBU2eKoTlpu+KYgGXzS/RynR3kJSh2WSinQpzgP3isEkcT7z 1a5d/jRyV5A7zgJMmhHZCpmpeG7N/4taSisynJdA/zE0y/kiguYWSZ7Gr00L/zcwf5lU vWALBYNF+Sdb7LWstGI0PAhknhJ8TRpah9TOqSCHwgs4SM9rr0DYD+HjYlG9k9q4kehQ J59v5jvME2AYNCxOypAWia9AHRTxhBv9j6fVrEi4qMjSeaJbS9tgN69wFm3etD9aJsVb 2XFH0+Hn13+mAOtaxZtKOHXe/4ajL71Q8mwhSylZPPAfAKvERb9kyc1Vxj8MsGUIO6Og DJtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=l/56HYk3U9Y4LV+2FmZVDHqpDTYCIi9PrEWu1pOBxZw=; b=gWw4JeaFxIXUTNdrsx3HnV7CNEQ1m6PKoH+CGFDo8ezjxyvVBTKCJBDoNuM6oBERX7 B1S9vmJP1PH87/L69lyinhRSyB7OEpH9+zE/WfXP0K4WDtRcCk8hYg4p1UMzOU02TMwQ ZY6dNeCqc9HiCSq3y5w+yk5V75O318LT1DXO4HiLX8jkBDMAUe+Wj/2INpAqK+fg8F95 io/vH8WFSAUJ6B5qtmKcFDVjqSwjNIx5zy6kEXf5od6BTOXs+OJs5+t2k/aSQBVozjtx +Xpev3QAF+wR4hRKXo4c40q+SD5+qJ9+lYySB0fVbViq0W3w9ZXBs0s39kDAiAjdxEQ0 UVhw== X-Gm-Message-State: AOPr4FW5rZDjoyiGjalG8B2mgdz5M+93GS37CzJco2Qa33rNG8as25P5QQGmNgTqgXkuZA== X-Received: by 10.194.19.197 with SMTP id h5mr4448245wje.139.1461089741897; Tue, 19 Apr 2016 11:15:41 -0700 (PDT) Received: from [192.168.1.15] (abpy245.neoplus.adsl.tpnet.pl. [83.8.66.245]) by smtp.gmail.com with ESMTPSA id u3sm5512566wmg.15.2016.04.19.11.15.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2016 11:15:41 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Diskless workstation and some minor issues From: =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Mailer: iPhone Mail (13E238) In-Reply-To: Date: Tue, 19 Apr 2016 20:15:38 +0200 Cc: =?utf-8?Q?BERTRAND_Jo=C3=ABl?= , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <57163991.4000100@systella.fr> To: Bob Bishop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 18:15:43 -0000 Dnia 19.04.2016 o godz. 16:23 Bob Bishop napisa=C5=82(a): > Hi, >=20 >> On 19 Apr 2016, at 14:58, BERTRAND Jo=C3=ABl w= rote: >>=20 >> Hello, >>=20 >> I have installed a diskless workstation (10.2-RELEASE-p14) that mounts= its rootfs from a NetBSD nfs server. My fstab is : >>=20 >> root@pythagore:~ # cat /etc/fstab >> # Device Mountpoint FStype Options Dump Pass# >> 192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw 0 = 0 >> ... >> 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw 0 = 0 >> root@pythagore:~ # >>=20 >> First question. I have installed this diskless workstation with an USB= stick. Now, FreeBSD kernel mounts rootfs over NFS. But in a first time, it t= ries to mount usbus0 (!) : >>=20 >> Apr 9 10:48:00 pythagore kernel: Root mount waiting for: usbus2 usbus1 u= sbus0 > [snip] >> Apr 9 10:48:02 pythagore kernel: ugen0.4: at usbus0 (disconnec= ted) >> Apr 9 10:48:02 pythagore kernel: uhub_reattach_port: could not allocate n= ew device >> Apr 9 10:48:02 pythagore kernel: Trying to mount root from nfs:192.168.1= 0.128:/srv/pythagore [nfsv3,tcp,soft,intr,rw]... >> Apr 9 10:48:02 pythagore kernel: NFS ROOT: 192.168.10.128:/srv/pythagore= >>=20 >> I don't understand why kernel tries to mount an USB rootfs... And I ha= ven't found how fix this trouble. >=20 > It doesn=E2=80=99t. It waits for USB just in case the root is on USB, I as= sume this isn=E2=80=99t optimised to keep things simple. It is, but only in 11-CURRENT. From owner-freebsd-hackers@freebsd.org Wed Apr 20 18:38:28 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DE2AB16185; Wed, 20 Apr 2016 18:38:28 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D2531EA3; Wed, 20 Apr 2016 18:38:28 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from [172.17.133.77] (dip-cali.panasas.com [64.80.217.3]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5Y003Z63RXHW10@mr11p00im-asmtp002.me.com>; Wed, 20 Apr 2016 18:38:22 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-20_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604200295 User-Agent: Microsoft-MacOutlook/f.15.1.160411 Date: Wed, 20 Apr 2016 11:38:20 -0700 Subject: g_event and sysctllock From: Ravi Pokala To: "freebsd-hackers@freebsd.org" , "freebsd-geom@freebsd.org" , "Rai, Sushanth" Message-id: <1E22BEFB-5C0E-4DE2-91E1-FD5F8AEFD04A@mac.com> Thread-topic: g_event and sysctllock MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Wed, 20 Apr 2016 19:06:51 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 18:38:28 -0000 Hi folks, My colleague Sushanth (CCed) tried to send this to hackers@ yesterday, but it didn't go through for some reason. Resending on his behalf, adding geom@, and noting that while we saw this on 7-STABLE, it looks like it could still be an issue in -HEAD. -------------------------------- Hello, We have a home-grown geom driver that creates sysctl in the device creation path. Device creation is handled by the geom event thread. The call to SYSCTL_ADD_NODE() takes the sysctllock in exclusive mode. If the event thread is racing with another thread that calls sysctl_disks(), then you end up with a deadlock since sysctl_disks() tickles the event thread and goes to sleep while holding the sysctllock. It is expected to woken up by the event thread when the event of listing all the disks is processed. But the geom event is blocked waiting for the sysctllock. I did see g_disk_create() adds a sysctl variable in a similar fashion, hence the email. I'm thinking of fixing the sysctl_disks() to drop the sysctllock before going to sleep and reacquiring it after being woken up. Let me know your thoughts. Thanks, Sushanth -------------------------------- -Ravi (rpokala@) From owner-freebsd-hackers@freebsd.org Wed Apr 20 19:24:16 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23542B1520E; Wed, 20 Apr 2016 19:24:16 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8CE31DD3; Wed, 20 Apr 2016 19:24:15 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x22b.google.com with SMTP id r5so18696252pag.1; Wed, 20 Apr 2016 12:24:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=T7kZ1cJeJLAMT/osQKq2EoCoPL61egMEQfP1cqC4URc=; b=FN6bDvcEVE0AylzTo1GPUtHWyZ52rueLVT9SXs433KMPiTRBcDdVxqTw3n4/DHz0HZ 4J/M3pDrZpz/QN8RU4AoR2Wx9XhF2YaoGraa1tll2G7hQi2lu8K8U4MJJBGhSwNYPied KaoS79jNgk1DBHUzcG/omjDh4EoXekgNR1FOtFAbcczc4IdbUrHwPlHLdHXh3oLYFttv Yflr8PjQSQtlAXbFc3oo4x2osVPzIMcENjzgPvD8MZUBgo0TSZ6cdXhzDZ6VY7Xp2GR9 F1oDxDo84YvaA5K6BhKhZqISoa3qaUdy0txLECuEb5v6Jgh3B+85EyAkVJlI8m43AhVe xtRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=T7kZ1cJeJLAMT/osQKq2EoCoPL61egMEQfP1cqC4URc=; b=CtM0tNTCRKkb2EkMXbCMHSzm60w/3i3iLVLxB505ug8IZGbCBoJrPhhoxdgMuafYHC XBlGKDQVb0Fc1MGfAN1x2h9DYKVsoj2SmIussCjhdg1OpqxvsPOzZ5jqKPu8ppcC8RJG 2n2S2QCOcN8u0G4nL+p1/3rh5SElZSDVV5CdDExIy5+h54J3lkayICDSG5goGjQi/mE8 hBhlzudvyJny0KmanLT0OiNY41620eU89TLsDbSBPtjLljwLiP1wlUqKFKvmCtbzU8LV 038KF+gLfxGrZcoKjC6KRQgwe1F25TNSnnFQBtsb1xQQ5ERy5oWp7XTU0EwwOPb6yFf7 y84A== X-Gm-Message-State: AOPr4FV8HDPCm9C0PM8LKeqGR0ymGBxNgtveXYjNnod/DQ6fJaTDkJbiAPTXEJIr/JI0UQ== X-Received: by 10.66.251.10 with SMTP id zg10mr14628476pac.1.1461180255525; Wed, 20 Apr 2016 12:24:15 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-67-182-131-225.hsd1.wa.comcast.net. [67.182.131.225]) by smtp.gmail.com with ESMTPSA id h85sm100083737pfj.52.2016.04.20.12.24.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Apr 2016 12:24:14 -0700 (PDT) Sender: Mark Johnston Date: Wed, 20 Apr 2016 12:27:16 -0700 From: Mark Johnston To: Ravi Pokala Cc: "freebsd-hackers@freebsd.org" , "freebsd-geom@freebsd.org" , "Rai, Sushanth" Subject: Re: g_event and sysctllock Message-ID: <20160420192716.GA16105@wkstn-mjohnston.west.isilon.com> References: <1E22BEFB-5C0E-4DE2-91E1-FD5F8AEFD04A@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1E22BEFB-5C0E-4DE2-91E1-FD5F8AEFD04A@mac.com> User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 19:24:16 -0000 On Wed, Apr 20, 2016 at 11:38:20AM -0700, Ravi Pokala wrote: > Hi folks, > > My colleague Sushanth (CCed) tried to send this to hackers@ yesterday, but it didn't go through for some reason. Resending on his behalf, adding geom@, and noting that while we saw this on 7-STABLE, it looks like it could still be an issue in -HEAD. > > -------------------------------- > > Hello, > > We have a home-grown geom driver that creates sysctl in the device creation path. Device creation is handled by the geom event thread. The call to SYSCTL_ADD_NODE() takes the sysctllock in exclusive mode. If the event thread is racing with another thread that calls sysctl_disks(), then you end up with a deadlock since sysctl_disks() tickles the event thread and goes to sleep while holding the sysctllock. It is expected to woken up by the event thread when the event of listing all the disks is processed. But the geom event is blocked waiting for the sysctllock. > > I did see g_disk_create() adds a sysctl variable in a similar fashion, hence the email. I'm thinking of fixing the sysctl_disks() to drop the sysctllock before going to sleep and reacquiring it after being woken up. Let me know your thoughts. > This is not an issue in head. r216060 modified the sysctl code so that the sysctl lock is dropped before handlers are called. So sysctl_disks() is no longer executed with the sysctl lock held, and this addresses the problem you described. This change was MFCed to stable/7 in r220012 though. Do you have that revision? From owner-freebsd-hackers@freebsd.org Fri Apr 22 08:37:18 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B2FFB17689; Fri, 22 Apr 2016 08:37:18 +0000 (UTC) (envelope-from kristoffer.eriksson@preciofishbone.se) Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0084.outbound.protection.outlook.com [157.56.112.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 999A810DB; Fri, 22 Apr 2016 08:37:15 +0000 (UTC) (envelope-from kristoffer.eriksson@preciofishbone.se) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=precio.onmicrosoft.com; s=selector1-preciofishbone-se; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=X2uF/LV0MOEsUFMiTzdGUMbtnRH+zCZ9eW7CTTUDZ08=; b=UHE9gCVMXSjg5eAAU4hupq7ck5/ly/O2b7H7GE1NV710OYBbQbqYM25/AN3oovfWmXrq4hxwWmiVXtawyI8/K8RfRJM1p6Bgl8O7nEVdsDrjclnTlWelVYI+kt6xo0w6hud4+BwGH+dsO+Cbrg/oAbXQNTOotmxdZ8OW7FA97uI= Received: from AM4PR0401MB1826.eurprd04.prod.outlook.com (10.165.245.13) by AM4PR0401MB1825.eurprd04.prod.outlook.com (10.165.245.12) with Microsoft SMTP Server (TLS) id 15.1.466.19; Fri, 22 Apr 2016 08:37:07 +0000 Received: from AM4PR0401MB1826.eurprd04.prod.outlook.com ([10.165.245.13]) by AM4PR0401MB1826.eurprd04.prod.outlook.com ([10.165.245.13]) with mapi id 15.01.0466.023; Fri, 22 Apr 2016 08:37:07 +0000 From: Kristoffer Eriksson To: "freebsd-hackers@freebsd.org" CC: "freebsd-emulation@freebsd.org" Subject: What to do after submitting a patch for SVR4/STREAMS? Thread-Topic: What to do after submitting a patch for SVR4/STREAMS? Thread-Index: AdGccb2m547ZZ+PEQ+m7lIyn31g0sw== Date: Fri, 22 Apr 2016 08:37:07 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=preciofishbone.se; x-originating-ip: [83.253.72.64] x-ms-office365-filtering-correlation-id: d77a61c8-b5b5-4a72-89ea-08d36a8949dd x-microsoft-exchange-diagnostics: 1; AM4PR0401MB1825; 5:GjbW7jQ4EJrDFrkUVFkZBoBPDZMTjkgPuw4pZmdD0+pSHCZASjrBq06FyRo/n4r/7J3buqIKgnnpMfo0UC5ll1ZLY/pb4+yvAMeOuStOGSo4S6EmawIQ3jo+dQFvVAiYbENqrfQxSOtOBXuHPB5vXdT0AucJ7ebuhT7v/jr7iuqXN6+bk76ozjGEwNvMibvF; 24:pCNxvsQHdSObRdRNL5BJFO1nfdCC4m1M45xUVnWqCluxuAvVnulj8W2fmmo/cJsDZkZgKhM57Mx+wrkGdtcqtRnUHK5a5fIo3zBqJ/iocCs=; 7:jW26mDQ9HsjYBNZtqAMe5yw+QC/IFCupgAz9Vt9uh/4HUydgd2BbrYzVbHqu+xO9yrZU5pKb00wPjrpCGb0jIbYV9h512rh/EHgSnHDHTIMfLXi6DQAssJUGvC9saI3H1jWW6MXozLSK0BYHmZkMoSEWz9Ok9JlnlmtkZXIepUCuLyNCKTE+n593ICt8NtnEyB4BHI+8EMX3I6WrQoUZS4Wny+dnZgSNuUNQe0Fdc80= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM4PR0401MB1825; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(6040130)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041072)(6043046); SRVR:AM4PR0401MB1825; BCL:0; PCL:0; RULEID:; SRVR:AM4PR0401MB1825; x-forefront-prvs: 0920602B08 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(2900100001)(33656002)(2501003)(77096005)(5003600100002)(76576001)(5002640100001)(189998001)(66066001)(229853001)(86362001)(3660700001)(110136002)(15975445007)(3280700002)(16236675004)(19580395003)(2351001)(2906002)(19625215002)(19300405004)(586003)(450100001)(9686002)(87936001)(11100500001)(74482002)(81166005)(81156013)(5630700001)(10400500002)(5640700001)(5008740100001)(74316001)(5004730100002)(92566002)(4326007)(3846002)(102836003)(790700001)(1220700001)(6116002)(50986999)(54356999)(122556002)(1096002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4PR0401MB1825; H:AM4PR0401MB1826.eurprd04.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: preciofishbone.se X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2016 08:37:07.0753 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 7f34bc08-7585-4811-b5e3-124306325c55 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR0401MB1825 X-Mailman-Approved-At: Fri, 22 Apr 2016 11:20:48 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 08:37:18 -0000 Hi, I submitted patches to problem report 208464 to fix a problem that prevente= d the kernel modules svr4.ko & streams.ko from loading, which has been a pr= oblem since probably many years back, and up to the current 10.3-RELEASE. What should I do next to get this incorporated into the current source, so = others can benefit from it? /Kristoffer From owner-freebsd-hackers@freebsd.org Fri Apr 22 11:31:56 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0C26B18055; Fri, 22 Apr 2016 11:31:56 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 782041029; Fri, 22 Apr 2016 11:31:56 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4]) by mail.rdsor.ro (Postfix) with ESMTP id 756551F9A7; Fri, 22 Apr 2016 14:31:54 +0300 (EEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 22 Apr 2016 14:32:04 +0300 From: dan_partelly To: Kristoffer Eriksson Cc: , Subject: Re: What to do after submitting a patch for =?UTF-8?Q?SVR=34/STREAMS=3F?= In-Reply-To: References: Message-ID: X-Sender: dan_partelly@rdsor.ro User-Agent: RoundCube Webmail/0.4-beta X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 11:31:56 -0000 Try to out it up on phabricator for review, post on current too, ask who mainatains the compat subsystems, mail him, dont give up. Some things move slow. On Fri, 22 Apr 2016 08:37:07 +0000, Kristoffer Eriksson wrote: > Hi, > > I submitted patches to problem report 208464 to fix a problem that > prevented the kernel modules svr4.ko & streams.ko from loading, which has > been a problem since probably many years back, and up to the current > 10.3-RELEASE. > > What should I do next to get this incorporated into the current source, so > others can benefit from it? > > /Kristoffer > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Sat Apr 23 17:12:22 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 139C1B1A710 for ; Sat, 23 Apr 2016 17:12:22 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id EBEF91173 for ; Sat, 23 Apr 2016 17:12:21 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EB440B1A70F; Sat, 23 Apr 2016 17:12:21 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAC94B1A70D; Sat, 23 Apr 2016 17:12:21 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86D171171; Sat, 23 Apr 2016 17:12:21 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id r12so11701605wme.0; Sat, 23 Apr 2016 10:12:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=HtyTqRLGvs1M43qZFHR83I6+2umGPiaxViPU4gQB2E8=; b=i25fXmEehHKt780gLlEMsJLSwj78z2n8G/GQIeXufZwCVai8bXgaypzSlAaH43eWZK upo3IXyZ+3WvszVgs4LnLxFwu6kEpV4OppsDoLfsdYLG/49xJDpPWVLHVBPHD8PvOe5L 8/te8mlogmma5GzoC7a16jlhS8oyNgWfisjsKZIzWWbGxXbPtuEdrqvYggM9meBLCqul 4hQ7g9aiC3bqm/bVQ2ykub7NRpBYICH5q/Z0vuSoZ3xrsiybh+KnYh9I4tDbB4d6br0N Ig9CP9L3jSjeoUR2OVRO+kIoTJGcHQTfVDKjVklw6Ays299bwN1ZNFkobEdqDeOHRQxx +vJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=HtyTqRLGvs1M43qZFHR83I6+2umGPiaxViPU4gQB2E8=; b=aNUiOd0SuXi0QxlCSlqEAtGc6unNPHS7ME3g2hotAC9hInFER3qjIN54H6K3gT4Amv JAUQ2gVviyx93tICELMLcf/Jzp8d06G6x/DJKglO06uqT1nq5VO678r2HamUbvjNZdgB Z6vpFLXMgJmHtCY8GLAwctwXYExGBH3tQ4OgsbOoq0fH3gKrYIdYB8IuJRjSNcG71M57 wygaq926PlWT3dRDOj5+HKVcPt6//qxSd8nY7efhwEUqLCKE90sX7I5xd4gjJ++Q49E2 pRHk/ZYowoyNxj0l4xFaaSZF717tvaeEfpwQrHY13yMUtpJlfVEwyGHE+zm0+Q95uv3r 0WrA== X-Gm-Message-State: AOPr4FXZGCzPXHcPrAKdK0abW7Ogf5fV13tdM1p6Wzeou6mvf5O40MbqiOFUWDRcdRyxdA== X-Received: by 10.28.47.206 with SMTP id v197mr3449528wmv.87.1461431539114; Sat, 23 Apr 2016 10:12:19 -0700 (PDT) Received: from localhost ([188.252.244.162]) by smtp.gmail.com with ESMTPSA id o4sm3094263wjx.45.2016.04.23.10.12.18 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 23 Apr 2016 10:12:18 -0700 (PDT) Date: Sat, 23 Apr 2016 19:12:13 +0200 From: To: hackers@freebsd.org, ports@freebsd.org Subject: py-* ports falsely appearing as deps Message-ID: <20160423191213.0000483e@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 17:12:22 -0000 Like plaque, in many installed ports after issuing: # make missing -- devel/py-pytest-capturelog devel/py-pytest-timeout devel/py-pytest-xdist devel/py-virtualenv devel/py-scripttest devel/py-pretend devel/py-freezegun devel/py-dateutil -- I can confirm that for; x11-drivers/xf86-video-ati, x11-servers/xorg-server, x11-toolkits/gtk20, ... Those will also list as deps for ports, even they aren't port's deps and aren't built. D.