Your message dated Wed, 18 Feb 2009 23:28:32 +0100 with message-id <[email protected]> and subject line Re: linux-image-2.6.15-1-sparc64-smp: RED state exception crashes on sparc64 SMP has caused the Debian Bug report #361214, regarding linux-image-2.6.15-1-sparc64-smp: RED state exception crashes on sparc64 SMP to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 361214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361214 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-2.6.15-1-sparc64-smp Version: 2.6.15-8 Severity: important This error repeatadly happens, and is the main reason sparc is no longer considered a release architecture, but I could not find a bug filed for it. Running with a serial consoled logged to another system, I was able to catch the error messages. They arn't completely consistant, so I'm including them all below. (A couple of weeks worth on my sparc pbuilder system.) Speculation: there has been a report that heavy disk I/O causes this problem. Since many of the messages have truncated kernel fault messages, I guess that the system buffers a kernel fault message, then tries to dump core causing a fault in the fault handler. (I think that's what a RED state exception is.) Adding a delay or turning off the kernel core dump may allow the full error message to be displayed. The doubled characters may be due to both processors printing the same message at the same time. (All the RED state excpetion lines below were followed by the normal reboot messages.) sundry login: Unable to handle kernel NULL pointer dereference RED State Exception sundry:~# \|/ ____ \ |/ "@'/ .. \`@" /_| \__/ |K00//r e RED State Exception sundry login: kernel BUG at arch/sparc64/mm/fault.c:273! \|/ ____ \|/ #4 . RED State Exception sundry login: Unable to handle kernel paging request at virtual address 00000000 000f4240 UnaUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddee rreeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerreennccee U RED State Exception sundry login: RED State Exception sundry login: kernel BUG pointer dce <1>U handle kLL pointerence <1to handle ULL pointerence < to handl NULL poieference e to handl NULL poreferencele to hanel NULL dereferenable to hrnel NULL pointer RED State Exception sundry login: \|/ ____ \|/ "@'/ .. \`@" /_| \l:0 RED State Exception sundry login: \|/ ____ \|/ "@'/ .. \`@" /_| \l:0 RED State Exception sundry login: UnaUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooii nntteerr ddeerreeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerrreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeffeerreennccee UUnnaabbllee ttoo hhaannddllee kkeerrnneell NNUULLLL ppooiinntteerr ddeerr eeff RED State Exception -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-sparc64-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.15-1-sparc64-smp depends on: ii initramfs-tools [linux-initra 0.59b tools for generating an initramfs ii module-init-tools 3.2.2-2 tools for managing Linux kernel mo linux-image-2.6.15-1-sparc64-smp recommends no packages. -- debconf information: linux-image-2.6.15-1-sparc64-smp/postinst/old-dir-initrd-link-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/prerm/removing-running-kernel-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/prerm/would-invalidate-boot-loader-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/postinst/old-system-map-link-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/preinst/overwriting-modules-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/preinst/abort-install-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/preinst/already-running-this-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/preinst/failed-to-move-modules-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/postinst/old-initrd-link-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/postinst/depmod-error-2.6.15-1-sparc64-smp: false linux-image-2.6.15-1-sparc64-smp/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-sparc64-smp/postinst/bootloader-test-error-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/postinst/bootloader-error-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/preinst/lilo-initrd-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/postinst/kimage-is-a-directory: linux-image-2.6.15-1-sparc64-smp/postinst/depmod-error-initrd-2.6.15-1-sparc64-smp: false linux-image-2.6.15-1-sparc64-smp/preinst/initrd-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/preinst/elilo-initrd-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/preinst/abort-overwrite-2.6.15-1-sparc64-smp: linux-image-2.6.15-1-sparc64-smp/postinst/create-kimage-link-2.6.15-1-sparc64-smp: true linux-image-2.6.15-1-sparc64-smp/preinst/bootloader-initrd-2.6.15-1-sparc64-smp: true
--- End Message ---
--- Begin Message ---On Fri, Apr 07, 2006 at 01:22:52AM -0700, Blars Blarson wrote: > Package: linux-image-2.6.15-1-sparc64-smp > Version: 2.6.15-8 > Severity: important > > This error repeatadly happens, and is the main reason sparc is no > longer considered a release architecture, but I could not find a bug > filed for it. > > Running with a serial consoled logged to another system, I was able to > catch the error messages. They arn't completely consistant, so I'm > including them all below. (A couple of weeks worth on my sparc > pbuilder system.) > > Speculation: there has been a report that heavy disk I/O causes this > problem. Since many of the messages have truncated kernel fault > messages, I guess that the system buffers a kernel fault message, then > tries to dump core causing a fault in the fault handler. (I think > that's what a RED state exception is.) Adding a delay or turning off > the kernel core dump may allow the full error message to be displayed. > The doubled characters may be due to both processors printing the same > message at the same time. > > (All the RED state excpetion lines below were followed by the normal > reboot messages.) This bug report has been pinged at least twice for more information, so I'm closing it now. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz
--- End Message ---
