Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
Tejun Heo a écrit : > Jeff Garzik wrote: > > Mathieu, just to be sure, can you post the result of 'hdparm -I > /dev/sdX' and 'lspci -nn'? > Hi, no problem : lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03) 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3) 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 03) 00:1e.3 Modem [0703]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller [8086:266d] (rev 03) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03) 00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03) 00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M24 [Radeon Mobility X600] [1002:5462] 06:01.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) 06:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG Network Connection [8086:4220] (rev 05) 06:04.0 CardBus bridge [0607]: Texas Instruments PCIxx21/x515 Cardbus Controller [104c:8031] 06:04.2 FireWire (IEEE 1394) [0c00]: Texas Instruments OHCI Compliant IEEE 1394 Host Controller [104c:8032] 06:04.3 Mass storage controller [0180]: Texas Instruments PCIxx21 Integrated FlashMedia Controller [104c:8033] 06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller [104c:8034] hdparm -I /dev/sda: /dev/sda: ATA device, with non-removable media Model Number: HTS541010G9SA00 Serial Number: MP2ZM4X0GSWJKR Firmware Revision: MBZOC60D Standards: Used: ATA/ATAPI-7 T13 1532D revision 1 Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 195371568 LBA48 user addressable sectors: 195371568 device size with M = 1024*1024: 95396 MBytes device size with M = 1000*1000: 100030 MBytes (100 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Vendor, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Advanced power management level: 128 (0x80) Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE *Advanced Power Management feature set Power-Up In Standby feature set *SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *
Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
Tejun Heo a écrit : Jeff Garzik wrote: Mathieu, just to be sure, can you post the result of 'hdparm -I /dev/sdX' and 'lspci -nn'? Hi, no problem : lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03) 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3) 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 03) 00:1e.3 Modem [0703]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller [8086:266d] (rev 03) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03) 00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03) 00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M24 [Radeon Mobility X600] [1002:5462] 06:01.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) 06:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG Network Connection [8086:4220] (rev 05) 06:04.0 CardBus bridge [0607]: Texas Instruments PCIxx21/x515 Cardbus Controller [104c:8031] 06:04.2 FireWire (IEEE 1394) [0c00]: Texas Instruments OHCI Compliant IEEE 1394 Host Controller [104c:8032] 06:04.3 Mass storage controller [0180]: Texas Instruments PCIxx21 Integrated FlashMedia Controller [104c:8033] 06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller [104c:8034] hdparm -I /dev/sda: /dev/sda: ATA device, with non-removable media Model Number: HTS541010G9SA00 Serial Number: MP2ZM4X0GSWJKR Firmware Revision: MBZOC60D Standards: Used: ATA/ATAPI-7 T13 1532D revision 1 Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 195371568 LBA48 user addressable sectors: 195371568 device size with M = 1024*1024: 95396 MBytes device size with M = 1000*1000: 100030 MBytes (100 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Vendor, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Advanced power management level: 128 (0x80) Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE *Advanced Power Management feature set Power-Up In Standby feature set *SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit : > Hello, > > > Due to blacklisting, NCQ > won't be turned on your drive in future kernels. > > Hello thanks. I have found on Hitachi website the technical datasheets of my drive model: http://www.hitachigst.com/tech/techlib.nsf/techdocs/28DCCB17E0EEC5A086256F4E006E2F5B/$file/5K100_SATA_sp1.2.pdf It seems to state that the drive does not support NCQ... -- Mathieu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit : Hello, Due to blacklisting, NCQ won't be turned on your drive in future kernels. Hello thanks. I have found on Hitachi website the technical datasheets of my drive model: http://www.hitachigst.com/tech/techlib.nsf/techdocs/28DCCB17E0EEC5A086256F4E006E2F5B/$file/5K100_SATA_sp1.2.pdf It seems to state that the drive does not support NCQ... -- Mathieu - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit : > Can you apply the attached patch and report what the kernel says with > ACPI turned on? > > Hi, I got this: [ 13.523816] SCSI subsystem initialized [ 13.528914] ACPI: PCI Interrupt :00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19 [ 14.529383] ahci :00:1f.2: AHCI 0001. 32 slots 4 ports 1.5 Gbps 0x5 impl IDE mode [ 14.529439] ahci :00:1f.2: flags: 64bit ncq pm led slum part [ 14.529565] ata1: SATA max UDMA/133 cmd 0xf8824d00 ctl 0x bmdma 0x irq 19 [ 14.529683] ata2: SATA max UDMA/133 cmd 0xf8824d80 ctl 0x bmdma 0x irq 19 [ 14.529801] ata3: SATA max UDMA/133 cmd 0xf8824e00 ctl 0x bmdma 0x irq 19 [ 14.529921] ata4: SATA max UDMA/133 cmd 0xf8824e80 ctl 0x bmdma 0x irq 19 [ 14.529984] scsi0 : ahci [ 14.987273] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 15.032119] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100 [ 15.032168] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 15.034170] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 15.034464] ata1.00: configured for UDMA/100 [ 15.034515] scsi1 : ahci [ 15.337188] ata2: SATA link down (SStatus 0 SControl 0) [ 15.337241] scsi2 : ahci [ 15.640125] ata3: SATA link down (SStatus 0 SControl 300) [ 15.640178] scsi3 : ahci [ 15.943062] ata4: SATA link down (SStatus 0 SControl 0) [ 15.943191] scsi 0:0:0:0: Direct-Access ATA HTS541010G9SA00 MBZO PQ: 0 ANSI: 5 and for each ata errors: [ 47.089624] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen [ 47.089682] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 in [ 47.089684] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 47.392549] ata1: soft resetting port [ 47.547533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 47.549756] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 47.552600] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 47.552969] ata1.00: configured for UDMA/100 [ 47.553022] ata1: EH complete [ 47.553104] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 47.553160] sda: Write Protect is off [ 47.553226] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA -- Mathieu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit :
> > Mathieu Bérard wrote:
>> >> Jeff Garzik a écrit :
>>> >>> Adrian Bunk wrote:
>>>> >>>> Subject: NCQ problem with ahci and Hitachi drive
>>>> >>>> References : http://lkml.org/lkml/2007/3/4/178
>>>> >>>> Submitter : Mathieu Bérard <[EMAIL PROTECTED]>
>>>> >>>> Status : unknown
>>> >>> according to the last message in that thread, it sounds like
ACPI and
>>> >>> interrupt problems
>>> >>>
>> >> Hi,
>> >> after more testing with a 2.6.21-rc3, it appears that after
several ata
>> >> errors the boot process
>> >> somehow continued as normal, after a "NCQ disabled due to excessive
>> >> errors" message.
>> >> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
>> >> does nothing.
> >
> > I was mistaken. It can't be IRQ routing problem. I somehow thought the
> > port was a ata_piix one. Considering the reported broken NCQ feature on
> > the device GTF might be mangling with the drive to disable NCQ or
> > something. Does giving "libata.noacpi=1" make any difference?
> >
Hi,
libata.noacpi=1 worked. The drive is up and running with NCQ on.
Here is the PATA/SATA related part of my DSDT table with the _GTF methods:
Device (PATA)
{
Name (_ADR, 0x001F0001)
OperationRegion (PACS, PCI_Config, 0x40, 0xC0)
Field (PACS, DWordAcc, NoLock, Preserve)
{
PRIT, 16,
Offset (0x04),
PSIT, 4,
Offset (0x08),
SYNC, 4,
Offset (0x0A),
SDT0, 2,
, 2,
SDT1, 2,
Offset (0x14),
ICR0, 4,
ICR1, 4,
ICR2, 4,
ICR3, 4,
ICR4, 4,
ICR5, 4
}
Device (PRID)
{
Name (_ADR, 0x00)
Method (_GTM, 0, NotSerialized)
{
Name (PBUF, Buffer (0x14)
{
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00
})
CreateDWordField (PBUF, 0x00, PIO0)
CreateDWordField (PBUF, 0x04, DMA0)
CreateDWordField (PBUF, 0x08, PIO1)
CreateDWordField (PBUF, 0x0C, DMA1)
CreateDWordField (PBUF, 0x10, FLAG)
Store (GETP (PRIT), PIO0)
Store (GDMA (And (SYNC, 0x01), And (ICR3, 0x01), And (ICR0,
0x01), SDT0, And (ICR1, 0x01)), DMA0)
If (LEqual (DMA0, 0x))
{
Store (PIO0, DMA0)
}
If (And (PRIT, 0x4000))
{
If (LEqual (And (PRIT, 0x90), 0x80))
{
Store (0x0384, PIO1)
}
Else
{
Store (GETT (PSIT), PIO1)
}
}
Else
{
Store (0x, PIO1)
}
Store (GDMA (And (SYNC, 0x02), And (ICR3, 0x02), And (ICR0,
0x02), SDT1, And (ICR1, 0x02)), DMA1)
If (LEqual (DMA1, 0x))
{
Store (PIO1, DMA1)
}
Store (GETF (And (SYNC, 0x01), And (SYNC, 0x02), PRIT), FLAG)
If (And (LEqual (PIO0, 0x), LEqual (DMA0, 0x)))
{
Store (0x78, PIO0)
Store (0x14, DMA0)
Store (0x03, FLAG)
}
Return (PBUF)
}
Method (_STM, 3, NotSerialized)
{
CreateDWordField (Arg0, 0x00, PIO0)
CreateDWordField (Arg0, 0x04, DMA0)
CreateDWordField (Arg0, 0x08, PIO1)
CreateDWordField (Arg0, 0x0C, DMA1)
CreateDWordField (Arg0, 0x10, FLAG)
If (LEqual (SizeOf (Arg1), 0x0200))
{
And (PRIT, 0x40F0, PRIT)
And (SYNC, 0x02, SYNC)
Store (0x00, SDT0)
And (ICR0, 0x02, ICR0)
And (ICR1, 0x02, ICR1)
And (ICR3, 0x02, ICR3)
And (ICR5, 0x02, ICR5)
CreateWordField (Arg1, 0x62, W490)
CreateWordField (Arg1, 0x6A, W530)
CreateWordField (Arg1, 0x7E, W630)
CreateWordField (Arg1, 0x80, W640)
CreateWordField (Arg1, 0xB0, W880)
CreateWordField (Arg1, 0xBA, W930)
Or (PRIT, 0x8004, PRIT)
If (LAnd (And (FLAG, 0x02), And (W490, 0x0800)))
{
Or (PRIT, 0x02, PRIT)
}
Or (PRIT, SETP (PIO0, W530, W640), PRIT)
If (And (FL
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit :
Mathieu Bérard wrote:
Jeff Garzik a écrit :
Adrian Bunk wrote:
Subject: NCQ problem with ahci and Hitachi drive
References : http://lkml.org/lkml/2007/3/4/178
Submitter : Mathieu Bérard [EMAIL PROTECTED]
Status : unknown
according to the last message in that thread, it sounds like
ACPI and
interrupt problems
Hi,
after more testing with a 2.6.21-rc3, it appears that after
several ata
errors the boot process
somehow continued as normal, after a NCQ disabled due to excessive
errors message.
pci=noacpi or noacpi parameters workarounds the problem irqpoll
does nothing.
I was mistaken. It can't be IRQ routing problem. I somehow thought the
port was a ata_piix one. Considering the reported broken NCQ feature on
the device GTF might be mangling with the drive to disable NCQ or
something. Does giving libata.noacpi=1 make any difference?
Hi,
libata.noacpi=1 worked. The drive is up and running with NCQ on.
Here is the PATA/SATA related part of my DSDT table with the _GTF methods:
Device (PATA)
{
Name (_ADR, 0x001F0001)
OperationRegion (PACS, PCI_Config, 0x40, 0xC0)
Field (PACS, DWordAcc, NoLock, Preserve)
{
PRIT, 16,
Offset (0x04),
PSIT, 4,
Offset (0x08),
SYNC, 4,
Offset (0x0A),
SDT0, 2,
, 2,
SDT1, 2,
Offset (0x14),
ICR0, 4,
ICR1, 4,
ICR2, 4,
ICR3, 4,
ICR4, 4,
ICR5, 4
}
Device (PRID)
{
Name (_ADR, 0x00)
Method (_GTM, 0, NotSerialized)
{
Name (PBUF, Buffer (0x14)
{
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00
})
CreateDWordField (PBUF, 0x00, PIO0)
CreateDWordField (PBUF, 0x04, DMA0)
CreateDWordField (PBUF, 0x08, PIO1)
CreateDWordField (PBUF, 0x0C, DMA1)
CreateDWordField (PBUF, 0x10, FLAG)
Store (GETP (PRIT), PIO0)
Store (GDMA (And (SYNC, 0x01), And (ICR3, 0x01), And (ICR0,
0x01), SDT0, And (ICR1, 0x01)), DMA0)
If (LEqual (DMA0, 0x))
{
Store (PIO0, DMA0)
}
If (And (PRIT, 0x4000))
{
If (LEqual (And (PRIT, 0x90), 0x80))
{
Store (0x0384, PIO1)
}
Else
{
Store (GETT (PSIT), PIO1)
}
}
Else
{
Store (0x, PIO1)
}
Store (GDMA (And (SYNC, 0x02), And (ICR3, 0x02), And (ICR0,
0x02), SDT1, And (ICR1, 0x02)), DMA1)
If (LEqual (DMA1, 0x))
{
Store (PIO1, DMA1)
}
Store (GETF (And (SYNC, 0x01), And (SYNC, 0x02), PRIT), FLAG)
If (And (LEqual (PIO0, 0x), LEqual (DMA0, 0x)))
{
Store (0x78, PIO0)
Store (0x14, DMA0)
Store (0x03, FLAG)
}
Return (PBUF)
}
Method (_STM, 3, NotSerialized)
{
CreateDWordField (Arg0, 0x00, PIO0)
CreateDWordField (Arg0, 0x04, DMA0)
CreateDWordField (Arg0, 0x08, PIO1)
CreateDWordField (Arg0, 0x0C, DMA1)
CreateDWordField (Arg0, 0x10, FLAG)
If (LEqual (SizeOf (Arg1), 0x0200))
{
And (PRIT, 0x40F0, PRIT)
And (SYNC, 0x02, SYNC)
Store (0x00, SDT0)
And (ICR0, 0x02, ICR0)
And (ICR1, 0x02, ICR1)
And (ICR3, 0x02, ICR3)
And (ICR5, 0x02, ICR5)
CreateWordField (Arg1, 0x62, W490)
CreateWordField (Arg1, 0x6A, W530)
CreateWordField (Arg1, 0x7E, W630)
CreateWordField (Arg1, 0x80, W640)
CreateWordField (Arg1, 0xB0, W880)
CreateWordField (Arg1, 0xBA, W930)
Or (PRIT, 0x8004, PRIT)
If (LAnd (And (FLAG, 0x02), And (W490, 0x0800)))
{
Or (PRIT, 0x02, PRIT)
}
Or (PRIT, SETP (PIO0, W530, W640), PRIT)
If (And (FLAG, 0x01))
{
Or (SYNC, 0x01, SYNC)
Store (SDMA (DMA0), SDT0)
If (LLess (DMA0, 0x1E))
{
Or (ICR3, 0x01, ICR3)
}
If (LLess (DMA0, 0x3C))
{
Or (ICR0, 0x01, ICR0)
}
If (And (W930, 0x2000))
{
Or (ICR1, 0x01, ICR1
Re: [3/6] 2.6.21-rc2: known regressions
Tejun Heo a écrit : Can you apply the attached patch and report what the kernel says with ACPI turned on? Hi, I got this: [ 13.523816] SCSI subsystem initialized [ 13.528914] ACPI: PCI Interrupt :00:1f.2[B] - GSI 19 (level, low) - IRQ 19 [ 14.529383] ahci :00:1f.2: AHCI 0001. 32 slots 4 ports 1.5 Gbps 0x5 impl IDE mode [ 14.529439] ahci :00:1f.2: flags: 64bit ncq pm led slum part [ 14.529565] ata1: SATA max UDMA/133 cmd 0xf8824d00 ctl 0x bmdma 0x irq 19 [ 14.529683] ata2: SATA max UDMA/133 cmd 0xf8824d80 ctl 0x bmdma 0x irq 19 [ 14.529801] ata3: SATA max UDMA/133 cmd 0xf8824e00 ctl 0x bmdma 0x irq 19 [ 14.529921] ata4: SATA max UDMA/133 cmd 0xf8824e80 ctl 0x bmdma 0x irq 19 [ 14.529984] scsi0 : ahci [ 14.987273] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 15.032119] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100 [ 15.032168] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 15.034170] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 15.034464] ata1.00: configured for UDMA/100 [ 15.034515] scsi1 : ahci [ 15.337188] ata2: SATA link down (SStatus 0 SControl 0) [ 15.337241] scsi2 : ahci [ 15.640125] ata3: SATA link down (SStatus 0 SControl 300) [ 15.640178] scsi3 : ahci [ 15.943062] ata4: SATA link down (SStatus 0 SControl 0) [ 15.943191] scsi 0:0:0:0: Direct-Access ATA HTS541010G9SA00 MBZO PQ: 0 ANSI: 5 and for each ata errors: [ 47.089624] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen [ 47.089682] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 in [ 47.089684] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 47.392549] ata1: soft resetting port [ 47.547533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 47.549756] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 47.552600] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef [ 47.552969] ata1.00: configured for UDMA/100 [ 47.553022] ata1: EH complete [ 47.553104] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 47.553160] sda: Write Protect is off [ 47.553226] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA -- Mathieu - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3/6] 2.6.21-rc2: known regressions
Jeff Garzik a écrit : > Adrian Bunk wrote: >> Subject: NCQ problem with ahci and Hitachi drive >> References : http://lkml.org/lkml/2007/3/4/178 >> Submitter : Mathieu Bérard <[EMAIL PROTECTED]> >> Status : unknown > > according to the last message in that thread, it sounds like ACPI and > interrupt problems > Hi, after more testing with a 2.6.21-rc3, it appears that after several ata errors the boot process somehow continued as normal, after a "NCQ disabled due to excessive errors" message. "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll" does nothing. lspci: 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc M24 [Radeon Mobility X600] 06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) 06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller /proc/interrupts: CPU0 0: 3242 IO-APIC-edge timer 1:863 IO-APIC-edge i8042 8: 3 IO-APIC-edge rtc 9: 1 IO-APIC-fasteoi acpi 12:116 IO-APIC-edge i8042 14:128 IO-APIC-edge libata 15: 0 IO-APIC-edge libata 16: 1 IO-APIC-fasteoi uhci_hcd:usb4, yenta 17: 0 IO-APIC-fasteoi tifm_7xx1, Intel ICH6 18:249 IO-APIC-fasteoi eth0 19: 2712 IO-APIC-fasteoi libata, uhci_hcd:usb2, sdhci:slot0, sdhci:slot1, sdhci:slot2 20: 47 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5 21: 3 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394 22: 1 IO-APIC-fasteoi ipw2200 NMI: 0 LOC: 15767 ERR: 0 MIS: 0 /proc/interrupts with pci=noacpi: CPU0 0: 2886XT-PIC-XTtimer 1: 79XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 8: 3XT-PIC-XTrtc 9: 1XT-PIC-XTacpi 10: 1XT-PIC-XTuhci_hcd:usb4, tifm_7xx1, yenta, sdhci:slot0, sdhci:slot1, sdhci:slot2, Intel ICH6 11: 3415XT-PIC-XTeth0, libata, uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb5, ohci1394, ipw2200 12:116XT-PIC-XTi8042 14:129XT-PIC-XTlibata 15: 0XT-PIC-XTlibata NMI: 0 LOC: 6594 ERR: 0 MIS: 0 Full 2.6.21-rc3 boot log: [0.00] Linux version 2.6.21-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 PREEMPT Fri Mar 9 01:54:11 CET 2007 [0.00] BIOS-provided physical RAM map: [0.00] sanitize start [0.00] sanitize end [0.00] copy_e820_map() start: size: 0009f800 end: 0009f800 type: 1 [0.00] copy_e820_map() type is E820_RAM [0.00] copy_e820_map() start: 0009f800 size: 0800 end: 000a type: 2 [0.00] copy_e8
Re: [3/6] 2.6.21-rc2: known regressions
Jeff Garzik a écrit : Adrian Bunk wrote: Subject: NCQ problem with ahci and Hitachi drive References : http://lkml.org/lkml/2007/3/4/178 Submitter : Mathieu Bérard [EMAIL PROTECTED] Status : unknown according to the last message in that thread, it sounds like ACPI and interrupt problems Hi, after more testing with a 2.6.21-rc3, it appears that after several ata errors the boot process somehow continued as normal, after a NCQ disabled due to excessive errors message. pci=noacpi or noacpi parameters workarounds the problem irqpoll does nothing. lspci: 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc M24 [Radeon Mobility X600] 06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) 06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller /proc/interrupts: CPU0 0: 3242 IO-APIC-edge timer 1:863 IO-APIC-edge i8042 8: 3 IO-APIC-edge rtc 9: 1 IO-APIC-fasteoi acpi 12:116 IO-APIC-edge i8042 14:128 IO-APIC-edge libata 15: 0 IO-APIC-edge libata 16: 1 IO-APIC-fasteoi uhci_hcd:usb4, yenta 17: 0 IO-APIC-fasteoi tifm_7xx1, Intel ICH6 18:249 IO-APIC-fasteoi eth0 19: 2712 IO-APIC-fasteoi libata, uhci_hcd:usb2, sdhci:slot0, sdhci:slot1, sdhci:slot2 20: 47 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5 21: 3 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394 22: 1 IO-APIC-fasteoi ipw2200 NMI: 0 LOC: 15767 ERR: 0 MIS: 0 /proc/interrupts with pci=noacpi: CPU0 0: 2886XT-PIC-XTtimer 1: 79XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 8: 3XT-PIC-XTrtc 9: 1XT-PIC-XTacpi 10: 1XT-PIC-XTuhci_hcd:usb4, tifm_7xx1, yenta, sdhci:slot0, sdhci:slot1, sdhci:slot2, Intel ICH6 11: 3415XT-PIC-XTeth0, libata, uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb5, ohci1394, ipw2200 12:116XT-PIC-XTi8042 14:129XT-PIC-XTlibata 15: 0XT-PIC-XTlibata NMI: 0 LOC: 6594 ERR: 0 MIS: 0 Full 2.6.21-rc3 boot log: [0.00] Linux version 2.6.21-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 PREEMPT Fri Mar 9 01:54:11 CET 2007 [0.00] BIOS-provided physical RAM map: [0.00] sanitize start [0.00] sanitize end [0.00] copy_e820_map() start: size: 0009f800 end: 0009f800 type: 1 [0.00] copy_e820_map() type is E820_RAM [0.00] copy_e820_map() start: 0009f800 size: 0800 end: 000a type: 2 [0.00] copy_e820_map() start: 000d2000 size: 2000 end: 000d4000 type: 2 [0.00] copy_e820_map
Re: Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive
Tejun Heo a écrit : Hi, > No, your drive isn't blacklisted yet. NCQ is still being enabled. > > Sorry, I wasn't very clear: The NCQ blacklist patch is not in the 2.6.21-rc tree, just in -mm. I tried a 2.6.21-rc2-mm1 and the drive is blacklisted. The logs I pasted were from 2.6.20 and 2.6.21-rc1. >> [ 16.091804] ata1.00: configured for UDMA/100 >> [ 18.151756] SCSI device sda: write cache: enabled, read cache: >> enabled, doesn't support DPO or FUA >> > [--snip--] > >> [ 18.151856] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) >> [ 18.151911] sda: Write Protect is off >> [ 18.151977] SCSI device sda: write cache: enabled, read cache: >> enabled, doesn't support DPO or FUA >> [] >> [ 48.143940] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 >> frozen >> [ 48.143999] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 >> cdb 0x0 data 4096 in >> [ 48.144000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask >> 0x4 (timeout) >> > > It looks like IRQ isn't getting through. Does giving "acpi=off" kernel > parameter make any difference? > > Yes It works with acpi=off (2.6.21-rc1): Please notice that IRQ is changed from 19 with ACPI to 11 without. [ 24.226291] SCSI subsystem initialized [ 24.230178] libata version 2.10 loaded. [ 24.231315] ahci :00:1f.2: version 2.0 [ 25.231137] PCI: Setting latency timer of device :00:1f.2 to 64 [ 25.231144] ahci :00:1f.2: AHCI 0001. 32 slots 4 ports 1.5 Gbps 0x5 impl SATA mode [ 25.231202] ahci :00:1f.2: flags: 64bit ncq pm led slum part [ 25.231341] ata1: SATA max UDMA/133 cmd 0xf880ed00 ctl 0x bmdma 0x irq 11 [ 25.231468] ata2: SATA max UDMA/133 cmd 0xf880ed80 ctl 0x bmdma 0x irq 11 [ 25.231596] ata3: SATA max UDMA/133 cmd 0xf880ee00 ctl 0x bmdma 0x irq 11 [ 25.231722] ata4: SATA max UDMA/133 cmd 0xf880ee80 ctl 0x bmdma 0x irq 11 [ 25.231783] scsi0 : ahci [ 25.688849] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 25.689915] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100 [ 25.689964] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 25.691271] ata1.00: configured for UDMA/100 [ 25.691321] scsi1 : ahci [ 25.993653] ata2: SATA link down (SStatus 0 SControl 0) [ 25.993706] scsi2 : ahci [ 26.296471] ata3: SATA link down (SStatus 0 SControl 300) [ 26.296524] scsi3 : ahci [ 26.599288] ata4: SATA link down (SStatus 0 SControl 0) [ 26.599423] scsi 0:0:0:0: Direct-Access ATA HTS541010G9SA00 MBZO PQ: 0 ANSI: 5 [] [ 27.741608] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 27.741706] sda: Write Protect is off [ 27.741753] sda: Mode Sense: 00 3a 00 00 [ 27.741921] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 27.742037] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 27.742091] sda: Write Protect is off [ 27.742171] sda: Mode Sense: 00 3a 00 00 [ 27.742182] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 27.742238] sda: sda1 sda2 < sda5 sda6 > sda3 [ 28.204850] sd 0:0:0:0: Attached scsi disk sda [ 28.207809] sd 0:0:0:0: Attached scsi generic sg0 type 0 -- Mathieu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive
Tejun Heo a écrit : Hi, No, your drive isn't blacklisted yet. NCQ is still being enabled. Sorry, I wasn't very clear: The NCQ blacklist patch is not in the 2.6.21-rc tree, just in -mm. I tried a 2.6.21-rc2-mm1 and the drive is blacklisted. The logs I pasted were from 2.6.20 and 2.6.21-rc1. [ 16.091804] ata1.00: configured for UDMA/100 [ 18.151756] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [--snip--] [ 18.151856] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 18.151911] sda: Write Protect is off [ 18.151977] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [] [ 48.143940] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen [ 48.143999] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 in [ 48.144000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) It looks like IRQ isn't getting through. Does giving acpi=off kernel parameter make any difference? Yes It works with acpi=off (2.6.21-rc1): Please notice that IRQ is changed from 19 with ACPI to 11 without. [ 24.226291] SCSI subsystem initialized [ 24.230178] libata version 2.10 loaded. [ 24.231315] ahci :00:1f.2: version 2.0 [ 25.231137] PCI: Setting latency timer of device :00:1f.2 to 64 [ 25.231144] ahci :00:1f.2: AHCI 0001. 32 slots 4 ports 1.5 Gbps 0x5 impl SATA mode [ 25.231202] ahci :00:1f.2: flags: 64bit ncq pm led slum part [ 25.231341] ata1: SATA max UDMA/133 cmd 0xf880ed00 ctl 0x bmdma 0x irq 11 [ 25.231468] ata2: SATA max UDMA/133 cmd 0xf880ed80 ctl 0x bmdma 0x irq 11 [ 25.231596] ata3: SATA max UDMA/133 cmd 0xf880ee00 ctl 0x bmdma 0x irq 11 [ 25.231722] ata4: SATA max UDMA/133 cmd 0xf880ee80 ctl 0x bmdma 0x irq 11 [ 25.231783] scsi0 : ahci [ 25.688849] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 25.689915] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100 [ 25.689964] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 25.691271] ata1.00: configured for UDMA/100 [ 25.691321] scsi1 : ahci [ 25.993653] ata2: SATA link down (SStatus 0 SControl 0) [ 25.993706] scsi2 : ahci [ 26.296471] ata3: SATA link down (SStatus 0 SControl 300) [ 26.296524] scsi3 : ahci [ 26.599288] ata4: SATA link down (SStatus 0 SControl 0) [ 26.599423] scsi 0:0:0:0: Direct-Access ATA HTS541010G9SA00 MBZO PQ: 0 ANSI: 5 [] [ 27.741608] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 27.741706] sda: Write Protect is off [ 27.741753] sda: Mode Sense: 00 3a 00 00 [ 27.741921] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 27.742037] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 27.742091] sda: Write Protect is off [ 27.742171] sda: Mode Sense: 00 3a 00 00 [ 27.742182] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 27.742238] sda: sda1 sda2 sda5 sda6 sda3 [ 28.204850] sd 0:0:0:0: Attached scsi disk sda [ 28.207809] sd 0:0:0:0: Attached scsi generic sg0 type 0 -- Mathieu - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive
113 SControl 300) [ 79.062836] ata1.00: configured for UDMA/100 [ 79.062887] ata1: EH complete [ 79.062957] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 79.063011] sda: Write Protect is off [ 79.063077] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 109.055268] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen [ 109.055324] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 in [ 109.055325] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 109.358190] ata1: soft resetting port [ 109.513168] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 109.518528] ata1.00: configured for UDMA/100 [ 109.518579] ata1: EH complete [ 109.518648] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 109.518703] sda: Write Protect is off [ 109.518769] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [looping forever with this error] Thanks. (Please CC me) -- Mathieu Bérard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive
) [ 79.062836] ata1.00: configured for UDMA/100 [ 79.062887] ata1: EH complete [ 79.062957] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 79.063011] sda: Write Protect is off [ 79.063077] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 109.055268] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen [ 109.055324] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 in [ 109.055325] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 109.358190] ata1: soft resetting port [ 109.513168] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 109.518528] ata1.00: configured for UDMA/100 [ 109.518579] ata1: EH complete [ 109.518648] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) [ 109.518703] sda: Write Protect is off [ 109.518769] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [looping forever with this error] Thanks. (Please CC me) -- Mathieu Bérard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT400 + Kernel 2.6.12 + IO-APIC + uhci_hcd = IRQ trouble
Michel Bouissou a écrit : Hi there, Natalie Protasevich and Alan Stern have worked a lot on helping me out with a VIA KT400 chipset / kernel 2.6.12 / IO-APIC / IRQ problem "irq 21: nobody cared!", which so far hasn't found its solution. Research done with Alan shows that, on my system, the USB 2.0 controller seems to generate interrupts on the IRQ line attributed to the USB 1.1 controller, which isn't supposed to happen, and puzzles the system, when IO-APIC is enabled. However, this didn't cause problems with 2.4 series kernels. For the time being, there is no solution (Natalie is still investigating this), and it boils down to the following: - If I boot with USB 2.0 enabled in BIOS, AND IO-APIC enabled in the kernel, then it badly breaks. - If I either disable USB 2.0 in BIOS, or IO-APIC in the kernel, then it's OK. I found today the thread between Bjorn Helgaas and Mathieu Bérard on LKML, where Mathieu reported the same problem, and Bjorn advised him to reverse a kernel patch (http://lkml.org/lkml/2005/6/21/243 ). Mathieu (I don't have his email address, Bjorn, could you be so kind to forward this message to him) reports that it apparently solved this problem, so I tried to do the same, and reversed the same patch. Hi, yes I've encountered the same problem but my system is a little bit different: It's a MSI mainboard with a VIA KT266A chipset and no USB 2.0 controller (just 3 uhci). IO-APIC is enabled. With a 2.6.13-rc1-mm1 kernel, for example, I got those error messages just after the integrated sound card detection: Jul 2 21:04:12 perenold kernel: irq 21: nobody cared (try booting with the "irqpoll" option) Jul 2 21:04:12 perenold kernel: [] __report_bad_irq+0x24/0x80 Jul 2 21:04:12 perenold kernel: [] note_interrupt+0x72/0xc0 Jul 2 21:04:12 perenold kernel: [] __do_IRQ+0xe0/0xf0 Jul 2 21:04:12 perenold kernel: [] do_IRQ+0x3e/0x60 Jul 2 21:04:12 perenold kernel: === Jul 2 21:04:12 perenold kernel: [] common_interrupt+0x1a/0x20 Jul 2 21:04:12 perenold kernel: [] zap_pte_range+0x82/0x1c0 Jul 2 21:04:12 perenold kernel: [] unmap_page_range+0x7f/0xb0 Jul 2 21:04:12 perenold kernel: [] unmap_vmas+0x106/0x210 Jul 2 21:04:12 perenold kernel: [] exit_mmap+0x71/0x140 Jul 2 21:04:12 perenold kernel: [] mmput+0x2e/0xe0 Jul 2 21:04:12 perenold kernel: [] exec_mmap+0xac/0x160 Jul 2 21:04:12 perenold kernel: [] flush_old_exec+0x70/0x700 Jul 2 21:04:12 perenold kernel: [] vfs_read+0xf5/0x160 Jul 2 21:04:12 perenold kernel: [] kernel_read+0x40/0x60 Jul 2 21:04:12 perenold kernel: [] load_elf_binary+0x252/0xd20 Jul 2 21:04:12 perenold kernel: [] buffered_rmqueue+0xb7/0x210 Jul 2 21:04:12 perenold kernel: [] __alloc_pages+0xdb/0x400 Jul 2 21:04:12 perenold kernel: [] do_IRQ+0x45/0x60 Jul 2 21:04:12 perenold kernel: [] __copy_from_user_ll+0x3e/0x70 Jul 2 21:04:12 perenold kernel: [] search_binary_handler+0x4f/0x1d0 Jul 2 21:04:12 perenold kernel: [] do_execve+0x14e/0x200 Jul 2 21:04:12 perenold kernel: [] sys_execve+0x2f/0x70 Jul 2 21:04:12 perenold kernel: [] sysenter_past_esp+0x54/0x75 Jul 2 21:04:12 perenold kernel: handlers: Jul 2 21:04:12 perenold kernel: [] (snd_via82xx_interrupt+0x0/0xc0 [snd_via82xx]) Jul 2 21:04:12 perenold kernel: Disabling IRQ #21 and later: Jul 2 21:04:37 perenold kernel: uhci_hcd :00:11.3: Unlink after no-IRQ? Controller is probably using the wrong IRQ. IRQ 21 is then crazy with a rate of increasing of around 20 per second in /proc/interrupts All those error messages disappear if I revert the patch as I was advised to. I have that in /proc/interrupts: (with an healthy kernel) CPU0 0: 201893429IO-APIC-edge timer 1: 21IO-APIC-edge i8042 7: 2IO-APIC-edge parport0 8: 0IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 14:5448524IO-APIC-edge ide0 15: 14583934IO-APIC-edge ide1 16: 172543 IO-APIC-level ide3 17: 299810 IO-APIC-level saa7134[0] 18: 24973124 IO-APIC-level eth0 19:5233000 IO-APIC-level eth1 20: 82 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3 21: 0 IO-APIC-level VIA8233 NMI: 0 LOC: 201897508 ERR: 0 MIS: 0 So maybe, in my case, it's a mess between the IRQ of the uhci controllers and the one of the integrated AC'97 sound ship. But as it is mainly a server box nor the usb controllers nor the sound card are used very often, so I don't know if those devices are actually working now. I am currently on vacation 300 km away from that box so I can't really plug an USB key to do some tests. But I will as soon as a can if that can help. I will also try to reboot the box several times to see if the "IRQ 21 nobody cared" error reappears. -- Mathieu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL
Re: VIA KT400 + Kernel 2.6.12 + IO-APIC + uhci_hcd = IRQ trouble
Michel Bouissou a écrit : Hi there, Natalie Protasevich and Alan Stern have worked a lot on helping me out with a VIA KT400 chipset / kernel 2.6.12 / IO-APIC / IRQ problem irq 21: nobody cared!, which so far hasn't found its solution. Research done with Alan shows that, on my system, the USB 2.0 controller seems to generate interrupts on the IRQ line attributed to the USB 1.1 controller, which isn't supposed to happen, and puzzles the system, when IO-APIC is enabled. However, this didn't cause problems with 2.4 series kernels. For the time being, there is no solution (Natalie is still investigating this), and it boils down to the following: - If I boot with USB 2.0 enabled in BIOS, AND IO-APIC enabled in the kernel, then it badly breaks. - If I either disable USB 2.0 in BIOS, or IO-APIC in the kernel, then it's OK. I found today the thread between Bjorn Helgaas and Mathieu Bérard on LKML, where Mathieu reported the same problem, and Bjorn advised him to reverse a kernel patch (http://lkml.org/lkml/2005/6/21/243 ). Mathieu (I don't have his email address, Bjorn, could you be so kind to forward this message to him) reports that it apparently solved this problem, so I tried to do the same, and reversed the same patch. Hi, yes I've encountered the same problem but my system is a little bit different: It's a MSI mainboard with a VIA KT266A chipset and no USB 2.0 controller (just 3 uhci). IO-APIC is enabled. With a 2.6.13-rc1-mm1 kernel, for example, I got those error messages just after the integrated sound card detection: Jul 2 21:04:12 perenold kernel: irq 21: nobody cared (try booting with the irqpoll option) Jul 2 21:04:12 perenold kernel: [c0133c24] __report_bad_irq+0x24/0x80 Jul 2 21:04:12 perenold kernel: [c0133d22] note_interrupt+0x72/0xc0 Jul 2 21:04:12 perenold kernel: [c0133710] __do_IRQ+0xe0/0xf0 Jul 2 21:04:12 perenold kernel: [c0104f8e] do_IRQ+0x3e/0x60 Jul 2 21:04:12 perenold kernel: === Jul 2 21:04:12 perenold kernel: [c0103502] common_interrupt+0x1a/0x20 Jul 2 21:04:12 perenold kernel: [c0142102] zap_pte_range+0x82/0x1c0 Jul 2 21:04:12 perenold kernel: [c01422bf] unmap_page_range+0x7f/0xb0 Jul 2 21:04:12 perenold kernel: [c01423f6] unmap_vmas+0x106/0x210 Jul 2 21:04:12 perenold kernel: [c01469c1] exit_mmap+0x71/0x140 Jul 2 21:04:12 perenold kernel: [c011547e] mmput+0x2e/0xe0 Jul 2 21:04:12 perenold kernel: [c015af3c] exec_mmap+0xac/0x160 Jul 2 21:04:12 perenold kernel: [c015b0a0] flush_old_exec+0x70/0x700 Jul 2 21:04:12 perenold kernel: [c0151475] vfs_read+0xf5/0x160 Jul 2 21:04:12 perenold kernel: [c015ae70] kernel_read+0x40/0x60 Jul 2 21:04:12 perenold kernel: [c0178f32] load_elf_binary+0x252/0xd20 Jul 2 21:04:12 perenold kernel: [c0138bf7] buffered_rmqueue+0xb7/0x210 Jul 2 21:04:12 perenold kernel: [c0138eeb] __alloc_pages+0xdb/0x400 Jul 2 21:04:12 perenold kernel: [c0104f95] do_IRQ+0x45/0x60 Jul 2 21:04:12 perenold kernel: [c01c2c6e] __copy_from_user_ll+0x3e/0x70 Jul 2 21:04:12 perenold kernel: [c015b92f] search_binary_handler+0x4f/0x1d0 Jul 2 21:04:12 perenold kernel: [c015bbfe] do_execve+0x14e/0x200 Jul 2 21:04:12 perenold kernel: [c010181f] sys_execve+0x2f/0x70 Jul 2 21:04:12 perenold kernel: [c0102aeb] sysenter_past_esp+0x54/0x75 Jul 2 21:04:12 perenold kernel: handlers: Jul 2 21:04:12 perenold kernel: [e0c59450] (snd_via82xx_interrupt+0x0/0xc0 [snd_via82xx]) Jul 2 21:04:12 perenold kernel: Disabling IRQ #21 and later: Jul 2 21:04:37 perenold kernel: uhci_hcd :00:11.3: Unlink after no-IRQ? Controller is probably using the wrong IRQ. IRQ 21 is then crazy with a rate of increasing of around 20 per second in /proc/interrupts All those error messages disappear if I revert the patch as I was advised to. I have that in /proc/interrupts: (with an healthy kernel) CPU0 0: 201893429IO-APIC-edge timer 1: 21IO-APIC-edge i8042 7: 2IO-APIC-edge parport0 8: 0IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 14:5448524IO-APIC-edge ide0 15: 14583934IO-APIC-edge ide1 16: 172543 IO-APIC-level ide3 17: 299810 IO-APIC-level saa7134[0] 18: 24973124 IO-APIC-level eth0 19:5233000 IO-APIC-level eth1 20: 82 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3 21: 0 IO-APIC-level VIA8233 NMI: 0 LOC: 201897508 ERR: 0 MIS: 0 So maybe, in my case, it's a mess between the IRQ of the uhci controllers and the one of the integrated AC'97 sound ship. But as it is mainly a server box nor the usb controllers nor the sound card are used very often, so I don't know if those devices are actually working now. I am currently on vacation 300 km away from that box so I can't really plug an USB key to do some tests. But I will as soon as a can if that can help. I will also try to reboot the box several times to see if the IRQ 21 nobody cared error
Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem
Bartlomiej Zolnierkiewicz a écrit : On Apr 3, 2005 11:56 PM, Andrew Morton <[EMAIL PROTECTED]> wrote: Mathieu Bérard <[EMAIL PROTECTED]> wrote: Hi, I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4. (Everyting run smoothly using 2.6.11-mm1) It seems to be related with mounting a reiserfs3 filesystem. It looks more like an IDE bug. ReiserFS: hdg1: checking transaction log (hdg1) Unable to handle kernel paging request at virtual address 0a373138 printing eip: df6d1211 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic slhc w83627hf_wdt msr cpuid rtc CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010202 (2.6.12-rc1-mm4) EIP is at 0xdf6d1211 eax: c9393266 ebx: df6d1c84 ecx: d84eab1e edx: c155ccf8 esi: c039242c edi: c039239c ebp: 700d580a esp: df6d1c80 ds: 007b es: 007b ss: 0068 Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50) Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 c0223051 0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c c022333e df6d1d1c c153d6e0 c155bd78 df6d1d1c c14007f0 c0212260 Call Trace: [] flagged_taskfile+0x125/0x380 [] start_request+0x1f1/0x2a0 [] ide_do_request+0x20e/0x3c0 [] __generic_unplug_device+0x20/0x30 [] generic_unplug_device+0x11/0x30 [] blk_backing_dev_unplug+0xc/0x10 [] sync_buffer+0x26/0x40 [] __wait_on_bit+0x42/0x70 [] sync_buffer+0x0/0x40 [] sync_buffer+0x0/0x40 [] out_of_line_wait_on_bit+0x7d/0x90 [] wake_bit_function+0x0/0x60 [] __wait_on_buffer+0x29/0x30 [] _update_journal_header_block+0xf7/0x140 [] journal_read+0x31d/0x470 [] journal_init+0x4e1/0x650 [] printk+0x1b/0x20 [] reiserfs_fill_super+0x34d/0x770 [] snprintf+0x20/0x30 [] disk_name+0x96/0xf0 [] get_sb_bdev+0xe5/0x130 [] link_path_walk+0x65/0x140 [] get_super_block+0x18/0x20 [] reiserfs_fill_super+0x0/0x770 [] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 <1>general p It appears that we might have jumped from flagged_taskfile into something at 0xdf6d1211, which is rather odd. It is very odd, we shouldn't hit flagged_taskfile() in the first place. This function currently is executed only for special HDIO_DRIVE_TASKFILE ioctl requests. Whatever the explanation was, This oops is fixed in 2.6.12-rc2-mm1... -- Mathieu Bérard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem
Bartlomiej Zolnierkiewicz a écrit : On Apr 3, 2005 11:56 PM, Andrew Morton [EMAIL PROTECTED] wrote: Mathieu Bérard [EMAIL PROTECTED] wrote: Hi, I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4. (Everyting run smoothly using 2.6.11-mm1) It seems to be related with mounting a reiserfs3 filesystem. It looks more like an IDE bug. ReiserFS: hdg1: checking transaction log (hdg1) Unable to handle kernel paging request at virtual address 0a373138 printing eip: df6d1211 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic slhc w83627hf_wdt msr cpuid rtc CPU:0 EIP:0060:[df6d1211]Not tainted VLI EFLAGS: 00010202 (2.6.12-rc1-mm4) EIP is at 0xdf6d1211 eax: c9393266 ebx: df6d1c84 ecx: d84eab1e edx: c155ccf8 esi: c039242c edi: c039239c ebp: 700d580a esp: df6d1c80 ds: 007b es: 007b ss: 0068 Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50) Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 c0223051 0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c c022333e df6d1d1c c153d6e0 c155bd78 df6d1d1c c14007f0 c0212260 Call Trace: [c0229945] flagged_taskfile+0x125/0x380 [c0223051] start_request+0x1f1/0x2a0 [c022333e] ide_do_request+0x20e/0x3c0 [c0212260] __generic_unplug_device+0x20/0x30 [c0212281] generic_unplug_device+0x11/0x30 [c02122ac] blk_backing_dev_unplug+0xc/0x10 [c0156336] sync_buffer+0x26/0x40 [c02a0b22] __wait_on_bit+0x42/0x70 [c0156310] sync_buffer+0x0/0x40 [c0156310] sync_buffer+0x0/0x40 [c02a0bcd] out_of_line_wait_on_bit+0x7d/0x90 [c012bf80] wake_bit_function+0x0/0x60 [c01563c9] __wait_on_buffer+0x29/0x30 [c01b0dd7] _update_journal_header_block+0xf7/0x140 [c01b290d] journal_read+0x31d/0x470 [c01b3241] journal_init+0x4e1/0x650 [c011748b] printk+0x1b/0x20 [c01a3ced] reiserfs_fill_super+0x34d/0x770 [c01c9470] snprintf+0x20/0x30 [c0189ab6] disk_name+0x96/0xf0 [c015bf75] get_sb_bdev+0xe5/0x130 [c0163945] link_path_walk+0x65/0x140 [c01a4168] get_super_block+0x18/0x20 [c01a39a0] reiserfs_fill_super+0x0/0x770 [c015c194] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 1general p It appears that we might have jumped from flagged_taskfile into something at 0xdf6d1211, which is rather odd. It is very odd, we shouldn't hit flagged_taskfile() in the first place. This function currently is executed only for special HDIO_DRIVE_TASKFILE ioctl requests. Whatever the explanation was, This oops is fixed in 2.6.12-rc2-mm1... -- Mathieu Bérard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem
Andrew Morton a écrit : It appears that we might have jumped from flagged_taskfile into something at 0xdf6d1211, which is rather odd. You have two different low-level IDE drivers configured. Which one is driving that filesystem? VIA or Promise? hdg is connected to my Promise PDC20268 (Ultra100 TX2) -- Mathieu Bérard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem
set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_INFO is not set # CONFIG_PAGE_OWNER is not set # CONFIG_DEBUG_FS is not set # CONFIG_FRAME_POINTER is not set CONFIG_EARLY_PRINTK=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_4KSTACKS=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y # CONFIG_KGDB is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_AES_586=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_CRC32C=m # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # CONFIG_CRC_CCITT=m CONFIG_CRC32=y CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=m CONFIG_ZLIB_DEFLATE=m CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y lspci output: :00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] :00:05.0 Multimedia controller: Philips Semiconductors SAA7134 (rev 01) :00:06.0 Unknown mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02) :00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.4 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 10) :01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 11) -- Mathieu Bérard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem
Andrew Morton a écrit : It appears that we might have jumped from flagged_taskfile into something at 0xdf6d1211, which is rather odd. You have two different low-level IDE drivers configured. Which one is driving that filesystem? VIA or Promise? hdg is connected to my Promise PDC20268 (Ultra100 TX2) -- Mathieu Bérard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
