Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes)
Brian Fundakowski Feldman <[email protected]>
| Newsgroups | gmane.os.freebsd.current,gmane.os.freebsd.devel.mobile |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jul 21, 2004 at 03:18:48PM +0400, Maxim Maximov wrote: > Brian Fundakowski Feldman wrote: > > >On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > > > >>Jake Hamby wrote: > >> > >>>3) Random freezes > >> > >>>After an average of 30-40 minutes of heavy usage, I get random system > >>>freezes. I am typically running XFree86 and downloading something > >>>or reading web pages at the time it happens. More disturbingly, I am > >>>occasionally seeing files get renamed, for example > >>>/usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > >>>with or without WITNESS, with INVARIANTS enabled, with or without > >>>ACPI, and with or without SMP. I am using SCHED_ULE and no > >>>PREEMPTION. > >> > >>you are not alone.. I think you just chose a bad moment to > >>jump into -current > >>:-/ > > > > > >Who else is getting random memory corruption? I've only ever seen it > >in my life with bad RAM/bad cooling, but this could be bad anything, > >including something spamming random addresses with DMA. The characters > >'I' and 'T' are far enough apart such that I wouldn't expect a simple > >memory error which usually seems to appear as a single bit flip. > > What are you guys all smoking? 64BTT stands for "64 bit time_t" > http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.64BTT Haha; never believe everything you read I suppose. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> [email protected] \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[email protected]"