all] Error code 71
sean
t do prior to single-user mode.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261912
sean
functional, which probably means
that a data structure has changed or something else that I haven't
started at in quite some time.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261936
sean
think I settled on the TERRAMASTER D5-300 USB3.1
I'll post back results when it arrives and I get done swearing and
cursing during the replacement.
sean
Performance, unsurprisingly is way better.
Some irritating XHCI initialization was noted on reboots:
https://bugs.freebsd.org/bugzilla
On 2/6/22 10:14, Sean Bruno wrote:
I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I
have here at the house to provide me with a nice little NAS at home. I'm
using 2x USB2 external disks as the mirror.
I noted that the two USB2 disks I'm using in
Things resume after this is emitted, but there is a substantial
(multiple minutes) pause here. I would assume that timeouts would fire
much quicker.
sean
On 2/6/22 10:52, Mehmet Erol Sanliturk wrote:
On Sun, Feb 6, 2022 at 8:15 PM Sean Bruno <mailto:sbr...@freebsd.org>> wrote:
I'm doing something "gross" with ZFS & Plex on a little Intel NUC
that I
have here at the house to provide me with a nice litt
data loss or anything, I just note from time to time
during large file transfers that the clanking/grinding sound of the
spinning rust on my desk completely stops, the encoding of the video
files stops (so its waiting for a read to complete) and its gets much
quieter in my office. :-)
sean
The 23rd. Sorry for the confusion - there were some scheduling conflicts
that caused this to be pushed back. Cheers. -sc
On Wed, Sep 16, 2020 at 1:05 AM Jakob Alvermark wrote:
> On 2020-09-15 16:12, FreeBSD Core Team Secretary wrote:
> > Based on the continuity of our last CORE Office Hours
Ok, if I run the bhyve commands manually, then I get a serial console.
So something is just borked with vm-bhyve and its use of tmux. Whew.
(Now I don't know *what*, but that's at least progress in my diagnosis!)
___
freebsd-current@freebsd.org
Ok, with debug=yes I see that it *is* running the VM -- but I have no
serial console? This may be operator error here, which is a big relief.
An update after I get back from the vet :). Thanks!
Sean.
___
freebsd-current@freebsd.org mailing list
https
>Could you test with larger memory setup - instead of 512M, 1-2G?
I tried multiple vcpus and 1G of RAM; it made no difference (to either my
attempting to boot the system I built, or the ISO; just confirmed the ISO with
1G).
Sean.
___
freebsd-curr
ith status 1
destroying network device tap0
stopped
Alan was trying to help me debug this yesterday, and I manually ran bhyve, but
had no errors, and it still didn't work.
Thanks,
Sean.
___
freebsd-current@freebsd.org mailin
, so that was
done by doing
vm create VM-TEST ; vm install VM-TEST 13.0.iso
Sean.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current
Just testing mailing lists. Delete.
sean
signature.asc
Description: OpenPGP digital signature
sFILESINS_cleanup.ksh" defined here
Is this something easily fixable? I'm unclear what is throwing a
warning here?
sean
signature.asc
Description: OpenPGP digital signature
ove of libssl.so.9 -> libssl.so.111 ?
https://svnweb.freebsd.org/changeset/base/339709
sean
signature.asc
Description: OpenPGP digital signature
> Found
>
> The package builders are not yet providing packages for 13.0-CURRENT.
>
> It's being worked on, but will take a little more time.
>
Portmgr has pushed out packages for 13, give 'em a spin and see what
happens.
sean
signature.asc
Description: OpenPGP digital signature
r case and ZFS
tends to go read-only in an error case. (over generalization here, but
its been my experience).
sean
signature.asc
Description: OpenPGP digital signature
On 9/23/18 3:57 PM, David P. Discher wrote:
> This is correct for a EFI+BIOS map. If the installer did this for an EFI
> only map, then that is a bug.
>
Is it supposed to "Detect" BIOS vs UEFI booting in the installer?
sean
> My 12-Alpha7 install I just did, with B
Does it make sense to add an IPv6 localhost (::1) to our setup scripts
for local_unbound? unbound is definitely listening on ::1 as well at
127.0.0.1 so things like "host -6" will work if we add it like this perhaps?
--- /usr/sbin/local-unbound-setup 2018-09-20 21:47:41.0 -0600
+++
I don't think this layout from the installer is correct, but I could be
wrong. Is there any reason to have a freebsd-boot in this layout
created by the installer when using UEFI?
% gpart show
=> 40 537234688 ada0 GPT (256G)
40 409600 1 efi (200M)
409640
( dsl-only.net went
> away in early 2018-Mar)
>
>
So, what should we even do here? It sort of looks like this entire
section should be purged or something.
There was a bit of error committing this section I guess.
sean
signature.asc
Description: OpenPGP digital signature
?
sean
signature.asc
Description: OpenPGP digital signature
On 9/2/18 6:17 AM, Alexander Leidinger wrote:
> Hi,
>
> -current at r338322 with manually applied r338372 (fix potential data
> corruption in iflib) and r338416 (re-compute arc size).
>
> What worries me a little bit about the validity of this report is the
> gdb 8.1.1 error when loading the
t is safe to store the IV in the
* top 32 bits of blk_fill, while leaving the bottom 32 bits of the fill count
* for the dnode code.
Sean
__
148 blocks (of 128k bytes), which supports your
statement.
With compression=on, it creates a 1 block file.
Sean.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
same master and HMAC keys.
(So, same issue. I don’t think encryption and deduplication should live
together,
so I would not have made that choice.)
Sean.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-c
ompatible or not it
is with it.
Sean.
___
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"
On 08/08/18 17:13, Warner Losh wrote:
>
>
> On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno <mailto:sbr...@freebsd.org>> wrote:
>
> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after
> multiuser.
>
> The FreeBSD cluster just acquire
lly (on vs
onifconsole), I see dmesg/kernel boot messages but never get a tty.
Its as though FreeBSD does *not* recognize the IPMI SOL port as the
console or something and I'm super confused. Any thoughts here?
sean
signature.asc
Description: OpenPGP digital signature
On 07/03/18 13:53, Yuri wrote:
> On 07/03/18 12:50, Lev Serebryakov wrote:
>> No, it isn't.
>>
>>
>> https://lists.freebsd.org/pipermail/freebsd-wireless/2016-October/007232.html
>>
>>
>> I don't know, why is it not mentioned in UPDATING:-(
>
>
> I may be mistaken about the interface
of FreeBSD SVN was in use on "June 1st" ?
sean
> On a guess, I tried reverting SVN r335303 but that didn't help.
>
> em0: port 0xf080-0xf09f mem
> 0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
> em0: attach_pre capping queues at 1
> em0: us
On 06/29/18 08:50, Mark Millard wrote:
> Side note:
>
> All I get for the lists that I normally look at is:
>
> Error 503 Backend fetch failed
>
> Backend status: Backend fetch failed
>
> Transaction ID: . . .
I think I fixed that about an hour ago. Try ag
> 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"
>
https://svnweb.freebsd.org/base/head/
?
sean
signature.asc
Description: OpenPGP digital signature
This seems to be a "iwm(4)" device. Try loading this driver in loader.conf.
https://www.freebsd.org/doc/handbook/network-wireless.html
sean
signature.asc
Description: OpenPGP digital signature
On 05/16/18 10:42, Sean Bruno wrote:
> https://reviews.freebsd.org/D15443
>
> The FreeBSD Foundation has collaborated with a few folks so that we can
> continue to process and update microcode on FreeBSD.
>
> This review represents the first step in updating our infras
this a spin
and report back if you see a different version of microcode being loaded
on the new package vs the old package.
sean
bcc emaste
signature.asc
Description: OpenPGP digital signature
n me this week. Anyone see what's going on?
sean
signature.asc
Description: OpenPGP digital signature
___
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"
On 01/15/18 11:14, Sean Bruno wrote:
> https://reviews.freebsd.org/D13921
>
> In order to better absorb updates as they appear, I'm proposing that we
> switch from the current model of processing the "microcode.dat" legacy
> file to consuming the pre-digested updat
n that you previously
received, but I'd like for folks to give it a spin before we commit yet
another update to this port.
sean
signature.asc
Description: OpenPGP digital signature
On 01/12/18 04:49, Rainer Hurling wrote:
> Am 12.01.2018 um 00:03 schrieb Sean Bruno:
>> https://reviews.freebsd.org/D13832 <--- test this update
>>
>> I'd like to get some feedback from AMD cpu users on this update. I've
>> restructured and undone a few things th
On 01/12/18 08:38, Mike Tancsa wrote:
> On 1/11/2018 6:03 PM, Sean Bruno wrote:
>> https://reviews.freebsd.org/D13832 <--- test this update
>>
>> I'd like to get some feedback from AMD cpu users on this update. I've
>> restructured and undone a few things th
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
After installing the port, grab
askqgroup_attach+0x230:orq
> %rax,-0x 58(%rbp,%xrx,8)
>
> I can provide more specific excerpts, but I need to focus on some
> other activities for a while.
>
> Peace,
> david
>
When you get a chance, let me know what em(4) device is in your machine
(pciconf -lvbc). I'
>
> Thoughts?
>
> [1]
> https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless
>
Maybe this is a "iflib" problem. em(4) and igb(4) are pretty different
now in head. Can you shove it into bugzilla with a test case
(copy/paste your email) and tag me on it?
sean
signature.asc
Description: OpenPGP digital signature
ignore
signature.asc
Description: OpenPGP digital signature
On 01/24/17 08:27, Olivier Cochard-Labbé wrote:
> On Tue, Jan 24, 2017 at 3:17 PM, Sean Bruno <sbr...@freebsd.org
> <mailto:sbr...@freebsd.org>> wrote:
>
>
>
> Did you increase the number of rx/tx rings to 8 and the number of
> descriptors to 4k i
On 01/23/17 23:31, Olivier Cochard-Labbé wrote:
> On Tue, Jan 24, 2017 at 2:40 AM, Sean Bruno <sbr...@freebsd.org
> <mailto:sbr...@freebsd.org>> wrote:
>
>
>
> Which set of configs from your test suite are you using for this?
> Specifically, what pa
>
> http://dev.bsdrp.net/apu2.r311848.BU_CPU_CLK_UNHALTED.svg
> http://dev.bsdrp.net/apu2.r311849.BU_CPU_CLK_UNHALTED.svg
>
> Thanks
>
>
Olivier:
Which set of configs from your test suite are you using for this?
Specifically, what packet size are you slamming across?
https://github.com/ocochard/netbenches/tree/master/pktgen.configs
sean
signature.asc
Description: OpenPGP digital signature
On 01/18/17 08:20, O. Hartmann wrote:
> On Wed, 18 Jan 2017 07:59:17 -0700
> Sean Bruno <sbr...@freebsd.org> wrote:
>
>> On 01/18/17 07:41, Sean Bruno wrote:
>>>
>>>
>>> On 01/18/17 00:34, O. Hartmann wrote:
>>>> On Thu, 5 Jan 20
On 01/18/17 07:41, Sean Bruno wrote:
>
>
> On 01/18/17 00:34, O. Hartmann wrote:
>> On Thu, 5 Jan 2017 20:17:56 -0700
>> Sean Bruno <sbr...@freebsd.org> wrote:
>>>
>> On a Fujitsu Celsius M740, the "em0" device gets stuck on heavy I/O. I c
On 01/18/17 00:34, O. Hartmann wrote:
> On Thu, 5 Jan 2017 20:17:56 -0700
> Sean Bruno <sbr...@freebsd.org> wrote:
>
>> tl;dr --> igbX devices will become emX devices
>>
>> We're about to commit an update to sys/dev/e1000 that will implement and
>>
dletd+0x37a
> #13 0x805460f5 at fork_exit+0x85
> #14 0x808f3b1e at fork_trampoline+0xe
>
> Peter
Thanks for the report. We're looking at this.
This is with an igb(4) interface or em(4)?
sean
signature.asc
Description: OpenPGP digital signature
ebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
>
> Has this been fixed? I bugs mee, too.
> I went back to r312235, too, which doesn't coredump.
>
> Regards,
>
> oh
>
For the time being, I'm suggesting people add EARLY_AP_START to their
kernel configs as is in GENERIC.
We are still debugging this.
sean
signature.asc
Description: OpenPGP digital signature
slots: TX 4/1024, RX 4/1024
> ...
>
> Any ideas?
>
> -Alan
>
Yeah, fighting with EARLY_AP_STARTUP with regards to initialization of
the interfaces. em(4) seems to be ok with my change today, but that
change makes igb(4) *very* angry.
I'm aware and trying to find a happy medium.
sean
signature.asc
Description: OpenPGP digital signature
gt; --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x4b194a, rsp =
> 0x7fffe478, rbp = 0x7fffe4d0 ---
> db>
>
>
>
>
>
Just to make sure, you're running GENERIC?
sean
signature.asc
Description: OpenPGP digital signature
> oh
If you have the time today or tomorrow. Can you please capture 'sysctl
dev.em.0' and post it here?
In addition, I would like to have this patch tested in your configuration:
https://people.freebsd.org/~sbruno/em_tx_limit.diff
Finally, if you have any loader.conf entries for hw.em, please post them
as well.
sean
signature.asc
Description: OpenPGP digital signature
On 01/11/17 15:44, Sean Bruno wrote:
>
>> My tunning are (same for both test):
>> hw.igb.rxd="2048" (it should be useless now)
>> hw.igb.txd="2048" (it should be useless now)
>> hw.em.rxd="2048"
>> hw.em.txd="
oo)
> hw.em.rx_process_limit="-1"
>
> dev.igb.2.fc=0
> dev.igb.3.fc=0
>
> I can generate profiling data for you: what kind of data do you want ?
Specifically, you may want to adjust these:
dev.em.0.iflib.override_nrxds: 0
dev.em.0.iflib.override_ntxds: 0
dev.
On 01/11/17 12:47, Olivier Cochard-Labbé wrote:
> On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno <sbr...@freebsd.org
> <mailto:sbr...@freebsd.org>> wrote:
>
>
>
> Olivier:
>
> Give this a quick try. This isn't the correct way to do this, but I
>
On 01/11/17 05:54, Matthew Macy wrote:
>
>
>
> On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labbé
> <oliv...@cochard.me> wrote
> > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno <sbr...@freebsd.org> wrote:
> >
> > >
> >
bsd-net@ megaphone for things
that I may have broken.
man page updates are coming up next. Please let us know if this
revision has made things better, worse or none-of-the above on whatever
Intel Gigabit NIC you happen to have lying around.
sean
On 01/05/17 20:17, Sean Bruno wrote:
> tl;dr --
ntly* when we dropped
this implementation, hence why we wanted to make 12-current a clean break.
sean
bcc matt
>
> On 06/01/2017 03:17, Sean Bruno wrote:
>> tl;dr --> igbX devices will become emX devices
>>
>> We're about to commit an update to sys/dev/e1000 that will i
legacy implementation that doesn't use
IFLIB for compatibility reasons.
A documentation and man page update will follow in the next few days
explaining how to work with the changed driver.
sean
bcc net@ current@ re@
signature.asc
Description: OpenPGP digital signature
On 10/06/16 10:58, Dimitry Andric wrote:
> On 06 Oct 2016, at 17:23, Sean Bruno <sbr...@freebsd.org> wrote:
>>
>> On 10/06/16 09:19, Sean Bruno wrote:
>>>
>>> On 10/06/16 09:00, Alan Somers wrote:
>>>> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno
On 10/06/16 09:19, Sean Bruno wrote:
>
>
> On 10/06/16 09:00, Alan Somers wrote:
>> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno <sbr...@freebsd.org> wrote:
>>>
>>>
>>> On 10/06/16 08:23, Slawa Olhovchenkov wrote:
>>>> On Thu, Oct 06
On 10/06/16 09:00, Alan Somers wrote:
> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno <sbr...@freebsd.org> wrote:
>>
>>
>> On 10/06/16 08:23, Slawa Olhovchenkov wrote:
>>> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote:
>>>
>>>>
On 10/06/16 08:23, Slawa Olhovchenkov wrote:
> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote:
>
>> I'm doing a large amount of change to ixgbe(4) in support of IFLIB
>> implementations and running into failures when trying to apply large
>> diffs. Thi
I'm doing a large amount of change to ixgbe(4) in support of IFLIB
implementations and running into failures when trying to apply large
diffs. This is causing phabricator reviews to be unuseable as well.
I've setup two trees to test this. The first tree is used to generate
the diff and the
client that
would do the right thing here?
sean
signature.asc
Description: OpenPGP digital signature
regions.
At this point in time this could be replaced with kqueue(2) EVFILT_PROC, but no
one has done that yet.
-sc
--
Sean Chittenden
s...@chittenden.org
> On Jun 22, 2016, at 07:26 , Maxim Sobolev <sobo...@freebsd.org> wrote:
>
> Konstantin,
>
> Not if you do sem_unlink
same thing myself: it means that updates can be
more targeted.
Sean.
___
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"
Please create/update/point-me-at a bugzilla issue with all this information.
sean
On 12/22/15 08:37, Alan Somers wrote:
> I'm experiencing the same problem, and I can confirm that Alexander's
> workaround fixes it. Here is some more information:
>
> * I see the exact same pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/24/15 04:03, O. Hartmann wrote:
> Building kernel on r292688 fails with the error shown below:
>
This appears to be breakage due to missing "options INET6" in the
kernconf being used.
I've repaired this at svn revision 292697.
> [...] cc
~~~
> /usr/src/sys/modules/ix/../../dev/ixgbe/ix_txrx.c:814:14: error:
> use of undeclared identifier 'ip6' ipproto = ip6->ip6_nxt; ^ ---
> all_subdir_isci ---
>
Is this just GENERIC? Or custom kernconf?
sean
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQF8BAEBCgBm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/19/15 15:42, Warner Losh wrote:
>
>
> On Thu, Nov 19, 2015 at 11:12 AM, John Baldwin <j...@freebsd.org
> <mailto:j...@freebsd.org>> wrote:
>
> On Thursday, November 19, 2015 09:13:06 AM Sean Bruno wrote:
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/19/15 10:12, John Baldwin wrote:
> On Thursday, November 19, 2015 09:13:06 AM Sean Bruno wrote:
>> I thought I fixed this a year or two ago, but now a "make clean"
>> in sys/modules seems to leave bus_if.h
nt: ${SRCS}
${LINT} ${LINTKERNFLAGS} ${CFLAGS:M-[DILU]*} ${.ALLSRC:M*.c}
sean
bcc -- imp@
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQF8BAEBCgBmBQJWTgMbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RD
the better.
sean
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQF8BAEBCgBmBQJWK7G1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5k6JwH/0d2sg+hg6e+MfkE4FTMZHjw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/02/15 00:47, O. Hartmann wrote:
> On Thu, 01 Oct 2015 15:39:11 + Eric Joyner <ricer...@gmail.com>
> wrote:
>
>> Oliver,
>>
>> did you try Sean's suggestion?
>>
>> - Eric
>>
his.
>
> is that observation of any help?
>
> Regards,
>
> oh
>
>>
>> On Mon, Sep 21, 2015 at 1:58 AM O. Hartmann
>> <ohart...@zedat.fu-berlin.de> wrote:
>>
>>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
>>> <sbr...@freebsd.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/26/15 14:12, Larry Rosenman wrote:
> Was playing with pmcstats -S instructions -T, and got the following
> when I tried to ctrl/c out.
>
>
> oldtbh.lerctr.org dumped core - see /var/crash/vmcore.3
>
> Wed Aug 26 16:05:16 CDT 2015
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/18/15 10:20, Eric Joyner wrote:
> He has an i210 -- he would want to revert e1000_i210.[ch], too.
>
> Sorry for the thrash Sean -- it sounds like it would be a good idea
> for you should revert this patch, and Jeff and I
>
> r287762 broke the system
Before I revert this changeset *again* can you test revert r287762 from
if_igb.c, e1000_82575.c and e1000_82575.h *only*
That narrows down the change quite a bit.
sean
___
freebsd-current@freebsd.org mailing list
On 09/12/15 13:45, Mark R V Murray wrote:
>
>> On 8 Sep 2015, at 19:02, Mark R V Murray <ma...@freebsd.org> wrote:
>>
>>
>>> On 8 Sep 2015, at 17:22, Sean Bruno <sbr...@freebsd.org> wrote:
>>>
>>>
>>>>>>
>&g
ort the failure to attach, and I am not seeing it as I don’t
> think I built a kernel that had that particular failure. I am having the
> “failure after 10-15 minutes” problem; this is on an em0 device.
>
> M
>
Hrm, that's odd. That sounds like a hole where interrupts aren't being
r
t ; ifconfig em0 up
>
> :-)
>
> I’m running CURRENT, r287538. This last worked of me a month or so
> ago at my previous build.
>
> M
>
Just so I'm clear, the original problem reported was a failure to
attach (you were among several folks reporting breakage).
On 08/29/15 00:38, Joel Dahl wrote:
> On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote:
>>
>>
>> On 08/25/15 12:10, Joel Dahl wrote:
>>>>> Seems to work. However, I cannot reproduce the user panic in the first
>>>>> place. What's the
On 08/25/15 12:10, Joel Dahl wrote:
Seems to work. However, I cannot reproduce the user panic in the first
place. What's the scenario that seems to work here? NFS seems happy
with/without the patch so I'm not confident in anything we are doing her
e.
I see several patches here. Which
-if_hw_tsomaxsegsize = EM_TSO_SEG_SIZE;
Seems to work. However, I cannot reproduce the user panic in the first
place. What's the scenario that seems to work here? NFS seems happy
with/without the patch so I'm not confident in anything we are doing her
e.
sean
-BEGIN PGP SIGNATURE-
Version
I'm going to guess that you're using an em net driver, since that is the
only one that sets if_hw_tsomax IP_MAXPACKET (65535) from what I can see.
Sean, EM_TSO_SIZE is defined as (65535 + sizeof(struct ether_vlan_header)),
which makes it IP_MAXPACKET. The value of if_hw_tsomax must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I added a couple of DDB_HOOKS to em(4) recently and they definitely used
to work. :-)
KDB: enter: Break to debugger
[ thread pid 11 tid 16 ]
Stopped at kdb_alt_break_internal+0x197: movq$0,kdb_why
db help
ahd_dumpahd_in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/15/15 13:24, Sean Bruno wrote:
I added a couple of DDB_HOOKS to em(4) recently and they definitely
used to work. :-)
KDB: enter: Break to debugger [ thread pid 11 tid 16 ] Stopped
at kdb_alt_break_internal+0x197: movq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201127
ex(4) is an old Intel ethernet driver that isn't being actively
maintained. I propose purging it from -current for 11.0 release things.
sean
p.s. will post to -net as well
-BEGIN PGP
it doesn't seem to be causing observable harm -- it just
seemed a bit odd to me.
Peace, david
Bapt fixed this in head, so you should not see this anymore.
sean
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQF8BAEBCgBmBQJVcF56XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
-deterministic test case. Three instances of qemu
core dumped and the system did *not* panic.
However, this appears to be interfering with signal handling and
reaping. Applications seems to stall out and become
unkillable/unreapable. I have to reboot the system via panic/reset.
sean
last pid: 41009
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/22/15 10:53, Konstantin Belousov wrote:
On Sun, Feb 22, 2015 at 10:46:53AM -0800, Sean Bruno wrote:
Hmm ... looks unrelated to signals (maybe). This looks like a
common ZFS deadlock that is yet undiagnosed. I do not have a
show alllocks
1 - 100 of 496 matches
Mail list logo
