[Bug 757858] New: Installer using default kernel begins system probing hangs at "Search for Linux partitions"
https://bugzilla.novell.com/show_bug.cgi?id=757858 https://bugzilla.novell.com/show_bug.cgi?id=757858#c0 Summary: Installer using default kernel begins system probing hangs at "Search for Linux partitions" Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 3 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rb03884@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=486758) --> (http://bugzilla.novell.com/attachment.cgi?id=486758) inxi -F readout of my setup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Since 12.2 M1 - M3. The installer using the default kernel always hangs at "System Probing" when it tries to "Search for Linux partitions". The only way around this was to add acpi=off to Boot Options or select "NO ACPI" or "Safe Setting". Reproducible: Always Steps to Reproduce: 1. Select default kernel 2. Installer gets to System Probing --> Search for Linux partitions 3. Installer hangs 4. Press reset button to restart installation and select "NO ACPI". Actual Results: The installer using the default kernel always hangs at "System Probing" and "Search for Linux partitions". I have 12.1 installed on the first 4 partitions. Expected Results: The installer should not hang when System Probing --> Search for Linux partitions. When I tested 11.3 - 12.1 Milestones with default kernel. They never hang when the "Search for Linux partitions" was performed. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c1
Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c2
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c
Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c3
--- Comment #3 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c4
--- Comment #4 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c5
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c6
--- Comment #6 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c7
--- Comment #7 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c8
--- Comment #8 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c9
Thomas Renninger
Sorry. I cannot provide a screenshot. I do not have a camera. Ok, it's somewhat difficult then without any output of the affected system.
You say, this happens since: Since 12.2 M1 - M3 Do you still remember a as recent as possible working kernel? Like that I have a chance to look at relevant patches which came in in this time frame. I have to read up quite some mails on the acpi list. Hopefully I see something related. If not I may try to remove the latest ACPI 5.0 patches, they are typically rather separated and this may work out without too much work. Stay tuned, this may take time. If pci=noacpi works, most/all power management features should work and this may be a sufficient workaround for you for some time. If pci=noacpi works, please also try pci=nocrs. Setting needinfo flag for pci=noacpi test. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c10
--- Comment #10 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c11
--- Comment #11 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c12
--- Comment #12 from Roman Bysh
Sorry. I cannot provide a screenshot. I do not have a camera. Ok, it's somewhat difficult then without any output of the affected system.
You say, this happens since: Since 12.2 M1 - M3
Do you still remember a as recent as possible working kernel? Like that I have a chance to look at relevant patches which came in in this time frame.
I have to read up quite some mails on the acpi list. Hopefully I see something related. If not I may try to remove the latest ACPI 5.0 patches, they are typically rather separated and this may work out without too much work. Stay tuned, this may take time.
If pci=noacpi works, most/all power management features should work and this may be a sufficient workaround for you for some time.
If pci=noacpi works, please also try pci=nocrs. Setting needinfo flag for pci=noacpi test. What is the exact command for "set needinfo flag for pci=noacpi test"? -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c13
--- Comment #13 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c14
--- Comment #14 from Thomas Renninger
What is the exact command for "set needinfo flag for pci=noacpi test"? These are 2 different things: -> set needinfo flag for this bug. If you have a look at the state of the bug, it's up to you to provide some information. This is for better handling if one has to deal with quite a lot bugs.
-> pci=noacpi Sorry, I should have been more clear about that. This is a boot parameter. You can add additional boot parameters at the point when the SUSE DVD got booted and you choose between: - Boot from Harddisk - Installation - ... There is a field where you can add boot parameters, there add: pci=noacpi and choose the Installation (as you've done before). If pci=noacpi helps, you should be able to use the system without any bad side effects. Switching of ACPI in general (acpi=off, safe settings) will result in missing some important Hardware features. It looks like Interrupt or resource settings provided by ACPI prevents one device (the disk?) to get initialized properly. If the kernel is able to set it up without ACPI info (pci=noacpi) everything should be just fine. It would still be interesting to find out why this happens, but you can at least work with the system. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c15
--- Comment #15 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c16
--- Comment #16 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c17
--- Comment #17 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c18
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c19
--- Comment #19 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c20
--- Comment #20 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c21
--- Comment #21 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c22
--- Comment #22 from Thomas Renninger
I have watched the boot up and it flickers intensely. Does that mean it's readable/photographable?
Try with "Text mode" if you boot from install DVD. And/or add vga=normal as boot parameter. Hm, evtl. nomodeset boot param helps. But this one depends on which graphics card you have. ATI: radeon.modeset=0 (ATI graphics card) nouveau.modeset=0 (NVidia graphics card_) may help. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c23
--- Comment #23 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c24
--- Comment #24 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c25
--- Comment #25 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c26
Tom C
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c27
--- Comment #27 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c28
Thomas Renninger
Please fix it soon! Tom: I need some data to be able to fix this. This is a very platform specific bug.
You may have to scale the photo and invert the colors to read it. I cannot see anything on this screen shot. It looks like some ACPI paths show up there, but I cannot read it. If possible boot with vga=normal parameter and also try to scroll up a bit and photograph the beginning of the error messages (and some non-error messages to be able to get an idea at which stage of booting this happens).
-- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c29
--- Comment #29 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c30
--- Comment #30 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c31
--- Comment #31 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c32
--- Comment #32 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c33
--- Comment #33 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c34
--- Comment #34 from Thomas Renninger
As mentioned before the problem happens during the installation? Once I'm up and running, I remove the command from the kernel options and I'm okay. Ah ok, you mentioned that in comment #10, that's an important detail I've overseen.
In fact this is really strange... This does not have to do anything with the disk or partition layout. ACPI may be involved when the sata/disk driver is loaded, but once the HW is working, ACPI is out of the game. It looks like the install (userspace) system is trying to load an ACPI driver manually which otherwise would not be loaded or is playing in /sys or /proc which triggers ACPI code to be interpreted by the kernel. Strange is that this seem to happen in parallel when the disk is scanned for other Linux/OS installations. Does it always hang at exactly the same point? If there is a thermal or other HW event happening..., this would explain why ACPI is involved again, but this should not always happen at exactly the same stage. One test could be to blacklist all kind of acpi drivers for the installation via: brokenmodules=video,acpi-cpufreq,processor,thermal,button,wmi,battery You find more here in an installed system (adjust the kernel version): find /lib/modules/3.0.4-0.0.0.1.a432f18-default/kernel/drivers/acpi/ |grep "\.ko" Best add every ACPI driver you can find to brokenmodules=. The guy who is most involved in the installer (linuxrc), is on vacation until today. I try to reach him as soon as he's back. But I fear he also won't have much of a clue, as the problem (ACPI, HW related) and the time it is happening (when all HW should have been initialized already) is really strange. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c35
--- Comment #35 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c36
Roman Bysh
It looks like the install (userspace) system is trying to load an ACPI driver >manually which otherwise would not be loaded or is playing in /sys or /proc >which triggers ACPI code to be interpreted by the kernel. Strange is that this >seem to happen in parallel when the disk is scanned for other Linux/OS >installations. Does it always hang at exactly the same point?
Yes. It always hangs in the same place I tried "brokenmodules=video,acpicpufreq,processor,thermal,button,wmi,battery" and it hangs at the same spot. I'm going to try the rest that were not listed from the ACPI folder. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c37
--- Comment #37 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c38
--- Comment #38 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c39
--- Comment #39 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c40
--- Comment #40 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c41
--- Comment #41 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c42
--- Comment #42 from Roman Bysh
Sure: 1) Try to reproduce in an installed system with acpi=off removed ================================================================
1.1 Boot the installed system with acpi=off removed from grub2 configs Not exactly sure where yast puts the acpi=off param when installed with this param with grub2. Could be: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash=silent acpi=off" then remove acpi=off and run: grub2-mkconfig -o /boot/grub2/grub.cfg or just remove it from /boot/grub2/grub.cfg to give it a try
1.2 When booted run: 1.2.1 hwinfo -> does it cause the hang? If yes, try to find out on which HW probing it hangs (hwinfo disk?) 1.2.2 yast2 disk -> this should initialize disk HW similar to what happens at the installation stage when the machine hangs
Response No problem with hwinfo. What has changed with the kernel in 12.1 compared to 12.2? What if I were to try out the live cd? OTOH I might be delayed due to the fact that I've hit my monthly maximum. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c43
--- Comment #43 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c44
--- Comment #44 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c45
--- Comment #45 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c46
--- Comment #46 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c47
--- Comment #47 from Thomas Renninger
Any one else using the P5Q mobo in Germany? Yep, this is probably a very machine/BIOS specific issue.
I'm wondering why you want me to deviate via the ssh route trying an alternate method for installation when the problem lies within the "System Probing". This is the only way to be able to retrieve logs/debugging output when the system hangs during installation. It's not really an alternative installation method. It's just that an ssh daemon is started before the installation starts. If the system does not hang totally (irqs are still delivered and network, etc. still works to some extend, you can then log in, examine why it did hang and copy away logs over the network).
It sits for a while at hard disk and then hangs probing for Linux partitions. I cannot see that this has to do with Linux partition probing. It must be something HW related, because of ACPI being involved. Possibly yast tries to configure software raid or similar at this point.
I need more info. A clear picture of the hang, yast logs, dmesg, top, ... when the system hangs or whatever. As said, if the machine's network still responds when the system hangs, please start a ssh installation and try to copy this info over network via scp. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c48
--- Comment #48 from Tom C
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c49
Michael Shields
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c50
--- Comment #50 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c51
--- Comment #51 from Thomas Renninger
All the requests heated up the IDE DVD drive. Is this really an IDE or could it be a SATA drive?
-- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c52
--- Comment #52 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c53
--- Comment #53 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c54
--- Comment #54 from Tom C
By default the value should be "auto": cat /sys/devices/pci0000:00/*/ata*/power/control
I did this on my machine, and the values are already set to ON for all. If I am reading your response correctly, this means its already disabled. I am still having the problem.
But this makes only sense if you have SATA DVD drives. Michael (Shields) mentioned in comment #49:
All the requests heated up the IDE DVD drive. Is this really an IDE or could it be a SATA drive?
In my machine the DVD is definitely an IDE drive. The hard disks are SATA. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c55
Tom C
What is urgently needed are yast logs when this is happening. Yast logs everything in detail to /var/log/Yast2 or even better, there is a tiny executable which collects all needed data: save_y2logs /tmp/yast2logs.tar.bz2
I didn't redo the install, however the same slowness also occurs in yast when you bring up the 'partitioner' feature. It sits there for a VERY long time displaying the message "Volumes are being detected". I assume this is the very same problem that happens during install. So I used the save_y2logs command above a few times while it was sitting there running and I was waiting for it. Then I waited it out, and ran it one final time after it had brought up the expert partitioner window. Hopefully this is what you need, so I removed NEEDINFO flag on this bug. If this doesn't do it, please put the flag back and let me know if there is something else I can help you collect. yast2logs-4.tar.bz was the most recent one I made BEFORE it finished detecting the volumes. yast2logs-final.tar.bz was made after it passed that step and loaded the main window. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c56
--- Comment #56 from Tom C
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c57
--- Comment #57 from Tom C
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c58
Thomas Renninger
I didn't redo the install, however the same slowness also occurs in yast when you bring up the 'partitioner' feature. It sits there for a VERY long time displaying the message "Volumes are being detected". I assume this is the very same problem that happens during install. Perfect! That makes things *much* easier to test/verify.
Things seem to get stuck in blkid call issued by yast. After talking with installation and Yast partitioner guys, there may already be a duplicate (bug #757368). It seem to be a (not existing?) floppy drive that the is tried to get probed. You can try by not loading the floppy driver. During installation pass this grub/kernel boot parameter: BrokenModules=floppy or easier when you can reproduce this at runtime, make sure the floppy driver is not loaded: Add this line to /etc/modprobe.d/99-local.conf: blacklist floppy and remove the module manually if it already got loaded: rmmod floppy and try again to start the yast partitioner. Unfortunately kernel logs are not included in the yast logs you posted. But if this happens you should see quite some kernel messages pointing to the floppy driver in dmesg (command) or /var/log/messages similar to what got reported in the bug I mentioned above. If you can verify that this is about the floppy driver, I am going to poke the guys in the other bug that this is more urgent they think it is... -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c59
--- Comment #59 from Thomas Renninger
Fortunately, the issue appears to be fixed in 12.2 Beta 2. Still it would be great if you give the "not loading floppy driver" a try to be able to further limit the issue. It should be much easier to test things now.
Please also have a look at /var/log/messages (best attach it) if this still happens. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c60
--- Comment #60 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c61
--- Comment #61 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c62
--- Comment #62 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c63
--- Comment #63 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c64
--- Comment #64 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c65
Tom C
make sure the floppy driver is not loaded: Add this line to /etc/modprobe.d/99-local.conf: blacklist floppy and remove the module manually if it already got loaded: rmmod floppy and try again to start the yast partitioner.
Hi Thomas, I did this, and the problem is gone! The partitioner now goes through the search VERY quickly. For the record, there is no floppy disk drive attached to this system. -- 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.
Thinking that the BIOS had something to do with it Yep, definitely. This is something that only happens on specific
Could an overheating CPU cause this problem? No. What happens when the CPU overheats is HW specific, typically the OS is told to restrict CPU frequency. But CPU power would still be enough for (nearly) the same IO (disk, DVD,...) performance. There are othere techniques, e.g. throttling (or even shutdown, ...). There the CPU is even slower, but it would not get stuck like that and always at the same
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c66
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c67
--- Comment #67 from Tom C
So you did not modify the BIOS and the issue is solved by not using the floppy driver?
Correct, I did NOT modify BIOS. I only disabled the floppy driver.
Can you double check that you have the latest 12.2 kernel running (zypper update).
I will have to check later on when I get home from work to see if there are any kernel updates applied, but I don't think so. -- 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=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c68
Axel Keller
https://bugzilla.novell.com/show_bug.cgi?id=757858
https://bugzilla.novell.com/show_bug.cgi?id=757858#c69
Thomas Renninger
participants (1)
-
bugzilla_noreply@novell.com