public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libATA  PATA status report, new patch
Date: Tue, 7 Feb 2006 19:02:36 +0200 (EET)	[thread overview]
Message-ID: <Pine.SOC.4.61.0602071856520.11554@math.ut.ee> (raw)
In-Reply-To: <1139324653.18391.41.camel@localhost.localdomain>

> I've put up a -ide2 patch at
>
> http://zeniv.linux.org.uk/~alan/IDE

This time a report from an Intel ICH5 machine with 1 PATA disk and 1 
PATA cdrom, worked fine before. Now I got anb oops with previous kernel 
and the dmesg below ith current kernel (recoreded with netconsole). The 
previous fauls was also during partition table reading. This is fully 
reproducible, tried 3 times.

ata1: dev 0 ATA-6, max UDMA/100, 156301488 sectors: LBA
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
   Vendor: ATA       Model: WDC WD800BB-22HE  Rev: 14.0
   Type:   Direct-Access                      ANSI SCSI revision: 05
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x24C8 irq 15
ata2: dev 0 ATAPI, max UDMA/33
ata2: dev 0 configured for UDMA/33
scsi1 : ata_piix
   Vendor: _NEC      Model: DVD_RW ND-3540A   Rev: 1.01
   Type:   CD-ROM                             ANSI SCSI revision: 05
PCI: Found IRQ 11 for device 0000:00:1f.2
PCI: Sharing IRQ 11 with 0000:00:1d.2
PCI: Sharing IRQ 11 with 0000:00:1f.1
ata3: SATA max UDMA/133 cmd 0x24F8 ctl 0x2812 bmdma 0x24D0 irq 11
ata4: SATA max UDMA/133 cmd 0x2800 ctl 0x2816 bmdma 0x24D8 irq 11
ata3: SATA port has no device.
scsi2 : ata_piix
ata4: SATA port has no device.
scsi3 : ata_piix
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Unknown interrupt or fault at EIP 00000286 00000060 c0112acd
sda: Write Protect is off
SCSI device sda: drive cache: write back
  sda:Unknown interrupt or fault at EIP 00000246 00000060 c010162b


-- 
Meelis Roos (mroos@linux.ee)

  reply	other threads:[~2006-02-07 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 16:46 libATA PATA status report, new patch Alan Cox
2006-02-06 20:04 ` Meelis Roos
2006-02-06 22:53   ` Alan Cox
2006-02-07  8:43 ` Meelis Roos
2006-02-07 11:05   ` Alan Cox
2006-02-07 11:10     ` Meelis Roos
2006-02-07 11:29       ` Ed Sweetman
2006-02-07 11:32         ` Meelis Roos
2006-02-07 11:38       ` Alan Cox
2006-02-07 15:04         ` Alan Cox
2006-02-07 17:02           ` Meelis Roos [this message]
2006-02-07 19:38             ` Duplicated SCSI messages (Was: Re: libATA PATA status report, new patch) Tomasz Kłoczko
2006-02-07 17:30           ` libATA PATA status report, new patch Meelis Roos
2006-02-07 17:50           ` Meelis Roos
2006-02-08 13:31             ` Alan Cox
2006-02-08  7:42           ` Meelis Roos
2006-02-08 18:28           ` Meelis Roos
2006-02-09 15:31             ` Alan Cox
2006-02-09 21:12               ` Meelis Roos
2006-02-10 12:01                 ` Erik Mouw
2006-02-10 15:46                   ` Alan Cox
2006-02-12 18:07 ` Kyle Moffett
2006-07-07 16:29 ` Wakko Warner
2006-07-07 16:52   ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SOC.4.61.0602071856520.11554@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox