Summary: | Recompiled kernel crash on KMS loading | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | muziofg | ||||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||
Status: | RESOLVED NOTABUG | QA Contact: | |||||||
Severity: | critical | ||||||||
Priority: | medium | ||||||||
Version: | unspecified | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
muziofg
2011-06-25 11:31:47 UTC
This might be a duplicate of bug 38583. Relevant patches: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a377e187df725fe7e62d2cec59ec290c5a605d93 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ee4017f4ac8163737793cc64df535cd246792887 If they don't help, can you bisect? I tried to apply the patch and it did not work, the system freezes with a kernel panic. It seems correct because if a precompiled kernel (hence not patched) works and my custom kernel works (sometimes) could not be this the problem. What do you mean with "bisect" ? Problem solved My config have many years, each time "make menuconfig" add the new options but in the original configuration I have exagerated with the hardening :) I have analysed, compared and merged the config of a custom kernel on my old laptop (wich is full amd) and this .config. Now the kernel boot and KMS is loaded without problem I have attached a new archive with old and new confing files (configOldAndNewForDiff.tar.gz). The answer is in the diff If you consider interesting the detailed analisys of the problem I can try to test more combination between this two configuration to find what is requested by KMS for work without problem Created attachment 48463 [details]
old and new config file of my custom kernel
Although the 'crash' configuration is not very sensible, any valid configuration should not result in a crash so long as the hardware requirements are met. Comparing the 'ok' and 'crash' configurations, I think the important difference is probably: -CONFIG_VIDEO_OUTPUT_CONTROL=y +# CONFIG_VIDEO_OUTPUT_CONTROL is not set |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.