[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130905211113.GA22201@redhat.com>
Date: Thu, 5 Sep 2013 17:11:13 -0400
From: Dave Jones <davej@...hat.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>,
Greg KH <gregkh@...uxfoundation.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kobject: delayed kobject release: help find buggy drivers
On Thu, Sep 05, 2013 at 03:29:17PM -0400, Dave Jones wrote:
> On Thu, Sep 05, 2013 at 06:35:40PM +0100, Russell King - ARM Linux wrote:
>
> > Dave - thanks for your patience and effort in trying to track this down.
> > Hopefully the patch below will make it easier.
>
> I'm not sure if this is happening because I enabled DEBUG_KOBJECT this time around
> or not, but now I'm seeing a different trace. (same hang though)
>
> serial8250: ttyS0 at I/O 0x3f8 (ieq =4, base_baud = 115200) is 16550A
> Oops
> RIP: kobject_release
> trace:
>
> kobject_put
> cdev_del
> tty_unregister_device
> uart_remove_one_port
> serial8250_register_8250_port
> pciserial_init_ports
> pciserial_init_one
> local_pci_probe
> pci_device_probe
> driver_probe_device
> __driver_attach
> ? __device_attach
> bus_for_each_dev
> driver_attach
> bus_add_driver
> ? early_serial_setup
> driver_register
> ? early_serial_setup
> __pci_register_driver
> serial_pci_driver_init
> do_one_initcall
>
>
> Trying without serial console next..
rebuilt with all serial turned off.
no luck, then it oopses somewhere else. I'm suspecting something isn't
right with that debug patch, as the next trace is also in kobject_release
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists