diff options
| author | Rachita Kothiyal <rachita@in.ibm.com> | 2006-06-23 13:02:56 +0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-23 18:42:44 +0400 |
| commit | 1ad5544098a69d7dc1fa508cbb17e13a7a952fd8 (patch) | |
| tree | 60eb468a15572cbecd167286b5a91d22e8bd1710 /fs/adfs | |
| parent | 5fa21d821f6972e70942f2c555ec29dde962bdb2 (diff) | |
| download | linux-1ad5544098a69d7dc1fa508cbb17e13a7a952fd8.tar.xz | |
[PATCH] Fix cdrom being confused on using kdump
I have seen the cdrom drive appearing confused on using kdump on certain
x86_64 systems. During the booting up of the second kernel, the following
message would keep flooding the console, and the booting would not proceed
any further.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
In this patch, whenever we are hitting a confused state in the interrupt
handler with the DRQ set, we end the request and return ide_stopped. Using
this I dont see the status error.
Signed-off-by: Rachita Kothiyal <rachita@in.ibm.com>
Acked-by: Jens Axboe <axboe@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/adfs')
0 files changed, 0 insertions, 0 deletions