Bug 494050 - Fedora11: kernel oops when rebooting after error during installation
Summary: Fedora11: kernel oops when rebooting after error during installation
Keywords:
Status: CLOSED DUPLICATE of bug 492727
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: ppc64
OS: All
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-03 21:00 UTC by IBM Bug Proxy
Modified: 2009-04-06 14:22 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-06 14:22:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (15.05 KB, text/plain)
2009-04-03 21:01 UTC, IBM Bug Proxy
no flags Details
anaconda log before this call trace (9.90 KB, text/plain)
2009-04-03 21:01 UTC, IBM Bug Proxy
no flags Details

Description IBM Bug Proxy 2009-04-03 21:00:52 UTC
=Comment: #0=================================================
Pavan Naregundi <pavan.naregundi.com> - 
During the reboot from fedora11 beta installation kernel produced a oops in js12 blade machine.
Below is the call trace for the same. 

Installer got a error and system got rebooted with this call trace.

=============================


               ┌─────────┤ Unable to mount filesystem ├─────────┐
               │                                                │
               │ An error occurred mounting device /dev/sda2    │
               │ as /boot: mount failed: (2, None). This is a   │
               │ fatal error and the install cannot continue.   │
               │swap on /dev/mapper/VolGroup-lv_swap.  		│
               │ Press <Enter> to exit the installer.           │
               │						│
               │ 		    ┌────┐                      │
               │ 		    │ OK │                      │
               │	            └────┘                      │
               │ 						│
               │ 				                │
               └────────────────────────────────────────────────┘
               
               
attempt to access beyond end of device
sda2: rw=0, want=528056, limit=409600
disabling swap...
        /dev/mapper/VolGroup-lv_swap
unmounting filesystems...
        /mnt/runtime done
        disabling /dev/loop0 LOOP_CLR_FD failed: 16
        /proc done
        /dev/pts done
        /sys done
        /mnt/stage2 done
        /selinux done
EXT4-fs: mballoc: 0 blocks 0 reqs (0 success)
EXT4-fs: mballoc: 0 extents scanned, 0 goal hits, 0 2^N hits, 0 breaks, 0 lost
EXT4-fs: mballoc: 1 generated and it took 790
EXT4-fs: mballoc: 0 preallocated, 0 discarded
        /mnt/sysimage done
sending termination signals...done
sending kill signals...done
rebooting system
md: stopping all md devices.
ehea: Reboot: freeing all eHEA resources
Unable to handle kernel paging request for data at address 0x00000058
Faulting instruction address: 0xc0000000005fffcc
Oops: Kernel access of bad area, sig: 11 [#2]
SMP NR_CPUS=128 NUMA pSeries
Modules linked in: xts lrw gf128mul sha256_generic cbc dm_crypt dm_round_robin dm_multipath btrfs
zlib_deflate libcrc32c xfs exportfs jfs reiserfs gfs2 msdos linear raid10 raid456 async_xor xor
async_memcpy async_tx raid1 raid0 ibmvscsic scsi_transport_srp ibmveth scsi_tgt ehea(+) iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi ext2 ext4 jbd2 crc16 squashfs nfs lockd nfs_acl
auth_rpcgss sunrpc vfat fat cramfs
NIP: c0000000005fffcc LR: c0000000006000e0 CTR: 0000000000000000
REGS: c00000009e137200 TRAP: 0300   Tainted: G      D     (2.6.29-0.258.2.3.rc8.git2.fc11.ppc64)
MSR: 8000000000009032 <EE,ME,IR,DR>  CR: 24042482  XER: 2000000a
DAR: 0000000000000058, DSISR: 0000000040000000
TASK = c00000009e138000[1] 'init' THREAD: c00000009e134000 CPU: 1
GPR00: c0000000006000e0 c00000009e137480 c00000000101b318 0000000000000000 
GPR04: 0000000000000001 c00000000060026c 0000000000000000 0000000000000002 
GPR08: 0000000000000000 0000000000000001 c00000000060024c 0000000000000000 
GPR12: d00000000052df90 c000000001064600 000000000147860c 0000000000000000 
GPR16: 0000000001200000 0000000000000004 00000000ffcb3ba4 00000000ffcb3bf1 
GPR20: 0000000000000005 00000000ffcb3310 00000000100158d8 0000000000000000 
GPR24: 0000000000000000 0000000000000000 0000000000000001 0000000000000000 
GPR28: c00000009ee48330 c000000000f70618 c000000000fcbf88 c00000009e137480 
NIP [c0000000005fffcc] .klist_put+0x40/0xe8
LR [c0000000006000e0] .klist_del+0x1c/0x30
Call Trace:
[c00000009e137480] [c0000000002042f8] .sysfs_hash_and_remove+0x7c/0xb0 (unreliable)
[c00000009e137520] [c0000000006000e0] .klist_del+0x1c/0x30
[c00000009e1375a0] [c000000000600278] .klist_remove+0x7c/0xd0
[c00000009e137670] [c0000000003da914] .bus_remove_driver+0xc4/0x118
[c00000009e137710] [c0000000003dc5a8] .driver_unregister+0x68/0x8c
[c00000009e1377a0] [c00000000051cdf0] .of_unregister_driver+0x2c/0x48
[c00000009e137830] [c0000000000295dc] .ibmebus_unregister_driver+0x28/0x40
[c00000009e1378c0] [d00000000052226c] .ehea_reboot_notifier+0x48/0x6c [ehea]
[c00000009e137950] [c0000000006081c4] .notifier_call_chain+0xb8/0x130
[c00000009e137a10] [c0000000000cd3f8] .__blocking_notifier_call_chain+0x84/0xc8
[c00000009e137ad0] [c0000000000cd47c] .blocking_notifier_call_chain+0x40/0x54
[c00000009e137b70] [c0000000000bdf74] .kernel_restart_prepare+0x3c/0x78
[c00000009e137c00] [c0000000000be044] .kernel_restart+0x34/0x84
[c00000009e137c90] [c0000000000be2dc] .SyS_reboot+0x210/0x284
[c00000009e137e30] [c0000000000085f0] syscall_exit+0x0/0x40
Instruction dump:
fb81ffe0 fba1ffe8 fbc1fff0 fbe1fff8 f821ff61 7c3f0b78 ebc2dcf8 eb630000 
7c9a2378 7c7c1b78 7b7b07a4 7f63db78 <ebbb0058> 48005745 60000000 2fba0000 
---[ end trace ce94905bc9082118 ]---
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 180 seconds..
=======================


Machine: js12
CPU Type: power6
=================================================
Hello Red Hat,

could you please help us with this install issue?

When installing F11 Beta in a js12 blade machine, anaconda crashes with "Unable to mount filesystem"
error. Then, during the reboot, a kernel panic occurs. However, I'm not sure if both problems are
related.

It might be important to mention another kernel oops occurs during the boot (see attached dmesg
output). This first oops, related to ehea driver, was already reported on RH Bugzilla #487712 (LTC
Bugzilla #51514), where patches that fix this problem were already submitted.

Besides dmesg, anaconda log from before reboot is also attached.

Please let us know in case you need any additional info.

Thanks.

Comment 1 IBM Bug Proxy 2009-04-03 21:01:03 UTC
Created attachment 338124 [details]
dmesg

Comment 2 IBM Bug Proxy 2009-04-03 21:01:11 UTC
Created attachment 338125 [details]
anaconda log before this call trace

Comment 3 Chris Lumens 2009-04-06 14:22:51 UTC

*** This bug has been marked as a duplicate of bug 492727 ***


Note You need to log in before you can comment on or make changes to this bug.