kernel-image-2.6.7-1-686: mounting cdrom causes kernel panic

Bug #7312 reported by Debian Bug Importer
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Debian)
Invalid
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Daniel Stone

Bug Description

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

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1BsY9i-0005Zn-5y@localhost>
Date: Wed, 04 Aug 2004 22:38:57 -0400
From: Brian Frank <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.6.7-1-686: mounting cdrom causes kernel panic

Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: grave
Justification: causes non-serious data loss

Attempting to mount a CDROM results in the CD spinning for approximately
30 seconds, then the system locks up completely (unresponsive to
keyboard, mouse, and network). The lockup does not occur when a 2.4
series kernel is used (e.g. kernel-image-2.4.18-1-686), and a CDROM can
be mounted sucessfully, but some error messages are logged in
/var/log/syslog when the 2.4.18-1-686 kernel is used:

Aug 3 20:32:55 localhost kernel: hdd: DMA interrupt recovery
Aug 3 20:32:55 localhost kernel: hdd: lost interrupt
Aug 3 20:32:55 localhost kernel: hdd: cdrom_decode_status: status=0xd0
{ Busy }
Aug 3 20:32:55 localhost kernel: hdd: cdrom_decode_status:error=0xd0LastFailedSense 0x0d
Aug 3 20:32:55 localhost kernel: hdd: DMA disabled
Aug 3 20:32:55 localhost kernel: hdd: ATAPI reset complete
Aug 3 20:32:55 localhost kernel: hdd: command error: status=0x51 {
DriveReady SeekC
omplete Error }
Aug 3 20:32:55 localhost kernel: hdd: command error: error=0x50
Aug 3 20:32:55 localhost kernel: end_request: I/O error, dev 16:40
(hdd), sector 11

A similar problem seems to have been reported for
kernel-2.6.6-1-386 (Bug#257542: Kernel panics when cdrom mounted)

Sometimes the only related entries in /var/log/syslog before lockup is:

localhost kernel: hdd: ATAPI 24X CD-ROM drive, 120kB Cache, DMA
localhost kernel: Uniform CD-ROM driver Revision: 3.20

Occassionally some extra lines also appear:

localhost kernel: hdd: drive_cmd: status=0x51 {DriveReady SeekComplete Error }
localhost kernel: hdd: drive_cmd: error=0x04AbortedCommand
localhost kernel: hdd: irq timeout: status=0xd0 { Busy }
localhost kernel: hdd: irq timeout:error=0xd0LastFailedSense 0x0d

The CDROM can be used to play audio CD's, but after a long delay, and
the reading speed seems to be much slower than usual. When this is done,
the messages that appear in syslog are:

Output from appropriate /proc entries:

/proc/ide/hdd/model
CD-ROM 24X/AKOx

/proc/ide/hdd/driver
ide-cdrom version 4.61

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8

Versions of packages kernel-image-2.6.7-1-686 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

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sat, 14 Aug 2004 01:27:01 -0400
From: Andres Salomon <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: ultra crunchy kernel packages

--=-FHzAb8JLa4/ymT35Yokq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Since you both appear to be having a similar problem, could you try out
2.6.8-rc4 and see if the problem still occurs? If it does, please
provide the oops output/backtrace, as without that it's hard to figure
out what's happening.

I have 2.6.8-rc4 kernel packages here:
deb http://www.acm.rpi.edu/~dilinger/kernel-image-2.6.8-rc4/ ./

They will show up as 2.6.8; don't be fooled. 2.6.8 hasn't been released
yet ;)

--=20
Andres Salomon <email address hidden>

--=-FHzAb8JLa4/ymT35Yokq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBHaKk78o9R9NraMQRAhPmAKCqZQjFxrwKvI6rZpyFq02NGH6gtwCfQBhf
g9j0/wdj34zx7pD4BGQyddA=
=0NhP
-----END PGP SIGNATURE-----

--=-FHzAb8JLa4/ymT35Yokq--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 14 Aug 2004 11:50:08 +0100
From: Martin Michlmayr <email address hidden>
To: Andres Salomon <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#257542: ultra crunchy kernel packages

* Andres Salomon <email address hidden> [2004-08-14 01:27]:
> To: <email address hidden>, <email address hidden>

This won't reach the bug submitters.

> Since you both appear to be having a similar problem, could you try out
> 2.6.8-rc4 and see if the problem still occurs? If it does, please
...
--
Martin Michlmayr
<email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 18 Aug 2004 01:36:32 -0400
From: Andres Salomon <email address hidden>
To: <email address hidden>,
 <email address hidden>
Subject: cdrom mounting oops

--=-ufFG85HQWzyoBQx0Sres
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Since you both appear to be having a similar problem, could you try out
2.6.8 and see if the problem still occurs? If it does, please
provide the oops output/backtrace, as without that it's hard to figure
out what's happening.

2.6.8-1 kernels should be in Debian unstable as of today.

--=20
Andres Salomon <email address hidden>

--=-ufFG85HQWzyoBQx0Sres
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBIurf78o9R9NraMQRAv23AJ9uN58cuFKOIPUu/BxAmLgV73L1NQCeJBqS
0m8h8EZUOpaKAMVyGnjFxSg=
=sH8B
-----END PGP SIGNATURE-----

--=-ufFG85HQWzyoBQx0Sres--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040819014641.GA779@davespc>
Date: Wed, 18 Aug 2004 18:46:41 -0700
From: David Lawyer <email address hidden>
To: Andres Salomon <email address hidden>, <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#257542: cdrom mounting oops

On Wed, Aug 18, 2004 at 01:36:32AM -0400, Andres Salomon wrote:
> Hi,
>
> Since you both appear to be having a similar problem, could you try out
> 2.6.8 and see if the problem still occurs? If it does, please
> provide the oops output/backtrace, as without that it's hard to figure
> out what's happening.

I installed 2.6.8-1 per above and still the same problem. I don't know
how to do oops output/backtrace. But here's what I copied from the
screen after the crash. I didn't copy any numbers.
   David Lawyer

Call Trace:
cdrom_start_read_continuation [ide_cd]
cdrom_timer_expiry
cdrom_start_read
cdrom_start_read_continuation
ide_do_rw_cdrom
start_request [ide_core]
ide_do_request
ide_timer_expiry
ide_timer_expiry [<null>]
run_timer_softirq
do_softirq
do_IRQ
common_interrupt
default_idle
default_idle
cpu_idle
start_kernel
Code: .....
Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing

> 2.6.8-1 kernels should be in Debian unstable as of today.
> Andres Salomon <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040820143831.GC9622@aesop>
Date: Fri, 20 Aug 2004 10:38:31 -0400
From: Brian Frank <email address hidden>
To: <email address hidden>
Subject: Re: Bug#257542: cdrom mounting oops

I tried running kernel-image-2.6.8-1-686 from unstable - the same
problem occurs. I do not see any oops output, as the screen simply
freezes. I have left it like that for several minutes to see if it will
eventually give oops output, but nothing.

Brian

Revision history for this message
Daniel Stone (daniels) wrote :

Er, this one's kind of difficult to resolve without finding out what kind of
hardware is involved. I'll ping the submitters through the Debian BTS.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 5 Sep 2004 03:52:21 -0700
From: Daniel Stone <email address hidden>
To: <email address hidden>,
 <email address hidden>
Subject: Hardware list?

--wOOEd1gxhwV8K3c+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi guys,
Could you please email these bugs a rough description of your current
hardware, including the output of lspci and dmesg? Descriptions of your
motherboard and CD-ROM especially would help; also if you have made any
changes to things like BIOS settings.

Cheers,
:) d

--=20
Daniel Stone <daniels@debian=
=2Eorg>
Debian: the universal operating system http://www.debia=
n.org

--wOOEd1gxhwV8K3c+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBOu/lcPClnTztfv0RAioEAKCEKKPHzimfhxohp1DQYFBODLMtWQCfba7P
3YjW2+WT1qY3it+MAyiEOHI=
=4czU
-----END PGP SIGNATURE-----

--wOOEd1gxhwV8K3c+--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (17.4 KiB)

Message-ID: <20040910162355.GA18390@aesop>
Date: Fri, 10 Sep 2004 12:23:56 -0400
From: Brian Frank <email address hidden>
To: Daniel Stone <email address hidden>, <email address hidden>
Subject: Re: Bug#263753: Hardware list?

Note that I have removed the problematic CDROM and replaced it with a
newer CD-RW which works just fine, so I can't get the output from lspci.
I have attached the dmesg output from my logs though.

HARDWARE
=3D=3D=3D=3D=3D=3D=3D=3D

CD-ROM: AOpen Model CD-924E/AKO
CPU: Intel Celeron (Mendocino) stepping 05 at 400 MHz
Motherboard: MS-6163 for ATX BX13 chipset

dmesg output (before the old CDROM was removed)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Sep 9 08:59:31 localhost syslogd 1.4.1#15: restart.
Sep 9 08:59:31 localhost kernel: klogd 1.4.1#15, log source =3D /proc/kmsg=
 started.
Sep 9 08:59:31 localhost kernel: Inspecting /boot/System.map-2.6.7-1-686
Sep 9 08:59:32 localhost kernel: Loaded 26725 symbols from /boot/System.ma=
p-2.6.7-1-686.
Sep 9 08:59:32 localhost kernel: Symbols match kernel version 2.6.7.
Sep 9 08:59:32 localhost kernel: No module symbols loaded - kernel modules=
 not enabled.=20
Sep 9 08:59:32 localhost kernel: Linux version 2.6.7-1-686 (dilinger@toast=
er.hq.voxel.net) (gcc version 3.3.4 (Debian 1:3.3.4-2)) #1 Thu Jul 8 05:36:=
53 EDT 2004
Sep 9 08:59:32 localhost kernel: BIOS-provided physical RAM map:
Sep 9 08:59:32 localhost kernel: BIOS-e820: 0000000000000000 - 0000000000=
09fc00 (usable)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 000000000009fc00 - 0000000000=
0a0000 (reserved)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 00000000000f0000 - 0000000000=
100000 (reserved)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 0000000000100000 - 0000000017=
ff0000 (usable)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 0000000017ff0000 - 0000000017=
ff3000 (ACPI NVS)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 0000000017ff3000 - 0000000018=
000000 (ACPI data)
Sep 9 08:59:32 localhost kernel: BIOS-e820: 00000000ffff0000 - 0000000100=
000000 (reserved)
Sep 9 08:59:32 localhost kernel: 0MB HIGHMEM available.
Sep 9 08:59:32 localhost kernel: 383MB LOWMEM available.
Sep 9 08:59:32 localhost kernel: On node 0 totalpages: 98288
Sep 9 08:59:32 localhost kernel: DMA zone: 4096 pages, LIFO batch:1
Sep 9 08:59:32 localhost kernel: Normal zone: 94192 pages, LIFO batch:16
Sep 9 08:59:32 localhost kernel: HighMem zone: 0 pages, LIFO batch:1
Sep 9 08:59:32 localhost kernel: DMI 2.0 present.
Sep 9 08:59:32 localhost kernel: ACPI disabled because your bios is from 0=
0 and too old
Sep 9 08:59:32 localhost kernel: You can enable it with acpi=3Dforce
Sep 9 08:59:32 localhost kernel: Built 1 zonelists
Sep 9 08:59:32 localhost kernel: Kernel command line: root=3D/dev/hda1 ro=
=20
Sep 9 08:59:32 localhost kernel: Local APIC disabled by BIOS -- reenabling.
Sep 9 08:59:32 localhost kernel: Found and enabled local APIC!
Sep 9 08:59:32 localhost kernel: Initializing CPU#0
Sep 9 08:59:32 localhost kernel: PID hash table entries: 2048 (order 11: 1=
6384 bytes)
Sep 9 08:59:32 localhost...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 18 Sep 2004 14:00:30 +0200
From: Christoph Hellwig <email address hidden>
To: <email address hidden>
Subject: adjusting priority

severity 263753 important
thanks

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <1095962127.7414.3.camel@localhost>
Date: Thu, 23 Sep 2004 13:55:27 -0400
From: Andres Salomon <email address hidden>
To: <email address hidden>,
 <email address hidden>
Subject: cdrom mounting problems

--=-JNaSAUc9f8EmI8k7mpIH
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Christoph seems to think that disabling TASKFILE_IO will help things, so
I've prepared some test kernels w/ it disabled. Please try the kernels
here: http://www.acm.rpi.edu/~dilinger/kernel-image-taskfile_io/ and let
me know whether the kernel still oopses/hangs when attempting to mount
cdroms.

--=20
Andres Salomon <email address hidden>

--=-JNaSAUc9f8EmI8k7mpIH
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBUw4P78o9R9NraMQRAgLSAKCQVFrHWK4Kag2q4QcUj6AeBQtJNgCeIo21
tv2KW7Q0O+XY6jtvV6DJoRk=
=G9nx
-----END PGP SIGNATURE-----

--=-JNaSAUc9f8EmI8k7mpIH--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040924185134.GB805@davespc>
Date: Fri, 24 Sep 2004 11:51:34 -0700
From: David Lawyer <email address hidden>
To: Andres Salomon <email address hidden>, <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#257542: cdrom mounting problems

On Thu, Sep 23, 2004 at 01:55:27PM -0400, Andres Salomon wrote:
> Hi,
>
> Christoph seems to think that disabling TASKFILE_IO will help things, so
> I've prepared some test kernels w/ it disabled. Please try the kernels
> here: http://www.acm.rpi.edu/~dilinger/kernel-image-taskfile_io/ and let
> me know whether the kernel still oopses/hangs when attempting to mount
> cdroms.

I downloaded (using an analog modem --slow)
kernel-image-2.6.8-1-386_2.6.8-3.1_i386.deb. Then I installed it and
ran it. Still the same problem. It takes about a minute after one gives
the "mount" command until the system crashes. I ran: strace mount /cd
and the last line from strace was:
mount("/dev/hdc", "/cd", "iso9660", MS_RDONLY|0xc0ed0000, 0x805d758

So the system call "mount" is made, never to return (no return value
shown). I suppose that a closing ) for the mount command is added
when the return value is written by strace. Since no return value, no
closing ) is shown above.

> -- Andres Salomon <email address hidden>

   David Lawyer

Revision history for this message
Matt Zimmerman (mdz) wrote :

Bug is still present in 2.6.8.1 for the submitter, but apparently no one has
seen this in Ubuntu, and the cause is not at all clear. Doesn't affect enough
users to be major.

Revision history for this message
Daniel Stone (daniels) wrote :

No feedback, and no other reports of this problem. Weird.

Changed in linux-source-2.6.15:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.