On Wed, Nov 14, 2012 at 05:58:37PM -0500, Josh Boyer wrote:
On Wed, Nov 14, 2012 at 03:25:23PM -0600, Bruno Wolff III wrote:
> On Wed, Nov 14, 2012 at 15:04:51 -0500,
> Josh Boyer <jwboyer(a)redhat.com> wrote:
> >>[ 0.000000] Linux version 3.7.0-0.rc5.git0.2.fc19.i686.PAE (mockbuild@)
(gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #1 SMP Mon Nov 12 00:08:40 UTC 2012
> >You rebuilt your kernel? Or where did you get this? That build isn't
> >in koji.
> That one is from the new no-debug repo. I was seeing the same bug
> with ones from the normal rawhide repo as well.
> >I don't see any similar issues using the latest rawhide build in a VM,
> >so this is very curious. Is the dahdi-linux rebuild doing signing?
> Not that I am aware of. The build script pre-dates the signing stuff.
> I'll try a plain rawhide kernel without the dahdi module and see if
> I see those warnings. If not I'll also retest with a rebuilt
> dahdi-linux and see if they still show up. I can't do remote
> reboots, so I won't be able to test this until tonight.
Ugh. Don't bother. It isn't dahdi-linux doing it.
I looked closer and noticed you're using the PAE kernel, so I grabbed
that locally and booted it and saw the same problem. The issue is that
the modules for the PAE kernel are getting signed by the normal i686
kernel key. The i686 kernel+modules are fine.
I'll look at this more tonight and see if I can't get it fixed.
OK. I think I fixed this in F18/rawhide. I started another build for
rawhide with the fix included, but I'm not sure if it will make the
compose for tomorrow's repo.
I'm on PTO tomorrow, so if it isn't fixed for some reason just let me
know and I'll get back to it first thing.