From owner-freebsd-stable@FreeBSD.ORG Thu Oct 21 23:12:56 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2CDE1065670 for ; Thu, 21 Oct 2010 23:12:56 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2D60A8FC15 for ; Thu, 21 Oct 2010 23:12:55 +0000 (UTC) Received: by wyb42 with SMTP id 42so161092wyb.13 for ; Thu, 21 Oct 2010 16:12:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=jDiEWjTqmTr+UTnmHopbbhyXDaicmdbDezgJwe0I5Qw=; b=dC82kYEKWNyw1vQ5ITEfg3yq0O2hkwb09o8DLp5C8u815zPAtCvWLORBnlNI2nN/BQ D/2fdW2Yt7liMysTIpgZ0cWMeNpVQ5ZkAEJtc72s0AY7hKj0qd9ew72eXaCkJDLsYXg7 s5fkiale4cje1gMQnFdZIkQvl7q3tSVZF+nKs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TlHRiWQ0zAJ5+Nqv7ohXnHuKFEQgHpcvf7irm6Otbkdlemwg0ACwI0jmReWXU+QJ8P cBQ0/OdSBRVvwht95B9/x+7ixY2RiJ4bcOYOiT42PGRYcTb+MSCHOZSCmMoIlD+J6ieP 44kNJrjx/zcGFvnwQrtjBehqDNwYiw8xTu+Cg= MIME-Version: 1.0 Received: by 10.216.1.17 with SMTP id 17mr10276087wec.99.1287701370751; Thu, 21 Oct 2010 15:49:30 -0700 (PDT) Received: by 10.216.232.132 with HTTP; Thu, 21 Oct 2010 15:49:30 -0700 (PDT) In-Reply-To: References: <20101021193319.GA84134@icarus.home.lan> Date: Thu, 21 Oct 2010 15:49:30 -0700 Message-ID: From: Jack Vogel To: Randy Bush Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable , Jeremy Chadwick Subject: Re: repeating crashes with 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 23:12:56 -0000 pciconf -l I need to know which hardware it is and that doesnt show me. Jack On Thu, Oct 21, 2010 at 3:28 PM, Randy Bush wrote: > em0: port 0x2000-0x201f mem > 0xe8000000-0xe801ffff irq 16 at device 0.0 on pci13 > > randy > > Jeremy Chadwick wrote: > > > > On Thu, Oct 21, 2010 at 12:08:23PM -0700, Randy Bush wrote: > > > FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 > > > root@rip.psg.com:/usr/obj/usr/src/sys/RIP amd64 > > > > > > console recording > > > > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > em0: discard frame w/o packet header > > > panic: sbflush_internal: cc 4294965301 || mb 0 || mbcnt 0 > > > cpuid = 0 > > > panic: bufwrite: buffer is not busy??? > > > > > > > > > cpuid = 0 > > > Fatal trap 12: page fault while in kernel mode > > > Uptime: cpuid = 2; 48mapic id = 02 > > > 36s > > > fault virtual address = 0xffff804000000000 > > > Physical memory: 4086 MB > > > fault code = supervisor read data, page not present > > > Dumping 1647 MB:instruction pointer = 0x20:0xffffffff804c22ae > > > (CTRL-C to abort) stack pointer = > 0x28:0xffffff80000de9a0 > > > frame pointer = 0x28:0xffffff80000de9b0 > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > current process = 0 (em0 taskq) > > > trap number = 12 > > > 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 1440 1424 > 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 1200 1184 > 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 944 928 > 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 > 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 > 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16Attempt > to write outside dump device boundaries. > > > > > > ** DUMP FAILED (ERROR 6) ** > > > Automatic reboot in 15 seconds - press a key on the console to abort > > > em0: Watchdog timeout -- resetting > > > > > > and locked up. required power cycle to reboot > > > > CC'ing Jack Vogel of Intel, who is currently re-working portions of the > > em(4) driver. I think taskq issue might be the thing he's fixing and > > thus might have a workaround for you. > > > > But we're going to need to know exactly what em(4) model you have. > > > > Please provide "dmesg" output relevant to em0, and also "pciconf -lvc" > > output for the em0@ device. > > > > -- > > | Jeremy Chadwick jdc@parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | >