[Bug 240710] Fatal trap 12: page fault while in kernel mode : swi4: clock (0)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240710 Martin Filla changed: What|Removed |Added Resolution|--- |Overcome By Events Status|New |Closed --- Comment #2 from Martin Filla --- FreeBSD 12.0 is unsupported. In next version is without this issue. -- 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 232691] i915 (?): Fatal trap 12: page fault while in kernel mode (supervisor read data, page not present, i915_gem_* functions)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232691 Martin Filla changed: What|Removed |Added Resolution|--- |Overcome By Events Status|Open|Closed --- Comment #6 from Martin Filla --- FreeBSD 12.0 is unsupported. In next version is without this issue. -- 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 252160] smbfs is used, at shutdown or restart coredump
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252160 Bug ID: 252160 Summary: smbfs is used, at shutdown or restart coredump Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: t-matub...@miracle.ocn.ne.jp uname -a 13.0-CURRENT FreeBSD 13.0-CURRENT #11 9e4440ca5ba-c273667(master)-dirty: Sat Dec 26 05:49:32 JST 2020 That smbfs is used in autofs, at shutdown or a reboot coredump. samba -fstype=smbfs,-f=644,-d=755,-u=1001,-g=1001 ://XXX@X/xxx It'll be probably Device busy, and, umount Can, I think like the cause. A module of a possibility with the problem is written. kldstat (Something related) smbfs.ko libiconv.ko libmchain.ko coredump , So, how to take it log isn't understood. Could you try whether you reappear? It'll be 100 % by my environment. Thank you. -- 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 226112] awk(1) man page unclear about field separator, FS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226112 Guangyuan Yang changed: What|Removed |Added Assignee|y...@freebsd.org |b...@freebsd.org --- Comment #4 from Guangyuan Yang --- Returning to pool. -- 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 251868] Add tcgetwinsize() and tcsetwinsize() to termios.h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251868 --- Comment #15 from SOUMENDRA GANGULY <0.gang...@gmail.com> --- In https://reviews.freebsd.org/D27650, I had written: "OTOH, while it's not a big deal anymore, I wonder why some of the other platforms such as NetBSD have chosen to not put the winsize materials under _NETBSD_SOURCE." Here lies the answer to the question: https://mail-index.netbsd.org/tech-userlevel/2017/10/21/msg010899.html Basically, Christos Zoulas cleverly avoided the namespace contamination by letting sys/ttycom.h only make visible struct winsize when _NETBSD_SOURCE is not defined: https://github.com/NetBSD/src/blob/trunk/sys/sys/ttycom.h My OCD is now satisfied. -- 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 252163] r368739/a095390344fb1795c1b118a2f84da8f6a7f254ab causes a panic stating 'Fatal trap 12: page fault while in kernel mode'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252163 Bug ID: 252163 Summary: r368739/a095390344fb1795c1b118a2f84da8f6a7f254ab causes a panic stating 'Fatal trap 12: page fault while in kernel mode' Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: vidwer+fbsdb...@gmail.com Created attachment 220951 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220951&action=edit text file with backtrace details gathered by kgdb This change, see this PRs summary, will crash a machine after inserting wireless USB (if_rsu, RTL8191S, vendor/device ID 0x0bda:0x8172) hardware. r368738 / de66c99a works fine, as does hardware using if_rtwn_usb (RTL8188EU, vendor/device ID 0x0bda:0x8179). -- 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 252165] mii bus media status race condition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 Bug ID: 252165 Summary: mii bus media status race condition Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: ali.abdal...@suse.com I'm using if_ure on a USB-C dock station. I'm having the following random issue: Dec 25 12:20:10 Fryzen495 kernel: ue0: link state changed to UP Dec 25 12:20:10 Fryzen495 kernel: ue0: link state changed to DOWN Dec 25 12:20:10 Fryzen495 kernel: ue0: link state changed to UP Dec 25 12:20:58 Fryzen495 kernel: ue0: link state changed to DOWN Dec 25 12:21:01 Fryzen495 kernel: ue0: link state changed to UP Dec 25 12:21:07 Fryzen495 dhclient[20388]: New IP Address (ue0): 192.168.1.145 Dec 25 12:21:07 Fryzen495 dhclient[21191]: New Subnet Mask (ue0): 255.255.255.0 Dec 25 12:21:07 Fryzen495 dhclient[22099]: New Broadcast Address (ue0): 192.168.1.255 Dec 25 12:21:07 Fryzen495 dhclient[22651]: New Routers (ue0): 192.168.1.254 After digging into the code, I've discovered that the issue is caused by the following race condition: In mii/mii.c, the function miibus_linkchg(device_t dev) reads mii->mii_media_status and sets the link state accordingly. static void miibus_linkchg(device_t dev) { ... if (mii->mii_media_status & IFM_AVALID) { if (mii->mii_media_status & IFM_ACTIVE) link_state = LINK_STATE_UP; else link_state = LINK_STATE_DOWN; ... } On the other hand, the function mii_pollstat running on another thread, polls the media status, which is using rgephy.c code in my case. (via PHY_SERVICE call) static void rgephy_status(struct mii_softc *sc) { mii->mii_media_status = IFM_AVALID; mii->mii_media_active = IFM_ETHER; /* HERE IS THE ISSUE The read in miibus_linkchg is randomly seeing mii->mii_media_status as IFM_AVALID, but it does not yet have the IFM_ACTIVE flag set, which makes it trigger a link state change... */ if (rgephy_linkup(sc) != 0) mii->mii_media_status |= IFM_ACTIVE; ... This is an issue in all miibus modules, rgephy.c, truephy.c, mlphy.c, etc... Please note that also in mii_pollstat, mii->mii_media_status is initialized to 0 (not sure why), and that also races with miibus_linkchg. There are many ways to fix it, locally I'm not resetting mii->mii_media_status until rgephy_linkup(sc) returns link down. -- 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 231072] Mtree calculates checksum wrong when verifying a specification against a directory.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231072 Kyle Evans changed: What|Removed |Added CC||kev...@freebsd.org --- Comment #2 from Kyle Evans --- Created attachment 220962 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220962&action=edit git(1) diff against base This seems to improve the situation -- 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 219829] "systat -if 1" Peak has wrong display
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219829 --- Comment #9 from o...@j.email.ne.jp --- Do you plan merging to 11/stable, too? The bug is fixed in 12/stable and current; we can mark this fixed. -- 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 231380] 12-ALPHA5 Deadlock panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231380 Mark Johnston changed: What|Removed |Added Status|Open|Closed Resolution|--- |Overcome By Events --- Comment #8 from Mark Johnston --- (In reply to Jeremy Faulkner from comment #7) Ok, thanks for the update. I'll close for now, please re-open if the panic occurs again and we'll try to investigate more promptly. -- 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 252183] 12.2 files to boot after upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252183 Bug ID: 252183 Summary: 12.2 files to boot after upgrade Product: Base System Version: 12.2-RELEASE Hardware: i386 OS: Any Status: New Keywords: crash, install, loader Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: fine...@yahoo.com I tried to made a binary upgrade using freebsd-upgrade from freebsd 11 to the latest 12.2 on i386 machine with old 586 processor. The system failed to boot with illegal instruction error (see attached picture). Upgrading from sources on freebsd 11 produces buildable kernel but unworkable system. Cross compiling i386 system on amd64 produces 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 252183] 12.2 fails to boot after upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252183 G changed: What|Removed |Added Summary|12.2 files to boot after|12.2 fails to boot after |upgrade |upgrade -- 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 252183] 12.2 fails to boot after upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252183 --- Comment #1 from G --- Created attachment 220974 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220974&action=edit Screenshot of the crash -- 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"