mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sergey Dolgov" <dolgovs@gmail.com>
To: "Tejun Heo" <htejun@gmail.com>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ata_piix, laptop cdrom, ICH7: EH, limiting speed to PIO
Date: Mon, 17 Sep 2007 13:57:43 +0400	[thread overview]
Message-ID: <ac0be4d70709170257o62e856f4re049c968ab5590a7@mail.gmail.com> (raw)
In-Reply-To: <46ED19F0.8060205@gmail.com>

On 9/16/07, Tejun Heo <htejun@gmail.com> wrote:
> Michal Piotrowski wrote:
> > Sergey Dolgov pisze:
> >> On Wed, Sep 12, 2007 at 10:19:03PM +0200, Michal Piotrowski wrote:
> >>> Sergey Dolgov pisze:
> >>>> Hi Michal,
> >>>>
> >>>> On Wed, Sep 12, 2007 at 06:33:20PM +0200, Michal Piotrowski wrote:
> >>>>> Hi Sergey,
> >>>>>
> >>>>> On 11/09/2007, Sergey Dolgov <dolgovs@gmail.com> wrote:
> >>>>>> Hi!
> >>>>>>
> >>>>>> On my hp nx7300 laptop, 2 following scenarios can happen during bootup
> >>>>>> (see attachments for the full logs): the "good" one [1] and the one
> >>>>>> where multiple EHs lead to limiting the speed [2].
> >>>>>>
> >>>>>> [1] one is more rare, but it seems to be persistent over reboots: once
> >>>>>> it happened, just rebooting the machine always results in behaviour
> >>>>>> like [1].
> >>>>>>
> >>>>>> [1] results in a working cdrom from the start. An attempt to use cdrom
> >>>>>> after [2] happened results in even more EHs, resulting in "configured
> >>>>>> for PIO4", after which the cdrom is finaly working.
> >>>>>>
> >>>>>> The version I'm using is 2.6.23-rc6, but the same used to happen with
> >>>>>> the previous rc's, and probably with 2.6.22 too (I can check).
> >>>>> It would be great if you could check it.
> >>>> I've just built 2.6.22.6 with basically the same configuration, and
> >>>> the behaviour is just the same, i.e. both [1] and [2] still can
> >>>> happen.
> >>> Ok, thanks.
> >>>
> >>> BTW please check cables and PCU.
> >> What's a PCU?
> >
> > s/PCU/PSU - power supply unit
> >
> >> BTW, this only happens when using libata of course. The
> >> old CONFIG_IDE stuff works fine every time.
> >
> > This maybe one of libata weirdness (I really don't get it why some hardware
> > works perfectly fine with an old IDE and don't work well with libata).
>
> Hmmm... Is MWDMA2 mode used with ide driver too?
>

What's the best way to tell whether it does or not? (the log says
"selected mode 0x22", see below)

[    9.267682] ICH7: IDE controller at PCI slot 0000:00:1f.1
[    9.267776] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level,
low) -> IRQ 16
[    9.267928] ICH7: chipset revision 1
[    9.267998] ICH7: not 100% native mode: will probe irqs later
[    9.268088]     ide0: BM-DMA at 0x40a0-0x40a7, BIOS settings:
hda:DMA, hdb:pio
[    9.268286] Probing IDE interface ide0...
[    9.301139] USB Universal Host Controller Interface driver v3.0
[    9.307592] SCSI subsystem initialized
[    9.325583] libata version 2.21 loaded.
[    9.331069] Clocksource tsc unstable (delta = -127737806 ns)
[    9.333292] hda: HL-DT-ST DVDRAM GSA-T10N, ATAPI CD/DVD-ROM drive
[    9.333533] PM: Adding info for No Bus:ide0
[    9.335577] hda: selected mode 0x22
[    9.336161] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

-- 
Sergey

  reply	other threads:[~2007-09-17  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 21:21 Sergey Dolgov
2007-09-12 16:33 ` Michal Piotrowski
2007-09-12 20:07   ` Sergey Dolgov
2007-09-12 20:19     ` Michal Piotrowski
2007-09-12 21:20       ` Sergey Dolgov
2007-09-12 22:20         ` Michal Piotrowski
2007-09-16 11:56           ` Tejun Heo
2007-09-17  9:57             ` Sergey Dolgov [this message]
2007-09-17 11:37               ` Tejun Heo
2007-09-17 12:05                 ` Sergey Dolgov
2007-09-17 17:18                   ` Alexey Zaytsev
2007-09-18 18:05                     ` Sergey Dolgov

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=ac0be4d70709170257o62e856f4re049c968ab5590a7@mail.gmail.com \
    --to=dolgovs@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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®