Re: sparc64 on stable/10 panics with r299673

2016-05-13 Thread Kurt Lidl

On 5/13/16 5:10 PM, Mark Johnston wrote:

On Fri, May 13, 2016 at 04:14:34PM -0400, Kurt Lidl wrote:

I updated one of my sparc64 machines (a V240, dual processor, 8GB
of memory) and now it panics.

Before (working without issue):
FreeBSD spork.pix.net 10.3-STABLE FreeBSD 10.3-STABLE #18 r299561: Thu
May 12 16:28:16 EDT 2016
l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC  sparc64


Hi,

Could you give r299695 a try? It fixes a bug that looks related to what
you're hitting.



I updated to r299698, and that does boot successfully.  The rest of
'make installworld' is now running.

Thanks!

-Kurt

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


Re: sparc64 on stable/10 panics with r299673

2016-05-13 Thread Mark Johnston
On Fri, May 13, 2016 at 04:14:34PM -0400, Kurt Lidl wrote:
> I updated one of my sparc64 machines (a V240, dual processor, 8GB
> of memory) and now it panics.
> 
> Before (working without issue):
> FreeBSD spork.pix.net 10.3-STABLE FreeBSD 10.3-STABLE #18 r299561: Thu 
> May 12 16:28:16 EDT 2016 
> l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC  sparc64

Hi,

Could you give r299695 a try? It fixes a bug that looks related to what
you're hitting.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: sparc64 on stable/10 panics with r299673

2016-05-13 Thread Kurt Lidl

On 5/13/16 4:14 PM, Kurt Lidl wrote:

I updated one of my sparc64 machines (a V240, dual processor, 8GB
of memory) and now it panics.

Before (working without issue):
FreeBSD spork.pix.net 10.3-STABLE FreeBSD 10.3-STABLE #18 r299561: Thu
May 12 16:28:16 EDT 2016
l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC  sparc64

Updated (panics during boot):
lidl@spork-114: svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: svn://hydra.pix.net/stable/10
Relative URL: ^/stable/10
Repository Root: svn://hydra.pix.net
Repository UUID: 13f3649d-50b2-e011-b72e-0019bb358710
Revision: 299673
Node Kind: directory
Schedule: normal
Last Changed Author: ngie
Last Changed Rev: 299651
Last Changed Date: 2016-05-13 05:52:39 -0400 (Fri, 13 May 2016)



Here's what the boot looks like with boot_verbose set at the loader prompt:

-Kurt

jumping to kernel entry at 0xc00a8000.
Copyright (c) 1992-2016 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 10.3-STABLE #19 r299673: Fri May 13 12:24:06 EDT 2016
l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC sparc64
gcc version 4.2.1 20070831 patched [FreeBSD]
Preloaded elf kernel "/boot/kernel/kernel" at 0xc14a8000.
Preloaded elf module "/boot/kernel/zfs.ko" at 0xc14a8b78.
Preloaded elf module "/boot/kernel/opensolaris.ko" at 0xc14a9150.
Preloaded elf module "/boot/kernel/geom_mirror.ko" at 0xc14a96f0.
real memory  = 8589934592 (8192 MB)
avail memory = 8379719680 (7991 MB)
machine: SUNW,Sun-Fire-V240
cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU)
mask=0x34 maxtl=5 maxwin=7
initalizing intr_countp
cpu1: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU)
mask=0x34 maxtl=5 maxwin=7
INTR: Adding CPU 1 as a target
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Falling back to  random adaptor
random:  initialized
ULE: setup cpu 0
ULE: setup cpu 1
snd_unit_init() u=0x00ff8000 [512] d=0x7c00 [32] c=0x03ff [1024]
feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 
feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25

wlan: <802.11 Link Layer>
firmware: 'isp_1000' version 1: 20142 bytes loaded at 0xc093d890
firmware: 'isp_1040' version 1: 22944 bytes loaded at 0xc094273e
firmware: 'isp_1080' version 1: 31350 bytes loaded at 0xc09480de
firmware: 'isp_12160' version 1: 28050 bytes loaded at 0xc094fb54
firmware: 'isp_2100' version 1: 76770 bytes loaded at 0xc09568e6
firmware: 'isp_2200' version 1: 84566 bytes loaded at 0xc09694c8
firmware: 'isp_2300' version 1: 125252 bytes loaded at 0xc097df1e
firmware: 'isp_2322' version 1: 120814 bytes loaded at 0xc099c862
firmware: 'isp_2400' version 1: 204384 bytes loaded at 0xc09bdbc8
firmware: 'isp_2500' version 1: 223908 bytes loaded at 0xc09fd5f8
kbd0 at kbdmux0
mem: 
openfirm: 
null: 
nfslock: pseudo-device
nexus0: 
pcib0:  mem 
0x4000ff0-0x4000ff0afff,0x4000fc1-0x4000fc1701f,0x7f6-0x7f600ff,0x4000ff8-0x4000ff8 
irq 2035,2032,2033,2036,2019 on nexus0

pcib0: Tomatillo, version 4, IGN 0x1f, bus B, PCI mode, 66MHz
pcib0: DVMA map: 0xc000 to 0xdfff 65536 entries
pcib0: PROM IOTSB size: 1 (2048 entries)
pcib0: bus range 0 to 0; PCI bus 0
pci0:  on pcib0
pci0: domain=0, physical bus=0
found->  vendor=0x108e, dev=0xa801, revid=0x00
domain=0, bus=0, slot=0, func=0
class=06-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->  vendor=0x14e4, dev=0x1648, revid=0x00
domain=0, bus=0, slot=2, func=0
class=02-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
intpin=a, irq=255
powerspec 2  supports D0 D3  current D0
MSI supports 8 messages, 64 bit
map[10]: type Memory, range 64, base 0x20, size 16, memory disabled
map[18]: type Memory, range 64, base 0x11, size 16, enabled
found->  vendor=0x14e4, dev=0x1648, revid=0x00
domain=0, bus=0, slot=2, func=1
class=02-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x, statreg=0x02b0, cachelnsz=16 (dwords)
lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns)
intpin=b, irq=255
powerspec 2  supports D0 D3  current D0
MSI supports 8 messages, 64 bit
map[10]: type Memory, range 64, base 0x40, size 16, memory disabled
map[18]: type Memory, range 64, base 0x12, size 16, enabled
pcib1:  mem 
0x4000f60-0x4000f60afff,0x4000f41-0x4000f41701f,0x7fe-0x7fe00ff,0x4000f78-0x4000f78 
irq 1970,1968,1969,1972,1953 on nexus0

pcib1: Tomatillo, version 4, IGN 0x1e, bus A, PCI mode, 33MHz
Timecounter "pcib1" frequency 16700 Hz quality -100
pcib1: DVMA map: 0xc000 to 0xdfff 65536 entries
pcib1: PROM IOTSB size: 1 (2048 entries)
pcib1: bus range 0 to 0; PCI bus 0
pci1:  

sparc64 on stable/10 panics with r299673

2016-05-13 Thread Kurt Lidl

I updated one of my sparc64 machines (a V240, dual processor, 8GB
of memory) and now it panics.

Before (working without issue):
FreeBSD spork.pix.net 10.3-STABLE FreeBSD 10.3-STABLE #18 r299561: Thu 
May 12 16:28:16 EDT 2016 
l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC  sparc64


Updated (panics during boot):
lidl@spork-114: svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: svn://hydra.pix.net/stable/10
Relative URL: ^/stable/10
Repository Root: svn://hydra.pix.net
Repository UUID: 13f3649d-50b2-e011-b72e-0019bb358710
Revision: 299673
Node Kind: directory
Schedule: normal
Last Changed Author: ngie
Last Changed Rev: 299651
Last Changed Date: 2016-05-13 05:52:39 -0400 (Fri, 13 May 2016)

Boot messages from where it panics:

- snip, snip -
jumping to kernel entry at 0xc00a8000.
Copyright (c) 1992-2016 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 10.3-STABLE #19 r299673: Fri May 13 12:24:06 EDT 2016
l...@spork.pix.net:/usr/obj/usr/src/sys/GENERIC sparc64
gcc version 4.2.1 20070831 patched [FreeBSD]
real memory  = 8589934592 (8192 MB)
avail memory = 8379719680 (7991 MB)
cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU)
cpu1: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
random:  initialized
kbd0 at kbdmux0
nexus0: 
pcib0:  mem 
0x4000ff0-0x4000ff0afff,0x4000fc1-0x4000fc1701f,0x7f6-0x7f600ff,0x4000ff8-0x4000ff8 
irq 2035,2032,2033,2036,2019 on nexus0

pcib0: Tomatillo, version 4, IGN 0x1f, bus B, PCI mode, 66MHz
pcib0: DVMA map: 0xc000 to 0xdfff 65536 entries
pci0:  on pcib0
pcib1:  mem 
0x4000f60-0x4000f60afff,0x4000f41-0x4000f41701f,0x7fe-0x7fe00ff,0x4000f78-0x4000f78 
irq 1970,1968,1969,1972,1953 on nexus0

pcib1: Tomatillo, version 4, IGN 0x1e, bus A, PCI mode, 33MHz
pcib1: DVMA map: 0xc000 to 0xdfff 65536 entries
pci1:  on pcib1
pcib2:  mem 
0x4000e60-0x4000e60afff,0x4000e41-0x4000e41701f,0x7ce-0x7ce00ff,0x4000e78-0x4000e78 
irq 1842,1840,1841,1844,1827 on nexus0

pcib2: Tomatillo, version 4, IGN 0x1c, bus A, PCI mode, 66MHz
pcib2: DVMA map: 0xc000 to 0xdfff 65536 entries
pci2:  on pcib2
pcib3:  mem 
0x4000ef0-0x4000ef0afff,0x4000ec1-0x4000ec1701f,0x7c6-0x7c600ff,0x4000ef8-0x4000ef8 
irq 1907,1904,1905,1908,1893 on nexus0

pcib3: Tomatillo, version 4, IGN 0x1d, bus B, PCI mode, 66MHz
pcib3: DVMA map: 0xc000 to 0xdfff 65536 entries
pci3:  on pcib3
nexus0:  mem 0x400-0x407 type 
memory-controller (no driver attached)
nexus0:  mem 0x480-0x487 type 
memory-controller (no driver attached)
bge0:  mem 
0x20-0x20,0x11-0x11 at device 2.0 on pci0
bge0: CHIP ID 0x2003; ASIC REV 0x02; CHIP REV 0x20; PCI on PCI-X 66 
MHz; 64bit

miibus0:  on bge0
brgphy0:  PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow

bge0: Ethernet address: 00:03:ba:e0:ce:07
bge1:  mem 
0x40-0x40,0x12-0x12 at device 2.1 on pci0
bge1: CHIP ID 0x2003; ASIC REV 0x02; CHIP REV 0x20; PCI on PCI-X 66 
MHz; 64bit

miibus1:  on bge1
brgphy1:  PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow

bge1: Ethernet address: 00:03:ba:e0:ce:08
isab0:  at device 7.0 on pci1
isa0:  on isab0
pci1:  at device 6.0 (no driver attached)
ohci0:  mem 
0x100-0x1000fff at device 10.0 on pci1

usbus0 on ohci0
atapci0:  port 
0x900-0x907,0x918-0x91b,0x910-0x917,0x908-0x90b,0x920-0x92f at device 
13.0 on pci1
atapci0: using PIO transfers above 137GB as workaround for 48bit DMA 
access bug, expect reduced performance

ata2:  at channel 0 on atapci0
ata3:  at channel 1 on atapci0
sym0: <1010-66> port 0x900-0x9ff mem 0x10-0x1003ff,0x102000-0x103fff 
at device 2.0 on pci2

sym0: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym1: <1010-66> port 0xa00-0xaff mem 0x104000-0x1043ff,0x106000-0x107fff 
at device 2.1 on pci2

sym1: No NVRAM, ID 7, Fast-80, LVD, parity checking
bge2:  mem 
0x20-0x20,0x11-0x11 at device 2.0 on pci3
bge2: CHIP ID 0x2003; ASIC REV 0x02; CHIP REV 0x20; PCI on PCI-X 66 
MHz; 64bit

miibus2:  on bge2
brgphy2:  PHY 1 on miibus2
brgphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow

bge2: Ethernet address: 00:03:ba:e0:ce:09
bge3:  mem 
0x40-0x40,0x12-0x12 at device 2.1 on pci3
bge3: CHIP ID 0x2003; ASIC REV 0x02; CHIP REV 0x20; PCI on PCI-X 66 
MHz; 64bit

miibus3: