From: Adam Kropelin <akropel1@rochester.rr.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Norbert Kiesel <nkiesel@tbdnetworks.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
Date: Tue, 13 Sep 2005 12:02:55 -0400 [thread overview]
Message-ID: <20050913120255.A16713@mail.kroptech.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509130755280.3351@g5.osdl.org>
On Tue, 13 Sep 2005, Linus Torvalds wrote:
> On Tue, 13 Sep 2005, Linus Torvalds wrote:
> >
> > I bet this will fix it..
>
> Btw, there's a third case of this in the hpt34x driver. I'll fix that
> one too.
That made me do some grepping of my own. Nothing obvious, but this bit
from drivers/scsi/qla2xxx/qla_init.c seems a little odd:
uint16_t w, mwi;
...
/* Reset expansion ROM address decode enable */
pci_read_config_word(ha->pdev, PCI_ROM_ADDRESS, &w);
w &= ~PCI_ROM_ADDRESS_ENABLE;
pci_write_config_word(ha->pdev, PCI_ROM_ADDRESS, w);
Is the address register really only 16 bits wide on some hw?
--Adam
next prev parent reply other threads:[~2005-09-13 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 23:59 2.6.13.1 locks machine after some time, 2.6.12.5 work fine Norbert Kiesel
2005-09-13 3:00 ` Linus Torvalds
2005-09-13 3:38 ` Norbert Kiesel
2005-09-13 14:25 ` Linus Torvalds
2005-09-13 14:57 ` Linus Torvalds
2005-09-13 16:02 ` Adam Kropelin [this message]
2005-09-13 15:55 ` Linus Torvalds
2005-09-13 20:22 ` David S. Miller
2005-09-13 22:25 ` Adam Kropelin
2005-09-13 23:11 ` [PATCH] ibmphp: Use dword accessors for PCI_ROM_ADDRESS Adam Kropelin
2005-09-13 23:15 ` [PATCH] pciehp: " Adam Kropelin
2005-09-13 23:17 ` [PATCH] shpchp: " Adam Kropelin
2005-09-13 23:20 ` [PATCH] qla2xxx: " Adam Kropelin
2005-09-13 16:27 ` 2.6.13.1 locks machine after some time, 2.6.12.5 work fine Norbert Kiesel
2005-09-13 17:09 ` Norbert Kiesel
2005-09-13 17:23 ` Linus Torvalds
2005-09-13 21:23 ` Norbert Kiesel
2005-09-13 22:24 ` Chris Wright
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=20050913120255.A16713@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nkiesel@tbdnetworks.com \
--cc=torvalds@osdl.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