MCA: CPU 0 UNCOR PCC DTLB L1 error

2011-05-10 Thread John Hay
Hi,

I have seen this panic a few times on a Gigabyte E350N-USB3 running 8-STABLE.
I have only seen it while in X, but then the machine is always in X. At first,
I just got these hangs, so bought a PCI-express RS232 card and could see these
at last. For some reason it does not go past this, so I have not been able to
get a dump yet.

Have anybody an idea of why this is or how to debug it further? I searched
the archives and found something similar about a year ago, but it looks
like it was solved with a fix that got committed.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140338

I have now disabled mca in loader.conf with 'hw.mca.enabled="0"' and I have
not seen that panic again. I do occasionally see a panic in devfs_open(),
but I guess that should be handled in another thread.

The kernel is basically a GENERIC kernel with puc uncommented and the
following in loader.conf

vm.kmem_size="12G"
hw.mca.enabled="0"
zfs_load="YES"
ahci_load="YES"
xhci_load="YES"
amdtemp_load="YES"
ng_ubt_load="YES"
uplcom_load="YES"

Here is the panic message and after that dmesg.

John
-- 
John Hay -- j...@meraka.csir.co.za / j...@freebsd.org


MCA: Bank 0, Status 0xb6010015
MCA: Global Cap 0x0106, Status 0x0004
MCA: Vendor "AuthenticAMD", ID 0x500f10, APIC ID 0
MCA: CPU 0 UNCOR PCC DTLB L1 error
MCA: Address 0x8016c4000


Fatal trap 28: machine check trap while in user mode
cpuid = 0; apic id = 00
instruction pointer = 0x43:0x80156af85
stack pointer   = 0x3b:0x7fffcb18
frame pointer   = 0x3b:0x80fe87800
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 3, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = 2484 (initial thread)
trap number = 28
panic: machine check trap
cpuid = 0
KDB: stack backtrace:
#0 0x80608d5e at kdb_backtrace+0x5e
#1 0x805d6707 at panic+0x187
#2 0x808bf4c0 at trap_fatal+0x290
#3 0x808bfaa9 at trap+0x109
#4 0x808a7d94 at calltrap+0x8



Copyright (c) 1992-2011 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.2-STABLE #1: Fri Apr 29 10:14:26 SAST 2011
j...@angel.cids.org.za:/usr/obj/usr/src/sys/ANGEL amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD E-350 Processor (1600.07-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x500f10  Family = 14  Model = 1  Stepping = 0
  
Features=0x178bfbff
  Features2=0x802209
  AMD Features=0x2e500800
  AMD 
Features2=0x35ff
  TSC: P-state invariant
real memory  = 8589934592 (8192 MB)
avail memory = 7841800192 (7478 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, cfcf (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0:  on acpi0
cpu1:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  port 0xf800-0xf8ff mem 
0xd000-0xdfff,0xfdfc-0xfdff irq 18 at device 1.0 on pci0
pci0:  at device 1.1 (no driver attached)
pcib1:  irq 16 at device 4.0 on pci0
pci1:  on pcib1
pcib2:  irq 16 at device 0.0 on pci1
pci2:  on pcib2
puc0:  port 0xef00-0xef1f,0xee00-0xee0f irq 16 at device 8.0 on 
pci2
puc0: [FILTER]
uart0: <16950 or compatible> on puc0
uart0: [FILTER]
uart1: <16950 or compatible> on puc0
uart1: [FILTER]
ahci0:  port 
0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 
0xfe02f000-0xfe02f3ff irq 19 at device 17.0 on pci0
ahci0: [ITHREAD]
ahci0: AHCI v1.20 with 4 6Gbps ports, Port Multiplier supported
ahcich0:  at channel 0 on ahci0
ahcich0: [ITHREAD]
ahcich1:  at channel 1 on ahci0
ahcich1: [ITHREAD]
ahcich2:  at channel 2 on ahci0
ahcich2: [ITHREAD]
ahcich3:  at channel 3 on ahci0
ahcich3: [ITHREAD]
ohci0:  mem 0xfe02e000-0xfe02efff irq 18 at 
device 18.0 on pci0
ohci0: [ITHREAD]
usbus0:  on ohci0
ehci0:  mem 0xfe02d000-0xfe02d0ff irq 17 at 
device 18.2 on pci0
ehci0: [ITHREAD]
usbus1: EHCI version 1.0
usbus1:  on ehci0
ohci1:  mem 0xfe02c000-0xfe02cfff irq 18 at 
device 19.0 on pci0
ohci1: [ITHREAD]
usbus2:  on ohci1
ehci1:  mem 0xfe02b000-0xfe02b0ff irq 17 at 
device 19.2 on pci0
ehci1: [ITHREAD]
usbus3: EHCI version 1.0
usbus3:  on ehci1
pci0:  at device 20.0 (no driver attached)
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 

Re: mps driver instability under stable/8

2011-05-10 Thread Daniel Kalchev



On 03.05.11 20:28, Dmitry Morozovsky wrote:

Well, using
http://kb.lsi.com/KnowledgebaseArticle16414.aspx
I downgraded to version 8-fixed, and at least topology errors disappear.

Would this work with the Supermicro integrated LSI2008, like in 
X8DTH-6F? Mine came with firmware version 7, is there instability to be 
expected?


Daniel
___
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: df -t is broken?

2011-05-10 Thread Mark Felder

Here's what happens when I try to truss a df -t

http://paste.feld.me/3jb4c@raw


Regards,


Mark
___
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"


df -t is broken?

2011-05-10 Thread Mark Felder
Ok, not sure if this really belongs on the STABLE mailing list but we'll  
see if you can help:


- I was originally running FreeBSD 8.2-RELEASE
- I patched my 8.2 source with the patches here:  
http://blog.vx.sk/archives/24-Backported-patches-for-FreeBSD-82-RELEASE.html
- I built my system with "make buildworld && make buildkernel" and then  
installed both; rebooted. I know this isn't the norm, but I'm still  
running 8.2-RELEASE except these specific bugfixes so there really is no  
need for mergemaster

- Now df -t doesn't work


I noticed weird processes hanging and a few other things not running  
normally (monitoring). Turns out that anything that uses df -t just hangs  
(xymon, periodic, crons, find seems to hang when excluding filesystems)...  
doesn't matter what parameters you give it, it just hangs. Any thoughts on  
this? Regular df -h, etc work fine



Thanks,



Mark
___
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: mps driver instability under stable/8

2011-05-10 Thread Dmitry Morozovsky
On Tue, 10 May 2011, Daniel Kalchev wrote:

DK> > Well, using
DK> > http://kb.lsi.com/KnowledgebaseArticle16414.aspx
DK> > I downgraded to version 8-fixed, and at least topology errors disappear.
DK> > 
DK> Would this work with the Supermicro integrated LSI2008, like in X8DTH-6F?
DK> Mine came with firmware version 7, is there instability to be expected?

I suppose you can upgrade to "fixed" firmware from the URL above; at least, I'd 
been in mostly the same situation: SM server with onboard LSI and LSI expander, 
and so far flashing 8-fixed firmware is good for me, at least machine did not 
hang in find-related tasks as it were before...

-- 
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***

___
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"