Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 612
  • Last Modified:

Ubuntu 8.04 Kernel panic

I'm running a Ubuntu 8.04 vm on proxmox 1.4.  The last few weeks without notice I have been getting a kernel panic on it.  I've posted a screenshot of the panic and below is from the messages log right before the panic happened.  Can anyone help me to determine why this is happening?


Dec 17 06:43:07 nospam2 kernel: [726273.536233] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:43:07 nospam2 kernel: [726273.536251] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:43:07 nospam2 kernel: [726273.536264] sd 0:0:1:0: [sda] DEVICE RESET operation started
Dec 17 06:43:07 nospam2 kernel: [726273.536404]  target0:0:1: control msgout: c.
Dec 17 06:43:07 nospam2 kernel: [726273.536494]  target0:0:1: has been reset
Dec 17 06:43:07 nospam2 kernel: [726273.536591] sd 0:0:1:0: DEVICE RESET operation complete.
Dec 17 06:43:07 nospam2 kernel: [726273.536652] sd 0:0:1:0: M_REJECT received (0:0).
Dec 17 06:44:15 nospam2 kernel: [726324.755051] Clocksource tsc unstable (delta = 14060940642 ns)
Dec 17 06:44:15 nospam2 kernel: [726324.759152] Time: acpi_pm clocksource has been installed.
Dec 17 06:44:16 nospam2 kernel: [726345.280303] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:16 nospam2 kernel: [726345.280310] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:16 nospam2 kernel: [726345.280311] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:16 nospam2 kernel: [726345.280313] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:16 nospam2 kernel: [726345.280314] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:16 nospam2 kernel: [726345.280315] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:16 nospam2 kernel: [726345.280317] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:16 nospam2 kernel: [726345.280318] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280319] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280320] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280322] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280323] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280324] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280325] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280327] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280328] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280329] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280331] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280332] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280333] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280335] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280336] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280337] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280338] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280340] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280341] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:44:18 nospam2 kernel: [726345.280344] sd 0:0:1:0: [sda] DEVICE RESET operation started
Dec 17 06:44:18 nospam2 kernel: [726345.280464]  target0:0:1: control msgout: c.
Dec 17 06:44:18 nospam2 kernel: [726345.280551]  target0:0:1: has been reset
Dec 17 06:44:18 nospam2 kernel: [726345.280676] sd 0:0:1:0: DEVICE RESET operation complete.
Dec 17 06:44:18 nospam2 kernel: [726345.280735] sd 0:0:1:0: M_REJECT received (0:0).
Dec 17 06:46:06 nospam2 kernel: [726437.753164] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753171] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753173] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753175] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753176] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753177] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753187] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753188] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753189] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753191] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753192] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753193] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753194] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753196] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753197] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753198] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753199] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753201] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753202] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726437.753203] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726437.753204] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726440.223651] sd 0:0:1:0: ABORT operation complete.
Dec 17 06:46:06 nospam2 kernel: [726442.949581] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949587] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726442.949589] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949590] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726442.949591] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949592] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726442.949594] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949595] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726442.949596] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949598] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:46:06 nospam2 kernel: [726442.949602] sd 0:0:1:0: [sda] DEVICE RESET operation started
Dec 17 06:46:06 nospam2 kernel: [726442.949726]  target0:0:1: control msgout: c.
Dec 17 06:46:06 nospam2 kernel: [726442.949820]  target0:0:1: has been reset
Dec 17 06:46:06 nospam2 kernel: [726442.949917] sd 0:0:1:0: DEVICE RESET operation complete.
Dec 17 06:46:06 nospam2 kernel: [726442.949975] sd 0:0:1:0: M_REJECT received (0:0).
Dec 17 06:47:59 nospam2 kernel: [726532.815094] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:48:04 nospam2 kernel: [726532.815113] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:48:04 nospam2 kernel: [726532.815115] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:48:04 nospam2 kernel: [726541.026089] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:48:04 nospam2 kernel: [726541.026090] sd 0:0:1:0: [sda] ABORT operation started
Dec 17 06:48:04 nospam2 kernel: [726541.026091] sd 0:0:1:0: ABORT operation failed.
Dec 17 06:48:04 nospam2 kernel: [726541.026109] sd 0:0:1:0: [sda] DEVICE RESET operation started
Dec 17 06:48:04 nospam2 kernel: [726541.026234]  target0:0:1: control msgout: c.
Dec 17 06:48:04 nospam2 kernel: [726541.026321]  target0:0:1: has been reset
Dec 17 06:48:04 nospam2 kernel: [726541.026417] sd 0:0:1:0: DEVICE RESET operation complete.
Dec 17 06:48:04 nospam2 kernel: [726541.026476] sd 0:0:1:0: M_REJECT received (0:0).

Open in new window

ubuntupanic.png
0
andygee1
Asked:
andygee1
  • 4
1 Solution
 
nociSoftware EngineerCommented:
The interesting part just scrolled off your screen (Using shift pgup it could be brought into view)...
You need the top of that report. or the one before that....

The bottom message means that there is something serioulsy wrong during handling of an interrupt.
0
 
andygee1Author Commented:
Does is it store this in a log somewhere as I can't scroll up, it's already rebooted now.
0
 
nociSoftware EngineerCommented:
no the oopses are only stored on the screen.
0
 
nociSoftware EngineerCommented:
If you want to keep that kind of info, you can configure a serial port to be used as console.
then log anything from a serial port to a file  (on another system) ... There are console monitor tools for that.
0
 
nociSoftware EngineerCommented:
If this is a vm running on another host you might need to check if the file where this is stored is severly fragmented. If so then that might e a cause for performance trouble.
Store the virtual disks on a filesystem with 64K disk cluster size.
I know I once had trouble related with this an install took about an hour to get started. After moving to a different host, the same amount of work started within 5 minutes. The only difference between the vm-hosts was the cluster size + the amount of fragmentation on the first system.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now