Re: Panic during kernel boot, igb-init related? (8.3-RELEASE)

On 11/1/12 2:25 AM, Eugene Grosbein wrote: 31.10.2012 23:58, Charles Owens пишет: Hello, We're seeing boot-time panics in about 4% of cases when upgrading from FreeBSD 8.1 to 8.3-RELEASE (i386). This problem is subtle enough that it escaped detection during our regular testing cycle... now

Panic during kernel boot, igb-init related? (8.3-RELEASE)

at igb_refresh_mbufs+0x25e #3 0xc03c9f98 at igb_rxeof+0x638 #4 0xc03ca135 at igb_msix_que+0x105 #5 0xc0541e2b at intr_event_execute_handlers+0x13b #6 0xc05434eb at ithread_loop+0x6b #7 0xc053efb7 at fork_exit+0x97 #8 0xc0806744 at fork_trampoline+0x8 Thanks very much, Charles -- Charles Owens Great

Re: ? IO performance regression, post 8.1

Charles Owens Great Bay Software, Inc. v: 603.617.4844 m: 603.866.0860 On 6/22/12 10:22 AM, John Baldwin wrote: On Thursday, June 21, 2012 10:36:04 pm Charles Owens wrote: On 6/15/12 8:04 AM, John Baldwin wrote: On Friday, June 15, 2012 12:28:59 am Charles Owens wrote: Hello FreeBSD folk

re: disk IO performance regression, post 8.1

On 6/22/12 10:22 AM, John Baldwin wrote: On Thursday, June 21, 2012 10:36:04 pm Charles Owens wrote: On 6/15/12 8:04 AM, John Baldwin wrote: On Friday, June 15, 2012 12:28:59 am Charles Owens wrote: Hello FreeBSD folk, We're seeing what appears to be a storage performance regression as we

Re: mfi(4) IO performance regression, post 8.1

On 6/15/12 8:04 AM, John Baldwin wrote: On Friday, June 15, 2012 12:28:59 am Charles Owens wrote: Hello FreeBSD folk, We're seeing what appears to be a storage performance regression as we try to move from 8.1 (i386) to 8.3. We looked at 8.2 also and it appears that the regression happened

Re: mfi(4) IO performance regression, post 8.1

Yes, of course. So far I can say that the major shift appears to have occurred between 8.1 and 8.2 . Thanks, Charles Owens Great Bay Software, Inc. Sent from my phone - Reply message - From: Adrian Chadd adr...@freebsd.org To: Charles Owens cow...@greatbaysoftware.com Cc: sta

Re: mfi(4) IO performance regression, post 8.1

No reason other than history... will be changing over at some point. Charles Owens Great Bay Software, Inc. On 6/15/12 10:38 AM, Brian W. wrote: Curious why you are preferring i386 +PAE as opposed to amd64? On Jun 15, 2012 4:09 AM, Charles Owens cow...@greatbaysoftware.com mailto:cow

mfi(4) IO performance regression, post 8.1

ums1: 5 buttons and [XYZ] coordinates ID=0 ums2:ATEN International Co. Ltd GCS1808 V3.0.294, class 0/0, rev 1.10/1.00, addr 3 on usbus5 ums2: 3 buttons and [Z] coordinates ID=0 eth0: link state changed to UP -- Charles Owens Great Bay Software, Inc

superpages not solving PV entries limit warning

seeing the warning, do I need to tune something else? Other comments? System details: * 8.1-RELEASE-p2 i386 PAE kernel * 6 GB RAM Thanks very much! Charles -- Charles Owens Great Bay Software, Inc. ___ freebsd-stable@freebsd.org mailing list http

Re: superpages not solving PV entries limit warning

AM, Alan Cox wrote: On Thu, May 10, 2012 at 2:32 AM, Adam Vande More amvandem...@gmail.com mailto:amvandem...@gmail.com wrote: On Wed, May 9, 2012 at 12:55 PM, Charles Owens cow...@greatbaysoftware.com mailto:cow...@greatbaysoftware.comwrote: Hi fellow BSD-types, I

Re: superpages not solving PV entries limit warning

On 5/10/12 12:37 PM, Alan Cox wrote: On Thu, May 10, 2012 at 10:52 AM, Charles Owens cow...@greatbaysoftware.com mailto:cow...@greatbaysoftware.com wrote: That's very helpful! I had read about that and wondered if it applied to i386. Should I have expected superpages

8.0 changes behavior of who am i

? (I looked but can't find any existing threads about this issue). I'm guessing that the symptom here results somehow from the introduction of pts(4). Tnx -- Charles Owens Great Bay Software, Inc. ___ freebsd-stable@freebsd.org mailing list http

gjournal error while writing data (error=6)

# raw part, don't edit d: 54588610 1017077124.2BSD 2048 16384 28552 -- **Charles Owens** *Great Bay Software**|** ** e: *cow...@greatbaysoftware.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

READ_BIG w/DVD-pata motion? (kern/133122)

is working on it. Does anyone have a sense as to when it might be given a good look? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133122 Thanks much, Charles -- **Charles Owens** *Great Bay Software* ___ freebsd-stable@freebsd.org mailing list http

Re: READ_BIG w/DVD-pata motion? (kern/133122)

Gavin Atkinson wrote: On Mon, 2009-08-17 at 10:58 -0400, Charles Owens wrote: Just under a month ago I added a comment to this bug, to share that we're seeing this issue consistently with one of the HP appliance platforms that we support (with both FreeBSD 7.0 and 7.1). This bug (marked

Re: help with 7.0-p12 crash analysis panic: lockmgr: upgrade without shared

Kostik Belousov wrote: On Mon, May 18, 2009 at 09:39:10PM -0400, Charles Owens wrote: Hello, We had a crash of a 7.0-RELEASE-p12 running on a dual quad-core Xeon system with 6 gig RAM and mfi-based RAID. Pasted below are the output of kgdb crashdump backtrace, custom kernel config

help with 7.0-p12 crash analysis panic: lockmgr: upgrade without shared

after panic: lockmgr: upgrade without shared May 18 13:52:10 gbs01-etc savecore: writing core to vmcore.0 May 18 13:52:12 gbs01-etc kernel: eth0: link state changed to UP May 18 13:52:12 gbs01-etc kernel: eth1: link state changed to UP -- **Charles Owens** *Great Bay Software**|** m

Re: make installworld 3.2R - 3.2S fails over NFS

Rich Winkel wrote: I just cvsupped fresh sources this weekend with the same result. Does anyone else use nfs to "installworld"? Or am I the only one having this problem? From 3.0R to at least 3.1-stable I've seen this problem. The (annoying) workaround has been to do RW mounts of /usr/src