** Tags added: apport-collected

** Description changed:

  Hello,
  
  I'm experiencing kernel panics on 5 identical Ubuntu 10.04 servers. They
  are identical down to every bit of hardware and operating environment,
  They've been reliably running Debian and Ubuntu Linux releases for
  years. There's something in the latest Ubuntu 10.04 server builds that
  has introduced a regression. They are used for heavy but sporadic CPU-
  bound work.
  
  Over the course of a day, the odds are that a singular server will
  experience a kernel. Over two days it's practically guaranteed.
  
  The kernel panic says:
  
  "sd 2:0:0:0 rejecting i/o to offline device"
  
  sd is the system drive and is most certainly online. A hard reboot fixes
  the matter for the following day or so.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-25-generic 2.6.32-25.44
  Regression: Yes
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  Architecture: amd64
  Date: Fri Oct 22 16:19:50 2010
  Frequency: Once a day.
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux
+ --- 
+ Architecture: amd64
+ DistroRelease: Ubuntu 10.04
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
+ Regression: Yes
+ Reproducible: Yes
+ Tags: lucid filesystem regression-release needs-upstream-testing
+ Uname: Linux 2.6.32-33-generic x86_64
+ UserGroups:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665163

Title:
  kernel panic with 'rejecting i/o to offline device'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665163/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to