On Fri, Nov 15, 2013 at 08:42:07AM +0100, Remi Locherer wrote:
> On Mon, Nov 11, 2013 at 04:22:47PM +, Stuart Henderson wrote:
> > On 2013/11/11 09:53, RD Thrush wrote:
> > > >Synopsis:Firewall panic with Nov 10 snapshot
> > > >Category:kernel
> > > >Environment:
> > > System
1.84
> bpfdesc.h:1.18->1.19
>
>
> ...
>
> -
> PatchSet 3508
> Date: 2013/11/11 16:21:08
> Author: sthen
> Branch: HEAD
> Tag: (none)
> Log:
> Revert bpf.c 1.84 / bpfdesc.h 1.19 for now, "panic: timeout_add: to_ticks (-
bpf.c:1.83->1.84
bpfdesc.h:1.18->1.19
...
-
PatchSet 3508
Date: 2013/11/11 16:21:08
Author: sthen
Branch: HEAD
Tag: (none)
Log:
Revert bpf.c 1.84 / bpfdesc.h 1.19 for now, "panic: timeout_add: to_ticks (-1)
< 0" seen by RD Thrush, http://articl
On Wed, Dec 18, 2013 at 12:46:44AM -0500, RD Thrush wrote:
> On 12/17/13 20:42, RD Thrush wrote:
> > On 12/17/13 20:01, Kenneth R Westerback wrote:
> >> On Tue, Dec 17, 2013 at 07:32:02PM -0500, RD Thrush wrote:
> >>> On 11/22/13 12:03, Stuart Henderson wrote:
> On 2013/11/22 08:47, RD Thrush
On 12/17/13 20:42, RD Thrush wrote:
> On 12/17/13 20:01, Kenneth R Westerback wrote:
>> On Tue, Dec 17, 2013 at 07:32:02PM -0500, RD Thrush wrote:
>>> On 11/22/13 12:03, Stuart Henderson wrote:
On 2013/11/22 08:47, RD Thrush wrote:
> On 11/11/13 11:22, Stuart Henderson wrote:
>> On 201
On 12/17/13 20:01, Kenneth R Westerback wrote:
> On Tue, Dec 17, 2013 at 07:32:02PM -0500, RD Thrush wrote:
>> On 11/22/13 12:03, Stuart Henderson wrote:
>>> On 2013/11/22 08:47, RD Thrush wrote:
On 11/11/13 11:22, Stuart Henderson wrote:
> On 2013/11/11 09:53, RD Thrush wrote:
>>> Syn
we start the read, iff there's a timeout.
+ * If there's a timeout, bd_rdStart is tagged when we start the read.
* we can then figure out when we're done reading.
*/
i.e. only comment changes from 1.83 remain.
.
>
> I'm using "ladvd -Lz" and hit the panic pretty much as soon as it starts.
The panic remains with today's snapshot. This problem originated with v1.84 of
sys/net/bpf.c. Despite several reverts since, the problem remains. It is easy
to reproduce, ie.:
sudo pkg_a
.
The panic repeatably occurs after reboot by arranging to start the darkstat
package and ensuring one access to the darkstat port from a @reboot in a user
crontab. Here's what I did:
pkg_add darkstat
echo 'pkg_scripts="$pkg_scripts darkstat"' >>/etc/rc.conf.local
Add &#
On 11/29/13 17:03, Ted Unangst wrote:
> On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote:
>> On 2013/11/29 14:34, Ted Unangst wrote:
>>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
I've tried -current (Nov 28) on two real machines (soekris and amd64
homebrew) which panic with app
On 11/29/13 17:23, RD Thrush wrote:
> On 11/29/13 17:03, Ted Unangst wrote:
>> On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote:
>>> On 2013/11/29 14:34, Ted Unangst wrote:
On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
> I've tried -current (Nov 28) on two real machines (soekris and
On 11/29/13 17:41, Ted Unangst wrote:
> On Fri, Nov 29, 2013 at 17:23, RD Thrush wrote:
>
>> With the above patch, the reboot hung, no kbd (caps/scroll/num lock echo)
>> and no
>> response to the ddb interrupt. I had to do a hardware reset. Here's the last
>> bits from the serial console:
>
> Th
On Fri, Nov 29, 2013 at 17:23, RD Thrush wrote:
> With the above patch, the reboot hung, no kbd (caps/scroll/num lock echo)
> and no
> response to the ddb interrupt. I had to do a hardware reset. Here's the last
> bits from the serial console:
The thick plottens...
On 11/29/13 17:03, Ted Unangst wrote:
> On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote:
>> On 2013/11/29 14:34, Ted Unangst wrote:
>>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
I've tried -current (Nov 28) on two real machines (soekris and amd64
homebrew) which panic with app
On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote:
> On 2013/11/29 14:34, Ted Unangst wrote:
>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
>> > I've tried -current (Nov 28) on two real machines (soekris and amd64
>> > homebrew) which panic with apparently the same problem. FWIW, I have no
On 2013/11/29 14:34, Ted Unangst wrote:
> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
> > I've tried -current (Nov 28) on two real machines (soekris and amd64
> > homebrew) which panic with apparently the same problem. FWIW, I have not
> > been able to panic a virtualbox i386 machine. The pan
On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote:
> I've tried -current (Nov 28) on two real machines (soekris and amd64
> homebrew) which panic with apparently the same problem. FWIW, I have not
> been able to panic a virtualbox i386 machine. The panic occurs
> immediately after connecting to the
On 11/22/13 12:03, Stuart Henderson wrote:
> On 2013/11/22 08:47, RD Thrush wrote:
>> On 11/11/13 11:22, Stuart Henderson wrote:
>>> On 2013/11/11 09:53, RD Thrush wrote:
> Synopsis: Firewall panic with Nov 10 snapshot
> Category: kernel
> Environment:
System : OpenBSD 5.4
On 2013/11/22 08:47, RD Thrush wrote:
> On 11/11/13 11:22, Stuart Henderson wrote:
> > On 2013/11/11 09:53, RD Thrush wrote:
> >>> Synopsis: Firewall panic with Nov 10 snapshot
> >>> Category: kernel
> >>> Environment:
> >>System : OpenBSD 5.4
> >>Details : OpenBSD 5.4-current (GEN
f commit for now, it looks like the change is invalidating
> assumptions of the conditional around bpf_read()'s tsleep in bpf.c:439 ..
The panic is still there with snapshot from Nov 14. It's easy to reproduce:
Start darkstat and surf the web with lynx.
ddb output (typed by hand):
fo as well as normal sendbug details.
> >How-To-Repeat:
> Don't know.
> >Fix:
> Revert to Nov 7 kernel
I've reverted the bpf commit for now, it looks like the change is invalidating
assumptions of the conditional around bpf_read()'s tsleep in bpf.c:439 ..
> pan
Revert to Nov 7 kernel
panic: timeout_add: to_ticks (-1) < 0
Stopped at Debugger+0x4: popl%ebp
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb> trace
Debugger
22 matches
Mail list logo
