Re: ftrace: function radeon_init not traceable

2020-05-11 Thread Steven Rostedt
958 entries in 61 pages > >> [0.084542] ftrace: allocated 61 pages with 5 groups > >> [0.094184] ftrace: function radeon_init not traceable > >> > >> I believe it worked in the past. Is there a way to trace that init > >> function? > > > >

Re: ftrace: function radeon_init not traceable

2020-05-11 Thread Paul Menzel
pages [0.084542] ftrace: allocated 61 pages with 5 groups [0.094184] ftrace: function radeon_init not traceable I believe it worked in the past. Is there a way to trace that init function? Did it every work for modules? radeon_init() isn't in the symbol table at boot up

Re: ftrace: function radeon_init not traceable

2020-05-11 Thread Steven Rostedt
rejects” that: > > [0.075538] ftrace: allocating 30958 entries in 61 pages > [ 0.084542] ftrace: allocated 61 pages with 5 groups > [0.094184] ftrace: function radeon_init not traceable > > I believe it worked in the past. Is there a way to trace that init function? Did