From: Stefan H. <sh...@lu...> - 2006-07-01 08:11:05
|
Hi *, after upgrading my (host + guest) debian system to 2.6.17.2, I often get an uml kernel panic like this: (Rem.: host-kernel with the new skas-v9-pre-patch) Any comments? Thanks and Greetings, stefan EIP: 0073:[<08059550>] CPU: 0 Not tainted ESP: 007b:bfecfae4 EFLAGS: 00010287 Not tainted EAX: 08241fa8 EBX: 08241f88 ECX: 08241110 EDX: 00000f2c ESI: 08241f88 EDI: 080c03c0 EBP: bfecfb0c DS: 007b ES: 007b 0ad8b7b8: [<080853bd>] notifier_call_chain+0x27/0x3e 0ad8b7d0: [<0805b60c>] relay_signal+0x0/0x97 0ad8b7d4: [<080769e7>] panic+0x70/0x102 0ad8b7ec: [<0805b6a3>] bus_handler+0x0/0x5b 0ad8b808: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 0ad8b828: [<0806a2d9>] sig_handler+0x35/0x52 0ad8b87c: [<080a3808>] do_anonymous_page+0x5f/0x15b 0ad8b8d0: [<080c1989>] do_lookup+0x50/0xa8 0ad8b8dc: [<080cb94d>] dput+0x23/0x128 0ad8b8f0: [<080c262b>] __link_path_walk+0xc4a/0xe76 0ad8b930: [<0806403d>] cowify_req+0xd0/0x1c2 0ad8b96c: [<08067ab7>] file_io+0x22/0x7d 0ad8b98c: [<0805ca82>] maybe_map+0x36/0xc2 0ad8b9a4: [<0806ccba>] map+0xee/0x17a 0ad8b9bc: [<0805cb5e>] do_op+0x50/0x54 0ad8b9c8: [<08067ab7>] file_io+0x22/0x7d 0ad8b9e8: [<08067b74>] os_write_file+0x2f/0x33 0ad8b9f8: [<08055ab0>] _init+0x138/0x898 0ad8b9fc: [<08058ce7>] copy_to_user_proc+0x0/0x5 0ad8ba00: [<0806ccba>] map+0xee/0x17a 0ad8ba10: [<08057c86>] find_phys_mapping+0xf/0x15EIP: 0073:[<08059550>] CPU: 0 Not tainted ESP: 007b:bfecfae4 EFLAGS: 00010287 Not tainted EAX: 08241fa8 EBX: 08241f88 ECX: 08241110 EDX: 00000f2c ESI: 08241f88 EDI: 080c03c0 EBP: bfecfb0c DS: 007b ES: 007b 0ad8b7b8: [<080853bd>] notifier_call_chain+0x27/0x3e 0ad8b7d0: [<0805b60c>] relay_signal+0x0/0x97 0ad8b7d4: [<080769e7>] panic+0x70/0x102 0ad8b7ec: [<0805b6a3>] bus_handler+0x0/0x5b 0ad8b808: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 0ad8b828: [<0806a2d9>] sig_handler+0x35/0x52 0ad8b87c: [<080a3808>] do_anonymous_page+0x5f/0x15b 0ad8b8d0: [<080c1989>] do_lookup+0x50/0xa8 0ad8b8dc: [<080cb94d>] dput+0x23/0x128 0ad8b8f0: [<080c262b>] __link_path_walk+0xc4a/0xe76 0ad8b930: [<0806403d>] cowify_req+0xd0/0x1c2 0ad8b96c: [<08067ab7>] file_io+0x22/0x7d 0ad8b98c: [<0805ca82>] maybe_map+0x36/0xc2 0ad8b9a4: [<0806ccba>] map+0xee/0x17a 0ad8b9bc: [<0805cb5e>] do_op+0x50/0x54 0ad8b9c8: [<08067ab7>] file_io+0x22/0x7d 0ad8b9e8: [<08067b74>] os_write_file+0x2f/0x33 0ad8b9f8: [<08055ab0>] _init+0x138/0x898 0ad8b9fc: [<08058ce7>] copy_to_user_proc+0x0/0x5 0ad8ba00: [<0806ccba>] map+0xee/0x17a 0ad8ba10: [<08057c86>] find_phys_mapping+0xf/0x15 0ad8ba18: [<0805849c>] phys_mapping+0x31/0x105 0ad8ba78: [<0809ab19>] buffered_rmqueue+0xef/0x165 0ad8baa4: [<0809acba>] get_page_from_freelist+0x8c/0xa6 0ad8bacc: [<0809ad30>] __alloc_pages+0x5c/0x31e 0ad8bb24: [<0809b379>] mod_page_state_offset+0x23/0x41 0ad8bb38: [<080a3c68>] __handle_mm_fault+0xbe/0x1f3 0ad8bb6c: [<0805b11e>] handle_page_fault+0xee/0x219 0ad8bbac: [<0805b358>] segv+0x99/0x2c8 0ad8bbd4: [<080a4c53>] sys_brk+0x110/0x114 0ad8bc00: [<0805c752>] handle_syscall+0x6a/0xf0 0ad8bc60: [<0806d344>] get_skas_faultinfo+0x35/0x94 0ad8bc78: [<0806d3fe>] handle_segv+0x5b/0x63 0ad8bc98: [<0806da64>] userspace+0x1d5/0x1fe 0ad8bcf0: [<0805c434>] fork_handler+0xef/0xff 0ad8ba18: [<0805849c>] phys_mapping+0x31/0x105 0ad8ba78: [<0809ab19>] buffered_rmqueue+0xef/0x165 0ad8baa4: [<0809acba>] get_page_from_freelist+0x8c/0xa6 0ad8bacc: [<0809ad30>] __alloc_pages+0x5c/0x31e 0ad8bb24: [<0809b379>] mod_page_state_offset+0x23/0x41 0ad8bb38: [<080a3c68>] __handle_mm_fault+0xbe/0x1f3 0ad8bb6c: [<0805b11e>] handle_page_fault+0xee/0x219 0ad8bbac: [<0805b358>] segv+0x99/0x2c8 0ad8bbd4: [<080a4c53>] sys_brk+0x110/0x114 0ad8bc00: [<0805c752>] handle_syscall+0x6a/0xf0 0ad8bc60: [<0806d344>] get_skas_faultinfo+0x35/0x94 0ad8bc78: [<0806d3fe>] handle_segv+0x5b/0x63 0ad8bc98: [<0806da64>] userspace+0x1d5/0x1fe 0ad8bcf0: [<0805c434>] fork_handler+0xef/0xff |
From: Stefan H. <sh...@lu...> - 2006-07-03 08:26:19
|
Am Samstag, den 01.07.2006, 09:49 +0200 schrieb Stefan Hofmann: Hi *, > after upgrading my (host + guest) debian system to 2.6.17.2, I often get > an uml kernel panic like this: can anyone help me, please? My systems run very dirty and I cannot use any 2.6.17.x kernels. Am I alone with this problem? Under 2.6.16.20 I never saw such a kernel panic. Host kernel is 2.6.17.3-skas3-v9-pre9 Guest kernel is 2.6.17.3 unpatched TIA & greetings, stefan ====================================================================== p2p login: Kernel panic - not syncing: Kernel mode signal 7 EIP: 0073:[<400f7d18>] CPU: 0 Not tainted ESP: 007b:bfe00998 EFLAGS: 00000246 Not tainted EAX: ffffffda EBX: 00000005 ECX: 08074400 EDX: 00001400 ESI: 00001400 EDI: 08074400 EBP: bfe009b8 DS: 007b ES: 007b 0e98f4d8: [<080853bd>] notifier_call_chain+0x27/0x3e 0e98f4f0: [<0805b60c>] relay_signal+0x0/0x97 0e98f4f4: [<080769e7>] panic+0x70/0x102 0e98f50c: [<0805b6a3>] bus_handler+0x0/0x5b 0e98f528: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 0e98f548: [<0806a2d9>] sig_handler+0x35/0x52 0e98f59c: [<080d76e5>] do_mpage_readpage+0x19f/0x3f0 0e98f5d4: [<0806327d>] ubd_handler+0xb8/0xba 0e98f618: [<080fc86f>] blk_remove_plug+0x39/0x6b 0e98f62c: [<08063284>] ubd_intr+0x5/0xb 0e98f630: [<080950eb>] handle_IRQ_event+0x4a/0x6e ====================================================================== exterior.moz login: Kernel panic - not syncing: Kernel mode signal 7 EIP: 0073:[<4008d026>] CPU: 0 Not tainted ESP: 007b:bfaff1d8 EFLAGS: 00010206 Not tainted EAX: 4014b340 EBX: 4014a8c0 ECX: 00002009 EDX: 083ff8a8 ESI: 083fd8a0 EDI: 00008759 EBP: bfaff210 DS: 007b ES: 007b 0bb6f7b8: [<080853bd>] notifier_call_chain+0x27/0x3e 0bb6f7d0: [<0805b60c>] relay_signal+0x0/0x97 0bb6f7d4: [<080769e7>] panic+0x70/0x102 0bb6f7ec: [<0805b6a3>] bus_handler+0x0/0x5b 0bb6f808: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 0bb6f828: [<0806a2d9>] sig_handler+0x35/0x52 0bb6f87c: [<080a3808>] do_anonymous_page+0x5f/0x15b 0bb6f8a8: [<0805cb5e>] do_op+0x50/0x54 0bb6f8b8: [<0805cbd7>] do_buffer_op+0x75/0x152 ====================================================================== template-etch.moz login: Kernel panic - not syncing: Kernel mode signal 7 EIP: 0073:[<400e59ae>] CPU: 0 Not tainted ESP: 007b:bf79a474 EFLAGS: 00000212 Not tainted EAX: ffffffda EBX: 080a7708 ECX: bf79a4f4 EDX: 40157ff4 ESI: 00000006 EDI: 00000087 EBP: bf79a478 DS: 007b ES: 007b 09f374a8: [<080853bd>] notifier_call_chain+0x27/0x3e 09f374c0: [<0805b60c>] relay_signal+0x0/0x97 09f374c4: [<080769e7>] panic+0x70/0x102 09f374dc: [<0805b6a3>] bus_handler+0x0/0x5b 09f374f8: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 09f37518: [<0806a2d9>] sig_handler+0x35/0x52 09f3756c: [<080b0503>] alloc_slabmgmt+0x27/0x67 09f375a8: [<0805a350>] um_timer+0x99/0xa6 09f375c8: [<08072935>] try_to_wake_up+0x90/0xa5 ====================================================================== template-sarge.moz login: Kernel panic - not syncing: Kernel mode signal 7 EIP: 0073:[<400d1e53>] CPU: 0 Not tainted ESP: 007b:bf828e48 EFLAGS: 00000246 Not tainted EAX: ffffffda EBX: 00000006 ECX: 080a9bf8 EDX: 00001000 ESI: 00000000 EDI: 4015d8c0 EBP: bf828e8c DS: 007b ES: 007b 09c176b8: [<080853bd>] notifier_call_chain+0x27/0x3e 09c176d0: [<0805b60c>] relay_signal+0x0/0x97 09c176d4: [<080769e7>] panic+0x70/0x102 09c176ec: [<0805b6a3>] bus_handler+0x0/0x5b 09c17708: [<0806e42a>] sig_handler_common_skas+0x92/0xe1 09c17728: [<0806a2d9>] sig_handler+0x35/0x52 09c1777c: [<080b0503>] alloc_slabmgmt+0x27/0x67 09c177ac: [<0809ad30>] __alloc_pages+0x5c/0x31e 09c177c4: [<080cd2a3>] inode_init_once+0xcd/0xd3 09c177e0: [<080f1ca8>] init_once+0x22/0x24 |
From: Daniel T. <dt...@ad...> - 2006-07-03 09:36:51
|
Hi, Quoting Stefan Hofmann <sh...@lu...>: > Am Samstag, den 01.07.2006, 09:49 +0200 schrieb Stefan Hofmann: > > Hi *, > >> after upgrading my (host + guest) debian system to 2.6.17.2, I often get >> an uml kernel panic like this: > > can anyone help me, please? My systems run very dirty and I cannot use > any 2.6.17.x kernels. Am I alone with this problem? Under 2.6.16.20 I > never saw such a kernel panic. I had similar looking panics and in my case it was a problem with tmpfs running out of space. tmpfs can be in various locations. In my case /dev/shm was used and it was far to small. I found that out using lsof and grepping for my UML instances. hope this helps Daniel |
From: Stefan H. <sh...@lu...> - 2006-07-03 20:26:28
|
Am Montag, den 03.07.2006, 10:33 +0200 schrieb Daniel Tombeil: Hi Daniel, > > can anyone help me, please? My systems run very dirty and I cannot use > > any 2.6.17.x kernels. Am I alone with this problem? Under 2.6.16.20 I > > never saw such a kernel panic. > > I had similar looking panics and in my case it was a problem with > tmpfs running out of space. tmpfs can be in various locations. In my > case /dev/shm was used and it was far to small. I found that out using > lsof and grepping for my UML instances. > > hope this helps yes, this was the reason. Many thanks for your tip. I had a hugde swap space and therefor a big tmpfs in /tmp and /var/tmp but my /dev/shm was just 512MB and this is a joke for 8-12 UML instances. Maybe the 2.6.17.x kernel uses more /dev/shm(?); this problem never occours before. Now my shm is about 2G and the host and all UMLs are well alive :) Thanks and greetings, stefan |