I am having a problem with kernel 3.11, using an encrypted LVM.
I upgraded to 3.11.0-26 several days ago, but did not reboot at that time. When I rebooted today, I could not unlock the encrypted LVM. I was prompted for the key. It looked as if the keyboard was not being read. The key that I entered was never accepted, and booting stalled at that point. It is a USB keyboard, if that is relevant.
I was able to boot with the last 3.10 kernel. There, I tried rebuilding the “initrd” for the 3.11 kernel. That did not help.
I went into Yast, and installed the 3.11.0-27 kernel. Another boot attempt, and that also stalled on the prompt for the key.
I have a second computer with tumbleweed, where I did not have this problem.
Incidentally, I am also seeing the “python-sip” problem mentioned in other threads. I am not doing a “zypper dup” until I can proceed without that problem.
Interesting. I had a WiFi issue for the network type of ath9k due to a new driver not being loaded with kernel 3.10 which is alleged to be fixed in kernel 3.11, now up to 3.11.2 I see. There seems to be a lot of such stuff going on in the background of the kernel development. In the case of the WIFI driver, it was moved out of the kernel-firmware file and is now loaded as a select-able kernel configuration option. In kernel 3.10, its not loaded by default and in kernel 3.11 it will be there by default, as I understand it.