From: Dave Jones <davej@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
rmk+kernel@arm.linux.org.uk
Subject: Re: kobject: delayed kobject release: help find buggy drivers
Date: Thu, 5 Sep 2013 11:47:00 -0400 [thread overview]
Message-ID: <20130905154700.GD24177@redhat.com> (raw)
In-Reply-To: <20130905153457.GA27954@kroah.com>
On Thu, Sep 05, 2013 at 08:34:57AM -0700, Greg KH wrote:
> > Trace:
> > <IRQ>
> > run_timer_softirq
> > __do_softirq
> > irq_exit
> > smp_apic_timer_interrupt
> > apic_timer_interrupt
> > <EOI>
> > vprintk_emit
> > dev_vprintk_emit
> > dev_vprint_emit
> > __dev_printk
> > _dev_info
> > ahci_print_info
> > ahci_init_one
> > local_pci_probe
> > pci_device_probe
> > driver_probe_device
> > __driver_attach
> > bus_for_each_dev
> > driver_attach
> > bus_add_driver
> > driver_register
> > __pci_register_driver
> > ahci_pci_driver_init
>
> So we are loading a ahci driver here. Any hint as to which
> driver/device this is? Is it a device that fails for this driver, and
> then falls back to another more "specific" one?
It's "ahci.ko" (though it's built in).
For a boring onboard intel sata controller...
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
When I disable the debug option, usually it looks like..
[ 6.382970] ahci 0000:00:1f.2: version 3.0
[ 6.384753] ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
[ 6.385039] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x6 impl SATA mode
[ 6.385067] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
[ 6.385101] ahci 0000:00:1f.2: setting latency timer to 64
[ 6.402536] scsi0 : ahci
[ 6.403669] scsi1 : ahci
[ 6.404208] scsi2 : ahci
[ 6.404756] scsi3 : ahci
[ 6.405342] scsi4 : ahci
[ 6.405951] scsi5 : ahci
[ 6.406345] ata1: DUMMY
[ 6.406364] ata2: SATA max UDMA/133 abar m2048@0xc043b000 port 0xc043b180 irq 43
[ 6.406393] ata3: SATA max UDMA/133 abar m2048@0xc043b000 port 0xc043b200 irq 43
[ 6.406416] ata4: DUMMY
[ 6.406427] ata5: DUMMY
[ 6.406438] ata6: DUMMY
Dave
next prev parent reply other threads:[~2013-09-05 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130903185924.046EE660E91@gitolite.kernel.org>
2013-09-03 20:44 ` kobject: delayed kobject release: help find buggy drivers Dave Jones
2013-09-03 20:55 ` Greg KH
2013-09-04 5:23 ` Rusty Russell
2013-09-05 4:13 ` Dave Jones
2013-09-05 4:57 ` Greg KH
2013-09-05 5:00 ` Dave Jones
2013-09-05 5:19 ` Dave Jones
2013-09-05 15:34 ` Greg KH
2013-09-05 15:47 ` Dave Jones [this message]
2013-09-05 17:35 ` Russell King - ARM Linux
2013-09-05 18:13 ` Dave Jones
2013-09-05 19:29 ` Dave Jones
2013-09-05 21:11 ` Dave Jones
2013-09-05 21:26 ` Dave Jones
2013-09-05 21:44 ` Russell King - ARM Linux
2013-09-06 1:11 ` Dave Jones
2013-09-06 7:59 ` Russell King - ARM Linux
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=20130905154700.GD24177@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rusty@rustcorp.com.au \
/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