[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#507220: marked as done (linux-source-2.6.24: Kernel panic when accessing Adaptec 1542CF SCSI controller (aha1542 driver))

Your message dated Wed, 3 Dec 2008 23:42:14 +0100
with message-id <20081203224214.GA5476@galadriel.inutil.org>
and subject line Re: problem seemss to be corrrected in 2.6.26
has caused the Debian Bug report #507220,
regarding linux-source-2.6.24: Kernel panic when accessing Adaptec 1542CF SCSI controller (aha1542 driver)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
507220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507220
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-source-2.6.24
Version: 2.6.24-6~etchnhalf.6
Severity: critical
Justification: breaks the whole system


I've moved an Adaptec 1542CF with a SCSI chain of: scanner, tape drive and
CD writer into a P3.  This hardware worked just fine in a pentium 133 years
ago under 2.4 kernels.

On this newer machine any access to the controller or any scsi device
causes a kernel panic.  Both on kernel 2.6.18 and 2.6.24 (the latest
kernel available for Etch via aptitude).  Both kernels were locally
compiled, via make-kpkg.

What works: the BIOS recognizes the controller and the connected devices.
The Adaptec SCSI utility can run DMA tests with no problem.  Manually
loading the aha1542 driver with this command:

modprobe -v aha1542 aha1542=0x134,5,10

causes no errors and identifies the connected devices.  Since this is an
old ISA device, it had to be manually configured for I/O address of 0x134,
dma 5 and irq 10.  In the bios, dma 5 and irq 10 were allocated to "legacy
devices".

Strangely, even with the options in the /etc/modules.conf file and an
explicit mention of aha1542 in /etc/modules, the driver is not loaded
on boot.

Furthermore, any access to the controller causes an immediate panic and
crash.  For instance, running lshw after the driver is loaded causes
this: (kernel 2.6.18)

Bad segment list supplied to aha1542.c (1,0)
0: c0090000 255
cptr c0366e00: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <0> Kernel panic - not syncing: Foooooooood fight!

or (kernel 2.6.24)

Bad segment list supplied to aha1542.c (1,0)
0: c0c20000 255
cptr c0c1be00: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <0> Kernel panic - not syncing: Foooooooood fight!

Any hints?  Looks like a genuine bug to me.  What could be causing
a bad segment list to be supplied to the scsi driver?  If I can supply
more information, just ask and I'll perform the tests required.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.241
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-source-2.6.24 depends on:
ii  binutils                      2.17-3     The GNU assembler, linker and bina
ii  bzip2                         1.0.3-6    high-quality block-sorting file co

Versions of packages linux-source-2.6.24 recommends:
ii  gcc                    4:4.1.1-15        The GNU C compiler
ii  libc6-dev [libc-dev]   2.3.6.ds1-13etch7 GNU C Library: Development Librari
ii  make                   3.81-2            The GNU version of the "make" util

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-10

On Mon, Dec 01, 2008 at 02:49:47AM +0000, The Eclectic One wrote:
> Just compiled a new kernel 2.6.26 (from backports.org) and lshw now
> seems to talk correctly to the scsi system and the panic doesn't
> occur.

Marking that version as fixed.

Cheers,
        Moritz

--- End Message ---
Reply to: