[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: System freeze (Update, Close to the reason)



X gets kindof restarted for every new session initiated by kdm,
maybe that's locking you off. 
If you have some stable LAN anywhere (another NIC) you can find out via ssh 
or telnet if only input devices are dead but the kernel is still running.
A real kernel guru will be harder to track...Use grub pre-boot edit mode for 
debugging and try pci=routeirq.
/usr/src/linux/Documentation/kernel-parameters.txt

> > ----------  snip ------
> > Nov 26 16:23:07 protheus2 kernel: APIC error on CPU0: 40(40)
> > Nov 26 16:28:07 protheus2 kernel: APIC error on CPU0: 40(40)
> > Nov 26 16:33:09 protheus2 kernel: APIC error on CPU0: 40(40)

This may or may not be related.

> > Nov 26 16:33:21 protheus2 kernel: bcm43xx: Controller RESET (TX timeout) ...
> > Nov 26 16:33:21 protheus2 kernel: ACPI: PCI interrupt for device 0000:06:05.0 
> > disabled
> > Nov 26 16:33:21 protheus2 kernel: PCI: Enabling device 0000:06:05.0 (0000 -> 
> > 0002)

(... until "controller restarted")

ok the net driver gets reinitialized  ....but why, in first place ?
Are there any other useful logs (daemon.log, syslog) ?

> You have the problem with fgrlx and ATI, I have it with the fb server 
> and nvidia.  What is left?  What do we still have in common?

A kernel interrupt problem ?
 
A typical 2.6.18 SMP irq table before any X launched (textconsole):

          CPU0       CPU1       
  0:      21818     215693    IO-APIC-edge  timer
  1:        954          0    IO-APIC-edge  i8042
  9:        108          0   IO-APIC-level  acpi
 12:       2890          0    IO-APIC-edge  i8042
 14:       1697          0    IO-APIC-edge  ide0
 66:       3084          0         PCI-MSI  libata
 74:      25226      13363   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb5
 82:        107          0   IO-APIC-level  uhci_hcd:usb3, HDA Intel
 90:          0          0   IO-APIC-level  uhci_hcd:usb4
 98:         75          0         PCI-MSI  eth0
169:         91          0   IO-APIC-level  uhci_hcd:usb2, yenta
NMI:          0          0 
LOC:     236863     236749 
ERR:          0
MIS:          0

Launching X adds the fglrx (ati) driver:

(...)

169:      12362          0   IO-APIC-level  uhci_hcd:usb2, yenta, fglrx
NMI:          0          0 
LOC:     554243     554129 
ERR:          0
MIS:          0

As POC you may try to temprarily move  /etc/rc2.d/S99kdm out of the way
and start kdm manually (as root, kdm &) at the point where the frereze
uses to occur.




 m°



Reply to: