From: Bob McElrath <mcelrath+kernel@draal.physics.wisc.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide-scsi oops
Date: Sat, 7 Sep 2002 13:33:29 -0500 [thread overview]
Message-ID: <20020907183328.GB5985@draal.physics.wisc.edu> (raw)
In-Reply-To: <1031421665.14390.2.camel@irongate.swansea.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 6067 bytes --]
Alan Cox [alan@lxorguk.ukuu.org.uk] wrote:
> On Sat, 2002-09-07 at 17:37, Bob McElrath wrote:
> > Kernel 2.4.20-pre5-ac4 with the latest ACPI patches gives me an oops any
> > time I try to access the CD-ROM:
> >
> > Note this also happened with pre4-ac1 so I don't think it's due to the
> > latest IDE merge in pre5-ac4.
>
> Yes. What were you doing to trigger it. Also do you have highio/highmem
> stuff enabled and is taskfile on or off ?
Highmem is not used (this machine has 'only' 512M). Not sure what
highio is but I did NOT pass the option "idex=nohighio" to the kernel
(mentioned in Documentation/ide.txt). I'm not sure what taskfile is
either.
(2)<mcelrath@navi:/usr/src/linux/Documentation> grep -i high
../.config
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
(1)<mcelrath@navi:/usr/src/linux/Documentation> grep -i task ../.config
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
My boot command line is:
(0)<mcelrath@navi:/usr/src/linux/Documentation> cat /proc/cmdline
auto BOOT_IMAGE=2.4.20pre5ac4 ro root=302 BOOT_FILE=/boot/vmlinuz-2.4.20-pre5-ac3 hdc=ide-scsi resume=/dev/hda4
^^^^^^^^^^^^
ac3/ac4 confusion is because you must have forgotten to increment that
number in the Makefile (but you probably know that already). This is
pre5-ac4. resume= is not used as I did not compile swsusp into this
kernel.
> I'm having real trouble reproducing this problem although enough people
> see it thats its clearly quite real
I can mount the drive successfully, the oops is triggered by the first
attempt at a read on the drive. i.e. less /mnt/cdrom/<first file>
There are probably other ways to trigger it. But reading the first file
oopses 100%.
Here is the contents of /proc/ide that might be relevant: My DVD/CD-RW is
drive0 on the second channel.
(0)<mcelrath@navi:/home/mcelrath> cat /proc/ide/piix
Controller: 0
Intel PIIX4 Ultra 100 Chipset.
--------------- Primary Channel ---------------- Secondary Channel -------------
enabled enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------
DMA enabled: yes no yes no
UDMA enabled: yes no no no
UDMA enabled: 5 X X X
UDMA
DMA
PIO
(0)<mcelrath@navi:/home/mcelrath> cat /proc/ide/drivers
ide-scsi version 0.93
ide-cdrom version 4.59
ide-disk version 1.16
(0)<mcelrath@navi:/home/mcelrath> sudo cat /proc/ide/ide1/hdc/capacity
2147483647
(0)<mcelrath@navi:/home/mcelrath> sudo cat /proc/ide/ide1/hdc/identify
85c0 0000 0000 0000 0000 0000 0000 0000
0000 0000 3432 3434 3430 3734 3636 2020
2020 2020 2020 2020 0000 1000 0000 3130
3136 2020 2020 544f 5348 4942 4120 4456
442d 524f 4d20 5344 2d52 3231 3032 2020
2020 2020 2020 2020 2020 2020 2020 0000
0000 0f00 0000 0400 0200 0006 0000 0000
0000 0000 0000 0000 0000 0000 0000 0407
0003 0078 0078 0078 0078 0000 0000 0000
0000 0004 0009 0000 0000 0000 0000 0000
003c 0013 0000 0000 0000 0000 0000 0000
0007 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 fffe 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
(0)<mcelrath@navi:/home/mcelrath> sudo cat /proc/ide/ide1/hdc/media
cdrom
(0)<mcelrath@navi:/home/mcelrath> sudo cat /proc/ide/ide1/hdc/model
TOSHIBA DVD-ROM SD-R2102
(0)<mcelrath@navi:/home/mcelrath> sudo cat /proc/ide/ide1/hdc/settings
name value min max mode
---- ----- --- --- ----
bios_cyl 0 0 1023 rw
bios_head 0 0 255 rw
bios_sect 0 0 63 rw
current_speed 34 0 70 rw
ide-scsi 0 0 1 rw
init_speed 66 0 70 rw
io_32bit 1 0 3 rw
keepsettings 1 0 1 rw
log 0 0 1 rw
nice1 1 0 1 rw
number 2 0 3 rw
pio_mode write-only 0 255 w
slow 0 0 1 rw
transform 1 0 3 rw
unmaskirq 0 0 1 rw
using_dma 1 0 1 rw
Cheers,
-- Bob
Bob McElrath
Univ. of Wisconsin at Madison, Department of Physics
"No nation could preserve its freedom in the midst of continual warfare."
--James Madison, April 20, 1795
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-09-07 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 16:37 Bob McElrath
2002-09-07 18:01 ` Alan Cox
2002-09-07 18:26 ` Andre Hedrick
2002-09-07 18:33 ` Bob McElrath [this message]
2002-09-07 18:47 ` Andre Hedrick
2002-09-08 0:50 ` Bob McElrath
2002-09-08 1:30 ` Art Wagner
2002-09-08 1:01 ` Bob McElrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020907183328.GB5985@draal.physics.wisc.edu \
--to=mcelrath+kernel@draal.physics.wisc.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®