Re: Linux 2.6.21-rc6 - regressions update
On Fri, 2007-04-06 at 16:04 -0700, Linus Torvalds wrote: [HPET issues resolved] > > 3) Subject: SATA breakage on resume > > References : http://lkml.org/lkml/2007/3/7/233 > > Submitter : Thomas Gleixner <[EMAIL PROTECTED]> > > Soeren Sonnenburg <[EMAIL PROTECTED]> > > Status : unknown > > > > I am still seeing these messages after a suspend/resume cycle (though > > all devices work even after multiple suspend/resume cycles) > > > > ATA: abnormal status 0x80 on port 0x000140df > > This seems to be normal, and related to some unknown timing issue. If the > thing works for you apart from the message, I'd just ignore it.. Argh! Now after intensive use over the last 2 days, I realized that the internal harddisk works OK, but the dvd-drive did not after the 7th suspend/resume cycle - the device was suddenly gone (I could not even eject the disc I just inserted), more verbose dmesg follows: ata1: port is slow to respond, please be patient (Status 0x80) ata1: port failed to respond (30 secs, Status 0x80) ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ata1.00: qc timeout (cmd 0xa1) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1: failed to recover some devices, retrying in 5 secs ata1: port is slow to respond, please be patient (Status 0x80) ata1: port failed to respond (30 secs, Status 0x80) ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ATA: abnormal status 0x80 on port 0x000101f7 ata1.00: qc timeout (cmd 0xa1) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1.00: limiting speed to UDMA/33:PIO3 ata1: failed to recover some devices, retrying in 5 secs ata1: port is slow to respond, please be patient (Status 0x80) ata1: port failed to respond (30 secs, Status 0x80) ATA: abnormal status 0x80 on port 0x000101f7 sage repeated 4 times ata1.00: qc timeout (cmd 0xa1) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1.00: disabled Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 - 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: Linux 2.6.21-rc6 - regressions update
[ Added some people to the cc.. Len, Thomas, Ingo - look for the exact report on linux-kernel, but basically it's a "irq 9: nobody cared" issue with acpi_irq on irq9 ] On Sat, 7 Apr 2007, Soeren Sonnenburg wrote: > > regression update for 21-rc6: > > 1) all s2ram and NO_HZ related things seem to be resolved on my macbook > pro, also > CONFIG_HPET_TIMER=y > CONFIG_HPET_EMULATE_RTC=y > > don't break resume anymore. Goodie. I think we fixed most stuff.. > 2) However I am still having problems with > +CONFIG_HIGH_RES_TIMERS=y > +CONFIG_HPET=y > +CONFIG_HPET_MMAP=y > although the machine resumes, I've managed to get the attached oops. Ok, interesting. I'd have blamed ACPI for this one (stuck IRQ9 is almost always some ACPI event that got stuck or the SCI got mis-routed and/or marked with the wrong polarity), although from your message I take it you don't get it without high-res timers? In fact, I have a theory.. Your backtrace is: [] smp_apic_timer_interrupt+0x57/0x90 [] retrigger_next_event+0x0/0xb0 [] apic_timer_interrupt+0x28/0x30 [] retrigger_next_event+0x0/0xb0 [] __kfifo_put+0x8/0x90 [] on_each_cpu+0x35/0x60 [] clock_was_set+0x18/0x20 [] timekeeping_resume+0x7c/0xa0 [] __sysdev_resume+0x11/0x80 [] sysdev_resume+0x47/0x80 [] device_power_up+0x5/0x10 and the thing is, I don't think we should have interrupt enabled at this point in time! I susect that the timer resume enables interrupts too early! We should be doing the whole "device_power_up()" sequence with irq's off, I think.. > 3) Subject: SATA breakage on resume > References : http://lkml.org/lkml/2007/3/7/233 > Submitter : Thomas Gleixner <[EMAIL PROTECTED]> > Soeren Sonnenburg <[EMAIL PROTECTED]> > Status : unknown > > I am still seeing these messages after a suspend/resume cycle (though > all devices work even after multiple suspend/resume cycles) > > ATA: abnormal status 0x80 on port 0x000140df This seems to be normal, and related to some unknown timing issue. If the thing works for you apart from the message, I'd just ignore it.. Linus - 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: Linux 2.6.21-rc6 - regressions update
On Thu, 2007-04-05 at 19:50 -0700, Linus Torvalds wrote: > Ok, > I don't think there really is anything very interesting here, but we're > hopefully whittling down the list of regressions, and fixing various > random other small issues while at it. > > Some smallish MIPS updates, networking (and network driver) fixes, removal > of a long obsolete framebuffer driver, etc etc. The shortlog really tells > the story. > > We should be getting close to a 2.6.21 release, so please update any > regression reports you've done, regression update for 21-rc6: 1) all s2ram and NO_HZ related things seem to be resolved on my macbook pro, also CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y don't break resume anymore. 2) However I am still having problems with +CONFIG_HIGH_RES_TIMERS=y +CONFIG_HPET=y +CONFIG_HPET_MMAP=y although the machine resumes, I've managed to get the attached oops. 3) Subject: SATA breakage on resume References : http://lkml.org/lkml/2007/3/7/233 Submitter : Thomas Gleixner <[EMAIL PROTECTED]> Soeren Sonnenburg <[EMAIL PROTECTED]> Status : unknown I am still seeing these messages after a suspend/resume cycle (though all devices work even after multiple suspend/resume cycles) ATA: abnormal status 0x80 on port 0x000140df ata3.01: revalidation failed (errno=-2) ata3: failed to recover some devices, retrying in 5 secs ata1.00: configured for UDMA/33 ATA: abnormal status 0x7F on port 0x000140df ATA: abnormal status 0x7F on port 0x000140df ata3.01: configured for UDMA/133 So that's been a big step forward... Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 CPU1 is down Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Back to C! irq 9: nobody cared (try booting with the "irqpoll" option) [] __report_bad_irq+0x24/0x90 [] note_interrupt+0x22f/0x260 [] acpi_irq+0xb/0x14 [] handle_IRQ_event+0x25/0x60 [] handle_level_irq+0xe0/0x110 [] do_IRQ+0x3b/0x80 [] smp_apic_timer_interrupt+0x57/0x90 [] common_interrupt+0x23/0x28 [] __kfifo_put+0x78/0x90 [] __do_softirq+0x6d/0xf0 [] do_softirq+0x37/0x40 [] irq_exit+0x7a/0x90 [] smp_apic_timer_interrupt+0x57/0x90 [] retrigger_next_event+0x0/0xb0 [] apic_timer_interrupt+0x28/0x30 [] retrigger_next_event+0x0/0xb0 [] __kfifo_put+0x8/0x90 [] on_each_cpu+0x35/0x60 [] clock_was_set+0x18/0x20 [] timekeeping_resume+0x7c/0xa0 [] __sysdev_resume+0x11/0x80 [] sysdev_resume+0x47/0x80 [] device_power_up+0x5/0x10 [] suspend_enter+0x56/0x60 [] enter_state+0x11a/0x1c0 [] state_store+0xbd/0xd0 [] state_store+0x0/0xd0 [] subsys_attr_store+0x29/0x40 [] sysfs_write_file+0xb2/0x110 [] vfs_write+0xa6/0x140 [] sysfs_write_file+0x0/0x110 [] sys_write+0x41/0x70 [] sysenter_past_esp+0x5f/0x85 === handlers: [] (acpi_irq+0x0/0x14) Disabling IRQ #9 Enabling non-boot CPUs ... SMP alternatives: switching to SMP code
