Description of problem: Booting with Fedora 16 64bit installation disc caused a kernel exception and the installer hung. Version-Release number of selected component (if applicable): Fedora-16-x86_64-DVD.iso How reproducible: It is not always reproduced. It was caused only once during the installation on a new PC. A minimal installation was finished and then booted again the computer in order to repeat the installation and the problem occurred. Steps to Reproduce: 1. Boot F16 64bit DVD 2. Perform a minimal installation 3. 206 packages are installed 4. Reboot the PC when the installation is over 5. Boot F16 64bit DVD again Actual results: The kernel exception is caused during booting and installer hangs. Expected results: The installer should have continued in the GUI installation environment Additional info: I've turned off the PC and booted the DVD again. No problem was observed and the installation was completed successfully. After booting again with the DVD the problem hasn't occurred.
The actual kernel exception could help. Maybe it was just a temporary hardware problem? Without any more information we can't find out what might went wrong, so we're unable to fix this.
Hello Martin, I apologise for the inconvenience. You are absolutely right. Fortunately, I have saved /tmp logs in a USB stick. I've seen that /tmp/syslog has included the error message. I don't have the USB stick with me right now. I will upload the obtained logs as soon as possible.
Created attachment 533147 [details] System log of /tmp/syslog
Created attachment 533148 [details] Anaconda log of /tmp/anaconda.log
Please, find attached the /tmp promised logs of syslog and anaconda.log. The log file program.log is empty. There is also a file called 99anaconda-copy-ks.sh in the same directory. Please, advise if you would also like to view that file in case it is of any importance.
Kernel panic is way towards the bottom of the syslog referenced in comment #3. Enjoy.
20:17:36,018 ALERT kernel:[ 28.130746] BUG: unable to handle kernel NULL pointer dereference at (null) 20:17:36,018 ALERT kernel:[ 28.130767] IP: [<ffffffffa002ac0f>] rtl8169_open+0x34e/0x684 [r8169] 20:17:36,018 WARNING kernel:[ 28.130782] PGD 1f9f91067 PUD 210bad067 PMD 0 20:17:36,018 EMERG kernel:[ 28.130794] Oops: 0000 [#1] SMP 20:17:36,018 WARNING kernel:[ 28.130801] CPU 1 20:17:36,018 WARNING kernel:[ 28.130804] Modules linked in: iscsi_ibft iscsi_boot_sysfs pcspkr edd iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi cramfs nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core r8169 mii video mxm_wmi wmi squashfs 20:17:36,018 WARNING kernel:[ 28.130847] 20:17:36,018 WARNING kernel:[ 28.130851] Pid: 850, comm: NetworkManager Not tainted 3.1.0-7.fc16.x86_64 #1 Gigabyte Technology Co., Ltd. Z68A-D3H-B3/Z68A-D3H-B3 20:17:36,018 WARNING kernel:[ 28.130867] RIP: 0010:[<ffffffffa002ac0f>] [<ffffffffa002ac0f>] rtl8169_open+0x34e/0x684 [r8169] 20:17:36,018 WARNING kernel:[ 28.130881] RSP: 0018:ffff8801fb7cb7a8 EFLAGS: 00010202 20:17:36,018 WARNING kernel:[ 28.130887] RAX: 0000000000000000 RBX: ffff88020fc6a000 RCX: 000000000000262b 20:17:36,018 WARNING kernel:[ 28.130894] RDX: 0000000000000af4 RSI: 0000000000000000 RDI: ffff88020fc6a000 20:17:36,018 WARNING kernel:[ 28.130900] RBP: ffff8801fb7cb818 R08: ffffea000820f1c0 R09: 0000000000543ad0 20:17:36,018 WARNING kernel:[ 28.130905] R10: 0000000000000000 R11: 0000000000012f80 R12: ffff88020fc6a740 20:17:36,018 WARNING kernel:[ 28.130910] R13: ffff880210a08280 R14: ffff88020676d9c0 R15: ffffffffa002c0e5 20:17:36,018 WARNING kernel:[ 28.130914] FS: 00007f629e776800(0000) GS:ffff88021f440000(0000) knlGS:0000000000000000 20:17:36,018 WARNING kernel:[ 28.130919] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 20:17:36,018 WARNING kernel:[ 28.130923] CR2: 0000000000000000 CR3: 000000020fe0e000 CR4: 00000000000406e0 20:17:36,018 WARNING kernel:[ 28.130928] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 20:17:36,018 WARNING kernel:[ 28.130932] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 20:17:36,018 WARNING kernel:[ 28.130938] Process NetworkManager (pid: 850, threadinfo ffff8801fb7ca000, task ffff880207671730) 20:17:36,018 EMERG kernel:[ 28.130946] Stack: 20:17:36,018 WARNING kernel:[ 28.130951] ffff8801fb7cb7e8 00000000dc61a000 ffff880211bef000 ffff88007f85e000 20:17:36,018 WARNING kernel:[ 28.130972] ffffc90005cd4000 0000000000000ff0 ffff880211bef090 ffff880211bef090 20:17:36,018 WARNING kernel:[ 28.130982] ffff8801fb7cb7f8 ffff88020fc6a000 ffffffffa002ca40 0000000000001000 20:17:36,018 EMERG kernel:[ 28.130991] Call Trace: 20:17:36,018 WARNING kernel:[ 28.130998] [<ffffffff813d995c>] __dev_open+0x91/0xbf 20:17:36,018 WARNING kernel:[ 28.131002] [<ffffffff813d9b90>] __dev_change_flags+0xab/0x12f 20:17:36,018 WARNING kernel:[ 28.131007] [<ffffffff813d9c8d>] dev_change_flags+0x1e/0x54 20:17:36,018 WARNING kernel:[ 28.131012] [<ffffffff813e42ac>] do_setlink+0x2b0/0x779 20:17:36,018 WARNING kernel:[ 28.131017] [<ffffffff811ddb72>] ? avc_has_perm_flags+0x61/0x7a 20:17:36,018 WARNING kernel:[ 28.131022] [<ffffffff813e49db>] rtnl_setlink+0xcd/0xed 20:17:36,018 WARNING kernel:[ 28.131028] [<ffffffff811e3300>] ? selinux_netlink_recv.part.22+0x3a/0x9e 20:17:36,018 WARNING kernel:[ 28.131033] [<ffffffff813e4d37>] rtnetlink_rcv_msg+0x23b/0x251 20:17:36,018 WARNING kernel:[ 28.131037] [<ffffffff813e4afc>] ? __rtnl_unlock+0x17/0x17 20:17:36,018 WARNING kernel:[ 28.131042] [<ffffffff813f8ca7>] netlink_rcv_skb+0x42/0x8d 20:17:36,018 WARNING kernel:[ 28.131047] [<ffffffff813e3e88>] rtnetlink_rcv+0x26/0x2d 20:17:36,018 WARNING kernel:[ 28.131051] [<ffffffff813f87b1>] netlink_unicast+0xec/0x156 20:17:36,018 WARNING kernel:[ 28.131056] [<ffffffff813f8a9b>] netlink_sendmsg+0x280/0x2b8 20:17:36,018 WARNING kernel:[ 28.131061] [<ffffffff813c62f7>] sock_sendmsg+0xe6/0x109 20:17:36,018 WARNING kernel:[ 28.131067] [<ffffffff81450265>] ? scm_destroy+0x2b/0x4c 20:17:36,018 WARNING kernel:[ 28.131073] [<ffffffff81044023>] ? should_resched+0xe/0x2d 20:17:36,018 WARNING kernel:[ 28.131081] [<ffffffff814b4685>] ? _cond_resched+0xe/0x22 20:17:36,018 WARNING kernel:[ 28.131091] [<ffffffff81044023>] ? should_resched+0xe/0x2d 20:17:36,018 WARNING kernel:[ 28.131104] [<ffffffff813d0287>] ? copy_from_user+0x2f/0x31 20:17:36,018 WARNING kernel:[ 28.131112] [<ffffffff813d0672>] ? verify_iovec+0x52/0xa4 20:17:36,018 WARNING kernel:[ 28.131123] [<ffffffff813c65dc>] __sys_sendmsg+0x213/0x2ba 20:17:36,018 WARNING kernel:[ 28.131137] [<ffffffff813c636f>] ? fput_light+0x12/0x14 20:17:36,018 WARNING kernel:[ 28.131146] [<ffffffff813c81dd>] sys_sendmsg+0x42/0x60 20:17:36,018 WARNING kernel:[ 28.131156] [<ffffffff814bc482>] system_call_fastpath+0x16/0x1b 20:17:36,018 EMERG kernel:[ 28.131165] Code: c6 d2 2b e1 85 c0 41 89 c6 0f 88 e4 01 00 00 4d 8b 75 00 48 8b bb 50 07 00 00 49 8b 16 49 8b 76 08 48 83 fa 03 0f 86 a8 00 00 00 20:17:36,018 ALERT kernel:[ 28.131331] RIP [<ffffffffa002ac0f>] rtl8169_open+0x34e/0x684 [r8169] 20:17:36,018 WARNING kernel:[ 28.131345] RSP <ffff8801fb7cb7a8> 20:17:36,018 EMERG kernel:[ 28.131352] CR2: 0000000000000000 20:17:36,018 WARNING kernel:[ 28.131366] ---[ end trace a9088da3782901d6 ]---
Are you still seeing this with the 3.2.7 kernels? We can't really fix the F16 install media, so if you are it would be nice of you to test the F17 Alpha release. If you see it there we can try and fix it before F17 is released.
Hello Josh, The problem was probably temporary hardware issue as Martin in comment 1 said. The installation was successful on both PCs having exactly the same hardware afterwards. However, one of them is off after an update a couple of months ago. Both new installed and previous kernels cause exceptions. I can't boot that system and I'll need a rescue disc. Do you want me to try to collect the logs to check if it is related to present issue or to file a new bug?
(In reply to comment #9) > Hello Josh, > > The problem was probably temporary hardware issue as Martin in comment 1 said. > The installation was successful on both PCs having exactly the same hardware > afterwards. Great, thanks you. > However, one of them is off after an update a couple of months ago. Both new > installed and previous kernels cause exceptions. I can't boot that system and > I'll need a rescue disc. Do you want me to try to collect the logs to check if > it is related to present issue or to file a new bug? Let's use a new bug if you do that. Thanks.