[Bug 558740] New: kernel parameter module=ide-generic not passed to installed kernel
http://bugzilla.novell.com/show_bug.cgi?id=558740 http://bugzilla.novell.com/show_bug.cgi?id=558740#c0 Summary: kernel parameter module=ide-generic not passed to installed kernel Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: amb@jb.man.ac.uk QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6; InfoPath.1; .NET CLR 1.1.4322) I have to supply the kernel parameter "insmod=ide-generic" to the install disk to get it to see my hard drives. However the installed system fails to boot "waiting for /dev/disk/by-id/..." because the required module ide-generic is not passed to the installed kernel. Reproducible: Always Steps to Reproduce: 1. Install 11.1 fails to recognise hard drives 2. Re-install 11.1 using the kernel parameter "insmod=ide-generic". 3. Initial installation successful. However initial reboot fails "waiting for /dev/disk/by-id/..." Actual Results: Booting installed system fails "waiting for /dev/disk/by-id/..." Expected Results: kernel parameters to the install should be passed to installed kernel. The kernel parameter "insmod ide-generic" should be passed to the installed system. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c
shuang qiu
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c
shuang qiu
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c3
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c4
Angela Bayley
Does the module appear in /etc/sysconfig/kernel? If so, it's a mkinitrd bug, otherwise it's the installer not adding it to the sysconfig entry.
No, the module does not appear in /etc/sysconfig/kernel. I had to load the rescue system and edit /etc/sysconfig/kernel to add the module to the modules list on the INITRD_MODULES line. Then proceed as described in the man page for mkinitrd, RECOVERY section. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c5
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c6
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c7
--- Comment #7 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c8
Angela Bayley
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c9
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c10
--- Comment #10 from Angela Bayley
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c11
--- Comment #11 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c12
--- Comment #12 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c13
--- Comment #13 from Angela Bayley
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c14
--- Comment #14 from Angela Bayley
Thanks!
That looks really unusual. Why do you need ide-generic? Are the normal modules not working?
Anyway, please run 'getsysinfo' (as root) and attach the tar file this creates. As the command will probably hang, better do it this way:
# umount /sys/kernel/debug # getsysinfo # unt -t debugfs debugfs /sys/kernel/debug
If I don't supply the kernel parameter 'insmod=ide-generic' to the install it reports "No hard drives found" (or words to that effect). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c15
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c16
Jeff Mahoney
http://bugzilla.novell.com/show_bug.cgi?id=558740
http://bugzilla.novell.com/show_bug.cgi?id=558740#c17
--- Comment #17 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c18
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c19
--- Comment #19 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c20
--- Comment #20 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c21
--- Comment #21 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c22
--- Comment #22 from Jiri Slaby
So far we have not been able to boot 11.3 installation media.
What exactly does it mean? (IDE is disabled as of 11.3, so there is no way to use ide-generic.)
Also I don't understand how to provide the output of dmesg during an unsuccessful boot as this requires a command prompt? And how would I capture the output?
Doesn't initrd jump to one if it fails to find disks? You can then insmod ide-generic and go on with booting. I see in the boot.msg, that ata_piix is trying to acquire the device, but it fails due to ide-generic holding the resources... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c23
--- Comment #23 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c24
--- Comment #24 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c25
--- Comment #25 from Jiri Slaby
OK, our system does boot 11.3 from the installation media OK, but it cannot find any hard drives ("No Hard Drives found").
I take it that this is because IDE has been removed from 11.3?
Yes, exactly.
How should we proceed?
Boot the media, switch to console 2 (C-A-F2), setup network (like dhcpcd eth0) and # mount /dev/sr0 /mnt # cd / # rpm2cpio /mnt/suse/i586/netcat-1-10...|cpio -i --mak # netcat IP 60000 < /var/log/boot.msg Prior that, run on another machine with IP: netcat -lp 60000 >dmesg And attach the captured dmesg here then. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c26
--- Comment #26 from Jiri Slaby
# netcat IP 60000 < /var/log/boot.msg
(Or transport /var/log/boot.msg here however you want... E.g. by USB flash disk.) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c27
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c28
Jiri Slaby
Created an attachment (id=399607) --> (http://bugzilla.novell.com/attachment.cgi?id=399607) [details] Output from dmesg following failed install 11.3 ("No Hard Drives found")
dmesg attached as requested
Ok, thanks, it's clearly due to bogus BIOS: ata_piix 0000:00:1f.1: version 2.13 ata_piix 0000:00:1f.1: device not available (can't reserve [io 0x0000-0x0007]) The BAR 2 of the device is IO: 0x0000000000000000 0x0000000000000007 0x0000000000000110 which is quite bogus. According to ICH specs, this range is reserved for DMA controller. I guess it should rather have been 0x170-0x177, because all 0x1f0-0x1f7, 0x376-0x376 and 0x3f6-0x3f6 are listed otherwise, but who knows... Let's see what happens if we fix the resource start to be 0x170 in a quirk. Could you provide dmidecode and lspci -nnvvxxxs :1f.1 outputs from whatever kernel? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c29
--- Comment #29 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c30
Angela Bayley
From the lspci, this is not a BIOS bug. I investigated further and it's caused by an ugly quirk code in pci_setup_device. Whenever a device is of IDE class,
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c31
--- Comment #31 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c32
Jiri Slaby
Let's remove the quirk from pci_setup_device, build the kernel[1] and find somebody who can build installation ISOs.
Other way around. Could you install the 11.3 kernel from your 11.2 installation: http://download.opensuse.org/repositories/home:/jirislaby:/kern-11.3-ide/ope... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c33
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c34
Jiri Slaby
We are at 11.1
Ah, sorry, 11.1 repo will appear at http://download.opensuse.org/repositories/home:/jirislaby:/kern-11.3-ide/ope... after it gets build. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c35
--- Comment #35 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c36
--- Comment #36 from Jiri Slaby
I'm not sure what I should do now? Is it an rpm?
Yes, just install one that matches your architecture and flavor, install it with rpm -ivh and reboot to it... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c37
--- Comment #37 from Angela Bayley
(In reply to comment #35)
I'm not sure what I should do now? Is it an rpm?
Yes, just install one that matches your architecture and flavor, install it with rpm -ivh and reboot to it...
The error message is: 'Could not find /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2.' when we reboot This is exactly what happened under 11.1 (the original bug report see description) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c38
--- Comment #38 from Jiri Slaby
This is exactly what happened under 11.1 (the original bug report see description)
Could you transfer somehow /var/log/boot.msg here? You can create a monster initrd to have network (to have network) and USB modules (usb disk) at that stage: mkinitrd -k /boot/vmlinuz-<version> -i initrd-<version> -A -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c39
--- Comment #39 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c40
--- Comment #40 from Angela Bayley
If we continue the reboot using a rescue system as described in comment #4 can we recover boot.msg that way?
Please disregard this comment as it won't work under 11.2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c41
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c42
Jiri Slaby
Created an attachment (id=400780) --> (http://bugzilla.novell.com/attachment.cgi?id=400780) [details] /var/log/boot.msg from failed 11.3 reboot
No, this one is from 11.1: 2.6.27.7-9-pae. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c43
--- Comment #43 from Angela Bayley
(In reply to comment #41)
Created an attachment (id=400780) --> (http://bugzilla.novell.com/attachment.cgi?id=400780) [details] [details] /var/log/boot.msg from failed 11.3 reboot
No, this one is from 11.1: 2.6.27.7-9-pae.
Sorry should have realised. There isn't one available for 11.3 since it couldn't access the hard drives? How would I capture the screen on failed reboot (terminates in 'Could not find /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2.' In 11.1 we overcame this problem with insmod=ide-generic -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c44
--- Comment #44 from Angela Bayley
(In reply to comment #42)
(In reply to comment #41)
Created an attachment (id=400780) --> (http://bugzilla.novell.com/attachment.cgi?id=400780) [details] [details] [details] /var/log/boot.msg from failed 11.3 reboot
No, this one is from 11.1: 2.6.27.7-9-pae.
Please disregard comment #43. We'll do the monster initrd and use that to send you /var/log/boot.msg -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c45
--- Comment #45 from Angela Bayley
Could you transfer somehow /var/log/boot.msg here? You can create a monster initrd to have network (to have network) and USB modules (usb disk) at that stage: mkinitrd -k /boot/vmlinuz-<version> -i initrd-<version> -A
OK I have rebooted kernel 2.6.34 with monster initrd Following the "waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2" it has now dropped into the $ prompt. dhcpcd eth0 hangs How should I proceed? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c46
--- Comment #46 from Jiri Slaby
Following the "waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2" it has now dropped into the $ prompt.
Great!
dhcpcd eth0 hangs
Hangs in what way? Can you kill it? What it writes with -d option? Isn't eth1 the correct device to try to connect with? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c47
--- Comment #47 from Angela Bayley
(In reply to comment #45)
Following the "waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2" it has now dropped into the $ prompt.
Great!
dhcpcd eth0 hangs
Hangs in what way? Can you kill it? What it writes with -d option? Isn't eth1 the correct device to try to connect with?
eth0 is correct. I've connected a usb stick which the system recognises. What command(s) should I use to transfer /var/log/boot.msg to the usb stick? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c48
--- Comment #48 from Angela Bayley
(In reply to comment #45)
Following the "waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2" it has now dropped into the $ prompt.
Great!
dhcpcd eth0 hangs
Hangs in what way? Can you kill it? What it writes with -d option? Isn't eth1 the correct device to try to connect with?
dhcpcd gets an IP address from the server then fails: Looking up hostname via DNS Failed: Name or Service not known dhcpcd: forking to background I haven't managed to write /var/log/boot.msg to the USB stick under the ramdisk. Under 11.1 kernel 2.6.27 the stick appears as /dev/sda1 and can be mounted. However this is not possible under the ramdisk. Any ideas? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c49
--- Comment #49 from Angela Bayley
(In reply to comment #45)
Following the "waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2" it has now dropped into the $ prompt.
Great!
dhcpcd eth0 hangs
Hangs in what way? Can you kill it? What it writes with -d option? Isn't eth1 the correct device to try to connect with?
I can ping from the ramdisk system, but there is no netcat. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c50
--- Comment #50 from Jiri Slaby
I can ping from the ramdisk system, but there is no netcat.
You would need to pack it to the initrd by hand. For the usb disk, you can add -m 'usb-storage nls_cp437 nls_iso8859-1 vfat' to mkinitrd cmdline to support usb disks (assuming it's with fat FS, otherwise you need to specify the proper FS and charset modules). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c51
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c52
Jiri Slaby
Created an attachment (id=401948) --> (http://bugzilla.novell.com/attachment.cgi?id=401948) [details] /var/log/boot.msg from failed reboot of kernel 2.6.34
Holy crap, init scripts in 11.1 seem not to put whole boot message into boot.msg. Could you do: cat /proc/kmsg >/my_log & (the ampersand is necessary) instead and transfer /my_log here? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c53
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c54
Jiri Slaby
Created an attachment (id=402011) --> (http://bugzilla.novell.com/attachment.cgi?id=402011) [details] /proc/kmsg from failed boot kernel 2.6.34
Ok, thanks, could you try the kernel from: http://labs.suse.cz/jslaby/bug-558740/ -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c55
Angela Bayley
Ok, thanks, could you try the kernel from: http://labs.suse.cz/jslaby/bug-558740/
The reboot hangs: 'Waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2.' as before -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c56
Jiri Slaby
The reboot hangs:
'Waiting for /dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2.'
That's weird. Could you create the monster initrd once again and extract /proc/kmsg? The config space in 00:1f.0 seems to be broken (doesn't correspond to the ICH4 specs) and the second kernel should fix that. Maybe the disks would be correctly found by pata_legacy which we don't build. BTW. don't you have an option in your BIOS to turn the disk controller into AHCI mode? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c57
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c58
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c59
--- Comment #59 from Angela Bayley
So if you boot with root=/dev/sda2, it should work out. Why the id is not ata-ST380215A_6QZ58NB4-part2 that I don't know. If you boot the kernel with root=/dev/sda2, what's in /dev/disk/by-id/?
The reboot drops straight into the $ shell prompt. The original kernel command line had resume=/dev/disk/by-id/ata-ST380215A_6QZ58NB4-part1 I added root=/dev/sda2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c60
--- Comment #60 from Angela Bayley
So if you boot with root=/dev/sda2, it should work out. Why the id is not ata-ST380215A_6QZ58NB4-part2 that I don't know. If you boot the kernel with root=/dev/sda2, what's in /dev/disk/by-id/?
It seems to see the disks this time but gives an error message when attempting to mount the root file system. It says cannot mount /dev/sda2, device or resource busy. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c61
--- Comment #61 from Angela Bayley
So if you boot with root=/dev/sda2, it should work out. Why the id is not ata-ST380215A_6QZ58NB4-part2 that I don't know. If you boot the kernel with root=/dev/sda2, what's in /dev/disk/by-id/?
/proc/kmsg: <5>[ 0.000000] Kernel command line: root=/dev/disk/by-id/ata-ST380215A_6QZ58NB4-part2 root=/dev/sda2 resume=/dev/disk/by-id/ata-ST380215A_6QZ58NB4-part1 splash=silent vga=0x314 ie two root= on kernel command line -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c62
--- Comment #62 from Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c63
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c64
Jiri Slaby
Created an attachment (id=404295) --> (http://bugzilla.novell.com/attachment.cgi?id=404295) [details] /proc/kmsg from failed reboot of 2.6.34.7-0.1-default
Booting with root=/dev/sda2 resume=/dev/sda1 drops into the $ shell prompt.
This command line (i.e. only one root= option) is correct.
The error message is:
mount: /dev/sda2 already mounted or /root busy
This is weird. Could you check what's in /proc/mounts regarding /dev/sda2 or /dev/root? If /proc is empty (not mounted), you need to: mount -t proc none /proc first. Also is it possible to mount it manually like: mkdir /XX mount /dev/sda2 /XX ? Are you able to cat -A /dev/sda2? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c65
Angela Bayley
The error message is:
mount: /dev/sda2 already mounted or /root busy
This is weird. Could you check what's in /proc/mounts regarding /dev/sda2 or /dev/root? If /proc is empty (not mounted), you need to: mount -t proc none /proc first. Also is it possible to mount it manually like: mkdir /XX mount /dev/sda2 /XX ? Are you able to cat -A /dev/sda2?
cat /proc/mounts gives: rootfs / rootfs rw 0 0 /proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 udev /dev tmpfs rw,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 /proc was mounted so no need to mount manually, cat -A /dev/sda2 just gives a screen full of characters. I guess that is is just reading the disk and showing the ascii character for the disk data. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c66
--- Comment #66 from Jiri Slaby
cat -A /dev/sda2 just gives a screen full of characters. I guess that is is just reading the disk and showing the ascii character for the disk data.
Yes, exactly, so the disk is there. Hence I see no reason why it shouldn't boot normally. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c67
--- Comment #67 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c68
--- Comment #68 from Angela Bayley
(In reply to comment #65)
cat -A /dev/sda2 just gives a screen full of characters. I guess that is is just reading the disk and showing the ascii character for the disk data.
Yes, exactly, so the disk is there. Hence I see no reason why it shouldn't boot normally.
Why doesn't it mount then? (See Comment #62): Booting with root=/dev/sda2 resume=/dev/sda1 drops into the $ shell prompt. The error message is: mount: /dev/sda2 already mounted or /root busy -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c69
Jiri Slaby
Why doesn't it mount then? (See Comment #62):
Dunno. Have you tried (from c#64):
mkdir /XX mount /dev/sda2 /XX ? Are you able to cat -A /dev/sda2?
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c70
--- Comment #70 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c71
--- Comment #71 from Angela Bayley
Anyway, what's that machine?
http://www.xembedded.com/content/vme/processors/xvme-690.php
And the kernel also fails to find a root pointer (RSDP) to ACPI tables. Don't you have ACPI disabled in BIOS?
ACPI is disabled in the BIOS. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c72
Angela Bayley
(In reply to comment #68)
Why doesn't it mount then? (See Comment #62):
Dunno. Have you tried (from c#64):
mkdir /XX mount /dev/sda2 /XX
This gives the following error: cannot mount /dev/sda2, device or resource busy. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c73
Jiri Slaby
ACPI is disabled in the BIOS.
Why do you have ACPI disabled? This is a very bad idea. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c74
--- Comment #74 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c75
--- Comment #75 from Angela Bayley
(In reply to comment #71)
ACPI is disabled in the BIOS.
Why do you have ACPI disabled? This is a very bad idea.
We have to disable ACPI in order for VME interrupts to work! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c76
Angela Bayley
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c77
Jiri Slaby
We have to disable ACPI in order for VME interrupts to work!
Hmm, that seems like an overkill. What's the problem exactly? Is there a bug entry somewhere? (In reply to comment #76)
output from hexdump -Cv /sys/bus/pci/devices/0000\:00\:1f.0/config
Hmm, ACPI_EN is 1 which means enabled but it shouldn't when ACPI is off -- is ACPI off in BIOS or only in the kernel? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c78
Angela Bayley
(In reply to comment #75)
We have to disable ACPI in order for VME interrupts to work!
Hmm, that seems like an overkill. What's the problem exactly? Is there a bug entry somewhere?
(In reply to comment #76)
output from hexdump -Cv /sys/bus/pci/devices/0000\:00\:1f.0/config
Hmm, ACPI_EN is 1 which means enabled but it shouldn't when ACPI is off -- is ACPI off in BIOS or only in the kernel?
I can certainly file a bug for the interference of ACPI with VME interrupts. The reason I haven't is because it is hard to provide sufficient evidence without assuming a knowledge of the Tundra VME-PCI Bridge chip. Please note that for the XYCOM XVME-6200 processor http://www.xembedded.com/content/vme/processors/xvme-6200.php we have also to disable APIC in addition to ACPI in order for VME interrupts to be received. We disable ACPI/APIC both in the BIOS and in the kernel ("belt and braces"). It doesn't matter which method we use, either or both produces the required state - VME interrupts are received correctly. If APIC/ACPI are enabled both in the BIOS and in the kernel, VME interrupts, generated correctly by the VME bridge chip are lost and not received by the processor. I believe this is due to a software fault in the Linux kernel. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c79
Jiri Slaby
I can certainly file a bug for the interference of ACPI with VME interrupts. The reason I haven't is because it is hard to provide sufficient evidence without assuming a knowledge of the Tundra VME-PCI Bridge chip.
Why? There seems to be only ACPI IRQ routing broken... It is definitely a good idea to file a separate bug for that one (with the information I'm asking below).
we have also to disable APIC in addition to ACPI in order for VME interrupts to be received.
What happens if you enable ACPI and APIC in the BIOS and pass acpi=noirq to the kernel? And if that doesn't help, try to add noapic too.
We disable ACPI/APIC both in the BIOS and in the kernel ("belt and braces"). It doesn't matter which method we use, either or both produces the required state - VME interrupts are received correctly.
I understand, but I want to know whether the dump in the comment#76 was taken when ACPI in the _BIOS_ was disabled. I'm asking because the BIOS still reports that the ACPI base address is available (and correct). And it's not -- that's the IDE bug you are describing here.
If APIC/ACPI are enabled both in the BIOS and in the kernel, VME interrupts, generated correctly by the VME bridge chip are lost and not received by the processor. I believe this is due to a software fault in the Linux kernel.
(Or broken ACPI IRQ routing tables.) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c80
--- Comment #80 from Angela Bayley
What happens if you enable ACPI and APIC in the BIOS and pass acpi=noirq to the kernel? And if that doesn't help, try to add noapic too.
I have tried acpi=noirq but VME interrupts are NOT received correctly. It has to be acpi=off OR acpi disabled in the BIOS. (To summarize: XVME-690: VME interrupts are received correctly if ACPI is disabled _EITHER_ in the BIOS _OR_ via acpi=off on the kernel command line. XVME-6200: VME interrupts are received correctly if ACPI is disabled EITHER in the BIOS OR via acpi=off on the kernel command line _AND_ APIC is disabled EITHER in the bios ("legacy PIC") or via noapic on the kernel command line. ) I will file a separate bug report for this. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c81
Angela Bayley
I understand, but I want to know whether the dump in the comment#76 was taken when ACPI in the _BIOS_ was disabled. I'm asking because the BIOS still reports that the ACPI base address is available (and correct). And it's not -- that's the IDE bug you are describing here.
We have just checked the BIOS again. ACPI is disabled in the BIOS. The dump in c#76 was taken with ACPI disabled in the BIOS -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c82
--- Comment #82 from Angela Bayley
(In reply to comment #79)
(To summarize:
XVME-690: VME interrupts are received correctly if ACPI is disabled _EITHER_ in the BIOS _OR_ via acpi=off on the kernel command line.
APIC must be also disabled, either in the BIOS or by noapic on the kernel command line (as XVME-6200 below)
XVME-6200: VME interrupts are received correctly if ACPI is disabled EITHER in the BIOS OR via acpi=off on the kernel command line _AND_ APIC is disabled EITHER in the bios ("legacy PIC") or via noapic on the kernel command line.
)
I will file a separate bug report for this.
Filed as Bug #664210 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c83
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c84
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c85
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c86
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c87
--- Comment #87 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c88
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c89
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c90
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c91
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c92
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c93
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c94
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c95
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c96
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c97
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c98
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c99
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c100
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=558740
https://bugzilla.novell.com/show_bug.cgi?id=558740#c101
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com