From: Greg KH <greg@kroah.com>
To: marcel cotta <mc123@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 - Badness in pci_find_subsys at drivers/pci/search.c:167
Date: Tue, 24 Feb 2004 14:30:43 -0800 [thread overview]
Message-ID: <20040224223043.GA2455@kroah.com> (raw)
In-Reply-To: <403B7627.6080805@mail.ru>
On Tue, Feb 24, 2004 at 05:04:55PM +0100, marcel cotta wrote:
> i came across this while playing with hdparm
>
> Call Trace:
> [<c0264128>] pci_find_subsys+0xe8/0xf0
> [<c026415f>] pci_find_device+0x2f/0x40
> [<c02e5d89>] ide_system_bus_speed+0x69/0x90
> [<c02e528e>] ali15x3_tune_drive+0x1e/0x250
Ugh, this is due to calling system_bus_clock() from within an interrupt.
Is there any good reason to do this? Can't we just cache the bus speed
in the local device structure if we really have to do this from within
an interrupt?
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-24 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 16:04 2.6.3 - Badness in pci_find_subsys at drivers/pci/search.c:167 marcel cotta
2004-02-24 22:30 ` Greg KH [this message]
2004-02-24 23:55 ` Bartlomiej Zolnierkiewicz
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=20040224223043.GA2455@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mc123@mail.ru \
/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