Created attachment 375876 [details] .config file for 3.14.1 kernel Hi. I upgraded to 3.14.1 from 3.13.5, which worked (and still works) perfectly. However, when I try to start up 3.14.1 it freezes at kdm, where the stopwatch (at kdm) just stays on. /boot is formatted with ext2, /usr is formatted with ext4, and /var, /var/tmp, /home, /opt, /tmp, /usr/portage, and /usr/portage/distfiles are formatted with btrfs. In experimenting with different kernel settings to try to solve this, I forgot to activate in the kernel btrfs. When I rebooted, the computer booted into kdm! But of course I couldn't get into my home directory, but I could boot into X as root. When I activated btrfs, whether as a module or building it into the kernel, the freeze returned. As I said, 3.13.5 (and 3.13.3) load and operate without any problems.
Created attachment 375878 [details] emerge --info output
It would probably be useful to see your Xorg.0.log from when /something is a btrfs mount so that we can figure out what /something is.
Created attachment 375986 [details] Xorg.0.log This is the Xorg log after I've booted to the frozen kdm screen, went to a terminal, and copied the Xorg.0.log as root.
(In reply to Jeroen Roovers from comment #2) > It would probably be useful to see your Xorg.0.log from when /something is a > btrfs mount so that we can figure out what /something is. The root is a mdraid device formatted with ext4.
For me btrfs + kdm is working here great. Cant find anything in Xorg log that indicates an error. Are you sure this is kdm related? Did you tried to run other login manager?
(In reply to Johannes Huber from comment #5) > For me btrfs + kdm is working here great. > > Cant find anything in Xorg log that indicates an error. Are you sure this is > kdm related? Did you tried to run other login manager? Hi Johannes. What kernel are you using? I have no problem with any kernel from 3.13 and earlier. But no luck with 3.14.0 or 3.14.1 or 3.14.2. And kdm itself has nothing to do with it. If I exit X and try to start it from TTY1 with "startx", still no luck.
(In reply to Jeroen Roovers from comment #2) > It would probably be useful to see your Xorg.0.log from when /something is a > btrfs mount so that we can figure out what /something is. Hi Jeroen. kdm has nothing to do with the problem. No matter how I try to get into X (using xdm or exiting X altogether and trying to start from a command line with "startx"), I cannot do it. If I use any kernel from 3.13 and earlier, I have no problem. I have changed the Summary line back to the original, because kdm is irrelevant to the problem. It is some combo of the three. The real test would be to change the btrfs partitions (which are specified in my first post) to another filesystem, but oh, what a headache that would be.
Maybe kernel team knows whats going on.
When you do find a _bug_ to report, feel free. In the mean time, there is nothing to see here. Try our forums, IRC channels and/or mailing lists for support.
(In reply to Jeroen Roovers from comment #9) > When you do find a _bug_ to report, feel free. In the mean time, there is > nothing to see here. Try our forums, IRC channels and/or mailing lists for > support. How does one know ahead of time if something is a bug or not? Are you suggesting that there is something inherently wrong with kernel 3.14 and therefore not a Gentoo bug?
(In reply to Paul Monsour from comment #10) > (In reply to Jeroen Roovers from comment #9) > > When you do find a _bug_ to report, feel free. In the mean time, there is > > nothing to see here. Try our forums, IRC channels and/or mailing lists for > > support. > > How does one know ahead of time if something is a bug or not? Are you > suggesting that there is something inherently wrong with kernel 3.14 and > therefore not a Gentoo bug? When it is a bug, it manifests itself as a bug; until then, support can help.
