On 2016/08/02 08:11, Andrew Fresh wrote:
> On Tue, Aug 02, 2016 at 10:53:24AM -0400, RD Thrush wrote:
> > Resending this report since it hasn't appeared on bugs nor marc.info.
> > Apologies if it emerges from a queue.
>
> This was broken (by me) in r1.2 and fixed in r1.3 of this file. Sadly
> t
Hi, goord afternoon.
I have a similar problem. Sometimes I get the message "iwm0: fatal firmware
error" and then, I have to restart the network interface doing sh
/etc/netstart. But most of the time, I have internet access. Now, I've
added the option IWM_DEBUG in the kernel, I rebuilt the kernel a
Hi All,
I have used Umap2 to scan OpenBSD 5.9 on i386 for supported USB devices,
and during this scan I have found 4 issues with the USB stack.
Umap2 can be downloaded from github [1].
The scanning requires some hardware - facedancer/beaglebone board,
and consists of emulating USB devices with si
Bug: page fault in handling of VID 0x04bb PID 0x0904
uname -a: OpenBSD <> 5.9 GENERIC.MP#1616 i386
Umap2 command line: umap2vsscan -P gadgetfs -s 04bb:0904
After emulating this device (with the Umap2 command above), the host
USB stack becomes unresponsive, and will not even enumerate new devices.
On Tue, Aug 02, 2016 at 10:53:24AM -0400, RD Thrush wrote:
> Resending this report since it hasn't appeared on bugs nor marc.info.
> Apologies if it emerges from a queue.
This was broken (by me) in r1.2 and fixed in r1.3 of this file. Sadly
the broken one is tagged OPENBSD_6_0, but I will be co
On Tue, Aug 02, 2016 at 10:53:24AM -0400, RD Thrush wrote:
> Resending this report since it hasn't appeared on bugs nor marc.info.
> Apologies if it emerges from a queue.
>
> >Synopsis:Diagnostic warning appeared after amd64 -current Sat Jul 16
> >11:37:22 MDT 2016
> >Category:system
>
Resending this report since it hasn't appeared on bugs nor marc.info.
Apologies if it emerges from a queue.
>Synopsis: Diagnostic warning appeared after amd64 -current Sat Jul 16
>11:37:22 MDT 2016
>Category: system
>Environment:
System : OpenBSD 6.0
Details :
On Tue, Aug 02, 2016 at 11:34:13AM +0300, lifayk wrote:
> Hello!
>
> Periodically, I get the fatal firmware error with iwm. I have to swith
> off and on iwm to restart the Wi-Fi. I rebuild the kernel with "option
> IWM_DEBUG" and attached the log with the error.
> snapshot from 02 June 2016.
>
> --
>Synopsis: wsconsctl says keysym Caps_Lock not found
>Category: system
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT
2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GE
I didn't think it had a default setting. Can't believe I didn't check that
first.
Thanks,
Edgar
Sent from my iPhone
> On Aug 2, 2016, at 12:59 AM, Raf Czlonka wrote:
>
> Hi Edgar,
>
> This is by design - the flags you are trying to set simply match
> the default ones:
>
># unset flags
up ?
Le 2016-07-18 11:05, Solène a écrit :
hello,
I checked the addresses and they are still fine.
Index: unbound.conf
===
RCS file: /cvs/src/etc/unbound.conf,v
retrieving revision 1.6
diff -u -p -r1.6 unbound.conf
--- unbound.con
Hello!
Periodically, I get the fatal firmware error with iwm. I have to swith
off and on iwm to restart the Wi-Fi. I rebuild the kernel with "option
IWM_DEBUG" and attached the log with the error.
snapshot from 02 June 2016.
--
lifayk
e: lif...@gmail.com
pgp: 0x84CAC40B
Aug 2 11:05:41 t4 /bsd
12 matches
Mail list logo
