I am using gentoo-sources 3.10.7 kernel My system is x86_64 Intel(R) Core(TM) i5-4200M During booting, I encounter a kernel panic : WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule (Full log is in attachment) I've searched for this bug, and found this bug exposed in early upstream kenrel, and it _seems_(?) got fixed. I don't know whether this is patched for gentoo-sources, so report a bug here.
Created attachment 359242 [details] gentoo sources 3.10.7 kernel panic log This is a hand copy of the panic screen snapshot, so some info is not correct, for example the time-stamp ;)
mount_block_root means it cannot mount the root fs; so, could you please try to follow https://wiki.gentoo.org/wiki/Knowledge_Base:Unable_to_mount_root_fs and see if that fixes it?
(In reply to Tom Wijsman (TomWij) from comment #2) > mount_block_root means it cannot mount the root fs; so, could you please try > to follow > https://wiki.gentoo.org/wiki/Knowledge_Base:Unable_to_mount_root_fs and see > if that fixes it? Hi, I've checked this wiki, and make sure I built the controller driver and filesystem support in kernel. But this problem remains.
It still panics there so there must be something going wrong with that; can we please see: 1) Your boot loader configuration file. (eg. /etc/grub/grub.cfg) 2) The 3.10.7 .config (eg. /usr/src/linux-3.10.7-gentoo/.config) 3) The /etc/fstab file and the command output of `ls -la /boot` If you have a working install, please provide `mount` and `lspci` output too. Thank you in advance.
(In reply to Tom Wijsman (TomWij) from comment #4) > It still panics there so there must be something going wrong with that; can > we please see: > > 1) Your boot loader configuration file. (eg. /etc/grub/grub.cfg) > 2) The 3.10.7 .config (eg. /usr/src/linux-3.10.7-gentoo/.config) > 3) The /etc/fstab file and the command output of `ls -la /boot` > > If you have a working install, please provide `mount` and `lspci` output too. > > Thank you in advance. Hi. Sorry for late reply... 1) grub.cfg http://www.pastebin.ca/2460053 2) .config http://www.pastebin.ca/2460054 3) /etc/fstab /dev/sda7 /boot ext2 defaults,noatime 1 2 /dev/sda8 / ext4 noatime 0 1 /dev/sda9 none swap sw 0 0 /dev/sda10 /home ext4 defaults,noatime 0 0 /dev/cdrom /mnt/cdrom auto noauto,ro 0 0 /dev/fd0 /mnt/floppy auto noauto 0 0 /dev/sda2 /boot/efi vfat defaults 0 2 4) ls -la /boot total 10249 drwxr-xr-x 5 root root 1024 Sep 30 22:50 . drwxr-xr-x 21 root root 4096 Sep 30 05:09 .. drwxr-xr-x 4 root root 512 Jan 1 1970 efi drwxr-xr-x 6 root root 1024 Sep 20 07:02 grub -rw-r--r-- 1 root root 0 Aug 22 09:31 .keep -rw-r--r-- 1 root root 5249920 Sep 30 04:55 kernel-3.10.7-gentoo-new -rw-r--r-- 1 root root 5181872 Sep 30 23:34 kernel-3.10.7-gentoo-new-no-debug-options drwx------ 2 root root 12288 Sep 19 22:28 lost+found
All the grub entries contain ro at the end, can you try removing that? (ro means readonly, you probably do not intend that) Other than that I have no idea, everything seems to be in order; also, if you look at http://forums.gentoo.org/viewtopic-p-7406306.html which has the same laptop, seems you have the same .config settings so that should suffice. Given the date of that, I wonder if that is perhaps your forum thread.
(In reply to Tom Wijsman (TomWij) from comment #6) > All the grub entries contain ro at the end, can you try removing that? > > (ro means readonly, you probably do not intend that) > > Other than that I have no idea, everything seems to be in order; also, if > you look at http://forums.gentoo.org/viewtopic-p-7406306.html which has the > same laptop, seems you have the same .config settings so that should suffice. > > Given the date of that, I wonder if that is perhaps your forum thread. Ah. That's indeed myself ;) But that is another panic. BTW, removing ro is of no help. I will do more try. Thanks!!!
(In reply to larmbr from comment #7) > But that is another panic. Take a closer look, they are exactly the same; confirmed by running a diff.
Okay, given the lsmod output; here are some more but they might be false positive: 1) The CONFIG_MD_RAID* options are not selected, which can act as fallback. 2) The CONFIG_MD_MULTIPATH option falls under this as well. 3) Though unrelated, please note that support for other things is also missing; for example, CONFIG_IDEAPAD_LAPTOP. You might want to run line by line through lsmod to proceed and ensure you have everything you need. Anyhow, you said in the forum thread that it was resolved; why do you still get the exact same panic then? Did you accidentally paste the wrong one here?
(In reply to Tom Wijsman (TomWij) from comment #9) > Okay, given the lsmod output; here are some more but they might be false > positive: > > 1) The CONFIG_MD_RAID* options are not selected, which can act as fallback. > 2) The CONFIG_MD_MULTIPATH option falls under this as well. > 3) Though unrelated, please note that support for other things is also > missing; for example, CONFIG_IDEAPAD_LAPTOP. You might want to run line by > line through lsmod to proceed and ensure you have everything you need. > Ok > Anyhow, you said in the forum thread that it was resolved; why do you still > get the exact same panic then? Did you accidentally paste the wrong one here? Actually, for the original .config I posted for this bug report and the one posted on forum , they are the same. At first, I thought I have not built in correct driver support for my SATA. But after I solved the SATA driver problem, This panic problem remains. But it changes to something like: VFS: cannot open root device "(null)" or unknown-block(0,0): error -6 Please use boot option "root=" ..... So I opened another thread for this panic on forum: https://forums.gentoo.org/viewtopic-p-7406772.html#7406772 NeddySeagoon has given me a lot of hints and help. And after we did most checks and found everything is sane, as you can see. But after following his latest suggestion, I still encounted this panic. And this time, the panic turn back to arch/x86/kernel/smp.c:123 native_smp_send_reschedule+0x52/0x60()
Can you test with the latest 3.11.X kernel and lets us know if you still get a oops. Can you attach or paste the full oops if you do get it.
