Re: Deprecating ISA sound cards

2022-03-18 Thread Cy Schubert
In message <20220319022405.ga29...@lonesome.com>, Mark Linimon writes:
> Anyone objecting to this, be careful, I might ship a pile of such
> things to you from the depths of the closets :-)

<<=1


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  https://FreeBSD.org
NTP:   Web:  https://nwtime.org

The need of the many outweighs the greed of the few.





Re: DTrace Brokenness [Solved]

2022-03-18 Thread Cy Schubert
A full clean build resolved the problem. It was likely some incompatible 
CTF or possibly some other patch that touched DTrace that left my obj tree 
in an inconsistent state.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  https://FreeBSD.org
NTP:   Web:  https://nwtime.org

The need of the many outweighs the greed of the few.


In message <20220318234704.6c14...@slippy.cwsent.com>, Cy Schubert writes:
> It's been a while (~ 4-6 months) since I've last used dtrace. Needing to 
> use it again today scripts that worked before fail to.
>
> A first example:
>
> cwfw# cat dt10.d
> #!/usr/sbin/dtrace -s
>
> fbt::ipf_check:entry {
>   parintf("%x\n", (void) arg[1]);
> }
>
> cwfw# 
>
> Results in this error:
>
> cwfw# ./dt10.d 
> dtrace: failed to compile script ./dt10.d: "/usr/lib/dtrace/psinfo.d", line 
> 1: cannot translate from "struct thread *" to "lwpsinfo_t *"
> cwfw# 
>
> Another example,
>
> slippy# cat dtrace.d 
> #!/usr/sbin/dtrace -s
>
> fbt::uma_reclaim:entry {
>   printf("in uma_reclaim\n");
> }
> slippy# 
>
> Results in the same error:
>
> slippy# ./dtrace.d 
> dtrace: failed to compile script ./dtrace.d: "/usr/lib/dtrace/psinfo.d", 
> line 1: cannot translate from "struct thread *" to "lwpsinfo_t *"
> slippy# 
>
>
> A variation of the second example,
>
> slippy# cat dtrace.sh 
> #!/bin/sh -
> dtrace -n 'fbt::uma_reclaim:entry { printf("in uma_reclaim\n"); }'
> slippy# 
>
> Results in two errors, the first being that the -n option results in an 
> invalid probe specified and the second being the struct thread * error.
>
> slippy# ./dtrace.sh 
> dtrace: invalid probe specifier fbt::uma_reclaim:entry { printf("in 
> uma_reclaim\n"); }: "/usr/lib/dtrace/psinfo.d", line 1: cannot translate 
> from "struct thread *" to "lwpsinfo_t *"
> slippy# 
>
> I'm not sure if this is related to 2d5d2a986ce or something else.
>
>
> -- 
> Cheers,
> Cy Schubert 
> FreeBSD UNIX: Web:  https://FreeBSD.org
> NTP:   Web:  https://nwtime.org
>
>   The need of the many outweighs the greed of the few.
>
>
>





Re: Deprecating ISA sound cards

2022-03-18 Thread Mark Linimon
Anyone objecting to this, be careful, I might ship a pile of such
things to you from the depths of the closets :-)

mcl



DTrace Brokenness

2022-03-18 Thread Cy Schubert
It's been a while (~ 4-6 months) since I've last used dtrace. Needing to 
use it again today scripts that worked before fail to.

A first example:

cwfw# cat dt10.d
#!/usr/sbin/dtrace -s

fbt::ipf_check:entry {
parintf("%x\n", (void) arg[1]);
}

cwfw# 

Results in this error:

cwfw# ./dt10.d 
dtrace: failed to compile script ./dt10.d: "/usr/lib/dtrace/psinfo.d", line 
1: cannot translate from "struct thread *" to "lwpsinfo_t *"
cwfw# 

Another example,

slippy# cat dtrace.d 
#!/usr/sbin/dtrace -s

fbt::uma_reclaim:entry {
printf("in uma_reclaim\n");
}
slippy# 

Results in the same error:

slippy# ./dtrace.d 
dtrace: failed to compile script ./dtrace.d: "/usr/lib/dtrace/psinfo.d", 
line 1: cannot translate from "struct thread *" to "lwpsinfo_t *"
slippy# 


A variation of the second example,

slippy# cat dtrace.sh 
#!/bin/sh -
dtrace -n 'fbt::uma_reclaim:entry { printf("in uma_reclaim\n"); }'
slippy# 

Results in two errors, the first being that the -n option results in an 
invalid probe specified and the second being the struct thread * error.

slippy# ./dtrace.sh 
dtrace: invalid probe specifier fbt::uma_reclaim:entry { printf("in 
uma_reclaim\n"); }: "/usr/lib/dtrace/psinfo.d", line 1: cannot translate 
from "struct thread *" to "lwpsinfo_t *"
slippy# 

I'm not sure if this is related to 2d5d2a986ce or something else.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  https://FreeBSD.org
NTP:   Web:  https://nwtime.org

The need of the many outweighs the greed of the few.





Re: Deprecating ISA sound cards

2022-03-18 Thread Ed Maste
On Fri, 18 Mar 2022 at 16:06, Joel Dahl  wrote:
>
> On Fri, Mar 18, 2022 at 12:08:02PM -0400, Ed Maste wrote:
> > ISA sound cards have been obsolete for more than a decade, and it is
> > (past) time to retire their drivers. This includes the following
> > drivers/devices:
> >
> > ...
> You can remove snd_aureal, snd_ds1 and snd_maestro as well while you're at it.
> They've been broken for 10+ years:
> https://lists.freebsd.org/pipermail/freebsd-multimedia/2012-January/012751.html

Thanks for the note. I removed snd_aureal just now as it was not even
connected to the build. I'll take care of the others soon.



Re: Deprecating ISA sound cards

2022-03-18 Thread Joel Dahl
On Fri, Mar 18, 2022 at 12:08:02PM -0400, Ed Maste wrote:
> ISA sound cards have been obsolete for more than a decade, and it is
> (past) time to retire their drivers. This includes the following
> drivers/devices:
> 
> snd_ad1816  Analog Devices AD1816 SoundPort
> snd_ess Ensoniq ESS
> snd_guscGravis UltraSound
> snd_mss Microsoft Sound System
> snd_sbc Creative Sound Blaster

You can remove snd_aureal, snd_ds1 and snd_maestro as well while you're at it.
They've been broken for 10+ years:
https://lists.freebsd.org/pipermail/freebsd-multimedia/2012-January/012751.html

-- 
Joel



Deprecating ISA sound cards

2022-03-18 Thread Ed Maste
ISA sound cards have been obsolete for more than a decade, and it is
(past) time to retire their drivers. This includes the following
drivers/devices:

snd_ad1816  Analog Devices AD1816 SoundPort
snd_ess Ensoniq ESS
snd_guscGravis UltraSound
snd_mss Microsoft Sound System
snd_sbc Creative Sound Blaster

I have a review open to add deprecation notices:
https://reviews.freebsd.org/D34604

I expect to commit this in the near future, then MFC to stable
branches and remove these drivers from main. Please follow up if
there's a reason we should postpone the removal of any of these
drivers.