From: Steven Haigh <netwiz@crc.id.au>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_SYSFS_DEPRECATED & CONFIG_SYSFS_DEPRECATED_V2 appear to not work
Date: Thu, 18 Oct 2012 17:29:38 +1100 [thread overview]
Message-ID: <507FA1D2.3070407@crc.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Hi all,
Firstly, please CC me in replies as I am not subscribed to the list.
I'm trying to build kernel 3.5.4 and 3.6.2 to work with EL5. Each time I
try to boot this kernel, I get a panic stating it can't find /
The same kernel config works correctly in EL6 (without the
CONFIG_SYSFS_DEPRECATED and CONFIG_SYSFS_DEPRECATED_V2 options set)
The documentation I have found states that for compatibility with EL5, I
should enable the CONFIG_SYSFS_DEPRECATED and
CONFIG_SYSFS_DEPRECATED_V2 options in General Setup.
I have done this as shown:
# grep SYSFS /boot/config-3.5.4-4.el5xen.x86_64
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_ISCSI_BOOT_SYSFS=m
# CONFIG_GPIO_SYSFS is not set
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_RTC_INTF_SYSFS=y
# CONFIG_DMI_SYSFS is not set
CONFIG_SYSFS=y
The system however does not boot. I have also tried passing
"sysfs.deprecated=1" on the kernel line in grub with no success.
I cannot seem to find anything further that could cause this issue other
than a fault in these kernel options.
I have added a few attachments (kernel config, screenshot of panic)
which I won't attach to the list:
https://bugzilla.kernel.org/show_bug.cgi?id=48991
Can anyone much wiser than me assist here? How can I help debug this
further?
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4965 bytes --]
reply other threads:[~2012-10-18 6:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507FA1D2.3070407@crc.id.au \
--to=netwiz@crc.id.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox