Re: SCSI and dmesg

On Mon, Nov 26, 2018 at 3:57 PM Warner Losh <imp_at_bsdimp.com> wrote:

> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev <sobomax_at_sippysoft.com>
> 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.


>
>
> > -Max
> >
> > On Mon, Nov 26, 2018 at 2:08 PM Yuri Pankov <yuripv_at_yuripv.net> 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_at_$(hostname)" -d
> > > >> "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker)
> $(kenv
> > > >> smbios.system.product)" -d "do=addd" --data-urlencode 'dmesg_at_
> > > >> /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_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe_at_freebsd.org
> "
> >
> _______________________________________________
> freebsd-stable_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe_at_freebsd.org"
>