From owner-freebsd-current@freebsd.org Thu Nov 29 18:01:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09FCD11470A3; Thu, 29 Nov 2018 18:01:22 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2ED6E79E09; Thu, 29 Nov 2018 18:01:21 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f45.google.com with SMTP id p86so2139487lfg.5; Thu, 29 Nov 2018 10:01:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SMEJKLFSITlsGdCt1owZquahzxQG9fpc1QTVeuUOHAA=; b=LIE1u1FFPCkhHEm60T2Me6m9dX6JfeuPcUG26JVo0AfQCSLGo7Rp3AIoLHG304SzkT vo6gYNh4+PHu3L5TYEmHYAK+/p9oAsXq2uwHgXxRB3fgHh7GjDnPA4ExJNsy/4T1YhVb LbLRJzcU34lml7PDTv4HAEMdbCqrTZLPY9jrAUn5Cc/+f/aESY8j5hCUH/xy6suQJ9yr ucXWBqxCkHlLV0W0DDYnQ0ptb3o462aE2xWhgg5BFeMlZvJd44cXZvFRlvauaFnXHO70 yn4te4F4lEzZmLunEox3H2yekzUsp4vz6aV11+Gfufgos7iwfJMlGDUehewVttVD4Rk1 21Qg== X-Gm-Message-State: AA+aEWZ9nbohirpqO9fxKZGWHHifZcjvy1CMXXXmYLS3aquihCRakyd5 SemZNcoxpCBOhnUiSuMV/WUXWY+VRqsD5vO7Yy8= X-Google-Smtp-Source: AFSGD/X0IdP1G7phtldk2cqXjcPxEY51kFhnZ+B8HVieOXLRLqWwLYAjy8FeEEE9OVgGEcsmq1yySGMp9bQ4sL2TrgI= X-Received: by 2002:a19:c396:: with SMTP id t144mr1647187lff.110.1543514473430; Thu, 29 Nov 2018 10:01:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Thu, 29 Nov 2018 11:01:01 -0700 Message-ID: Subject: Re: SCSI and dmesg To: Warner Losh Cc: Maxim Sobolev , yuripv@yuripv.net, FreeBSD CURRENT , FreeBSD X-Rspamd-Queue-Id: 2ED6E79E09 X-Spamd-Result: default: False [-3.92 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.94)[-0.938,0]; RCVD_IN_DNSWL_NONE(0.00)[45.167.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.98)[ipnet: 209.85.128.0/17(-3.47), asn: 15169(-1.33), country: US(-0.09)]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2018 18:01:22 -0000 On Thu, Nov 29, 2018 at 10:49 AM Warner Losh wrote: > > > On Thu, Nov 29, 2018 at 8:09 AM Alan Somers wrote: > >> On Mon, Nov 26, 2018 at 3:57 PM Warner Losh wrote: >> >>> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev >>> wrote: >>> >>> > Somebody needs to make collection/submission automatic and make a port >>> out >>> > of it, so that it's as easy as pkg install dmesg_survey && >>> > dmesg_survey_enabled="YES" in the /etc/rc.conf. JIMHO. I'd gladly make >>> it a >>> > default on all dev boxes within our organization. Might also make a >>> nice >>> > SoC project idea. >>> > >>> >>> It's barely a weekend hack, since with the curl 1 liner 95% of what you >>> want is there. >>> >>> This service isn't suitable, though, to have it in rc.conf, I don't >>> think, >>> unless it's updated only when there's a material change... >>> >>> And I'd rather we get more nuanced data than dmesg can provide if we were >>> to do the data collection. The admonition to submit to this site was one >>> of >>> expedience... >>> >>> Warner >>> >> >> Sounds like somebody needs to adopt sysutils/bsdstats. It's a great >> start, but it needs some TLC. >> > > Except there's no available data from it. And it's not a great start, but > a terrible one. It gathers the wrong things. > > Warner > What do you mean "no available data"? Are you saying that you'd prefer direct access to the server rather than access through the web UI? I'm sure Scrappy would allow that. He's implied that he'd like some help with the server. What I like about bsdstats is that it's much more structured than your dmesg service. Instead of a big long string, it gathers structured info with sysctl, pciconf, and pkg. Plus, it already has a port, it's integrated into periodic(8), and it has a website. If it omits some information that you would like to see, then you should enhance it; not replace it. -Alan > > > > >> >>> >>> > -Max >>> > >>> > On Mon, Nov 26, 2018 at 2:08 PM Yuri Pankov wrote: >>> > >>> > > Yuri Pankov wrote: >>> > > > Warner Losh wrote: >>> > > >> Greetings >>> > > >> >>> > > >> a few weeks ago I pointed people to the nycbug dmesg service. I >>> said I >>> > > was >>> > > >> looking at data to drive SCSI retirement. I've gatherd some >>> > preliminary >>> > > >> data, which I've uploaded to >>> > > >> https://github.com/bsdimp/device-data/blob/master/cam.md along >>> with >>> > > some >>> > > >> preliminary notions of disposition for the hardware. I'm still >>> working >>> > > out >>> > > >> the kinks in the dmesg parsing, but this is interesting data. >>> > > >> >>> > > >> If you've not recently submitted, please consider doing so. We'll >>> be >>> > > >> finalizing the scsi SIMs that I'm going to propose retiring in 13 >>> here >>> > > in a >>> > > >> few weeks, and I'm going to base much of what list I come up with >>> > based >>> > > on >>> > > >> what is submitted. The glitches with FreeBSD dmesgs have been >>> cleared >>> > > up as >>> > > >> well. >>> > > >> >>> > > >> http://dmesgd.nycbug.org/index.cgi >>> > > >> >>> > > >> or >>> > > >> >>> > > >> curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d >>> > > >> "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) >>> $(kenv >>> > > >> smbios.system.product)" -d "do=addd" --data-urlencode 'dmesg@ >>> > > >> /var/run/dmesg.boot' http://dmesgd.nycbug.org/index.cgi >>> > > > >>> > > > Got another system to submit, but continuously getting "500 >>> Internal >>> > > > Server Error" using the curl one-liner. dmesg.boot attached in >>> case >>> > > > it's the source of the problem. >>> > > >>> > > It works now, sorry for the noise. >>> > > >>> > > >>> > _______________________________________________ >>> > freebsd-stable@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> > To unsubscribe, send any mail to " >>> freebsd-stable-unsubscribe@freebsd.org" >>> > >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org >>> " >>> >>