mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin Radloff" <radsaq@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Updated libata PATA patch
Date: Wed, 10 May 2006 12:39:23 -0400	[thread overview]
Message-ID: <3b0ffc1f0605100939r607ef30dya743a7f1a1dbe03f@mail.gmail.com> (raw)
In-Reply-To: <1147279198.19935.6.camel@localhost.localdomain>

On 5/10/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mer, 2006-05-10 at 12:05 -0400, Kevin Radloff wrote:
> > >         ae.irq_flags = SA_SHIRQ ?
> >
> > Another new and exciting oops :)
>
> Yay, so that one was the PCMCIA code being broken.
>
> > pcmcia: registering new device pcmcia1.0
> > ata3: PATA max PIO0 cmd 0x3100 ctl 0x310E bmdma 0x0 irq 11
> > ata3: dev 0 cfg 49:0200 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0000
> > ata3: dev 0 ATA-10, max PIO4, 2001888 sectors: LBA
> > ata3: dev 0 configured for PIO0
>
> This is all good. Its a PIO0 device (PCMCIA is ISA cycles which are PIO0
> cycles)
>
> > scsi2 : pata_pcmcia
> >   Vendor: ATA       Model: SanDisk SDCFH-10  Rev: HDX
> >   Type:   Direct-Access                      ANSI SCSI revision: 05
> > SCSI device sdb: 2001888 512-byte hdwr sectors (1025 MB)
>
> The disk was found and the indentify data came out correctly.
>
> > sdb: Write Protect is off
> > sdb: Mode Sense: 00 3a 00 00
> > SCSI device sdb: drive cache: write through
> > SCSI device sdb: 2001888 512-byte hdwr sectors (1025 MB)
> > sdb: Write Protect is off
> > sdb: Mode Sense: 00 3a 00 00
> > SCSI device sdb: drive cache: write through
>
> The drive was sized, the cache checked properly.
>
> >  sdb:<1>BUG: unable to handle kernel NULL pointer dereference at
> > virtual address 00000000
>
> Awww.. how to ruin a good day 8)
>
> At this point its trying to read the partition table. It has translated
> the command into a SCSI command block and into ATA,. It has queued it,
> and it has just set out to issue it when it went boom
>
> I'll do some more digging, but putting printks into ata_qc_issue_prot to
> see where it explodes is the next step I suspect.

Ah, I see.. I'll be waiting. :)

--
Kevin 'radsaq' Radloff
radsaq@gmail.com
http://thesaq.com/

  reply	other threads:[~2006-05-10 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 17:44 Alan Cox
2006-05-10  1:48 ` Kevin Radloff
2006-05-10 14:09   ` Alan Cox
2006-05-10 16:05     ` Kevin Radloff
2006-05-10 16:39       ` Alan Cox
2006-05-10 16:39         ` Kevin Radloff [this message]
2006-05-15 22:08           ` Alan Cox
2006-05-15 23:13             ` Alan Cox
2006-05-12  2:34     ` John Stoffel
2006-05-15  2:46       ` John Stoffel
2006-05-11 19:06 ` Matthieu CASTET
2006-05-12 23:04 ` Guennadi Liakhovetski

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=3b0ffc1f0605100939r607ef30dya743a7f1a1dbe03f@mail.gmail.com \
    --to=radsaq@gmail.com \
    --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

all inboxes | Powered by JetHome®