Hi Pierre, On 08/08/14(Fri) 15:10, BARDOU Pierre wrote: > Synopsis: Kernel panic when adding a route already present in a rdomain > Category: Networking > Environment: > System : OpenBSD 5.5 > Details : OpenBSD 5.5-stable (GENERIC.MP) #0: Thu May 15 14:28:53 > CEST 2014 > > [email protected]:/usr/src/sys/arch/i386/compile/GENERIC.MP > > Architecture: OpenBSD.i386 > Machine : i386 > >Description: > When doing a netstart on an already started interface with rdomains > and routes, kernel panics. > I tried to input the commands by hand, the problem occurs when doing > the first route add -> the route is already present, but instead of the > classic error I get a panic. > > Hostname.if conf file : > # cat /etc/hostname.carp2031 > 10.200.0.246/28 vhid 1 advskew $(cat /etc/carp.prio) carpdev vlan2031 rdomain > 31 pass $(cat /etc/carp.pass) description "TL-FU-WAN31" > up -inet6 > !route -q -T 31 add 10.60.0.0/16 10.200.0.241 > !route -q -T 31 add 10.80.0.0/16 10.200.0.241 > !route -q -T 31 add 10.193.0.0/16 10.200.0.241 > !route -q -T 31 add 10.194.0.0/16 10.200.0.241 > !route -q -T 31 add 10.195.0.0/16 10.200.0.241 > !route -q -T 31 add 217.109.108.0/24 10.200.0.241 > > 100% reproducible on OpenBSD 5.5-stable, i386 and amd64. > > Panic message : > uvm_fault(0xfffffe811d574010, 0x1ea, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at rtrequest1+0x330: movzbl 0x1ea(%rax),%eax
This means an ifp pointer is wrong. Unfortunately I cannot reproduce this panic here with the hostname.carp2031 alone. Could you try to find the smallest configuration to reproduce it? In case you can reproduce this trap, I'd interested in the output of "show reg". Thanks, Martin
