On Sun, Jun 7, 2009 at 11:26 PM, Miroslav Lachman 000.f...@quip.cz wrote:
claudiu vasadi wrote:
On Sun, Jun 7, 2009 at 9:38 PM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
Jun 7 21:10:47 da1 kernel: ad6: detached
Jun 7 21:10:47 da1 kernel:
isn;t it trying to read past the end of disk?
Hmm.. I guess you are correct. The question is why is it doing this ?
because partition/slice table is wrong?
___
freebsd-stable@freebsd.org mailing list
On Mon, Jun 8, 2009 at 9:16 AM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
the type fdisk /dev/da1 and then compare the sectors values with what dmesg
says
fdisk /dev/ad2 :
*** Working on device /dev/ad2 ***
parameters extracted from in-core disklabel are:
2009/6/7 Clifton Royston clift...@lava.net:
On Sun, Jun 07, 2009 at 04:12:41PM -0400, Scott Ullrich wrote:
On Sun, Jun 7, 2009 at 3:36 PM, Chris Reesutis...@googlemail.com wrote:
2009/6/7 Clifton Royston clift...@lava.net:
If you feel you just *can't* do it via a script in
Dmitry Morozovsky wrote:
On Sun, 7 Jun 2009, Willem Jan Withagen wrote:
WJW KS On Friday 05 June 2009 06:27:23 am Willem Jan Withagen wrote:
WJW KS Hi,
WJW KS
WJW KS I'm trying to get my world to 7.2-stable(amd64),but run into:
WJW KS install -o root -g wheel -m 444 kgzldr.o
Willem Jan Withagen wrote:
Dmitry Morozovsky wrote:
On Sun, 7 Jun 2009, Willem Jan Withagen wrote:
WJW KS On Friday 05 June 2009 06:27:23 am Willem Jan Withagen wrote:
WJW KS Hi,
WJW KS
WJW KS I'm trying to get my world to 7.2-stable(amd64),but run
into:
WJW KS install -o root -g
John Baldwin wrote:
On Monday 01 June 2009 5:17:48 pm Bruce Simpson wrote:
Jilles Tjoelker wrote:
If process-shared semaphores really work, then the above structure is
not a pathological case. Effectively, sem_t is carved in stone. So
process-private semaphores should continue to have most of
Hello,
The PmcTools is merged to RELENG_7.
You can now enjoy the same level of features / hw supported as in head:
- Callchain in capture
- Core 2 support
- Core i7 support
- pmcannotate: source code annotation using pmc capture
- bug fixes
...
Tell me if you find any problems with it.
Fabien
Kip Macy wrote:
The second bug is the use of LOADER_ZFS_SUPPORT without any
consideration of WITHOUT_CDDL and/or WITHOUT_ZFS (or MK_ZFS)
I'll try get it fixed by Wednesday.
Kip, I noticed a fix went in with revision 193494 but was then backed
out straight away with no reason.
Will this
My old workstation finally died and replaced by a Dell Vostro 420.
Since the hard drives on the old machine were fine, I decided to throw
them into the new machine. The new machine only had SATA onboard, so I added a
Promise controller to the mix:
atap...@pci0:5:3:0: class=0x018000
Hello list
Any ideas if gptzfsboot is going to be MFC'ed into RELENG_7 anytime
soon? I am going to be building a NAS soon and I would like to have a
full ZFS system without having to resort to running 8-CURRENT :)
Sincerely,
- Dan Naumov
___
On Mon, 8 Jun 2009 10:18:37 -0400
Adam K Kirchhoff ad...@voicenet.com wrote:
My old workstation finally died and replaced by a Dell Vostro 420.
Since the hard drives on the old machine were fine, I decided to throw
them into the new machine. The new machine only had SATA onboard, so I added
On Saturday 06 June 2009 10:14:31 am Robert wrote:
Greetings
This problem seems the same as this one from May of this year
http://lists.freebsd.org/pipermail/freebsd-stable/2009-May/050088.html
This happens on an older HP laptop. It was running on 7.1 prerelease
fine and then I updated
Several posts made to this list AFTER the zfs v13 MFC to RELENG_7
indicated that even after that MFC, you still needed gptzfsboot from
8-CURRENT to be able to boot from a full ZFS system. Is this not the
case? I have a 7.2-STABLE built on May 30 and I do not have gptzfsboot
in my /boot, only
On Monday 08 June 2009 17:44:40 Dan Naumov wrote:
Several posts made to this list AFTER the zfs v13 MFC to RELENG_7
indicated that even after that MFC, you still needed gptzfsboot from
8-CURRENT to be able to boot from a full ZFS system. Is this not the
case? I have a 7.2-STABLE built on May
Ah, so there is still a (small) piece of 8-CURRENT needed to have a
working 7-STABLE zfs boot configuration? I am getting really confused
now, if I add LOADER_ZFS_SUPPORT=yes to my /etc/make.conf, the
RELENG_7 system will be built with zfs boot support, but I still need
the actual /boot/loader
After recent upgrade (on June 3) of my 7-stable host (WITNESS is enabled, the
previous build was Apr 26), I have been experienced panics when starting some
our home made application:
Architecture: i386
Architecture Version: 2
Dump Length: 73797632B (70 MB)
Blocksize: 512
Dumptime:
Dan Naumov wrote:
Ah, so there is still a (small) piece of 8-CURRENT needed to have a
working 7-STABLE zfs boot configuration? I am getting really confused
now, if I add LOADER_ZFS_SUPPORT=yes to my /etc/make.conf, the
RELENG_7 system will be built with zfs boot support, but I still need
the
On Mon, Jun 08, 2009 at 08:25:50PM +0300, Mikolaj Golub wrote:
After recent upgrade (on June 3) of my 7-stable host (WITNESS is enabled, the
previous build was Apr 26), I have been experienced panics when starting some
our home made application:
Architecture: i386
Architecture Version:
After upgrading from FreeBSD 7.1-RELEASE to FreeBSD 7.2-STABLE
I Get a gazillion of these :
kernel: ath0: stuck beacon; resetting (bmiss count 4)
in /var/log/messages
Mostly when all workstations are turned off. The messagestorm slows down after
the first workstation
has connected, but there
TB --- 2009-06-08 21:28:33 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-08 21:28:33 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2009-06-08 21:28:33 - cleaning the object tree
TB --- 2009-06-08 21:28:56 - cvsupping the source tree
TB --- 2009-06-08 21:28:56 -
I got a lockup at 3 a.m. JST, but because I'm not ready for dcons I
cannot show you guys the whole ddb session.
I put a 'bt' output of kgdb.
http://www.heimat.gr.jp/localhost/kgdbbtvmcore.0
Kernel config:
include GENERIC
ident HEIMAT
options MSGBUF_SIZE=81920
makeoptions DEBUG=-g
options
TB --- 2009-06-08 22:42:21 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-08 22:42:21 - starting RELENG_7 tinderbox run for i386/pc98
TB --- 2009-06-08 22:42:21 - cleaning the object tree
TB --- 2009-06-08 22:42:52 - cvsupping the source tree
TB --- 2009-06-08 22:42:52 -
TB --- 2009-06-08 22:42:38 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-08 22:42:38 - starting RELENG_7 tinderbox run for ia64/ia64
TB --- 2009-06-08 22:42:39 - cleaning the object tree
TB --- 2009-06-08 22:43:09 - cvsupping the source tree
TB --- 2009-06-08 22:43:09 -
TB --- 2009-06-08 23:55:30 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-08 23:55:30 - starting RELENG_7 tinderbox run for powerpc/powerpc
TB --- 2009-06-08 23:55:30 - cleaning the object tree
TB --- 2009-06-08 23:55:50 - cvsupping the source tree
TB --- 2009-06-08 23:55:50 -
TB --- 2009-06-09 00:18:40 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-06-09 00:18:40 - starting RELENG_7 tinderbox run for sparc64/sparc64
TB --- 2009-06-09 00:18:40 - cleaning the object tree
TB --- 2009-06-09 00:19:03 - cvsupping the source tree
TB --- 2009-06-09 00:19:03 -
I updated my recently acquired core-2 duo laptop to 7-stable amd64 (I
had been running 7-stable i386 with few problems) and have acquired an
apparent irq problem.
Fortunately in debugging a linux shared-interrupt problem about a month
ago I learned that the X server will happily accept mouse
27 matches
Mail list logo
