All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, erikbenada@yahoo.ca, caver_sean@ou.edu
Subject: promise-sata-pata crash on boot
Date: Mon, 23 Oct 2006 09:38:44 -0400	[thread overview]
Message-ID: <453CC5E4.9020001@gentoo.org> (raw)

Hi Jeff,

I've been including the promise-sata-pata patch in the Gentoo kernel for 
quite a while, taken directly from the git branch. The most recent 
incarnations of this patch have stopped working, causing an oops on 
bootup. This has been reproduced with unmodified 2.6.19-rc2 plus the patch.

Unable to handle kernel NULL pointer dereference at 0
RIP: pdc_sata_scr_read+0x3e

Trace:
sata_scr_read
ata_device_add
process_timeout
pdc_ata_init_one
pci_device_probe
driver_probe_device

http://weather.ou.edu/~sarms/panic3.jpeg

We added the following printk to pdc_sata_scr_read:

         printk("pdc_sata_scr_read ap=%p scr_addr %ld sc_reg %d\n", ap,
		ap->ioaddr.scr_addr, sc_reg);

And the output is:

pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 2
pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 0
pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 0
pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 2
pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 0
ata2: SATA link down (SStatus 0 SControl 300)
pdc_sata_src_read ap=ffff8100bfce0498 src_addr -68169720896256 sc_reg 0
pdc_sata_src_read ap=ffff8100bfd08498 src_addr 0 sc_reg 2
Unable to handle kernel NULL pointer dereference

See http://weather.ou.edu/~sarms/panic4.jpeg


Bug report is at http://bugs.gentoo.org/148059
Any ideas? Should we file this on the kernel bugzilla?

Thanks!
Daniel

                 reply	other threads:[~2006-10-23 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=453CC5E4.9020001@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=caver_sean@ou.edu \
    --cc=erikbenada@yahoo.ca \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.