lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 19 Jan 2009 22:44:11 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	kernel list <linux-kernel@...r.kernel.org>, teheo@...ell.com,
	trenn@...e.de, Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-ide@...r.kernel.org
Subject: Re: 2.6.29-rc2: thinkpad dock -- cdrom vs. s2ram

On Mon 2009-01-19 21:50:58, Rafael J. Wysocki wrote:
> On Monday 19 January 2009, Pavel Machek wrote:
> > Hi!
> > 
> > In 2.6.29 (and probably earlier) kernels, booting in docking station
> > results in undocked s2ram failing.
> > 
> > Problem seems to be that hda (cdrom in dock) is not deregistered
> > during undock, and that hda driver loops spitting error messages at
> > 'too-fast-to-read' rate when suspend with missing hda is attempted.
> 
> What driver do you mean exactly?  Old-IDE I would guess.

piix. hda, so I guess it is old-ide:

piix 0000:00:1f.1: IDE controller (0x8086:0x27df rev 0x02)
pci 0000:00:1f.1: PCI INT C -> GSI 16 (level, low) -> IRQ 16
piix 0000:00:1f.1: IDE port disabled
piix 0000:00:1f.1: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1810-0x1817
Probing IDE interface ide0...
hda: UJDA765 DVD/CDRW, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide_generic: please use "probe_mask=0x3f" module parameter for probing
all legacy ISA IDE ports
ide-gd driver 1.18
ide-cd driver 5.00
ide-cd: hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20

If I try to access cdrom after undocking, I get:

hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
ide-cd: hda: weird block size 0
ide-cd: hda: default to 2kb block size
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted
hda: status error: status=0x20 { DeviceFault }
ide: failed opcode was: unknown
hda: Strange, packet command initiated yet DRQ isn't asserted

...something similar scrolls when it hangs during s2ram, but it is too
fast to read.

> Does this also happen with a PATA/libata driver?

Will try...
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ