Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Ruben van Staveren
Hi, On 18 Jul 2010, at 4:20, Sean wrote: On 18/07/2010 1:24 AM, Alex Kozlov wrote: Hi, stable After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE [snip] I'm getting the same thing; what shell are you using? I changed my shell on one

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Jeremy Chadwick
On Tue, Jul 20, 2010 at 09:19:39AM +0200, Ruben van Staveren wrote: To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. Too late for that now... ftp://ftp4.freebsd.org/pub/FreeBSD/releases/amd64/ ftp://ftp4.freebsd.org/pub/FreeBSD/releases/i386/ --

Re: 8.1-RC2 MCE caused by some LAPIC/clock changes? (was: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?)

2010-07-20 Thread jhell
On Sat, 17 Jul 2010 14:35, Markus Gebert wrote: In Message-Id: f744f475-3d2b-4bc6-856a-a5d302aa8...@hostpoint.ch On 13.07.2010, at 16:02, Markus Gebert wrote: Unfortunately, I have not been able to get anything useful out the svn commit logs, which could explain this. Maybe someone else has

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Sean
On 20/07/2010, at 5:19 PM, Ruben van Staveren wrote: Hi, This happens during a sudo portupgrade -va --batch my shell is /bin/tcsh too. When I run exec bash after sudo -s and then do the portupgrade the problem doesn't show up. To me, this is a clear breakage and should be considered a

Re: Problems replacing failing drive in ZFS pool

2010-07-20 Thread Andriy Gapon
on 20/07/2010 01:04 Garrett Moore said the following: Well, hotswapping worked, but now I have a totally different problem. Just for reference: # zpool offline tank da3 # camcontrol stop da3 swap drive # camcontrol rescan all 'da3 lost device, removing device entry' # camcontrol rescan all

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Ruben van Staveren
On 20 Jul 2010, at 10:03, Jeremy Chadwick wrote: On Tue, Jul 20, 2010 at 09:19:39AM +0200, Ruben van Staveren wrote: To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. Too late for that now… Oh well, errata when the culprit is found… I've filed

Re: Problems replacing failing drive in ZFS pool

2010-07-20 Thread Pawel Tyll
Hi guys, I second what others have said - crap. But there could be some hope, not sure. Can you check what is the actual size used by the pool on the disk? It should be somewhere in zdb -C output (asize?). If I remember correctly, that actual size should be a multiple of some rather large

today's 8.1/i386: panic: bad pte

2010-07-20 Thread Mikhail T.
Some part of KDE4's kdm crashed at start-up and seems to have taken the entire machine with it: kgdb /boot/kernel/kernel /var/crash/vmcore.22 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and

Re: panic: handle_written_inodeblock: bad size

2010-07-20 Thread Jeremy Chadwick
On Mon, Jul 19, 2010 at 01:41:24PM -0700, Jeremy Chadwick wrote: On Mon, Jul 19, 2010 at 11:55:59AM -0400, Mikhail T. wrote: 19.07.2010 07:31, Jeremy Chadwick написав(ла): If you boot the machine in single-user, and run fsck manually, are there any errors? Thanks, Jeremy... I wish, there

Re: today's 8.1/i386: panic: bad pte

2010-07-20 Thread Alan Cox
On Mon, Jul 19, 2010 at 11:40 PM, Mikhail T. mi+t...@aldan.algebra.commi%2bt...@aldan.algebra.com wrote: Some part of KDE4's kdm crashed at start-up and seems to have taken the entire machine with it: kgdb /boot/kernel/kernel /var/crash/vmcore.22 GNU gdb 6.1.1 [FreeBSD] Copyright

Re: today's 8.1/i386: panic: bad pte

2010-07-20 Thread Alan Cox
Mikhail T. wrote: 20.07.2010 12:47, Alan Cox написав(ла): Historically, this panic has indicated flakey memory. This panic occurs because a memory location within a page table has unexpectedly changed to zero. Ouch... Thanks for the hint (maybe, the panic should say something like that?)

Re: today's 8.1/i386: panic: bad pte

2010-07-20 Thread Mikhail T.
20.07.2010 12:47, Alan Cox написав(ла): Historically, this panic has indicated flakey memory. This panic occurs because a memory location within a page table has unexpectedly changed to zero. Ouch... Thanks for the hint (maybe, the panic should say something like that?) In any case, is

Re: 8.1-RC2 MCE caused by some LAPIC/clock changes? (was: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?)

2010-07-20 Thread John Baldwin
On Saturday, July 17, 2010 2:35:21 pm Markus Gebert wrote: On 13.07.2010, at 16:02, Markus Gebert wrote: Unfortunately, I have not been able to get anything useful out the svn commit logs, which could explain this. Maybe someone else has an idea what could have changed between 7 and 8 to

Re: 8.1-RC2 MCE caused by some LAPIC/clock changes? (was: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?)

2010-07-20 Thread Markus Gebert
On 20.07.2010, at 10:15, jhell wrote: Any ideas how to proceed? Adding to this I remembered some specific commits that caught my attention when they happened. Specifically they were to mca.c (locate mca) on my machine provided the file paths and svn log provided the commit log. When

Re: 8.1-RC2 MCE caused by some LAPIC/clock changes? (was: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?)

2010-07-20 Thread Markus Gebert
On 20.07.2010, at 21:59, John Baldwin wrote: I started narrowing the revisions down until I found out, that while on r202386 I'm still able to trigger the MCE, r202387 seems to solve the problem on CURRENT: http://svn.freebsd.org/viewvc/base?view=revisionrevision=202387 Although this

Re: Problems replacing failing drive in ZFS pool

2010-07-20 Thread alan bryan
--- On Mon, 7/19/10, Dan Langille d...@langille.org wrote: From: Dan Langille d...@langille.org Subject: Re: Problems replacing failing drive in ZFS pool To: Freddie Cash fjwc...@gmail.com Cc: freebsd-stable freebsd-stable@freebsd.org Date: Monday, July 19, 2010, 7:07 PM On 7/19/2010