[olug] SuSE 9.0 problems w/X freezing

Tue Dec 9 03:43:34 UTC 2003

ohci1394 is a firewire thingy IEEE1394.


> Alright, I've found out a few goodies.
>
> Here's discrepency in /proc/pci between 8.2 and 9.0:
> --------------------------------------------------
> 8.2 had:
>   Bus  2, device   8, function  0:
>     Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet
> Controller
> (rev 3).
>       IRQ 11.
> ...
>   Bus  2, device   9, function  0:
>     FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
> Controller
> (Link) (rev 0).
>       IRQ 10
>
> 9.0 had:
>   Bus  2, device   8, function  0:
>     Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet
> Controller
> (rev 3).
>       IRQ 5.
> ...
>   Bus  2, device   9, function  0:
>     FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
> Controller
> (Link) (rev 0).
>       IRQ 5.
> --------------------------------------------------
> So it looks like 2 devices, which originally were assigned separate IRQs
> (11 & 10), are both grabbing IRQ 5 under 9.0.
> Conflict, non?
>
> Maybe it's easier to see in /proc/interrupts:
> --------------------------------------------------
> 8.2 had:
>  10:          2          XT-PIC  ohci1394, Intel 82801BA-ICH2
>  11:         30          XT-PIC  eth0
>
> 9.0 had:
>   5:         25          XT-PIC  eth0, ohci1394
> --------------------------------------------------
>
> I'm not sure what this ohci business is.  Some kind of USB controller?
>
> lspci output from both 8.2 & 9.0 were the same.
>
> So do I need to 'hardcode' one of the conflicting devices in BIOS?  Or
> is there a config file I can noodle around in?
>
> Anyway, thanks for reading all this stuff.
> Fun.. fun.. FUN!
>
> Eric Pierce
>
> --- Jay Swackhamer <Jay at RebootTheUser.com> wrote:
>> Irqs are being set by the motherboard/pnp.
>>
>> You can check for contention by
>> lspci
>> cat /proc/interrupts
>> cat /proc/pci
>>
>> > Once X goes, I'm not able to get to the other terminals.  I am
>> booting into
>> > runlevel 3, so I can tinker a bit.  I thought I wiped my 8.2
>> XFConfig file, but
>> > I just remembered that it was on my failing HD.  I should be able to
>> pull it
>> > off (Knoppix to the rescue).
>> >
>> >> some causes of lockups are having 'dri' loaded in XF86Config in the
>> module
>> >> section, or not loading freetype, or having framebuffer enabled, or
>> having
>> >> shared irq's with the video/another device.........
>> > 'freetype' is loaded in the 'Modules', 'dri' isn't.  I didn't see
>> anything like
>> > 'fb' or 'frame' in XFConfig.  That is where it would be set,
>> correct?
>> >
>> > Where are irqs being set?  'modules.conf'?
>> >
>> > Thanks!
>> > Eric Pierce
>> >
>> > ps. I'll grab my /etc folder from my old system right now.
>> >
>> >>
>> >>
>> >> >
>> >> > --- Eric Pierce <eric_olug at yahoo.com> wrote:
>> >> >> Just completed a network install of SuSE 9.0 which I
>> >> >> thought went without a
>> >> >> hitch, but I can barely use X as it freezes within
>> >> >> minutes each time I start it
>> >> >> up.
>> >> >>
>> >> >> I used SuSE 8.2 on the same machine and had
>> >> >> basically no probs with my video
>> >> >> hardware setup (NVidia TNT2 32mb) w/3D acceleration.
>> >> >>  Now I can't even get Sax2
>> >> >> to stay up long enough (before X freezes) to try
>> >> >> some different settings, and I
>> >> >> don't know much about editing the XFConfig file
>> >> >> except that it seams I need to
>> >> >> run SuSEconfig after making any changes.
>> >> >>
>> >> >> Without ssh'ing into the box to kill X, I'm willing
>> >> >> to bet that the kernel is
>> >> >> still purring along in the background because I did
>> >> >> have one 3D accelerated
>> >> >> game (Marble Blast) that would bring X (under 8.2)
>> >> >> to its knees.  I could kill
>> >> >> X after ssh'ing in, but I couldn't get my screen
>> >> >> back. <reboot>
>> >> >>
>> >> >> I did have a peek at /var/log/XFree86.0.log, but I
>> >> >> can't see any errors logged
>> >> >> (not sure exactly what to look for all the same).
>> >> >>
>> >> >> Any suggestions?
>> >> >>
>> >> >
>> >> >
>> >> > I've found myself in this situation a few tims as well
>> >> > and have often wondered this.
>> >> >
>> >> > Save xf86config file before upgrading, in your case
>> >> > SuSE 8.2.  I do this with my /etc/fstab file and
>> >> > others that I don't want to mess with.
>> >> >
>> >> > If upgrade has problems with X, then install on
>> >> > xf86config file, and again, in your case SuSE 9.0.
>> >> >
>> >> > Of course you have wiped away the old system, but this
>> >> > is something to think about before upgrading to save
>> >> > heartache later...
>> >> >
>> >> > -Chris
>> >
>> > __________________________________
>> > Do you Yahoo!?
>> > Protect your identity with Yahoo! Mail AddressGuard
>> > http://antispam.yahoo.com/whatsnewfree
>> > _______________________________________________
>> > OLUG mailing list
>> > OLUG at olug.org
>> > http://lists.olug.org/mailman/listinfo/olug
>> >
>>
>>
>> --
>> Jay Swackhamer
>> Reboot The User
>> 15791 West Dodge Road
>> Suite 135
>> Omaha, NE 68118
>> (402) 933-6449
>> (402) 933-6456 Fax
>> http://www.RebootTheUser.com
>> _______________________________________________
>> OLUG mailing list
>> OLUG at olug.org
>> http://lists.olug.org/mailman/listinfo/olug
>
>
> __________________________________
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard
> http://antispam.yahoo.com/whatsnewfree
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug