Re: 3.5.0 kernel problem

2012-06-04 Thread Josh Boyer
On Mon, Jun 4, 2012 at 1:54 PM, Andre Robatino
 wrote:
> I'm using a Rawhide VirtualBox 4.1.16 guest set up to automatically install
> guest additions via dkms for each new kernel. My problem is apparently caused 
> by
> failure of the guest additions to build properly with the 3.5.0 kernel. When 
> it
> attempts to build (either when I install a new 3.5.0 kernel, or boot into one)
> it causes the corruption I mentioned. For the time being I've removed dkms in
> the guest. The next version of VirtualBox will probably have a fix.
>
> http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/475811-re-linux-kernel-3-5-rcx-has-been-released-test-post-your-commentshere-post2467176.html

Someone else reported issues with VBox and the 3.5 kernel upstream.
The changes to mmap broke the build of it.  Al Viro looked at it and
apparently found that vbox has some dodgy code that was relying on some
of the old symbols and needs to be rewritten.

I am utterly unsurprised in this development.

Anyway, as you said, VirtualBox needs to fix itself.  There's nothing
we can do here.

josh
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

3.5.0 kernel problem

2012-06-04 Thread Andre Robatino
I'm using a Rawhide VirtualBox 4.1.16 guest set up to automatically install
guest additions via dkms for each new kernel. My problem is apparently caused by
failure of the guest additions to build properly with the 3.5.0 kernel. When it
attempts to build (either when I install a new 3.5.0 kernel, or boot into one)
it causes the corruption I mentioned. For the time being I've removed dkms in
the guest. The next version of VirtualBox will probably have a fix.

http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/475811-re-linux-kernel-3-5-rcx-has-been-released-test-post-your-commentshere-post2467176.html

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 3.5.0 kernel problem

2012-06-03 Thread Frank Murphy

On 03/06/12 21:26, Josh Boyer wrote:


In all cases I did not get an initramfs. In all cases these kernels will
not boot.


https://bugzilla.redhat.com/show_bug.cgi?id=826689


https://bugzilla.redhat.com/show_bug.cgi?id=824981

I've had this a while, as discussed on test list.
I blame dracut, dracut blames grubby.

Which is a duplicate of which,
systemd obliterating udev, hasn't helped the mix.


--
Regards,
Frank
"Jack of all, fubars"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

3.5.0 kernel problem

2012-06-03 Thread Andre Robatino
Josh Boyer  gmail.com> writes:

> That sounds like a deltarpm problem.  The kernel-devel package has that
> file in it, and it's a normal file not a symlink or something.  If you
> download the full RPM and install it via RPM (not yum, or disable the
> deltarpm plugin) does it exist?

Yum-presto shouldn't matter since when it sees an error like this, it would
download the full RPM instead, and even if it didn't, if the rebuild
subsequently failed it would download the full RPM after that. It shouldn't be
possible for a corrupted RPM to get into the transaction.

Anyway, I downloaded kernel-devel-3.5.0-0.rc0.git12.1.fc18.x86_64.rpm from Koji
and used yum reinstall on it. After this, the corresponding System.map file
exists, though it didn't before. While doing this, I was running the 3.4.0
non-debug kernel as usual.

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 3.5.0 kernel problem

2012-06-03 Thread David
On 6/3/2012 4:26 PM, Josh Boyer wrote:
> On Sun, Jun 3, 2012 at 1:02 PM, David  wrote:
>> First - If this is the wrong place for this please tell me where.
>>
>> Rawhide (Fedora 18)
>>
>> I have never been able to install and configure any of the 3.5.0
>> kernels. They install but fail to create a initramfs file. Hence they
>> will not boot.
>>
>> I have seen two different 'failed' messages. One from today is
>> "Non-fatel POSTTRANS scriptlet failure in rpm package
>> kernel-3.5.0-0.rc0.git11.1.fc18.x86_64. I got no initramfs file for this
>> kernel.
>>
>> The other 'failed' message, which I unfortunately did not write down,
>> was a failure to
>> 'find modules' that showed the path to where they expected to find these
>> modules. I got no initramfs file for these kernels either.
>>
>> In all cases I did not get an initramfs. In all cases these kernels will
>> not boot.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=826689
> 


That sounds exactly what I am seeing. I did search for 'something like
this' but I found nothing. I must have asked the wrong question.

Thank you for the link.


-- 

  David
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 3.5.0 kernel problem

2012-06-03 Thread Josh Boyer
On Sun, Jun 3, 2012 at 2:47 PM, Andre Robatino
 wrote:
> David  gmail.com> writes:
>
>> In all cases I did not get an initramfs. In all cases these kernels will
>> not boot.
>
> I have
>
> kernel-3.4.0-1.fc18.x86_64
> kernel-3.5.0-0.rc0.git11.1.fc18.x86_64
> kernel-3.5.0-0.rc0.git12.1.fc18.x86_64
>
> installed, I have an initramfs for all of them, and testing the latest one, it
> boots properly (most of the time I just boot into a non-debug kernel in 
> runlevel
> 3, apply updates, and shut down). I see a different problem - for the latest
> 3.5.0 kernels, kernel-devel does not contain the file
> /usr/src/kernels/*/System.map. For example, when installing the latest kernel 
> I
> saw
>
> Processing delta metadata
> /usr/src/kernels/3.5.0-0.rc0.git11.1.fc18.x86_64/System.map: No such file or
> directory
> delta does not match installed data

That sounds like a deltarpm problem.  The kernel-devel package has that
file in it, and it's a normal file not a symlink or something.  If you
download the full RPM and install it via RPM (not yum, or disable the
deltarpm plugin) does it exist?

Dependencies Resolved


 Package  Arch   Version  Repository   Size

Installing:
 kernel-devel x86_64 3.5.0-0.rc0.git12.1.fc18
/kernel-devel-3.5.0-0.rc0.git12.1.fc18.x86_64
   28 M
Removing:
 kernel-devel x86_64 3.3.4-5.fc17 @updates-testing 28 M

Transaction Summary

Install  1 Package
Remove   1 Package

Total size: 28 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : kernel-devel-3.5.0-0.rc0.git12.1.fc18.x86_64 1/2
  Cleanup: kernel-devel-3.3.4-5.fc17.x86_64 2/2
  Verifying  : kernel-devel-3.5.0-0.rc0.git12.1.fc18.x86_64 1/2
  Verifying  : kernel-devel-3.3.4-5.fc17.x86_64 2/2

Removed:
  kernel-devel.x86_64 0:3.3.4-5.fc17

Installed:
  kernel-devel.x86_64 0:3.5.0-0.rc0.git12.1.fc18

Complete!
[jwboyer@vader ~]$ ls
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map
[jwboyer@vader ~]$ ls -l
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map
-rw-r--r--. 1 root root 2611877 Jun  2 08:16
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map
[jwboyer@vader ~]$ file
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map
/usr/src/kernels/3.5.0-0.rc0.git12.1.fc18.x86_64/System.map: ASCII text
[jwboyer@vader ~]$


josh
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 3.5.0 kernel problem

2012-06-03 Thread Josh Boyer
On Sun, Jun 3, 2012 at 1:02 PM, David  wrote:
> First - If this is the wrong place for this please tell me where.
>
> Rawhide (Fedora 18)
>
> I have never been able to install and configure any of the 3.5.0
> kernels. They install but fail to create a initramfs file. Hence they
> will not boot.
>
> I have seen two different 'failed' messages. One from today is
> "Non-fatel POSTTRANS scriptlet failure in rpm package
> kernel-3.5.0-0.rc0.git11.1.fc18.x86_64. I got no initramfs file for this
> kernel.
>
> The other 'failed' message, which I unfortunately did not write down,
> was a failure to
> 'find modules' that showed the path to where they expected to find these
> modules. I got no initramfs file for these kernels either.
>
> In all cases I did not get an initramfs. In all cases these kernels will
> not boot.

https://bugzilla.redhat.com/show_bug.cgi?id=826689
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

3.5.0 kernel problem

2012-06-03 Thread Andre Robatino
David  gmail.com> writes:

> In all cases I did not get an initramfs. In all cases these kernels will
> not boot.

I have

kernel-3.4.0-1.fc18.x86_64
kernel-3.5.0-0.rc0.git11.1.fc18.x86_64
kernel-3.5.0-0.rc0.git12.1.fc18.x86_64

installed, I have an initramfs for all of them, and testing the latest one, it
boots properly (most of the time I just boot into a non-debug kernel in runlevel
3, apply updates, and shut down). I see a different problem - for the latest
3.5.0 kernels, kernel-devel does not contain the file
/usr/src/kernels/*/System.map. For example, when installing the latest kernel I
saw

Processing delta metadata
/usr/src/kernels/3.5.0-0.rc0.git11.1.fc18.x86_64/System.map: No such file or
directory
delta does not match installed data

and surely enough the file does not exist, even though "rpm -ql
kernel-devel-3.5.0-0.rc0.git11.1.fc18.x86_64 | grep System.map" lists it. The
two 3.5.0 kernels have this problem, the 3.4.0 kernel does not.





-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

3.5.0 kernel problem

2012-06-03 Thread David
First - If this is the wrong place for this please tell me where.

Rawhide (Fedora 18)

I have never been able to install and configure any of the 3.5.0
kernels. They install but fail to create a initramfs file. Hence they
will not boot.

I have seen two different 'failed' messages. One from today is
"Non-fatel POSTTRANS scriptlet failure in rpm package
kernel-3.5.0-0.rc0.git11.1.fc18.x86_64. I got no initramfs file for this
kernel.

The other 'failed' message, which I unfortunately did not write down,
was a failure to
'find modules' that showed the path to where they expected to find these
modules. I got no initramfs file for these kernels either.

In all cases I did not get an initramfs. In all cases these kernels will
not boot.
-- 

  David
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel