From: Roger Oberholtzer <roger@opq.se>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata question
Date: Tue, 01 Aug 2006 20:39:42 +0200 [thread overview]
Message-ID: <1154457583.4665.5.camel@shark.pacific> (raw)
In-Reply-To: <44CF7447.300@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2878 bytes --]
On Wed, 2006-08-02 at 00:33 +0900, Tejun Heo wrote:
> Roger Oberholtzer wrote:
> > Should hotplug work with Intel Corporation 82801GB/GR/GH (ICH7
> > Family) chipset? I am trying kernel 2.6.17.7
> >
> > I have been trying the warmplug stuff. But I am not convinced it is
> > acting as I expect. If I remove a disk and then do a scan, shouldn't
> > the disk entry go away?
>
> Eventually, yes. Do you mind to send me the dmesg?
I have picked out the lines related to this. Some of the complaints at
the end are probably when I moved the disk.
> > I know about the problems with just removing a disk. But this is with
> > one that is not mounted. I just want to see if the disks are properly
> > sensed as coming and going. I am using the warmplug instructions on
> > your web site.
>
> There are some complications with piix PCS register (port
> enable/disable) which always seems to have some problem. If you can use
> AHCI mode, it will be *much* better.
OK. How do I get it in ahci mode? I see that both the ata_piix and achi
drivers are loaded. This is what is loaded:
Module Size Used by
xfs 465784 0
af_packet 28040 2
ipv6 238368 18
nfsd 202244 9
exportfs 9600 1 nfsd
lockd 57992 2 nfsd
nfs_acl 7680 1 nfsd
sunrpc 142524 9 nfsd,lockd,nfs_acl
edd 12740 0
loop 18824 0
dm_mod 54936 0
usbhid 47328 0
ehci_hcd 32008 0
shpchp 38304 0
uhci_hcd 24588 0
e1000 104888 0
pci_hotplug 31548 1 shpchp
usbcore 115968 4 usbhid,ehci_hcd,uhci_hcd
ide_cd 39712 0
cdrom 36640 1 ide_cd
i2c_i801 12172 0
i2c_core 23552 1 i2c_i801
parport_pc 39780 1
lp 15140 0
parport 37320 2 parport_pc,lp
ext3 125576 2
jbd 64032 1 ext3
sg 35996 0
ata_piix 15492 0
ahci 18436 0
processor 30056 0
libata 65676 2 ata_piix,ahci
piix 13444 0 [permanent]
sd_mod 22656 0
scsi_mod 127624 4 sg,ahci,libata,sd_mod
ide_disk 19072 4
ide_core 118344 3 ide_cd,piix,ide_disk
> If you think the driver doesn't do the right thing(tm), please send me
> detailed info. I'll try to fix the problem if possible or explain why
> it can't be fixed at the very least.
I bet the driver does the right thing. The trick is knowing what that is
supposed to be. And how to use the various commands on files in /sys at
the correct time and in the correct order.
--
Roger Oberholtzer
[-- Attachment #2: m.txt.gz --]
[-- Type: application/x-gzip, Size: 3477 bytes --]
next prev parent reply other threads:[~2006-08-01 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 15:18 libata question Roger Oberholtzer
2006-08-01 15:33 ` Tejun Heo
2006-08-01 18:39 ` Roger Oberholtzer [this message]
2006-08-01 18:45 ` Tejun Heo
2006-08-01 19:03 ` Roger Oberholtzer
2006-08-01 19:06 ` Tejun Heo
2006-08-02 7:05 ` Roger Oberholtzer
2006-08-02 7:20 ` Tejun Heo
2006-08-02 8:06 ` Roger Oberholtzer
2006-08-02 14:35 ` Roger Oberholtzer
2006-08-02 15:02 ` Tejun Heo
2006-08-03 7:26 ` Roger Oberholtzer
2006-08-03 7:58 ` Tejun Heo
2006-08-03 8:49 ` Roger Oberholtzer
2006-08-03 20:08 ` Stefan Smietanowski
2006-08-02 1:22 ` 31244 PCI Card sam song
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=1154457583.4665.5.camel@shark.pacific \
--to=roger@opq.se \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.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 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.