Hi all,
HDD LED on my Laptop (Fujitsu-Siemens LB E8020) never goes off when 2.6 kernel
is running (tested with 2.6.10-2.6.13.4).
My controller is:
$ lspci | grep SATA
0000:00:1f.2 0106: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 04)
This is from my dmesg:
ahci(0000:00:1f.2) AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0x5 impl SATA mode
ahci(0000:00:1f.2) flags: 64bit ncq pm led slum part
ata1: SATA max UDMA/133 cmd 0xE0820D00 ctl 0x0 bmdma 0x0 irq 225
ata2: SATA max UDMA/133 cmd 0xE0820D80 ctl 0x0 bmdma 0x0 irq 225
ata3: SATA max UDMA/133 cmd 0xE0820E00 ctl 0x0 bmdma 0x0 irq 225
ata4: SATA max UDMA/133 cmd 0xE0820E80 ctl 0x0 bmdma 0x0 irq 225
ata1: dev 0 cfg 49:2f00 82:346b 83:7f09 84:6063 85:3469 86:3f09 87:6063
88:203f
ata1: dev 0 ATA, max UDMA/100, 156301488 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : ahci
ata2: no device found (phy stat 00000000)
scsi1 : ahci
ata3: no device found (phy stat 00000000)
scsi2 : ahci
ata4: no device found (phy stat 00000000)
scsi3 : ahci
Vendor: ATA Model: FUJITSU MHT2080B Rev: 0000
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Is this common problem?
thanx
-michal
On Mon, Oct 31 2005, Michal Vanco wrote:
> Hi all,
>
> HDD LED on my Laptop (Fujitsu-Siemens LB E8020) never goes off when
> 2.6 kernel is running (tested with 2.6.10-2.6.13.4).
It's a bug in the ahci driver, which coincidentally is fixed with
2.6.14. So you should upgrade :)
--
Jens Axboe
Dňa Monday 31 October 2005 20:05 Jens Axboe napísal:
> On Mon, Oct 31 2005, Michal Vanco wrote:
> > Hi all,
> >
> > HDD LED on my Laptop (Fujitsu-Siemens LB E8020) never goes off when
> > 2.6 kernel is running (tested with 2.6.10-2.6.13.4).
>
> It's a bug in the ahci driver, which coincidentally is fixed with
> 2.6.14. So you should upgrade :)
:) thanks ... i should read changelogs :)
-m