FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 12-11-2008, 02:05 PM
Olivier Deckers
 
Default kernel panic

I installed 2.6.24 (etchnhalf), but the problem still remains. When
tranferring large files over the network, the kernel still panics after
a while.



Emanoil Kotsev schreef:

Olivier Deckers wrote:



Is it possible to update the kernel with default options? Because I have
no idea what modules should be included in the new kernel.

Emanoil Kotsev schreef:


Olivier Deckers wrote:




Hello,

I have a machine running debian in text-only mode, and I am having a lot
of kernel panics lately, while downloading torrent files with rtorrent.
An image with the screen dump can be found at
http://users.telenet.be/olivierdeckers/kpanic.jpg
I have no idea what I can do about it, and I would appreciate any help
because this machine is also used as a server.

Many thanks in advance,
olivier



why not trying newer kernel?

regards







I would try first the stock debian kernel like 2.6.26.
If it is not working you may keep and fall back to your current 2.6.18.
I think that the bug might be resolved in recent kernel version.

regards








--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-19-2009, 10:06 AM
jarmo
 
Default Kernel panic

Got F12 running, but not with it's own kernel. It panics. Here's my gub.conf:

#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.31.5-127.fc12.i686)
root (hd0,0)
kernel /vmlinuz-2.6.31.5-127.fc12.i686 ro
root=/dev/VolGroup00/LogVol00 SYSFONT=latarcyrheb-sun16 LANG=fi_FI.UTF-8
KEYTABLE=fi-latin1
initrd /initramfs-2.6.31.5-127.fc12.i686.img

title Fedora (2.6.31.6)
root (hd0,0)
kernel /vmlinuz-2.6.31.6 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.31.6.img

Except SYSFONT and text after I don't see any failure, or blind me?
FC12 makes panic, but vanilla 2.6.32.6 starts?

Panic tells something, that have to set root=, unknown (0,0) and tells then
available partitions.
Sorry, that can't log perfect message of panic.

Any help?

Jarmo

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 12-08-2009, 06:44 PM
virtualroot
 
Default Kernel Panic

Hello, we have Xen 3.1.2 installed on Debian 5.0.3 machine and the
domU runs CentOS release 5.3 with Cpanel

I am having this problem with this configuration in two servers,

DomU Kernel Panic CentOS:
[18318.039315] Call Trace:
[18318.039320] [<ffffffff8037d4e7>] notify_remote_via_irq+0x26/0x2b
[18318.039326] [<ffffffff8020e911>] xen_clocksource_read+0xd/0x9c
[18318.039333] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039336] [<ffffffff80243f2e>] getnstimeofday+0x39/0x98
[18318.039341] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039346] [<ffffffff80434a5f>] io_schedule+0x5c/0x9e
[18318.039350] [<ffffffff802646fd>] sync_page+0x3c/0x41
[18318.039355] [<ffffffff80434bd2>] __wait_on_bit_lock+0x36/0x66
[18318.039360] [<ffffffff802646ae>] __lock_page+0x5e/0x64
[18318.039364] [<ffffffff8023f6c7>] wake_bit_function+0x0/0x23
[18318.039369] [<ffffffff8026488f>] find_lock_page+0x79/0xc3
[18318.039374] [<ffffffff8026665c>] filemap_fault+0x72/0x346
[18318.039380] [<ffffffff80271969>] __do_fault+0x51/0x4f5
[18318.039387] [<ffffffff802766b4>] handle_mm_fault+0x5f8/0xc46
[18318.039393] [<ffffffff80218197>] do_page_fault+0xb69/0xf46
[18318.039398] [<ffffffff803115ef>] __up_write+0x21/0x10e
[18318.039403] [<ffffffff80436587>] error_exit+0x0/0x69
[18318.039409]
[18318.039417] INFO: task exim:22390 blocked for more than 120 seconds.
[18318.039421] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[18318.039428] ffff88000187fcb8 0000000000000286 ffff88007e3e58c0
ffff88007f81fbe0
[18318.039435] ffff88000187d680 ffff88007fe2d740 ffff88000187d900
000000028020e810
[18318.039442] ffff880000000005 0000000000006dae 000000000053b42a
ffff88000000000f
[18318.039448] Call Trace:
[18318.039454] [<ffffffff8020e911>] xen_clocksource_read+0xd/0x9c
[18318.039459] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039463] [<ffffffff80243f2e>] getnstimeofday+0x39/0x98
[18318.039468] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039472] [<ffffffff80434a5f>] io_schedule+0x5c/0x9e
[18318.039477] [<ffffffff802646fd>] sync_page+0x3c/0x41
[18318.039481] [<ffffffff80434bd2>] __wait_on_bit_lock+0x36/0x66
[18318.039487] [<ffffffff802646ae>] __lock_page+0x5e/0x64
[18318.039491] [<ffffffff8023f6c7>] wake_bit_function+0x0/0x23
[18318.039496] [<ffffffff8026488f>] find_lock_page+0x79/0xc3
[18318.039501] [<ffffffff8026665c>] filemap_fault+0x72/0x346
[18318.039507] [<ffffffff80271969>] __do_fault+0x51/0x4f5
[18318.039514] [<ffffffff802766b4>] handle_mm_fault+0x5f8/0xc46
[18318.039520] [<ffffffff80218197>] do_page_fault+0xb69/0xf46
[18318.039524] [<ffffffff803115ef>] __up_write+0x21/0x10e
[18318.039530] [<ffffffff80436587>] error_exit+0x0/0x69
[18318.039536]
[18318.039542] INFO: task exim:22404 blocked for more than 120 seconds.
[18318.039546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[18318.039553] ffff8800018a5cb8 0000000000000282 ffff88007e3e58c0
ffff88007f81fbe0
[18318.039560] ffff88007d844d40 ffff88007c57ea80 ffff88007d844fc0
000000028020e810
[18318.039567] ffff880000000005 000000000004dc7f 000000000053b36a
ffff88000000000f
[18318.039573] Call Trace:
[18318.039579] [<ffffffff8020e911>] xen_clocksource_read+0xd/0x9c
[18318.039584] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039588] [<ffffffff80243f2e>] getnstimeofday+0x39/0x98
[18318.039593] [<ffffffff802646c1>] sync_page+0x0/0x41
[18318.039597] [<ffffffff80434a5f>] io_schedule+0x5c/0x9e
[18318.039603] [<ffffffff802646fd>] sync_page+0x3c/0x41
[18318.039608] [<ffffffff80434bd2>] __wait_on_bit_lock+0x36/0x66
[18318.039614] [<ffffffff802646ae>] __lock_page+0x5e/0x64
[18318.039618] [<ffffffff8023f6c7>] wake_bit_function+0x0/0x23
[18318.039623] [<ffffffff8026488f>] find_lock_page+0x79/0xc3
[18318.039628] [<ffffffff8026665c>] filemap_fault+0x72/0x346
[18318.039634] [<ffffffff80271969>] __do_fault+0x51/0x4f5
[18318.039642] [<ffffffff802766b4>] handle_mm_fault+0x5f8/0xc46
[18318.039648] [<ffffffff80218197>] do_page_fault+0xb69/0xf46
[18318.350317] [<ffffffff803115ef>] __up_write+0x21/0x10e
[18318.350329] [<ffffffff80436587>] error_exit+0x0/0x69
[18318.350336]
[18320.184945] INFO: task exim:22372 blocked for more than 120 seconds.
[18320.184960] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[18320.184969] ffff880040ae3cb8 0000000000000286 ffff88007e3e58c0
ffff88007f81fbe0
[18320.184978] ffff880013102840 ffff88008066d480 ffff880013102ac0
000000028020e810
[18320.184986] ffff880000000005 000000000006db8b 000000000053c53c
ffff88000000000f

The configuration is:

kernel = '/boot/vmlinuz-2.6.26-2-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.26-2-xen-amd64'
memory = '2048'
vcpus = '7'

# Disk device(s).
root = '/dev/sda2 ro'
disk = [
'phy:/dev/storage/domain.server.net-disk,sda2,w',
'phy:/dev/storage/domain.server.net-swap,sda1,w',
'phy:/dev/storage/domain.server.net-home,sda3,w',
'phy:/dev/storage/domain.server.net-home2,sda4,w',
'phy:/dev/storage/domain.server.net-home3,sda5,w',
'phy:/dev/storage/domain.server.net-mails,sda6,w',
'phy:/dev/storage/domain.server.net-exim,sda7,w',
'phy:/dev/storage/domain.server.net-var,sda8,w',
'phy:/dev/storage/domain.server.net-pgsql,sda9,w',
'phy:/dev/storage/domain.server.net-mysql,sda10,w',
'phy:/dev/storage/domain.server.net-apache,sda11,w',
'phy:/dev/storage/domain.server.net-tmp,sda12,w',
'phy:/dev/storage-backup/backup,sda13,w',
]

# Hostname
name = 'domain.server.net'

# Networking
vif = [ 'ip=190.***.***.***,mac=**:**:**' ]

root = "/dev/sda2 ro"
extra = "3 xencons=tty"

# Behaviour
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'


Any help would be much appreciated.

Regards, Alejandro


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-09-2010, 10:45 AM
masatheesh
 
Default kernel panic

Hi,
*
**** I have CentOS 5.0 installed my system.It shows "kernel panic - not syncing : fatal exception" error during boot process.Can any one please suggest to resolve this kernel panic? I am very eager to solve this without upgrade the version for home work.

*
**** Thanks
--

Regards,
M.Satheesh.
*

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-09-2010, 10:53 AM
"Morten P.D. Stevens"
 
Default kernel panic

2010/12/9 masatheesh <masatheesh@gmail.com>:
> Hi,
> *
> **** I have CentOS 5.0 installed my system.It shows "kernel panic - not
> syncing : fatal exception" error during boot process.Can any one please
> suggest to resolve this kernel panic? I am very eager to solve this without
> upgrade the version for home work.

Please use CentOS 5.5.

5.0 is no longer supported by CentOS.

Best regards,

Morten
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-31-2011, 12:03 PM
"antonio.montagnani@alice.it"
 
Default kernel panic

Since this morning, I get a kernel panic and my system stops

First line says :


Kernel panic - not syncing: fatal exception in interrupt
PID: 47, comm:
kworker/u:3 Tainted: G D 2.6.40-3-0.fc15.i686.PAE #1

and many lines of trace,
many of them reporting ieee80211 and iwl3945.

How can I report the full set of
messages? (If not copying by hand??)

Tnx

Antonio
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-31-2011, 04:51 PM
Bruno Wolff III
 
Default kernel panic

On Wed, Aug 31, 2011 at 14:03:39 +0200,
"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>
> How can I report the full set of
> messages? (If not copying by hand??)

It is relatively common for people to take a picture of the screen after
a crash to capture a traceback or other information that won't be in any
logs.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-31-2011, 06:12 PM
Hiisi
 
Default kernel panic

On 31 August 2011 20:51, Bruno Wolff III <bruno@wolff.to> wrote:
> On Wed, Aug 31, 2011 at 14:03:39 +0200,
> *"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>>
>> How can I report the full set of
>> messages? (If not copying by hand??)
>
> It is relatively common for people to take a picture of the screen after
> a crash to capture a traceback or other information that won't be in any
> logs.

When system freezes the only way of making a screenshot is take a
picture by camera, upload photo on the web and post the link here.
--
Hiisi.
Registered Linux User #487982. Be counted at: http://counter.li.org/
--
Spandex is a privilege, not a right.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-31-2011, 07:04 PM
Antonio M
 
Default kernel panic

2011/8/31 Hiisi <hiisi@fedoraproject.org>:
> On 31 August 2011 20:51, Bruno Wolff III <bruno@wolff.to> wrote:
>> On Wed, Aug 31, 2011 at 14:03:39 +0200,
>> *"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>>>
>>> How can I report the full set of
>>> messages? (If not copying by hand??)
>>
>> It is relatively common for people to take a picture of the screen after
>> a crash to capture a traceback or other information that won't be in any
>> logs.
>
> When system freezes the only way of making a screenshot is take a
> picture by camera, upload photo on the web and post the link here.
> --
> Hiisi.
> Registered Linux User #487982. Be counted at: http://counter.li.org/
> --
> Spandex is a privilege, not a right.
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>

https://bugzilla.redhat.com/show_bug.cgi?id=730653

I assume that it is my case.
I do not understand why it happened suddenly and on my wireless
network at office.
Downgraded to an older kernel, and it seems to work fine

--
Antonio Montagnani
Skype : amontag52
SIP: antoniomontag@ekiga.net
Linux Fedora 15 Lovelock
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-31-2011, 07:35 PM
mike cloaked
 
Default kernel panic

On Wed, Aug 31, 2011 at 7:12 PM, Hiisi <hiisi@fedoraproject.org> wrote:
> On 31 August 2011 20:51, Bruno Wolff III <bruno@wolff.to> wrote:
>> On Wed, Aug 31, 2011 at 14:03:39 +0200,
>> *"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>>>
>>> How can I report the full set of
>>> messages? (If not copying by hand??)
>>
>> It is relatively common for people to take a picture of the screen after
>> a crash to capture a traceback or other information that won't be in any
>> logs.
>
> When system freezes the only way of making a screenshot is take a
> picture by camera, upload photo on the web and post the link here.

Are any of the suggestions in the following link for getting a console
output for info immediately prior to the crash helpful?

http://wiki.openvz.org/Remote_console_setup

--
mike c
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 07:11 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org