psmouse.c, throwing 3 bytes away

psmouse.c, throwing 3 bytes away

[Walt Nelson]

My mouse has been acting wired occationally, not all the time. I receive the 
following error in the syslog. This has been happening since 2.6.2-RC3. I am 
currently using 2.6.2. Are these related?

Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
lost synchronization, throwing 3 bytes away.

The following occurs when starting KDE/X.
Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set 2, 
code 0x7a on isa0060/serio0).
Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.
Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set 2, 
code 0x7a on isa0060/serio0).
Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
access hardware directly.

Thanks in advance

Walt

Re: psmouse.c, throwing 3 bytes away

[Claudio Martins]

On Thursday 05 February 2004 02:20, Walt Nelson wrote:
> My mouse has been acting wired occationally, not all the time. I receive
> the following error in the syslog. This has been happening since 2.6.2-RC3.
> I am currently using 2.6.2. Are these related?
>
> Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at
> isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
>
> The following occurs when starting KDE/X.
> Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> 2, code 0x7a on isa0060/serio0).
> Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> access hardware directly.
> Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> 2, code 0x7a on isa0060/serio0).
> Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> access hardware directly.
>


  I saw the same here yesterday, using a logitech wheel mouse:

Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
lost synchronization, throwing 2 bytes away.

  Before this happened the mouse in X just went nuts with random clicks in 
many windows, but after that it's been ok up to now.

  FYI the mouse is detected as: 

Feb  4 08:57:42 vega kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb  4 08:57:42 vega kernel: input: PS2++ Logitech Wheel Mouse on 
isa0060/serio1

  The motherboard is an Intel 440BX2 with a PII-350 running kernel 2.6.2.

Thanks 

Claudio

Re: psmouse.c, throwing 3 bytes away

[Mike Houston]

On Wed, 4 Feb 2004 18:20:39 -0800
Walt Nelson <wnelsonjr@comcast.net> wrote:

> My mouse has been acting wired occationally, not all the time. I receive the 
> following error in the syslog. This has been happening since 2.6.2-RC3. I am 
> currently using 2.6.2. Are these related?
> 
> Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> lost synchronization, throwing 3 bytes away.

Hello everyone

I too have started to experience this problem, starting with 2.6.2-rc3. The symptom is, the mouse goes crazy... erratic, and every movement of the mouse clicks on things. Menus fly... programs open. It lasts for a few seconds. If I stop moving the mouse for a few and then click somewhere, it comes back to normal. This message is seen in the output of dmesg afterwards.

psmouse.c: MX Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

It happened 4 times in one day, so I went back to 2.6.1 and it did not happen again. Today, I did 2.6.2 and have been running it all day. It didn't happen until just a few minutes ago.

I only have one mouse configuration section in my XF86Config file (I did some searching and saw this problem can be caused by having duplicate sections)

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "IMPS/2"
    Option "Device"      "/dev/psaux"
    Option "ZAxisMapping"  "4 5"
    Option "Buttons"      "5"
    Option "Resolution"   "500"

Ok, I know you folks don't like attachments, so I'll just paste my config and dmesg output to this email should anyone care to peruse it.

This is a pentium4 system, with an i845 based Gigabyte motherboard. Nothing fancy or weird in this box. The mouse is a logitech MX500 optical wheel mouse.

--------------------------------------------------------------
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
# CONFIG_STANDALONE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
CONFIG_EMBEDDED=y
# CONFIG_KALLSYMS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_IOSCHED_NOOP is not set
CONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_FAN is not set
CONFIG_ACPI_PROCESSOR=y
# CONFIG_ACPI_THERMAL is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Device Drivers
#

#
# Generic Driver Options
#

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_PACKET is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
CONFIG_SUNDANCE=y
CONFIG_SUNDANCE_MMIO=y
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
# CONFIG_LOGO is not set

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
CONFIG_SOUND_ES1371=m
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_AD1980 is not set

#
# USB support
#
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=m
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=m
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_NEC98_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=m
CONFIG_X86_BIOS_REBOOT=y
------------------------------------------------------------------

The top part of dmesg is truncated, because of all the noisy atkbd.c: unknown key released messages, of which there are now double because of the "this is an xfree86 bug".

However, the kernel is 2.6.2 and the compiler used was gcc 3.3.2

bash-2.05b$ dmesg
served)
 BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
 BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
 BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f4a90
hm, page 000f4000 reserved twice.
hm, page 000f5000 reserved twice.
hm, page 000f0000 reserved twice.
hm, page 000f1000 reserved twice.
On node 0 totalpages: 262128
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 225280 pages, LIFO batch:16
  HighMem zone: 32752 pages, LIFO batch:7
DMI 2.3 present.
ACPI: RSDP (v000 GBT                                       ) @ 0x000f6570
ACPI: RSDT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff3000
ACPI: FADT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff3040
ACPI: MADT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff6740
ACPI: DSDT (v001 GBT    AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI BALANCE SET
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Building zonelist for node : 0
Kernel command line: BOOT_IMAGE=2.6.2 ro root=302 video=radeonfb:1024x768-8@76
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2019.907 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 1035396k/1048512k available (1124k kernel code, 12176k reserved, 319k data, 124k init, 131008k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3981.31 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 3febfbff 00000000 00000000 00000000
CPU:     After vendor identify, caps: 3febfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU:     After all inits, caps: 3febfbff 00000000 00000000 00000080
CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2018.0964 MHz.
..... host bus clock speed is 100.0948 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf9d70, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040116
IOAPIC[0]: Set PCI routing entry (2-9 -> 0x71 -> IRQ 9 Mode:1 Active:0)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
SCSI subsystem initialized
IOAPIC[0]: Set PCI routing entry (2-16 -> 0xa9 -> IRQ 16 Mode:1 Active:1)
00:00:1e[A] -> 2-16 -> IRQ 16
IOAPIC[0]: Set PCI routing entry (2-17 -> 0xb1 -> IRQ 17 Mode:1 Active:1)
00:00:1e[B] -> 2-17 -> IRQ 17
IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb9 -> IRQ 18 Mode:1 Active:1)
00:00:1e[C] -> 2-18 -> IRQ 18
IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19 Mode:1 Active:1)
00:00:1e[D] -> 2-19 -> IRQ 19
Pin 2-16 already programmed
Pin 2-17 already programmed
IOAPIC[0]: Set PCI routing entry (2-23 -> 0xc9 -> IRQ 23 Mode:1 Active:1)
00:00:1f[C] -> 2-23 -> IRQ 23
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
IOAPIC[0]: Set PCI routing entry (2-20 -> 0xd1 -> IRQ 20 Mode:1 Active:1)
00:02:08[A] -> 2-20 -> IRQ 20
IOAPIC[0]: Set PCI routing entry (2-21 -> 0xd9 -> IRQ 21 Mode:1 Active:1)
00:02:08[B] -> 2-21 -> IRQ 21
IOAPIC[0]: Set PCI routing entry (2-22 -> 0xe1 -> IRQ 22 Mode:1 Active:1)
00:02:08[C] -> 2-22 -> IRQ 22
Pin 2-23 already programmed
Pin 2-18 already programmed
Pin 2-21 already programmed
Pin 2-22 already programmed
Pin 2-16 already programmed
Pin 2-21 already programmed
Pin 2-22 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
Pin 2-22 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
Pin 2-21 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
Pin 2-21 already programmed
Pin 2-22 already programmed
Pin 2-18 already programmed
Pin 2-21 already programmed
Pin 2-22 already programmed
Pin 2-16 already programmed
Pin 2-21 already programmed
Pin 2-22 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00178020
.......     : max redirection entries: 0017
.......     : PRQ implemented: 1
.......     : IO APIC version: 0020
.... register #02: 00000000
.......     : arbitration: 00
.... register #03: 00000001
.......     : Boot DT    : 1
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 000 00  1    0    0   0   0    0    0    00
 01 001 01  0    0    0   0   0    1    1    39
 02 001 01  0    0    0   0   0    1    1    31
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 001 01  0    0    0   0   0    1    1    51
 06 001 01  0    0    0   0   0    1    1    59
 07 001 01  0    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  0    1    0   0   0    1    1    71
 0a 001 01  0    0    0   0   0    1    1    79
 0b 001 01  0    0    0   0   0    1    1    81
 0c 001 01  0    0    0   0   0    1    1    89
 0d 001 01  0    0    0   0   0    1    1    91
 0e 001 01  0    0    0   0   0    1    1    99
 0f 001 01  0    0    0   0   0    1    1    A1
 10 001 01  1    1    0   1   0    1    1    A9
 11 001 01  1    1    0   1   0    1    1    B1
 12 001 01  1    1    0   1   0    1    1    B9
 13 001 01  1    1    0   1   0    1    1    C1
 14 001 01  1    1    0   1   0    1    1    D1
 15 001 01  1    1    0   1   0    1    1    D9
 16 001 01  1    1    0   1   0    1    1    E1
 17 001 01  1    1    0   1   0    1    1    C9
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9-> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ18 -> 0:18
IRQ19 -> 0:19
IRQ20 -> 0:20
IRQ21 -> 0:21
IRQ22 -> 0:22
IRQ23 -> 0:23
.................................... done.
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=12, xclk=23000 defaults
radeonfb: probed DDR SGRAM 65536k videoram
radeon_get_moninfo: bios 4 scratch = 2000002
radeonfb: ATI Radeon 7500 QW DDR SGRAM 64 MB
radeonfb: DVI port no monitor connected
radeonfb: CRT port CRT monitor connected
radeonfb_pci_register END
highmem bounce pool size: 64 pages
ACPI: Processor [CPU0] (supports C1, 2 throttling states)
hStart = 1032, hEnd = 1152, hTotal = 1360
vStart = 784, vEnd = 787, vTotal = 823
h_total_disp = 0x7f00a9    hsync_strt_wid = 0x8f0412
v_total_disp = 0x2ff0336           vsync_strt_wid = 0x83030f
post div = 0x2
fb_div = 0x4c
ppll_div_3 = 0x1004c
ron = 1184, roff = 19292
vclk_freq = 8550, per = 689
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
sundance.c:v1.01+LK1.09a 10-Jul-2003  Written by Donald Becker
  http://www.scyld.com/network/sundance.html
eth0: D-Link DFE-530TXS FAST Ethernet Adapter at 0xf8807000, 00:05:5d:ff:6b:bb, IRQ 21.
eth0: MII PHY found at address 1, status 0x782d advertising 01e1.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 5
ICH2: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:DMA
hda: Maxtor 6E040L0, ATA DISK drive
hdb: Maxtor 6E040L0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: HL-DT-ST GCE-8481B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 >
hdb: max request size: 128KiB
hdb: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hdb: hdb1 hdb2
Console: switching to colour frame buffer device 128x48
mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
input: PS2++ Logitech MX Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 124k freed
Adding 1052216k swap on /dev/hda5.  Priority:-1 extents:1
eth0: Link changed: 100Mbps, full duplex
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i845 Chipset.
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: AGP aperture is 128M @ 0xd0000000
es1371: version v0.32 time 12:10:26 Feb  4 2004
es1371: found chip, vendor id 0x1274 device id 0x5880 revision 0x02
es1371: found es1371 rev 2 at io 0xa400 irq 22 joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x8384:0x7608 (SigmaTel STAC9708)
[drm] Initialized radeon 1.9.0 20020828 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode

Re: psmouse.c, throwing 3 bytes away

[Isaac Claymore]

On Thu, Feb 05, 2004 at 04:54:44AM +0000, Claudio Martins wrote:
> 
> On Thursday 05 February 2004 02:20, Walt Nelson wrote:
> > My mouse has been acting wired occationally, not all the time. I receive
> > the following error in the syslog. This has been happening since 2.6.2-RC3.
> > I am currently using 2.6.2. Are these related?
> >
> > Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at
> > isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> >
> > The following occurs when starting KDE/X.
> > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > 2, code 0x7a on isa0060/serio0).
> > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > access hardware directly.
> > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > 2, code 0x7a on isa0060/serio0).
> > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > access hardware directly.
> >
> 
> 
>   I saw the same here yesterday, using a logitech wheel mouse:
> 
> Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> lost synchronization, throwing 2 bytes away.
> 
>   Before this happened the mouse in X just went nuts with random clicks in 
> many windows, but after that it's been ok up to now.
> 
I've been suffering this same problem ever since upgrade to 2.6 kernel.

FYI, here is an article giving some possible solutions to this, but I
failed to fix my mouse problem by any method it suggests:

http://kerneltrap.org/node/view/2199


>   FYI the mouse is detected as: 
> 
> Feb  4 08:57:42 vega kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> Feb  4 08:57:42 vega kernel: input: PS2++ Logitech Wheel Mouse on 
> isa0060/serio1
> 
>   The motherboard is an Intel 440BX2 with a PII-350 running kernel 2.6.2.
> 
> Thanks 
> 
> Claudio
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

Regards, Isaac
()  ascii ribbon campaign - against html e-mail
/\                        - against microsoft attachments

Re: psmouse.c, throwing 3 bytes away

[Michael Buesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I saw the same messages since 2.6.2-rc2 (I didn't try any other 2.6.2
prerelease). 2.6.1 didn't do that.

On Thursday 05 February 2004 05:54, you wrote:
> 
> On Thursday 05 February 2004 02:20, Walt Nelson wrote:
> > My mouse has been acting wired occationally, not all the time. I receive
> > the following error in the syslog. This has been happening since 2.6.2-RC3.
> > I am currently using 2.6.2. Are these related?
> >
> > Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at
> > isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> >
> > The following occurs when starting KDE/X.
> > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > 2, code 0x7a on isa0060/serio0).
> > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > access hardware directly.
> > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > 2, code 0x7a on isa0060/serio0).
> > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > access hardware directly.
> >
> 
> 
>   I saw the same here yesterday, using a logitech wheel mouse:
> 
> Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> lost synchronization, throwing 2 bytes away.
> 
>   Before this happened the mouse in X just went nuts with random clicks in 
> many windows, but after that it's been ok up to now.
> 
>   FYI the mouse is detected as: 
> 
> Feb  4 08:57:42 vega kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> Feb  4 08:57:42 vega kernel: input: PS2++ Logitech Wheel Mouse on 
> isa0060/serio1
> 
>   The motherboard is an Intel 440BX2 with a PII-350 running kernel 2.6.2.

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAIke+FGK1OIvVOP4RAsB6AKCVznga6Q1Uo7nfSIn1LfzpYgYlFACeJYgv
8BeJSlNeI2vFlQVegtMLiyE=
=wdjy
-----END PGP SIGNATURE-----

Re: psmouse.c, throwing 3 bytes away

[johann lombardi]

> Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at
> isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

I had the same issue with 2.6.1. Always under heavy disk activity. 
Turning on DMA support for my hard drive sovled the problem.

However, I've recently upgraded to 2.6.2-rc2 and the problem has reappeared.
This time, it is not linked to disk activity (DMA support is now enabled). 
http://kerneltrap.org/node/view/2199 does not solve the problem.
Still investigating ...

Greetings,
Johann

ps: my kernel is not tainted.

Re: psmouse.c, throwing 3 bytes away

[Murilo Pontes]

I have same problems since of 2.6.0, now I running 2.6.2 stock kernel
I run XFree86-4.3.0 and still with problems, anyone try XFree86-4.4.0 devel snapshots???

I try kernel with/without  preempty/acpi/apic make all possibilities, 
then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary 
and source incompatibilites,  


Thanks in advance

Re: psmouse.c, throwing 3 bytes away

[Murilo Pontes]

My motherboard is k7n2-delta-l from MSI, and my mouse is Logitech PS/2 Optical Mouse Whell,
512mb of ram, no swap partitions

Well, always which compiling large sources like kde-3.2 and using XFree86-4.3.0 in parallel,
this bug is appears several times. Maybe not related with disks DMA/apic/acpi/preempt/agp issues,

Near of isolate bug is on VM system(stress it, like compiling kde-3.2 with no swap partitions) or 
I2C/ACPI Thermal zone/ACPI fans. Both have related with input system?

With lower load I newer take is bug. Anyone take? 


Em Qui 05 Fev 2004 20:38, Vojtech Pavlik escreveu:
> On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
> > I have same problems since of 2.6.0, now I running 2.6.2 stock kernel
> > I run XFree86-4.3.0 and still with problems, anyone try XFree86-4.4.0 devel snapshots???
> > 
> > I try kernel with/without  preempty/acpi/apic make all possibilities, 
> > then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
> > of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary 
> > and source incompatibilites,  
> 
> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.
> 

Re: psmouse.c, throwing 3 bytes away

[Murilo Pontes]

Em Qui 05 Fev 2004 20:59, você escreveu:
> The exception seems to be coming from
> linux-2.6.2/drivers/input/mouse/psmouse-base.c, specifically from
> 
> if (psmouse->state == PSMOUSE_ACTIVATED &&
>             psmouse->pktcnt && time_after(jiffies, psmouse->last +
> HZ/2)) {
>                 printk(KERN_WARNING "psmouse.c: %s at %s lost
> synchronization, throwing %d bytes away.\n",
>                        psmouse->name, psmouse->phys, psmouse->pktcnt);
>                 psmouse->pktcnt = 0;
>         }
> 
> 
> where (for me) HZ is 1804768000, and therefore HZ/2 is 902384000,  
> psmouse->pktcnt is 3, and (I assume) PSMOUSE_ACTIVATED is non-0 after
> boot.  I assume that pktcnt is fed by interrupt, and the problem then is
> that psmouse->last + HZ/2 blows past the jiffies value, causing the
> warning message to be issued.  When mouse service finally comes back,
> pktcnt is non-zero (and possibly whatever the maximum is that it will
> hold), and when it flushes, the mouse pointer goes nuts for a second. 
> The real problem then, is why does the sum of ps->last + HZ/2 grow to
> beyond the size of jiffies (or what is delaying the mouse service)?
> 
> This is just a rough guesstimate of what is going on, but seems to fit
> the facts.   Cheers!
> 
> Bob
Always in heavy load(like c++ compiling, high volume of VM operations),
kernel jiffies are more large or short delay....

Bug is solved?
I am open to receive patchs for test! 
Please send when avaliable! 

Thanks

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
> I have same problems since of 2.6.0, now I running 2.6.2 stock kernel
> I run XFree86-4.3.0 and still with problems, anyone try XFree86-4.4.0 devel snapshots???
> 
> I try kernel with/without  preempty/acpi/apic make all possibilities, 
> then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
> of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary 
> and source incompatibilites,  

Hey, guys, could you possibly try to figure out what your machines have
in common? I've switched all my computers to PS/2 mice so that I have a
bigger chance to reproduce the problem, but it is not happening on any
of them.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c, throwing 3 bytes away

[Michael Buesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 05 February 2004 21:38, you wrote:
> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.

Hm, that's a good question. :)
As I said I had these error messages on 2.6.2-rc2, but now
on 2.6.2 I don't have them anymore. (at least until yet).
But could also have something to do with the switch from
KDE-cvsHEAD-december2003 to KDE-3.2. I don't know.

I'm compiling software and accessing the disk heavily today
(and yesterday) but I can't see the message anymore.
That's strange!

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAIrBzFGK1OIvVOP4RAs1SAKCHWBStoIZ119Zq7wAomnYC2R1ukACePqTH
o0HPu/uLewEvpUD52TzbWqw=
=RG51
-----END PGP SIGNATURE-----

Re: psmouse.c, throwing 3 bytes away

[Mike Houston]

On Thu, 5 Feb 2004 21:38:40 +0100
Vojtech Pavlik <vojtech@suse.cz> wrote:

> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.

Hello Vojtech and everyone following this thread.

The problem is quite intermittent, it hasn't happened to me yet today. (machine has been up about 6 hours). The problem has never happened to me, with 2.6.1 or any previous kernel.

I'm not sure that it's load related, each time it has seemed to happen to me, while in a menu somewhere. (not specific apps either, and it has happened both in KDE and XFCE)

In trying to nail down something in common, I'll start with XFree86.

XFree86 Version 4.3.99.902 (4.4.0 RC 2)
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.0 i686 [ELF] 
Current Operating System: Linux getstuffed 2.6.2 #1 Wed Feb 4 12:11:41 EST 2004 i686
Build Date: 21 December 2003
Changelog Date: 19 December 2003

Kernel headers were mentioned by Murilo in the previous email. On my Slackware system, I have /usr/include/linux and asm as links pointing to the appropriate places in the 2.4.23 source tree. (I compiled Glibc 2.3.2 with these in place)

I posted my 2.6.2 config and dmesg in a previous email, so I won't bore the list again with it. I put them up on my personal web space though, in case anyone wants to look at them.

http://www.bitbenderforums.com/~grogan/files/config-2.6.2.txt
http://www.bitbenderforums.com/~grogan/files/dmesg.txt

This is a pentium4 system. i845 chipset (Gigabyte board). Logitech MX500 optical wheel mouse (not cordless), using the usb to ps/2 adapter that came with it. Radeon 7500 AGP video card.

I am using ACPI and IO-APIC. Next time my mouse acts up, I will consider trying 2.6.2 without ACPI and IO-APIC (though I'd hate to lose that functionality). Trouble is it might take a long time for the mouse glitch to occur.

That's about all I can think of for now, holler if you wish to ask something more.

I am also willing to try any patches or configuration options to help track this down. I'll tell you right now, I'm not much of a coder but if I'm told what to do, I can do it.

Thanks,
Mike Houston (a.k.a. Grogan)

RE:psmouse.c, throwing 3 bytes away

[Walt Nelson]

XFree86 Version 4.3.99.16
Release Date: 20 November 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-gentoo-r8 i686 [ELF]
Current Operating System: Linux gumby 2.6.2-bk1 #1 SMP Thu Feb 5 09:47:35 PST 
2004 i686
Build Date: 03 December 2003
Changelog Date: 02 December 2003

MSI 865PE LS
512mb Ram
w/o ACPI
IO-APIC on
Standard PS/2 mouse and Keyboard
Nvidia Geforce 4 440FX

Kernel versions 2.6.1-rc3 to 2.6.2. I have been using a tainted kernel with 
the NVIDIA drivers since 2.5.75 up until now. I am currently using 2.6.2-bk1 
right now and have not notice it yet. 
I have only been at my computer now for 15 minutes, so not enough time yet to 
happen. If there is any other info that you may need let me know.

Thank in advance

Walt

Re: psmouse.c, throwing 3 bytes away

[Pete Clements]

Quoting Vojtech Pavlik
  > 
  > Hey, guys, could you possibly try to figure out what your machines have
  > in common? I've switched all my computers to PS/2 mice so that I have a
  > bigger chance to reproduce the problem, but it is not happening on any
  > of them.
  > 
  > -- 
  > Vojtech Pavlik
  > SuSE Labs, SuSE CR
  > -
I'll join in on this. Have two systems that have this problem.  Do not
recall when first observed, believe post 2.6.0 bk's/rc's.  Occurance is
totally random, only common thread is the mouse lost sync message. Running
Debian 3.0r2, one system SMP, both bare bones X.  Config for the smp system 
below (2.6.2-bk1 have not actually seen problem on this kernel yet).

-- 
Pete Clements 

CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

CONFIG_EXPERIMENTAL=y
CONFIG_STANDALONE=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y

CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y

CONFIG_X86_PC=y
CONFIG_MPENTIUMIII=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_HAVE_DEC_LOCK=y


CONFIG_ACPI_BOOT=y


CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y

CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y




CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y


CONFIG_BLK_DEV_FD=y

CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDE_TASKFILE_IO=y

CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_IDE_CHIPSETS=y

CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y

CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=y

CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y

CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_SCSI_QLA2XXX_CONFIG=y






CONFIG_NET=y

CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_INET=y

CONFIG_IPV6=m
CONFIG_NETFILTER=y

CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m


CONFIG_IPV6_SCTP__=m


CONFIG_NETDEVICES=y


CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL3=y



CONFIG_PPP=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m









CONFIG_INPUT=y

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768

CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y

CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_NR_UARTS=4

CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y



CONFIG_RTC=y






CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y




CONFIG_EXT2_FS=y

CONFIG_ISO9660_FS=y

CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y

CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_DEVPTS_FS=y
CONFIG_RAMFS=y


CONFIG_NFS_FS=y
CONFIG_NFSD=y
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"

CONFIG_MSDOS_PARTITION=y

CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y


CONFIG_DEBUG_KERNEL=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y



CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y

Re: psmouse.c, throwing 3 bytes away

[Mike Houston]

On Thu, 5 Feb 2004 17:10:27 -0500
Mike Houston <mikeserv@bmts.com> wrote:

> I am using ACPI and IO-APIC. Next time my mouse acts up, I will consider trying
> 2.6.2 without ACPI and IO-APIC (though I'd hate to lose that functionality).
> Trouble is it might take a long time for the mouse glitch to occur.

Ok, shortly after posting earlier today, it did indeed happen again with 2.6.2. I was just clicking on mails in my sylpheed client. There wasn't much load, I wasn't doing anything but reading mails.

So I built another 2.6.2 with acpi and io-apic disabled and ran it for about 5 hours and the problem reoccurred. I was just chatting on IRC and moved my mouse and it happened. Again, I was doing nothing else so load wasn't a factor.

psmouse.c: MX Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

Gee whiz, it just happened again while composing this mail :-)

So it doesn't have anything to do with acpi, or being under load for that matter, on my system, anyway.

Mike

Re: psmouse.c, throwing 3 bytes away

[Walt Nelson]

I am not sure but patch-2.6.2-bk1.tar.gz has not produce the mouse problems. I 
applied it about 14 hours ago. I have no seen any mouse problems. I noticed 
that there was a possible fix for loosing ticks in it?

Walt


On Thursday 05 February 2004 11:15 pm, Mike Houston wrote:
> On Thu, 5 Feb 2004 17:10:27 -0500
>
> Mike Houston <mikeserv@bmts.com> wrote:
> > I am using ACPI and IO-APIC. Next time my mouse acts up, I will consider
> > trying 2.6.2 without ACPI and IO-APIC (though I'd hate to lose that
> > functionality). Trouble is it might take a long time for the mouse glitch
> > to occur.
>
> Ok, shortly after posting earlier today, it did indeed happen again with
> 2.6.2. I was just clicking on mails in my sylpheed client. There wasn't
> much load, I wasn't doing anything but reading mails.
>
> So I built another 2.6.2 with acpi and io-apic disabled and ran it for
> about 5 hours and the problem reoccurred. I was just chatting on IRC and
> moved my mouse and it happened. Again, I was doing nothing else so load
> wasn't a factor.
>
> psmouse.c: MX Mouse at isa0060/serio1/input0 lost synchronization, throwing
> 2 bytes away.
>
> Gee whiz, it just happened again while composing this mail :-)
>
> So it doesn't have anything to do with acpi, or being under load for that
> matter, on my system, anyway.
>
> Mike
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: psmouse.c, throwing 3 bytes away

[Kronos]

Vojtech Pavlik <vojtech@suse.cz> ha scritto:
> On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
>> I have same problems since of 2.6.0, now I running 2.6.2 stock kernel
>> I run XFree86-4.3.0 and still with problems, anyone try XFree86-4.4.0 devel snapshots???
>> 
>> I try kernel with/without  preempty/acpi/apic make all possibilities, 
>> then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
>> of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary 
>> and source incompatibilites,  
> 
> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.

I see also this messages (other than XFree being buggy):

psmouse.c: bad data from KBC - bad parity
psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.

They seem totaly random, this one happened while the system was almost
idle (was talking to a friend of mine using licq, under X). DMA is
turned on (but disks were idle).

I tried to reproduce under heavy disk and network load but without
success. However, it seems that the problem often happens when switching
from console to X (can't reproduce...).

This is the mouse:

root@dreamland:~# cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

and lspci:

root@dreamland:~# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:09.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 05)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 40)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]
01:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9500 Pro] (Secondary)

kernel is 2.6.2 UP with preempt (I'm sorry but I'm preparing some exams
so don't have much free time to test other configuration). 2.6.1 works
fine.

HTH,
Luca
-- 
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Non capisco tutta questa eccitazione per il Multitasking: 
io sono anni che leggo in bagno.

Re: psmouse.c, throwing 3 bytes away

[Jamie Lokier]

Vojtech Pavlik wrote:
> On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
> > I try kernel with/without  preempty/acpi/apic make all possibilities, 
> > then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
> > of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary 
> > and source incompatibilites,  
> 
> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.

Heh.  I have a USB mouse and I see similar problems:

Red Hat 9 (more or less), XFree86-4.3.0-2, kernel 2.6.0-test10, dual
athlon, USB Logitech optical mouse, configured to read from
/dev/input/mice (only!).

Every few hours the mouse suddenly jumps to a corner of the screen and
seems broken for a second or so.  After that I can move it back to
where it is useful.

I never noticed such behaviour when running 2.4 on this box, nor when
running earlier 2.6 kernels.

There is nothing about "atkbd" or "mouse" or "lost synchronisation" in
the kernel log.

-- Jamie

Re: psmouse.c, throwing 3 bytes away

[Gene Heskett]

On Friday 06 February 2004 21:35, Jamie Lokier wrote:
>Vojtech Pavlik wrote:
>> On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
>> > I try kernel with/without  preempty/acpi/apic make all
>> > possibilities, then may be error is not in kernel, but in
>> > XFree86-4.3.0 which not support big changes in input system of
>> > 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel
>> > headers was 100% fail, sounds binary and source
>> > incompatibilites,
>>
>> Hey, guys, could you possibly try to figure out what your machines
>> have in common? I've switched all my computers to PS/2 mice so
>> that I have a bigger chance to reproduce the problem, but it is
>> not happening on any of them.
>
>Heh.  I have a USB mouse and I see similar problems:
>
>Red Hat 9 (more or less), XFree86-4.3.0-2, kernel 2.6.0-test10, dual
>athlon, USB Logitech optical mouse, configured to read from
>/dev/input/mice (only!).
>
>Every few hours the mouse suddenly jumps to a corner of the screen
> and seems broken for a second or so.  After that I can move it back
> to where it is useful.
>
>I never noticed such behaviour when running 2.4 on this box, nor
> when running earlier 2.6 kernels.
>
>There is nothing about "atkbd" or "mouse" or "lost synchronisation"
> in the kernel log.

FWIW, I do have those lines from atkbd, blamed on X in my logs as I 
startx.

And, I have an occasional attack of spasticity in my mouse, on this 
machine only (VIA 8233 chipset) since back in later 2.4 days.  I've 
even posted about it, but its not a *huge* problem, just a minor 
aggravation.  The exact same mouse model, and mouse cause I've traded 
them (a pair of logitech usb optical wheel mice) has no trouble at 
all on an old TYAN S-1590 mobo.  ISTR its running some version of 
2.4.20 yet, with lots of guard dogs, its my firewall.

>-- Jamie
>-
>To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: psmouse.c, throwing 3 bytes away

[Mike Houston]

On Fri, 6 Feb 2004 00:06:32 -0800
Walt Nelson <wnelsonjr@comcast.net> wrote:

> I am not sure but patch-2.6.2-bk1.tar.gz has not produce the mouse problems. I 
> applied it about 14 hours ago. I have no seen any mouse problems. I noticed 
> that there was a possible fix for loosing ticks in it?
> 

Well, I've been running 2.6.2-bk2 for around 12 hours now, and the problem hasn't surfaced. While this is the longest I've gone, it still could be coincidence but I'm hoping that strange mouse glitch won't come back.

I'm going to move on to 2.6.3-rc1 now. Here's to having nothing to report :-)

Mike

Re: psmouse.c, throwing 3 bytes away

[Murilo Pontes]

Problem still occurs :-(



09:03:17 [root@murilo:~]#cat /proc/version
Linux version 2.6.3-rc1 (root@murilo) (gcc version 3.3.2) #2 Sat Feb 7 08:24:31 UTC 2004
09:03:20 [root@murilo:~]#
09:03:20 [root@murilo:~]#dmesg | grep psmouse
psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
09:03:41 [root@murilo:~]#
09:04:45 [root@murilo:~]#uptime
 09:04:49 up 39 min,  0 users,  load average: 0.08, 0.16, 0.15
09:04:49 [root@murilo:~]#
09:10:46 [root@murilo:~]#dmesg | grep time
Using tsc for high-res timesource
Machine check exception polling timer started.
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:02.2 to 64
PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:00:02.1 to 64
PCI: Setting latency timer of device 0000:00:06.0 to 64
09:11:11 [root@murilo:~]#


Em Sáb 07 Fev 2004 05:47, Mike Houston escreveu:
> On Fri, 6 Feb 2004 00:06:32 -0800
> Walt Nelson <wnelsonjr@comcast.net> wrote:
> 
> > I am not sure but patch-2.6.2-bk1.tar.gz has not produce the mouse problems. I 
> > applied it about 14 hours ago. I have no seen any mouse problems. I noticed 
> > that there was a possible fix for loosing ticks in it?
> > 
> 
> Well, I've been running 2.6.2-bk2 for around 12 hours now, and the problem hasn't surfaced. While this is the longest I've gone, it still could be coincidence but I'm hoping that strange mouse glitch won't come back.
> 
> I'm going to move on to 2.6.3-rc1 now. Here's to having nothing to report :-)
> 
> Mike
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Sat, Feb 07, 2004 at 09:11:42AM +0000, Murilo Pontes wrote:

> Problem still occurs :-(

I have good news - I've managed to reliably reproduce the bug on my
machine and that means I now have a good chance to find and fix it.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c, throwing 3 bytes away

[aeriksson]

> 
> > Problem still occurs :-(
> 
> I have good news - I've managed to reliably reproduce the bug on my
> machine and that means I now have a good chance to find and fix it.
> 

Another data point. I just tried switching to a non-preempt kernel as
was suggested by someone. The problem still occurs.

/A

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson@fastmail.fm wrote:

> > > Problem still occurs :-(
> > 
> > I have good news - I've managed to reliably reproduce the bug on my
> > machine and that means I now have a good chance to find and fix it.
> > 
> 
> Another data point. I just tried switching to a non-preempt kernel as
> was suggested by someone. The problem still occurs.

You may want to try killing the mod_timer() calls in i8042.c. That'll
probably help.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c, throwing 3 bytes away

[Bernd Schubert]

On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson-97jfqw80gc6171pxa8y+qA@public.gmane.org wrote:
> 
> > 
> > > Problem still occurs :-(
> > 
> > I have good news - I've managed to reliably reproduce the bug on my
> > machine and that means I now have a good chance to find and fix it.
> > 
> 
> Another data point. I just tried switching to a non-preempt kernel as
> was suggested by someone. The problem still occurs.
> 

Hello,

on IBM Thinkpads R31 this is also easiliy to reproduce:

For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
and the mouse becomes crazy and one gets the throwing 2 bytes away
messages in the log files. By fast reading in an endless loop even
input from the keyboard is ignored.

For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
affected in 2.4. kernel versions.

Well, for R31's it is said that it is the bad bios, but maybe its
related? Any ideas why it doesn't happen with acpi and 2.4.? 

My knowlege of the kernel interals is quite low and pretty much limited
to the basic vfs area, so could you please give me some good advises how to
debug this?

Thanks,
	Bernd


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: psmouse.c, throwing 3 bytes away

[Bernd Schubert]

On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson@fastmail.fm wrote:
> 
> > 
> > > Problem still occurs :-(
> > 
> > I have good news - I've managed to reliably reproduce the bug on my
> > machine and that means I now have a good chance to find and fix it.
> > 
> 
> Another data point. I just tried switching to a non-preempt kernel as
> was suggested by someone. The problem still occurs.
> 

Hello,

on IBM Thinkpads R31 this is also easiliy to reproduce:

For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
and the mouse becomes crazy and one gets the throwing 2 bytes away
messages in the log files. By fast reading in an endless loop even
input from the keyboard is ignored.

For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
affected in 2.4. kernel versions.

Well, for R31's it is said that it is the bad bios, but maybe its
related? Any ideas why it doesn't happen with acpi and 2.4.? 

My knowlege of the kernel interals is quite low and pretty much limited
to the basic vfs area, so could you please give me some good advises how to
debug this?

Thanks,
	Bernd

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 12:03:14AM +0100, Bernd Schubert wrote:

> On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson-97jfqw80gc6171pxa8y+qA@public.gmane.org wrote:
> > 
> > > 
> > > > Problem still occurs :-(
> > > 
> > > I have good news - I've managed to reliably reproduce the bug on my
> > > machine and that means I now have a good chance to find and fix it.
> > > 
> > 
> > Another data point. I just tried switching to a non-preempt kernel as
> > was suggested by someone. The problem still occurs.

> Hello,
> 
> on IBM Thinkpads R31 this is also easiliy to reproduce:
> 
> For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
> and the mouse becomes crazy and one gets the throwing 2 bytes away
> messages in the log files. By fast reading in an endless loop even
> input from the keyboard is ignored.
> 
> For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
> affected in 2.4. kernel versions.
> 
> Well, for R31's it is said that it is the bad bios, but maybe its
> related? Any ideas why it doesn't happen with acpi and 2.4.? 

There are many reasons why it can happen. I'm currently debugging the
one where no APM or ACPI or anything else is needed.

> My knowlege of the kernel interals is quite low and pretty much limited
> to the basic vfs area, so could you please give me some good advises how to
> debug this?

You can enable DEBUG in i8042.c, and then look at 'dmesg' when the
problem happens. There will be a missing byte in the stream ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 12:03:14AM +0100, Bernd Schubert wrote:

> On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson@fastmail.fm wrote:
> > 
> > > 
> > > > Problem still occurs :-(
> > > 
> > > I have good news - I've managed to reliably reproduce the bug on my
> > > machine and that means I now have a good chance to find and fix it.
> > > 
> > 
> > Another data point. I just tried switching to a non-preempt kernel as
> > was suggested by someone. The problem still occurs.

> Hello,
> 
> on IBM Thinkpads R31 this is also easiliy to reproduce:
> 
> For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
> and the mouse becomes crazy and one gets the throwing 2 bytes away
> messages in the log files. By fast reading in an endless loop even
> input from the keyboard is ignored.
> 
> For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
> affected in 2.4. kernel versions.
> 
> Well, for R31's it is said that it is the bad bios, but maybe its
> related? Any ideas why it doesn't happen with acpi and 2.4.? 

There are many reasons why it can happen. I'm currently debugging the
one where no APM or ACPI or anything else is needed.

> My knowlege of the kernel interals is quite low and pretty much limited
> to the basic vfs area, so could you please give me some good advises how to
> debug this?

You can enable DEBUG in i8042.c, and then look at 'dmesg' when the
problem happens. There will be a missing byte in the stream ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

[patch] Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

[-- Attachment #1: Type: text/plain, Size: 178 bytes --]

On Sat, Feb 07, 2004 at 09:11:42AM +0000, Murilo Pontes wrote:

> Problem still occurs :-(

And here is a fix. Damn stupid mistake I made.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

[-- Attachment #2: lost-sync-fix --]
[-- Type: text/plain, Size: 1084 bytes --]

You can pull this changeset from:
	bk://kernel.bkbits.net/vojtech/input

===================================================================

ChangeSet@1.1587, 2004-02-09 01:47:16+01:00, vojtech@suse.cz
  input: Fix "psmouse: Lost sync" problem. It was really losing sync.


 i8042.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

===================================================================

diff -Nru a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
--- a/drivers/input/serio/i8042.c	Mon Feb  9 01:47:46 2004
+++ b/drivers/input/serio/i8042.c	Mon Feb  9 01:47:46 2004
@@ -379,9 +379,12 @@
 	unsigned int dfl;
 	int ret;
 
+	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
+
 	spin_lock_irqsave(&i8042_lock, flags);
 	str = i8042_read_status();
-	data = i8042_read_data();
+	if (str & I8042_STR_OBF)
+		data = i8042_read_data();
 	spin_unlock_irqrestore(&i8042_lock, flags);
 
 	if (~str & I8042_STR_OBF) {
@@ -432,7 +435,6 @@
 irq_ret:
 	ret = 1;
 out:
-	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
 	return IRQ_RETVAL(ret);
 }
 

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Claudio Martins]

  Just FYI:

  CC      drivers/input/serio/i8042.o
drivers/input/serio/i8042.c: In function `i8042_interrupt':
drivers/input/serio/i8042.c:378: warning: `data' might be used uninitialized 
in this function

regards

Claudio


On Monday 09 February 2004 00:48, Vojtech Pavlik wrote:
> On Sat, Feb 07, 2004 at 09:11:42AM +0000, Murilo Pontes wrote:
> > Problem still occurs :-(
>
> And here is a fix. Damn stupid mistake I made.

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 01:13:23AM +0000, Claudio Martins wrote:
> 
>   Just FYI:
> 
>   CC      drivers/input/serio/i8042.o
> drivers/input/serio/i8042.c: In function `i8042_interrupt':
> drivers/input/serio/i8042.c:378: warning: `data' might be used uninitialized 
> in this function

It can't be used uninitalized. I've fixed this in my tree already, just
ignore the warning for the time being.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c, throwing 3 bytes away

[Isaac Claymore]

On Thu, Feb 05, 2004 at 06:20:23PM +0800, Isaac Claymore wrote:
> On Thu, Feb 05, 2004 at 04:54:44AM +0000, Claudio Martins wrote:
> > 
> > On Thursday 05 February 2004 02:20, Walt Nelson wrote:
> > > My mouse has been acting wired occationally, not all the time. I receive
> > > the following error in the syslog. This has been happening since 2.6.2-RC3.
> > > I am currently using 2.6.2. Are these related?
> > >
> > > Feb  4 13:56:02 gumby kernel: psmouse.c: Wheel Mouse at
> > > isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> > >
> > > The following occurs when starting KDE/X.
> > > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > > 2, code 0x7a on isa0060/serio0).
> > > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > > access hardware directly.
> > > Feb  4 18:05:11 gumby kernel: atkbd.c: Unknown key released (translated set
> > > 2, code 0x7a on isa0060/serio0).
> > > Feb  4 18:05:11 gumby kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> > > access hardware directly.
> > >
> > 
> > 
> >   I saw the same here yesterday, using a logitech wheel mouse:
> > 
> > Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> > lost synchronization, throwing 2 bytes away.
> > 
> >   Before this happened the mouse in X just went nuts with random clicks in 
> > many windows, but after that it's been ok up to now.
> > 
> I've been suffering this same problem ever since upgrade to 2.6 kernel.
> 
> FYI, here is an article giving some possible solutions to this, but I
> failed to fix my mouse problem by any method it suggests:
> 
> http://kerneltrap.org/node/view/2199
> 
> 

Just FYI:

This annoying mouse problem hasn't shown up for 3 days, after I did a 
'hdparm -u1 /dev/hda'. But be sure to read the hdparm man page before 
doing this on your box.


> >   FYI the mouse is detected as: 
> > 
> > Feb  4 08:57:42 vega kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> > Feb  4 08:57:42 vega kernel: input: PS2++ Logitech Wheel Mouse on 
> > isa0060/serio1
> > 
> >   The motherboard is an Intel 440BX2 with a PII-350 running kernel 2.6.2.
> > 
> > Thanks 
> > 
> > Claudio
> > 
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> -- 
> 
> Regards, Isaac
> ()  ascii ribbon campaign - against html e-mail
> /\                        - against microsoft attachments
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

Regards, Isaac
()  ascii ribbon campaign - against html e-mail
/\                        - against microsoft attachments

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 02:15:32PM +0800, Isaac Claymore wrote:

> > >   I saw the same here yesterday, using a logitech wheel mouse:
> > > 
> > > Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> > > lost synchronization, throwing 2 bytes away.
> > > 
> > >   Before this happened the mouse in X just went nuts with random clicks in 
> > > many windows, but after that it's been ok up to now.
> > > 
> > I've been suffering this same problem ever since upgrade to 2.6 kernel.
> > 
> > FYI, here is an article giving some possible solutions to this, but I
> > failed to fix my mouse problem by any method it suggests:
> > 
> > http://kerneltrap.org/node/view/2199
> > 
> > 
> 
> Just FYI:
> 
> This annoying mouse problem hasn't shown up for 3 days, after I did a 
> 'hdparm -u1 /dev/hda'. But be sure to read the hdparm man page before 
> doing this on your box.

I think you're looking for 'hdparm -d1 /dev/hda', if your mainboard is
not very very old. That'll have a better effect.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c, throwing 3 bytes away

[Isaac Claymore]

On Mon, Feb 09, 2004 at 10:09:55AM +0100, Vojtech Pavlik wrote:
> On Mon, Feb 09, 2004 at 02:15:32PM +0800, Isaac Claymore wrote:
> 
> > > >   I saw the same here yesterday, using a logitech wheel mouse:
> > > > 
> > > > Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> > > > lost synchronization, throwing 2 bytes away.
> > > > 
> > > >   Before this happened the mouse in X just went nuts with random clicks in 
> > > > many windows, but after that it's been ok up to now.
> > > > 
> > > I've been suffering this same problem ever since upgrade to 2.6 kernel.
> > > 
> > > FYI, here is an article giving some possible solutions to this, but I
> > > failed to fix my mouse problem by any method it suggests:
> > > 
> > > http://kerneltrap.org/node/view/2199
> > > 
> > > 
> > 
> > Just FYI:
> > 
> > This annoying mouse problem hasn't shown up for 3 days, after I did a 
> > 'hdparm -u1 /dev/hda'. But be sure to read the hdparm man page before 
> > doing this on your box.
> 
> I think you're looking for 'hdparm -d1 /dev/hda', if your mainboard is
> not very very old. That'll have a better effect.
> 

using_dma was already turned on, before I tried that '-u1'. At least in
my case, turning on using_dma alone didn't seem to help much.

Thanks for the hint.


> -- 
> Vojtech Pavlik
> SuSE Labs, SuSE CR
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

Regards, Isaac
()  ascii ribbon campaign - against html e-mail
/\                        - against microsoft attachments

Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 05:49:51PM +0800, Isaac Claymore wrote:
> On Mon, Feb 09, 2004 at 10:09:55AM +0100, Vojtech Pavlik wrote:
> > On Mon, Feb 09, 2004 at 02:15:32PM +0800, Isaac Claymore wrote:
> > 
> > > > >   I saw the same here yesterday, using a logitech wheel mouse:
> > > > > 
> > > > > Feb  4 18:19:46 vega kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 
> > > > > lost synchronization, throwing 2 bytes away.
> > > > > 
> > > > >   Before this happened the mouse in X just went nuts with random clicks in 
> > > > > many windows, but after that it's been ok up to now.
> > > > > 
> > > > I've been suffering this same problem ever since upgrade to 2.6 kernel.
> > > > 
> > > > FYI, here is an article giving some possible solutions to this, but I
> > > > failed to fix my mouse problem by any method it suggests:
> > > > 
> > > > http://kerneltrap.org/node/view/2199
> > > > 
> > > > 
> > > 
> > > Just FYI:
> > > 
> > > This annoying mouse problem hasn't shown up for 3 days, after I did a 
> > > 'hdparm -u1 /dev/hda'. But be sure to read the hdparm man page before 
> > > doing this on your box.
> > 
> > I think you're looking for 'hdparm -d1 /dev/hda', if your mainboard is
> > not very very old. That'll have a better effect.
> > 
> 
> using_dma was already turned on, before I tried that '-u1'. At least in
> my case, turning on using_dma alone didn't seem to help much.
> 
> Thanks for the hint.

That's interesting, because -d1 makes -u1 irrelevant, -u1 is for PIO
accesses only, and -d1 switches to DMA mode.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: Re: psmouse.c, throwing 3 bytes away

[roychris]

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

I resolved this problem. It's the fault of the multiplexing on i8042. 
You must pass i8042_nomux=1 to the kernel for 2.4.X or 2.6.0 or you must 
modify
linux-2.6.x/drivers/input/serio/i8042.c by quoting many lines if > 2.6.0 
because nomux doesn't work :


/*      if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values)) {
                if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values))
                        for (i = 0; i < 4; i++) {
                                i8042_init_mux_values(i8042_mux_values + 
i, i804
2_mux_port + i, i);
                                i8042_port_register(i8042_mux_values + 
i, i8042_
mux_port + i);
                        }
                else
*/                    
             i8042_port_register(&i8042_aux_values, &i8042_aux_port);
//      }

I know it's a very bad way to solve the problem but it's working and I 
don't have more time.


Vojtech Pavlik a écrit :

>On Mon, Feb 09, 2004 at 12:03:14AM +0100, Bernd Schubert wrote:
>
>  
>
>>On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson-97jfqw80gc6171pxa8y+qA@public.gmane.org wrote:
>>    
>>
>>>>>Problem still occurs :-(
>>>>>          
>>>>>
>>>>I have good news - I've managed to reliably reproduce the bug on my
>>>>machine and that means I now have a good chance to find and fix it.
>>>>
>>>>        
>>>>
>>>Another data point. I just tried switching to a non-preempt kernel as
>>>was suggested by someone. The problem still occurs.
>>>      
>>>
>
>  
>
>>Hello,
>>
>>on IBM Thinkpads R31 this is also easiliy to reproduce:
>>
>>For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
>>and the mouse becomes crazy and one gets the throwing 2 bytes away
>>messages in the log files. By fast reading in an endless loop even
>>input from the keyboard is ignored.
>>
>>For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
>>affected in 2.4. kernel versions.
>>
>>Well, for R31's it is said that it is the bad bios, but maybe its
>>related? Any ideas why it doesn't happen with acpi and 2.4.? 
>>    
>>
>
>There are many reasons why it can happen. I'm currently debugging the
>one where no APM or ACPI or anything else is needed.
>
>  
>
>>My knowlege of the kernel interals is quite low and pretty much limited
>>to the basic vfs area, so could you please give me some good advises how to
>>debug this?
>>    
>>
>
>You can enable DEBUG in i8042.c, and then look at 'dmesg' when the
>problem happens. There will be a missing byte in the stream ...
>
>  
>


[-- Attachment #2: Type: text/html, Size: 4347 bytes --]

Re: Re: psmouse.c, throwing 3 bytes away

[roychris]

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

I resolved this problem. It's the fault of the multiplexing on i8042. 
You must pass i8042_nomux=1 to the kernel for 2.4.X or 2.6.0 or you must 
modify
linux-2.6.x/drivers/input/serio/i8042.c by quoting many lines if > 2.6.0 
because nomux doesn't work :


/*      if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values)) {
                if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values))
                        for (i = 0; i < 4; i++) {
                                i8042_init_mux_values(i8042_mux_values + 
i, i804
2_mux_port + i, i);
                                i8042_port_register(i8042_mux_values + 
i, i8042_
mux_port + i);
                        }
                else
*/                    
             i8042_port_register(&i8042_aux_values, &i8042_aux_port);
//      }

I know it's a very bad way to solve the problem but it's working and I 
don't have more time.


Vojtech Pavlik a écrit :

>On Mon, Feb 09, 2004 at 12:03:14AM +0100, Bernd Schubert wrote:
>
>  
>
>>On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson-97jfqw80gc6171pxa8y+qA@public.gmane.org wrote:
>>    
>>
>>>>>Problem still occurs :-(
>>>>>          
>>>>>
>>>>I have good news - I've managed to reliably reproduce the bug on my
>>>>machine and that means I now have a good chance to find and fix it.
>>>>
>>>>        
>>>>
>>>Another data point. I just tried switching to a non-preempt kernel as
>>>was suggested by someone. The problem still occurs.
>>>      
>>>
>
>  
>
>>Hello,
>>
>>on IBM Thinkpads R31 this is also easiliy to reproduce:
>>
>>For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
>>and the mouse becomes crazy and one gets the throwing 2 bytes away
>>messages in the log files. By fast reading in an endless loop even
>>input from the keyboard is ignored.
>>
>>For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
>>affected in 2.4. kernel versions.
>>
>>Well, for R31's it is said that it is the bad bios, but maybe its
>>related? Any ideas why it doesn't happen with acpi and 2.4.? 
>>    
>>
>
>There are many reasons why it can happen. I'm currently debugging the
>one where no APM or ACPI or anything else is needed.
>
>  
>
>>My knowlege of the kernel interals is quite low and pretty much limited
>>to the basic vfs area, so could you please give me some good advises how to
>>debug this?
>>    
>>
>
>You can enable DEBUG in i8042.c, and then look at 'dmesg' when the
>problem happens. There will be a missing byte in the stream ...
>
>  
>


[-- Attachment #2: Type: text/html, Size: 4436 bytes --]

Re: psmouse.c, throwing 3 bytes away

[Bernd Schubert]

On Monday 09 February 2004 13:43, roychris wrote:
> I resolved this problem. It's the fault of the multiplexing on i8042.
> You must pass i8042_nomux=1 to the kernel for 2.4.X or 2.6.0 or you must
> modify
> linux-2.6.x/drivers/input/serio/i8042.c by quoting many lines if > 2.6.0
> because nomux doesn't work :
>
>
> /*      if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values)) {
>                 if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values))
>                         for (i = 0; i < 4; i++) {
>                                 i8042_init_mux_values(i8042_mux_values +
> i, i804
> 2_mux_port + i, i);
>                                 i8042_port_register(i8042_mux_values +
> i, i8042_
> mux_port + i);
>                         }
>                 else
> */
>              i8042_port_register(&i8042_aux_values, &i8042_aux_port);
> //      }
>

Hello Roychris,

on 2.4.25-rc1 the i8042_nomux=1 option causes the following:
- on a single read on /proc/apm the mouse still jumps
- several/few reads make the mouse to stop and only to work after a few 
seconds
- a fast endless read makes the mouse to stop at all and never work again

Commenting out the lines in 2.6.2-rc2 causes the mouse not to work at all. No 
error messages, nothing in the logs.

Do you have a Thinkpad R31 and it workes there for you?

Thanks a lot for your help,
	Bernd

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Greg Norris]

On Mon, Feb 09, 2004 at 01:48:12AM +0100, Vojtech Pavlik wrote:
> And here is a fix. Damn stupid mistake I made.

This appears to squash my problem as well (the "usb mouse/keyboard
problems under 2.6.2" thread).  Thanx!!!

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Mon, Feb 09, 2004 at 08:56:27PM -0600, Greg Norris wrote:
> On Mon, Feb 09, 2004 at 01:48:12AM +0100, Vojtech Pavlik wrote:
> > And here is a fix. Damn stupid mistake I made.
> 
> This appears to squash my problem as well (the "usb mouse/keyboard
> problems under 2.6.2" thread).  Thanx!!!

USB?? This was for PS/2 mice. If it fixed your USB mouse problem, you
were using PS/2 drivers with your USB mouse, which is wrong (although it
can work). You need to use USB drivers.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[johann lombardi]

> And here is a fix. Damn stupid mistake I made.
It solves the problem for me.
Thanks.

Johann

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Walt Nelson]

Thanks for the psmouse.c fix.

Walt

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Greg Norris]

On Tue, Feb 10, 2004 at 08:07:35AM +0100, Vojtech Pavlik wrote:
> USB?? This was for PS/2 mice. If it fixed your USB mouse problem, you
> were using PS/2 drivers with your USB mouse, which is wrong (although it
> can work). You need to use USB drivers.

I thought I was... all of the appropriate USB drivers are enabled, and
I haven't done anything special to load the psmouse module.  I guess
it's possible that a bootup script is loading it automagically,
tho.  I'll check into this.

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Vojtech Pavlik]

On Tue, Feb 10, 2004 at 01:48:55PM -0600, Greg Norris wrote:
> On Tue, Feb 10, 2004 at 08:07:35AM +0100, Vojtech Pavlik wrote:
> > USB?? This was for PS/2 mice. If it fixed your USB mouse problem, you
> > were using PS/2 drivers with your USB mouse, which is wrong (although it
> > can work). You need to use USB drivers.
> 
> I thought I was... all of the appropriate USB drivers are enabled, and
> I haven't done anything special to load the psmouse module.  I guess
> it's possible that a bootup script is loading it automagically,
> tho.  I'll check into this.

The most suspicious issue here is that not only psmouse gets loaded, but
that it finds a mouse attached! Note that ehci-hcd is not enough, you
also will need either uhci or ohci.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Murilo Pontes]

Thanks, 
I tested by 12hours, everything is ok :)
But I want test more few days


Em Seg 09 Fev 2004 00:48, você escreveu:
> On Sat, Feb 07, 2004 at 09:11:42AM +0000, Murilo Pontes wrote:
> 
> > Problem still occurs :-(
> 
> And here is a fix. Damn stupid mistake I made.
> 

Re: [patch] Re: psmouse.c, throwing 3 bytes away

[Claudio Martins]

  Hi,

  Just to report that during many hours of desktop use and also some heavier 
use (like quake3 :-), the mouse behaved just fine without any glitches or 
error messages.

  So it seems that the problem is solved with your patch.

  Thanks for your work!

best regards

Claudio

On Monday 09 February 2004 00:48, Vojtech Pavlik wrote:
> On Sat, Feb 07, 2004 at 09:11:42AM +0000, Murilo Pontes wrote:
> > Problem still occurs :-(
>
> And here is a fix. Damn stupid mistake I made.