Re: 12-Current-r331347 panics on boot (r331346 and earlier didn't.)

OK, I've completed the search: r331346 works, r331347 panics somewhere in the initialization of random. In the 331347 change (Add the "TCP Blackbox Recorder") I can't see anything obvious to tweak, unfortunately. It's a fair chunk of new code but it's all network-stack related, and my kernel is

Re: 12-Current panics on boot (didn't a week ago.)

OK, I've completed the search: r331346 works, r331347 panics somewhere in the initialization of random. In the 331347 change (Add the "TCP Blackbox Recorder") I can't see anything obvious to tweak, unfortunately. It's a fair chunk of new code but it's all network-stack related, and my kernel is

Current fails to install in virtualbox: Distribution extract failed

This ISO image: FreeBSD-12.0-CURRENT-amd64-20180322-r331345-disc1.iso Differences with default: I chose ZFS root fs and only left "ports" checked in "Distribution Select". Yuri ___ freebsd-current@freebsd.org mailing list

Re: 12-Current panics on boot (didn't a week ago.)

So, r331464 crashes in the same place, on my system. r331064 still boots OK. I'll keep searching. One week ago there was a change to randomdev to poll for signals every so often, as a defence against very large reads. That wouldn't have introduced a race somewhere, or left things in an

Re: 12-Current panics on boot (didn't a week ago.)

Thanks Andrew... I can't recreate this on my VM nor my real hardware. Warner On Sat, Mar 24, 2018 at 5:22 PM, Andrew Reilly wrote: > So, r331464 crashes in the same place, on my system. r331064 still boots > OK. I'll keep searching. > > One week ago there was a change

Re: 12-Current panics on boot (didn't a week ago.)

Hi Warner, The breakage was in 331470, and at least one version earlier, that I updated past when it panicked. I'm guessing that kdb's inability to dump would be down to it not having found any disk devices yet, right? So yes, bisecting to narrow down the issue is probably the best bet.

Re: CURRENT r331284: crashing with USB

On Sat, Mar 24, 2018 at 11:52:17AM -0600, Ian Lepore wrote: > > Those snippets are some of the first things uboot says when it starts. > > -- Ian Yes, understood. The initial console text flooded off the terminal scrollback, so it couldn't be captured. The portion selected was meant mostly to

Re: CURRENT r331284: crashing with USB

On Sat, 2018-03-24 at 10:39 -0700, bob prohaska wrote: > On Wed, Mar 21, 2018 at 09:49:34PM -0700, bob prohaska wrote: > > > > On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote: > > > > > > > > > not the ZFS. I can plugin the USB and then unplug it and after > > > two or > > > three

Re: CURRENT r331284: crashing with USB

On Wed, Mar 21, 2018 at 09:49:34PM -0700, bob prohaska wrote: > On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote: > > > > not the ZFS. I can plugin the USB and then unplug it and after two or > > three times doing this, the box goes down. > > > > > > Does anyone else observe this

Re: freebsd-update: to a specific patch level - help please? [PATCH]

On 18-03-23 06:44 AM, Kurt Jaeger wrote: Hi! To be clear, *I've included a link to a patch to freebsd-update in my initial post, and the help I'm looking for: is to get this functionality added as a feature so others can benefit.* It works for me already, and I've already benefited. (I'm

Re: 12-Current panics on boot (didn't a week ago.)

Also, what rev failed? I booted r331464 last night w/o issue. Warner On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly wrote: > Hi all, > > For reasons that still escape me, I haven't been able to get a kernel dump > to debug, sorry. > > Just thought that I'd generate a

Re: 12-Current panics on boot (didn't a week ago.)

That lock has been there for a long, long time (like 5 or 6 major releases)... It's surprising that it's causing issues now. Can you bisect versions to find when this starts happening? Warner On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly wrote: > Hi all, > > For

installkernel error WITHOUT_BLUETOOTH

Hi,    Just ran into this issue when trying to "make installkernel" after adding the "WITHOUT_BLUETOOTH" flag to my "/etc/src.conf" (see snippet below). Is this expected behaviour? Do I need to add "WITHOUT_NETGRAPH" also? > install -T

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov wrote: > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > patch causes a different panic: > > > >

g_handleattr: md0 bio_length 24 len 31 -> EFAULT

Writing out memory (md) backed images of UFS2 filesystems (NanoBSD images, created via the classical manual way, no makefs), my recent CURRENT system dumps the console full of these error messages: g_handleattr: md0 bio_length 24 len 31 -> EFAULT I do not know what they are supposed to mean and

12-Current panics on boot (didn't a week ago.)

Hi all, For reasons that still escape me, I haven't been able to get a kernel dump to debug, sorry. Just thought that I'd generate a fairly low-quality report, to see if anyone has some ideas. The last kernel that I have that booted OK (and I'm now running) is: FreeBSD Zen.ac-r.nu