kern/166937: [panic] Random and frequent kernel crash, reason unknown

>Number: 166937 >Category: kern >Synopsis: [panic] Random and frequent kernel crash, reason unknown >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Clas

Re: kern/166920: dtrace(1) kills itself with SIGUSR1

Synopsis: dtrace(1) kills itself with SIGUSR1 Responsible-Changed-From-To: freebsd-bugs->gnn Responsible-Changed-By: emaste Responsible-Changed-When: Sat Apr 14 00:56:58 UTC 2012 Responsible-Changed-Why: Is this fixed by r234234? http://www.freebsd.org/cgi/query-pr.cgi?pr=166920

bin/166933: [PATCH] clean up iscontrol(8) and iscsi(4) post-r234233

>Number: 166933 >Category: bin >Synopsis: [PATCH] clean up iscontrol(8) and iscsi(4) post-r234233 >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Clas

kern/166929: dtrace -c doesn't seem to like it if the subcommand doesn't call exit()

>Number: 166929 >Category: kern >Synopsis: dtrace -c doesn't seem to like it if the subcommand doesn't >call exit() >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >D

kern/166928: fbt provider does not destroy probes when module unloaded

>Number: 166928 >Category: kern >Synopsis: fbt provider does not destroy probes when module unloaded >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >C

misc/166927: Kernel panics if you unload a kld module that provides probes with an active D script

>Number: 166927 >Category: misc >Synopsis: Kernel panics if you unload a kld module that provides probes >with an active D script >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywo

misc/166921: Use after free in dtrace(1) error handling

>Number: 166921 >Category: misc >Synopsis: Use after free in dtrace(1) error handling >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

kern/166920: dtrace(1) kills itself with SIGUSR1

>Number: 166920 >Category: kern >Synopsis: dtrace(1) kills itself with SIGUSR1 >Confidential: no >Severity: serious >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Subm

misc/166926: Individual probes cannot be destroyed, only providers

>Number: 166926 >Category: misc >Synopsis: Individual probes cannot be destroyed, only providers >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class

misc/166925: lockstat provider only works in files that #include "opt_kdtrace.h"

>Number: 166925 >Category: misc >Synopsis: lockstat provider only works in files that #include >"opt_kdtrace.h" >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-

kern/166924: deferred DTrace probes never match if executable linked with -E

>Number: 166924 >Category: kern >Synopsis: deferred DTrace probes never match if executable linked with -E >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Requir

kern/166923: dtrace: kernel trap 12 with interrupts disabled (not a panic!?)

>Number: 166923 >Category: kern >Synopsis: dtrace: kernel trap 12 with interrupts disabled (not a panic!?) >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Requir

misc/166922: Wildcarded dtrace probe names not always working

>Number: 166922 >Category: misc >Synopsis: Wildcarded dtrace probe names not always working >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

kern/166919: If dtrace(1) crashes while attached to a process, the process is left in a weird state

>Number: 166919 >Category: kern >Synopsis: If dtrace(1) crashes while attached to a process, the process >is left in a weird state >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keyw

kern/166918: USDT probes not cleaned up when process exits uncleanly

>Number: 166918 >Category: kern >Synopsis: USDT probes not cleaned up when process exits uncleanly >Confidential: no >Severity: non-critical >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >

Re: kern/130998: [dtrace] DTrace stops tracing because of struct thread

Synopsis: [dtrace] DTrace stops tracing because of struct thread State-Changed-From-To: open->closed State-Changed-By: gnn State-Changed-When: Fri Apr 13 20:56:12 UTC 2012 State-Changed-Why: All the issues relating to these scripts are either now fixed in the FreeBSD implementation of DTrace (HEA

Re: kern/165541: [dtrace] [panic] Kernel panic when dtracing userland

Synopsis: [dtrace] [panic] Kernel panic when dtracing userland State-Changed-From-To: open->closed State-Changed-By: gnn State-Changed-When: Fri Apr 13 20:54:08 UTC 2012 State-Changed-Why: Could not reproduce on HEAD as of 13 April 2012 Responsible-Changed-From-To: freebsd-bugs->gnn Responsibl

Re: kern/159659: [dtrace] PID provider dies with: Trying sleep, but thread marked as sleeping prohibited

Synopsis: [dtrace] PID provider dies with: Trying sleep, but thread marked as sleeping prohibited State-Changed-From-To: open->closed State-Changed-By: gnn State-Changed-When: Fri Apr 13 20:34:01 UTC 2012 State-Changed-Why: This is no longer a problem as of HEAD 13 April 2012. Could not reproduc

Re: bin/160275: [patch] dtrace(1): dtrace -lv causes "unknown function" warnings

Synopsis: [patch] dtrace(1): dtrace -lv causes "unknown function" warnings Responsible-Changed-From-To: freebsd-bugs->rstone Responsible-Changed-By: gnn Responsible-Changed-When: Fri Apr 13 20:29:01 UTC 2012 Responsible-Changed-Why: Ryan, if this is no longer a bug, and it seems that this is not

Re: kern/164724: [dtrace] [patch] Signal bug in Dtrace

Synopsis: [dtrace] [patch] Signal bug in Dtrace Responsible-Changed-From-To: freebsd-bugs->gnn Responsible-Changed-By: gnn Responsible-Changed-When: Fri Apr 13 20:27:28 UTC 2012 Responsible-Changed-Why: Take this bug and try the fix. http://www.freebsd.org/cgi/query-pr.cgi?pr=164724

Re: bin/158431: [dtrace] crash in dt_proc_lookup when attaching to PID, assert(dpr != NULL)

Synopsis: [dtrace] crash in dt_proc_lookup when attaching to PID, assert(dpr != NULL) State-Changed-From-To: open->patched State-Changed-By: gnn State-Changed-When: Fri Apr 13 20:24:35 UTC 2012 State-Changed-Why: The latest fixes to user tracing in DTrace will cure this problem. Of course, using

Re: kern/166909: [alc] NIC alc(4) does not support 1000baseTX

Old Synopsis: NIC alc (4) does not support 1000baseTX New Synopsis: [alc] NIC alc(4) does not support 1000baseTX Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Apr 13 16:45:55 UTC 2012 Responsible-Changed-Why: Over to maintaine

kern/166912: Panic after converting Softupdates to journaled softupdates

>Number: 166912 >Category: kern >Synopsis: Panic after converting Softupdates to journaled softupdates >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >C

Re: kern/166866: [build] [cy] cy(4) driver breaks kernel build in 8.3

excuse my manners. thank you very much for the report. Eugene wrote: The following reply was made to PR kern/166866; it has been noted by GNATS. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsub

Re: kern/166866: [build] [cy] cy(4) driver breaks kernel build in 8.3

a "revision" that breaks not only software but hardware... is CERTAINLY not a subrevision (ie, 8.3) but a major revision (ie, 9.x) I've used "advanced TTY" and myself see 0 no null ZERO improvement. I'd rather have the drivers fixed before they implement. You know some drivers not compiling a

misc/166909: NIC alc (4) does not support 1000baseTX

>Number: 166909 >Category: misc >Synopsis: NIC alc (4) does not support 1000baseTX >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bu

Re: misc/166906: xz strange bug

Synopsis: xz strange bug State-Changed-From-To: open->closed State-Changed-By: fluffy State-Changed-When: Fri Apr 13 13:21:46 UTC 2012 State-Changed-Why: Submitter's request via IM, wrong test case http://www.freebsd.org/cgi/query-pr.cgi?pr=166906 ___

misc/166906: xz strange bug

>Number: 166906 >Category: misc >Synopsis: xz strange bug >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: curr

Re: kern/166866: [build] [cy] cy(4) driver breaks kernel build in 8.3

The following reply was made to PR kern/166866; it has been noted by GNATS. From: Eugene To: bug-follo...@freebsd.org, eugene...@mail.ru Cc: Subject: Re: kern/166866: [build] [cy] cy(4) driver breaks kernel build in 8.3 Date: Fri, 13 Apr 2012 12:42:13 +0400 In fact, this problem is described