Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: > on 30/09/2010 02:27 Don Lewis said the following: >> I tried enabling apic and got worse results. I saw ping RTTs as high as >> 67 seconds. Here's the timer info with apic enabled: [snip] >> Here's the verbose boot info with apic: >>

Re: Problem running 8.1R on KVM with AMD hosts

On Thu, 2010-09-30 at 18:55 -0400, Jung-uk Kim wrote: > It seems MCA capability is advertised by the CPUID translator but > writing to the MSRs causes GPF. In other words, it seems like a CPU > emulator bug. A simple workaround is 'set hw.mca.enabled=0' from the > loader prompt. If it works,

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

On Sep 30, 2010, at 3:56 AM, Jeremy Chadwick wrote: > The diff is pretty obvious/simple (2 line change), so the other > databases/mysqlXX-server ports can be upgraded in the same manner. > > --- files/mysql-server.sh.in.orig 2010-03-27 03:24:53.0 -0700 > +++ files/mysql-server.sh.in

Re: Problem running 8.1R on KVM with AMD hosts

On Thu, Sep 30, 2010 at 07:57:51PM +0100, Luke Marsden wrote: > Hi FreeBSD-stable, > > > > 1. Please, build your kernel with debug symbols. > > > 2. Show kgdb output > > I could not convince the kernel to dump (it was looping forever but not > panicing), but I have managed to compiled a kernel wi

Re: Problem running 8.1R on KVM with AMD hosts

On Thursday 30 September 2010 02:57 pm, Luke Marsden wrote: > Hi FreeBSD-stable, > > > > 1. Please, build your kernel with debug symbols. > > > 2. Show kgdb output > > I could not convince the kernel to dump (it was looping forever but > not panicing), but I have managed to compiled a kernel with >

Re: Problem running 8.1R on KVM with AMD hosts

Hi FreeBSD-stable, > > 1. Please, build your kernel with debug symbols. > > 2. Show kgdb output I could not convince the kernel to dump (it was looping forever but not panicing), but I have managed to compiled a kernel with debugging symbols and DDB which immediately drops into the debugger when

Re: MCA messages in dmesg

On Thu, Sep 30, 2010 at 12:25 PM, John Baldwin wrote: > Ok, it is a memory error of some sort, but mcelog claims it is a > transaction > timeout rather than an ECC error, per se: > > > I've no idea what specific hardware is busted (memory or motherboard or > CPU), > but I suspect something is li

Re: MCA messages in dmesg

On Thursday, September 30, 2010 12:33:24 pm Adam Vande More wrote: > On Thu, Sep 30, 2010 at 8:40 AM, John Baldwin wrote: > > > On Thursday, September 30, 2010 2:49:24 am Adam Vande More wrote: > > > For awhile now, my home server has been acting up. Actually it had a bad > > > set of RAM long a

Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE

On Thursday, September 30, 2010 10:53:14 am Vitaly Magerya wrote: > John Baldwin wrote: > > A true uncorrected machine check would trigger a MC# fault and panic. I > > think > > this is just garbage in the MCx banks. Are you running the latest > > 8-stable? > > No, 8.1-RELEASE. Ok, that al

Re: MCA messages in dmesg

On Thu, Sep 30, 2010 at 8:40 AM, John Baldwin wrote: > On Thursday, September 30, 2010 2:49:24 am Adam Vande More wrote: > > For awhile now, my home server has been acting up. Actually it had a bad > > set of RAM long ago, replaced and it and worked fine. It's been weird > again > > now, and I'

Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE

John Baldwin wrote: > A true uncorrected machine check would trigger a MC# fault and panic. I > think > this is just garbage in the MCx banks. Are you running the latest 8-stable? No, 8.1-RELEASE. ___ freebsd-stable@freebsd.org mailing list http://

Re: MCA messages in dmesg

On Thursday, September 30, 2010 2:49:24 am Adam Vande More wrote: > For awhile now, my home server has been acting up. Actually it had a bad > set of RAM long ago, replaced and it and worked fine. It's been weird again > now, and I've found this in dmesg: > > MCA: Bank 0, Status 0xf20008

Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE

On Tuesday, September 28, 2010 3:57:01 pm Vitaly Magerya wrote: > Jung-uk Kim wrote: > >> - the mouse doesn't work until I restart moused manually > > > > I always use hint.psm.0.flags="0x6000" in /boot/loader.conf, i.e., > > turn on both HOOKRESUME and INITAFTERSUSPEND, to work around similar >

Re: fetch: Non-recoverable resolver failure

Jeremy Chadwick wrote: On Tue, Sep 28, 2010 at 10:59:04PM +0200, Miroslav Lachman wrote: Jeremy Chadwick wrote: On Tue, Sep 28, 2010 at 08:12:00PM +0200, Miroslav Lachman wrote: Hi, we are using fetch command from cron to run PHP scripts periodically and sometimes cron sends error e-mails lik

Re: RELENG_7 em problems (and RELENG_8)

At 08:00 PM 9/26/2010, Jack Vogel wrote: The system I've had stress tests running on has 82574 LOMs, so I hope it will solve the problem, will see tomorrow morning at how things have held up... I pulled a copy of sys/dev/e1000 from HEAD and copied onto my RELENG_8 box. I had another nic lock u

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: > on 30/09/2010 02:27 Don Lewis said the following: > vmstat -i ? I didn't see anything odd in the vmstat -i output that I posted to the list earlier. It looked more or less normal as the ntp offset suddenly went insane. >> I did manage to catch the problem with

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

On Thu, Sep 30, 2010 at 08:53:07AM -0400, Paul Mather wrote: > On Sep 30, 2010, at 3:56 AM, Jeremy Chadwick wrote: > > > The diff is pretty obvious/simple (2 line change), so the other > > databases/mysqlXX-server ports can be upgraded in the same manner. > > > > --- files/mysql-server.sh.in.orig

[releng_8_0 tinderbox] failure on mips/mips

TB --- 2010-09-30 08:54:21 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-30 08:54:21 - starting RELENG_8_0 tinderbox run for mips/mips TB --- 2010-09-30 08:54:21 - cleaning the object tree TB --- 2010-09-30 08:56:19 - cvsupping the source tree TB --- 2010-09-30 08:56:19 - /usr

[releng_8_0 tinderbox] failure on ia64/ia64

TB --- 2010-09-30 08:07:07 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-30 08:07:07 - starting RELENG_8_0 tinderbox run for ia64/ia64 TB --- 2010-09-30 08:07:07 - cleaning the object tree TB --- 2010-09-30 08:10:48 - cvsupping the source tree TB --- 2010-09-30 08:10:48 - /usr

Re: Diskless/readonly root booting issues

> Hi all, > > I've been working on updating my semi-embedded images to > 7.3-stable of late (I generally wait for .3+ releases), it's been a > few years since the last time I did one of these and I'm having some > issues getting my netboot test environment to behave itself. > > I'm sure i

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

Jeremy Chadwick ha scritto: > Until rc(8) can be updated to support daemon(8) natively, This would be the Right Thing IMHO. > the ~76 ports > which Do The Wrong Thing(tm) should get updated to do it this way. Ones > like mysqlXX-server should be placed high on the priority list given > their pop

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

On Thu, Sep 30, 2010 at 09:30:25AM +0200, Alex Dupre wrote: > Jeremy Chadwick ha scritto: > > Until rc(8) can be updated to support daemon(8) natively, > > This would be the Right Thing IMHO. > > > the ~76 ports > > which Do The Wrong Thing(tm) should get updated to do it this way. Ones > > like

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

On Thu, Sep 30, 2010 at 09:03:33AM +0200, Ed Schouten wrote: > Hi Jeremy, > > * Jeremy Chadwick wrote: > > 1) "mysqld_safe > /dev/null 2>&1 &" never released the tty > > 2) "nohup mysqld_safe > /dev/null 2>&1 &" did release the tty > > What happens if you run the following command? > > da

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

Hi Jeremy, * Jeremy Chadwick wrote: > 1) "mysqld_safe > /dev/null 2>&1 &" never released the tty > 2) "nohup mysqld_safe > /dev/null 2>&1 &" did release the tty What happens if you run the following command? daemon -cf mysqld_safe The point is that FreeBSD's pts(4) driver only dealloca

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

On Thu, Sep 30, 2010 at 1:51 AM, Jeremy Chadwick wrote: > Something interesting I've come across which happens on both RELENG_7 > and RELENG_8 (indicating it's not a problem with the older tty code or > the newer pty/pts code), and it's reproducible on Linux (sort of...). > > mysqld_safe appears t