https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206836
schm...@ze.tum.de changed:
What|Removed |Added
CC||schm...@ze.tum.de
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206836
Bug ID: 206836
Summary: Random Lockups of partition /var
Product: Base System
Version: 10.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206829
NGie Cooper changed:
What|Removed |Added
CC||ma...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205359
--- Comment #3 from j...@transactionware.com ---
(In reply to Marius Strobl from comment #2)
Thanks for the update Marius. I will import into our tree and test.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206829
Bug ID: 206829
Summary: /usr/share/dtrace/toolkit/hotcpu perl
Product: Base System
Version: 10.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #5 from Arrigo Marchiori ---
FWIW, the problem is _not_ reproducible on my 10-RELEASE x86-64 machine:
# uname -a
FreeBSD myhost 10.1-RELEASE-p26 FreeBSD 10.1-RELEASE-p26 #0: Wed Jan 13
20:59:29 UTC 2016
r...@amd64-builder.d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #4 from Arrigo Marchiori ---
Running e2fsck on the md(4)-backed file, after reboot:
# e2fsck /dev/md0s1
e2fsck 1.42.13 (17-May-2015)
/dev/md0s1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #3 from Arrigo Marchiori ---
The panic is also reproducible when writing to a md(4) instead of a USB drive.
The stack trace is analogous.
(kgdb) bt
#0 doadump (textdump=1) at pcpu.h:250
#1 0xc0aed3ae in kern_reboot (howto=260
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206649
Alexander Mishurov changed:
What|Removed |Added
Attachment #166152|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #2 from Arrigo Marchiori ---
Created attachment 166397
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166397&action=edit
/var/crash/core.txt from the second panic
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #1 from Arrigo Marchiori ---
Created attachment 166396
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166396&action=edit
/var/crash/core.txt from the first panic
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
Bug ID: 206820
Summary: [ext2fs] Panic when writing to ext3fs mounted as
ext2fs
Product: Base System
Version: 9.3-STABLE
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206762
--- Comment #4 from Jean-Sébastien Pédron ---
Yes, the check looks wrong. Some time ago, I verified in later versions of
Linux and it was still there. I didn't look again recently if it was fixed. I
had no time to report this yet.
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721
Andrey V. Elsukov changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|a...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205834
Andrey V. Elsukov changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
--
Yo
16 matches
Mail list logo
