ebugging messages at
this point?
Thanks for help. Hopefully useful log data are below.
Steven
=== PANIC ===
Apr 2 04:16:27 freebsd kernel: iichid0:
at addr 0x2c irq 51 on iicbus0
Apr 2 04:16:27 freebsd kernel: hidbus0: on iichid0
Apr 2 04:16:27 freebsd kernel:
Apr 2 04:16:27 freebsd syslogd:
4)
# make -j4 kernel (5)# shutdown -r now (6)
And am after the shutdown -r now step:
If my process for kernel and world build is correct, then I have found a panic.
How can I help/debug?
Thanks!
Steven
---
Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE
Messages from this account are
n-technical friends. Pair with a short autoboot_delay and
beastie_disable, this setting gets the computer from POST to a graphical
login without leaking any of the OS internals
* waylandDM: Same as above but with Wayland
There might be other variables that capture the signal bett
nguage / versioning in the man pages, but will update later today after I
install the world.
On Sat, Mar 22, 2025 at 03:02, Emmanuel Vadot
<[m...@bidouilliste.com](mailto:On Sat, Mar 22, 2025 at 03:02, Emmanuel Vadot
< wrote:
> Hi,
>
> On Fri, 21 Mar 2025 22:13:29 +
> "Ste
red
behavior is. Can anyone help me figure out what the desired behavior is (and
maybe I can update the comments)? My current plan is to turn the array into
0x00 and see what happens, but I'd like to know how I can turn the results of
that experiment into a patch.
Best,
Steven
docs bug?
Best,
Steven
---
Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE
Messages from this account are considered the best-secured and most reliable.
Send information regarding health, wealth, or requiring higher standards of
security to this address.
Sent with [Proton Mail](https://prot
ving
i915_driver_(register|probe)...which suggests that maybe these two things are
related. Line 3260 is where a mutex is sought as part of the replace routine.
I think I've troubleshot this reasonably, is there some angle I've missed? I'd
like to have a clean dmesg on my
frightening/annoying to
some
- a dedicated live sink for console messages (versus a log file or versus your
vi session) closer to a real serial console or OSX's console.app
Is this a better approach vs extending boot_mute's run? Or if this is
wrong-headed I'll go back to p
covering up kernel init as well as RC init).
The source suggests to me that once the vt subsystem is up and the console
connected, the overlay is expelled. I don’t have a background in this, but
what’s the difficulty of making that overlay persist?
Steven
On Mon, Feb 3, 2025 at 14:22, Maku Bex
ry / possible /
> allowed.
I support this implementation. boot_mute=YES hides all diagnostic data up
to the prompt being ready (surely one could hook getty's code for an
ioctl?). I also think that ESC as a means for getting to the full
diagnostics as in status quo is a great place to debug uh-oh moments.
It's beyond my capability to
size this story, *but* I can't imagine it being a weeks-long effort.
Steven
something that should be available?
* If so: resolve via log level, per-function verbosity suffixes, provide a
longer overlay bitmap duration option, or some other means
Thank you for your consideration,
Steven
Steven
e. If that's not the correct procedure,
please advise.
Thanks for all the work everyone on the list does!
Steven
---
Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE
Messages from this account are considered the best-secured and most reliable.
Send information regarding health, wealth, or
On Friday, 19 February 2021 06:41:49 EST Steven Friedrich wrote:
> BTW, I included output from pciconf, but the device is USB. Sorry.
> I was confused because there's an unsupported wi-fi on the motherboard, also
> from Realtek.
> mobo Realtek is 8821ce
> USB Realtek is 881
On Thursday, 18 February 2021 16:35:48 EST Daniel Stevenson wrote:
> On Thursday, February 18th, 2021 at 04:40, Steven Friedrich
wrote:
> > Starting devd.
> >
> > Cannot 'start' webcamd. Set webcamd_enable to YES in /etc/rc.conf or use
> >
> >
Looks like it should still be there if your using the in tree ZFS:
https://svnweb.freebsd.org/base/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c?revision=358333&view=markup#l144
On 01/05/2020 19:03, Graham Perrin wrote:
In my sysctl.conf:
vfs.zfs.min_auto_ashift=12
– if I recall c
On 20/12/2018 11:03, Bob Bishop wrote:
Hi,
On 19 Dec 2018, at 23:16, Matthew Macy wrote:
On Wed, Dec 19, 2018 at 15:11 Steven Hartland
wrote:
Sorry been off for a few weeks so must have missed that, please do prod me
on again if you don’t see any response to anything not just this. Like
this over the
line, especially when people have competing priorities.
On Wed, 19 Dec 2018 at 22:52, Matthew Macy wrote:
>
>
> On Wed, Dec 19, 2018 at 14:47 Steven Hartland
> wrote:
>
>> Thanks for the write up most appreciated. One of the more meaty
>> differences is
Thanks for the write up most appreciated. One of the more meaty differences
is that FreeBSD ZFS still has the only merged and production ready TRIM
support so my question would be are their any plans to address this before
creating the new port as going back to a world without TRIM support
wouldn’t
Yes it does know how to figure out based on stripe size
On Tue, 26 Dec 2017 at 20:25, O. Hartmann wrote:
> Am Tue, 26 Dec 2017 09:31:53 -0800 (PST)
> "Rodney W. Grimes" schrieb:
>
> > > On Tue, Dec 26, 2017 at 10:04 AM, O. Hartmann
> > > wrote:
> > >
> > > > Am Tue, 26 Dec 2017 11:44:29 -0500
You only need to set the min if the drives hide their true sector size, as
Allan mentioned.
camcontrol identify is one of the easiest ways to check this.
If the pool reports ashift 12 then zfs correctly detected the drives as 4K
so that part is good
On Tue, 26 Dec 2017 at 20:15, Rodney W. Grime
Is this related to kib's additional fix over the weekend?
https://svnweb.freebsd.org/changeset/base/320344
Regards
Steve
On 26/06/2017 09:29, O. Hartmann wrote:
Over the past week we did not update several 12-CURRENT running development
hosts, so today is the first day of performing th
Add the following to /boot/loader.conf
Its a tunable but not a sysctl so you can't query it, you just need to
set it by adding it to /boot/loader.conf:
hw.vga.textmode="1"
On 20/03/2017 21:58, Chris H wrote:
I'm attempting to get a video card that DTRT on FreeBSD.
I started with the graphics
On 07/02/2017 16:33, Toomas Soome wrote:
On 7. veebr 2017, at 18:08, Thomas Sparrevohn
wrote:
Hi all
Last week I decided to upgrade my FreeBSD installation - it's been a while
(September 16 was last time). Unfortunately CURRENT does not boot and cash
in a weird way. Both 11-RELEASE and 1
On 15/01/2017 17:45, Pete Wright wrote:
On 1/15/17 8:22 AM, Kyle Evans wrote:
On Jan 15, 2017 10:03, "Julian Elischer" wrote:
I noticed that suddenly vim is grabbing mouse movements, which makes
life
really hard.
Was there a specific revision that brought in this change, and can it be
rem
Hmm I'm not sure about everyone else but I we treat emX as legacy
devices (not used one in years) but igbX is very common here.
The impact of changing a nic device name is quite a bit more involved
than just rc.conf it effects other areas too, jails etc so given we can
loose access to the mach
On Fri, Dec 16, 2016 at 03:19:09PM -0800, John Baldwin wrote:
>
> So the hack in pause() is probably not as necessary now. In particular, I
> think we only need it for thread0, not for other threads. The patch below
> worked for me with SPEW's config:
>
> Index: kern_synch.c
> =
On Fri, Dec 16, 2016 at 03:19:09PM -0800, John Baldwin wrote:
>
> So the hack in pause() is probably not as necessary now. In particular, I
> think we only need it for thread0, not for other threads. The patch below
> worked for me with SPEW's config:
>
> Index: kern_synch.c
> =
On Wed, Dec 14, 2016 at 04:50:21PM -0800, Mark Johnston wrote:
> On Wed, Dec 14, 2016 at 03:48:04PM -0800, Steven G. Kargl wrote:
> > On Wed, Dec 14, 2016 at 02:10:48PM -0800, Mark Johnston wrote:
> > > On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote:
> > >
On Wed, Dec 14, 2016 at 02:10:48PM -0800, Mark Johnston wrote:
> On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote:
> > On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote:
> > > Well, after 3 days of bisection, I finally found the commit
> >
Well, after 3 days of bisection, I finally found the commit
that renders my system unbootable. The system does not panic.
It simply gets stuck in some state. Nonfunctional keyboard,
so can't break into debugger. No serial console available.
The verbose dmesg.boot for a working kernel from revisi
On Fri, Dec 09, 2016 at 03:45:30PM -0800, Steven G. Kargl wrote:
> On Fri, Dec 09, 2016 at 11:58:21PM +0100, Hans Petter Selasky wrote:
> > On 12/09/16 22:09, Steve Kargl wrote:
> > > I updated my system to
> > >
> > > % svn info /usr/src
> > > Revision
On Fri, Dec 09, 2016 at 11:58:21PM +0100, Hans Petter Selasky wrote:
> On 12/09/16 22:09, Steve Kargl wrote:
> > I updated my system to
> >
> > % svn info /usr/src
> > Revision: 309748
> >
> > Built a shiny new kernel, which hangs during boot.
> > There is no panic. Using the dmesg from kernel.old
CAM already does this, doesn't really help with speed as much as you
might think though.
On 04/10/2016 19:53, Maxim Sobolev wrote:
For the whole disk destruction, hopefully one day we'd have BIO_DELETE
coalesce code, so that you can batch of lot of operations into handful SATA
commands. I've he
On Fri, Sep 16, 2016 at 02:07:38PM +0900, Takanori Watanabe wrote:
> On Thu, Sep 15, 2016 at 07:20:39PM -0700, Steven G. Kargl wrote:
> > On Thu, Sep 15, 2016 at 06:20:06PM -0700, Adrian Chadd wrote:
> > > hi,
> > >
> > > bluetooth uses netgraph.
> >
&g
On Thu, Sep 15, 2016 at 06:20:06PM -0700, Adrian Chadd wrote:
> hi,
>
> bluetooth uses netgraph.
>
Yeah, I figured that much out. I do not
need bluetooth nor netgraph. How does
one explicitly disable this (other than
through the BIOS)?
--
Steve
http://troutmask.apl.washington.edu/~kargl/
___
Out of sync kernel / world?
Do you have a crash dump?
On 03/09/2016 21:50, Subbsd wrote:
Hi.
Can anybody test of output for:
zfs list
command on FreeBSD current after r305211 ? On my hosts his leads to
zfs segfault.
___
freebsd-current@freebsd.org
On Thu, Jul 21, 2016 at 03:50:48PM -0400, Michael Butler wrote:
> On 07/21/16 14:32, Steve Kargl wrote:
> > Updating uname -a
> > FreeBSD 11.0-ALPHA5 FreeBSD 11.0-ALPHA5
> > #3 r302248: Tue Jun 28 10:11:31 PDT 2016
> > data/obj/usr/src/sys/SPEW amd64
> >
> > to top-of-tree
> >
> > ===> lib/libsb
When ever I've seen installworld issues after a full buildworld its been
clock related, so might want to check the clock on the machine is right.
On 17/07/2016 20:58, Kim Culhan wrote:
Seeing this on FreeBSD 11.0-BETA1 #0 r302963M
After make buildworld completes with no problem, then rebooted
On 12/07/2016 22:20, Ed Schouten wrote:
2016-07-11 23:01 GMT+02:00 Ronald Klop :
Just downloaded the amd64 BETA1 ISO (873MB) and tried to burn a CD on
Windows 10. It complained that the ISO is too big for my 700 MB CD-r.
I remember back in the days we also had a 'miniinst' CD, which was
identic
On 12/07/2016 21:50, Slawa Olhovchenkov wrote:
On Tue, Jul 12, 2016 at 01:39:34PM -0700, Conrad Meyer wrote:
Maybe Tier 2 can deal with just bootonly.iso. Or your machines should
be dropped from Tier 2 if they don't support USB and we aren't okay
with dropping disc1 support for all of Tier 2.
On 12/07/2016 20:52, Mark Linimon wrote:
On Tue, Jul 12, 2016 at 04:09:10PM +0930, Shane Ambler wrote:
+1 on dropping CD images.
I have 24U of things that don't have DVD players, including some tier-2
machines for which no upgrade is available.
Any no USB?
On 11/07/2016 23:39, Allan Jude wrote:
On 2016-07-11 18:33, Chris H wrote:
On Tue, 12 Jul 2016 00:46:04 +0300 Slawa Olhovchenkov
wrote
On Mon, Jul 11, 2016 at 09:41:44PM +, Glen Barber wrote:
On Mon, Jul 11, 2016 at 03:32:34PM -0600, Alan Somers wrote:
On Mon, Jul 11, 2016 at 2:01 P
Just a heads-up.
Thanks again.
On Wed, Jul 6, 2016 at 7:51 PM, Steven Hartland
mailto:kill...@multiplay.co.uk>> wrote:
On 06/07/2016 21:39, Eric van Gyzen wrote:
On 07/06/16 03:35 PM, Steven Hartland wrote:
The ARC settings and kmem aren't initialised when
On 06/07/2016 21:39, Eric van Gyzen wrote:
On 07/06/16 03:35 PM, Steven Hartland wrote:
The ARC settings and kmem aren't initialised when tunables are loaded
so the tests fail.
I've fixed this locally by blindly setting if ARC is not configured.
Request to commit the fix is with r
nk in about 4 - 5 hours I can show what values I'm using in
loader.conf under, say, r302264 and r302265 for comparison. I'm not 100%
sure that the problem arose for me in r302265; I merely suspect it.
On Tue, Jul 5, 2016 at 9:25 PM, Allan Jude mailto:allanj...@freebsd.org>> wrote:
On 06/07/2016 02:25, Allan Jude wrote:
On 2016-07-05 20:27, Steven Hartland wrote:
Ahh right, let me check that.
On 06/07/2016 00:51, Nathan Bosley wrote:
I actually have this same problem.
I'll send more details when I get home later.
I think the problem started for me after r302265.
B
sing 'sysct' or sysctl.conf for vfs.zfs.arc_max
and vfs.zfs.arc_min works.
I only have problems with setting them now in loader.conf.
Like I said, I'll try to send output from my setup later.
Thanks.
On Tue, Jul 5, 2016 at 6:10 PM, Steven Hartland
mailto:ste...@multiplay.co.uk>&g
uspect you're requesting a value which one of
the following:
* < arc_abs_min
* > kmem_size
* < arc_c_min
* < zfs_arc_meta_limit
Regards
Steve
On 05/07/2016 22:56, Eric van Gyzen wrote:
Steven and -current:
I just updated to r302350 with a GENERIC kernel config. I see this i
On Wed, Jun 22, 2016 at 11:15:27AM +0300, Andriy Gapon wrote:
> On 22/06/2016 01:04, Steve Kargl wrote:
> > After a forced umount of a msdos filesystem, I received
> > a panic. I have the kernel and vmcore. The first hundred
> > or so lines of core.txt.4 follow my .sig.
> >
>
> It seems that th
On 24/05/2016 21:56, Kenneth D. Merry wrote:
On Tue, May 24, 2016 at 23:54:09 +0300, Oleg V. Nauman wrote:
On Tuesday 24 May 2016 16:17:33 you wrote:
Okay, I've got a basic idea of what may be going on. The resets that are
getting sent are triggering another probe, which then triggers a rese
On 15/04/2016 09:11, Kurt Jaeger wrote:
Hi!
avg wrote:
For what it's worth, I have been using the following SSDs since September of
2015 :
ada2: ACS-2 ATA SATA 3.x device
ada3: ACS-2 ATA SATA 3.x device
I have one in use with zfs and trim:
ada1: ACS-2 ATA SATA 3.x device
Works as my por
On 11/04/2016 15:24, Tomoaki AOKI wrote:
Thanks for your answer!
On Sun, 10 Apr 2016 16:15:56 +0100
Steven Hartland wrote:
On 10/04/2016 15:35, Tomoaki AOKI wrote:
On Sun, 10 Apr 2016 06:59:04 -0600
Alan Somers wrote:
On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI
wrote:
Hi. Maybe
On 10/04/2016 15:35, Tomoaki AOKI wrote:
On Sun, 10 Apr 2016 06:59:04 -0600
Alan Somers wrote:
On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI
wrote:
Hi. Maybe freebsd-hardware list would be the right place, but it's not
so active. :-(
Is 4K quirks needed for every HDDs/SSDs having physic
vfs.zfs.min_auto_ashift is only used when a device is added so you can set it
add, then change.
On 31/03/2016 07:15, Allan Jude wrote:
On 2016-03-31 02:13, Dustin Marquess wrote:
I have what I think is a pretty normal setup.. a bunch of HDDs plus 2 SSDs
(one ZIL, one SLOG).
The HDDs are stan
On 18/03/2016 17:51, Guido Falsi wrote:
On 03/18/16 17:54, José Pérez wrote:
Hi Guido,
maybe it's because of this:
https://svnweb.freebsd.org/base?view=revision&revision=296963
I see.
There is a problem with this though, we have howtos suggesting 64K for
the size of the freebsd-boot gpt part
On 18/03/2016 17:42, Nikolai Lifanov wrote:
On 03/18/16 13:03, Allan Jude wrote:
On 2016-03-18 12:33, Guido Falsi wrote:
Hi,
I have just update one of my machines and noticed the booloaders files
got quite fat in the last few days, some by a big margin.
on an updated machine(r296993):
ls
On 14/03/2016 22:28, Larry Rosenman wrote:
On 2016-03-14 17:25, Poul-Henning Kamp wrote:
In message <2016031428.ga1...@borg.lerctr.org>, Larry Rosenman
writes:
And sshd is busted.
FYI: I seeing no such issues on two systems running:
11.0-CURRENT #4 r296808: Sun Mar 13 2
So your saying "kldload zfs" fails because it can't find opensolaris or
are you giving it absolute paths?
If so try without absolute paths.
Regards
Steve
On 07/03/2016 14:09, Larry Rosenman wrote:
If I type load /boot/kernel/kernel, and then load /boot/kernel/zfs.ko,
the loader
(loade
isn't that 48 cores (12 real 12 virtual) per CPU?
On 22/02/2016 21:26, Ultima wrote:
This system has 24 cores (e5-2670v3)x2
Ultima
On Mon, Feb 22, 2016 at 3:53 PM, Pieper, Jeffrey E <
jeffrey.e.pie...@intel.com> wrote:
Just out of curiosity, how many cores does your system have?
Jeff
-
Yep thanks, I committed this to head today, after Warner confirmed it
was good in his env too.
It will sit there for 1 week before I request permission to MFC to
stable/10.
On 05/02/2016 17:24, Tomoaki AOKI wrote:
> I got a feedback from Yuichiro NAITO at freebsd-users-jp ML.
>
> Boots fine using
), 5) [USB boot] for Diff7 and 1) [single
drive] for Diff8 are done.
Regards.
On Sun, 31 Jan 2016 13:58:23 +0000
Steven Hartland wrote:
Thanks for doing that it was very helpful, and I know transcribing from
video would have been quite a time consuming task.
I noticed a few interesting facts:
1
drive] for Diff8 are done.
Regards.
On Sun, 31 Jan 2016 13:58:23 +
Steven Hartland wrote:
Thanks for doing that it was very helpful, and I know transcribing from
video would have been quite a time consuming task.
I noticed a few interesting facts:
1. It looks like when you boot fr
be in conjunction with changes after r294265 in head, as
currently Diff6 doesn't apply to stable/10.
Regards.
On Sat, 30 Jan 2016 19:12:34 +
Steven Hartland wrote:
I believe, based on testing, that the from Diff 5 onwards of
https://reviews.freebsd.org/D5108 this should work as you
ed
ZFS module, so I must edit the definition of *boot_modules[] in
boot1.c. I'd have been missing something.
Regards.
On Fri, 29 Jan 2016 02:58:26 +
Steven Hartland wrote:
On 28/01/2016 16:22, Doug Rabson wrote:
On 28 January 2016 at 15:03, Tomoaki AOKI wrote:
It's exa
ed
ZFS module, so I must edit the definition of *boot_modules[] in
boot1.c. I'd have been missing something.
Regards.
On Fri, 29 Jan 2016 02:58:26 +
Steven Hartland wrote:
On 28/01/2016 16:22, Doug Rabson wrote:
On 28 January 2016 at 15:03, Tomoaki AOKI wrote:
It's exa
I just realised an important point, does your usb disk have a UFS
root partition and your internal disk ZFS root partition?
If so then I know what the issue is, I'll have quick look now, so wait for
a diff5 to appear before testing.
On Saturday, 30 January 2016, Steven Hartland
wrote:
&g
. I built ZFS-disabled boot1.efi
> and it worked fine for USB memstick for me.
>
> *`make clean && make -DMK_ZFS=no` in sys/boot/efi/boot1 didn't disabled
>ZFS module, so I must edit the definition of *boot_modules[] in
>boot1.c. I'd have been missing somethi
On 28/01/2016 16:22, Doug Rabson wrote:
On 28 January 2016 at 15:03, Tomoaki AOKI wrote:
It's exactly the NO GOOD point. The disk where boot1 is read from
should be where loader.efi and loader.conf are first read.
I just wanted to note that gptzfsboot and zfsboot behaves this way. Boot1
look
On 24/01/2016 12:53, Tomoaki AOKI wrote:
Unfortunately, this (and its committed successor and original for UFS)
fails to boot in some situation, like below. OTOH, gptzfsboot (and
maybe gptboot for UFS, too) is OK.
When I select Disk1 from UEFI firmware, bootx64.efi in Disk1 EFI
partition is used
On 18/01/2016 21:57, Ed Maste wrote:
On 18 January 2016 at 15:26, Andrew Turner wrote:
the issue was we were caching reads from the first filesystem we looked
at. I've committed the fix in r294291 to force the code to re-read on
each filesystem it looks at.
Thanks Andrew - my QEMU boot failure
.
Any suggestions possible? Did I miss something?
Looks to me like fallout from the recent modularisation in r294060,
and/or ZFS support in r294068. Steven, any clue?
In QEMU boot1 failed for me with "Failed start image provided by UFS",
and I can confirm that it's fixed by reve
Bank 5 seems to be common to all the crashes, which may suggest you have
some dodgy ram or possibly the driving CPU's memory controller.
As the error says this is a Hardware issue.
One thing we've used in the past to narrow issues like this down is to
remove as much RAM as possible and to disa
Ive literally just got this working on 10.2 after working on the code
posted on the review which you can find here:
https://reviews.freebsd.org/D4104
If you're happy running current then the patch file I linked in my comment
should apply cleanly and just work.
If you want 10.x then there's quite
4k block size on the underlying device?
On 12/05/2015 00:14, Adrian Chadd wrote:
So I'm curious - why's it faster?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
On 18/04/2015 17:30, David Wolfskill wrote:
On Sat, Apr 18, 2015 at 06:34:59PM +0300, Konstantin Belousov wrote:
...
- printf("LE_STATUS: %d %d %lx\n", e, rp.status, rp.le_status);
+ printf("LE_STATUS: %d %d %jx\n", e, rp.status, rp.le_status);
return 0;
}
The j modifica
Verbose boot of the working OS version was what I was after, which
should provide details of what its detecting ;-)
Also a camcontrol identify of the cdrom from the working version may
also be useful
On 31/03/2015 09:54, Pietro Sammarco wrote:
Currently the cdrom drive and yes it works fine t
Is there anything connected to the second channel, if so what.
Was this working in a previous version and if so which one and what was
the verbose boot log from it?
On 30/03/2015 19:07, bsdml wrote:
Hello Kevin,
thanks for your clarification. Unfortunately I wasn't aware that the
T40 and *4
On 18/01/2015 02:35, Steve Kargl wrote:
On Sun, Jan 18, 2015 at 02:10:19AM +, Steven Hartland wrote:
On 18/01/2015 01:44, Steve Kargl wrote:
On Sun, Jan 18, 2015 at 01:40:09AM +, Steven Hartland wrote:
% svn revert -r 377300:377299 .
Just double checked and I can building r277307
On 18/01/2015 01:44, Steve Kargl wrote:
On Sun, Jan 18, 2015 at 01:40:09AM +, Steven Hartland wrote:
% svn revert -r 377300:377299 .
Just double checked and I can building r277307 without issue, build box
is running 10.1-RELEASE.
My head box is quite a bit slower and is still running
On 18/01/2015 00:22, Steve Kargl wrote:
On Sat, Jan 17, 2015 at 03:54:47PM -0800, Steve Kargl wrote:
% cd /usr/src
% svn update
Updating '.':
At revision 277307.
% make buildworld
===> cddl/usr.sbin/dtrace (all)
cc -O2 -pipe -march=core2 -I/usr/src/cddl/usr.sbin/dtrace/../../../sys/cddl
On 02/01/2015 01:23, Bjoern A. Zeeb wrote:
Hi,
you need the next line of source to see that while the union only defines
Simple[1], the comparison goes up to SG_LIST (or something) which is indeed
defined as 58. Cn someone fix this? This makes i386 compiles failing
currently.
/scratch/t
On 05/12/2014 13:07, Borja Marcos wrote:
On Dec 5, 2014, at 2:00 PM, Steven Hartland wrote:
On 04/09/2014 09:49, Borja Marcos wrote:
On Jun 30, 2014, at 8:02 PM, John Baldwin wrote:
I think these sound fine, but I've cc'd Xin Li (delphij@) who has worked with
folks at Emulex t
On 04/09/2014 09:49, Borja Marcos wrote:
On Jun 30, 2014, at 8:02 PM, John Baldwin wrote:
I think these sound fine, but I've cc'd Xin Li (delphij@) who has worked with
folks at Emulex to maintain this driver. He is probably the best person to
review this.
Hi,
Seems 10.1 is on the pipeline n
Fixed, sorry forgot asr wasn't in GENERIC, so missed it in testing.
On 22/11/2014 14:34, David Wolfskill wrote:
Running:
FreeBSD g1-253.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1434
r274790M/274790:1100047: Fri Nov 21 06:07:24 PST 2014
r...@g1-253.catwhisker.org:/common/S4/obj/us
Its usually something like stalled IO
On 16/11/2014 18:07, Steve Kargl wrote:
In init(8), one finds under DIAGNOSISTICS
"some processes would not die; ps axl advised."
So, just how is one to actually run 'ps axl advised' as
the message appears as init(8) is killing off the system?
_
On 05/11/2014 09:52, Andriy Gapon wrote:
On 04/11/2014 14:55, Steven Hartland wrote:
This is likely spikes in uma zones used by ARC.
The VM doesn't ever clean uma zones unless it hits a low memory condition, which
explains why your little script helps.
Check the output of vmstat
On 05/11/2014 06:15, Marcus Reid wrote:
On Tue, Nov 04, 2014 at 06:13:44PM +, Steven Hartland wrote:
On 04/11/2014 17:22, Allan Jude wrote:
snip...
Justin Gibbs and I were helping George from Voxer look at the same issue
they are having. They had ~169GB in inact, and only ~60GB being used
On 04/11/2014 17:57, Ben Perrault wrote:
snip...
I would also be interested in any additional debugging steps and would be
willing to help test in any way I can - as I've seen the behavior a few times
as well. As recently a Sunday evening, I caught a system running with ~44GB ARC
but ~117GB
On 04/11/2014 17:22, Allan Jude wrote:
snip...
Justin Gibbs and I were helping George from Voxer look at the same issue
they are having. They had ~169GB in inact, and only ~60GB being used for
ARC.
Are there any further debugging steps we can recommend to him to help
investigate this?
The vario
This is likely spikes in uma zones used by ARC.
The VM doesn't ever clean uma zones unless it hits a low memory
condition, which explains why your little script helps.
Check the output of vmstat -z to confirm.
On 04/11/2014 11:47, Dmitriy Makarov wrote:
Hi Current,
It seems like there is co
On 30/10/2014 14:40, Ed Maste wrote:
On 30 October 2014 10:26, Steven Hartland wrote:
Yer that's the process that was in my head, if debug symbols aren't
available when savecore runs we're going to need a way to update / rerun
when they are available, or even better give it th
On 30/10/2014 14:15, Ed Maste wrote:
On 30 October 2014 09:21, Steven Hartland wrote:
On 30/10/2014 12:10, Bjoern A. Zeeb wrote:
(a) symbol files are for developers. Developers are clever people, often
with custom systems, they know how to deal with them as they already do
whatever they
On 30/10/2014 12:10, Bjoern A. Zeeb wrote:
On 30 Oct 2014, at 09:47 , O'Connor, Daniel wrote:
On 30 Oct 2014, at 19:44, Steven Hartland wrote:
On 30/10/2014 08:24, O'Connor, Daniel wrote:
On 30 Oct 2014, at 13:23, Steven Hartland wrote:
Making things harder to manage vs savin
On 30/10/2014 09:47, O'Connor, Daniel wrote:
On 30 Oct 2014, at 19:44, Steven Hartland wrote:
On 30/10/2014 08:24, O'Connor, Daniel wrote:
On 30 Oct 2014, at 13:23, Steven Hartland wrote:
Making things harder to manage vs saving a little bit of space on the
root partition real
On 30/10/2014 08:24, O'Connor, Daniel wrote:
On 30 Oct 2014, at 13:23, Steven Hartland 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 be
On 30/10/2014 02:32, Steve Kargl wrote:
On Wed, Oct 29, 2014 at 03:15:50PM -0400, Ed Maste wrote:
On 29 October 2014 12:49, Steven Hartland wrote:
Hmm not sure I like this idea as it would make it more difficult to make a
copy / backup a kernel.
ATM when I want to copy a kernel for
Hmm not sure I like this idea as it would make it more difficult to make
a copy / backup a kernel.
ATM when I want to copy a kernel for debugging its a one liner,
splitting debug symbols off to /usr/lib would prevent this.
Is there not a way to allow separate install of the debug files but to
Unfortunately ZFS doesn't prevent new inflight writes until it
hits zfs_dirty_data_max, so while what your suggesting will
help, if the writes come in quick enough I would expect it to
still be able to out run the pageout.
- Original Message -
From: "Justin T. Gibbs"
To:
Cc: ; "Andriy
- Original Message -
From: "Steve Wills"
To: "Andriy Gapon"
Cc: ;
Sent: Friday, October 10, 2014 2:27 AM
Subject: Re: zfs hang
On Wed, Oct 08, 2014 at 08:55:26AM +0300, Andriy Gapon wrote:
On 08/10/2014 03:40, Steve Wills wrote:
> Hi,
>
> Not sure which thread this belongs to, b
- Original Message -
From: "Benjamin Kaduk"
To: "José Pérez Arauzo"
Cc: "FreeBSD Current"
Sent: Sunday, September 28, 2014 8:54 PM
Subject: Re: What do you use for kernel debugging?
On Sun, 28 Sep 2014, José Pérez Arauzo wrote:
Hello,
I am trying to track down a (deadlock?) issue
1 - 100 of 304 matches
Mail list logo
