Date: Sat, 22 Apr 2006 14:14:41 -0700 (PDT) From: "R. B. Riddick" <arne_woerner@yahoo.com> To: Erin E Conn <econn@nc.rr.com> Cc: freebsd-multimedia@freebsd.org Subject: Re: Rebooting problems with /dev/cxm0 Message-ID: <20060422211441.89853.qmail@web30315.mail.mud.yahoo.com> In-Reply-To: <444A7E66.8010509@nc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Erin E Conn <econn@nc.rr.com> wrote: > R. B. Riddick wrote: > > --- Erin E Conn <econn@nc.rr.com> wrote: > It crashes before any of my power saving features have time to kick in. > You could experiment with ur BIOS settings and/or ur PCI/ISA slots... if u feel like it... I would turn of all power saving features and ACPI and such things - just for testing dev/cxm of course... > > I could send u the two C programs (one for gathering+marshalling > > and one for demarshalling. > > Thanks, those might be helpful. > see below... > > And for how long could you do this test? I mean: If it crashed every 2-5 > > minutes with "cat", when does it crash, when you use "dd"? > > > Interestingly, using dd, the computer did not crash, but the X server > dumped core and restarted, which killed the dd process since I was > running it in an xterm. Trying it from the console to see if that makes > a difference. It crashed after about the same amount of time as cat did, > using a blocksize of 1m. > Hmm... U seem to have a much different problem than I had, because: The "dd" command merely reads from /dev/cxm0 as fast as possible without any delay (e. g. due to busy network or disc), since /dev/null is quite quick... So I did not send my "cxm-network-transfer&buffering-tool", because one side of it does nearly the same as the "dd" command, and because my box was able to do the "dd" test for many hours... -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060422211441.89853.qmail>