Bug#506835: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created
- To: 506835@bugs.debian.org
- Subject: Bug#506835: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created
- From: Arthur Marsh <arthur.marsh@internode.on.net>
- Date: Mon, 08 Dec 2008 19:58:14 +1030
- Message-id: <[🔎] 493CE8AE.3060200@internode.on.net>
- Reply-to: Arthur Marsh <arthur.marsh@internode.on.net>, 506835@bugs.debian.org
- In-reply-to: <20081128173727.GB3450@cat.rubenette.is-a-geek.com>
- References: <sfspv5-ec4.ln1@CPE-124-182-251-164.sa.bigpond.net.au> <20081124145432.GI31423@cat.rubenette.is-a-geek.com> <cujsv5-5r5.ln1@ppp150-101-64-129.as1.adl6.internode.on.net> <vdd206-4up.ln1@ppp150-101-64-129.as1.adl6.internode.on.net> <20081127174954.GV13038@cat.rubenette.is-a-geek.com> <btf406-i65.ln1@ppp150-101-64-129.as1.adl6.internode.on.net> <e9s406-qn5.ln1@ppp150-101-64-129.as1.adl6.internode.on.net> <492FFEDE.6040305@internode.on.net> <20081128173727.GB3450@cat.rubenette.is-a-geek.com>
lee wrote, on 29/11/08 04:07:
Hm, I've always been using the kernels from kernel.org without
problems.
You should file a bug report about this problem. Obviously something
has changed that makes the current kernels incompatilbe with the eata
module.
Done and ongoing.
I'm still trying to get to the source of the bug that prevents me from
using a DPT2044W SCSI card that uses the eata module, and have narrowed
down the working and non-working Debian kernel images to between
linux-image-2.6.22-3-686 version 2.6.22-6.lenny1 which works, and
linux-image-2.6.23-1-686 version 2.6.23-1 which fails.
There appear to be a large number of changes between the two and I am
unfamiliar with how to generate an intermediate kernel source with
Debian changes and config to build and test.
I am currently running linux-image-2.6.22-3-686 version 2.6.22-6.lenny1
and dmesg reports the following when loading eata:
EATA/DMA 2.0x: Copyright (C) 1994-2003 Dario Ballabio.
EATA config options -> tm:1, lc:y, mq:16, rs:y, et:n, ip:y, ep:n, pp:y.
EATA0: 2.0C, PCI 0xe010, IRQ 5, BMST, SG 122, MB 64.
EATA0: wide SCSI support enabled, max_id 16, max_lun 8.
EATA0: SCSI channel 0 enabled, host target ID 7.
scsi0 : EATA/DMA 2.0x rev. 8.10.00
scsi 0:0:6:0: Direct-Access IBM DCAS-34330W S65A PQ: 0 ANSI: 2
scsi 0:0:6:0: cmds/lun 16, sorted, simple tags.
sd 0:0:6:0: [sda] 8466688 512-byte hardware sectors (4335 MB)
sd 0:0:6:0: [sda] Write Protect is off
sd 0:0:6:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:6:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:6:0: [sda] 8466688 512-byte hardware sectors (4335 MB)
sd 0:0:6:0: [sda] Write Protect is off
sd 0:0:6:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:6:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2 < sda5 >
sd 0:0:6:0: [sda] Attached SCSI disk
When loading eata in a later kernel I get some of the same messages
followed by a kernel stack trace and later lock-up.
Any help on narrowing down the problem appreciated.
Arthur.
Reply to: