All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Masoud Sharbiani \"مسعود شربیانی\"" <masouds@masoud.ir>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: bzolnier@gmail.com, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: HPT374 detection crash with 74811f355f4f69a187fa74892dcf2a684b84ce99
Date: Fri, 5 Sep 2008 09:32:43 -0700	[thread overview]
Message-ID: <1a9da18c0809050932x1d42d74co64416bf4ce99d40b@mail.gmail.com> (raw)
In-Reply-To: <48C15F07.6000501@ru.mvista.com>

On Fri, Sep 5, 2008 at 9:32 AM, Sergei Shtylyov <sshtylyov@ru.mvista.com> wrote:
> Hello, I just wrote:
>
>>> Hi there, Looks like your commit 74811f355f4f69a187fa74892dcf2a684b84ce99
>>>  (hpt366: convert to use ->host_priv)
>
>>   Thanks for doing the bisection.
>
>>> has caused the following crash:
>
>>   Oops, we did it again. :-)
>
>   Already seeing Bart's mistake, see below:
>
>>> (Full dmesg follows, as captured from a serial console)
>
>>> [   22.555200] hpt366: HPT374 chipset detected
>>> [   22.559489] hpt366 0000:03:06.0: IDE controller (0x1103:0x0008 rev
>>> 0x07)
>>> [   22.566278] HPT366_IDE 0000:03:06.0: PCI INT A -> GSI 28 (level, low)
>>> -> IRQ 28
>>> [   22.573729] usb 1-2: new full speed USB device using uhci_hcd and
>>> address 4
>>> [   22.580726] pci 0000:03:06.1: PCI INT A -> GSI 28 (level, low) -> IRQ
>>> 28
>>> [   22.587529] hpt366 0000:03:06.0: DPLL base: 48 MHz, f_CNT: 142,
>>> assuming 33 MHz PCI
>>> [   22.602705] hpt366 0000:03:06.0: using 50 MHz DPLL clock
>>> [   22.608181] hpt366 0000:03:06.0: 100% native mode on irq 28
>>> [   22.613831] hpt366 0000:03:06.1: no clock data saved by BIOS
>
>>   Aha, HPT374 workaround for reading BIOS clock data didn't get executed.
>
>>> [   22.731015] usb 1-2: configuration #1 chosen from 1 choice
>>> [   22.737191] ata2.00: ATA-6: ST3120022A, 3.04, max UDMA/100
>>> [   22.738880] hub 1-2:1.0: USB hub found
>>> [   22.746597] ata2.00: 234441648 sectors, multi 16: LBA48
>>> [   22.747804] hpt366 0000:03:06.1: DPLL base: 33 MHz, f_CNT: 139,
>>> assuming
>
>>   Uh, I wonder where did it get those 33 MHz DPLL base -- there's simply
>> no such base.  Looks like memory addressed by .host_priv got corrupt...
>
>   No, that's just wrong pointer arithmetics there:
>
>       struct hpt_info *info = host->host_priv + (hwif->dev == host->dev[1]);
>
> The 'host_priv' is declared as 'void *', hence in case the condition abobe
> is true, there will be added only 1 to host->host_priv, not sizeof(struct
> hpt_info) as it should've been...
>

Hey I can try that now....stay tuned.

Masoud
> MBR, Sergei
>
>

      reply	other threads:[~2008-09-05 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1a9da18c0809041610tb3f2a58r6acd6f10a3d50a91@mail.gmail.com>
2008-09-04 23:11 ` HPT374 detection crash with 74811f355f4f69a187fa74892dcf2a684b84ce99 Masoud Sharbiani "مسعود شربیانی"
2008-09-05 16:16 ` Sergei Shtylyov
2008-09-05 16:16 ` Sergei Shtylyov
2008-09-05 16:32   ` Sergei Shtylyov
2008-09-05 16:32     ` Masoud Sharbiani "مسعود شربیانی" [this message]

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=1a9da18c0809050932x1d42d74co64416bf4ce99d40b@mail.gmail.com \
    --to=masouds@masoud.ir \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.