Not booting after latest kernel upgrade x86_64

The new kernel 2.6.23.9 refuses to boot - spits out something about filesystems, says cd rom sata all (hooks) ndiswrapper, forcedeth blah blah, continously call traces happening but not booting. Not even in fallback mode.
I will try to boot thru live CD, but what should I alter? mkinitcpio.
This is on 64 bit only. My 686 desktop does not have this issue (atleast one of them). The other one I am using now. I don't want to upgrade this too and become incommunicado as the other desktop is in the office.
This is happening too often with Arch nowadays. It automatically upgraded the nvidia module and asked me to log out of X and remove the module manually. But I chose to reboot and this is what happened.

Actually it is screwing up at the loading modules stage
it says bug soft lockup cpu#0 stuck for 11s [rc.sysinit:1782]
modules linked in ndiswrapper forcedeth ext3 jbd mbcache sd_mod sr_mod cdrom ehci_hcd usbcore sata_nv ata_generic pata_amd libata
Pid : 1782 comm: rc.sysinit Tainted: P D: 2.6.23-ARCH#1
Then a lot of gibberish about RIP etc. This is continuously looping

Similar Messages

VMWARE not working after latest kernel upgrade [SOLVED]

I've done a kernel update and after rebooting VMWare was not working. That's "standard", I figured, because I have a new kernel.
So, I run the any_any patch (as usual) to re-configure the VM to the new kernel but this time no joy
Is there anyone else having the same problem?
The error seems to be here:
In file included from /tmp/vmware-config0/vmmon-only/common/hostKernel.h:56,
from /tmp/vmware-config0/vmmon-only/common/task.c:24:
include/asm/page.h: In function 'pte_t native_make_pte(long unsigned int)':
include/asm/page.h:112: error: expected primary-expression before ')' token
include/asm/page.h:112: error: expected ';' before '{' token
include/asm/page.h:112: error: expected primary-expression before '.' token
include/asm/page.h:112: error: expected `;' before '}' token
make[2]: *** [/tmp/vmware-config0/vmmon-only/common/task.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.
R.
Note: Running /usr/bin/vmware-config.pl is of no help either (same error).
Last edited by ralvez (2007-07-28 13:58:06)

stonecrest wrote:Yes, and the PKGBUILD works;
You'd rather say "I, myself, me, thinks it works".
Because it does not work for many people, including me.
The modules do build with kernel 2.6.22.X, but the network behaviour using bridged networking is extremely clumsy (used to work fine with 2.6.21.X), and shared folders are a pain in the butt- for example whenever I try to copy a file from the guest to a host shared folder, the guest OS (winXP) comes close to totally freezing, and I have to kill explorer to stop the transaction.
Do you call THAT "works"?
IMO the issues with kernel 2.6.22 won't be addressed before a new VMWare version is out... Until then, yeah... the old version/PKGBUILD works...
I'm close to ditching VMWare in favour of VirtualBox, but a couple of VMWare features (mainly related to low level hardware access) still prevent me from doing so.
Last edited by scarecrow (2007-07-29 13:31:51)

X240 will not boot after latest bios update

I bought windows 8 .1 machine from factory. Then I had local shop install 8.1 on larger ssd. I just performed latest bios update and now machine will not boot. I am sure this is uefi related but I am not knowledgable in that area. The boot parameter returned to me by the shop was "legacy only" and secure boot was disabled.
Solved!
Go to Solution.

StanFan wrote:
I bought windows 8 .1 machine from factory. Then I had local shop install 8.1 on larger ssd. I just performed latest bios update and now machine will not boot. I am sure this is uefi related but I am not knowledgable in that area. The boot parameter returned to me by the shop was "legacy only" and secure boot was disabled.
Since doing the BIOS update are the settings still as you noted above? You also didn't mention which SSD is now installed in the system.
Just as an aside, installing Windows 8.1 in legacy mode isn't exactly optimal. Were there any particular reasons for this? Just being curious.
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Late 2013 13 inch mackbook pro will not boot after latest upgrade

I got push notification to say there's an upgrade available. I upgraded from App Store and then after reboot, it waits in the rounding circle on the gray screen forever.
Safemode won't boot.
I reset PRAM
I reset SMC
But all above won't work.
I boot to the verbose mode, the last lines I see is
Executing fsck_hfs (version hfs-226.1.1).
USBMSC Identifier (non-unique): 000000000820 0x5ac 0x8406 0x820, 3
IOThunderboltSwitch<0xffffff8015d8e400>(0x0)::listennerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
IOThunderboltSwitch<0xffffff8015d8e400>(0x0)::listennerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
Then it stopped here forever......
Anyone knows what's going on? Please help!!!!!!

Well the people at Apple have no way of knowing if you have a marginal hard drive, or something installed that would interfere with the update from a third party. Problems can arise especially from tools such as system cache cleaners, anti-virus, firewall, and other software that operates in the background.
http://www.roaringapps.com/ should help you know what is compatible if you are running 10.7 or later.
In the future ignore push notifications, and turn them off via the Apple menu -> System preferences, Software Update, and the App Store preferences.

OS will not boot after Snow Leopard Upgrade

I have a MacPro (Intel). I just upgraded to Snow Leopard and everything appeared fine. However, after restarting my computer the OS will not load. A circle with a hash through it replaces the Apple logo and the apple's spinning wheel continues but all drive activity. I have tried to run the install again by forcing the computer to open the dvd drive then booting for the OS DVD but this has not worked. Has anyone experienced this and successfully resolved?

You have a five year old computer, so a failing hard drive at this point is not so strange. You have a couple of options you can try. Start with this one, but if it does not work you will have to erase the hard drive. I hope you have a backup of all your files.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.

Macbook pro will not boot after snow leopard upgrade

My GF has had a macbook pro since mid 2008. It's been running like a champ since I've known her for the past 3 years with no issues. It has/had OSX 10.5.8 installed. We tried to consolidate all our pictures from all our apple devices and realized she didn't have an icloud on the old 10.5.8 OSX. So I called apple and they told me to order and install the snow leopard OSX 10.6 first and then upgrade to lion etc after that, Well we got the disk yesterday popped it in to install and it's been a disaster.... the computer shutdown for what looked like a normal restart during the installation process and never booted back up. Attempts to manually reboot leave us locked on a grey apple logo screen with spinning gear indefinately whith the Snow Leopard disk installed during boot up. With the disk removed I get the flashing file folder with a question mark. I called apple support we tried all the PRAM and SMC resets and then decided that we should go to the Genius Bar once all those failed. After an hour and a half drive to the nearest genius bar we were told that the we suddenly had a hardware issue which just happened to coincide with the new OS installation.... I'm not buying it and am looking for some help. The macbook was running like a champ until we inserted a disk recommended by apple... Any takers?

You have a five year old computer, so a failing hard drive at this point is not so strange. You have a couple of options you can try. Start with this one, but if it does not work you will have to erase the hard drive. I hope you have a backup of all your files.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.

K210 Vista Home Premium not booting after latest Vista Update.

This is my pc specs:
Lenovo IdeaCentre K210 Intel Desktop PC - Intel Celeron Dual Core E1200 1.6GHz, 2GB DDR2, 320GB SATA II, DVDRW, Intel GMA3100, Webcam, Veriface, Flash Reader, Vista Home Premium SP1
After the latest windows update on February 12th, 2009. I woke up to my pc error beeping continously at the prompt before windows should boot up.
I have only had this lenovo pc for 5 months and it was working perfectly fine before this update. Onekey recovery is not working. I cannot get it to boot from a dvd or cd. I tried a recovery disc, did not work. I changed the pc to boot from the dvd and that did not work.
If I have it boot normally I get the continous error beeping.
The fact that I am writing this from my 6 year old HP computer makes me rethink my recent purchase of the Lenovo brand.

Phantera wrote:
After the latest windows update on February 12th, 2009. I woke up to my pc error beeping continously at the prompt before windows should boot up.
If you think a windows update caused the problem; are you able to say which update caused the problem?
You could also describe the beep error more precisely before it boots into windows. Or is windows not working at all in normal or safe mode?
Thanks
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Imac will not boot after trying to upgrade OS

A friend gave me an iMac 266MHz, one of the old tangerine models. He thought the firmware was upgraded but it had an old OS. I installed my OSX on it but when it was shut down it will not reboot. I am getting the same error message as above. I tried to boot from an 8.5 installer disk but it will not work.
Do I need the original startup disks for this machine? I do not have them. Is there any tricks I should know about trying to boot from the disks? I have used macs for a little while but I am not very familiar with this area {boot errors}

ok you needed to upgrade the firmware before installing os x and now you need a reinstallation cd for the mac as well now don't panic you need to find a mac os 9.2.2 restore cd i use the gray cd on my imac and it works great then you need to insert the cd press c on the keyboard as the computer starts up then once the os 9.2.2 cd shows up and boots you need to format the hard drive let the mac choose the type of format then install os 9.2.2 then upgrade the firmware then reinstall mac os x but a warning here from what i have read at the forums here i don't know if mac os x is compatible with that version of mac so you may need to look at the support section here to find out or the os x section
I hope this helps

Can not boot after the last upgrade [solved]

Hi all,
I upgraded my system this morning, but when loading I get the following error:
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 seconds
It says so for 3 times, then continues and ends with a kernel panic.
Any idea what might have gone wrong?
Best regards,
Jan

Hi again,
Thanks to good guys on IRC, my problem is a sort of solved. The solution was basically to go back to the old IDE subsystem on my Intel box and wait until the kernel and the respective modules get more stable before trying the transition again. More precisely, I did the following:
1) in /etc/mkinitcpio.conf removed pata, sata and scsi hooks and put back the ide hook (and then of course ran mkinitcpio again);
2) in /etc/rc.conf blacklisted ata_piix and ata_generic;
3) in /etc/fstab and /boot/grub/menu.lst changed the device names back from /dev/sda* to /dev/hda*.
I hope there will be some announcement on Arch website when it will make sense to try the new system again.
Thanks to everyone who helped to sort this trouble out,
Jan

OS X not booting after Vista SP1 upgrade

Ok, so I have this really bad problem with my OS X drive.
It's stuck at the grey screen with the loading thing continuously loading without starting OS X.
This all happened after I upgraded my Vista to Service Pack 1.
When going back to Vista a pop-up appeared (from Mac Drive 7).
http://img180.imageshack.us/img180/2734/capturehu8.jpg - The Pop-up.
Also had a pop-up that said the drive was corrupt.
I've tried using my Leopard install Disc to use Disk Utility, but it can't verify/check or repair my OS X drive.
Tried to reinstall OS X, but it asks me where I want to install it on, but doesn't show me any partition.
Now what can I do to fix it? (preferably without erasing anything)
Also, I've been thinking about completely removing OS X and replacing it with Vista...is it possible and could I still reinstall OS X later if I wanted to?

I've read bad reviews of MacDrive causing corruption.
I use Ultimate and its complete backup PC and file backups so covered there. And same for OS X with multiple SuperDuper clones along with a TimeMachine backup. Covers that side.
Vista SP1 needed to move files around a lot and some 5-7GB (depends on version etc) temp space during the process. So I ran CHKDSK and System File Checker before hand. And boot from Vista DVD and see if you can do anything if those two don't help.
One of the biggest problems is getting too low on disk space.
For OS X, I swear by Disk Warrior 4.1. I would install OS X on an external drive rather than use the DVD, make it your "emergency boot drive" and run DU and Disk Warrior from there.
Those that have backups are ready. And always backup your OS X volume before you apply updates and patches on it as well. You may never need to if you plan for and do some maintenance.
I'd dump MacDrive though. And for OS X, I feel safe / okay with NTFS from MacFUSE 3G.

System will not boot after trying to upgrade to yosamite

My wife tried to update her OS to yosamite on her MBP 2011. Now it wont boot at all. All she gets is the folder question mark screen. It won't boot in safe mode and won't do a recovery from internet. Please help !

Maybe try to use Yosemite (with an e). I don't think that there is an OS Yosamite that works on a mac. Probably you got the wrong OS.

[SOLVED] Kernel will not boot after update to 3.1.5

Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
Last edited by bolshevik (2011-12-16 14:31:19)

bolshevik wrote:
Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
If you foolishly interrupted the initramfs creation after a kernel upgrade and didn't regenerate it manually, you earned this.
You'll need to find a live CD so you can chroot to your install and rerun mkinitcpio.

Macbook Pro is Not Booting After RAM Upgrade

Hi,
I just upgraded the RAM in my MacBook Pro running Mountain Lion from 4gb to 8gb (Using the memory that the guy at Fry's recommended). It has been stuck on the Apple logo for about 20 minutes after the upgrade, even after I made sure that the RAM was seated properly. Is it normal for it to take this long to boot after a RAM upgrade?

I installed 8gb (2 X4gb) and it has a maximum of 8gb. I have determined that it was just bad RAM, so I will return it as soon as I can.
Thanks.

Not Booting after recent Security Patch/Java update

My wife has experienced what many have experienced with the recent update.
MacBook not booting after update (i.e. - "I have no name!")
I have tried everything posted on this topic since 2/13/09, but without any success. Does anyone have the fix for this yet?
Things I have tried:
* I can boot in safe mode (holding "Shift" while restarting)
* I cannot boot from an install disk(s) (holding C while restarting) - I have both a black one from purchase, and two gray ones with purchase from MiniMac
* Booting with verbose - gets stuck at same place as everyone else
Operating in safe mode:
* I can run DU and "repair" drive
* I can see and access the CD/DVD
* I cannot see drive in target drive mode (doesn't ever connect the 2 systems)
* I downloaded the update files from apple and reinstalled them individually (via USB ext Drive) with a reboot in between
* I attempted to update & archive, but I cannot run install CD from any systems disks (see above)
Has anyone figured out how to fix this yet?

Same problem than the other guy who is not mentioning the update in the title.
Powerbook 1.67.
System log said "No user defined computer name" and "using blah blah name" or so.
Mac Os X report (for apple) says:
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003900FF1C PC=0x00000000008FC020
Latest crash info for cpu 0:
Exception state (sv=0x4299D280)
PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0xFF9BA29B
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x8d8000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
Proceeding back via exception chain:
Exception state (sv=0x4299D280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x43D0D000)
PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x4299D280)
PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0xFF9BA29B
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x8d8000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
Exception state (sv=0x43D0D000)
PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

VMware wont start after latest kernel update!

Okay when i went to reboot it went to boot into arch but wile it was loading the vmware modules it would stay stuck at loading vm communication interface socket family and would just stay there the only way i could even boot into arch was to edit my grub so i could login and at least comment out vmware i tried to reapply the vmware patch fix that was on the wiki and had no luck also tried reinstalling + reapplying patch after words and still no luck I'm hoping this is happening to someone else as well and not just me (mean i know lol) I also tried virtualbox but seems it has it's own mess of problems as well after latest kernel update.

I have tried rebuilding the the kernel image and even tried reinstalling grub with no luck. After not having a usable system for several days I ended up just having to reinstall and maybe found out more about the problem. Using the net install image and a 64 bit install this time making a EXT2 boot and a root partition of JFS right after install I get a panic during boot about how the system can't find a valid filesystem on what would be root partition. Even when passing the "rootfstype=jfs" to the kernel line in grub it still errors out telling me that it is "Bailing out, your on your own. Good luck!" (pretty funny error messages if you are not ripping your hair out). After that I redid the install this time making a EXT4 root partition and everything is working.
It seems to me that this all points to a problem with JFS on 64 bit systems, my other systems are all 32 bit and usign JFS root just fine... can anyone else confirm this?
Last edited by vendion (2011-01-12 13:39:56)

Not booting after latest kernel upgrade x86_64

Similar Messages

Maybe you are looking for