[Bug 254398] rc.conf.5: Remove documentation of variables which have been removed from the system
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254398 Bug ID: 254398 Summary: rc.conf.5: Remove documentation of variables which have been removed from the system Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: tobias.rehb...@web.de CC: d...@freebsd.org Created attachment 223416 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223416&action=edit Patch for rc.conf.5 Remove documentation of variables which have been removed from the system. rc_parallel_start, removed in f61831d2e8bd44b6568b00d538e738c25190bb96 ipv6_ipfilter_rules, removed in e2ad10e84792e8dcfb0e03a9b5cb19cd3d93ddf8 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254398] rc.conf.5: Remove documentation of variables which have been removed from the system
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254398 --- Comment #1 from tobias.rehb...@web.de --- Links to the relevant commits: https://cgit.freebsd.org/src/commit/?id=e2ad10e84792e8dcfb0e03a9b5cb19cd3d93ddf8 https://cgit.freebsd.org/src/commit/?id=f61831d2e8bd44b6568b00d538e738c25190bb96 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Nathan Whitehorn changed: What|Removed |Added CC||nwhiteh...@freebsd.org --- Comment #1 from Nathan Whitehorn --- You should not include the EFI partition in the PARTITIONS variable in general, but that won't cause this issue. Does the installer actually fail, resulting in a non-bootable system? Or do you just see this message in the output? Any more detail about your install script? What are you untarring? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Ryan Moeller changed: What|Removed |Added CC||freql...@freebsd.org --- Comment #2 from Ryan Moeller --- This affects me as well. The install completely fails. I'm even doing EFI installs: PARTITIONS="zvol/pool/dataset/vol gpt" I've used this same script quite a lot and it has only started to fail recently. I noticed yesterday and started looking into it a bit before I got pulled into something else. The tarball that fails to be extracted is base.txz (it's the one that contains ./boot/efi). The output on the console shows this as well: DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[] DEBUG: UNAME_S=[FreeBSD] UNAME_P=[amd64] UNAME_R=[14.0-CURRENT] DEBUG: common.subr: Successfully loaded. DEBUG: f_debug_init: ARGV=[mount] GETOPTS_STDARGS=[dD:] DEBUG: f_debug_init: debug=[1] debugFile=[] DEBUG: Running installation step: mount DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[] DEBUG: UNAME_S=[FreeBSD] UNAME_P=[amd64] UNAME_R=[14.0-CURRENT] DEBUG: common.subr: Successfully loaded. DEBUG: f_debug_init: ARGV=[checksum] GETOPTS_STDARGS=[dD:] DEBUG: f_debug_init: debug=[1] debugFile=[] DEBUG: Running installation step: checksum DEBUG: Extracting /storage/bhyve/14.0-CURRENT/a771bf748f9/kernel.txz DEBUG: Extracting /storage/bhyve/14.0-CURRENT/a771bf748f9/kernel-dbg.txz DEBUG: Extracting /storage/bhyve/14.0-CURRENT/a771bf748f9/base.txz ERROR: bsdinstall script failed At this point the script exits, leaving the filesystems mounted even: /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep2 on /mnt (ufs, local, journaled soft-updates) /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep1 on /mnt/boot/efi (msdosfs, local) devfs on /mnt/dev (devfs) # cat /tmp/bsdinstall-tmp-fstab /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep1 /mnt/boot/efi msdosfs rw 2 2 /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep2 /mntufs rw 1 1 # cat /tmp/bsdinstall_etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep1 /boot/efi msdosfs rw 2 2 /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep2 / ufs rw 1 1 /dev/zvol/storage/bhyve/14.0-CURRENT/a771bf748f9/templatep3 none swapsw 0 0 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #3 from Nathan Whitehorn --- Well, I found the issue and there's even a nice comment in the relevant code that an older, smarter version of me put in in 2018 describing exactly why this is going to break: # Unpack distributions bsdinstall checksum for set in $DISTRIBUTIONS; do f_dprintf "Extracting $BSDINSTALL_DISTDIR/$set" # XXX: this will fail if any mountpoints are FAT, due to inability to # set ctime/mtime on the root of FAT partitions. tar has no option to # ignore this. We probably need to switch back to distextract here # to properly support EFI. tar -xf "$BSDINSTALL_DISTDIR/$set" -C $BSDINSTALL_CHROOT done I'll try to get a patch in today. Apologies for the breakage, and thanks for the report. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395
--- Comment #4 from Andrey Fesenko ---
(In reply to Nathan Whitehorn from comment #1)
Installer fail, if set PARTITIONS="$DISKSLICE GPT { auto freebsd-ufs / }" fail
too
https://64.media.tumblr.com/2c95d2ddeed5cc2bd7ffb8fc68f34436/f8abb8c6d81ea645-e4/s1280x1920/6c4753c8bfdd3af75f597371189c4dcb1cbf0880.png
build packer
"qemu_binary": "/usr/libexec/qemu-kvm",
"-bios",
"/usr/share/edk2.git/ovmf-x64/OVMF-pure-efi.fd"
Check virtualbox builder BETA4 installer ok. RC2 fail, similar error
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #5 from Andrey Fesenko --- (In reply to Nathan Whitehorn from comment #3) If possible, it is also worth mentioning in the release notes that you no longer need to specify the efi and boot partitions, but is it possible to make the efi partition smaller, since 260M is a lot for a virtual machine, where there will be only 1 system -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 229357] bootpool is not imported after boot (separated bootpool/zroot due to zroot encryption)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229357 Allan Jude changed: What|Removed |Added CC||allanj...@freebsd.org --- Comment #3 from Allan Jude --- (In reply to Ryan Moeller from comment #2) So the workaround is: zpool import bootpool zpool set cachefile=/etc/zfs/zpool.cache bootpool And now your bootpool will be on the list to auto-import at boot. Of course, if you use updated UEFI code, you don't need a separate bootpool anymore: You can convert to a single pool that supports boot environments now: https://ftfl.ca/blog/2016-09-17-zfs-fde-one-pool-conversion.html -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 252236] atp(4): Need EVDEV support for modern input stack
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252236 --- Comment #33 from Greg V --- (In reply to Vladimir Kondratyev from comment #32) Three mistakes in the hidbus one: - forgotten sc->sc_dev = dev - evdev_set_methods needs dev (not sc) as second argument, because that's what hidbus_intr_start expects - missing hidbus_set_intr(dev, bcm5974_intr, sc) With these fixed, WSP9 works. But it continues sending events on the hms device as well, so we get double movement :D (btw when we have both bcm and wsp supporting this device, there's weird stuff like wsp loading instead of bcm on resume from S3 sleep) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238733] kvm disk i/o extremely slow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238733 --- Comment #2 from rai...@ultra-secure.de --- Still the same with FreeBSD 13.0RC2. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 Maarten changed: What|Removed |Added CC||maarten.rootsa...@vaph.be --- Comment #5 from Maarten --- Reproduced on HP DL380 Gen10 with LSI 9300-8e(FW:16.00.12.00) connected to HPE D3610(FW:5.04) enclosure with 6 HDDs Same issue only "last" HDD in enclosure has 2 paths An other server with the same setup has no issues, only difference: - it currently has only 2 HDDs(same series) - the HPE D3610 enclosure has an older firmware 3.64 instead of 5.04 -- FreeBSD 12.2-RELEASE-p3 (TrueNAS-12.0-U2.1) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251726] LOR between in6_multi_sx and if_lagg sx
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251726 --- Comment #3 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=ee231b27fff9d6950bf36a9800c02f6474b53139 commit ee231b27fff9d6950bf36a9800c02f6474b53139 Author: Alex Richardson AuthorDate: 2021-03-19 18:35:04 + Commit: Alex Richardson CommitDate: 2021-03-19 18:35:06 + Also skip sys/net/if_lagg_test:witness on non-i386 The LOR also happens on amd64 and other architectures. Ideally we would fix this. However, in order to get Jenkins green again to catch real regressions, we should skip this test for now. PR: 251726 Reviewed By:lwhsu Differential Revision: https://reviews.freebsd.org/D29341 tests/sys/net/if_lagg_test.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Andrey Fesenko changed: What|Removed |Added Blocks||231027 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027 [Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027 Andrey Fesenko changed: What|Removed |Added Depends on||254395 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 [Bug 254395] bsdinstall: fail script install after BETA3 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Nathan Whitehorn changed: What|Removed |Added Severity|Affects Only Me |Affects Some People CC||i...@freebsd.org Priority|--- |Normal --- Comment #6 from Nathan Whitehorn --- Thanks for the suggestion about the documentation -- I've updated the man page. The core problem here is that our tar can't extract archives to FAT32 with default options, since it treats inability to set modification time as a fatal error and FAT32 doesn't let you do that on the root directory. As such, any file in the release tarballs can't be extracted to FAT32. For interactive installations, the bsdinstall distextract tool, a CURSES-y frontend to libarchive, solves this by ignoring ctime/mtime errors. Some extra commentary on solutions, so it can be in one place. Possibilities are: 1. We drop /boot/efi from mtree. That will result in it not existing in base.txz, solving this issue, but will result in it not being in mtree. It will also leave in place an identical bug that will break scripted installation on bare-metal POWER8 and POWER9 systems, although that is a tier-2 platform. 2. We add an option to tar to ignore failure in setting ctime/mtime, like the interactive installer uses. This has the difficulty that the patch is hacky and would have to go through upstream. 3. We go back to using distextract for scripted installations as well as interactive ones, reverting d7640440fb644fde697f62fdff0b55aa3a4d5ef7. This fixes this issue but will result in installation failures for scripted installs without a controlling tty. (It will also add nice progress bars to scripted installs). 4. We do --exclude /boot/efi when running tar, then mkdir -p it by hand afterward. This is incredibly hacky and otherwise essentially functionally equivalent to #1. Like #1, it will fix this issue and has no obvious functional downside, but leaves scripted installs bare-metal POWER8 and POWER9 broken. 5. We patch the file system driver to (pretend to) allow setting times on the mount point. I don't want to do this, since I don't want to solve this in the kernel at RC3 and I don't like it pretending to do things it can't do. Of these, 1, 3, and 4 are quite easy to implement, but all have some downside. My temptation is to do 4 for 13.0, since it will definitely work but is just lame, then either do #2 or a variant on #3 where distextract notices there is no tty and doesn't try to set up a dialog as a longer-term fix in HEAD. Any thoughts? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #7 from Warner Losh --- #4 sounds good for 13.0. Of the hacks, it's the most localized and least hacky, imho. I'd prefer #5, honestly, longer term but I've not thought through all the implictions. We should loop in cem@ since he's been touching that code most recently. Or delphij@ as he has too... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #8 from Ryan Moeller --- Would it be possible to defer mounting the ESP until after the tarballs have been extracted? We don't actually have anything in /boot/efi in the base archive. My understanding is that it's just there to ensure the mountpoint exists. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250682] certctl(8)'s list command just says "GlobalSign" for five of the GlobalSign certificates
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250682 Michael Osipov changed: What|Removed |Added CC||michael.osi...@siemens.com --- Comment #2 from Michael Osipov --- (In reply to Kyle Evans from comment #1) I agree on the wrong with the special case. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #9 from Nathan Whitehorn --- (In reply to Ryan Moeller from comment #8) We could delay it, but it's harder and less-localized than the other solutions. It also completely breaks PowerPC and other systems with analagous but non-ESP boot partions. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #10 from Warner Losh --- (In reply to Ryan Moeller from comment #8) Oh! I like this idea better, I think, but I don't know how hard it is to do. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254395] bsdinstall: fail script install after BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #11 from Nathan Whitehorn --- (In reply to Warner Losh from comment #10) It's pretty tricky, since it touches code in a lot of places, has to be conditional on platform, and runs a risk of breaking interactive installs just because it is pretty invasive. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254410] newfs creates .snap with world readable permissions 0777
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254410 Bug ID: 254410 Summary: newfs creates .snap with world readable permissions 0777 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-b...@freebsd.org Reporter: clmnjus...@gmail.com CC: al.baj8...@gmail.com, b...@freebsd.org, heliocent...@gmail.com, rsimmo...@gmail.com, s...@freebsd.org +++ This bug was initially created as a clone of Bug #192227 +++ According to the dump(8) man page, the .snap directory should have 0770 permissions, but after running newfs and mounting a UFS file system, the .snap directory permissions are 0777. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254419] Fatal trap 12: page fault while in kernel mode, nginx + sendfile on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254419
Bug ID: 254419
Summary: Fatal trap 12: page fault while in kernel mode, nginx
+ sendfile on
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: viap...@gmail.com
FreeBSD-13.0-RC3, git rev 8f731a397ad4dc7b17622c0e69ac045f4a7b9d5b
nginx + sendfile on = kernel panic. With sendfile = off - working fine.
Fatal trap 12: page fault while in kernel mode
cpuid = 19; apic id = 13
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x8095fa46
stack pointer = 0x28:0xfe01533dd1a0
frame pointer = 0x28:0xfe01533dd1b0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 3395 (nginx)
trap number = 12
panic: page fault
cpuid = 19
time = 1616197293
KDB: stack backtrace:
#0 0x80687015 at kdb_backtrace+0x65
#1 0x8063a051 at vpanic+0x181
#2 0x80639ec3 at panic+0x43
#3 0x809830d7 at trap_fatal+0x387
#4 0x8098312f at trap_pfault+0x4f
#5 0x8098278d at trap+0x27d
#6 0x8095b938 at calltrap+0x8
#7 0x8095f957 at in_cksum_skip+0x77
#8 0x8079dc1d at in_delayed_cksum+0x3d
#9 0x80823d03 at pf_test+0x1403
#10 0x8083ac6f at pf_check_out+0x1f
#11 0x80770de7 at pfil_run_hooks+0x97
#12 0x8079d3f1 at ip_output+0xb61
#13 0x807b44e4 at tcp_output+0x1b04
#14 0x807ca379 at tcp_usr_send+0x229
#15 0x80637f6a at vn_sendfile+0x197a
#16 0x80638967 at sendfile+0x127
#17 0x809839dc at amd64_syscall+0x10c
Uptime: 1m0s
Dumping 1632 out of 32637 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) list *0x8095fa46
0x8095fa46 is in in_cksumdata
(/usr/src/sys/amd64/amd64/in_cksum.c:113).
108 if ((offset = 3 & (long) lw) != 0) {
109 const u_int32_t *masks = in_masks + (offset << 2);
110 lw = (u_int32_t *) (((long) lw) - offset);
111 sum = *lw++ & masks[len >= 3 ? 3 : len];
112 len -= 4 - offset;
113 if (len <= 0) {
114 REDUCE32;
115 return sum;
116 }
117 }
(kgdb)
(kgdb) bt
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0x80639c46 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:486
#3 0x8063a0c0 in vpanic (fmt=, ap=) at
/usr/src/sys/kern/kern_shutdown.c:919
#4 0x80639ec3 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:843
#5 0x809830d7 in trap_fatal (frame=0xfe01533dd0e0, eva=0) at
/usr/src/sys/amd64/amd64/trap.c:915
#6 0x8098312f in trap_pfault (frame=frame@entry=0xfe01533dd0e0,
usermode=false, signo=, signo@entry=0x0, ucode=,
ucode@entry=0x0)
at /usr/src/sys/amd64/amd64/trap.c:732
#7 0x8098278d in trap (frame=0xfe01533dd0e0) at
/usr/src/sys/amd64/amd64/trap.c:398
#8
#9 0x8095fa46 in in_cksumdata (buf=,
len=len@entry=1140) at /usr/src/sys/amd64/amd64/in_cksum.c:113
#10 0x8095f957 in in_cksum_skip (m=0xf80608d32300,
m@entry=0xf804e6cab200, len=1140, skip=, skip@entry=20) at
/usr/src/sys/amd64/amd64/in_cksum.c:224
#11 0x8079dc1d in in_delayed_cksum (m=0xf804e6cab200) at
/usr/src/sys/netinet/ip_output.c:1083
#12 0x80823d03 in pf_route (m=0xfe01533dd4f8, r=0xf8000d90cc00,
dir=0, oifp=0xf8000d86c000, s=, pd=0xfe01533dd288,
inp=0xf8062603a988)
at /usr/src/sys/netpfil/pf/pf.c:5558
#13 pf_test (dir=, dir@entry=2, pflags=,
ifp=, m0=, m0@entry=0xfe01533dd4f8,
inp=)
at /usr/src/sys/netpfil/pf/pf.c:6269
#14 0x8083ac6f in pf_check_out (m=0xfe01533dd4f8, ifp=0x0,
flags=1140, ruleset=, inp=0x0) at
/usr/src/sys/netpfil/pf/pf_ioctl.c:4516
#15 0x80770de7 in pfil_run_hooks (head=, p=...,
ifp=0xf8000d86c000, flags=flags@entry=131072,
inp=inp@entry=0xf8062603a988) at /usr/src/sys/net/pfil.c:187
#16 0x8079d3f1 in ip_output_pfil (mp=0xfe01533dd4f8,
ifp=0xf8000d86c000, flags=0, inp=0xf8062603a988,
dst=0xf8062603ab30, fibnum=,
error=) at /usr/src/sys/netinet/ip_output.c:130
#17 ip_output (m=m@entry=0xf804e6cab200, opt=, ro=, flags=0, imo=imo@entry=0x0, inp=) at
/usr/src/s
[Bug 254373] T440p fails to boot while docked with 13.0-RC2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254373 Kubilay Kocak changed: What|Removed |Added Keywords||needs-qa, regression Status|New |Open CC||ko...@freebsd.org Severity|Affects Only Me |Affects Some People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 254373] T440p fails to boot while docked with 13.0-RC2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254373 --- Comment #9 from Kubilay Kocak --- Created attachment 223437 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223437&action=edit Panic screenshot and backtrace -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
