Re: [Vectorlinux-devel] VLdynamite locking up using ATI driver.

[uel a. <ue...@gm...>]

i put a post to the forum looking for similar hardware so we can see if this
problem can be duplicated
also I have built a non-smp kernel for the next dynamite hopefully we can
figure this out

Uel

On 9/6/06, Jose J. Rodriguez <jo...@gm...> wrote:
>
> On 9/6/06, Jose J. Rodriguez <jo...@gm...> wrote:
> > On 9/6/06, nig...@ju... <nig...@ju...> wrote:
> > > Not sure if I'm doing this right.. In lilo.conf, I changed the line:
> > > append = ""
> > > to this:
> > > append = "nosmp"
> > > or:
> > > append = "maxcpus=0"
> > >
> > > and then ran "lilo"
> > >
> > > In both cases, I get some kind of IDE errors:
> > > --- snip--
> > > ide1 at 0x170-0x177, 0x376 on irq 15
> > > hda: max request size: 128 KiB
> > > hda: lost interrupt             <------- here is where it slows down--
> > > hda: lost interrupt             <----- no response to keyboard---
> > > hda: lost interrupt
> > > hda: lost interrupt
> > > hda: (xxxxxxx sectors, size, cache, UDMA status...)
> > > hda: cache flush supported
> > > hda:<4>hda: dma_timer_expiry: dma status == 0x661
> > > hda: lost interrupt
> > >  hda1:
> > > hda: lost interrupt
> > > .......
> > >
> > > It repeats this for hdb and hdc, after around 5 minutes, about halfway
> > > through hdc the screen goes blank and nothing more happens.
> > >
> > > Are there variances in the syntax I should try?
> > >
> >
> > Sounds right to me. Anyway, just found another one specifically for HT:
> >
> > "The `noht' Argument:
> > This will disable hyper-threading on intel processors that have this
> feature."
> >
>
> After some testing and more searching, "noht" seems to be gone from
> current kernels and "nosmp" gives me the same problem as you get.
>
> Funny thing is, I've been getting a hard lockup lately when closing
> the KDE session. KDM starts to show up, but it will not get as far as
> showing any text or user avatars. Only a hard switch-off will get me
> out of that. I'm not sure when it started, but I suspect after
> upgrading the propietary ATI driver from one version to the next.
> Can't be quite sure though. A search shows this is something that
> happens now and again in various KDE versions, but I couldn't find a
> definite explanation for any case. Anyway, this happens the same with
> HT enabled or disabled in the BIOS. I'll have to experiment with my
> previous ATI driver, or the new one that was just released.
>
> I still don't see the kind of X unresponsiveness you get though. I'll
> have to experiment extensively on the next Dynamite, as it seems to be
> an xorg 6.9 problem and I have 6.8.2 on my SOHO.
>
> Regards,
> Joe1962
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>