Hi,
I encounter a problem of parsing in ksh(1): a quote in a comment in a
command substitution $(...) or `...` is parsed as quote and a closing quote
is expected.
Here code snippet that expose the problem:
$ cat test.sh
echo $(echo abc |
# comment
cat)
echo $(echo abc |
> I think this is how a null-pointer call shows up in ddb.
>
> Does the diff below help?
>
Perfect! That stopped the uvm_fault occuring, scanning now works well;
however when actually connecting to an AP I get a number of
bwi0: watchdog timeout
and although it successfully can acquire a DHCP addr
On 06/03/15(Fri) 22:06, Remi Locherer wrote:
> On Fri, Mar 06, 2015 at 09:15:23AM +0100, Stefan Sperling wrote:
> > On Fri, Mar 06, 2015 at 08:45:20AM +0100, Remi Locherer wrote:
> > > Hi,
> > >
> > > Since about fall 2014 I see "urtwn0 timeout" every now an then like
> > > others that reported i
On Fri, Mar 06, 2015 at 09:15:23AM +0100, Stefan Sperling wrote:
> On Fri, Mar 06, 2015 at 08:45:20AM +0100, Remi Locherer wrote:
> > Hi,
> >
> > Since about fall 2014 I see "urtwn0 timeout" every now an then like
> > others that reported it. An unplug and replut of the urtwn device
> > usually h
>Synopsis: kernel panic when something attempts to execute user address in
>supervisor mode
>Category: system
>Environment:
System : OpenBSD 5.6
Details : OpenBSD 5.6-stable (GENERIC) #2: Wed Jan 14 10:21:38 PST
2015
r...@new.tilderoot.
On Fri, Mar 06, 2015 at 08:45:20AM +0100, Remi Locherer wrote:
> Hi,
>
> Since about fall 2014 I see "urtwn0 timeout" every now an then like
> others that reported it. An unplug and replut of the urtwn device
> usually helped.
>
> But with the snapshots from March 1st and 3rd the system just fre
I confirm. I have the same issue.
On Fri, Mar 6, 2015 at 10:45 AM, Remi Locherer
wrote:
> Hi,
>
> Since about fall 2014 I see "urtwn0 timeout" every now an then like
> others that reported it. An unplug and replut of the urtwn device
> usually helped.
>
> But with the snapshots from March 1st an
