On Mon, Oct 03, 2005 at 11:55:58AM +0200, Hugo van der Merwe wrote: > Horms wrote: > > >On Sat, Oct 01, 2005 at 05:16:06PM -0700, Steve Langasek wrote: > > > > > >>On Sun, Oct 02, 2005 at 01:45:13AM +0200, Hugo van der Merwe wrote: > >> > >> > >> > >>>My machine is running stable on 2.6.11, however, if I boot 2.6.12, it > >>>usually hangs/crashes within a minute after having logged in graphically > >>>(gdm, gnome), and started doing things. (Last time I was switching > >>>desktops, starting up terminals and loading web pages.) > >>> > >>> > >>>I looked over the bug-list, but didn't see anything relevant. (Late at > >>>night, I may have missed it...) What I want to know is how to best > >>>provide more info? I think I should try single processor versions, > >>>386/486 versions, try a different display driver, or work in text mode > >>>for a long time (more troublesome though), or just leave my machine on > >>>doing nothing other than maybe moving the mouse, to try and find out > >>>when it crashes/hangs and when it doesn't? > >>> > >>> > > > >Try examining the output of dmsg or /var/log/kern.log to examine > >what part of the kernel is crashing. > > > > > Unfortunately no such luck: > > Oct 1 15:26:55 vervet kernel: klogd 1.4.1#17, log source = /proc/kmsg > started. > Oct 1 15:26:55 vervet kernel: Inspecting /boot/System.map-2.6.12-1-686-smp > Oct 1 15:26:55 vervet kernel: Loaded 28143 symbols from > /boot/System.map-2.6.12-1-686-smp. > Oct 1 15:26:55 vervet kernel: Symbols match kernel version 2.6.12. > Oct 1 15:26:55 vervet kernel: No module symbols loaded - kernel modules > not enabled. > Oct 1 15:26:55 vervet kernel: Linux version 2.6.12-1-686-smp > ([EMAIL PROTECTED]) (gcc version 4.0.2 20050821 (prerelease) (Debian > 4.0.1-6)) #1 SMP Tue Sep 6 15:52:07 UTC 2005 > <SNIP> > Oct 1 15:27:23 vervet kernel: Installing knfsd (copyright (C) 1996 > [EMAIL PROTECTED]). > Oct 1 15:27:35 vervet kernel: [drm] Initialized drm 1.0.0 20040925 > Oct 1 15:27:35 vervet kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> > GSI 16 (level, low) -> IRQ 177 > Oct 1 15:27:35 vervet kernel: [drm] Initialized radeon 1.16.0 20050311 > on minor 0: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] > Oct 1 15:27:35 vervet kernel: agpgart: Found an AGP 3.0 compliant > device at 0000:00:00.0. > Oct 1 15:27:35 vervet kernel: agpgart: reserved bits set in mode > 0x1f004201. Fixed. > Oct 1 15:27:35 vervet kernel: agpgart: Device is in legacy mode, > falling back to 2.x > Oct 1 15:27:35 vervet kernel: agpgart: Putting AGP V2 device at > 0000:00:00.0 into 1x mode > Oct 1 15:27:35 vervet kernel: agpgart: Putting AGP V2 device at > 0000:01:00.0 into 1x mode > Oct 1 15:33:20 vervet kernel: klogd 1.4.1#17, log source = /proc/kmsg > started. > Oct 1 15:33:20 vervet kernel: Inspecting /boot/System.map-2.6.11-1-686-smp > Oct 1 15:33:20 vervet kernel: Loaded 27488 symbols from > /boot/System.map-2.6.11-1-686-smp. > Oct 1 15:33:20 vervet kernel: Symbols match kernel version 2.6.11. > Oct 1 15:33:20 vervet kernel: No module symbols loaded - kernel modules > not enabled. > Oct 1 15:33:20 vervet kernel: Linux version 2.6.11-1-686-smp > ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian 1:3.3.6-6)) #1 SMP Mon Jun > 20 20:18:45 MDT 2005 > > I was able to log into Gnome before it crashed, it definately lasted > more than a minute, so there is nothing in kern.log regarding the crash... > > I always love blaming hardware, but if hardware is rock-solid stable > (uh, I think so) on an older kernel... (though I suppose it can always > be that the newer kernel hits the hardware problem while the old doesn't).
What exactly happens when you experience a crash? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
