On Mon, Jul 19, 2010 at 6:33 PM, Aurelien Jarno wrote:
> This has been caused by the switch from freebsd-buildutils 7.2 to 8.0
> and is also likely the cause of bug#587629.
>
> I will try to narrow down the problem even more.
Just tried your fixed package and it is working fine, thank you!
--
On Wed, Jul 14, 2010 at 03:52:35PM +0200, Tuco wrote:
> On 7/9/10, Tuco wrote:
> > This doesn't happen when using a native FreeBSD kernel on my Debian
> > GNU/kFreeBSD. I noticed a few patches related to ZFS, but disabling
> > them has no effect. I'm not a kernel developer, anything I can do to
>
On 7/9/10, Tuco wrote:
> This doesn't happen when using a native FreeBSD kernel on my Debian
> GNU/kFreeBSD. I noticed a few patches related to ZFS, but disabling
> them has no effect. I'm not a kernel developer, anything I can do to
> help solve this?
To be a bit more specific, for this workarou
On 6/30/10, Tuco wrote:
> $ zpool create mypool da1
> panic: stack overflow detected; backtrace may be corrupted
> cpuid = 0
> Uptime: 1m10s
> Cannot dump. Device not defined or unavailable.
> Automatic reboot in 15 seconds - press a key on the console to abort
This doesn't happen when using a na
Package: kfreebsd-image-8.0-1-amd64
Severity: important
Version: 8.0-9
I installed ZFS utilities by copying them from FreeBSD. When running
zpool, kernel panics:
$ zpool create mypool da1
panic: stack overflow detected; backtrace may be corrupted
cpuid = 0
Uptime: 1m10s
Cannot dump. Device not de
5 matches
Mail list logo
