kernel-image-2.6.7-1-k7-smp: Kernel panics when psmouse.proto={bare|imps|exps} is present as kernel parameter

[Debian Bug Importer]

Automatically imported from Debian bug report #265039 http://bugs.debian.org/265039

[Debian Bug Importer (debzilla)]

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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 15 Aug 2004 14:25:35 -0700
From: William Lee Irwin III <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: please try to reproduce on newer kernel packages

Could you try to reproduce this on newer kernel packages?

Thanks.

-- wli

[LaMont Jones (lamont)]

post-warty version

[Debian Bug Importer (debzilla)]

Message-ID: <20040830044143.GA2419@localhost>
Date: Sun, 29 Aug 2004 21:41:43 -0700
From: Don Estberg <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: kernel-image-2.6.8-1-686: Kernel panics when psmouse.proto=bare is present as kernel
 parameter

I ran into the same problem when upgrading from 2.6.5 to 2.6.8. When I
remove psmouse.proto=bare as a parameter in /etc/lilo.conf and instead
put "psmouse proto=bare" in /etc/modules, it works fine, which is the
same as what worked for me in 2.6.5.

Don Estberg

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 10 Sep 2004 09:20:45 +0200
From: maks attems <email address hidden>
To: <email address hidden>
Subject: reassign hole bunch of 2.6.7 bugs, get them on the radar

reassign #263420 kernel
reassign #265039 kernel
reassign #263753 kernel
reassign #258282 kernel
reassign #259481 kernel
reassign #262383 kernel
reassign #262657 kernel
reassign #264197 kernel
reassign #267014 kernel
reassign #270194 kernel
reassign #270198 kernel
reassign #257526 kernel
reassign #257629 kernel
reassign #257691 kernel
reassign #257996 kernel
reassign #259042 kernel
reassign #259185 kernel
reassign #259381 kernel
reassign #259886 kernel
reassign #259893 kernel
reassign #259910 kernel
reassign #260755 kernel
reassign #260917 kernel
reassign #261348 kernel
reassign #261734 kernel
reassign #263316 kernel
reassign #264528 kernel
reassign #264633 kernel
reassign #265536 kernel
reassign #267006 kernel
reassign #267077 kernel
reassign #267079 kernel
reassign #267553 kernel
reassign #267628 kernel
reassign #268583 kernel
reassign #268964 kernel
reassign #269451 kernel
reassign #269579 kernel
reassign #260694 kernel
reassign #260695 kernel
reassign #262628 kernel
reassign #259698 kernel
reassign #267466 kernel
thanks

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 5 Feb 2005 20:58:13 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: readjust severities

severity #287100 wishlist
severity #286609 wishlist
retitle #286609 not enough entropy due to hardware choice
severity 285615 normal
merge 267079 267628 285615
severity #290418 normal
severity #265039 important
severity #283715 important
thanks

--
maks

[Jonathan Aquilina (eagles051387)]

can the debian bug be reproduced on the latest kernels found in intrepid or jaunty?

[Jonathan Aquilina (eagles051387)]

since this cannot be reproduced in intrepid or jaunty i will be closing this bug. if this bug resurfaces feel free to reopen the bug.