OpenVZ Forum


Home » Mailing lists » Users » Another kernel panic, Debian AMD64 with Supermicro hardware
Another kernel panic, Debian AMD64 with Supermicro hardware [message #23110] Mon, 12 November 2007 17:39 Go to next message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
Hi All...

I thought this issue was resolved with the last kernel upgrade I did, but 
this morning at about 6:25AM Eastern (I think) one of my OpenVZ machines 
experienced a kernel panic.

The kernel is:

actual:/var/log# uname -a
Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Sat 
Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux

This is Debian Etch AMD64 running on Supermicro hardware.

The messages log is not much help.  I rebooted at about noon:

Nov 12 05:43:37 actual -- MARK --
Nov 12 06:03:37 actual -- MARK --
Nov 12 06:23:37 actual -- MARK --
Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg 
started.
.
.
.


Same for syslog.  Here are the last few lines:


syslog.0:

Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD 
(/home/jim/check-vps-wrapper.sh)
Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD 
(/usr/share/vzctl/scripts/vpsnetclean)
Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD 
(/usr/share/vzctl/scripts/vpsreboot)
Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD 
(/usr/share/vzctl/scripts/vpsreboot)
Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD 
(/usr/share/vzctl/scripts/vpsnetclean)
Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD 
(/usr/share/vzctl/scripts/vpsreboot)
Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD 
(/usr/share/vzctl/scripts/vpsnetclean)
Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD 
(/home/jim/check-vps-wrapper.sh)
Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x 
/usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD 
(/usr/share/vzctl/scripts/vpsreboot)
Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD 
(/usr/share/vzctl/scripts/vpsnetclean)

syslog:

Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg 
started.
Nov 12 12:00:44 actual kernel: Bootdata ok (command line is 
root=/dev/mapper/VG--RAID-LV1 ro )
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23111 is a reply to message #23110] Mon, 12 November 2007 17:44 Go to previous messageGo to next message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
Oh, and the last message on the console was:

 Kernel panic - not syncing: Aiee, killing intrrupt handler!


--On Monday, November 12, 2007 12:39 PM -0500 Jim Archer <jim@archer.net> 
wrote:

> Hi All...
>
> I thought this issue was resolved with the last kernel upgrade I did, but
> this morning at about 6:25AM Eastern (I think) one of my OpenVZ machines
> experienced a kernel panic.
>
> The kernel is:
>
> actual:/var/log# uname -a
> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Sat
> Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>
> This is Debian Etch AMD64 running on Supermicro hardware.
>
> The messages log is not much help.  I rebooted at about noon:
>
> Nov 12 05:43:37 actual -- MARK --
> Nov 12 06:03:37 actual -- MARK --
> Nov 12 06:23:37 actual -- MARK --
> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
> started.
> .
> .
> .
>
>
> Same for syslog.  Here are the last few lines:
>
>
> syslog.0:
>
> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
> (/home/jim/check-vps-wrapper.sh)
> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
> (/usr/share/vzctl/scripts/vpsnetclean)
> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
> (/usr/share/vzctl/scripts/vpsreboot)
> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
> (/usr/share/vzctl/scripts/vpsreboot)
> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
> (/usr/share/vzctl/scripts/vpsnetclean)
> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
> run-parts --report /etc/cron.hourly)
> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
> (/usr/share/vzctl/scripts/vpsreboot)
> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
> (/usr/share/vzctl/scripts/vpsnetclean)
> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
> (/home/jim/check-vps-wrapper.sh)
> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
> (/usr/share/vzctl/scripts/vpsreboot)
> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
> (/usr/share/vzctl/scripts/vpsnetclean)
>
> syslog:
>
> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
> started.
> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
> root=/dev/mapper/VG--RAID-LV1 ro )
>
>
>
>
>
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23272 is a reply to message #23111] Thu, 15 November 2007 07:15 Go to previous messageGo to next message
Thorsten Schifferdeck is currently offline  Thorsten Schifferdeck
Messages: 38
Registered: February 2006
Member
Hi Jim,

can you poste more info, or can it be solved by installing a new kernel,
maybe this thread helps (-> 
http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )

Bye,
  Thorsten

Jim Archer wrote:
> Oh, and the last message on the console was:
> 
> Kernel panic - not syncing: Aiee, killing intrrupt handler!
> 
> 
> --On Monday, November 12, 2007 12:39 PM -0500 Jim Archer 
> <jim@archer.net> wrote:
> 
>> Hi All...
>>
>> I thought this issue was resolved with the last kernel upgrade I did, but
>> this morning at about 6:25AM Eastern (I think) one of my OpenVZ machines
>> experienced a kernel panic.
>>
>> The kernel is:
>>
>> actual:/var/log# uname -a
>> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Sat
>> Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>>
>> This is Debian Etch AMD64 running on Supermicro hardware.
>>
>> The messages log is not much help.  I rebooted at about noon:
>>
>> Nov 12 05:43:37 actual -- MARK --
>> Nov 12 06:03:37 actual -- MARK --
>> Nov 12 06:23:37 actual -- MARK --
>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>> started.
>> .
>> .
>> .
>>
>>
>> Same for syslog.  Here are the last few lines:
>>
>>
>> syslog.0:
>>
>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
>> (/home/jim/check-vps-wrapper.sh)
>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsnetclean)
>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsreboot)
>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsreboot)
>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsnetclean)
>> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
>> run-parts --report /etc/cron.hourly)
>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsreboot)
>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsnetclean)
>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
>> (/home/jim/check-vps-wrapper.sh)
>> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
>> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
>> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsreboot)
>> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
>> (/usr/share/vzctl/scripts/vpsnetclean)
>>
>> syslog:
>>
>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>> started.
>> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
>> root=/dev/mapper/VG--RAID-LV1 ro )
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23375 is a reply to message #23272] Fri, 16 November 2007 07:43 Go to previous messageGo to next message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
Hi Thorsten,

Well this is the most recent kernel available from this link:

http://download.openvz.org/kernel/debian/etch/

I use these because they include the iSCSI daemon which I need to talk to 
my SAN box.  Is there a newer kernel available and if so, where do I get it?

Thanks...




--On Thursday, November 15, 2007 8:15 AM +0100 Thorsten Schifferdecker 
<tsd@debian.systs.org> wrote:

> Hi Jim,
>
> can you poste more info, or can it be solved by installing a new kernel,
> maybe this thread helps (->
> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
>
> Bye,
>   Thorsten
>
> Jim Archer wrote:
>> Oh, and the last message on the console was:
>>
>> Kernel panic - not syncing: Aiee, killing intrrupt handler!
>>
>>
>> --On Monday, November 12, 2007 12:39 PM -0500 Jim Archer
>> <jim@archer.net> wrote:
>>
>>> Hi All...
>>>
>>> I thought this issue was resolved with the last kernel upgrade I did,
>>> but this morning at about 6:25AM Eastern (I think) one of my OpenVZ
>>> machines experienced a kernel panic.
>>>
>>> The kernel is:
>>>
>>> actual:/var/log# uname -a
>>> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP
>>> Sat Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>>>
>>> This is Debian Etch AMD64 running on Supermicro hardware.
>>>
>>> The messages log is not much help.  I rebooted at about noon:
>>>
>>> Nov 12 05:43:37 actual -- MARK --
>>> Nov 12 06:03:37 actual -- MARK --
>>> Nov 12 06:23:37 actual -- MARK --
>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>> started.
>>> .
>>> .
>>> .
>>>
>>>
>>> Same for syslog.  Here are the last few lines:
>>>
>>>
>>> syslog.0:
>>>
>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
>>> (/home/jim/check-vps-wrapper.sh)
>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsreboot)
>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsreboot)
>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
>>> run-parts --report /etc/cron.hourly)
>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsreboot)
>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
>>> (/home/jim/check-vps-wrapper.sh)
>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
>>> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsreboot)
>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>
>>> syslog:
>>>
>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>> started.
>>> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
>>> root=/dev/mapper/VG--RAID-LV1 ro )
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23379 is a reply to message #23375] Fri, 16 November 2007 09:20 Go to previous messageGo to next message
Thorsten Schifferdeck is currently offline  Thorsten Schifferdeck
Messages: 38
Registered: February 2006
Member
Hi Jim,

you need the iscsi kernel modules like iscsi_tcp, libiscsi and
scsi_transport_iscsi ?

I've built some debian kernel images, see
http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-version-028stab481/

There's the modules built as module like, the original Debian Kernel.

Hope this helps,
 Thorsten

Am Fr, 16.11.2007, 07:43, schrieb Jim Archer:
> Hi Thorsten,
>
> Well this is the most recent kernel available from this link:
>
> http://download.openvz.org/kernel/debian/etch/
>
> I use these because they include the iSCSI daemon which I need to talk to
> my SAN box.  Is there a newer kernel available and if so, where do I get
> it?
>
> Thanks...
>
>
>
>
> --On Thursday, November 15, 2007 8:15 AM +0100 Thorsten Schifferdecker
> <tsd@debian.systs.org> wrote:
>
>> Hi Jim,
>>
>> can you poste more info, or can it be solved by installing a new kernel,
>> maybe this thread helps (->
>> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
>>
>> Bye,
>>   Thorsten
>>
>> Jim Archer wrote:
>>> Oh, and the last message on the console was:
>>>
>>> Kernel panic - not syncing: Aiee, killing intrrupt handler!
>>>
>>>
>>> --On Monday, November 12, 2007 12:39 PM -0500 Jim Archer
>>> <jim@archer.net> wrote:
>>>
>>>> Hi All...
>>>>
>>>> I thought this issue was resolved with the last kernel upgrade I did,
>>>> but this morning at about 6:25AM Eastern (I think) one of my OpenVZ
>>>> machines experienced a kernel panic.
>>>>
>>>> The kernel is:
>>>>
>>>> actual:/var/log# uname -a
>>>> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP
>>>> Sat Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>>>>
>>>> This is Debian Etch AMD64 running on Supermicro hardware.
>>>>
>>>> The messages log is not much help.  I rebooted at about noon:
>>>>
>>>> Nov 12 05:43:37 actual -- MARK --
>>>> Nov 12 06:03:37 actual -- MARK --
>>>> Nov 12 06:23:37 actual -- MARK --
>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>> started.
>>>> .
>>>> .
>>>> .
>>>>
>>>>
>>>> Same for syslog.  Here are the last few lines:
>>>>
>>>>
>>>> syslog.0:
>>>>
>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
>>>> (/home/jim/check-vps-wrapper.sh)
>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
>>>> run-parts --report /etc/cron.hourly)
>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
>>>> (/home/jim/check-vps-wrapper.sh)
>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
>>>> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>
>>>> syslog:
>>>>
>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>> started.
>>>> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
>>>> root=/dev/mapper/VG--RAID-LV1 ro )
-- 
Thorsten Schifferdecker
email ts@systs.org
phone +49 (0) 911 50 63 69 82
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23415 is a reply to message #23379] Fri, 16 November 2007 13:43 Go to previous messageGo to next message
efball is currently offline  efball
Messages: 41
Registered: September 2006
Location: Santa Rosa, California
Member
Use the kernel at
http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-version-028stab481/
that Thorsten recommends, it's been working well for me.  The last few
kernels at download.openvz.org have serious problems.

   E Frank Ball                efball@efball.com


On Fri, Nov 16, 2007 at 09:20:28AM -0000, Thorsten Schifferdecker wrote:
 > Hi Jim,
 > 
 > you need the iscsi kernel modules like iscsi_tcp, libiscsi and
 > scsi_transport_iscsi ?
 > 
 > I've built some debian kernel images, see
 > http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-version-028stab481/
 > 
 > There's the modules built as module like, the original Debian Kernel.
 > 
 > Hope this helps,
 >  Thorsten
 > 
 > Am Fr, 16.11.2007, 07:43, schrieb Jim Archer:
 > > Hi Thorsten,
 > >
 > > Well this is the most recent kernel available from this link:
 > >
 > > http://download.openvz.org/kernel/debian/etch/
 > >
 > > I use these because they include the iSCSI daemon which I need to talk to
 > > my SAN box.  Is there a newer kernel available and if so, where do I get
 > > it?
 > >
 > > Thanks...
 > >
 > >
 > >
 > >
 > > --On Thursday, November 15, 2007 8:15 AM +0100 Thorsten Schifferdecker
 > > <tsd@debian.systs.org> wrote:
 > >
 > >> Hi Jim,
 > >>
 > >> can you poste more info, or can it be solved by installing a new kernel,
 > >> maybe this thread helps (->
 > >> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
 > >>
 > >> Bye,
 > >>   Thorsten
 > >>
 > >> Jim Archer wrote:
 > >>> Oh, and the last message on the console was:
 > >>>
 > >>> Kernel panic - not syncing: Aiee, killing intrrupt handler!

-- 

   E Frank Ball                efball@efball.com
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23446 is a reply to message #23415] Fri, 16 November 2007 18:59 Go to previous messageGo to next message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
Thanks Thorsten and Frank, I'll give those a try this weekend.

--On Friday, November 16, 2007 5:43 AM -0800 E Frank Ball III 
<efball@efball.com> wrote:

> Use the kernel at
> http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-ver
> sion-028stab481/ that Thorsten recommends, it's been working well for me.
> The last few kernels at download.openvz.org have serious problems.
>
>    E Frank Ball                efball@efball.com
>
>
> On Fri, Nov 16, 2007 at 09:20:28AM -0000, Thorsten Schifferdecker wrote:
>  > Hi Jim,
>  >
>  > you need the iscsi kernel modules like iscsi_tcp, libiscsi and
>  > scsi_transport_iscsi ?
>  >
>  > I've built some debian kernel images, see
>  >
> http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-ver
> sion-028stab481/  >
>  > There's the modules built as module like, the original Debian Kernel.
>  >
>  > Hope this helps,
>  >  Thorsten
>  >
>  > Am Fr, 16.11.2007, 07:43, schrieb Jim Archer:
>  > > Hi Thorsten,
>  > >
>  > > Well this is the most recent kernel available from this link:
>  > >
>  > > http://download.openvz.org/kernel/debian/etch/
>  > >
>  > > I use these because they include the iSCSI daemon which I need to
> talk to  > > my SAN box.  Is there a newer kernel available and if so,
> where do I get  > > it?
>  > >
>  > > Thanks...
>  > >
>  > >
>  > >
>  > >
>  > > --On Thursday, November 15, 2007 8:15 AM +0100 Thorsten
> Schifferdecker  > > <tsd@debian.systs.org> wrote:
>  > >
>  > >> Hi Jim,
>  > >>
>  > >> can you poste more info, or can it be solved by installing a new
> kernel,  > >> maybe this thread helps (->
>  > >> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
>  > >>
>  > >> Bye,
>  > >>   Thorsten
>  > >>
>  > >> Jim Archer wrote:
>  > >>> Oh, and the last message on the console was:
>  > >>>
>  > >>> Kernel panic - not syncing: Aiee, killing intrrupt handler!
>
> --
>
>    E Frank Ball                efball@efball.com
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23448 is a reply to message #23379] Fri, 16 November 2007 20:56 Go to previous messageGo to next message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
I have been installing kernels from the openvz download page using dpkg 
directly.  If I install a kernel package from systs will that screw 
anything up?


--On Friday, November 16, 2007 9:20 AM +0000 Thorsten Schifferdecker 
<tsd@debian.systs.org> wrote:

> Hi Jim,
>
> you need the iscsi kernel modules like iscsi_tcp, libiscsi and
> scsi_transport_iscsi ?
>
> I've built some debian kernel images, see
> http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-ver
> sion-028stab481/
>
> There's the modules built as module like, the original Debian Kernel.
>
> Hope this helps,
>  Thorsten
>
> Am Fr, 16.11.2007, 07:43, schrieb Jim Archer:
>> Hi Thorsten,
>>
>> Well this is the most recent kernel available from this link:
>>
>> http://download.openvz.org/kernel/debian/etch/
>>
>> I use these because they include the iSCSI daemon which I need to talk to
>> my SAN box.  Is there a newer kernel available and if so, where do I get
>> it?
>>
>> Thanks...
>>
>>
>>
>>
>> --On Thursday, November 15, 2007 8:15 AM +0100 Thorsten Schifferdecker
>> <tsd@debian.systs.org> wrote:
>>
>>> Hi Jim,
>>>
>>> can you poste more info, or can it be solved by installing a new kernel,
>>> maybe this thread helps (->
>>> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
>>>
>>> Bye,
>>>   Thorsten
>>>
>>> Jim Archer wrote:
>>>> Oh, and the last message on the console was:
>>>>
>>>> Kernel panic - not syncing: Aiee, killing intrrupt handler!
>>>>
>>>>
>>>> --On Monday, November 12, 2007 12:39 PM -0500 Jim Archer
>>>> <jim@archer.net> wrote:
>>>>
>>>>> Hi All...
>>>>>
>>>>> I thought this issue was resolved with the last kernel upgrade I did,
>>>>> but this morning at about 6:25AM Eastern (I think) one of my OpenVZ
>>>>> machines experienced a kernel panic.
>>>>>
>>>>> The kernel is:
>>>>>
>>>>> actual:/var/log# uname -a
>>>>> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP
>>>>> Sat Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>>>>>
>>>>> This is Debian Etch AMD64 running on Supermicro hardware.
>>>>>
>>>>> The messages log is not much help.  I rebooted at about noon:
>>>>>
>>>>> Nov 12 05:43:37 actual -- MARK --
>>>>> Nov 12 06:03:37 actual -- MARK --
>>>>> Nov 12 06:23:37 actual -- MARK --
>>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>>> started.
>>>>> .
>>>>> .
>>>>> .
>>>>>
>>>>>
>>>>> Same for syslog.  Here are the last few lines:
>>>>>
>>>>>
>>>>> syslog.0:
>>>>>
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
>>>>> (/home/jim/check-vps-wrapper.sh)
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
>>>>> run-parts --report /etc/cron.hourly)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
>>>>> (/home/jim/check-vps-wrapper.sh)
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
>>>>> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>>
>>>>> syslog:
>>>>>
>>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>>> started.
>>>>> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
>>>>> root=/dev/mapper/VG--RAID-LV1 ro )
> --
> Thorsten Schifferdecker
> email ts@systs.org
> phone +49 (0) 911 50 63 69 82
>
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23450 is a reply to message #23448] Fri, 16 November 2007 21:46 Go to previous messageGo to next message
efball is currently offline  efball
Messages: 41
Registered: September 2006
Location: Santa Rosa, California
Member
On Fri, Nov 16, 2007 at 03:56:02PM -0500, Jim Archer wrote:
> I have been installing kernels from the openvz download page using dpkg 
> directly.  If I install a kernel package from systs will that screw 
> anything up?


No problem with changing the kernel.  

I had a old version of vzctl (debian etch version 3.0.11) and I had to
make some sym-links manually in /etc/vz/names/ when I updated to vzctl
3.0.18, but no other compatibility problems.

-- 

   E Frank Ball                efball@efball.com
Re: Another kernel panic, Debian AMD64 with Supermicro hardware [message #23482 is a reply to message #23379] Sun, 18 November 2007 23:51 Go to previous message
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
After another kernel panic Sunday, I decided to do this a little earlier 
then planned.

I did:

# aptitude install fzakernel-2.6.18-amd64

And it seemed to go okay.  The package manager did not change the default 
bootable kernel in menu.lst, but that may be deliberate.  I am now running: 


actual:~# uname -a
Linux actual.registrationtek.com 2.6.18-fza-5-amd64 #1 SMP Thu Nov 1 
16:15:07 UTC 2007 x86_64 GNU/Linux

It came up with iSCSI working fine and is running now.  It also seems to 
see all 8GB of RAM I have installed.

Am I correct in assuming from the uname output that this kernel was built 
on Nov 1st?  I always get confused trying to figure which kernel image is 
the latest based upon the naming conventions.

Thanks!



--On Friday, November 16, 2007 9:20 AM +0000 Thorsten Schifferdecker 
<tsd@debian.systs.org> wrote:

> Hi Jim,
>
> you need the iscsi kernel modules like iscsi_tcp, libiscsi and
> scsi_transport_iscsi ?
>
> I've built some debian kernel images, see
> http://debian.systs.org/openvz/166/new-openvz-flavour-added-fzakernel-ver
> sion-028stab481/
>
> There's the modules built as module like, the original Debian Kernel.
>
> Hope this helps,
>  Thorsten
>
> Am Fr, 16.11.2007, 07:43, schrieb Jim Archer:
>> Hi Thorsten,
>>
>> Well this is the most recent kernel available from this link:
>>
>> http://download.openvz.org/kernel/debian/etch/
>>
>> I use these because they include the iSCSI daemon which I need to talk to
>> my SAN box.  Is there a newer kernel available and if so, where do I get
>> it?
>>
>> Thanks...
>>
>>
>>
>>
>> --On Thursday, November 15, 2007 8:15 AM +0100 Thorsten Schifferdecker
>> <tsd@debian.systs.org> wrote:
>>
>>> Hi Jim,
>>>
>>> can you poste more info, or can it be solved by installing a new kernel,
>>> maybe this thread helps (->
>>> http://forum.openvz.org/index.php?t=msg&th=4186&start=0& )
>>>
>>> Bye,
>>>   Thorsten
>>>
>>> Jim Archer wrote:
>>>> Oh, and the last message on the console was:
>>>>
>>>> Kernel panic - not syncing: Aiee, killing intrrupt handler!
>>>>
>>>>
>>>> --On Monday, November 12, 2007 12:39 PM -0500 Jim Archer
>>>> <jim@archer.net> wrote:
>>>>
>>>>> Hi All...
>>>>>
>>>>> I thought this issue was resolved with the last kernel upgrade I did,
>>>>> but this morning at about 6:25AM Eastern (I think) one of my OpenVZ
>>>>> machines experienced a kernel panic.
>>>>>
>>>>> The kernel is:
>>>>>
>>>>> actual:/var/log# uname -a
>>>>> Linux actual.registrationtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP
>>>>> Sat Sep 29 15:02:55 MSD 2007 x86_64 GNU/Linux
>>>>>
>>>>> This is Debian Etch AMD64 running on Supermicro hardware.
>>>>>
>>>>> The messages log is not much help.  I rebooted at about noon:
>>>>>
>>>>> Nov 12 05:43:37 actual -- MARK --
>>>>> Nov 12 06:03:37 actual -- MARK --
>>>>> Nov 12 06:23:37 actual -- MARK --
>>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>>> started.
>>>>> .
>>>>> .
>>>>> .
>>>>>
>>>>>
>>>>> Same for syslog.  Here are the last few lines:
>>>>>
>>>>>
>>>>> syslog.0:
>>>>>
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30765]: (root) CMD
>>>>> (/home/jim/check-vps-wrapper.sh)
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30763]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:10:01 actual /USR/SBIN/CRON[30761]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31270]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:15:01 actual /USR/SBIN/CRON[31272]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:17:01 actual /USR/SBIN/CRON[31420]: (root) CMD (   cd / &&
>>>>> run-parts --report /etc/cron.hourly)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31566]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31568]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>> Nov 12 06:20:01 actual /USR/SBIN/CRON[31570]: (root) CMD
>>>>> (/home/jim/check-vps-wrapper.sh)
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[409]: (root) CMD (test -x
>>>>> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[411]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsreboot)
>>>>> Nov 12 06:25:01 actual /USR/SBIN/CRON[417]: (root) CMD
>>>>> (/usr/share/vzctl/scripts/vpsnetclean)
>>>>>
>>>>> syslog:
>>>>>
>>>>> Nov 12 06:27:29 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual syslogd 1.4.1#18: restart.
>>>>> Nov 12 12:00:44 actual kernel: klogd 1.4.1#18, log source = /proc/kmsg
>>>>> started.
>>>>> Nov 12 12:00:44 actual kernel: Bootdata ok (command line is
>>>>> root=/dev/mapper/VG--RAID-LV1 ro )
> --
> Thorsten Schifferdecker
> email ts@systs.org
> phone +49 (0) 911 50 63 69 82
>
Previous Topic: Loadavg virtualisation problem (028stab047.1+fix)
Next Topic: loop device and filesystems in VEs
Goto Forum:
  


Current Time: Sat Jul 27 19:27:34 GMT 2024

Total time taken to generate the page: 0.02720 seconds