kernel

things i want to read:

configuring

http://swsusp.sourceforge.net/Software-suspend-4.html

nfs:

fam

swsusp

see notebook

FS:

pwc

mtrr on X/kernel/vesafb

input

http://linuxconsole.sf.net

Docs

• http://www.tldp.org/LDP/tlk/tlk.html

2.4 version:

• http://www.xml.com/ldd/chapter/book/ch05.html (Rubini)

2.6 only pdfs? api changes: http://lwn.net/Articles/2.6-kernel-api/

Sample chapters: Robert Love The Linux Process Scheduler

slab allocator

memory barrier and Linus explains

i need to make a new system call:

Linux 2.xx Syscalls Intro

kernel side

Files which i changed: /linux/13/usr/src/linux-2.6.11.6/kernel/time.c /linux/13/usr/src/linux-2.6.11.6/include/linux/time.h /linux/13/usr/src/linux-2.6.11.6/arch/i386/kernel/entry.S /linux/13/usr/src/linux-2.6.11.6/drivers/input/evdev.c

user side:

patches

linux kernel patch submission format

my posts:

http://lkml.org/lkml/2005/6/19/13 http://lkml.org/lkml/2005/10/6/92 http://lkml.org/lkml/fancy/2005/12/27/141

Git

http://linux.yyz.us/git-howto.html

• man page http://www.kernel.org/pub/software/scm/git/docs/git.html
• Darcs-git http://marc.theaimsgroup.com/?l=darcs-users&m=111565618815632&w=2

profiler

http://lkml.org/lkml/2005/9/17/122

aio

apic:

Mar 1 03:43:06 linux11 APIC error on CPU0: 80(80) Mar 1 03:44:08 linux11 APIC error on CPU0: 80(80) Mar 1 03:45:23 linux11 APIC error on CPU0: 80(80) Mar 1 03:45:39 linux11 APIC error on CPU0: 80(80)

2.6.15

http://lkml.org/faq/lkmlfaq-13.html

1. Why does my kernel report lots of "APIC error" messages?

(REG, contributed by Mark Hahn) You may get messages like: APIC error on CPU1: 00(08).

APIC is the hardware that ia32 systems use to communicate between CPUs to handle low-level events like interrupts and TLB flushes. APIC messages are checksummed, and automatically retried when they fail. This message indicates that a transaction failed; it's only a problem when there are many of them. The APIC checksum is quite weak, so even a few failures is a cause for concern, since it implies that some corruption has likely gone undetected.

Assuming you're not forcing your motherboard to use an invalid system clock (i.e. AGP other than 66 MHz), this is strictly a physical design flaw in your motherboard. The Abit BP6 is notorious for this flaw, but it's not unheard of on other boards (such as the Gigabyte BXD), and it's possible on any board that uses APICs.

You can force the kernel not to use APIC like this with the "noapic" kernel option. This also forces CPU0 to handle all interrupts.

Corefiles

Bluetooth