Oops in stock 2.2.18

Can anybody shed some light on this? Thanks, --- cut here --- Unable to handle kernel paging request at virtual address e6d94ba1 current->tss.cr3 = 07211000, %cr3 = 07211000 *pde = Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206

[2.2.18] Oops in schedule/reschedule

[1.] One line summary of the problem: Oops in schedule [2.] Full description of the problem/report: I am unsure of the actual cause. My machine is running Postfix and INN and both were killed when the oops occurred. These are the only two tasks that appear to have died. [3.] Keywords (i.e.,

Oops in 2.2.19pre7

Unable to handle kernel paging request at virtual address 813de1c0 current->tss.cr3 = 015fa000, %cr3 = 015fa000 *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010283 eax: c09ef0e0 ebx: c7fff740 ecx: 000f edx: c09ef0e0 es

Re: Status of ALi MAGiK 1 support in 2.4.?

On Mon, May 28, 2001 at 05:57:12PM +0200, Axel Thimm wrote: > What is the status of the support for this chipset, found for example in an > ASUS A7A266? Judging from > http://www.acerlabs.com/eng/support/faqlnx.htm > one gets the impression that ALi is respectfully treating the Linux

Re: Status of ALi MAGiK 1 support in 2.4.?

On Tue, May 29, 2001 at 05:18:39AM +0600, Bobby D. Bryant wrote: > sailing ever since. The only problems that I'm are ware of are a > (maybe) DMA problem and a (maybe) SMBus problem, per below. Right now I noticed the Win32 benchmark/test application Sandra mentioned an SMBus problem with the A

IRQ problems w/VIA Apollo VP2/97 & NCR 53c875

Summary: IRQ conflict on VIA Apollo VP2/97-based motherboard between dual controllers on NCR 53c875 (Diamond Fireport 40). Kernel version is 2.4.5-ac9. --- cut here --- 00:00.0 Host bridge: VIA Technologies, Inc. VT82C595/97 [Apollo VP2/97] (rev 04) Flags: bus master, 66Mhz, medium devs