Re: Weird yum/kernel problem
"Brian Long (brilong)" <[email protected]> Mon, 2 Feb 2015 14:22:40 +0000
| Newsgroups | gmane.linux.rpm.yum |
|---|---|
| Message-ID | <[email protected]> |
--===============7519971720576254499==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_981952A19EA343ACA8101C08465DA353ciscocom_"
--_000_981952A19EA343ACA8101C08465DA353ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Bob,
Since your building things manually, I wonder if the old /usr/src/linux sym=
link is the issue? If you install a new kernel, it might create that symli=
nk pointing to its specific headers. When you remove the kernel RPM, it wo=
n=92t restore the symlink to the previous kernel headers. I=92m not sure i=
f this is your issue since I=92ve not seen your exact build script or Makef=
ile, but it=92s just a thought.
/Brian/
--
Brian Long | |
Research Triangle Park, NC . | | | . | | | .
' '
C I S C O
On Feb 1, 2015, at 5:24 AM, Bob McKay <[email protected]<mailto:rimsnucse=
@gmail.com>> wrote:
The weirdness continues. I never got 3.17.3 working, but a week or so ago, =
after 3.17.7 had been out for a while, I tried again, and the build worked =
flawlessly. So I was feeling reasonably confident to try 3.17.8 last week. =
But it failed. So I rebooted to 3.17.7 and used rpm to remove 3.17.8 (maybe=
I should have used yum, but I don=92t know how to do that for a kernel). I=
then tried to build the module again. But although I was in kernel 3.17.7,=
and 3.17.8 had been removed, it believed it built a kernel for 3.17.8! i.e=
. the reverse of my previous problem. A bit confusing - it couldn=92t have =
actually built a kernel for 3.17.8, because all the relevant headers and li=
braries no longer existed - but somehow it thought it had, and this seem to=
relate to another issue. It turned out that an rpm uninstall didn=92t remo=
ve the boot files for 3.17.8; removing those by hand allowed me to build a =
module for 3.17.7. So it looked like the build system decided what kernel i=
t had built for by checking what was the latest in /boot??? But this can=92=
t explain the whole problem, because we can be absolutely certain that when=
I was building for the 3.17.8 kernel, the boot files were available (after=
all, I was booted into it).
So basing on Anders=92 comment, it raises another possibility. When a new k=
ernel arrives, I always delay installing it until the corresponding devel a=
nd header files are available in my local mirrors. But if I build soon afte=
r a new kernel turns up, it still always seems to fail. Waiting for a week =
or so often seems to do the trick (but difficult to experiment with, so I=
=92m not certain). Does this ring any bells for anyone? Is there something =
else that the module build process could be relying on to determine what ke=
rnel it has built for - something that might not get updated for a few days=
in remote mirrors, after the kernel, headers and devel have arrived?
Thanks for any suggestions
Bob
On 12 Dec 2014, at 13:03, Bob McKay <[email protected]<mailto:rimsnucse@g=
mail.com>> wrote:
I=92m not sure whether the problem I=92m about to describe is a yum problem=
, or a problem with the way the kernel packages are set up in our Fedora 20=
server. If this is the wrong place to ask, I=92d really appreciate a point=
er to the right one (the Fedora mechanism for yum kernel updates seems to b=
e particularly complex, and I haven=92t properly understood it yet, which i=
s why I=92m not sure where the real problem lies).
I have some RAID hardware that requires a driver module to be built after e=
very kernel update (all updates are performed with yum, not package-manager=
). My process is to disable the hardware, boot to the newly-updated kernel,=
build and install the module, then re-enable the harware and reboot. Since=
about mid year, I have been having repeated problems building the module. =
When I build it, the build appears to succeed, but install fails, saying th=
at the module wasn=92t built against the running kernel. This seems to be c=
orrect - when I manually check the magic of the built module, it shows the =
preceding kernel (i.e. at the moment, 3.17.2), although it was built under=
a running 3.17.3 kernel, and is installed in the correct location for 3.17=
.3 modules.
By the way, I have no clear idea how I got to a working 3.17.2 kernel - the=
problem originally occurred at 3.16.3, and I was stuck in that kernel for =
a long while. Fortunately I had some free time on the server a few weeks ag=
o. Somehow something in a complex sequence of grub2-install, grub2-mkconfig=
, removals and reinstallations of the corresponding kernel and kernel-deve=
l, and module rebuilds changed something, and I managed to get the 3.17.2 u=
pdate working. But I haven=92t been able to figure out what it was, or to r=
eproduce it since.
Why it looks like it should build correctly: at the time of building, all k=
ernel components have been fully updated. For example, at the moment, I hav=
e kernel, kernel-devel, kernel-modules-extra and kernel devel all at 3.17.3=
(but of course, I also have earlier versions of kernel, kernel-headers and=
kernel-modules-extra installed as well - in this case, including 3.17.2). =
When I try to do the build and install, it is booted in 3.17.3. So I don=92=
t understand why it builds a 3.17.2 module.
It seems that at the time it is building the module, the system is somehow =
defaulting to building for 3.17.2. That suggests that a necessary flag reco=
rding the current kernel version isn=92t being updated when the kernel is u=
pdated or booted - I haven=92t been able to figure out how the system decid=
es what the current kernel is, so I don=92t know where this flag might be. =
Any suggestions on how this is done (and why it might be failing, or how to=
check it) would be really appreciated.
There is more detail on the problem at:
http://forums.fedoraforum.org/showthread.php?t=3D300863
https://bugzilla.redhat.com/show_bug.cgi?id=3D1167222
but unfortunately no responses in either place yet (possibly because there =
isn=92t sufficient detail - but I have no idea what else to supply).
The system is a production server; it=92s currently running stably with 3.1=
7.2, and I can=92t reboot very often, so any suggestions that would help me=
to diagnose this problem without rebooting would be particularly appreciat=
ed.
_______________________________________________
Yum mailing list
[email protected]<mailto:[email protected]>
http://lists.baseurl.org/mailman/listinfo/yum
--_000_981952A19EA343ACA8101C08465DA353ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <[email protected]>
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
Bob,
<div>Since your building things manually, I wonder if the old /usr/src/linu=
x symlink is the issue? If you install a new kernel, it might create =
that symlink pointing to its specific headers. When you remove the ke=
rnel RPM, it won=92t restore the symlink to
the previous kernel headers. I=92m not sure if this is your issue si=
nce I=92ve not seen your exact build script or Makefile, but it=92s just a =
thought.</div>
<div><br>
</div>
<div>/Brian/<br>
<div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-style: nor=
mal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; t=
ext-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -we=
bkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: bre=
ak-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-style: nor=
mal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; t=
ext-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -we=
bkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: bre=
ak-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-style: nor=
mal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; t=
ext-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -we=
bkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: bre=
ak-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "=
>
<div style=3D"color: rgb(0, 0, 0); font-variant: normal; letter-spacing: no=
rmal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-inden=
t: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing:=
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-=
wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white=
-space; ">
<div><font face=3D"Courier New">-- </font></div>
<div><font face=3D"Courier New"> Brian Long  =
; &nb=
sp; | |</font></div>
<div><font face=3D"Courier New"> Research Triangl=
e Park, NC . | | | . | | | .</font></div>
<div><font face=3D"Courier New"> &=
nbsp; =
' '</font><=
/div>
<div><font face=3D"Courier New"> &=
nbsp; =
C I S C O</font></div>
</div>
</div>
</div>
</div>
</div>
<br>
<div>
<div>On Feb 1, 2015, at 5:24 AM, Bob McKay <<a href=3D"mailto:rimsnucse@=
gmail.com">[email protected]</a>> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
The weirdness continues. I never got 3.17.3 working, but a week or so ago, =
after 3.17.7 had been out for a while, I tried again, and the build worked =
flawlessly. So I was feeling reasonably confident to try 3.17.8 last week. =
But it failed. So I rebooted to
3.17.7 and used rpm to remove 3.17.8 (maybe I should have used yum, but I =
don=92t know how to do that for a kernel). I then tried to build the module=
again. But although I was in kernel 3.17.7, and 3.17.8 had been removed, i=
t believed it built a kernel for 3.17.8!
i.e. the reverse of my previous problem. A bit confusing - it couldn=92t h=
ave actually built a kernel for 3.17.8, because all the relevant headers an=
d libraries no longer existed - but somehow it thought it had, and this see=
m to relate to another issue. It turned
out that an rpm uninstall didn=92t remove the boot files for 3.17.8; remov=
ing those by hand allowed me to build a module for 3.17.7. So it looked lik=
e the build system decided what kernel it had built for by checking what wa=
s the latest in /boot??? But this
can=92t explain the whole problem, because we can be absolutely certain th=
at when I was building for the 3.17.8 kernel, the boot files were available=
(after all, I was booted into it).
<div><br>
</div>
<div>So basing on Anders=92 comment, it raises another possibility. When a =
new kernel arrives, I always delay installing it until the corresponding de=
vel and header files are available in my local mirrors. But if I build soon=
after a new kernel turns up, it still
always seems to fail. Waiting for a week or so often seems to do the trick=
(but difficult to experiment with, so I=92m not certain). Does this ring a=
ny bells for anyone? Is there something else that the module build process =
could be relying on to determine what
kernel it has built for - something that might not get updated for a few d=
ays in remote mirrors, after the kernel, headers and devel have arrived?&nb=
sp;</div>
<div><br>
</div>
<div> Thanks for any suggestions</div>
<div> Bob<br>
<div><br>
</div>
<div><br>
<div>
<div>On 12 Dec 2014, at 13:03, Bob McKay <<a href=3D"mailto:rimsnucse@gm=
ail.com">[email protected]</a>> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
I=92m not sure whether the problem I=92m about to describe is a yum problem=
, or a problem with the way the kernel packages are set up in our Fedora 20=
server. If this is the wrong place to ask, I=92d really appreciate a point=
er to the right one (the Fedora mechanism
for yum kernel updates seems to be particularly complex, and I haven=92t p=
roperly understood it yet, which is why I=92m not sure where the real probl=
em lies).
<div><br>
</div>
<div>I have some RAID hardware that requires a driver module to be built af=
ter every kernel update (all updates are performed with yum, not package-ma=
nager). My process is to disable the hardware, boot to the newly-updated ke=
rnel, build and install the module,
then re-enable the harware and reboot. Since about mid year, I have been h=
aving repeated problems building the module. When I build it, the build app=
ears to succeed, but install fails, saying that the module wasn=92t built a=
gainst the running kernel. This seems
to be correct - when I manually check the magic of the built module, it sh=
ows the preceding kernel (i.e. at the moment, 3.17.2), although it wa=
s built under a running 3.17.3 kernel, and is installed in the correct loca=
tion for 3.17.3 modules.</div>
<div><br>
</div>
<div>By the way, I have no clear idea how I got to a working 3.17.2 ke=
rnel - the problem originally occurred at 3.16.3, and I was stuck in t=
hat kernel for a long while. Fortunately I had some free time on the server=
a few weeks ago. Somehow something in a complex
sequence of grub2-install, grub2-mkconfig , removals and reinstallations o=
f the corresponding kernel and kernel-devel, and module rebuilds changed so=
mething, and I managed to get the 3.17.2 update working. But I haven=92t be=
en able to figure out what it was,
or to reproduce it since.</div>
<div>
<div><br>
</div>
<div>Why it looks like it should build correctly: at the time of building, =
all kernel components have been fully updated. For example, at the moment, =
I have kernel, kernel-devel, kernel-modules-extra and kernel devel all at 3=
.17.3 (but of course, I also have
earlier versions of kernel, kernel-headers and kernel-modules-extra instal=
led as well - in this case, including 3.17.2). When I try to do the build a=
nd install, it is booted in 3.17.3. So I don=92t understand why it builds a=
3.17.2 module.</div>
<div><br>
</div>
<div>It seems that at the time it is building the module, the system is som=
ehow defaulting to building for 3.17.2. That suggests that a necessary flag=
recording the current kernel version isn=92t being updated when the kernel=
is updated or booted - I haven=92t
been able to figure out how the system decides what the current kernel is,=
so I don=92t know where this flag might be. Any suggestions on how this is=
done (and why it might be failing, or how to check it) would be really app=
reciated.</div>
</div>
<div><br>
</div>
<div>There is more detail on the problem at:</div>
<div><a href=3D"http://forums.fedoraforum.org/showthread.php?t=3D300863">ht=
tp://forums.fedoraforum.org/showthread.php?t=3D300863</a></div>
<div><a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1167222">http=
s://bugzilla.redhat.com/show_bug.cgi?id=3D1167222</a></div>
<div>but unfortunately no responses in either place yet (possibly because t=
here isn=92t sufficient detail - but I have no idea what else to supply).&n=
bsp;</div>
<div><br>
</div>
<div>The system is a production server; it=92s currently running stably wit=
h 3.17.2, and I can=92t reboot very often, so any suggestions that would he=
lp me to diagnose this problem without rebooting would be particularly appr=
eciated.</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
_______________________________________________<br>
Yum mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
http://lists.baseurl.org/mailman/listinfo/yum<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>
--_000_981952A19EA343ACA8101C08465DA353ciscocom_--
--===============7519971720576254499==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Yum mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum
--===============7519971720576254499==--