[Bug 191651] 10.0-RELEASE-p14 Fatal trap 30: reserved (unknown) fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191651 tio.mad...@hotmail.com changed: What|Removed |Added Status|New |Closed

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Konstantin Belousov k...@freebsd.org changed: What|Removed |Added Component|threads |kern

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 --- Comment #13 from Eygene Ryabinkin r...@freebsd.org --- Perhaps the more proper thing will be to say .max_ioctl= (DRM_ARRAY_SIZE(i915_ioctls) - 1) since this will preserve the semantics of the max_ioctl name that should keep the

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 --- Comment #15 from commit-h...@freebsd.org --- A commit references this bug: Author: rea Date: Fri Nov 28 12:15:00 UTC 2014 New revision: 275209 URL: https://svnweb.freebsd.org/changeset/base/275209 Log: DRM2: fix off-by-one overflow

[Bug 195349] CAM status: Command timeout since upgrade to 10.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349 --- Comment #3 from Ganael LAPLANCHE marty...@freebsd.org --- Same on this morning, my NAS lost 3 disks (ada1, ada2, ada3) and even panic'ed ! See attached messages and core.txt. -- You are receiving this mail because: You are the

[Bug 195349] CAM status: Command timeout since upgrade to 10.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349 --- Comment #4 from Ganael LAPLANCHE marty...@freebsd.org --- Created attachment 149957 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149957action=edit /var/log/messages before panic -- You are receiving this mail because: You

[Bug 195349] CAM status: Command timeout since upgrade to 10.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349 --- Comment #5 from Ganael LAPLANCHE marty...@freebsd.org --- Created attachment 149958 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149958action=edit /var/crash/core.txt.5 after panic -- You are receiving this mail because:

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Eygene Ryabinkin r...@freebsd.org changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Eygene Ryabinkin r...@freebsd.org changed: What|Removed |Added Status|New |In Progress

[Bug 195165] Kernel with drm panics, when xorg tries to load new drm-modules

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195165 Eygene Ryabinkin r...@freebsd.org changed: What|Removed |Added CC|

[Bug 195165] Kernel with drm panics, when xorg tries to load new drm-modules

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195165 --- Comment #2 from Eygene Ryabinkin r...@freebsd.org --- Also, a backtrace from the panic (kgdb /boot/$DRM-ENABLED-KERNEL/kernel.debug /var/crash/vmcore.1 and bt from inside kgdb) will be great here. -- You are receiving this mail

[Bug 195119] aacraid 3.2.5 may loose da drives

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195119 Eygene Ryabinkin r...@freebsd.org changed: What|Removed |Added CC|

[Bug 195479] New: mpt(4) on VMware ESXi causes enormous number of SCSI busy errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195479 Bug ID: 195479 Summary: mpt(4) on VMware ESXi causes enormous number of SCSI busy errors Product: Base System Version: 10.1-RELEASE Hardware: amd64

[Bug 195483] New: /usr/bin/ld: //lib/libm.so.5: invalid DSO for symbol `cos@@FBSD_1.0' definition

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195483 Bug ID: 195483 Summary: /usr/bin/ld: //lib/libm.so.5: invalid DSO for symbol `cos@@FBSD_1.0' definition Product: Base System Version: 10.1-STABLE Hardware: i386

[Bug 195484] New: freebsd-update(8) fails to update 9.2-RELEASE to 10.1-RELEASE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195484 Bug ID: 195484 Summary: freebsd-update(8) fails to update 9.2-RELEASE to 10.1-RELEASE Product: Base System Version: 9.2-RELEASE Hardware: amd64 OS:

[Bug 195485] New: [ufs] mksnap_ffs(8) cannot create snapshot with journaled soft updates enabled

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195485 Bug ID: 195485 Summary: [ufs] mksnap_ffs(8) cannot create snapshot with journaled soft updates enabled Product: Base System Version: 10.1-RELEASE Hardware: Any

[Bug 171120] [patch] bsd.gcc.mk: GCC incorrectly identified in base when CLANG_IS_CC and WITHOUT_GCC are set

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171120 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 195491] New: Keyboard stop working after r274861 when kbdmux is disabled in kernel

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195491 Bug ID: 195491 Summary: Keyboard stop working after r274861 when kbdmux is disabled in kernel Product: Base System Version: 10.1-STABLE Hardware: Any

[Bug 195165] Kernel with drm panics, when xorg tries to load new drm-modules

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195165 --- Comment #3 from Mikhail T. m...@aldan.algebra.com --- Thanks, Eugene, for the prompt response, but I've already figured, that I am much happier with the xf86-video-ati-ums driver for my card -- it has no GL hardware and the newest

[Bug 195436] patch utility, line number overflows checks

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195436 --- Comment #3 from Pedro F. Giffuni p...@freebsd.org --- If the changes come from OpenBSD, it would be good to update the CVS revision information as the tags are used for reference in future updates. -- You are receiving this mail