Messages in this thread | | | Date | Thu, 24 Jul 2003 00:33:42 +0530 | From | Apurva Mehta <> | Subject | Re: Scheduler starvation (2.5.x, 2.6.0-test1) |
| |
* Mike Fedyk <mfedyk@matchmail.com> [2003-07-23 22:41]: > On Wed, Jul 23, 2003 at 01:48:11PM +0530, Apurva Mehta wrote: > > The problems do not end there. Once I start X, I experience > > random freezes of the system. In one session I could play some music > > and write some email. It froze just after dialing into the > > internet. In another session it froze while trying to start xmms. > > please post the output of lspci here. Also, what version of Xfree86 are you > running, and read the documentation for the nmi oopser in the kernel > documentation tree, and turn it on for your system. > > Then we might be able to get a useful message out of your system.
Here is the output of lspci:
------
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 23) 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 10) 00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 11) 00:04.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 30) 00:0b.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 15)
------
I enabled the nmi watchdog by appending nmi_watchdog=1 to my kernel boot parameters. I verified that it was enabled by doing a `cat /proc/interrupts`. The NMI value was 30.
Still, there are no special messages in /var/log/messages or in any XFree86 log nor in any boot log..
May be the nmi watchdog is not working because it is not a normal 'freeze' per se. What happens is that my mouse still moves around the screen, I can also type (*only* type) commands into an xterm. But those commands cannot be executed. When I try to execute a command, nothing happens, I do not even get the prompt back. If I try to login to a virtual console, I can type my login name, but then the password prompt does not come up. When I try to switch back to X, I cannot do so and I get stuck at that blank screen. Then I am force to do a cold reboot.
Sometime during the subsequent boot process, I get that error message while trying to load a random startup program. Last time, it was while trying to load xfs.
Also, I have found that there is no pattern to the sequence of operations that lead up to these freezes. I mentioned that if I executed some programs on a virtual console before starting X, then X would load fine, otherwise it would not. This is not true all the time.
- Apurva - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |