[opensuse-factory] 10.2 Frozen stiff after upgrade
Hi all, Two days ago, at work, i upgraded a IBM-notebook that was installed with the 10.2-dvd. That particular machines was allways left non-connected, so when it was connected to the out-side world it discoverd that about 120 patches were available. After some time (ahum) most patches were installed (except the java-patches, that failed). Next day i booted the system, but it hang during startup, without any clear indication where of why (one time during ntfs, next time during wireless-setup, each time somewhere else. Fearing the worst, i let it run memtest for several hours, nothing came up. Booted the "other" OS; disk check, nothing wrong. Booted in resque mode from dvd, and performed filesystem check, nothing wrong. But still could not boot any more. Still system frooze stiff. AFAIK, there was no kernel-patch and the initrd was left unchanged before/after the upgrade. Because i had work to do, i re-installed the notebook again, hooked it up the net and had a suspicious look at the patches. As one of the patches involved lvm (which i allways use), I decided to install all, except lvm (and java that still failed to install) Installation and upgrade went well, untill the boot Is this an isolated incident, or is it something for bugzilla? Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF FAC4 236C 4A73 F76E EDFC D032 926E BB12 Registered linux user: 75761 (http://counter.li.org) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hans Witvliet wrote:
Hi all,
Two days ago, at work, i upgraded a IBM-notebook that was installed with the 10.2-dvd. That particular machines was allways left non-connected, so when it was connected to the out-side world it discoverd that about 120 patches were available. After some time (ahum) most patches were installed (except the java-patches, that failed). Next day i booted the system, but it hang during startup, without any clear indication where of why (one time during ntfs, next time during wireless-setup, each time somewhere else.
Fearing the worst, i let it run memtest for several hours, nothing came up. Booted the "other" OS; disk check, nothing wrong. Booted in resque mode from dvd, and performed filesystem check, nothing wrong. But still could not boot any more. Still system frooze stiff. AFAIK, there was no kernel-patch and the initrd was left unchanged before/after the upgrade.
Because i had work to do, i re-installed the notebook again, hooked it up the net and had a suspicious look at the patches. As one of the patches involved lvm (which i allways use), I decided to install all, except lvm (and java that still failed to install) Installation and upgrade went well, untill the boot
Is this an isolated incident, or is it something for bugzilla?
Hans
There is something strange going on. A few guys I know, long time SuSE users with good experience, tell me of problems they have with 10.2 on PC's and notebooks. Each and every new install or upgrade of PC's and Notebooks I've done has been flawless. All patches have gone on and up to yesterday I did a YOU on the x86_64 laptop and it's fine. I can only suggest you test with boot option "acpi=off" to see if that helps, could be kernel related. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hans Witvliet wrote:
Hi all,
Two days ago, at work, i upgraded a IBM-notebook that was installed with the 10.2-dvd. That particular machines was allways left non-connected, so when it was connected to the out-side world it discoverd that about 120 patches were available. After some time (ahum) most patches were installed (except the java-patches, that failed). Next day i booted the system, but it hang during startup, without any clear indication where of why (one time during ntfs, next time during wireless-setup, each time somewhere else.
Fearing the worst, i let it run memtest for several hours, nothing came up. Booted the "other" OS; disk check, nothing wrong. Booted in resque mode from dvd, and performed filesystem check, nothing wrong. But still could not boot any more. Still system frooze stiff. AFAIK, there was no kernel-patch and the initrd was left unchanged before/after the upgrade.
Because i had work to do, i re-installed the notebook again, hooked it up the net and had a suspicious look at the patches. As one of the patches involved lvm (which i allways use), I decided to install all, except lvm (and java that still failed to install) Installation and upgrade went well, untill the boot
Is this an isolated incident, or is it something for bugzilla?
I had something similar with a new duo-core system I bought. The 10.2 install went fine, everything seemed to run perfectly, but after a few days I would find the box comatose - blank screen, unresponsive. The box would never exceed 5 days uptime or so, and once I found it with a load average of 55 before it went comatose. There was nothing unusual running on the box at the time, and there were never any log entries indicating trouble. I installed the 2.6.18.5-SL102_BRANCH_20070120194918-default kernel on the off chance that it might have a bug fix, and that seemed to improve the reliability somewhat. The box became solid after I removed beagle, zmd and friends. It's been up for a couple weeks now. Not enough data points really, but those few facts might be of interest to someone. Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 2007-02-14 at 08:46 -0800, J Sloan wrote:
Hans Witvliet wrote:
Hi all,
<snip>
Is this an isolated incident, or is it something for bugzilla?
I had something similar with a new duo-core system I bought. The 10.2 install went fine, everything seemed to run perfectly, but after a few days I would find the box comatose - blank screen, unresponsive. The box would never exceed 5 days uptime or so, and once I found it with a load average of 55 before it went comatose. There was nothing unusual running on the box at the time, and there were never any log entries indicating trouble.
I installed the 2.6.18.5-SL102_BRANCH_20070120194918-default kernel on the off chance that it might have a bug fix, and that seemed to improve the reliability somewhat.
The box became solid after I removed beagle, zmd and friends. It's been up for a couple weeks now. Not enough data points really, but those few facts might be of interest to someone.
Humble apologies for the noise! Mea culpa, pebkac Had a UDEV-config that worked fine on a working system, but caused havoc during booting. Broke the golden rule: never change more than one thing at any time.. (blush) Thought i tested the udev-rule enough, but obviously not. Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF FAC4 236C 4A73 F76E EDFC D032 926E BB12 Registered linux user: 75761 (http://counter.li.org) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Hans Witvliet -
J Sloan -
Sid Boyce