Re: kernel version in git repo

2012-01-25 Thread YONETANI Tomokazu
On Tue, Jan 24, 2012 at 05:20:44PM -0500, Pierre Abbat wrote:
 I have a bug report (starting X causes reboot) in which I gave a date but not 
 an exact version, and I've been asked to check out the latest code and see if 
 it fixes an unrelated bug (make -j2 buildkernel). What git command can I use 
 before checking out so that you can reproduce the first bug?

The output from `uname -a' contains a prefix of the commit hash
of the source code from which the kernel was built

  $ uname -a
  DragonFly X335 2.13-DEVELOPMENT DragonFly v2.13.0.929.g2a1f9-DEVELOPMENT #0: 
Mon Jan 16 18:02:19 JST 2012 root@X335:/usr/obj/build/usr/src/sys/SMP  i386

The string `2a1f9' after `g' before `-DEVELOPMENT' is the one you need.
If you need the `uname -a' output from the older kernel, try this:

  $ strings /boot/kernel.old/kernel |tail -n4
  DragonFly v2.13.0.796.g4090d-DEVELOPMENT #0: Wed Jan  4 22:59:22 JST 2012
  root@X335:/usr/obj/build/usr/src/sys/SMP
  DragonFly
  2.13-DEVELOPMENT

You can use this string to checkout the previous version:
  $ cd /usr/src
  $ git checkout 2a1f9
  Note: checking out '2a1f9'.
  (and long message here mentioning you're not on a particular branch
   and an instruction on how to create a new branch)

You can go back to the original branch, say, `master', by
  $ git checkout master

Finally, Git remembers what you did to your repository for you for a while,
so you don't even have to remember what version you have now before updating
to the latest:
  $ git reflog
  e27434d HEAD@{0}: checkout: moving from 
2a1f96b998a7a95f220d7a527c2f0a7b9e42be3a to master
  2a1f96b HEAD@{1}: checkout: moving from master to 2a1f9
  e27434d HEAD@{2}: pull: Fast-forward
  2a1f96b HEAD@{3}: pull: Fast-forward
  4090d6f HEAD@{4}: pull: Fast-forward
  e820d19 HEAD@{5}: pull: Fast-forward


Re: kernel version in git repo

2012-01-25 Thread Pierre Abbat
On Wednesday, January 25, 2012 11:47:09 YONETANI Tomokazu wrote:
 On Tue, Jan 24, 2012 at 05:20:44PM -0500, Pierre Abbat wrote:
  I have a bug report (starting X causes reboot) in which I gave a date but
  not an exact version, and I've been asked to check out the latest code
  and see if it fixes an unrelated bug (make -j2 buildkernel). What git
  command can I use before checking out so that you can reproduce the
  first bug?
 
 The output from `uname -a' contains a prefix of the commit hash
 of the source code from which the kernel was built

Matthias answered by private email and I added the output of git show to the 
bug report. uname -a wouldn't work, since I copied the previous kernel after 
finding out that the one I built caused the X server to reboot.

Pierre
-- 
sei do'anai mi'a djuno puze'e noroi nalselganse srera


Re: kernel version in git repo

2012-01-25 Thread Matthias Rampke
On Wednesday, 25. January 2012 at 18:34, Pierre Abbat wrote:
 Matthias answered by private email

Ooops, forgot to add users@ again. For the record, here's the core bit:

 to mark your currently checked out version use git tag bug_foo; if you just 
 want to know the commit ID use e.g. git show or git log (top entry) – in 
 the end both ways are equivalent only that with git tag the note is within 
 the git repo.

/Matthias



X reboot

2012-01-25 Thread Romick
Hello,


If you have intel video then you can try edit /etc/X11/xorg.conf :

   Section Device
 Identifier devname
 Driver intel
 ...
  Option DRI False
   EndSection


---
 with best regards, Yellow Rabbit   
 GPG: 0x6E2F8DBB at keyserver.linux.it
 Linux 3.1.0-gentoo x86_64 GNU/Linux


Re: kernel version in git repo

2012-01-25 Thread YONETANI Tomokazu
On Wed, Jan 25, 2012 at 12:34:43PM -0500, Pierre Abbat wrote:
  The output from `uname -a' contains a prefix of the commit hash
  of the source code from which the kernel was built
 
 Matthias answered by private email and I added the output of git show to 
 the 
 bug report. uname -a wouldn't work, since I copied the previous kernel 
 after 
 finding out that the one I built caused the X server to reboot.

Well, /var/log/messages* contains the uname -a output from the previos
boots.  Look for the word `Copyright' and a few lines after that.
The messages file may (or may not) also contain the panic message,
so you can use it as the guide if you forgot when the panic happened.

Cheers.


Re: X reboot

2012-01-25 Thread Pierre Abbat
On Wednesday, January 25, 2012 17:09:30 Romick wrote:
 Hello,
 
 
 If you have intel video then you can try edit /etc/X11/xorg.conf :
 
Section Device
  Identifier devname
  Driver intel
  ...
 Option DRI False
EndSection

That worked. What does it mean?

Pierre
-- 
sei do'anai mi'a djuno puze'e noroi nalselganse srera


Re: X reboot

2012-01-25 Thread Romick
From: Pierre Abbat p...@phma.optus.nu
Subject: Re: X reboot
Date: Wed, 25 Jan 2012 23:24:38 -0500

 On Wednesday, January 25, 2012 17:09:30 Romick wrote:
 Hello,
 
 
 If you have intel video then you can try edit /etc/X11/xorg.conf :
 
Section Device
  Identifier devname
  Driver intel
  ...
    Option DRI False
EndSection
 
 That worked. What does it mean?
 

I don't know. Something broken intel or drm.


---
 with best regards, Yellow Rabbit   
 GPG: 0x6E2F8DBB at keyserver.linux.it
 Linux 3.1.0-gentoo x86_64 GNU/Linux


Re: kernel version in git repo

2012-01-25 Thread Pierre Abbat
On Wednesday, January 25, 2012 14:22:50 Matthias Rampke wrote:
 Ooops, forgot to add users@ again. For the record, here's the core bit:

You don't need to add users@. Just hit the reply-to-list button. I'm on the 
list, so I don't need a reply in my inbox, just the one in the list folder.

Pierre
-- 
lo ponse be lo mruli po'o cu ga'ezga roda lo ka dinko