| Summary: | kernel does not activate md1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udo <udovdh> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-17 06:37:24 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
(In reply to comment #0) > Additional info: > at the dracut prompt I can assemble /dev/md1 by hand > > also: > > kernel.org kernels compiled since upgrading to F16 have failed boots: monitor > goes into powersave as soon as dracut starts; no network after a while, no > /var/log/messages > own 3.0.3 rt kernel does boot fine though, so raid and lvm are ok. So kernel.org kernels you've built also fail in the same manner? If so, this might be some kind of issue with dracut, udev, or device-mapper. Which upstream kernels have you tried building? I cannot actually verify what happens with my own kernels due to the monitor going into powersave and no network etc. If you have a trick to turn the monitor on from powersave I could give that a try. I tried 3.0.9 and 3.1.4 kernel.org kernels. Both without rt patch and 3.0.9 with rt patch. I diffed the 3.0.9 rt config with the working 3.0.3. rt config and there's no real differences there. kernel 2.6.41 from F15 also does not activate /dev/md1. changing the name of /usr/sbin/vbetool does not change the pwoersave behaviour of the kernel.org kernels built under F16. How can I check what goes on when the screen goes into powersave? modprobe fbcon was a step towards a solution |
Created attachment 540252 [details] screenshot of said situation Description of problem: kernel does not activate /dev/md1, does not see pv and thus no lv's to boot the system Version-Release number of selected component (if applicable): kernel-3.1.2-1.fc16.x86_64 How reproducible: upgrade to f16, install kernel, boot kernel Steps to Reproduce: 1. 2. 3. Actual results: dracut prompt Expected results: system running Additional info: at the dracut prompt I can assemble /dev/md1 by hand also: kernel.org kernels compiled since upgrading to F16 have failed boots: monitor goes into powersave as soon as dracut starts; no network after a while, no /var/log/messages own 3.0.3 rt kernel does boot fine though, so raid and lvm are ok.