-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Setting kern.geom.eli.threads="1" from loader.conf solves the problem.
This looks like similar to kern/104669 but not fixed.
Krassimir Slavchev wrote:
> Hi,
>
> I have problems with geli and SMP kernel:
>
> ...
> Enter passphrase for md0:
> GEOM_ELI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Judge wrote:
> Krassimir Slavchev wrote:
>
>>
>> Any ideas how to debug this?
>>
>
>
> Have you looked at:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
The problem is that I can't attach the provider
Krassimir Slavchev wrote:
Any ideas how to debug this?
Have you looked at:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have problems with geli and SMP kernel:
...
Enter passphrase for md0:
GEOM_ELI: Device md0.eli created.
GEOM_ELI: Encryption: Blowfish-CBC 128
GEOM_ELI: Crypto: software
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault wh
John-Mark> How about drop iir?
Doug> But your suggestion does have merit, especially as recent PCI-X
Doug> and PCI-E ICP cards have no FreeBSD driver in sight.
Scott> My understanding is that the ICP division is switching over to
Scott> the architcture supported by the 'aac' driver. Adaptec
Scot
Douglas K. Rand wrote:
Doug> We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP
Doug> Vortex GDT8546RZ 4 port SATA RAID
John-Mark> We've had very similar experiences on 4.7-R. The box would
John-Mark> hang on one partition waiting for IO to come back, but
John-Mark> direct access t
Douglas K. Rand wrote this message on Fri, Apr 21, 2006 at 17:31 -0500:
> Doug> We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP
> Doug> Vortex GDT8546RZ 4 port SATA RAID
>
> John-Mark> We've had very similar experiences on 4.7-R. The box would
> John-Mark> hang on one partition wa
Doug> We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP
Doug> Vortex GDT8546RZ 4 port SATA RAID
John-Mark> We've had very similar experiences on 4.7-R. The box would
John-Mark> hang on one partition waiting for IO to come back, but
John-Mark> direct access to the disk, or accessing
Douglas K. Rand wrote this message on Fri, Apr 21, 2006 at 16:59 -0500:
> We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP Vortex
> GDT8546RZ 4 port SATA RAID card in a Tyan S2460 system with dual AMD
> Athlon MP 1600+ CPUs. We do not have any problems with this
> configuration under
We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP Vortex
GDT8546RZ 4 port SATA RAID card in a Tyan S2460 system with dual AMD
Athlon MP 1600+ CPUs. We do not have any problems with this
configuration under FreeBSD 4.11, and we have the same ICP cards in
Tyan based Opterion system (S28
Same panic as the night before. Are there any hints in the panic message
as to what the problem might be ?
---Mike
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id =
fault virtual address = 0x20004
fault code = supervisor re
The previous kernel had been running fine for some time, and now at night
around the running of periodic, the box will 'periodically' crash. It does
not seem to do it each night, but almost every other night and always just
after 3am when periodic runs. I can never get a crash dump, and I had
On Mon, 19 Aug 2002, Jarrod Sayers wrote:
> We had the same problem a while ago with the 440GX+ boards and the
> disappearing CPU1 trick. There is an option in the BIOS to tell it to
> redetect what CPU's are in the box. Once we hit that, it found the second
> CPU and everything was good.
Th
On Sunday, 18 August 2002 at 13:51:54 -0700, Chern Lee wrote:
> I'm not sure where along the line I lost my second CPU, but I'm sure I had
> it 4.5. Now, the second CPU is never detected.
>
> Dual Pentium III 600
> Intel L440GX motherboard w/ 440GX+ chipset
>
> This is a VA Linux machine. Any id
A few days ago I posted a problem with a SCSi bus on a stable machine
allegedly being reset according to the messages from the kernel. I
have now had time to track this down and ensure it isnt a hardware fault
The symptoms are as follows:
copy a set of files (e.g.):
cp src/cgi-bin/**.exe
copy
15 matches
Mail list logo