dmesg submission service -- please submit today
Thank you for asking; I used the one-liner in hopes that it helps. I presume the same areas can be used from a release/stable/current boot media to gather it from another machine not running FreeBSD presently but will be a likely future goal so will try to get it submitted too. I would appreciate seeing this as an option or request on installs and think it could make a good reminder in the output when binary updating or source rebuilding or in the UPDATING file (I'm more likely to check there than in the handbook). Adding it to normal dmesg output or a login message would seem too bloated and likely to be removed or ignored. If something is planned for removal, documenting it and mentioning it in output when it is loaded both could help spread awareness. If needing feedback from those users, it could make it clear it is considered for removal so that people who need to speak up about being a user have a chance to be heard then too. freebsd.org hosting it would lead to more trust and easy control of a command sequence to generate it with options, review contents, then submit it would get more feedback. Anyways, I'm not a regular to this list and I only found out as I was browsing through release+stable+current mailings, PRs, changes, and patches under review for my issue of processes getting stuck in the pfault state (as listed by top) when I get down to about 140M free of 32G until more and more processes lock up. Power button set for shutdown usually eventually gives one after it begins killing things due to timeouts being reached. Though I have had some luck with patches improving how long until I can expect a needed action be taken, I've decided 11.2 is not stable enough for use so will likely go to 12-stable with hopes of changes I have not yet tested. I got rid of my last 10M adapter last year when I ran across it as any reason I may reach for it would be a painful experience to not just replace it. Thank you and good luck on a smooth cleanup, Edward Sanford Sutton, III ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sun, Oct 07, 2018 at 08:21:46AM -0600, Warner Losh wrote: > > Oh right. There's a known bug I should have mentioned: If your uname doesn't > have a '#' in it, the script will reject it. You can add #0+ after the ALPHA8 > and before the r339174 and it will work. I've reported this to the dmesg > guys. Thanks, I have submitted them. > > Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On 10/8/18 12:35 AM, Thomas Mueller wrote: I just submitted /var/run/dmesg.boot from my current NetBSD and from FreeBSD 11.1-STABLE. I was surprised to see some other BSD OSes listed, including 5 dmesg reports from Bitrig and 3 from RetroBSD. I had been tracking three bitrig trees from https://github.com/bitrig : bitrig, bitrig-xenocara and bitrig-ports , noticed no activity at all since December 2016 or January 2017: dead OS. there are lots of gems in dmesgd.nycbug.org. we put it up in 2004 or (earlier IIRC) - i know i've put posted some hardware in there that i wish i still had :) -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Mon, Oct 8, 2018 at 1:37 AM Thomas Mueller wrote: > I just submitted /var/run/dmesg.boot from my current NetBSD and from > FreeBSD 11.1-STABLE. > > I was surprised to see some other BSD OSes listed, including 5 dmesg > reports from Bitrig and 3 from RetroBSD. > > I had been tracking three bitrig trees from https://github.com/bitrig : > bitrig, bitrig-xenocara and bitrig-ports , noticed no activity at all since > December 2016 or January 2017: dead OS. > RetroBSD has a similar fate: there's been 4 commits total since 2016. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
I just submitted /var/run/dmesg.boot from my current NetBSD and from FreeBSD 11.1-STABLE. I was surprised to see some other BSD OSes listed, including 5 dmesg reports from Bitrig and 3 from RetroBSD. I had been tracking three bitrig trees from https://github.com/bitrig : bitrig, bitrig-xenocara and bitrig-ports , noticed no activity at all since December 2016 or January 2017: dead OS. Tom ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sun, Oct 7, 2018 at 3:49 AM Konstantin Belousov wrote: > On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > > > Greetings, > > > > > > As you can tell, the project is looking to clear some of the deadwood > from > > > its driver lists. One problem is that we have to guess what's in used > based > > > on our personal experience. This has proven to be less reliable than > hoped > > > in the 10/100 discussions that are going on now. > > > > > > So, to that end, I'd like to request as many people as possible submit > > > their current dmesg to the service at > http://dmesgd.nycbug.org/index.cgi > > > so that we have a better basis for future preliminary lists of drivers > for > > > other parts of the tree. Please take the time to make these submissions > > > regardless of what your current hardware is. Please submit for any > machine > > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > > > generally masked out. > > > > > > This is just a request by me. I'll be using the data in about a month > to > > > look at old parallel scsi driver use. Though not definitive, it will be > > > suggestive of what's in use. The data is currently a bit thin, so I > thought > > > I'd see what a message like this could do to improve that situation. > This > > > should be viewed as a personal suggestion right now... > > > > > > Warner > > > > > > P.S. I know there's other user generated data sites out there, but this > > > appears to be the only one that's actually still working. > > > > > > > This one-liner works to submit, though you'll need to change username, > > email and maybe tweak the description if your system doesn't have decent > > smbios entries. It's also x86 centric, since other systems won't have > this > > information as readily available. > > > > 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 > > FWIW, on my NUC smbios part looks like this: > nuc% kenv | grep smbios.system\|smbios.planar >~ > smbios.planar.location="To be filled by O.E.M." > smbios.planar.maker="Intel Corporation" > smbios.planar.product="NUC5CPYB" > smbios.planar.serial="GEPY645001G0" > smbios.planar.tag=" " > smbios.planar.version="H61145-407" > smbios.system.family=" " > smbios.system.maker=" " > smbios.system.product=" " > smbios.system.serial=" " > smbios.system.sku=" " > smbios.system.uuid="96091100-727a-11e3-b004-f44d30670aa1" > smbios.system.version=" " > Yes. It seems that some systems have it in planar, and others in system. I suspect we'll need a simple shell script to do this (The perl one I was given simply doesn't work even though it says it does). Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sun, Oct 7, 2018 at 2:16 AM Dhananjay Balan wrote: > On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > > > Greetings, > > > > > > As you can tell, the project is looking to clear some of the deadwood > from > > > its driver lists. One problem is that we have to guess what's in used > based > > > on our personal experience. This has proven to be less reliable than > hoped > > > in the 10/100 discussions that are going on now. > > > > > > So, to that end, I'd like to request as many people as possible submit > > > their current dmesg to the service at > http://dmesgd.nycbug.org/index.cgi > > > so that we have a better basis for future preliminary lists of drivers > for > > > other parts of the tree. Please take the time to make these submissions > > > regardless of what your current hardware is. Please submit for any > machine > > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > > > generally masked out. > > > > > > This is just a request by me. I'll be using the data in about a month > to > > > look at old parallel scsi driver use. Though not definitive, it will be > > > suggestive of what's in use. The data is currently a bit thin, so I > thought > > > I'd see what a message like this could do to improve that situation. > This > > > should be viewed as a personal suggestion right now... > > > > > > Warner > > > > > > P.S. I know there's other user generated data sites out there, but this > > > appears to be the only one that's actually still working. > > > > > > > This one-liner works to submit, though you'll need to change username, > > email and maybe tweak the description if your system doesn't have decent > > smbios entries. It's also x86 centric, since other systems won't have > this > > information as readily available. > > > > 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 > > When I try to submit (with the oneliner or web form), it fails with > "Sorry, this is an unsupported OS. If you feel it should be added, please > contact admin." > > dmesg is from FreeBSD 12.0-ALPHA8 r339174=b24b22909(master). > Oh right. There's a known bug I should have mentioned: If your uname doesn't have a '#' in it, the script will reject it. You can add #0+ after the ALPHA8 and before the r339174 and it will work. I've reported this to the dmesg guys. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > Greetings, > > > > As you can tell, the project is looking to clear some of the deadwood from > > its driver lists. One problem is that we have to guess what's in used based > > on our personal experience. This has proven to be less reliable than hoped > > in the 10/100 discussions that are going on now. > > > > So, to that end, I'd like to request as many people as possible submit > > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi > > so that we have a better basis for future preliminary lists of drivers for > > other parts of the tree. Please take the time to make these submissions > > regardless of what your current hardware is. Please submit for any machine > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > > generally masked out. > > > > This is just a request by me. I'll be using the data in about a month to > > look at old parallel scsi driver use. Though not definitive, it will be > > suggestive of what's in use. The data is currently a bit thin, so I thought > > I'd see what a message like this could do to improve that situation. This > > should be viewed as a personal suggestion right now... > > > > Warner > > > > P.S. I know there's other user generated data sites out there, but this > > appears to be the only one that's actually still working. > > > > This one-liner works to submit, though you'll need to change username, > email and maybe tweak the description if your system doesn't have decent > smbios entries. It's also x86 centric, since other systems won't have this > information as readily available. > > 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 FWIW, on my NUC smbios part looks like this: nuc% kenv | grep smbios.system\|smbios.planar ~ smbios.planar.location="To be filled by O.E.M." smbios.planar.maker="Intel Corporation" smbios.planar.product="NUC5CPYB" smbios.planar.serial="GEPY645001G0" smbios.planar.tag=" " smbios.planar.version="H61145-407" smbios.system.family=" " smbios.system.maker=" " smbios.system.product=" " smbios.system.serial=" " smbios.system.sku=" " smbios.system.uuid="96091100-727a-11e3-b004-f44d30670aa1" smbios.system.version=" " ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, 6 Oct 2018 12:48:25 -0600 Warner Losh wrote: > Greetings, > > As you can tell, the project is looking to clear some of the deadwood from > its driver lists. One problem is that we have to guess what's in used based > on our personal experience. This has proven to be less reliable than hoped > in the 10/100 discussions that are going on now. > > So, to that end, I'd like to request as many people as possible submit > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so > that we have a better basis for future preliminary lists of drivers for > other parts of the tree. Please take the time to make these submissions > regardless of what your current hardware is. Please submit for any machine > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > generally masked out. > Verbose or normal? Or doesn't it matter? [snip] -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, 6 Oct 2018 23:40:36 -0600 Warner Losh wrote: [snip original post] > This one-liner works to submit, though you'll need to change username, > email and maybe tweak the description if your system doesn't have decent > smbios entries. It's also x86 centric, since other systems won't have this > information as readily available. > > 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 > On my system I would have to use smbios.planar.maker and smbios.planar.product because the corresponding smbios.system values are not filled in. Just a heads up for other users. This should be easy enough to check, since kenv will dump all its values, which allows a user to check what is really set. > Hope helps facilitate submission of entries. Thanks to Charles Sprickman > for the idea of using a curl one-liner. > -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
I can submit a dmesg even if I'm in NetBSD at the time: mount the FreeBSD partition and get the latest /mount-point/var/run/dmesg.boot . Question is what about those devices that don't work in FreeBSD but work in NetBSD, or which work in neither FreeBSD nor NetBSD? I'm thinking of re, where one Ethernet works in NetBSD but not FreeBSD. Also, wireless rsu and athn. Maybe I can also think of others. I noticed a lot of SCSI cards listed in GENERIC, but most these have gone out of production long ago as USB and SATA have taken over. Tom ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > Greetings, > > > > As you can tell, the project is looking to clear some of the deadwood from > > its driver lists. One problem is that we have to guess what's in used based > > on our personal experience. This has proven to be less reliable than hoped > > in the 10/100 discussions that are going on now. > > > > So, to that end, I'd like to request as many people as possible submit > > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi > > so that we have a better basis for future preliminary lists of drivers for > > other parts of the tree. Please take the time to make these submissions > > regardless of what your current hardware is. Please submit for any machine > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > > generally masked out. > > > > This is just a request by me. I'll be using the data in about a month to > > look at old parallel scsi driver use. Though not definitive, it will be > > suggestive of what's in use. The data is currently a bit thin, so I thought > > I'd see what a message like this could do to improve that situation. This > > should be viewed as a personal suggestion right now... > > > > Warner > > > > P.S. I know there's other user generated data sites out there, but this > > appears to be the only one that's actually still working. > > > > This one-liner works to submit, though you'll need to change username, > email and maybe tweak the description if your system doesn't have decent > smbios entries. It's also x86 centric, since other systems won't have this > information as readily available. > > 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 When I try to submit (with the oneliner or web form), it fails with "Sorry, this is an unsupported OS. If you feel it should be added, please contact admin." dmesg is from FreeBSD 12.0-ALPHA8 r339174=b24b22909(master). > > Hope helps facilitate submission of entries. Thanks to Charles Sprickman > for the idea of using a curl one-liner. > > Warner > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > Greetings, > > As you can tell, the project is looking to clear some of the deadwood from > its driver lists. One problem is that we have to guess what's in used based > on our personal experience. This has proven to be less reliable than hoped > in the 10/100 discussions that are going on now. > > So, to that end, I'd like to request as many people as possible submit > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi > so that we have a better basis for future preliminary lists of drivers for > other parts of the tree. Please take the time to make these submissions > regardless of what your current hardware is. Please submit for any machine > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > generally masked out. > > This is just a request by me. I'll be using the data in about a month to > look at old parallel scsi driver use. Though not definitive, it will be > suggestive of what's in use. The data is currently a bit thin, so I thought > I'd see what a message like this could do to improve that situation. This > should be viewed as a personal suggestion right now... > > Warner > > P.S. I know there's other user generated data sites out there, but this > appears to be the only one that's actually still working. > This one-liner works to submit, though you'll need to change username, email and maybe tweak the description if your system doesn't have decent smbios entries. It's also x86 centric, since other systems won't have this information as readily available. 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 Hope helps facilitate submission of entries. Thanks to Charles Sprickman for the idea of using a curl one-liner. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
dmesg submission service -- please submit today
Greetings, As you can tell, the project is looking to clear some of the deadwood from its driver lists. One problem is that we have to guess what's in used based on our personal experience. This has proven to be less reliable than hoped in the 10/100 discussions that are going on now. So, to that end, I'd like to request as many people as possible submit their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so that we have a better basis for future preliminary lists of drivers for other parts of the tree. Please take the time to make these submissions regardless of what your current hardware is. Please submit for any machine you'd like to upgrade to FreeBSD 12 or 13. Identifying information is generally masked out. This is just a request by me. I'll be using the data in about a month to look at old parallel scsi driver use. Though not definitive, it will be suggestive of what's in use. The data is currently a bit thin, so I thought I'd see what a message like this could do to improve that situation. This should be viewed as a personal suggestion right now... Warner P.S. I know there's other user generated data sites out there, but this appears to be the only one that's actually still working. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
