On 27-Jul-2002 Arun Sharma wrote: > This is with the GENERIC kernel. Known problem ? How can I get a > -current kernel that boots to multiuser so that I can tinker around with > it ? Are there any magic config files that suppress these panics ? > > db> trace > _mtx_lock_flags(7069307e,0,c03ff2e0,530) at _mtx_lock_flags+0x3e > securelevel_ge(bfbffe00,3,c0291194,c04b0e60,c04b0ca8) at > securelevel_ge+0x3c > ip_fw_ctl(cad2fcc0,c026213c,0,c2075410,cad2fcac) at ip_fw_ctl+0x30 > rip_ctloutput(c2075410,cad2fcc0,cad2fd14,c0d6c540,cad2fcec) at > rip_ctloutput+0xe > sosetopt(c2075410,cad2fcc0,c2075410,1,0) at sosetopt+0x2c > setsockopt(c0d6c540,cad2fd14,5,0,213) at setsockopt+0x8e > syscall(2f,2f,2f,8093879,bfbffe73) at syscall+0x233 > syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
Knowing the actual panic message would help. :) -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
