Your message dated Sun, 11 Oct 2009 22:11:28 +0100
with message-id <1255295488.25061.480.ca...@localhost>
and subject line Re: 64-bit kernel failures on Nehelem CPUs such as Dell T610,
R610
has caused the Debian Bug report #526525,
regarding 64-bit kernel failures on Nehelem CPUs such as Dell T610, R610
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.)
--
526525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526525
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-15
Severity: important
Kernel from linux-image-2.6.26-2-amd64 does not see
root RAID device /dev/md0 so boot sequence drops
busybox shell. 2.6.26-2-686-bigmem and 2.6.26-2-686
work properly.
This is after an install with no issues from the std
32-bit install iso image.
Machine is a Dell T610 server with 8 GB RAM and
8 cores (two four-core Xeons, I think)
-- Package-specific info:
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-2-amd64 recommends no packages.
Versions of packages linux-image-2.6.26-2-amd64 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-2-amd64/postinst/bootloader-error-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/preinst/lilo-initrd-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/postinst/depmod-error-2.6.26-2-amd64: false
linux-image-2.6.26-2-amd64/postinst/old-dir-initrd-link-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/postinst/create-kimage-link-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/preinst/initrd-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.26-2-amd64/preinst/abort-install-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/postinst/old-initrd-link-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/postinst/depmod-error-initrd-2.6.26-2-amd64: false
linux-image-2.6.26-2-amd64/postinst/bootloader-test-error-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/preinst/overwriting-modules-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.26-2-amd64/preinst/failed-to-move-modules-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/prerm/would-invalidate-boot-loader-2.6.26-2-amd64:
true
linux-image-2.6.26-2-amd64/postinst/old-system-map-link-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/preinst/abort-overwrite-2.6.26-2-amd64:
linux-image-2.6.26-2-amd64/preinst/bootloader-initrd-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/preinst/elilo-initrd-2.6.26-2-amd64: true
linux-image-2.6.26-2-amd64/prerm/removing-running-kernel-2.6.26-2-amd64: true
Best Regards.
Please keep in touch.
This is unedited.
P-)
--- End Message ---
--- Begin Message ---
On Tue, 2009-07-21 at 13:11 -0600, dann frazier wrote:
> On Tue, Jul 21, 2009 at 10:37:08AM -0700, Tony Godshall wrote:
> > Hello ??
> >
> > As I stated, yes, I was able to install with 32 bit kernel from the
> > start and it worked well.
> >
> > Anyhow, as I also stated later, a BIOS upgrade fixed the 64 bit issue
> > and I was able to install the 64-bit kernel.
>
> OK - is there still an issue here? It sounds like the Dell issues were
> fixed w/ a BIOS change - but is the IBM x3850 still an issue? If so,
> can someone w/ one of these systems verify that they are running the
> latest available BIOS?
I think that the problems on the IBM x3850 should be treated as a
separate bug. I'm closing this one since the bug affecting Dell
machines is in the BIOS and a fix is available.
(Κώστας, please use reportbug to file a bug report.)
Ben.
--
Ben Hutchings
DNRC Motto: I can please only one person per day.
Today is not your day. Tomorrow isn't looking good either.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
