NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/51087: panic: m_copym: off -2074581028, len 1448
The following reply was made to PR kern/51087; it has been noted by GNATS.
From: Sean Davis <dive%hq.endersgame.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc:
Subject: Re: kern/51087: panic: m_copym: off -2074581028, len 1448
Date: Fri, 3 Jun 2016 19:45:27 -0500
I will give it a try reproducing it again -- hasn't happened on its own yet=
so I may have to poke it. :)
Here's the current kernel config: (I'm running with vlans, NO ipv6, +NFS):
# $egnet: PHOENIX,v 1.39 2015/08/28 16:36:46 dive Exp $
##############################################
## phoenix.endersgame.net // netbsd-7 amd64 ##
##############################################
## AMD Phenom 9150e 4 x 1.8ghz, 4GB RAM ##
##############################################
##############################################################
## DEFAULT INCLUDES: DO NOT REMOVE ANYTHING IN THIS SECTION ##
##############################################################
include "arch/amd64/conf/std.amd64"
###################################
## SYSTEM-SPECIFIC CONFIGURATION ##
###################################
ident "PHOENIX"
maxusers 64
#makeoptions DEBUG=3D"-g"
makeoptions COPTS=3D"-O2 -fno-omit-frame-pointer"
options INSECURE
#options ATADEBUG
options CPURESET_DELAY=3D2000
options RTC_OFFSET=3D0
options NTP
options CPU_UCODE
options SYSVMSG
options SYSVSEM
options SYSVSHM
options P1003_1B_SEMAPHORE
options MODULAR
options RAID_AUTOCONFIG
options DKWEDGE_AUTODISCOVER
options DKWEDGE_METHOD_GPT
options DKWEDGE_METHOD_BSDLABEL
options DKWEDGE_METHOD_MBR
options WAPBL
options INET
options WSEMUL_VT100
options WS_KERNEL_FG=3DWSCOL_GREEN
options WSDISPLAY_COMPAT_PCVT
options WSDISPLAY_COMPAT_SYSCONS
options PCKBD_CNATTACH_MAY_FAIL
options ACPI_SCANPCI
options MPBIOS
options MPBIOS_SCANPCI
options VCONS_DRAW_INTR
options VGA_POST
options NFSSERVER
options PFIL_HOOKS
options KTRACE
options BUFQ_READPRIO
options BUFQ_PRIOCSCAN
options BUFCACHE=3D30
options NMBCLUSTERS=3D262144
file-system FFS
file-system PTYFS
file-system TMPFS
file-system NFS
config netbsd root on ? type ffs
acpicpu* at cpu?
acpi0 at mainbus0
acpibut* at acpi?
acpifan* at acpi?
acpitz* at acpi?
attimer* at acpi?
hpet* at acpihpetbus?
hpet* at acpinodebus?
pci* at mainbus? bus ?
pci* at pchb? bus ?
pci* at ppb? bus ?
pchb* at pci? dev ? function ?
pcib* at pci? dev ? function ?
ppb* at pci? dev ? function ?
isa0 at pcib?
vga* at pci? dev ? function ?
wsdisplay* at vga? console ?
amdnb_misc* at pci?
amdtemp* at amdnb_misc?
nfsmbc* at pci? dev ? function ?
nfsmb* at nfsmbc?
iic* at nfsmb?
spdmem* at iic? addr 0x50
spdmem* at iic? addr 0x51
spdmem* at iic? addr 0x52
spdmem* at iic? addr 0x53
viaide* at pci? dev ? function ?
atabus* at ata?
wd* at atabus? drive ? flags 0x0000
skc* at pci? dev ? function ?
sk* at skc?
nfe* at pci?
ciphy* at mii?
icsphy* at mii?
makphy* at mii?
rlphy* at mii?
ehci* at pci? dev ? function ?
ohci* at pci? dev ? function ?
usb* at ehci?
usb* at ohci?
uhub* at usb?
uhub* at uhub? port ?
uhidev* at uhub? port ? configuration ? interface ?
uhid* at uhidev? reportid ?
ukbd* at uhidev? reportid ?
wskbd* at ukbd? console ? mux 1
pseudo-device raid 1
pseudo-device bpfilter
pseudo-device loop
pseudo-device accf_data
pseudo-device accf_http
pseudo-device pty
pseudo-device clockctl
pseudo-device ksyms
pseudo-device wsmux
pseudo-device wsfont
pseudo-device drvctl
pseudo-device vlan
pseudo-device crypto
pseudo-device swcrypto
pseudo-device npf
On Tue, May 31, 2016 at 06:25:01AM +0000, David Holland wrote:
> The following reply was made to PR kern/51087; it has been noted by GNATS.
>=20
> From: David Holland <dholland-bugs%netbsd.org@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc:=20
> Subject: Re: kern/51087: panic: m_copym: off -2074581028, len 1448
> Date: Tue, 31 May 2016 06:20:42 +0000
>=20
> On Fri, Apr 22, 2016 at 06:35:00PM +0000, dive%endersgame.net@localhost wrote:
> > >Synopsis: kernel panic in m_copym
> > I noticed this morning that this machine had rebooted. I was not
> > doing anything unusual at the time; I don't know what triggered i=
t,
> =20
> It would help to know what networking features you are (or aren't)
> using, and possibly what you put in your custom kernel config.
> =20
> Also any other information that may have been left in the logs would
> be helpful.
> =20
> The actual panic message was a good start though -- many people forget
> that :-)
> =20
> --=20
> David A. Holland
> dholland%netbsd.org@localhost
> =20
>=20
Home |
Main Index |
Thread Index |
Old Index