Random freezes with Kernel 2.6.37-0.dmz.x
Hmm,
just a hint in case others run in more trouble than me. I am currently experiencing random freezes (between 5 and 20 minutes after bootup) on my "old" Laptop with the 32-Bit 2.6.37-series (tested up to of the 2.6.37-0.dmz.6 version yet). No problems with the 64-Bit series of that kernel on my other boxes. Nothing to actually worry about, I can happily stay on the 32-Bit 2.6.36 series. regards Reiner Back to top |
|||||
Well, I guess you can look forward to the first stable kernel updates, 2.6.37.1, whenever that is pushed out. In the meantime, if it matters to you to run the latest, try Debian's trunk 2.6.37 kernel. It should be available in the experimental repository.
Back to top |
|||||
@damentz:
Iwill wait for the 2.6.37.1 series rep. will try newer kernels as they arrive. As I mentioned above it is really no urgent issue as I can use the 2.6.36 series without any problems. I will give notice however when this problem has disappered. thanks and regards Reiner Back to top |
|||||
Thinkpad 600e
The 2.6.37 kernel has introduced system freezes, when I try to burn a cd/dvd or have network traffic exceeding 1Mb/s or lasting more than about 5 minutes.
The freezes during network usage occurs with both of my cards, a Broadcom BCM4318 wifi card and a Realtek RTL-8139/C/C+ LAN card, both PCMCIA. These freezes did not occur with the 2.6.36 kernels. Is it possible that 2.6.37 introduced some type of I/O problem with this hardware? I'll downgrade back to 2.6.36, but I would like to know if I am done with kernel updates, beyond 2.6.36. If I can provide anyone info, let me know. Back to top |
|||||
I was using 2.6.37-zen kernel and I had the same problem.
I don't know the origin, I can burn CD/DVD without problems. The freeze, in my case, occurs always when the PC is unused (no inactive). I have compiled my kernel without support to suspend and hibernate states. And I set the ACPI Susped Type (in BIOS) to S1(POS). Perhaps the problem is the network traffic, but I think it isn't the unique factor. In my case, the freeze (as I've said) always occurs when the PC is unused but it always occurs when it downloads large amount the data, through FTP, from my server. The download speed is around 7 Mbps. But the time is much more than 5 minutes, and the PC always is unused. I'm testing now with kernel 2.6.37-0.dmz.7-liquorix-686 to discard a problem with my kernel config. If this test fails too, I'll test with the 2.6.37 Ubuntu kernel from kernel-ppa (I use Ubuntu 10.04). I'll post the result of my tests here in a few days. Back to top |
|||||
I experienced my first Liquorix freeze, today, with kernel 2.6.37-0.dmz.7-liquorix-686 / on a Ubuntu 10.10 box.
This has a "hard" lock (keyboard, mouse, display, sound, RAM, et cetera) requiring pressing the 'reset button' on my computer, to recover. I've been running Liquorix 2.6.37-0 since the initial release, and all revisions in between. The freeze was easily replicated, each time I rebooted, by going to Nautilus (2.32.0) and doing a filename search. Once I initiated a search in Nautilus, it would run for about 30 seconds - followed by a total system freeze. I tried this several times, before giving up -- fearing I would puke a drive, if I didn't quit. Otherwise, everything works fine! I assumed this was hardware related, but found this thread, and thought I should add my comment(s) as well. ;) BTW, when booting into the original Ubuntu kernel (via grub), the freeze CANNOT be reproduced... so, it's either a kernel issue, or a compatibility issue when using Nautilus under 2.6.37-0.dmz.7-liquorix-686, and/or a kernel/hardware compliance problem. As you can see, in my sig, I'm running ancient iron -- the functional equivalent of a '55 Chevrolet with a 454 cu in engine. Switching to the Liquorix 2.6.37-0 kernel, was akin to adding a turbocharger. Maybe it's just too much for it... LoL! I guess I'll quit searching via Nautilus, until 2.6.37-1 arrives. Back to top |
|||||
Tonight my PC freezes with Liquorix kernel too.
The info of my PC: :: Code :: Hardware Information
Motherboard name: X48T-DQ6 Motherboard vendor: Gigabyte Technology Co., Ltd. BIOS vendor: Award Software International, Inc. BIOS version: F5 BIOS release date: 07/21/2008 CPU 1 name: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz CPU 1 level 1 cache size: 32K Data cache. 32K Instruction cache. CPU 1 level 2 cache size: 6144K Unified cache. CPU 1 Mips: 5666.53 CPU 2 name: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz CPU 2 level 1 cache size: 32K Data cache. 32K Instruction cache. CPU 2 level 2 cache size: 6144K Unified cache. CPU 2 Mips: 5665.82 CPU 3 name: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz CPU 3 level 1 cache size: 32K Data cache. 32K Instruction cache. CPU 3 level 2 cache size: 6144K Unified cache. CPU 3 Mips: 5665.82 CPU 4 name: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz CPU 4 level 1 cache size: 32K Data cache. 32K Instruction cache. CPU 4 level 2 cache size: 6144K Unified cache. CPU 4 Mips: 5665.71 Total memory: 3.1 GB Total swap: 2096 MBytes Ethernet card: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Ethernet card: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Linux Information Kernel version: 2.6.37-0.dmz.7-liquorix-686 Kernel arch: i686 Default shell: /bin/bash X server version: X.Org X Server 1.7.6 OpenGL direct rendering: Yes OpenGL vendor: NVIDIA Corporation OpenGL renderer: GeForce 9800 GT/PCI/SSE2 OpenGL version: 3.3.0 NVIDIA 260.19.36 GCC version: 4.4.3 GTK version: 2.20.1 Ubuntu version: 10.04 GNOME version: 2.30.2 It's a hard lock too. In logs there is nothing. The log stops in freeze moment without any weird message. I'll test now with kernel of kernel-PPA. Back to top |
|||||
|
|||||
Can someone try the new 2.6.37-1.dmz.1 kernel? I removed some bits that might be causing problems. Also, there were _a lot_ of fixes for memory management in 2.6.37.1. Some of them might apply to you.
Back to top |
|||||
|
|||||
All times are GMT - 8 Hours
|