From: Giovanni Pancotti <gpanco@tiscali.it>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-ide@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
stable@kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [Bugme-new] [Bug 12351] New: sata_nv hotplug not work in 2.6.27.10
Date: Tue, 6 Jan 2009 11:27:58 +0100 [thread overview]
Message-ID: <20090106102758.GA7309@libero.it> (raw)
In-Reply-To: <4962AC5C.1000605@shaw.ca>
On Monday 05 January 2009, alle 18:57, Robert Hancock wrote:
>>> Hardware Environment:x86 ASUS M2N-E
>
> OK, this is an MCP61 board. We're now using softreset instead of hardreset
> on hotplug and apparently that doesn't work. Thing is that:
no, it is not MCP61, but MCP55:
dual ~ # lspci
00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
dual ~ # dmidecode
# dmidecode 2.9
SMBIOS 2.4 present.
72 structures occupying 2069 bytes.
Table at 0x000F0000.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies, LTD
Version: ASUS M2N-E ACPI BIOS Revision 1601
next prev parent reply other threads:[~2009-01-06 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12351-10286@http.bugzilla.kernel.org/>
2009-01-05 23:36 ` [Bugme-new] [Bug 12351] New: sata_nv hotplug not work in 2.6.27.10 Andrew Morton
2009-01-06 0:57 ` Robert Hancock
2009-01-06 10:27 ` Giovanni Pancotti [this message]
2009-01-07 0:19 ` Robert Hancock
2009-01-15 18:45 ` [stable] " Greg KH
2009-01-17 2:38 ` Robert Hancock
2009-02-02 22:55 ` Greg KH
2009-02-03 2:04 ` Robert Hancock
2009-02-03 22:21 ` Greg KH
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=20090106102758.GA7309@libero.it \
--to=gpanco@tiscali.it \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).