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-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [3/6] 2.6.21-rc2: known regressions
Can you apply the attached patch and report what the kernel says with ACPI turned on? -- tejun diff --git a/drivers/ata/libata-acpi.c b/drivers/ata/libata-acpi.c index 019d8ff..6a27a7f 100644 --- a/drivers/ata/libata-acpi.c +++ b/drivers/ata/libata-acpi.c @@ -473,8 +473,8 @@ static void taskfile_load_raw(struct ata_port *ap, struct ata_taskfile tf; unsigned int err; - if (ata_msg_probe(ap)) - ata_dev_printk(atadev, KERN_DEBUG, %s: (0x1f1-1f7): hex: + if (1 || ata_msg_probe(ap)) + ata_dev_printk(atadev, KERN_INFO, %s: (0x1f1-1f7): hex: %02x %02x %02x %02x %02x %02x %02x\n, __FUNCTION__, gtf-tfa[0], gtf-tfa[1], gtf-tfa[2],
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
Hello, Mathieu Bérard wrote: [ 15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00 00 a0 ef Okay, this is interesting. This is Enable Device-Initiated Interface Power State Transitions. So, after this command is executed the device will try to transit to partial/slumber SATA PHY power states at its discretion, which is all cool and dandy in theory but depending on controller and drive firmware can cause all sorts of problems. The NCQ problem you're seeing probably is some side effect of device initiated link PS. Can't tell whether the controller or the drive's firmware is problem without further info. Due to blacklisting, NCQ won't be turned on your drive in future kernels and link PS doesn't seem to cause any problem no non-NCQ, so your case is taken care of here but this leaves me a bit worried about what _GTF feeds us. I don't think we can reliably filter out command TFs as it might even contain vendor-specific commands but it might be better to always log TFs executed for _GTF such that we at least know what's going on with the drive. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [3/6] 2.6.21-rc2: known regressions
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? Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions
On Fri, 2007-03-09 at 21:41 -0800, Linus Torvalds wrote: On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote: With this quirk I got this oops on hibernate (but computer still working) Well, strictly speaking it's a warning, not an oops per se. What happens is that the quirk wants to do an ioremap_nocache(), which allocates memory, and that happens very early during initialization when interrupts are disabled. And you're really not supposed to allocate memory, except using GFP_ATOMIC. But we've always been lax about that during early boot, so we have stuff that does. And resume ends up doing a lot of the same things early boot does, and shows issues like this. So the quirk is probably still a good idea, and the warning message is just that - a very scary warning message, but not an indicator that anything is seriously screwed up for you. (It is an indication of a real bug, though, even though it's harmless in practice in this case) Hi, thanks Just to write, I test last fedora kernel(2.6.20-1.2981.fc7) which is based on 2.6.21-rc3-git5, without any problem, less than the scary warning, talked in this email :) Best regards, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature
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()
and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions
On Sat, 2007-03-10 at 02:09 +0100, 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. Hi, I have a laptop quite similar to this report, but still running 2.4.20. With /usr/bin/hal-device-manager on (00:1f.1) 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03 I found that I have an Hitachi Travelstar 80GN. And your initial report point that you have an Hitachi Travelstar 5K100 and the patch http://lkml.org/lkml/2007/2/22/8 blacklist your HD , correct ? I will try 20-rc3 to see if I have any problem. but blacklist it is not a good solution ... well I recently found a quirk that is apply on laptop that I mention here. which I remove from my kernel because I don't have a Assus and my laptop is quirked too. --- linux-2.6.20.i686/drivers/pci/quirks.c.orig 2007-03-04 04:52:21.0 + +++ linux-2.6.20.i686/drivers/pci/quirks.c 2007-03-04 04:52:41.0 + @@ -1121,8 +1121,8 @@ static void asus_hides_smbus_lpc_ich6(st iounmap(base); printk(KERN_INFO PCI: Enabled ICH6/i801 SMBus device\n); } -DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_1, asus_hides_smbus_lpc_ich6 ); -DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_1, asus_hides_smbus_lpc_ich6 ); +/* DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_1, asus_hides_smbus_lpc_ich6 ); */ +/* DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_1, asus_hides_smbus_lpc_ich6 ); */ /* * SiS 96x south bridge: BIOS typically hides SMBus device... With this quirk I got this oops on hibernate (but computer still working) Suspending console(s) eth1: Going into suspend... ACPI: PCI interrupt for device :02:04.0 disabled ACPI: PCI interrupt for device :00:1e.3 disabled ACPI: PCI interrupt for device :00:1e.2 disabled ACPI: PCI interrupt for device :00:1d.7 disabled ACPI: PCI interrupt for device :00:1d.3 disabled ACPI: PCI interrupt for device :00:1d.2 disabled ACPI: PCI interrupt for device :00:1d.1 disabled ACPI: PCI interrupt for device :00:1d.0 disabled ipw2200: Unable to load ucode: -22 ipw2200: Unable to load firmware: -22 ipw2200: Failed to up device swsusp: critical section: swsusp: Need to copy 57480 pages Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. BUG: sleeping function called from invalid context at mm/slab.c:3035 in_atomic():0, irqs_disabled():1 no locks held by pm-hibernate/22979. irq event stamp: 0 hardirqs last enabled at (0): [] 0x0 hardirqs last disabled at (0): [c042580c] copy_process+0x311/0x1249 softirqs last enabled at (0): [c042580c] copy_process+0x311/0x1249 softirqs last disabled at (0): [] 0x0 [c04051c9] show_trace_log_lvl+0x1a/0x2f [c040576e] show_trace+0x12/0x14 [c04057f2] dump_stack+0x16/0x18 [c0421266] __might_sleep+0xc9/0xcf [c0474cb1] kmem_cache_alloc+0x28/0xc4 [c046bb50] __get_vm_area_node+0x87/0x16f [c046bcae] __get_vm_area+0x22/0x28 [c046bcf3] get_vm_area+0x3f/0x43 [c041f0ed] __ioremap+0xa0/0xe6 [c041f147] ioremap_nocache+0x14/0x79 [c04f070a] asus_hides_smbus_lpc_ich6+0x37/0x61 [c04ef384] pci_fixup_device+0x70/0x7c [c04f0a70] pci_device_resume_early+0x17/0x2e [c0550779] dpm_power_up+0x41/0x53 [c0550798] device_power_up+0xd/0xf [c0448bc4] swsusp_suspend+0x55/0x62 [c044929c] pm_suspend_disk+0xd5/0x181 [c04480a7] enter_state+0x51/0x172 [c044824e] state_store+0x86/0x9c [c04b0a58] subsys_attr_store+0x20/0x25 [c04b0b69] sysfs_write_file+0xb8/0xe0 [c0478c68] vfs_write+0xaf/0x163 [c04792b6] sys_write+0x3d/0x61 [c0404058] syscall_call+0x7/0xb === PCI: Enabled ICH6/i801 SMBus device removing quirk resolve the oops. BTW I have an HP Compaq nx6110 , what laptop is yours ? ah! and WTF I don't attach your dmesg in a file ? 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
Re: and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions
On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote: With this quirk I got this oops on hibernate (but computer still working) Well, strictly speaking it's a warning, not an oops per se. What happens is that the quirk wants to do an ioremap_nocache(), which allocates memory, and that happens very early during initialization when interrupts are disabled. And you're really not supposed to allocate memory, except using GFP_ATOMIC. But we've always been lax about that during early boot, so we have stuff that does. And resume ends up doing a lot of the same things early boot does, and shows issues like this. So the quirk is probably still a good idea, and the warning message is just that - a very scary warning message, but not an indicator that anything is seriously screwed up for you. (It is an indication of a real bug, though, even though it's harmless in practice in this case) Linus - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [3/6] 2.6.21-rc2: known regressions
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 Subject: SATA_ACPI errors during kernel boot References : http://bugzilla.kernel.org/show_bug.cgi?id=8080 http://bugzilla.kernel.org/show_bug.cgi?id=8046 http://bugzilla.kernel.org/show_bug.cgi?id=8095 http://lkml.org/lkml/2007/2/22/159 Submitter : Janosch Machowinski [EMAIL PROTECTED] Lukas Hejtmanek [EMAIL PROTECTED] Meelis Roos [EMAIL PROTECTED] Olivier Mondoloni [EMAIL PROTECTED] Handled-By : Thomas Renninger [EMAIL PROTECTED] Tejun Heo [EMAIL PROTECTED] Robert Moore [EMAIL PROTECTED] Status : problem is being debugged Note that there WILL be an increase in ACPI diagnostic output. The key difference is whether the users are seeing scary printks, or whether the boot is actually breaking. Jeff - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [3/6] 2.6.21-rc2: known regressions
Subject: libata: PATA UDMA/100 configured as UDMA/33 References : http://lkml.org/lkml/2007/2/20/294 http://www.mail-archive.com/linux-ide@vger.kernel.org/msg04115.html Submitter : Fabio Comolli [EMAIL PROTECTED] Handled-By : Tejun Heo [EMAIL PROTECTED] Status : problem is being discussed Patch went to Jeff, hopefully it is now fixed. Bigger rework is heading into -mm but not appropriate or neccessary for 2.6.21 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[3/6] 2.6.21-rc2: known regressions
This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20 that are not yet fixed in Linus' tree. If you find your name in the Cc header, you are either submitter of one of the bugs, maintainer of an affectected subsystem or driver, a patch of you caused a breakage or I'm considering you in any other way possibly involved with one or more of these issues. Due to the huge amount of recipients, please trim the Cc when answering. 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 Subject: kernels fail to boot with drives on ATIIXP controller References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229621 Submitter : Michal Jaegermann [EMAIL PROTECTED] Status : unknown Subject: libata: PATA UDMA/100 configured as UDMA/33 References : http://lkml.org/lkml/2007/2/20/294 http://www.mail-archive.com/linux-ide@vger.kernel.org/msg04115.html Submitter : Fabio Comolli [EMAIL PROTECTED] Handled-By : Tejun Heo [EMAIL PROTECTED] Status : problem is being discussed Subject: SATA_ACPI errors during kernel boot References : http://bugzilla.kernel.org/show_bug.cgi?id=8080 http://bugzilla.kernel.org/show_bug.cgi?id=8046 http://bugzilla.kernel.org/show_bug.cgi?id=8095 http://lkml.org/lkml/2007/2/22/159 Submitter : Janosch Machowinski [EMAIL PROTECTED] Lukas Hejtmanek [EMAIL PROTECTED] Meelis Roos [EMAIL PROTECTED] Olivier Mondoloni [EMAIL PROTECTED] Handled-By : Thomas Renninger [EMAIL PROTECTED] Tejun Heo [EMAIL PROTECTED] Robert Moore [EMAIL PROTECTED] Status : problem is being debugged - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
