Announcement

Collapse
No announcement yet.

Interesting jump in stability

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Interesting jump in stability

    I've modified the powersave scripts on my system to bring down my frontend, any associated apps it may be running, then X, then a couple other key modules that are flakey when the system resumes. Of course it now takes a good 15 seconds more to resume but the difference in stability now is worth it.

    Before I made the changes, the system would crash inexplicably on about every 10th resume from hibernation. Now it never ever crashes (at least not yet knock on wood )

    The affected modules are ivtv and ati_remote and effectively the userspace X radeon driver with the restart of X. Most likely the cause is either the radeon kernel driver or the X radeon_drv.o driver but in any case I thought I'd throw that tidbit out here in case anyone is having similar problems.

    Rather than putting the modules into the sysconfig entries for removal and reinsertion (because it wasn't making any difference) I put the necessary rmmod and kill entries at the very beginning of the the sleep function and the necessary modprobes in the resume function inside /usr/lib/powersave/scripts/sleep_helper_functions (that's where it is on a SuSE distro anyway).

    Starting X on resume is more convoluted so I won't go into it unless anyone is curious how I did it (assuming I'm not the only one having this problem - in that case well I sucked and now I don't and this post serves only to inflate my ego knowing I finally got my system to stop it's weirdness albeit with a compromize of an extra 15 seconds).
    Silverwolf 2 is dead.
    Silverwolf 3...?

  • #2
    Okay I need to ammend results. After more usage the ratio of killing X before suspending compared to not killing it is close to the same, although some of the driver instances that are restarted before and after hibernation are still working better than before so at least there is a little more success in that regard.

    I'd like to get other users' experiences with hibernation using swsusp. What I'm experiencing is a random lockup a few minutes after system returns from hibernation. Sometimes it's fine and sometimes it's not. Any other's experiencing this? I'm running 2.6.11 kernel on an MII-12000.
    Silverwolf 2 is dead.
    Silverwolf 3...?

    Comment


    • #3
      .

      Are you sure its the OS? I mean are you testing this in a car? Maybe you have a hardware issue???

      Just a thought tho, I apoligize if you've got that covered.
      Progress [I will seriously never be done!]
      Via EPIA MII
      512MB RAM
      OEM GPS (embedded)
      nLite WinXP pro on
      1GB Extreme III CF card
      Carnetix 1260 startup/ DC-DC regulator
      Software: Still, re-Writing my existing front end in .Net

      Comment


      • #4
        Try using swsusp2. I had it running for a while on my epiaM gentoo system and kernel 2.6.8 (pre carputer) without any problems. Hibernation and resuming while having X loaded and playing video in mplayer or xine worked as well.
        Carputer installed!!!
        Nlited XP+Minlogon, EpiaM10k, 512mb, Seagate 40 gig 2.5" HD, FM Dlink usb radio, DWL122 USB Wifi, XMD1000 tuner, PT5071 6 amp regulator, Xenarc 700TSV, and 1 ikea key box.

        Comment


        • #5
          That's what I'm using now. It's reasonably stable but it's a pain when it hangs unpredictably (roughly about every 10th startup). If I can't find a reliable solution I'm going to look into speeding up a cold boot as much as possible (had it down to roughly 60s before switching to swsusp2) and just live with the extra delay.
          Silverwolf 2 is dead.
          Silverwolf 3...?

          Comment


          • #6
            swsusp2 is getting better and better. i'd use the latest kernels. 2.6.14rc1 is out, then patch the kernel w/swsusp2's latest patch for that kernel. i was running 2.6.12 (gentoo) w/swsusp2 and it was great,. previous versions never recovered completely. granted, i am not running the same hardware, just a 400 Mhz celeron pII laptop...

            are you using the hibernate script from swsusp2 (i think)? its good, simplifies shutting down/stopping services/restarting services etc.

            also someone previously posted initng here - that is the best way to go for speeding up bootup. it'll take a bit of work to get it up and running due to the lack of initscripts, but i'm sure relatively soon it'll be good and it will replace the old init, which is not really parallel and 'smart'.

            Comment


            • #7
              Thanks for the input. I'm running 2.6.11 right now and haven't upgraded to the latest and greatest swsusp2 yet so that's something I'll look into. I looked into initng a while back but as you say it's a bit laborious to set up and when I was checking it out I didn't have the time to devote to implementing and testing it out. For now I've reverted back to the full shutdown/cold boot scheme. It takes >60s to boot now but at least it's reliable.

              One thing I want to look into as well is getting a mingetty running as soon as possible into the boot sequence so it can autologin as root, start X, etc. via the .bashrc and let the rest of the sequence continue on in the background. If I can get X and my frontend up within 30-45 seconds I think I can live with that. When I have more time I think linuxbios may be something to look into to get past the POST faster. The MII-12000 takes a good 10s to get past it.
              Silverwolf 2 is dead.
              Silverwolf 3...?

              Comment


              • #8
                Originally posted by intuitionsys
                One thing I want to look into as well is getting a mingetty running as soon as possible into the boot sequence so it can autologin as root, start X, etc. via the .bashrc and let the rest of the sequence continue on in the background. If I can get X and my frontend up within 30-45 seconds I think I can live with that. When I have more time I think linuxbios may be something to look into to get past the POST faster. The MII-12000 takes a good 10s to get past it.
                Hmm, sounds to me like people may want to consider doing a little more tuning of the system before getting too carried away with other custom stuff.

                The system being built here (M10K-N, Gentoo, autologin, full blown X, ALSA initializing two audio devices w/ modules, audio output from GQMPEG) gets up and running in about 40-45 seconds without even trying. This is measured from after hitting enter on the grub screen.

                If you are including the BIOS and grub screen stuff in your times then ignore this post.
                My stagnant project

                Comment


                • #9
                  The dell laptop I'm using (Inspiron 2200) has a fast boot option and gets you to the grub/lilo screen in about 2 or 3 seconds. From there I can get to the init in about 10 more seconds. Then about another 20 or 30 seconds to get kde up and running.

                  I may work at optimizing boot times. Currently they check and load stuff they don't have too. The inspiron is a cheap laptop in pretty much all ways, however, with the fast boot time I may use it in my carputer and get another laptop to replace it for home use.
                  My carputer project

                  Comment


                  • #10
                    i think removing X would help quite a bit in speeding up the process to get to the 'useable' state. for those frontends that need X, consider using XDirectFB. it provides the windowing layer but skips the networking stuff (i THINK, check out www.directfb.org). DirectFB is some cool stuff, it has framebuffer acceleration for a few video cards (which i can't use). i used XDirectFB once...but that was awhile ago. my 400mhz pII celeron laptop is pretty slow by conventional standards...but handles framebuffered dvds quite easily with mplayer. with X, memory requirements (limited to 160mb here) tend to slow it down a bit and introduce a few glitches/timing problems.

                    Comment


                    • #11
                      I tried this but did not see an appreciable performance increase. At the time (~9 months ago) DirectFB had issues with image redraws and artifacting when page flipping and used in my environment.

                      It may be a function of my platform (CLE266 on VIA M10k-N) but given there did not seem to be much of a "seat of the pants" speed difference I was content to revert to X.org. Might be worth a go on other platforms?
                      My stagnant project

                      Comment

                      Working...
                      X