https://bugzilla.novell.com/show_bug.cgi?id=843041 https://bugzilla.novell.com/show_bug.cgi?id=843041#c0 Summary: kernel-ec2-3.0.93-0.8.2 has CONFIG_STRICT_DEVMEM=y Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: glasgow@beer.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36 Reading through some previous bug reports, CONFIG_STRICT_DEVMEM was disabled in previous kernel after it was enabled by mistake. I cannot run some proprietary software I need with this option enabled, so I'm wondering if enabling this option was a mistake, and if so, can we please disable it again? Thanks Reproducible: Always Steps to Reproduce: $ grep -i devmem /boot/config-3.0.93-0.8-ec2 Actual Results: CONFIG_XEN_DEVMEM=y CONFIG_STRICT_DEVMEM=y Expected Results: CONFIG_XEN_DEVMEM=y # CONFIG_STRICT_DEVMEM in not set I'm dead in the water for now, trying to build a custom kernel to work around it. If this could be fixed upstream, so much the better. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.