Re: SATA Cold Boot problems on >2.6.25 with NV - Kernel

This is a discussion on Re: SATA Cold Boot problems on >2.6.25 with NV - Kernel ; (ccing linux-ide) Tejun, another one of these reset issues? Konstantin Kletschke wrote: > Hello! > > > I found to references regarding this problem in this list. Many Maxwell > reported this and Tejo asked if his supposed fix helps ...

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 20 of 45

Thread: Re: SATA Cold Boot problems on >2.6.25 with NV

  1. Re: SATA Cold Boot problems on >2.6.25 with NV

    (ccing linux-ide)

    Tejun, another one of these reset issues?

    Konstantin Kletschke wrote:
    > Hello!
    >
    >
    > I found to references regarding this problem in this list. Many Maxwell
    > reported this and Tejo asked if his supposed fix helps out.
    >
    > Another reference by Jeff suggests bisecting a git commit. Since I am
    > very unexperienced in the git stuff I hope it is okay to start another
    > initial mail about this to ask
    >
    > 1.) What I should try out on the code to trace this further down
    >
    > 2.) I would extend this problem on >2.6.25 version of kernel.
    >
    > I have an "nForce3 250 chipset" on an Asrock K8Upgrade-NF3 Motherboard
    >
    > 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
    > 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
    > 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
    > 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
    > 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
    > 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
    > 00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
    > 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
    > 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
    > 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)
    > 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
    > 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
    > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
    > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    > 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
    > 02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    >
    > While 2.6.25 works very fine I experienced this with 2.6.26_rc7 at first
    > (I skipped versions between). Cold Boot yields into the described error,
    > I sadly only have real screenshots of this:
    >
    > http://ludenkalle.de/sata
    >
    > After a reset the Kernel was not able to do anything useful with the
    > SATA interface anymore (this description is a bit vague, IIRC it stuck
    > immediately around "SATA Link down..."). Only powercycling helped out,
    > then it booted with SATA.
    >
    > Now I have 2.6.27-rc3, same error but config netconsole enabled.
    > Normal Boot:
    >
    > ata1: SATA link down (SStatus 0 SControl 300)
    > ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    > ata2.00: ATA-7: SAMSUNG HD753LJ, 1AA01106, max UDMA7
    > ata2.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    > ata2.00: configured for UDMA/133
    > isa bounce pool size: 16 pages
    > scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD753LJ 1AA0 PQ: 0 ANSI: 5
    > sd 1:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB)
    > sd 1:0:0:0: [sda] Write Protect is off
    > sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    > sd 1:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB)
    > sd 1:0:0:0: [sda] Write Protect is off
    > sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    > sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
    > sd 1:0:0:0: [sda] Attached SCSI disk
    > PNP: No PS/2 controller found. Probing ports directly.
    > serio: i8042 KBD port at 0x60,0x64 irq 1
    > serio: i8042 AUX port at 0x60,0x64 irq 12
    > TCP cubic registered
    > NET: Registered protocol family 17
    > XFS mounting filesystem sda1
    > VFS: Mounted root (xfs filesystem) readonly.
    > Freeing unused kernel memory: 220k freed
    >
    > Cold Boot:
    >
    > ata1: SATA link down (SStatus 0 SControl 300)
    > ata2: link is slow to respond, please be patient (ready=0)
    > ata2: COMRESET failed (errno=-16)
    > ata2: link is slow to respond, please be patient (ready=0)
    > ata2: COMRESET failed (errno=-16)
    > ata2: link is slow to respond, please be patient (ready=0)
    > ata2: COMRESET failed (errno=-16)
    > ata2: limiting SATA link speed to 1.5 Gbps
    > ata2: COMRESET failed (errno=-16)
    > ata2: reset failed, giving up
    > PNP: No PS/2 controller found. Probing ports directly.
    > serio: i8042 KBD port at 0x60,0x64 irq 1
    > serio: i8042 AUX port at 0x60,0x64 irq 12
    > TCP cubic registered
    > NET: Registered protocol family 17
    > VFS: Cannot open root device "801" or unknown-block(8,1)
    > Please append a correct "root=" boot option; here are the available partitions:
    > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
    >
    > Hmn, thats it. Where should I poke into?
    >
    > Kind Regards, Konsti
    >
    >


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: SATA Cold Boot problems on >2.6.25 with NV

    Robert Han**** wrote:
    > (ccing linux-ide)
    >
    > Tejun, another one of these reset issues?


    Yeah, looks like it. I just sent the patch for #upstream-fixes and will
    forward it to -stable once it gets into #upstream-fixes.

    http://article.gmane.org/gmane.linux.ide/34077

    Thanks.

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-08-29 16:52 +0200 schrieb Tejun Heo:

    > http://article.gmane.org/gmane.linux.ide/34077


    I have this patch actually applied and had switched off the computer
    afterwards completely for more than one hour two times. Each time it
    booted then (this was the patch you suggested initially to Many Maxwell
    this month to this list).

    Everything seems to work fine, but my dmesg and /var/log/messages is
    flooded with this now:

    Aug 29 23:20:39 zappa ata1: EH complete
    Aug 29 23:20:41 zappa ata1: EH complete
    Aug 29 23:20:47 zappa ata1: EH complete
    Aug 29 23:20:49 zappa ata1: EH complete
    Aug 29 23:20:51 zappa ata1: EH complete
    Aug 29 23:20:53 zappa ata1: EH complete
    Aug 29 23:20:55 zappa ata1: EH complete
    Aug 29 23:20:56 zappa ata1: EH complete
    Aug 29 23:20:59 zappa ata1: EH complete
    Aug 29 23:21:01 zappa ata1: EH complete

    I am curious if it boots tomorrow after sleeping for one night :-P

    Regards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: SATA Cold Boot problems on >2.6.25 with NV

    Konstantin Kletschke wrote:
    > Am 2008-08-29 16:52 +0200 schrieb Tejun Heo:
    >
    >> http://article.gmane.org/gmane.linux.ide/34077

    >
    > I have this patch actually applied and had switched off the computer
    > afterwards completely for more than one hour two times. Each time it
    > booted then (this was the patch you suggested initially to Many Maxwell
    > this month to this list).
    >
    > Everything seems to work fine, but my dmesg and /var/log/messages is
    > flooded with this now:
    >
    > Aug 29 23:20:39 zappa ata1: EH complete
    > Aug 29 23:20:41 zappa ata1: EH complete
    > Aug 29 23:20:47 zappa ata1: EH complete
    > Aug 29 23:20:49 zappa ata1: EH complete
    > Aug 29 23:20:51 zappa ata1: EH complete
    > Aug 29 23:20:53 zappa ata1: EH complete
    > Aug 29 23:20:55 zappa ata1: EH complete
    > Aug 29 23:20:56 zappa ata1: EH complete
    > Aug 29 23:20:59 zappa ata1: EH complete
    > Aug 29 23:21:01 zappa ata1: EH complete


    Hmm... Can you post full dmesg output? We used to see things like above
    when ATAPI CHECK SENSE handling somehow failed to tell EH that it was an
    exception not worth whining about. Maybe EH action mask is not being
    cleared properly?

    > I am curious if it boots tomorrow after sleeping for one night :-P


    I somehow feel pretty optimistic about that part. :-)

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-08-30 11:14 +0200 schrieb Tejun Heo:

    > Hmm... Can you post full dmesg output? We used to see things like above


    Of course :-)

    dmesg is attached with patch applied. At the end of the patch it (of
    course) continues, but only with:

    ata1: EH complete
    ata1: EH complete
    ata1: EH complete
    ....

    > when ATAPI CHECK SENSE handling somehow failed to tell EH that it was an
    > exception not worth whining about. Maybe EH action mask is not being
    > cleared properly?


    Hmn, to take my pants down entirely: What is this "EH"?

    And how does the change of the .reset function affect this? May be, I
    will take a look onto this.

    > > I am curious if it boots tomorrow after sleeping for one night :-P

    >
    > I somehow feel pretty optimistic about that part. :-)


    You are right, it started immediately without a hitch this morning after
    sleeping entirely for a couple of hours.

    Kind Regards, Konsti


    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF


  6. Re: SATA Cold Boot problems on >2.6.25 with NV

    Konstantin Kletschke wrote:
    >> when ATAPI CHECK SENSE handling somehow failed to tell EH that it was an
    >> exception not worth whining about. Maybe EH action mask is not being
    >> cleared properly?

    >
    > Hmn, to take my pants down entirely: What is this "EH"?


    libata EH == libatata exception handling.

    > And how does the change of the .reset function affect this? May be, I
    > will take a look onto this.


    Your controller is raising exception continuously for some reason.
    Have no idea yet.

    Can you please apply the attached patch and post the resulting dmesg?

    --
    tejun

    ---
    drivers/ata/libata-eh.c | 4 ++--
    1 file changed, 2 insertions(+), 2 deletions(-)

    Index: tree0/drivers/ata/libata-eh.c
    ================================================== =================
    --- tree0.orig/drivers/ata/libata-eh.c
    +++ tree0/drivers/ata/libata-eh.c
    @@ -1890,8 +1890,8 @@ static void ata_eh_link_report(struct at
    nr_failed++;
    }

    - if (!nr_failed && !ehc->i.err_mask)
    - return;
    + //if (!nr_failed && !ehc->i.err_mask)
    + // return;

    frozen = "";
    if (ap->pflags & ATA_PFLAG_FROZEN)

  7. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-01 13:18 +0200 schrieb Tejun Heo:

    > > Hmn, to take my pants down entirely: What is this "EH"?

    >
    > libata EH == libatata exception handling.


    Seems this stuff is kinda new since 2.6.25?

    > Can you please apply the attached patch and post the resulting dmesg?


    Of course. Patch applied, here is dmesg output, looks interesting now -
    but anything works fine so far.

    Regards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF


  8. Re: SATA Cold Boot problems on >2.6.25 with NV

    Konstantin Kletschke wrote:
    > Am 2008-09-02 06:35 +0200 schrieb Tejun Heo:
    >
    >>> Seems this stuff is kinda new since 2.6.25?

    >> I think it's more circa 2.6.22 but in my memory terms, which sucks,
    >> that's a lifetime before so I don't really remember. :-)

    >
    > Okay :-)
    >
    >> Hmm... someone is scheduling EH incessantly without any error or action
    >> set. Can you please try the attached patch?

    >
    > I did and put here all dmesg gave me. Do you want to get the whole stuff
    > from the beginning? /var/log/messages has ist, but it is 416k, I put it
    > on a ftp server somewhere out there then. Or is something else
    > recommended?


    The excerpt is fine but please turn on CONFIG_KALLSYMS. The stack dump
    is pretty much meaningless without it.

    Thanks.

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-02 06:35 +0200 schrieb Tejun Heo:

    > > Seems this stuff is kinda new since 2.6.25?

    >
    > I think it's more circa 2.6.22 but in my memory terms, which sucks,
    > that's a lifetime before so I don't really remember. :-)


    Okay :-)

    > Hmm... someone is scheduling EH incessantly without any error or action
    > set. Can you please try the attached patch?


    I did and put here all dmesg gave me. Do you want to get the whole stuff
    from the beginning? /var/log/messages has ist, but it is 416k, I put it
    on a ftp server somewhere out there then. Or is something else
    recommended?

    Konsti



    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF


  10. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-02 07:45 +0200 schrieb Tejun Heo:

    > The excerpt is fine but please turn on CONFIG_KALLSYMS. The stack dump


    Yea, of course... my bad. First I wondered to turn this on or deliver
    System.map but then I forgot.

    > is pretty much meaningless without it.


    ;-)

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF


  11. Re: SATA Cold Boot problems on >2.6.25 with NV

    On Aug. 30, 2008, 12:14 +0300, Tejun Heo wrote:
    > Konstantin Kletschke wrote:
    >> Am 2008-08-29 16:52 +0200 schrieb Tejun Heo:
    >>
    >>> http://article.gmane.org/gmane.linux.ide/34077

    >> I have this patch actually applied and had switched off the computer
    >> afterwards completely for more than one hour two times. Each time it
    >> booted then (this was the patch you suggested initially to Many Maxwell
    >> this month to this list).
    >>
    >> Everything seems to work fine, but my dmesg and /var/log/messages is
    >> flooded with this now:
    >>
    >> Aug 29 23:20:39 zappa ata1: EH complete
    >> Aug 29 23:20:41 zappa ata1: EH complete
    >> Aug 29 23:20:47 zappa ata1: EH complete
    >> Aug 29 23:20:49 zappa ata1: EH complete
    >> Aug 29 23:20:51 zappa ata1: EH complete
    >> Aug 29 23:20:53 zappa ata1: EH complete
    >> Aug 29 23:20:55 zappa ata1: EH complete
    >> Aug 29 23:20:56 zappa ata1: EH complete
    >> Aug 29 23:20:59 zappa ata1: EH complete
    >> Aug 29 23:21:01 zappa ata1: EH complete


    I'm seeing a similar problem after upgrading from
    2.6.25.14-108.fc9.x86_64 to 2.6.27-rc6.

    From what I can tell the messages
    Sep 23 10:27:20 pangw kernel: ata6: EH pending after 5 tries, giving up
    Sep 23 10:27:20 pangw kernel: ata6: EH complete

    are printed for a disconnected ATA port that's a neighbor
    of one that's occupied.

    these are the ports that are in use:
    Sep 23 10:19:40 pangw kernel: ata1.00: ATA-6: ST3160023A, 3.01, max UDMA/100
    Sep 23 10:19:40 pangw kernel: ata2.00: ATAPI: _NEC DVD_RW ND-3550A, 1.05, max UDMA/33
    [PATA]
    Sep 23 10:19:40 pangw kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    The WDC drive was previously on ata3 and the message were then printed
    for ata4. This makes me thunk it might be related to managing of
    dual-ported sata_nv chips?

    before:
    Sep 21 19:14:10 pangw kernel: sata_nv 0000:00:08.0: PCI INT A -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
    Sep 21 19:14:10 pangw kernel: scsi2 : sata_nv
    Sep 21 19:14:10 pangw kernel: scsi3 : sata_nv
    Sep 21 19:14:10 pangw kernel: ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xcc00 irq 21
    Sep 21 19:14:10 pangw kernel: ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xcc08 irq 21
    Sep 21 19:14:10 pangw kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Sep 21 19:14:10 pangw kernel: ata3.00: ATA-7: WDC WD1600JS-60MHB1, 10.02E02, max UDMA/100
    Sep 21 19:14:10 pangw kernel: ata3.00: 312581808 sectors, multi 16: LBA48
    Sep 21 19:14:10 pangw kernel: ata3.00: configured for UDMA/100
    Sep 21 19:14:10 pangw kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD1600JS-60M 10.0 PQ: 0 ANSI: 5
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] Write Protect is off
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] Write Protect is off
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Sep 21 19:14:10 pangw kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
    Sep 21 19:14:10 pangw kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
    Sep 21 19:14:10 pangw kernel: sata_nv 0000:00:08.0: PCI INT A -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
    Sep 21 19:14:10 pangw kernel: scsi4 : sata_nv
    Sep 21 19:14:10 pangw kernel: scsi5 : sata_nv
    Sep 21 19:14:10 pangw kernel: ata5: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xb800 irq 20
    Sep 21 19:14:10 pangw kernel: ata6: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xb808 irq 20
    Sep 21 19:14:10 pangw kernel: ata4: EH complete

    after:
    Sep 23 09:55:45 pangw kernel: sata_nv 0000:00:08.0: PCI INT A -> Link[APSJ] -> GSI 20 (level, low)
    -> IRQ 20
    Sep 23 09:55:45 pangw kernel: scsi4 : sata_nv
    Sep 23 09:55:45 pangw kernel: scsi5 : sata_nv
    Sep 23 10:19:40 pangw kernel: ata5: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xb800 irq 20
    Sep 23 10:19:40 pangw kernel: ata6: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xb808 irq 20
    Sep 23 10:19:40 pangw kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Sep 23 10:19:40 pangw kernel: ata5.00: ATA-7: WDC WD1600JS-60MHB1, 10.02E02, max UDMA/100
    Sep 23 10:19:40 pangw kernel: ata5.00: 312581808 sectors, multi 16: LBA48
    Sep 23 10:19:40 pangw kernel: ata5.00: configured for UDMA/100
    Sep 23 10:19:40 pangw kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD1600JS-60M 10.0 PQ: 0 ANSI: 5
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] Write Protect is off
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] Write Protect is off
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Sep 23 10:19:40 pangw kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
    Sep 23 10:19:40 pangw kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
    Sep 23 10:19:40 pangw kernel: ata6: EH complete

    Benny

    >
    > Hmm... Can you post full dmesg output? We used to see things like above
    > when ATAPI CHECK SENSE handling somehow failed to tell EH that it was an
    > exception not worth whining about. Maybe EH action mask is not being
    > cleared properly?
    >
    >> I am curious if it boots tomorrow after sleeping for one night :-P

    >
    > I somehow feel pretty optimistic about that part. :-)
    >


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  12. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-23 10:36 +0300 schrieb Benny Halevy:

    > are printed for a disconnected ATA port that's a neighbor
    > of one that's occupied.


    Hey, I did not realize this yet!

    My only SATA device seems to be connected to Port2:

    Sep 24 07:12:47 zappa ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xd808 irq 21
    Sep 24 07:12:47 zappa ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Sep 24 07:12:47 zappa ata2.00: ATA-7: SAMSUNG HD753LJ, 1AA01106, max UDMA7
    Sep 24 07:12:47 zappa ata2.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Sep 24 07:12:47 zappa ata2.00: configured for UDMA/133

    Whereas my message log is still flooded by ata1 stuff:

    Sep 21 11:34:57 zappa ata1: EH complete
    Sep 21 11:34:57 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t4
    Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t3
    Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t2

    Tijo, is there any stuff I should try out? I mean, if I got this right,
    the boot problems itself were fixed by removing nv_hardreset, but is
    there a way around getting the log flooded by "EH complete" now?


    Kind regards, Konsti



    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  13. Re: SATA Cold Boot problems on >2.6.25 with NV

    Please apply the attached patch and post the resulting log. Please
    don't forget to turn on KALLSYMS.

    Thanks.

    --
    tejun


  14. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-24 18:36 +0900 schrieb Tejun Heo:
    > Please apply the attached patch and post the resulting log. Please
    > don't forget to turn on KALLSYMS.


    Mainly this is the patch you posted in

    http://marc.info/?l=linux-kernel&m=122033025206886&w=2

    which I replied with a useless reply containing no debug.
    After that I turned KALLSYMS on and posted, did you miss this?

    here:

    http://marc.info/?l=linux-kernel&m=122033745615187&w=2

    Kind Regards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  15. Re: SATA Cold Boot problems on >2.6.25 with NV

    Replying to myself...

    Indeed my HArddisk was plugged into SATA2 and SATA1 was left empty, I
    moved it to SATA1 now.

    Am 2008-09-24 10:48 +0200 schrieb Konstantin Kletschke:

    > Sep 24 07:12:47 zappa ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xd808 irq 21
    > Sep 24 07:12:47 zappa ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    > Sep 24 07:12:47 zappa ata2.00: ATA-7: SAMSUNG HD753LJ, 1AA01106, max UDMA7
    > Sep 24 07:12:47 zappa ata2.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    > Sep 24 07:12:47 zappa ata2.00: configured for UDMA/133


    > Sep 21 11:34:57 zappa ata1: EH complete
    > Sep 21 11:34:57 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    > Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t4
    > Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t3
    > Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t2


    Now:

    Sep 25 08:35:29 zappa ata1: SATA max UDMA/133 cmd 0xf80 ctl 0xf00 bmdma 0xd800 irq 21
    Sep 25 08:35:29 zappa ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xd808 irq 21
    Sep 25 08:35:29 zappa ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Sep 25 08:35:29 zappa ata1.00: ATA-7: SAMSUNG HD753LJ, 1AA01106, max UDMA7
    Sep 25 08:35:29 zappa ata1.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Sep 25 08:35:29 zappa ata1.00: configured for UDMA/133


    Sep 25 08:35:29 zappa ata2: EH pending after 5 tries, giving up
    Sep 25 08:35:29 zappa ata2: EH complete
    Sep 25 08:35:29 zappa ata2: EH pending after 5 tries, giving up
    Sep 25 08:35:29 zappa ata2: EH complete

    Kind REgards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  16. Re: SATA Cold Boot problems on >2.6.25 with NV


    Tejun, sorry for misspelling your name as Tijo :-/

    Do I hit your spamfilter with my KSYMOOPS enabled debug outputs or some
    sort of that? If not, sorry for the inconvenience and take your time.

    Regards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  17. Re: SATA Cold Boot problems on >2.6.25 with NV

    Konstantin Kletschke wrote:
    > Tejun, sorry for misspelling your name as Tijo :-/
    >
    > Do I hit your spamfilter with my KSYMOOPS enabled debug outputs or some
    > sort of that? If not, sorry for the inconvenience and take your time.


    Sorry about lack of response. I was on vacation after a series of
    conferences. There's a bug entry for this problem and I just posted a
    patch.

    http://bugzilla.kernel.org/show_bug.cgi?id=11615

    Can you please try the patch attached there and post the result there?

    Thanks.

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  18. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-28 06:22 +0900 schrieb Tejun Heo:

    > Sorry about lack of response. I was on vacation after a series of


    Thats no Problem at all :-) I hope the vacation was fine.

    > conferences. There's a bug entry for this problem and I just posted a
    > patch.
    >
    > http://bugzilla.kernel.org/show_bug.cgi?id=11615
    >
    > Can you please try the patch attached there and post the result
    > there?


    Well, this Patch simply installs the old weird behaviour with the
    result in sometimes no cold boot possible yielding into

    ataX: link too slow to response ...
    ataX: COMRESET failed (errno=-16)

    After that powercycle required. I wrote it down from memory. If there
    is a detailed log required I can create them tomorrow when I have my
    Hands back onto the machine.

    Kind Regards, Konsti

    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  19. Re: SATA Cold Boot problems on >2.6.25 with NV

    Konstantin Kletschke wrote:
    > Am 2008-09-28 06:22 +0900 schrieb Tejun Heo:
    >
    >> Sorry about lack of response. I was on vacation after a series of

    >
    > Thats no Problem at all :-) I hope the vacation was fine.
    >
    >> conferences. There's a bug entry for this problem and I just posted a
    >> patch.
    >>
    >> http://bugzilla.kernel.org/show_bug.cgi?id=11615
    >>
    >> Can you please try the patch attached there and post the result
    >> there?

    >
    > Well, this Patch simply installs the old weird behaviour with the
    > result in sometimes no cold boot possible yielding into
    >
    > ataX: link too slow to response ...
    > ataX: COMRESET failed (errno=-16)
    >
    > After that powercycle required. I wrote it down from memory. If there
    > is a detailed log required I can create them tomorrow when I have my
    > Hands back onto the machine.


    Ah.. okay, so generic is not the only one affected by the original
    hardreset problem. Can you please post the result of "lspci -nn"?

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  20. Re: SATA Cold Boot problems on >2.6.25 with NV

    Am 2008-09-30 23:09 +0900 schrieb Tejun Heo:

    > hardreset problem. Can you please post the result of "lspci -nn"?


    00:00.0 Host bridge [0600]: nVidia Corporation nForce3 250Gb Host Bridge [10de:00e1] (rev a1)
    00:01.0 ISA bridge [0601]: nVidia Corporation nForce3 250Gb LPC Bridge [10de:00e0] (rev a2)
    00:01.1 SMBus [0c05]: nVidia Corporation nForce 250Gb PCI System Management [10de:00e4] (rev a1)
    00:02.0 USB Controller [0c03]: nVidia Corporation CK8S USB Controller [10de:00e7] (rev a1)
    00:02.1 USB Controller [0c03]: nVidia Corporation CK8S USB Controller [10de:00e7] (rev a1)
    00:02.2 USB Controller [0c03]: nVidia Corporation nForce3 EHCI USB 2.0 Controller [10de:00e8] (rev a2)
    00:05.0 Bridge [0680]: nVidia Corporation CK8S Ethernet Controller [10de:00df] (rev a2)
    00:06.0 Multimedia audio controller [0401]: nVidia Corporation nForce3 250Gb AC'97 Audio Controller [10de:00ea] (rev a1)
    00:08.0 IDE interface [0101]: nVidia Corporation CK8S Parallel ATA Controller (v2.5) [10de:00e5] (rev a2)
    00:0a.0 IDE interface [0101]: nVidia Corporation CK8S Serial ATA Controller (v2.5) [10de:00e3] (rev a2)
    00:0b.0 PCI bridge [0604]: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge [10de:00e2] (rev a2)
    00:0e.0 PCI bridge [0604]: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge [10de:00ed] (rev a2)
    00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
    00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
    00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
    00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
    01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
    02:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)



    --
    GPG KeyID EF62FCEF
    Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast