I can confirm the patch works for me as well, thanks!
Hi,
I was building ports and at the same time started chromium and the
kernel panic-ed.
This has happened a few times in the last week. It started happening
at some point towards the end of May. It is not easy to reproduce locally.
I followed ddb.html and taken some pictures[0] of the crash.
On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > I was building ports and at the same time started chromium and the
> > kernel panic-ed.
> >
> > This has happened a few times in the last wee
On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > I was building ports and at the same time started chromium and the
> > kernel panic-ed.
> >
> > This has happened a few times in the last wee
Hi,
I am have some issues with iwm(4). I think this started happening
around the 22nd-23rd of June.
I cannot reproduce it very easily but it seems to trigger during
a large download (3-4GB or so).
Anything I should try to make diagnosing this easier?
$ ifconfig iwm0
iwm0: flags=208843
mtu 1500
On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> Without more information it's hard to find what could be the reason
> for this crash. Being able to reproduce the crash easily is the key
> to debugging. Can you do that?
while :; do (chrome &); sleep 8; pkill chrome; done
It ta
On Tue, Jul 05, 2016 at 07:43:57PM +0200, Stefan Sperling wrote:
> On Tue, Jul 05, 2016 at 06:22:00PM +0100, Dimitris Papastamos wrote:
> > Hi,
> >
> > I am have some issues with iwm(4). I think this started happening
> > around the 22nd-23rd of June.
> >
>
On Wed, Jul 06, 2016 at 03:17:43PM +0200, Martin Pieuchot wrote:
> Thanks! So could you try the second step? After applying the diff below
> set splassert to 4 before starting your loop (sysctl kern.splassert=4).
>
> The machine should no longer panic but dump multiple traces until a NULL
> poin
On Wed, Jul 06, 2016 at 09:56:10AM -0700, Philip Guenther wrote:
> On Wed, 6 Jul 2016, Tobias Ulmer wrote:
> > On Tue, Jul 05, 2016 at 07:01:11PM +0100, Dimitris Papastamos wrote:
> > > On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > > > Without
Hi,
I use tinc-vpn on my laptop and noticed that when I reboot or halt
the system, it freezes when it tries to stop the tinc daemon.
This is reproducible with today's current.
The tinc-down script that is executed when the daemon is stopped
does the following:
#!/bin/sh
route delete 172.17.0.2
On Thu, Jul 21, 2016 at 11:27:17AM +0100, Stuart Henderson wrote:
> On 2016/07/21 11:16, Dimitris Papastamos wrote:
> > Hi,
> >
> > I use tinc-vpn on my laptop and noticed that when I reboot or halt
> > the system, it freezes when it tries to stop the tinc daemon.
&g
On Thu, Jul 21, 2016 at 11:27:17AM +0100, Stuart Henderson wrote:
> On 2016/07/21 11:16, Dimitris Papastamos wrote:
> > Hi,
> >
> > I use tinc-vpn on my laptop and noticed that when I reboot or halt
> > the system, it freezes when it tries to stop the tinc daemon.
&g
Hi,
I am also seeing something similar on 6.0-stable. In my case, it does not
hang on boot however. I have not yet tried -current but will do and report
back.
OpenBSD 6.0-stable (GENERIC.MP) #6: Fri Sep 2 12:03:43 BST 2016
r...@sun.2f30.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real m
Hi,
In an attempt to fix video tearing in fullscreen mode I used the
following config in /etc/X11/xorg.conf.d/10-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "Tearfree" "true"
EndSection
After starting X, the screen
On Fri, Oct 14, 2016 at 11:47:58PM +0100, Dimitris Papastamos wrote:
> Hi,
>
> In an attempt to fix video tearing in fullscreen mode I used the
> following config in /etc/X11/xorg.conf.d/10-intel.conf
>
> Section "Device"
> Identifier "Intel Grap
Hi everyone,
I am experiencing a kernel freeze with -current. The last kernel I
built that still had the issue was from the 27th of December. The
freeze takes hours to happen but usually occurs with browsing
activity. I try to manually break into ddb but that did not work.
The machine is stuck
On Sat, Jan 30, 2016 at 11:03:06AM +, Stuart Henderson wrote:
> Replying to Paul's post and adding CCs, but Lars' post is also related
> http://marc.info/?l=openbsd-bugs&m=145409292029625&w=2
>
> Lars, and anyone else seeing this, what interface types do you have?
> Any tunnels (gif gre tun vx
Hi everyone,
After I rebuilt and booted the kernel today I noticed dmesg -s
produces no output. I suspect this is to do with the recent change:
If sendsyslog(2) is called with LOG_CONS before syslogd(8) has been
started and before init(8) has opened the console, the kernel could
cras
Hi all,
I recently bought a Thinkpad x250 and just noticed that IPv6 stateless
autoconfiguraton is not working using iwm(4). It works if I use em(4)
instead.
Not sure how this could be driver related. I have a t420 running
current and it works with iwn(4) and em(4).
pf was disabled during the
On Sun, May 29, 2016 at 08:10:02PM +0200, Stefan Sperling wrote:
> On Sun, May 29, 2016 at 01:25:02PM +0100, Dimitris Papastamos wrote:
> > Hi all,
> >
> > I recently bought a Thinkpad x250 and just noticed that IPv6 stateless
> > autoconfiguraton is not working using
I managed to capture a similar crash again on the same box.
See http://cream.2f30.org/sin/openbsd-crash2
Hi there,
I've been hitting a kernel crash on both OpenBSD 5.6 and 5.7.
See below for the dmesg + a picture[0] of the crash. There was no ddb prompt
so there is little information there.
For the details on the OpenBSD 5.6 crash (managed to drop into ddb there)
see http://marc.info/?t=1428657458
Hi,
I've upgraded to the latest snapshot today but X doesn't
start. See the dmesg and Xorg.0.log below.
I am currently rebuilding Xenocara from source in case
this has already been fixed.
Cheers,
Dimitris
OpenBSD 5.8-current (GENERIC.MP) #1252: Fri Aug 21 19:45:34 MDT 2015
dera...@amd64.op
On Sun, Aug 23, 2015 at 11:19:25AM +0100, Dimitris Papastamos wrote:
> Hi,
>
> I've upgraded to the latest snapshot today but X doesn't
> start. See the dmesg and Xorg.0.log below.
>
> I am currently rebuilding Xenocara from source in case
> this has already b
On Sun, Aug 23, 2015 at 09:42:10PM +1000, Jaime Tarrant wrote:
> Hi Dimitris,
>
> I experienced this also with snapshots dated 22 August from
> ftp3.usa.openbsd.org. I then upgraded again using a snapshot dated
> 23rd August from ftp.openbsd.org and X is working correctly again.
Ah, I was using t
Hi all,
Recording without a docking station, no longers works on amd64
-current on my T420. When using aucat, it doesn't error out or
anything but I can only hear back silence. If I revert[0] the recent
azalia changes then recording works.
[0] http://u.2f30.org/sin/azalia.patch
OpenBSD 5.8-cur
Hi,
I see the same problem on my router. I also lost IPv6 functionality.
I am using a tunnel through Hurricane Electric. If I tcpdump on the
external interface and ping6 an external host, I can see the
encapsulated echo requests reaching the tunnel but no replies are
coming through.
I am sure t
On Wed, Dec 16, 2015 at 09:01:20AM +, Dimitris Papastamos wrote:
> Hi,
>
> I see the same problem on my router. I also lost IPv6 functionality.
> I am using a tunnel through Hurricane Electric. If I tcpdump on the
> external interface and ping6 an external host, I can see the
Hi,
iwm seems to produce "unhandled firmware response" messages. Network
connectivity is really bad during this period and eventually ceases
entirely. I have captured a pcap file[0] right after I noticed the
messages.
[0] https://u.2f30.org/sin/iwm/iwm.pcap
I can reproduce this problem by down
On Mon, Jan 23, 2017 at 02:56:10PM +0100, Stefan Sperling wrote:
> On Mon, Jan 23, 2017 at 10:17:51AM +0000, Dimitris Papastamos wrote:
> > Hi,
> >
> > iwm seems to produce "unhandled firmware response" messages. Network
> > connectivity is really bad dur
On Mon, Jan 23, 2017 at 02:56:10PM +0100, Stefan Sperling wrote:
> On Mon, Jan 23, 2017 at 10:17:51AM +0000, Dimitris Papastamos wrote:
> > Hi,
> >
> > iwm seems to produce "unhandled firmware response" messages. Network
> > connectivity is really bad dur
Hi,
I have an alix2d13 and running 6.0-stable on it.
I get this in dmesg:
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: can't map
interrupt
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: can't map
interrupt
I think vr1 should map to irq 11 and vr2 to irq 15.
Below is the pcidump output.
The interrupt line for 0:10:0: and 0:11:0: (vr1 and vr2) seems to be
0xff which doesn't look right.
Domain /dev/pci0:
0:1:0: AMD Geode LX
0x: Vendor ID: 1022 Product ID: 2080
0x0004: Command: 0005 Status: 0220
0x0008: Class: 06 Subclass: 0
On Tue, Feb 21, 2017 at 12:03:06PM +, Stuart Henderson wrote:
> On 2017/02/21 11:30, Dimitris Papastamos wrote:
> > Hi,
> >
> > I have an alix2d13 and running 6.0-stable on it.
> >
> > I get this in dmesg:
> >
> > vr1 at pci0 dev 10 function
Mystery solved, I flashed the bios using FreeDOS and networking
works fine now.
Previously I used flashrom in securelevel -1, not sure what went
wrong there...
35 matches
Mail list logo
