Vivek Khera wrote:
On Mar 17, 2008, at 4:05 PM, Sascha Klauder wrote:
I've recently upgraded my 6.2-STABLE workstation to RELENG_7,
and I'm now experiencing system lockups that seem to be caused
by the hifn(4) driver.
I've got a Soekris vpn1401 card to help with GELI disk en-
cryption. Readi
On Tue, Mar 18, 2008 at 10:25:03AM -0400, Vivek Khera wrote:
> On Mar 17, 2008, at 4:05 PM, Sascha Klauder wrote:
> >I've got a Soekris vpn1401 card to help with GELI disk en-
> >cryption. Reading from a GELI volume is causing the system to
> >freeze completely, which does not happen if software c
On Mar 17, 2008, at 4:05 PM, Sascha Klauder wrote:
I've recently upgraded my 6.2-STABLE workstation to RELENG_7,
and I'm now experiencing system lockups that seem to be caused
by the hifn(4) driver.
I've got a Soekris vpn1401 card to help with GELI disk en-
cryption. Reading from a GELI volum
Hi all,
can someone comment on the state of the hifn(4) driver?
I've recently upgraded my 6.2-STABLE workstation to RELENG_7,
and I'm now experiencing system lockups that seem to be caused
by the hifn(4) driver.
I've got a Soekris vpn1401 card to help with GELI disk en-
cryption. Reading fr
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jung-uk Kim
> Sent: Monday, August 08, 2005 2:29 PM
> To: freebsd-stable@FreeBSD.org
> Cc: Josh Endries
> Subject: Re: twa0 errors and system lockup on amd64
>
> On Mon
On Monday 08 August 2005 05:03 pm, Josh Endries wrote:
> Hello,
>
> Just a little while ago I got this on a test 5.4-stable dual
> Opteron box I'm setting up (9500S-LP RAID 5 with a hot spare):
>
> Aug 8 15:58:21 kernel: twa0: ERROR: (0x05: 0x210b): Request timed
> out!: request = 0x80a677
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Just a little while ago I got this on a test 5.4-stable dual Opteron
box I'm setting up (9500S-LP RAID 5 with a hot spare):
Aug 8 15:58:21 kernel: twa0: ERROR: (0x05: 0x210b): Request timed
out!: request = 0x80a67700
Aug 8 15:58:21 k
The last two days have seen two lockups on one of our firewall
machines. Box is pingable, accepts TCP connections but does
nothing more. syslog shows it logging "MARK" every five minutes
even when unresponsive.
First thought: DoS attack. After cvsupping and recompiling
kernel and world yesterday
I'm using WMaker, and I'm not using the "no async dns" option. Whatever the
combination is, X grows in memory until it exposes hardware instabilities in
my system. X never gets that big in memory unless I run Communicator. It's
just that the odds of a crash are low when I'm not using much memory a
Does it lockup when you are connected to the internet also ?
Or only when you use Netscape offline ?
-
|FreeBSD powered|
-
On Mon, 6 Sep 1999, Huidae Cho wrote:
> Hmm, i use 3.2-19990815-STABLE and i experienced system lockup a few times.
>
> What&#
Hmm, i use 3.2-19990815-STABLE and i experienced system lockup a few times.
What's wrong? I suspect a netscape-communicator 'cause whenever system
locked up, i used netscape.
Please give me some clue.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
11 matches
Mail list logo
