<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: kernel panic in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224002#M33058</link>
    <description>At 08:28, someone tried to use a tape drive with no tape inserted. It's an error, but it should never be a cause for kernel panics.&lt;BR /&gt;&lt;BR /&gt;At 09:26, the drive notifies the system for acceptable block size limits (for the current drive + media combination?). This message is not an error, just information.&lt;BR /&gt;Maybe someone has inserted a tape into the drive and is now starting a system backup?&lt;BR /&gt;&lt;BR /&gt;Nothing here indicates any cause for a kernel panic. &lt;BR /&gt;&lt;BR /&gt;A wild guess: does the kernel panic happen whenever you're taking backups?&lt;BR /&gt;If so, are you backing up the /proc filesystem? &lt;BR /&gt;&lt;BR /&gt;/proc is a virtual filesystem which contains process information and kernel tunables. All the information in it is generated dynamically, so there is no reason to back it up. With some kernel versions, trying to back up /proc is known to cause kernel panics. &lt;BR /&gt;&lt;BR /&gt;You should always exclude /proc from your backups. If you're using a 2.6 series kernel, you should exclude /sys too: it's another virtual filesystem.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Sat, 28 Jun 2008 05:56:19 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2008-06-28T05:56:19Z</dc:date>
    <item>
      <title>kernel panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224001#M33057</link>
      <description>our servers keep hanging due to kernel panic.&lt;BR /&gt;&lt;BR /&gt;from the /var/log/messages we get:&lt;BR /&gt;&lt;BR /&gt;Jun 25 08:28:06 hostname1 kernel: st1: Error with sense data: Current st1: sense key Not Ready&lt;BR /&gt;Jun 25 08:28:06 hostname1 kernel: Additional sense: Medium not present&lt;BR /&gt;Jun 25 09:26:27 hostname1 kernel: st1: Block limits 1 - 16777215 bytes.&lt;BR /&gt;</description>
      <pubDate>Sat, 28 Jun 2008 00:48:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224001#M33057</guid>
      <dc:creator>Alvin_14</dc:creator>
      <dc:date>2008-06-28T00:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: kernel panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224002#M33058</link>
      <description>At 08:28, someone tried to use a tape drive with no tape inserted. It's an error, but it should never be a cause for kernel panics.&lt;BR /&gt;&lt;BR /&gt;At 09:26, the drive notifies the system for acceptable block size limits (for the current drive + media combination?). This message is not an error, just information.&lt;BR /&gt;Maybe someone has inserted a tape into the drive and is now starting a system backup?&lt;BR /&gt;&lt;BR /&gt;Nothing here indicates any cause for a kernel panic. &lt;BR /&gt;&lt;BR /&gt;A wild guess: does the kernel panic happen whenever you're taking backups?&lt;BR /&gt;If so, are you backing up the /proc filesystem? &lt;BR /&gt;&lt;BR /&gt;/proc is a virtual filesystem which contains process information and kernel tunables. All the information in it is generated dynamically, so there is no reason to back it up. With some kernel versions, trying to back up /proc is known to cause kernel panics. &lt;BR /&gt;&lt;BR /&gt;You should always exclude /proc from your backups. If you're using a 2.6 series kernel, you should exclude /sys too: it's another virtual filesystem.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 28 Jun 2008 05:56:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224002#M33058</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-06-28T05:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: kernel panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224003#M33059</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;This kernel panic indicates a hardware problem of some sort.&lt;BR /&gt;&lt;BR /&gt;Due to the tape drive being the trigger, check the scsi card, connectors cables and scsi ID setup for problems.&lt;BR /&gt;&lt;BR /&gt;Test the hardware, perhaps with the vendor. If the tape drive is bad it could trigger this kind of problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 29 Jun 2008 05:08:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224003#M33059</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-06-29T05:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: kernel panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224004#M33060</link>
      <description>The tape drive is going bad, may already have!&lt;BR /&gt;&lt;BR /&gt;To escape from a kernel panic and get your machine to reboot automagically, add this into /etc/sysctl.conf&lt;BR /&gt;&lt;BR /&gt;kernel.panic = 7 (after a 7 sec delay, kernel reboots)&lt;BR /&gt;&lt;BR /&gt;Make sysctl re-read this by sysctl -p /etc/sysctl.conf&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Sep 2008 09:44:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224004#M33060</guid>
      <dc:creator>Ragu_3</dc:creator>
      <dc:date>2008-09-15T09:44:53Z</dc:date>
    </item>
    <item>
      <title>Re: kernel panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224005#M33061</link>
      <description>Hi,&lt;BR /&gt;This is related to Tape drive, yes it may be hardware connection error.&lt;BR /&gt;Please check the stape status in Kernal, that shoud be static (Current value and Next Value).&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gokul Chandola</description>
      <pubDate>Tue, 16 Sep 2008 02:22:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/4224005#M33061</guid>
      <dc:creator>Gokul Chandola</dc:creator>
      <dc:date>2008-09-16T02:22:40Z</dc:date>
    </item>
  </channel>
</rss>

