--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image: sata drive connected via marvell controller crashes
- From: Mark Poks <markpoks@wp.pl>
- Date: Sat, 14 Feb 2009 19:35:01 +0100
- Message-id: <20090214183501.4189.14224.reportbug@localhost>
Package: linux-image
Severity: important
i have ASUS M2N32 WS Professionall mainboard with latest BIOS revision 2001.
it has two controllers for sata:
- standard (nvidia)
- marvell
and also i have two sata II disks:
1 - with Debian 32-bit, kernel 2.6.26-1-686-bigmem - plugged in standard sata
2 - with Debian 64-bit, kernel 2.6.26-1-amd64 - plugged in marvell sata
the standard sata controller works fine, but i have problems with the marvell.
* when booting disk 1 (disk 2 is connected to marvell controller) system does
not boot up correctly. it holds-on - see photo:
http://develop.euroimpex.pl/~marek/boot/dsc00226.jpg
last few lines of long display in a loop if waiting longer..
* when booting disk 1, with disk 2 unplugged, system starts fine ofcourse,
but when plugin disk 2 to marvell (when system is on), the message
'Disabling IRQ #16' appears in console and system hangs-up.
* i tried also bootup from disk 2 (marvell controller), the grub started,
kernel started to doing it's job, but it crashed - see photo:
http://develop.euroimpex.pl/~marek/boot/dsc00227.jpg
maybe i am doing something wrong? maybe my mainboard has a bug, or maybe
it's something wrong in kernel? or maybe i have badly configured IRQs in the
BIOS? - not sure
cheers.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 3.4.1-1~experimental.1+rm
Debian 6.0 Long Term Support is now ending, and the 'linux-2.6' source
package will no longer be updated. This bug is being closed on the
assumption that it does not affect the kernel versions in newer Debian
releases.
If you can still reproduce this bug in a newer release, please reopen
the bug report and reassign it to 'src:linux' and the affected version
of the package. You can find the package version for the running
kernel by running:
uname -v
or the versions of all installed kernel packages by running:
dpkg -l 'linux-image-[34]*' | grep ^.i
and looking at the third column.
I apologise that we weren't able to provide a specific resolution for
this bug.
Ben.
--
Ben Hutchings - Debian developer, member of Linux kernel and LTS teams
--- End Message ---