https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
Martin Birgmeier changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #13 from Martin Birgmeier ---
With -p7 the machine would simply reboot, but less frequently than before the
fix of bug #236121.
-- Martin
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #12 from Mark Johnston ---
(In reply to Martin Birgmeier from comment #11)
And to be clear, you were seeing panics on -p7 too?
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #11 from Martin Birgmeier ---
Before I was running -p7:
[0]# strings
/z/backup/rsync/mizar/ROOT/.zfs/snapshot/backup.2019-08-04.12:27:28/boot/kernel/kernel
| tail | grep FreeBSD
@(#)FreeBSD 12.0-RELEASE-p7 #8 r349733M: Thu Jul
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #10 from Mark Johnston ---
So, you still see problems after recompiling the kernel modules against -p9
sources? What version were you running before the update?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #9 from Martin Birgmeier ---
I am backup up the machines using rsync and zfs snapshots which I keep on a
monthly basis. This allows me to look at older messages...
[0]# bzgrep -c 'Reject scan trigger since one is already pendin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #8 from Martin Birgmeier ---
I am not sure the following is of relevance, but /var/log/messages yesterday
was spammed like this:
Aug 15 23:00:00 mizar newsyslog[10909]: logfile turned over due to size>1000K
Aug 15 23:00:00 miza
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #7 from Martin Birgmeier ---
To be added: unresponsive, with fan at full blast (so most likely more than 1
of the 4 cores fully loaded).
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #6 from Martin Birgmeier ---
Tried to let the machines run overnight (to recompile KDE applications
19.08.0). Machine 1 crashed at around midnight. In the morning found a blank
screen and complete unresponsiveness.
Firefox was
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #5 from Martin Birgmeier ---
I'll try it next time.
Currently I am recompiling all those ports with kernel modules.
-- Martin
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #4 from Mark Johnston ---
s/changes/hangs/
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #3 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #2 from Martin Birgmeier ---
I just had another of these deadlocks:
- Running firefox
- Opening a context menu
- Firefox does not respond anymore
- Klicked on upper right corner to close it
- KDE says that window does not close,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
Martin Birgmeier changed:
What|Removed |Added
Summary|deadlock|deadlock since FreeBSD 12.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
--- Comment #1 from Martin Birgmeier ---
Btw in the second case involving VBoxHeadless:
- Tried to interrupt the VBoxHeadless process (kill -INT)
- 100% CPU load fell to 0%
- Process did not get killed, instead pstree reported "STOP"
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239822
Bug ID: 239822
Summary: deadlock
Product: Base System
Version: 12.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Pr
16 matches
Mail list logo
