On Thu, Sep 05, 2013 at 09:11:37PM -0400, Dave Jones wrote:
> As discussed on irc, with this updated patch it hangs *really* early in boot.
>
> With earlyprintk=vga I can see some of the trace..
>
> kobject_init
> firmware_map_add_entry
> firmware_map_add_early
> e820_reserve_resources
>
On Thu, Sep 05, 2013 at 09:11:37PM -0400, Dave Jones wrote:
As discussed on irc, with this updated patch it hangs *really* early in boot.
With earlyprintk=vga I can see some of the trace..
kobject_init
firmware_map_add_entry
firmware_map_add_early
e820_reserve_resources
setup_arch
On Thu, Sep 05, 2013 at 10:44:34PM +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 05, 2013 at 05:26:06PM -0400, Dave Jones wrote:
> > On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
> > > > Trying without serial console next..
> > >
> > > rebuilt with all serial turned
On Thu, Sep 05, 2013 at 05:26:06PM -0400, Dave Jones wrote:
> On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
> > > Trying without serial console next..
> >
> > rebuilt with all serial turned off.
> >
> > no luck, then it oopses somewhere else. I'm suspecting something isn't
>
On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
> > 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
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
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,
On Thu, Sep 05, 2013 at 06:35:40PM +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
> > Got it. (I think I was getting tracebacks from multiple cpus, hence
> > the spewing). Adding a check for tainted() = infinite loop to
> > show_backtrace()
On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
> Got it. (I think I was getting tracebacks from multiple cpus, hence
> the spewing). Adding a check for tainted() = infinite loop to
> show_backtrace() combined with boot_delay gave me a really long oops
> that I had to grab video to
On Thu, Sep 05, 2013 at 08:34:57AM -0700, Greg KH wrote:
> > Trace:
> >
> > run_timer_softirq
> > __do_softirq
> > irq_exit
> > smp_apic_timer_interrupt
> > apic_timer_interrupt
> >
> > vprintk_emit
> > dev_vprintk_emit
> > dev_vprint_emit
> > __dev_printk
> > _dev_info
> >
On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
> On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
> > On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
> > > On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
> > >
> > > > >> With this enabled, I
On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
With this enabled, I get a bunch of
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
On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
Got it. (I think I was getting tracebacks from multiple cpus, hence
the spewing). Adding a check for tainted() = infinite loop to
show_backtrace() combined with boot_delay gave me a really long oops
that I had to grab video to record.
On Thu, Sep 05, 2013 at 06:35:40PM +0100, Russell King - ARM Linux wrote:
On Thu, Sep 05, 2013 at 01:19:45AM -0400, Dave Jones wrote:
Got it. (I think I was getting tracebacks from multiple cpus, hence
the spewing). Adding a check for tainted() = infinite loop to
show_backtrace()
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
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
On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
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
I
On Thu, Sep 05, 2013 at 05:26:06PM -0400, Dave Jones wrote:
On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
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
On Thu, Sep 05, 2013 at 10:44:34PM +0100, Russell King - ARM Linux wrote:
On Thu, Sep 05, 2013 at 05:26:06PM -0400, Dave Jones wrote:
On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
Trying without serial console next..
rebuilt with all serial turned off.
On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
> On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
> > On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
> >
> > > >> With this enabled, I get a bunch of scrolling oopses immediately
> > after
> > > >>
On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
> On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
> > On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
> >
> > > >> With this enabled, I get a bunch of scrolling oopses immediately
> > after
> > > >>
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
> On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
>
> > >> With this enabled, I get a bunch of scrolling oopses immediately after
> > >> exiting the bootloader. It happens so early I can't even capture them
> > >> over
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
> >> With this enabled, I get a bunch of scrolling oopses immediately after
> >> exiting the bootloader. It happens so early I can't even capture them
> >> over usb-serial, or earlyprintk=dbgp.
> >>
> >> And for whatever
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
With this enabled, I get a bunch of scrolling oopses immediately after
exiting the bootloader. It happens so early I can't even capture them
over usb-serial, or earlyprintk=dbgp.
And for whatever reason, the printk
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
With this enabled, I get a bunch of scrolling oopses immediately after
exiting the bootloader. It happens so early I can't even capture them
over usb-serial,
On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
With this enabled, I get a bunch of scrolling oopses immediately
after
exiting the
On Wed, Sep 04, 2013 at 09:57:45PM -0700, Greg KH wrote:
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
With this enabled, I get a bunch of scrolling oopses immediately
after
exiting the
160af60920d
>> > Commit: c817a67ecba7c3c2aaa104796d78f160af60920d
>> > Parent: 7c42721fe0c58a848849b43ff558cf2fb86aa35a
>> > Author: Russell King
>> > AuthorDate: Thu Jun 27 15:06:14 2013 +0100
>> > Committer: Greg Kroah-Hartman
>> > CommitDate: Thu Jul 25 15
60920d
> > Parent: 7c42721fe0c58a848849b43ff558cf2fb86aa35a
> > Author: Russell King
> > AuthorDate: Thu Jun 27 15:06:14 2013 +0100
> > Committer: Greg Kroah-Hartman
> > CommitDate: Thu Jul 25 15:39:04 2013 -0700
> >
> >
or: Russell King
> AuthorDate: Thu Jun 27 15:06:14 2013 +0100
> Committer: Greg Kroah-Hartman
> CommitDate: Thu Jul 25 15:39:04 2013 -0700
>
> kobject: delayed kobject release: help find buggy drivers
>
> Implement debugging for kobject release funct
rmk+ker...@arm.linux.org.uk
AuthorDate: Thu Jun 27 15:06:14 2013 +0100
Committer: Greg Kroah-Hartman gre...@linuxfoundation.org
CommitDate: Thu Jul 25 15:39:04 2013 -0700
kobject: delayed kobject release: help find buggy drivers
Implement debugging for kobject release
: 7c42721fe0c58a848849b43ff558cf2fb86aa35a
Author: Russell King rmk+ker...@arm.linux.org.uk
AuthorDate: Thu Jun 27 15:06:14 2013 +0100
Committer: Greg Kroah-Hartman gre...@linuxfoundation.org
CommitDate: Thu Jul 25 15:39:04 2013 -0700
kobject: delayed kobject release: help find
kobject: delayed kobject release: help find buggy drivers
Implement debugging for kobject release functions. kobjects are
reference counted, so the drop of the last reference to them is not
predictable. However, the common case is for the last reference
34 matches
Mail list logo
