Re: What do you use for kernel debugging?

On 1 Oct 2014, at 0:14, Julian Elischer jul...@freebsd.org wrote: Unfortunately you can't use a USB serial as it requires the USB stack be working before it can be used.. similar with ethernet connected debugging which requires that the driver for the ethernet hardware support it. (which

Re: What do you use for kernel debugging?

it for freebsd. :) Not sure I have the cycles :( -a On 30 September 2014 21:45, O'Connor, Daniel Daniel.O'con...@emc.com wrote: On 1 Oct 2014, at 0:14, Julian Elischer jul...@freebsd.org wrote: Unfortunately you can't use a USB serial as it requires the USB stack be working before it can

Re: What do you use for kernel debugging?

On 1 Oct 2014, at 15:54, O'Connor, Daniel Daniel.O'con...@emc.com wrote: On 1 Oct 2014, at 14:33, Adrian Chadd adr...@freebsd.org wrote: There's also something for XHCI. So I see.. Section 7.6 in here has details.. http://www.intel.com.au/content/dam/www/public/us/en/documents/technical

Re: HEADS UP: Standalone kernel debug files moving out of /boot/kernel/

On 30 Oct 2014, at 19:44, Steven Hartland kill...@multiplay.co.uk wrote: On 30/10/2014 08:24, O'Connor, Daniel wrote: On 30 Oct 2014, at 13:23, Steven Hartland kill...@multiplay.co.uk wrote: Making things harder to manage vs saving a little bit of space on the root partition really doesn't

Re: HEADS UP: Standalone kernel debug files moving out of /boot/kernel/

On 30 Oct 2014, at 13:23, Steven Hartland kill...@multiplay.co.uk wrote: Making things harder to manage vs saving a little bit of space on the root partition really doesn't sound like a good idea; especially when with the ZFS install, which I would suggest is becoming the norm, the root

Re: obtaining a minidump from panic() called from NMI handler

On 13 Jun 2015, at 09:17, Julian Elischer jul...@freebsd.org wrote: could it be that more than one CPUs get the NMI at the same time? i guess, its possible. is there an easy way to check for that? hard code checks in the code so that all except the first do something different. (even

-current broken when src is on NFS

I am seeing the following breakage when building -current and the source is on NFS make -j 4 buildworld ... --- rescue.all__D --- --- rescue --- MAKEOBJDIRPREFIX=/usr/obj/src/FreeBSD-HEAD/rescue/rescue make -f rescue.mk exe --- sbin.all__D --- --- pfctl_qstats.o --- cc -O2 -pipe -Wall

Re: -current broken when src is on NFS

On 16 Jul 2015, at 21:41, Rick Macklem rmack...@uoguelph.ca wrote: r285066 fixed a POLA violation w.r.t. the old NFS client where the new client didn't return an EEXIST error return for symlink or mkdir to userland. The behaviour of not returning this error to userland (which was inherited

Re: -current broken when src is on NFS

On 18 Jul 2015, at 13:59, Tim Kientzle t...@kientzle.com wrote: Crochet defaults MAKEOBJDIRPREFIX to ${WORKDIR}/obj if you have not already set it to something else. (This avoids cross-polluting the builds if you do regular manual cross-builds on the same machine.) If you’re having

Re: -current broken when src is on NFS

On 17 Jul 2015, at 14:27, O'Connor, Daniel dar...@dons.net.au wrote: On 16 Jul 2015, at 21:41, Rick Macklem rmack...@uoguelph.ca wrote: r285066 fixed a POLA violation w.r.t. the old NFS client where the new client didn't return an EEXIST error return for symlink or mkdir to userland

Re: -current broken when MAKEOBJDIRPREFIX is set (was: src is on NFS)

On 19 Jul 2015, at 02:56, Simon J. Gerraty s...@juniper.net wrote: O'Connor, Daniel dar...@dons.net.au wrote: However, Crochet _does_ build on the NFS client _and_ when the source tree isn't in /usr/src which makes this issue very strange :-/ I've seen similar errors in rescue... (no NFS

Re: -current broken when MAKEOBJDIRPREFIX is set (was: src is on NFS)

On 20 Jul 2015, at 04:29, Simon J. Gerraty s...@juniper.net wrote: O'Connor, Daniel dar...@dons.net.au wrote: But this did not.. make -j 8 buildworld MAKEOBJDIRPREFIX=/src/obj-amd64 Nor should it. There are several makefiles in the tree that expect to be able to change

Re: -current broken when MAKEOBJDIRPREFIX is set (was: src is on NFS)

On 20 Jul 2015, at 11:40, Simon J. Gerraty s...@juniper.net wrote: O'Connor, Daniel dar...@dons.net.au wrote: So, it seems MAKEOBJDIRPREFIX only works as an environmental variable Weird, I could have sworn I have set it on the command line and had it work, but.. In most normal usage

Re: gettimeofday((void *)-1, NULL) implicates core dump on recent FreeBSD 11-CURRENT

On 8 Jul 2015, at 08:11, Garrett Wollman woll...@hergotha.csail.mit.edu wrote: Perhaps the test was (erroneously) written to assume that gettimeofday() was a system call, and could therefore detect invalid pointers and return [EFAULT]. This has not been the case for some time. (In HEAD,

Re: Read-only /usr/obj/ no longer kosher?

On 27 Aug 2015, at 08:25, Pawel Jakub Dawidek p...@freebsd.org wrote: On Tue, Aug 25, 2015 at 03:32:35PM -0700, NGie Cooper wrote: On Tue, Aug 25, 2015 at 3:21 PM, Xin Li delp...@delphij.net wrote: On 08/25/15 14:55, Pawel Jakub Dawidek wrote: Now that I think of it, it might have been that

Re: Digi Watchport/T temperature sensor as /dev/ttyU

> On 23 Jul 2016, at 02:05, O. Hartmann wrote: > > I tried to load any available USB serial port/adaptor driver available to > make this > sensor attach as a ttyU? as it does in Linux (/dev/ttyUSB), but no luck so > far. I'm not > familiar with serial consoles or

Re: Passwordless accounts vi ports!

> On 11 Aug 2016, at 15:36, O'Connor, Daniel <dar...@dons.net.au> wrote: > My clamav and pulse users have a password field of * - i.e. they're disabled > (AND the shell is nologin) > > I suspect this is a bug in the check not the ports. Sorry, I just saw your next em

Re: Passwordless accounts vi ports!

> On 11 Aug 2016, at 14:35, O. Hartmann wrote: > [...] > Checking for passwordless accounts: > polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin > pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin > saned::194:194::0:0:SANE

Re: Somethign missing in my environment?

> On 18 Aug 2016, at 06:12, Willem Jan Withagen wrote: > >> There's nothing immediately obvious. I suggest trying without the >> "-DNOCLEAN -DNO_CLEAN" - they are shortcuts that aren't guaranteed to >> work under all circumstances. And if that still fails, skip the '-j8' >>

Re: Somethign missing in my environment?

> On 18 Aug 2016, at 20:59, Willem Jan Withagen wrote: >> >> Remove NO_CLEAN et al and delete /usr/obj/* then try again. > > It is running single thread, but compiling clang is a rather hefty build. Yes but you are having weird issues so.. Time to go back to basics :) >>

Re: Destroy GPT partition scheme absolutely, how?

> On 27 Sep 2016, at 14:28, Warner Losh wrote: > dd of 2MB of zeros to the start and end of the disk. That will destroy > pretty much everything. For SSDs, sometimes you can do the same with > TRIMs only faster (other times they are slower or unreliable). Yeah, but it would be

Re: Destroy GPT partition scheme absolutely, how?

> On 27 Sep 2016, at 06:21, John Baldwin wrote: > That doesn't always work. In particular, if a disk was partitioned with GPT > and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the > MBR will leave most of the GPT intact and the disk will come up with

Re: RFC: Removing hpt* drivers from GENERIC

> On 26 Oct 2017, at 08:13, Colin Percival wrote: > My reason for wanting to remove them is that the hpt27xx and hptnr drivers > spend ~150 ms in their DEVICE_PROBE routines every time the system boots. > Since they are roughly 1000x slower than the median driver, this is

Re: USB stack

> On 3 Jan 2018, at 11:31, blubee blubeeme wrote: > Does FreeBSD current USB stack support usb >= 2.0 devices? Absolutely. > Testing out the USB devices support I get about 7.2-7.8 megabytes per > second which seems odd. What sort of test? What sort of device? What sort

Re: USB stack

> On 3 Jan 2018, at 11:56, blubee blubeeme <gurenc...@gmail.com> wrote: > On Wed, Jan 3, 2018 at 6:41 PM, O'Connor, Daniel <dar...@dons.net.au> wrote: > > > > On 3 Jan 2018, at 11:31, blubee blubeeme <gurenc...@gmail.com> wrote: > > Does FreeBSD cu

Re: USB stack

> On 4 Jan 2018, at 09:23, Gary Jennejohn wrote: >> What is an "LG v30"? >> > It's a smartphone from LG and only supports USB2 speed. The reported > transfer rate is no big surprise. OK thanks. -- Daniel O'Connor "The nice thing about standards is that there are so

Re: Testing requested: Hybrid ISO/USB boot

> On 24 Mar 2018, at 07:31, Benno Rice wrote: > I think I’ve addressed this in this revision: > > https://svnweb.freebsd.org/changeset/base/331463 > > > And I’ve regenerated the image here: > >

Re: ipv6/ppp: FreeBSD obtains linklocal on tun0 only

> On 3 Dec 2018, at 08:15, O. Hartmann wrote: > > > The documentation lacks in many aspects how to deal with IPv6, especially > when it comes > to "well known things from the old IPv4 world". Since DDNS also is still > something people > use with IPv6, MYADDR6 doesn't carry the IPV6

Re: nvdXpY dissapears while ZFS pool on it is imported

> On 6 Oct 2019, at 01:06, Bernd Walter wrote: > > On Sat, Oct 05, 2019 at 02:50:21PM +0900, Tomoaki AOKI wrote: >> Hi. >> >> By sets of commits starting from r351355 though r351747, nvd driver >> creates partitioned GEOM provider like /dev/nvd0p1. >> >> Unfortunately, these partitioned

Re: Lockdown adaX numbers to allow booting ?

> On 21 Sep 2019, at 02:36, Garrett Wollman > wrote: > > In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: > >> Location of device in multi-chassis storage system is different story. >> I am don't know how to field engineer insert disks in chassis. >> For me simple is

Re: Lockdown adaX numbers to allow booting ?

> On 14 Oct 2019, at 03:17, Kurt Jaeger wrote: >>> You're probably looking for this: >>> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html >> >> Would glabel solve it? > > The disks are not gpart-formatted, they are used raw. What file system are they formatted with? UFS

Re: Lockdown adaX numbers to allow booting ?

> On 14 Oct 2019, at 19:08, Kurt Jaeger wrote: > > Hi! > > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Would glabel solve it? >>> >>> The disks are not gpart-formatted, they are used raw. >> >> What file

Re: Can't forward X11 apps over ssh since migrating to 13-CURRENT

> On 22 Sep 2020, at 08:06, Patrick McMunn wrote: > I don't know if it's just coincidental or if it's because of some change in > 13-CURRENT, but I recently migrated from 12.1-STABLE, and now I am unable > to forward X11 apps over ssh. The only app I was accustomed to running this > way was