Re: Panic on 8-STABLE in pfctl with options VIMAGE on a DELL PowerEdge R300 (bge)

2010-02-26 Thread Onur Bektas

Hi,

I had the same problem, I have updated the source tree and recompile the 
kernel  but the problem is  still unresolved..

pf + vimage = "kernel crash" problem was also reported as a bug..

http://www.freebsd.org/cgi/query-pr.cgi?pr=143808&cat=

Regards,

Onur.


On 2/26/2010 8:18 PM, Lorenzo Perone wrote:


Hello,

Just encountered a panic when starting pf (/etc/rc.d/pf start) on a 
FreeBSD benjamin 8.0-STABLE


uname -a

FreeBSD 8.0-STABLE #0: Fri Feb 26 18:33:44 UTC 2010 
r...@benjamin:/usr/obj/usr/src/sys/BYTESATWORK_R8_INTEL_DEBUG  amd64


the system is a Dell PowerEdge R300 with bge interfaces, 16 GB RAM 
(dmesg attached).


Panic and trace remote console screenshots:

http://lorenzo.yellowspace.net/R300_pfctl_panic.gif
http://lorenzo.yellowspace.net/R300_pfctl_panic_trace.gif

Excerpt transcript:

panic:

Fatal trap 12: page fault while in kernel mode
current process = 1302
Stopped at pfil_head_get+0x41 movq 0x28(%rcx),%rdx

trace:

pfil_head_get() at pfil_head_get+0x41
pfioctl() at pfioctl+0x3351
devfs_ioctl_f() at devfs_ioctl_f+0x71
kern_ioctl() at kern_ioctl+0xe4
ioctl() at ioctl+0xed
syscall() at syscall+0x1e7
Xfast_syscall() at Xfast_syscall+0xe1

While I was just planning to experiment with VIMAGE, and it is not 
required for production (I'm aware of the message of it being 
experimental...), I thought it might be useful to report it. Please 
send me a note if I should file a pr.


The panic does not occur with the same kernel compiled without options 
VIMAGE.


Note that the dmesg is from the system booted with the kernel without 
VIMAGE, that's why it doesn't contain the warning.


big Regards to all the team,

Lorenzo



___
freebsd-j...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"



Onur BEKTAS
Sistem Yöneticisi / System Administrator
TÜBITAK ULAKBIM

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Panic on 8-STABLE in pfctl with options VIMAGE on a DELL PowerEdge R300 (bge)

2010-02-26 Thread Bjoern A. Zeeb

On Fri, 26 Feb 2010, Lorenzo Perone wrote:

Hi,

While I was just planning to experiment with VIMAGE, and it is not required 
for production (I'm aware of the message of it being experimental...), I 
thought it might be useful to report it. Please send me a note if I should 
file a pr.


The panic does not occur with the same kernel compiled without options 
VIMAGE.


FAQ from virtualization@ ; pf support for VIMAGE only basically exists
here:  http://svn.freebsd.org/base/user/eri/pf45/head/
but is not fully ready either.

/bz

--
Bjoern A. Zeeb It will not break if you know what you are doing.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Panic on 8-STABLE in pfctl with options VIMAGE on a DELL PowerEdge R300 (bge)

2010-02-26 Thread Lorenzo Perone


Hello,

Just encountered a panic when starting pf (/etc/rc.d/pf start) on a 
FreeBSD benjamin 8.0-STABLE


uname -a

FreeBSD 8.0-STABLE #0: Fri Feb 26 18:33:44 UTC 2010 
r...@benjamin:/usr/obj/usr/src/sys/BYTESATWORK_R8_INTEL_DEBUG  amd64


the system is a Dell PowerEdge R300 with bge interfaces, 16 GB RAM 
(dmesg attached).


Panic and trace remote console screenshots:

http://lorenzo.yellowspace.net/R300_pfctl_panic.gif
http://lorenzo.yellowspace.net/R300_pfctl_panic_trace.gif

Excerpt transcript:

panic:

Fatal trap 12: page fault while in kernel mode
current process = 1302
Stopped at pfil_head_get+0x41 movq 0x28(%rcx),%rdx

trace:

pfil_head_get() at pfil_head_get+0x41
pfioctl() at pfioctl+0x3351
devfs_ioctl_f() at devfs_ioctl_f+0x71
kern_ioctl() at kern_ioctl+0xe4
ioctl() at ioctl+0xed
syscall() at syscall+0x1e7
Xfast_syscall() at Xfast_syscall+0xe1

While I was just planning to experiment with VIMAGE, and it is not 
required for production (I'm aware of the message of it being 
experimental...), I thought it might be useful to report it. Please send 
me a note if I should file a pr.


The panic does not occur with the same kernel compiled without options 
VIMAGE.


Note that the dmesg is from the system booted with the kernel without 
VIMAGE, that's why it doesn't contain the warning.


big Regards to all the team,

Lorenzo

Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-STABLE #0: Fri Feb 26 18:33:44 UTC 2010
r...@benjamin:/usr/obj/usr/src/sys/BYTESATWORK_R8_INTEL_NO_VIMAGE_DEBUG 
amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU   X3363  @ 2.83GHz (2833.34-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x1067a  Stepping = 10
  
Features=0xbfebfbff
  
Features2=0x40ce3bd
  AMD Features=0x20100800
  AMD Features2=0x1
  TSC: P-state invariant
real memory  = 17179869184 (16384 MB)
avail memory = 16542048256 (15775 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
ioapic0: Changing APIC ID to 4
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  at device 2.0 on pci0
pci3:  on pcib1
pcib2:  at device 3.0 on pci0
pci4:  on pcib2
pcib3:  at device 4.0 on pci0
pci5:  on pcib3
mpt0:  port 0xec00-0xecff mem 
0xdfcec000-0xdfce,0xdfcf-0xdfcf irq 16 at device 0.0 on pci5
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.18.0
mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
mpt0: 1 Active Volume (2 Max)
mpt0: 2 Hidden Drive Members (14 Max)
pcib4:  at device 5.0 on pci0
pci6:  on pcib4
pcib5:  at device 6.0 on pci0
pci7:  on pcib5
pcib6:  at device 7.0 on pci0
pci8:  on pcib6
pcib7:  irq 16 at device 28.0 on pci0
pci9:  on pcib7
pcib8:  irq 16 at device 28.4 on pci0
pci1:  on pcib8
bge0:  mem 
0xdfdf-0xdfdf irq 16 at device 0.0 on pci1
miibus0:  on bge0
brgphy0:  PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
bge0: Ethernet address: 00:26:b9:50:03:3e
bge0: [FILTER]
pcib9:  irq 17 at device 28.5 on pci0
pci2:  on pcib9
bge1:  mem 
0xdfef-0xdfef irq 17 at device 0.0 on pci2
miibus1:  on bge1
brgphy1:  PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
bge1: Ethernet address: 00:26:b9:50:03:3f
bge1: [FILTER]
uhci0:  port 0xcc80-0xcc9f irq 21 at device 
29.0 on pci0
uhci0: [ITHREAD]
usbus0:  on uhci0
uhci1:  port 0xcca0-0xccbf irq 20 at device 
29.1 on pci0
uhci1: [ITHREAD]
usbus1:  on uhci1
uhci2:  port 0xccc0-0xccdf irq 21 at device 
29.2 on pci0
uhci2: [ITHREAD]
usbus2:  on uhci2
ehci0:  mem 0xdfaffc00-0xdfaf irq 
21 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus3: EHCI version 1.0
usbus3:  on ehci0
pcib10:  at device 30.0 on pci0
pci10:  on pcib10
vgapci0:  port 0xdc00-0xdcff mem 
0xd000-0xd7ff,0xdfff-0xdfff irq 19 at device 7.0 on pci10
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0xcc20-0xcc27,0xcc10-0xcc13,0xcc28-0xcc2f,0xcc14-0xcc17,0xcc40-0xcc4f,0xcc50-0xcc5f
 irq 23 at device 31.2 on pci0
atapci0: [ITHREAD]
ata2:  on atapci0
ata2: [ITHREAD]
ata3:  on atapci0
ata3: [ITHREAD]
atapci1:  port 
0xcc30-0xcc37,0xcc18-0xcc1b,0xcc38-0xcc3f,0xcc1c-0xcc1f,0xcc60-0xcc6f,0xcc70-0xcc7f
 irq 22 at device 31.5 on pci0
atapci1: [ITHREAD]
ata4:  on atapci1
ata4: [ITH