| Autor |
Nachricht |
|
|
Titel: lockup after dist-upgrade
 Verfasst am: 09.10.2006, 15:56 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
I have a Kanotix 2005-04 system which has been upgraded several times. I just did another dist-upgrade which seemed to go OK except for some problems with fontconfig & openoffice...this was expected as it is posted on Kanotix main page.
but now x won't start!
Code:
Running local boot scripts (etc/rc.local)
Debian GNU Linux testing/unstable Desktop tty1
Desktop login:[drm: i810_wait_ring] *ERROR* space 65520 wanted 65528
[drm: i810_wait_ring] *ERROR* lockup
and the system freezes.
After a few attempts it will go to a console login from there but still am unable to start x from console login.
How do I fix this? |
|
|
| |
|
|
|
 |
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 09.10.2006, 17:18 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16792
|
|
| Most simple way: update-install to a new version. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 09.10.2006, 19:13 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
| Ouch! I was afraid of that. Not that it is difficult; I use Kanotix because it is so easy to install but my version gets quite a bit of customization & I will have to redo all of that. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 09.10.2006, 19:23 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 09.10.2006, 20:02 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
Yea, use h2's script, and you might want to select the xorg7 fix when presented with that option (it's one of the options after the dist-upgrade bit) ... it has helped other users with the same problems:
http://kanotix.com/PNphpBB2-viewtopic-t-21443.html |
_________________
Linux is evolution, not intelligent design - Linus Torvalds
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 21.10.2006, 16:43 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
OK, I have tried to install 2006-01-RC3 but it gives a segmentation fault for tuxracer...which is a "must have" for a couple of my favorite users. I have tried two installs on two different drives...same error.
I have never been able to fix a segmentation error.
Then I did a d-u...after which the printers quit (see my post in this thread: http://kanotix.com/index.php?name=PNphp ... highlight= ) and so far I have been unable to get them working again.
So I'm back to trying 2005-04, just did a fresh install & checked tuxracer works OK.
dmesg is reporting the following:
Code:
mtrr: base(0xf8000000) is not aligned on a size(0x180000) boundary
(2006-01 also had this error but BH9 did not)
Could it have been the cause of the first crash (my original post)?
How do I correct this? My search suggests adding 'vga=normal, nomtrr' to grub to disable mtrr but that doesn't seem to work, mtrr is still running when the system starts up. Disabling seems like a poor fix in any case.
Thanks
If this install works I will not dist-upgrade it...ever. Over the years, my succes with dist-upgrades has been less than 50% and at least 10% of the times dist-upgrade has killed the system completely. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 21.10.2006, 17:46 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
The thing to do is to create a test install for dist-upgrades. If you try to dist-upgrade a 2005-4 without my script your chances of success are close to zero at this point unless you know each and every fix the script runs automatically.
All my systems are 2005-4 and fully upgraded, but I admit I don't print so I can't speak to that. I also do regular backups, especially before risky upgrades, using my backup script, so restoring my / is a breeze. And, I make sure to keep / and /home on separate partitions always, so restoring always returns me to almost exactly where I was should a du go bad, which has happened now only 2 times in 1 year, and one of those times was only apache2 related. The apache issues only mattered if you ran apache locally, and only broke apache, so I don't count that.
Also keep in mind that I test du stuff much more than most people, so my odds of faiilure are actually higher than other people's I think, so even with that I'm doing quite well in terms of everything working.
Keeping a standard, non-upgraded install is great if you never want to install any new software at all, however the odds of any single package pulling in other things rises with time, so using an un-updated install is only a good option if you set it up, then leave it alone forever. This doesn't strike me as a very realistic user scenario, so I'd do either upgrades or dist-upgrades fairly routinely.
Your experience with kanotix is like mine, I broke early versions with dist-upgrades too, that's why I started my script, to avoid those issues as much as possible.
To restore:
have your rdiff-backup completed
reformat / partition with mkreiserfs /dev/<root partition>
restore using livecd to root partition from rdiff-backup
This entire restore process takes about 15 minutes or so. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 22.10.2006, 05:24 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
You've almost convinced me to try a d-u again. Other the other hand, a really large % of the problems posted in this forum are related to d-u's.
I think I agree with Swynndla (http://kanotix.com/PNphpBB2-viewtopic-t-21222.html ) that upgrades not dist-upgrades are safer.
Before there was kanotix I used Knoppix (started with version 3 or so) which rarely survived a dist-upgrade so the guideline was upgrade packages (with apt-get install) but don't apt-get upgrade the system. Right now my most reliable system is the BH9 install which has been upgraded a few times and has most packages up to date as of a couple of months ago. I am trying to replace it mainly because I have discovered that it seems to have a buggy drive for the DVD. Otherwise it works fine although startup/shutdown takes about twice as long as the newer versions.
Which brings back to the other points...the not aligned mtrr and the segmentation faults. Does anyone know anything about these? Perhaps I will post these as separate topics.
Which bring |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup after dist-upgrade
Verfasst am: 22.10.2006, 05:30 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
common causes for errors: failure to burn original iso with DAO or SAO, disk at once, session at once.
burning too fast, best to burn slow speed
burning with bad blanks, or a weak cd burner, or a cheap cd burner, or cheap no name / department store type cd blanks
After that, if those are not valid, which they unfortunately often are, and if you are starting from latest version available, du from that version should be safe.
But use my script, it's designed to handle the bumps of du and smooth them out.
As for the upgrade/dist-upgrade question, I can't give a real answer to that since I don't know, but my stuff is all running just fine with du for almost 1 year now, like most kanotix people who do the upgrading route.
The problem with upgrade is that you will need to know which packages to manually install, which fixes to run, and so on, at some point of that route no matter what.
But if you don't follow irc/forums/warning pages you will one day get bitten by a du bug for sure. My script also lists current or older but still valid warnings. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: Re: RE: lockup after dist-upgrade
Verfasst am: 22.10.2006, 05:50 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
|
h2 hat folgendes geschrieben::
common causes for errors: failure to burn original iso with DAO or SAO, disk at once, session at once.
burning too fast, best to burn slow speed
burning with bad blanks, or a weak cd burner, or a cheap cd burner, or cheap no name / department store type cd blanks
Assuming you are referring to my comment about the DVD driver, unfortunately it's not that sort of problem at all.
What it is is that the DVD was giving seek errors when trying to read a disk which reads fine in Windows. At first I thought this was just a Linux thing but then I tried to do an install based on Debian netinstall and discovered it would read just fine with this. Failed miserably with the install, it's just too complicated to build a system as complete as Kanotix so I tried 2005-04 ( I think it's the Easter version, current as of about June this year) and discovered the DVD would read just fine with it too. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: lockup after dist-upgrade
Verfasst am: 22.10.2006, 07:40 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
No, I wasn't actually referring to the dvd comment, just on a very frequent error people make, which is assuming an old, weak dvd/cd burner which may work ok for other stuff will work on kanotix compresssed isos.
These kinds of errors you're having are a very frequent symptom of that problem, and there is no hard and fast test to know if the burn was good or bad except to ask these questions:
was it burned sao/dao
was it burned too fast
is the drive old/fading
is the blank poor quality
If the answers to any of these are not known, the odds are very good that the cd was not burned well, and may be the cause of your issues. Hard to say of course, but this is far more common than people like to admit.
When people have routine failures, I've started to stop looking in kanotix for the errors and have started looking for other causes. This has turned out to be the case in many of the failures I've seen. This can be many different reasons, for some it's bad burns, etc, for others it's installing some package or other from source that ends up breaking the system.
The routine failure is the thing to focus on however. Almost every single person here I've followed up on or with about routine failures has always done something or other to trigger that failure, could be formatting issues of drive, burn problems of iso, lots of things. But one thing it has rarely been is Kanotix itself.
This is not to say that doing a dist-upgrade is all that safe, but it's not all that dangerous either. So far I have done zero reinstalls, but have done a few restore from backups. But I push this more than most I think. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: lockup after dist-upgrade
Verfasst am: 22.10.2006, 16:22 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
The problems I was having were read errors (seek errors) on DVD's..both on commercial DVD's (movies etc) and on DVD's I had burned myself using a Lite-on DVD player/writer. These DVD's would read OK everywhere else including with the same DVD drive on Windows (dual-boot system).
Once I discovered that only the BH9 system was giving trouble, I tried to find out how to fix it (update the DVD driver???) but was not able to find out where/what/how to upgrade....assuming of course that upgrading the driver would fix it. Sometimes it's just not fixeable for instance I have never been able to fix anything that is giving segmentation errors. The BH9 gives segmentation errors trying to run flightgear, all the upgrades I can do doesn't help. 2005-04 doesn't have this error. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: lockup after dist-upgrade
Verfasst am: 26.10.2006, 04:58 Uhr
|
|
Anmeldung: 20. Nov 2004
Beiträge: 62
|
|
Just FYI, I tried a 2005-04 install again & the original error ("Desktop login:[drm: i810_wait_ring] *ERROR* space 65520 wanted 65528
[drm: i810_wait_ring] *ERROR* lockup ") and system crash occurred after upgrading xorg (apt-get install xorg by itself) so I doubt if it could have been predicted & it would have happened with or without d-u-ing by script.
It appears there is something incompatible between 2005-04 and my system. Wonder what it is? |
|
|
| |
|
|
|
|
|
|
