Hi all,
I'm upgrading a FreeBSD amd64 box from 6.2p9 to 7.0p5.
After update the sources amd make world with success, I get this error:
[...]
newfs.lo(.text+0x659): In function `main':
: undefined reference to `__mb_sb_limit'
newfs_msdos.lo(.text+0x13): In function `mklabel':
: undefined referenc
John, I can ship you one of these machines for your own testing if you
like. Or send me a public key and I can give you SSH access to the
console serial port, whichever would be easiest for you to get what
you need.
Let me know how I can help.
On Nov 5, 2008, at 3:41 PM, Jo Rhett wrote:
Bartosz Stec wrote:
Well it's not simple indeed. I use ZFS on my home (not critical) box
(RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
stable. Unfortunately ZFS crashed next week ;)
How did it crash ? Just the system went down or did you lose any data ?
I'm planning
Hi,
I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
when pf(4) is enabled:
lock order reversal:
1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
2nd 0xc45d604c pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916
KDB: stack backtrace
On Thu, Nov 20, 2008 at 4:11 PM, Ulrich Spoerlein <[EMAIL PROTECTED]>wrote:
> Hi,
>
> I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
> when pf(4) is enabled:
>
> lock order reversal:
> 1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
> 2nd 0xc45d604c pf task mtx (pf
I'm writing to encourage an MFC for src/Makefile.inc1, rev. 1.614.
I tested it for the committer. :-} And if we're to make use of
amd64 arch "build" machines at $WORK, we'll need that change.
(Symptoms prior to the commit are that 32-bit executables that use
crypto libraries will fail to run bec
And there are these LORs when I shut down my external firewire attached
disk:
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
uma_zalloc_arg: zone "16" with the following non-sleepable loc
martinko wrote:
Bartosz Stec wrote:
Well it's not simple indeed. I use ZFS on my home (not critical) box
(RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
stable. Unfortunately ZFS crashed next week ;)
How did it crash ? Just the system went down or did you lose any dat
Rudy wrote:
Speaking of losing data on a ZFS system, I haven't yet (knock on wood)
had a disk failure. Anyone have a disk failure occur and have an
easy/hard time replacing the bad disk?
On a system with AHCI, I can literally yank the SATA disks, zfs keeps
working after a pause, and when I r
On Thu, 20 Nov 2008, Rudy wrote:
martinko wrote:
Bartosz Stec wrote:
Well it's not simple indeed. I use ZFS on my home (not critical) box
(RAIDZ1). After 4 weeks uptime with varied workload I assumed it's stable.
Unfortunately ZFS crashed next week ;)
How did it crash ? Just the system
martinko pisze:
Bartosz Stec wrote:
Well it's not simple indeed. I use ZFS on my home (not critical) box
(RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
stable. Unfortunately ZFS crashed next week ;)
How did it crash ? Just the system went down or did you lose any dat
11 matches
Mail list logo
