https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
--- Comment #5 from Conrad Meyer ---
I guess another solution would be to changes 'optional ccr' to 'optional ccr
cxgbe' in conf/files t4_crypto.c line, but that just silently "succeeds" when
ccr is set and cxgbe is not set, when failure se
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
--- Comment #4 from Conrad Meyer ---
Kernel config includes 'device ccr' but not 'device cxgbe', which is
probably invalid.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
Conrad Meyer changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #3 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031
--- Comment #3 from Kurt Jaeger ---
https://lists.freebsd.org/pipermail/freebsd-current/2019-May/073538.html
has a patch, which needs to be tested.
Unfortunatly, after upgrading to r348454, it's more difficult to reproduce.
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157724
--- Comment #8 from Eir Nym ---
The issue was lost in time.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
--- Comment #2 from Eir Nym ---
scc.conf and src-env.conf will be attached if needed
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
--- Comment #1 from Eir Nym ---
Created attachment 204745
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=204745&action=edit
kernel config
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238265
Bug ID: 238265
Summary: Unable to link kernel: sybmol not found
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #7 from Kyle Evans ---
(In reply to Scott Bennett from comment #6)
I'm afraid the output you get from loader is likely nonsensical (based on your
description in comment 0 and that it's way too early in loader) -- IMO, it will
b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #6 from Scott Bennett ---
Kyle, I will try, but no promises. I really do not want this system down for
very long when I have to reboot it, and it was already down about a week over
this issue once. It may have to wait until th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #5 from Kyle Evans ---
(In reply to Scott Bennett from comment #4)
Hi,
Can you snag loader_4th from a recent -CURRENT snapshot and try that as your
/boot/loader with other boot block bits updated please?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #4 from Scott Bennett ---
I can't easily confirm this at this point, but my recollection is that this
UPDATING entry was not present as of r347183. In any case, I do remember
looking carefully at /boot/loader and /boot/zfsloade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #3 from Scott Bennett ---
>From its description, r346549 doesn't appear to have anything to do with this
bug.
Yes, I am going to have to reboot soon anyway due to the kernel's memory
mismanagement bug(s) (as of r345498, at least
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238258
--- Comment #4 from Kubilay Kocak ---
What version (uname -a) of FreeBSD?
Is this a regresion after an upgrade?
If so, what exact version was the upgrade from?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238258
--- Comment #3 from c...@soi.spb.ru ---
Sorry for the incomplete description.
New loader (unified with zfsloader) can't find zfs pool on an unpartitioned
disk.
How to repeat:
1. Connect fresh zeroed-out disk to a freebsd machine.
2. Create
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238258
--- Comment #2 from c...@soi.spb.ru ---
Sorry once more. Old zfsloader, of course.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031
--- Comment #2 from Kurt Jaeger ---
The vnassert can be found in sys/kern/vfs_subr.c, _vdrop(), line 2982
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031
Kurt Jaeger changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238258
Kubilay Kocak changed:
What|Removed |Added
CC||kev...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
--- Comment #2 from Kubilay Kocak ---
See Also base r336537
20180720:
zfsloader's functionality has now been folded into loader.
zfsloader is no longer necesasary once you've updated your
boot blocks. For a transiti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa, regression
Sev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238258
Bug ID: 238258
Summary: loader cant't find pool by guid
Product: Base System
Version: 11.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable11+
Assignee|b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238257
Bug ID: 238257
Summary: zfsloader: 11.2-STABLE r345498 to r347183 update
leaves unbootable system
Product: Base System
Version: 11.2-STABLE
Hardware: amd64
24 matches
Mail list logo
