On 11 October 2010 18:36, Henrique de Moraes Holschuh <h...@debian.org> wrote: > On Sun, 10 Oct 2010, Jason Heeris wrote: t>> My system is a Helios single-board computer, with specs: >> >> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I >> could be wrong > > Yikes. You really need to track this one down, and find out whether it is > any different from a regular 486. The devil IS in the details, and these > older boxes are NOT regularly tested anymore.
According to http://www.vortex86.com/index2.html Vortex86 family integrates a high-performance processor that supports x86 instruction set with 3 integer units, 3-way superscalar architecture, and a fully pipelined floating point unit. Hmm. According to /proc/cpinfo on the installer, > 1. Set up a serial console (to capture crash data); > 2. Make sure you're in condition to lose data; > 3. Reproduce the crash, log *everything* since boot. What do you mean by "everything"? Every command? That's not hard. All the kernel messages? That's harder... The logs in /var/log do not seem to contain *anything* about the session during which the crash occurs. > 4. File a bug on bugzilla.kernel.org with all relevant information. This > does include the kernel config at the very least. It's just the Debian stock kernel config. > The box objected VERY HEAVILY to the ipv6 multicast operations trigerred by > avahi. Given this, can you think of another way I might be able to trigger the bug? If so, I might be able to do it without needing to reinstall the system every time. > Without fixing the underlying bug, your box will be unusable (lots > of other stuff are likely to trigger the same problem). That's what I was afraid of. Thanks for the info, I'll see what I can do. Cheers, Jason -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimjn1p1iynvwh4dtw=nqwa_sgxy7raqp8x8w...@mail.gmail.com
