Date: Mon, 08 Aug 2005 21:11:00 -0700 From: Sam Leffler <sam@errno.com> To: Pawel Jakub Dawidek <pjd@freebsd.org> Cc: Michael Reifenberger <mike@Reifenberger.com>, freebsd-current@freebsd.org, Mike Tancsa <mike@sentex.net> Subject: Re: Hifn driver in SMP (was Re: GELI - disk encryption GEOM class committed.) Message-ID: <42F82CD4.3010307@errno.com> In-Reply-To: <20050808084907.GB1578@garage.freebsd.pl> References: <20050728205413.GB762@darkness.comp.waw.pl> <6.2.1.2.0.20050806205925.0522cad0@64.7.153.2> <20050807065223.GB1002@garage.freebsd.pl> <6.2.1.2.0.20050807091937.040d9e48@64.7.153.2> <20050807160735.GD1002@garage.freebsd.pl> <6.2.1.2.0.20050807231805.0449b9c0@64.7.153.2> <6.2.1.2.0.20050807233527.06eef730@64.7.153.2> <20050808095233.P69029@fw.reifenberger.com> <20050808084907.GB1578@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Pawel Jakub Dawidek wrote: > On Mon, Aug 08, 2005 at 09:55:45AM +0200, Michael Reifenberger wrote: > +> On Sun, 7 Aug 2005, Mike Tancsa wrote: > +> > +> >Date: Sun, 07 Aug 2005 23:37:02 -0400 > +> >From: Mike Tancsa <mike@sentex.net> > +> >To: Pawel Jakub Dawidek <pjd@freebsd.org> > +> >Cc: freebsd-current@freebsd.org > +> >Subject: Hifn driver in SMP (was Re: GELI - disk encryption GEOM class > +> > committed.) > +> >Actually, it seems I can easily lock up the box with > +> >/usr/bin/openssl aes-128-cbc -in big -k pass | ssh -c aes128-cbc mdtancsa@127.0.0.1 "cat - > /home/mdtancsa/targetfile.enc" > +> >Is the hifn driver perhaps not fully smp safe ? > +> > +> BTW: > +> I've had hard lockups using the previous version of GELI and hifn on UP and amd64 (if that matters) too. > +> newfs worked but iozone locked up allways... > > You're probably seeing the same problem I have. > Are all the lockups on amd systems? I definitely tested hifn on a dual-xeon w/o issues but phk and others have reported various issues with hifn-based cards on operteron systems (though not hard lockups from what I recall). Given that I don't have an smp amd system someone w/ such a setup will need to collect info to help. Can you break to the debugger and inspect state? There's also debug.hifn I think (or something like it) to get debug msgs to the console. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42F82CD4.3010307>