linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Dominic Ijichi <dom@ijichi.org>
Cc: linux-ide@vger.kernel.org, axboe@suse.de, jgarzik@pobox.com
Subject: Re: [PATCH 6/6 update] SATA ACPI: ata_acpi functions
Date: Wed, 7 Dec 2005 10:34:49 -0800	[thread overview]
Message-ID: <20051207103449.2922faf3.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <1133976270.43971ace1c015@www.ijichi.org>

On Wed, 07 Dec 2005 17:24:30 +0000
Dominic Ijichi <dom@ijichi.org> wrote:

> Quoting Randy Dunlap <randy_d_dunlap@linux.intel.com>:
> 
> > On Wed, 07 Dec 2005 16:36:47 +0000
> > Dominic Ijichi <dom@ijichi.org> wrote:
> > 
> > > I get a segfault when applying these patches to 2.6.15-rc4.  ahci compiled
> > as
> > > module and inserted through initrd so the module fails with segfault and
> > kernel
> > > doesnt go any further through boot, hence no logging.  last thing screen
> > shows is:
> > >
> > > Code: e3 36 34 c0 c7 44 24 18 29 02 00 00 59 5b 5e 5f 5d e9 f3 05 00 00 53
> > 8b 5c
> > > 2408 e8 e9 03 00 00 a1 dc 0c 42 c0 eb 04 39 d8 74 07 <8b> 40 04 85 c0 75 f5
> > 5b
> > > c3 55 57 56 53 50 8b 44 24 20 8b 5c 24
> > 
> > Can you provide any more of the segfault messages?  That one
> > isn't particularly helpful.
> 
> ok, see below. this is typed in on another computer, i'll try to minimise typos!

OK, well, that's a little better, but the top of the backtrace
is where the nitty gritty info is.
Is it possible for you to use any other method of capturing
more fault messages, like serial console, netconsole,
or even higher resolution video (and smaller font)
so that I can see where the fault is actually happening?

Thanks.

> > Is this on your Fujitsu notebook, with the same hardware
> > configuration as last week?
> 
> yup
> 
> --
> 
> [<c02516c9>] ata_device_add+0x1e9/0x2b0
> [<e082d850>] ahci_interrupt+0x0/0x1e0 [achi]
> [<e082e263>] ahci_init_one+0x1a3/0x270 [achi]
> [<c01cb5d6>] __pci_device_probe+0x56/0x70
> [<c01cb61f>] pci_device_probe+0x2f/0x50
> [<c023b313>] driver_probe_device+0x43/0xd0
> [<c023b420>] __driver_attach+0x0/0x50
> [<c023b461>] __driver_attach+0x41/0x50
> [<c023a84d>] bus_for_each_dev+0x5d/0x80
> [<c023b495>] driver_attach+0x25/0x30
> [<c023b420>] __driver_attach+0x0/0x50
> [<c023ada9>] bus_add_driver+0x89/0xf0
> [<c01cb8a4>] __pci_register_driver+0x74/0xa0
> [<e0832018>] ahci_init+0x18/0x1c [achi]
> [c01364c2>] sys_init_module+0xd/0x210
> [<c0103291>] syscall_call+0x7/0xb
> 
> then the Code: line
> 
> thats all that's left on the screen unfortunately, the rest scrolls off the top.

---
~Randy

  reply	other threads:[~2005-12-07 18:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051202100119.032b242e.randy_d_dunlap@linux.intel.com>
2005-12-02 18:03 ` [PATCH 1/6] libata_suspend (Jens) Randy Dunlap
2005-12-02 18:04 ` [PATCH 2/6] SATA ACPI: make/config changes Randy Dunlap
2005-12-02 18:05 ` [PATCH 3/6] SATA ACPI: libata.h changes Randy Dunlap
2005-12-02 18:07 ` [PATCH 4/6] SATA ACPI: call new ACPI functions Randy Dunlap
2005-12-02 18:07 ` [PATCH 5/6] SATA ACPI: kernel-doc Randy Dunlap
2005-12-02 18:08 ` [PATCH 6/6] SATA ACPI: ata_acpi functions Randy Dunlap
2005-12-06 21:58   ` [PATCH 6/6 update] " Randy Dunlap
2005-12-07 16:36     ` Dominic Ijichi
2005-12-07 17:16       ` Randy Dunlap
2005-12-07 17:24         ` Dominic Ijichi
2005-12-07 18:34           ` Randy Dunlap [this message]
2005-12-08  9:43             ` Dominic Ijichi
2005-12-09  0:16               ` Randy Dunlap
2005-12-09  0:20                 ` Dominic Ijichi
2005-12-09  1:03                   ` Randy Dunlap
2005-12-09  1:10                     ` Randy Dunlap
2005-12-09 18:52                       ` Randy Dunlap
2005-12-10 19:01                         ` Dominic Ijichi
2005-12-12  0:16                           ` Randy.Dunlap
2005-12-02 18:15 ` [PATCH 0/6] SATA use ACPI methods for PM Randy Dunlap
2005-12-12  0:24 [PATCH 6/6 update] SATA ACPI: ata_acpi functions Dominic ES. Ijichi
2005-12-12  0:44 ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2005-12-12  1:24 Dominic ES. Ijichi
2005-12-12  2:13 ` Randy.Dunlap

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=20051207103449.2922faf3.randy_d_dunlap@linux.intel.com \
    --to=randy_d_dunlap@linux.intel.com \
    --cc=axboe@suse.de \
    --cc=dom@ijichi.org \
    --cc=jgarzik@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).