[Bug 187015] [panic] make_dev_credv: bad si_name (error=17, si_name=agpgart)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187015 --- Comment #16 from Tatsuki Makino --- By the way, how many PCs are affected by this bug in the whole world? My 855GME will no longer boot. orz -- 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 231897] kernel panic when xorg starts with legacy nvidia-drivers
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231897 Bug ID: 231897 Summary: kernel panic when xorg starts with legacy nvidia-drivers Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: core.dumped...@gmail.com I has video card NVIDIA® GeForce® 8600GT installed. After upgrading of an operating system from version 11.1-RELEASE to version 11.2-RELEASE and updating of all installed packages I have faced a problem. When Xorg starting there is an kernel panic in 100% of cases. Also i has the laptop with video card NVIDIA 240M installed. After upgrading of an system to version 11.2-RELEASE on the laptop there was a similar problem. When xorg starts this process utilizes 100% of resources of the CPU. At this time the Xorg doesn't loading. Process without reset it is impossible to kill. -- 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 231882] multiple toolchain issues with statically linked binaries
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231882 --- Comment #1 from Ed Maste --- Another llvm PR that may be related: https://bugs.llvm.org/show_bug.cgi?id=38074 -- 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 231881] boot0cfg can not configure "version 1.0" boot0 due to bug in gpart_mbr bootcode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231881 --- Comment #1 from Lev A. Serebryakov --- https://reviews.freebsd.org/D17386 -- 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 231881] boot0cfg can not configure "version 1.0" boot0 due to bug in gpart_mbr bootcode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231881 Lev A. Serebryakov changed: What|Removed |Added Summary|boot0cfg can not configutr |boot0cfg can not configure |"version 1.0" boot0 due to |"version 1.0" boot0 due to |bug in gpart_mbr bootcode |bug in gpart_mbr bootcode -- 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 231887] kldxref reports 'Bad address' for mips64el modules
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231887 --- Comment #1 from Ed Maste --- I see no ef_mips.c in usr.sbin/kldxref; it appears kldxref is just unable to process relocations on mips. -- 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 231887] kldxref reports 'Bad address' for mips64el modules
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231887 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2317 ||90 -- 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 231887] kldxref reports 'Bad address' for mips64el modules
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231887 Bug ID: 231887 Summary: kldxref reports 'Bad address' for mips64el modules Product: Base System Version: CURRENT Hardware: mips OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ema...@freebsd.org CC: sbr...@freebsd.org After the objcopy fix in r339083 (PR 231790) I can kldload modules on mips64el, but kldxref when it runs reports: root@:~ # kldxref -v /boot/kernel/ /boot/kernel/accf_data.ko kldxref: ef_obj_seg_read_string(/boot/kernel/accf_data.ko): bad offset (948200f2) kldxref: error while reading /boot/kernel/accf_data.ko: Bad address /boot/kernel/accf_dns.ko kldxref: ef_obj_seg_read_string(/boot/kernel/accf_dns.ko): bad offset (8c8201e0) kldxref: error while reading /boot/kernel/accf_dns.ko: Bad address /boot/kernel/accf_http.ko kldxref: ef_obj_seg_read_string(/boot/kernel/accf_http.ko): bad offset (3e8) kldxref: error while reading /boot/kernel/accf_http.ko: Bad address /boot/kernel/acl_nfs4.ko kldxref: ef_obj_seg_read_string(/boot/kernel/acl_nfs4.ko): bad offset (8c8300042402) ... root@:~ # readelf -x set_modmetadata_set /boot/kernel/accf_data.ko Hex dump of section 'set_modmetadata_set': 0x root@:~ # readelf -r /boot/kernel/accf_data.ko | grep -A 8 set_modmeta Relocation section with addend (.relaset_modmetadata_set): r_offset r_info r_type st_value st_name + r_addend 00030012 R_MIPS_64 .data + 18 Type2: R_MIPS_NONE Type3: R_MIPS_NONE 0008 00030012 R_MIPS_64 .data + 30 Type2: R_MIPS_NONE Type3: R_MIPS_NONE root@:~ # readelf -S /boot/kernel/accf_data.ko There are 19 section headers, starting at offset 0x880: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align ... [ 6] .data PROGBITS 00e0 00a0 WA 0 0 16 -- 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 231810] [build] release always fails with "mkimg: partition 2: No space left on device"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #11 from l...@ratnaling.org --- Created attachment 197721 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197721&action=edit Screenshot -- 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 231810] [build] release always fails with "mkimg: partition 2: No space left on device"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #10 from l...@ratnaling.org --- That created a 219G file on /tmp which is on a 10G partition -- 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"
PLAYERS GRADE CLASSIC GEAR PRICED TO SELL!
[[HEADLINE]] [[PERMALINK_FULL_LINK]] TITLE OF YOUR EMAIL The content of your email goes here. You can drag and drop blocks of text, images or other content elements to add them to your message. Customize the font and the colors. Add links to track clicks. This is a second paragraph you can customize as your please. If you have stored contact properties with your contacts, you can include personalization variables such as first name, last name in your message content. [[DELIVERY_INFO]] [[POSTAL_ADDRESS]] ___ 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 231060] pkill.1: clarify that patterns are EREs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231060 Guangyuan Yang changed: What|Removed |Added CC||y...@freebsd.org Assignee|b...@freebsd.org|y...@freebsd.org -- 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 231296] smartpqi - kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #4 from rai...@ultra-secure.de --- BTW: I've been running memtest86 v7.5 (the free edition of the commercial version that does UEFI) in this for 8h and it showed no 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 231882] multiple toolchain issues with statically linked binaries
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231882 Bug ID: 231882 Summary: multiple toolchain issues with statically linked binaries Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ema...@freebsd.org Blocks: 231027 Attempting to make use of some WIP with statically linked binaries (i386 / amd64) has uncovered a number of tool chain issues which will be tracked in this PR. * elfcopy/strip removes ifunc, probably other relocations Found by kib@, with userland ifunc stripped statically linked binaries segfault. strip removed the .rela.plt section header; file content at the expected relocation site has been zeroed. See LLVM PR 37538 for an initial part of this issue - lld is writing 0 in sh_info and sh_link on the .rela.plt section. https://bugs.llvm.org/show_bug.cgi?id=37538 This likely also affects static PIE. 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 Ed Maste changed: What|Removed |Added Depends on||231882 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231882 [Bug 231882] multiple toolchain issues with statically linked binaries -- 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 231881] boot0cfg can not configutr "version 1.0" boot0 due to bug in gpart_mbr bootcode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231881 Lev A. Serebryakov changed: What|Removed |Added Keywords||regression -- 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 231881] boot0cfg can not configutr "version 1.0" boot0 due to bug in gpart_mbr bootcode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231881
Bug ID: 231881
Summary: boot0cfg can not configutr "version 1.0" boot0 due to
bug in gpart_mbr bootcode
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: l...@freebsd.org
boot0/boot0sio have disk serial number compiled-in by default. It is named
"version 2" boot block by boot0cfg(8) and this format places 4 byte Disk Serial
Number where "version 1" boot block contains options.
Support for disk serial number in boot0/boot0sio is optional, and could be
turned off to save some bytes, needed for other options.
boot0cfg(8) properly supports old placement of boot block options, properly
detect boot block without disk serial number support and properly prepare
options for it.
Problem is, boot0cfg(8) uses "gpart bootcode" command to wriet boot block with
new options back to disk.
And gmart_mbr always try to save disk serial number, which kills options if
boot block is "version 1":
static int
g_part_mbr_bootcode(struct g_part_table *basetable, struct g_part_parms *gpp)
{
struct g_part_mbr_table *table;
uint32_t dsn;
if (gpp->gpp_codesize != MBRSIZE)
return (ENODEV);
table = (struct g_part_mbr_table *)basetable;
dsn = *(uint32_t *)(table->mbr + DOSDSNOFF);
bcopy(gpp->gpp_codeptr, table->mbr, DOSPARTOFF);
if (dsn != 0)
*(uint32_t *)(table->mbr + DOSDSNOFF) = dsn;
return (0);
}
Sometimes, it leads to complete bogus options written which kill boot0/boot0sio
(it have invalid slice mask, for example, and is unable to boot at all) and
sometimes it simply didn't give user ability to change boot0/boot0sio options.
--
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 231880] pid provider doesn't know about ifuncs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231880 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org -- 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 231880] pid provider doesn't know about ifuncs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231880 Bug ID: 231880 Summary: pid provider doesn't know about ifuncs Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ma...@freebsd.org We're starting to use ifuncs in libc. libproc needs to be taught how to resolve symbols of type STT_GNU_IFUNC. -- 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 231610] loader menu shown even with autoboot_delay=-1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231610 Kyle Evans changed: What|Removed |Added Attachment #197710|0 |1 is obsolete|| Status|New |In Progress Assignee|b...@freebsd.org|kev...@freebsd.org --- Comment #3 from Kyle Evans --- Created attachment 197716 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197716&action=edit Lift autoboot_delay processing up a level Revised patch- shouldn't affect this, but previous iteration broke the autoboot_delay="NO" case... invoking menu.autoboot with a nil delay will now do nothing, leaving the caller to come up with a reasonable default delay. This lines up with how I envision third-party usage (in, say, local.lua) to want to do things if they're invoking autoboot manually. -- 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 231610] loader menu shown even with autoboot_delay=-1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231610 --- Comment #2 from Kyle Evans --- Created attachment 197710 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197710&action=edit Lift autoboot_delay handling up a level Hi, Apologies for the delay. How does the attached patch look for you? Thanks, Kyle Evans -- 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 231810] [build] release always fails with "mkimg: partition 2: No space left on device"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #9 from Matthias Apitz --- (In reply to leeb from comment #6) Lee, could you please do a test for double check: modify the script /usr/src/release/amd64/make-memstick.sh and insert size values in the line for mkfs like this; change the line: makefs -B little ... to: makefs -B little -M 50331648b -m 50331648b ... Be prepared for the target memstick.img needs ~25 GByte -- 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 231873] Early usages of bzeor/memset/&c broke when switching to ifunc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231873 Mark Linimon changed: What|Removed |Added Keywords||patch -- 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 129036] [ipfw] 'ipfw fwd' does not change outgoing interface name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129036 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Assignee|b...@freebsd.org|n...@freebsd.org -- 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 231873] Early usages of bzeor/memset/&c broke when switching to ifunc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231873 Bug ID: 231873 Summary: Early usages of bzeor/memset/&c broke when switching to ifunc Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: roy...@freebsd.org Created attachment 197705 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197705&action=edit Initial patch The usages of bzero in hammer_time_xen and hammer_time_xen_legacy produce a triple-fault after the switch to use ifuncs for optimisation. -- 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"
