Bug#495014: linux-source-2.6.26: IDE reset, DMA, 32-bit access killed on hald startup, via driver
Package: linux-source-2.6.26
Version: 2.6.26-2
Severity: important
I am compiling in the via ide driver via82cxxx
Kernel boots up fine until hald starts. At this point, an 0xd opcode/busy is
reported and IDE is reset, DMA (and 32bit, etc) disabled.
I can restore these parameters with hdparms but this will lead to problems.
I noticed in the sources compared with 2.6.23 that the timing setup was changed.
This might be the problem (also had on 2.6.25). Possibly the "old" way is
necessary or a needed option.
Here is the logcheck section (hal startup shows on bootup display)
Aug 12 17:54:58 d_baron kernel: ttyS1: LSR safety check engaged!
Aug 12 17:54:58 d_baron kernel: hdc: dma_intr: status=0xd0 { Busy }
Aug 12 17:54:58 d_baron kernel: ide: failed opcode was: unknown
Aug 12 17:54:58 d_baron kernel: hdc: DMA disabled
Aug 12 17:54:58 d_baron kernel: hdd: DMA disabled
Aug 12 17:54:58 d_baron kernel: ide1: reset: success
(hda, hdb DMA, other parameters disabled as well.)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-rt1-davidb (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-source-2.6.26 depends on:
ii binutils 2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii bzip2 1.0.5-0.1 high-quality block-sorting file co
Versions of packages linux-source-2.6.26 recommends:
ii gcc 4:4.3.1-2 The GNU C compiler
ii libc6-dev [libc-dev] 2.7-13 GNU C Library: Development Librari
ii make 3.81-5 The GNU version of the "make" util
Versions of packages linux-source-2.6.26 suggests:
ii kernel-package 11.001-0.1 A utility for building Linux kerne
ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for
ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded)
-- no debconf information
Reply to: