Hi, I've got a kernel bug where a developer has asked me to try a git bisect. Does anyone have tips for doing a kernel bisect with fedora kernel packages? I found a koji bisect thing, but the last known good kernel is prior to the fedora release the machine is currently running, so not sure that is an option. Or do I just have to grit my teeth and try to get vanilla kernels built and installed? Other packages I've just dropped the bisected source directly into my rpmbuild, but guessing it's not going to be quite that simple here.
On Tue, Aug 20, 2013 at 8:25 AM, Ian Malone ibmalone@gmail.com wrote:
Hi, I've got a kernel bug where a developer has asked me to try a git bisect. Does anyone have tips for doing a kernel bisect with fedora kernel packages? I found a koji bisect thing, but the last known good kernel is prior to the fedora release the machine is currently running, so not sure that is an option. Or do I just have to grit my
That shouldn't really be an issue for the most part. It would only impact you if you're hitting issues in an area where the config options differ between releases, and those are fairly uncommon. You can try using koji bisect to start with to at least save yourself some time.
teeth and try to get vanilla kernels built and installed? Other packages I've just dropped the bisected source directly into my rpmbuild, but guessing it's not going to be quite that simple here.
Basically, the best bet is to copy the fedora kernel config into a kernel git tree and just use git bisect, make bzImage, make modules, make modules_install, make install. If you want to save some build time, trim the config to not include the bajillion modules we ship.
josh
On 20 August 2013 13:50, Josh Boyer jwboyer@fedoraproject.org wrote:
On Tue, Aug 20, 2013 at 8:25 AM, Ian Malone ibmalone@gmail.com wrote:
Hi, I've got a kernel bug where a developer has asked me to try a git bisect. Does anyone have tips for doing a kernel bisect with fedora kernel packages? I found a koji bisect thing, but the last known good kernel is prior to the fedora release the machine is currently running, so not sure that is an option. Or do I just have to grit my
That shouldn't really be an issue for the most part. It would only impact you if you're hitting issues in an area where the config options differ between releases, and those are fairly uncommon. You can try using koji bisect to start with to at least save yourself some time.
teeth and try to get vanilla kernels built and installed? Other packages I've just dropped the bisected source directly into my rpmbuild, but guessing it's not going to be quite that simple here.
Basically, the best bet is to copy the fedora kernel config into a kernel git tree and just use git bisect, make bzImage, make modules, make modules_install, make install. If you want to save some build time, trim the config to not include the bajillion modules we ship.
That's great, thanks for the advice.
On 20 August 2013 13:50, Josh Boyer jwboyer@fedoraproject.org wrote:
That shouldn't really be an issue for the most part. It would only impact you if you're hitting issues in an area where the config options differ between releases, and those are fairly uncommon. You can try using koji bisect to start with to at least save yourself some time.
Basically, the best bet is to copy the fedora kernel config into a kernel git tree and just use git bisect, make bzImage, make modules, make modules_install, make install. If you want to save some build time, trim the config to not include the bajillion modules we ship.
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmalone@gmail.com wrote:
On 20 August 2013 13:50, Josh Boyer jwboyer@fedoraproject.org wrote:
That shouldn't really be an issue for the most part. It would only impact you if you're hitting issues in an area where the config options differ between releases, and those are fairly uncommon. You can try using koji bisect to start with to at least save yourself some time.
Basically, the best bet is to copy the fedora kernel config into a kernel git tree and just use git bisect, make bzImage, make modules, make modules_install, make install. If you want to save some build time, trim the config to not include the bajillion modules we ship.
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
Er... it doesn't? Where did you try to get it from, and how did it fail?
josh
On 29 August 2013 01:53, Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmalone@gmail.com wrote:
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
Er... it doesn't? Where did you try to get it from, and how did it fail?
Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summar... Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations.
On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote:
On 29 August 2013 01:53, Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmalone@gmail.com wrote:
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
Er... it doesn't? Where did you try to get it from, and how did it fail?
Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summar... Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations.
-- imalone http://ibmalone.blogspot.co.uk
Hmm. I've read article from jwb and I see koji-bisect should good couple with my proposal [0], but I can't find sources koji-bisect..
[0]https://lists.fedoraproject.org/pipermail/devel/2013-August/188461.html
On Thu, Aug 29, 2013 at 3:32 AM, Igor Gnatenko i.gnatenko.brain@gmail.com wrote:
On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote:
On 29 August 2013 01:53, Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmalone@gmail.com wrote:
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
Er... it doesn't? Where did you try to get it from, and how did it fail?
Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summar... Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations.
Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage.
josh
On Thu, Aug 29, 2013 at 8:26 AM, Josh Boyer jwboyer@fedoraproject.org wrote:
On Thu, Aug 29, 2013 at 3:32 AM, Igor Gnatenko i.gnatenko.brain@gmail.com wrote:
On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote:
On 29 August 2013 01:53, Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmalone@gmail.com wrote:
Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread).
Er... it doesn't? Where did you try to get it from, and how did it fail?
Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summar... Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations.
Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage.
Ok, you can clone it with:
git clone git://fedorapeople.org/~jwboyer/koji-bisect.git
I'm guessing the web browsing part broken when Infrastructure switched from gitweb to cgit. Hopefully I'll get whatever is needed fixed up and it will show up at:
http://fedorapeople.org/cgit/jwboyer/public_git/koji-bisect.git
in the near future.
josh
On 29 August 2013 13:32, Josh Boyer jwboyer@fedoraproject.org wrote:
On Thu, Aug 29, 2013 at 8:26 AM, Josh Boyer jwboyer@fedoraproject.org wrote:
Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage.
Ok, you can clone it with:
git clone git://fedorapeople.org/~jwboyer/koji-bisect.git
I'm guessing the web browsing part broken when Infrastructure switched from gitweb to cgit. Hopefully I'll get whatever is needed fixed up and it will show up at:
http://fedorapeople.org/cgit/jwboyer/public_git/koji-bisect.git
Ah, cloning was probably the one thing I hadn't tried. Both the gitweb and cgit web access locations seem to work now.
devel@lists.stg.fedoraproject.org