similar to: Re: WINE & 2.6.32 Kernels

Displaying 20 results from an estimated 40000 matches similar to: "Re: WINE & 2.6.32 Kernels"

2008 Mar 17
1
hifn(4) causing system lockup
Hi all, can someone comment on the state of the hifn(4) driver? I've recently upgraded my 6.2-STABLE workstation to RELENG_7, and I'm now experiencing system lockups that seem to be caused by the hifn(4) driver. I've got a Soekris vpn1401 card to help with GELI disk en- cryption. Reading from a GELI volume is causing the system to freeze completely, which does not happen if
2013 Mar 04
5
Lockups with kernel-2.6.32-358.0.1.el6.i686
I updated my home server with the 6.4 CR packages, and I've experienced 3 or 4 hard lockups since. The server is a fanless VIA C7 "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, but doesn't currently have an IP
2015 Dec 24
0
[RFC PATCH v2 0/7] stabilize kepler reclocking
Hello, first of all, I'm new to this list, so please beer with me. On the other hand, I'm a graduate computer systems engineer with experience in Linux kernel code, so I can hopefully provide useful input/assistance on this topic. I'm replying because I tried your patches on my setup in the hope they'd fix my lockups. Unfortunately they didn't, so I'm offering debug
2005 Nov 11
7
Fedora Core 4 system lockup with wine 200506.. - 0.9.1
System specs: Fedora Core 4 2.6.13-1.1532_FC4smp ATI Radeon 9200 SE P4 2.4Ghz (hyperthreading) xorg 6.8.2 Aureal Semiconductor Vortex 2 sound card Intel 82801EB chipset wine-20050524 FC3 rpm works just fine on my FC4 system. But any versions after that lockup my system when running wine. For the 200506 - 200510 versions of wine I have compiled them from scratch so I assumed it was something
2004 Oct 01
1
Solution to my Grandstream lockups
Like many others on this list, I had been experiencing periodic lockups with my Grandstream products (Handytone 286 ATA & BudgeTone 101). The lockups consisted of seemingly dead devices, no dialtone or response, until I power cycled via software or hardware. The workaround had been to reboot the device every 30 minutes with a cron job. I contacted Grandstream and although they didn't
2006 Apr 03
0
Lockups after Asterisk upgrade
Hi We've recently updated our Asterisk 1.0.x installation to 1.2.4. Since this upgrade we're experiencing sporadic lockups of our Linux server. By lockup I mean no response from network-traffic or keyboard-input. However, the kernel seems to be running as it responds to SysRq, and NMIs. If we terminate all processes using "SysRq + E" the machine instantly gets responsive
2010 Sep 06
1
Help debugging lockup when running wine
Hey all, I'm running Ubuntu 10.04 with Wine 1.1.42 (distributed through the Ubuntu package manager), and I'm getting complete lockups when running SimCity 4. This also happened before when running WoW, but I switched games so did not completely debug that one. So anyway, basically after playing for 20-60 minutes I get complete lockups, only thing that happens is blinking caps lock
2014 Jul 23
2
[PATCH 09/17] drm/radeon: use common fence implementation for fences
Am 23.07.2014 09:06, schrieb Maarten Lankhorst: > op 23-07-14 08:52, Christian K?nig schreef: >> Am 23.07.2014 08:40, schrieb Maarten Lankhorst: >>> op 22-07-14 17:59, Christian K?nig schreef: >>>> Am 22.07.2014 17:42, schrieb Daniel Vetter: >>>>> On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig >>>>> <christian.koenig at amd.com>
2014 Jun 19
1
compiling centos 6.5 linux-2.6.32-431.el6-kernel
Dear all, I have compiled the linux-2.6.32-431.el6-kernel with the following steps 1. Make mproper 2. Make menuconfig 3. Make 4. Make modules 5. Make modules_install The compilation is successful but there is a huge change in the size of the .ko generated compared to original .ko from the rpm. Please suggest the steps to compile the centos
2010 Jul 28
2
Ghostcast random freeze.
Greetings again, I am experiencing a lockup when ghost casting about 1 out of 5 client machines locks up. I don't recall if I was having this issue when I was using 3com pxe menus or not. I was wondering if the issue I am seeing could be caused by pxelinux since it basically is loading a Linux kernel then booting a MSDos.imz file. I cannot find any errors from the ghostcast side or the
2008 Oct 21
0
Lockup problem, watchdog, other ways to debug?
Hi, I have been trying to figure out why my Supermicro X7DWA-N with dual Xeon E5420''s locks up occasionally when running Xen, I''ve tried 3.2.1 and 3.3 with the Xensource 2.6.18 kernel, with gentoo 2.6.21, and 2.6.25 and 2.6.27 kernels patched with suse xen patches, every single combination suffers from occasional lockups :(, I am reasonably confident that the hardware is ok
2014 Sep 17
10
[Bug 83992] New: [NVE0][NVF1] regression, linux 3.17 causes gpu lockups
https://bugs.freedesktop.org/show_bug.cgi?id=83992 Priority: medium Bug ID: 83992 Assignee: nouveau at lists.freedesktop.org Summary: [NVE0][NVF1] regression, linux 3.17 causes gpu lockups QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux (All) Reporter:
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Hey, op 04-08-14 13:57, Christian K?nig schreef: > Am 04.08.2014 um 10:55 schrieb Maarten Lankhorst: >> op 04-08-14 10:36, Christian K?nig schreef: >>> Hi Maarten, >>> >>> Sorry for the delay. I've got way to much todo recently. >>> >>> Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst: >>>> On 01-08-14 18:35, Christian K?nig
2010 Mar 18
4
[Bug 27153] New: [NV18] Frequent lockups during graphical activities
http://bugs.freedesktop.org/show_bug.cgi?id=27153 Summary: [NV18] Frequent lockups during graphical activities Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2008 Jul 03
2
Xorg "intel" driver on 965Q lockup?
Hi Folks, anyone out there successful in using the new xorg "intel" driver module on a 965Q-based motherboard with CentOS 5.2? The old "i810" and "vesa" work fine, I am looking for anyone else with experience with the new "intel" video driver in 5.2. The long of it: I have a customer's Dell Optiplex 745 (Core2 Duo 6300, 965Q chipset with integrated
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Hi Maarten, Sorry for the delay. I've got way to much todo recently. Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst: > > On 01-08-14 18:35, Christian K?nig wrote: >> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst: >>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> >>> --- >>> V1 had a nasty bug breaking gpu lockup
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
op 04-08-14 10:36, Christian K?nig schreef: > Hi Maarten, > > Sorry for the delay. I've got way to much todo recently. > > Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst: >> >> On 01-08-14 18:35, Christian K?nig wrote: >>> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst: >>>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at
2012 Apr 20
1
[PATCH v2 0/2] fix "perf top" soft lockups under Xen
v2: - fix compile issues if no CONFIG_SMP, Konrad Rzeszutek Wilk - move inc_irq_stat after irq_work_run These 2 patches fixed the "perf top" soft lockups under Xen reported by Steven at: https://lkml.org/lkml/2012/2/9/506 Both Steven and I tested it and "perf top" works well now. The soft lockup code path is: __irq_work_queue arch_irq_work_raise
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Am 04.08.2014 um 10:55 schrieb Maarten Lankhorst: > op 04-08-14 10:36, Christian K?nig schreef: >> Hi Maarten, >> >> Sorry for the delay. I've got way to much todo recently. >> >> Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst: >>> On 01-08-14 18:35, Christian K?nig wrote: >>>> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
> It'a pain to deal with gpu reset. Yeah, well that's nothing new. > I've now tried other solutions but that would mean reverting to the old style during gpu lockup recovery, and only running the delayed work when !lockup. > But this meant that the timeout was useless to add. I think the cleanest is keeping the v2 patch, because potentially any waiting code can be called