On 19-02-04 00:29:29, Anthony Jenkins wrote:
[snip]
Hi Adrian. I too am wondering what the plan is for this chipset. I am currently
using an awful USB wifi dongle. I can help with testing if needed - but I just
really want to know if we should expect upstream support which is relatively
stable in
On 18-11-23 13:05:00, Charlie Li wrote:
> On 23/11/2018 00:02, Ben Widawsky wrote:
> > Thanks both of you. Here's another shot at roughly the same thing I asked
> > the
> > first reporter to try (that patch was wrong). If it doesn't work, can you
> > please
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 18-11-23 16:42:22, Mateusz Piotrowski wrote:
> On Tue, 20 Nov 2018 at 15:47, Charlie Li wrote:
>
> > Somewhere between r340491 and r340650, probably starting from r340595,
> > my ThinkPad W550s started spewing these messages repeatedly in the
> > system log since boot:
> >
> > ...
> >
> > As a
Thanks both of you. Here's another shot at roughly the same thing I asked the
first reporter to try (that patch was wrong). If it doesn't work, can you please
post the dmesg?
diff --git a/sys/dev/acpica/acpi_ec.c b/sys/dev/acpica/acpi_ec.c
index a21dbc963af..666aba2b3c8 100644
--- a/sys/dev/acpica
On 18-11-20 11:28:56, Ben Widawsky wrote:
> On 18-11-20 14:09:08, Jung-uk Kim wrote:
> > On 18. 11. 20., Charlie Li wrote:
> > > Somewhere between r340491 and r340650, probably starting from r340595,
> > > my ThinkPad W550s started spewing these messages repeatedly in
On 18-11-20 14:09:08, Jung-uk Kim wrote:
> On 18. 11. 20., Charlie Li wrote:
> > Somewhere between r340491 and r340650, probably starting from r340595,
> > my ThinkPad W550s started spewing these messages repeatedly in the
> > system log since boot:
> >
> > Nov 20 09:35:19 ardmore kernel: ACPI Err
You'll need to update base first, and ideally update all your packages before
make delete-old and make delete-old-libs
On 18-10-25 16:29:59, Pieper, Jeffrey E wrote:
> I'm seeing:
>
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found,
On 18-05-18 13:22:01, Ben Widawsky wrote:
> On 18-05-18 14:15:03, Warner Losh wrote:
> > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg
> > wrote:
> >
> > >
> > >
> > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote:
> > >
>
On 18-05-18 14:15:03, Warner Losh wrote:
> On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg
> wrote:
>
> >
> >
> > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote:
> >
> >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl <
> >> s...@troutmask.apl.washington.edu> wrote:
> >>
> >> > On Fri, May
> Looking at the sendsig label in sys_process.c:kern_ptrace() makes it clear
> what's happening - in your testing the process was already stopped so
> the code sets td_xsig to SIGSTOP and wakes it up to send it the signal.
>
> But td_xsig doesn't seem to be used anywhere to set pending signals. Ma
If a debugger attaches to a suspended process, the process will be
resumed, and backgrounded. This seems like the incorrect behavior to me
based what I read in the man page. "The tracing process will see the
newly-traced process stop and may then control it as if it had been
traced all along."
The
12 matches
Mail list logo
