Comment 1 for bug 7393

Message-Id: <email address hidden>
Date: Wed, 11 Aug 2004 14:40:05 +0100
From: Johan Groth <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.6.7-1-k7-smp: Kernel panics when
 psmouse.proto={bare|imps|exps} is present as kernel parameter

Package: kernel-image-2.6.7-1-k7-smp
Version: 2.6.7-2
Severity: critical
Justification: breaks the whole system

Hardware Environment:
Motherboard: MSI K7D Master
CPU: 2x AMD Athlon MP 1800+
Disk ctrl: Adaptec 2410 SATA Raid
SCSI ctrl: Adaptec 2490UW
HD:s : 4 Seagate Barracuda 120 GB
Mouse: Logitech Cordless Optical Mouse
KVM switch: D-Link DKVM-2

Software Environment:
Linux jaguar 2.6.7-1-k7-smp #1 SMP Thu Jul 22 13:31:50 JST 2004 i686
GNU/Linux

Gnu C 3.3.4
Gnu make 3.80
binutils 2.14.90.0.7
util-linux 2.12
mount 2.12
module-init-tools 3.1-pre5
e2fsprogs 1.35
PPP 2.4.2
nfs-utils 1.0.6
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.2.1
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.2.1

As I can't get 2.6.7 to boot anymore the module list may not be
accurate.

Problem Description:
I've tried without success to resolve the mouse problem with KVM
switching from
and back to Linux with adding psmouse.proto=imps but when I boot the
kernel with that option it panics.

What I did was to install kernel-image-2.6.7-1-k7-smp from debian
testing and
booted. Everything worked as execepted, no errors.

I added psmouse.proto=imps to the kernel boot parameter list (using
grub) and
tried to boot again.

It gets as far as finding the SCSI controller and the raid controller
and tries to find file systems. It can find the root fs on /dev/sda1
and starts the swap on /dev/sda2 but gets very confused that /dev/sda3
is in fact a logical partition. So the kernel tries to check that
partition with every fs it has available but eventually fails and
panics. So I removed the psmouse.proto=imps from the kernel
parameters, rebooted and the kernel still panics! So I can't use 2.6.7
at all now.

What on earth is going on?

Unfortunately I can't determine if it is the SATA raid driver or the
psmouse.proto thing that is the problem.

Steps to reproduce:
Boot the kernel.

/Johan Groth
<email address hidden>

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-k7-smp
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.7-1-k7-smp depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii initrd-tools 0.1.71 tools to create initrd image for p
ii module-init-tools 3.1-pre5-3 tools for managing Linux kernel mo

-- no debconf information