OnePlus 5 kernel source with linux-stable merged in
Clone or download
nathanchance Merge 4.4.167 into oneplus/QC8998_O_8.1
Changes in 4.4.167: (91 commits)
        media: em28xx: Fix use-after-free when disconnecting
        Revert "wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()"
        rapidio/rionet: do not free skb before reading its length
        s390/qeth: fix length check in SNMP processing
        usbnet: ipheth: fix potential recvmsg bug and recvmsg bug 2
        kvm: mmu: Fix race in emulated page table writes
        xtensa: enable coprocessors that are being flushed
        xtensa: fix coprocessor context offset definitions
        Btrfs: ensure path name is null terminated at btrfs_control_ioctl
        ALSA: wss: Fix invalid snd_free_pages() at error path
        ALSA: ac97: Fix incorrect bit shift at AC97-SPSA control write
        ALSA: control: Fix race between adding and removing a user element
        ALSA: sparc: Fix invalid snd_free_pages() at error path
        ext2: fix potential use after free
        dmaengine: at_hdmac: fix memory leak in at_dma_xlate()
        dmaengine: at_hdmac: fix module unloading
        btrfs: release metadata before running delayed refs
        USB: usb-storage: Add new IDs to ums-realtek
        usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series
        misc: mic/scif: fix copy-paste error in scif_create_remote_lookup
        Kbuild: suppress packed-not-aligned warning for default setting only
        exec: avoid gcc-8 warning for get_task_comm
        disable stringop truncation warnings for now
        kobject: Replace strncpy with memcpy
        unifdef: use memcpy instead of strncpy
        kernfs: Replace strncpy with memcpy
        ip_tunnel: Fix name string concatenate in __ip_tunnel_create()
        drm: gma500: fix logic error
        scsi: bfa: convert to strlcpy/strlcat
        staging: rts5208: fix gcc-8 logic error warning
        kdb: use memmove instead of overlapping memcpy
        iser: set sector for ambiguous mr status errors
        uprobes: Fix handle_swbp() vs. unregister() + register() race once more
        MIPS: ralink: Fix mt7620 nd_sd pinmux
        mips: fix mips_get_syscall_arg o32 check
        drm/ast: Fix incorrect free on ioregs
        scsi: scsi_devinfo: cleanly zero-pad devinfo strings
        ALSA: trident: Suppress gcc string warning
        scsi: csiostor: Avoid content leaks and casts
        kgdboc: Fix restrict error
        kgdboc: Fix warning with module build
        leds: call led_pwm_set() in leds-pwm to enforce default LED_OFF
        leds: turn off the LED and wait for completion on unregistering LED class device
        leds: leds-gpio: Fix return value check in create_gpio_led()
        Input: xpad - quirk all PDP Xbox One gamepads
        Input: matrix_keypad - check for errors from of_get_named_gpio()
        Input: elan_i2c - add ELAN0620 to the ACPI table
        Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15ARR
        Input: elan_i2c - add support for ELAN0621 touchpad
        btrfs: Always try all copies when reading extent buffers
        Btrfs: fix use-after-free when dumping free space
        ARC: change defconfig defaults to ARCv2
        arc: [devboards] Add support of NFSv3 ACL
        mm: cleancache: fix corruption on missed inode invalidation
        mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT)
        usb: gadget: dummy: fix nonsensical comparisons
        iommu/vt-d: Fix NULL pointer dereference in prq_event_thread()
        iommu/ipmmu-vmsa: Fix crash on early domain free
        can: rcar_can: Fix erroneous registration
        batman-adv: Expand merged fragment buffer for full packet
        bnx2x: Assign unique DMAE channel number for FW DMAE transactions.
        qed: Fix PTT leak in qed_drain()
        qed: Fix reading wrong value in loop condition
        net/mlx4_core: Zero out lkey field in SW2HW_MPT fw command
        net/mlx4_core: Fix uninitialized variable compilation warning
        net/mlx4: Fix UBSAN warning of signed integer overflow
        net: faraday: ftmac100: remove netif_running(netdev) check before disabling interrupts
        iommu/vt-d: Use memunmap to free memremap
        net: amd: add missing of_node_put()
        usb: quirk: add no-LPM quirk on SanDisk Ultra Flair device
        usb: appledisplay: Add 27" Apple Cinema Display
        USB: check usb_get_extra_descriptor for proper size
        ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in card.c
        ALSA: hda: Add support for AMD Stoney Ridge
        ALSA: pcm: Fix starvation on down_write_nonblock()
        ALSA: pcm: Call snd_pcm_unlink() conditionally at closing
        ALSA: pcm: Fix interval evaluation with openmin/max
        virtio/s390: avoid race on vcdev->config
        virtio/s390: fix race in ccw_io_helper()
        SUNRPC: Fix leak of krb5p encode pages
        xhci: Prevent U1/U2 link pm states if exit latency is too long
        Staging: lustre: remove two build warnings
        cifs: Fix separator when building path from dentry
        tty: serial: 8250_mtk: always resume the device in probe.
        kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var()
        mac80211_hwsim: Timer should be initialized before device registered
        mac80211: Clear beacon_int in ieee80211_do_stop
        mac80211: ignore tx status for PS stations in ieee80211_tx_status_ext
        mac80211: fix reordering of buffered broadcast packets
        mac80211: ignore NullFunc frames in the duplicate detection
        Linux 4.4.167

Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Latest commit 20ac285 Dec 13, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Documentation Merge 4.4.166 into oneplus/QC8998_O_8.1 Dec 1, 2018
android/configs Merge android-4.4@59ff2e1 (v4.4.78) into msm-4.4 Aug 4, 2017
arch Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
block Merge 4.4.157 into oneplus/QC8998_O_8.1 Sep 19, 2018
certs Merge 4.4.118 into oneplus/QC8998_O_8.1 Mar 13, 2018
crypto Merge 4.4.164 into oneplus/QC8998_O_8.1 Nov 21, 2018
drivers Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
firmware firmware: Update information in linux.git about adding firmware May 7, 2015
fs Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
include Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
init Merge 4.4.136 into oneplus/QC8998_O_8.1 Jun 6, 2018
ipc Merge 4.4.134 into oneplus/QC8998_O_8.1 May 30, 2018
kernel Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
lib Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
mm Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
net Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
samples Merge 4.4.97 into oneplus/QC8998_O_8.1 Mar 12, 2018
scripts Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
security Merge 4.4.164 into oneplus/QC8998_O_8.1 Nov 21, 2018
sound Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
tools Merge 4.4.164 into oneplus/QC8998_O_8.1 Nov 21, 2018
usr usr/Kconfig: make initrd compression algorithm selection not expert Dec 13, 2014
virt Merge 4.4.152 into oneplus/QC8998_O_8.1 Aug 24, 2018
.get_maintainer.ignore Add hch to .get_maintainer.ignore Aug 21, 2015
.gitignore kbuild: Add support to generate LLVM assembly files Nov 27, 2018
.mailmap mailmap: update Javier Martinez Canillas' email Oct 23, 2015
AndroidKernel.mk AndroidKernel: add support to configure DLKM install path Apr 6, 2017
COPYING [PATCH] update FSF address in COPYING Sep 10, 2005
CREDITS MAINTAINERS/CREDITS: mark MaxRAID as Orphan, move Anil Ravindranath t… Sep 10, 2015
Kbuild kbuild: Consolidate header generation from ASM offset information Nov 27, 2018
Kconfig kbuild: migrate all arch to the kconfig mainmenu upgrade Sep 20, 2010
MAINTAINERS Merge 4.4.166 into oneplus/QC8998_O_8.1 Dec 1, 2018
Makefile Merge 4.4.167 into oneplus/QC8998_O_8.1 Dec 13, 2018
README README: Add ARC architecture Sep 18, 2015
REPORTING-BUGS Docs: Move ref to Frohwalt Egerer to end of REPORTING-BUGS Apr 18, 2013
backported-features backporting: a brief introduce of backported feautures on 4.4 Sep 13, 2016
build.config.goldfish.arm build: fix build config kernel_dir Dec 8, 2016
build.config.goldfish.arm64 build: fix build config kernel_dir Dec 8, 2016
build.config.goldfish.mips build: fix build config kernel_dir Dec 8, 2016
build.config.goldfish.mips64 build: fix build config kernel_dir Dec 8, 2016
build.config.goldfish.x86 build: fix build config kernel_dir Dec 8, 2016
build.config.goldfish.x86_64 build: fix build config kernel_dir Dec 8, 2016

README

        Linux kernel release 4.x <http://kernel.org/>

These are the release notes for Linux version 4.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong. 

WHAT IS LINUX?

  Linux is a clone of the operating system Unix, written from scratch by
  Linus Torvalds with assistance from a loosely-knit team of hackers across
  the Net. It aims towards POSIX and Single UNIX Specification compliance.

  It has all the features you would expect in a modern fully-fledged Unix,
  including true multitasking, virtual memory, shared libraries, demand
  loading, shared copy-on-write executables, proper memory management,
  and multistack networking including IPv4 and IPv6.

  It is distributed under the GNU General Public License - see the
  accompanying COPYING file for more details. 

ON WHAT HARDWARE DOES IT RUN?

  Although originally developed first for 32-bit x86-based PCs (386 or higher),
  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
  Xtensa, Tilera TILE, AVR32, ARC and Renesas M32R architectures.

  Linux is easily portable to most general-purpose 32- or 64-bit architectures
  as long as they have a paged memory management unit (PMMU) and a port of the
  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
  also been ported to a number of architectures without a PMMU, although
  functionality is then obviously somewhat limited.
  Linux has also been ported to itself. You can now run the kernel as a
  userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

 - There is a lot of documentation available both in electronic form on
   the Internet and in books, both Linux-specific and pertaining to
   general UNIX questions.  I'd recommend looking into the documentation
   subdirectories on any Linux FTP site for the LDP (Linux Documentation
   Project) books.  This README is not meant to be documentation on the
   system: there are much better sources available.

 - There are various README files in the Documentation/ subdirectory:
   these typically contain kernel-specific installation notes for some 
   drivers for example. See Documentation/00-INDEX for a list of what
   is contained in each file.  Please read the Changes file, as it
   contains information about the problems, which may result by upgrading
   your kernel.

 - The Documentation/DocBook/ subdirectory contains several guides for
   kernel developers and users.  These guides can be rendered in a
   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.
   After installation, "make psdocs", "make pdfdocs", "make htmldocs",
   or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

 - If you install the full sources, put the kernel tarball in a
   directory where you have permissions (eg. your home directory) and
   unpack it:

     xz -cd linux-4.X.tar.xz | tar xvf -

   Replace "X" with the version number of the latest kernel.

   Do NOT use the /usr/src/linux area! This area has a (usually
   incomplete) set of kernel headers that are used by the library header
   files.  They should match the library, and not get messed up by
   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 4.x releases by patching.  Patches are
   distributed in the xz format.  To install by patching, get all the
   newer patch files, enter the top level directory of the kernel source
   (linux-4.X) and execute:

     xz -cd ../patch-4.x.xz | patch -p1

   Replace "x" for all versions bigger than the version "X" of your current
   source tree, _in_order_, and you should be ok.  You may want to remove
   the backup files (some-file-name~ or some-file-name.orig), and make sure
   that there are no failed patches (some-file-name# or some-file-name.rej).
   If there are, either you or I have made a mistake.

   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 4.x kernel.  For example, if your base kernel is 4.0
   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
   patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
   Documentation/applying-patches.txt

   Alternatively, the script patch-kernel can be used to automate this
   process.  It determines the current kernel version and applies any
   patches found.

     linux/scripts/patch-kernel linux

   The first argument in the command above is the location of the
   kernel source.  Patches are applied from the current directory, but
   an alternative directory can be specified as the second argument.

 - Make sure you have no stale .o files and dependencies lying around:

     cd linux
     make mrproper

   You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

   Compiling and running the 4.x kernels requires up-to-date
   versions of various software packages.  Consult
   Documentation/Changes for the minimum version numbers required
   and how to get updates for these packages.  Beware that using
   excessively old versions of these packages can cause indirect
   errors that are very difficult to track down, so don't assume that
   you can just update packages when obvious problems arise during
   build or operation.

BUILD directory for the kernel:

   When compiling the kernel, all output files will per default be
   stored together with the kernel source code.
   Using the option "make O=output/dir" allow you to specify an alternate
   place for the output files (including .config).
   Example:

     kernel source code: /usr/src/linux-4.X
     build directory:    /home/name/build/kernel

   To configure and build the kernel, use:

     cd /usr/src/linux-4.X
     make O=/home/name/build/kernel menuconfig
     make O=/home/name/build/kernel
     sudo make O=/home/name/build/kernel modules_install install

   Please note: If the 'O=output/dir' option is used, then it must be
   used for all invocations of make.

CONFIGURING the kernel:

   Do not skip this step even if you are only upgrading one minor
   version.  New configuration options are added in each release, and
   odd problems will turn up if the configuration files are not set up
   as expected.  If you want to carry your existing configuration to a
   new version with minimal work, use "make oldconfig", which will
   only ask you for the answers to new questions.

 - Alternative configuration commands are:

     "make config"      Plain text interface.

     "make menuconfig"  Text based color menus, radiolists & dialogs.

     "make nconfig"     Enhanced text based color menus.

     "make xconfig"     X windows (Qt) based configuration tool.

     "make gconfig"     X windows (GTK+) based configuration tool.

     "make oldconfig"   Default all questions based on the contents of
                        your existing ./.config file and asking about
                        new config symbols.

     "make silentoldconfig"
                        Like above, but avoids cluttering the screen
                        with questions already answered.
                        Additionally updates the dependencies.

     "make olddefconfig"
                        Like above, but sets new symbols to their default
                        values without prompting.

     "make defconfig"   Create a ./.config file by using the default
                        symbol values from either arch/$ARCH/defconfig
                        or arch/$ARCH/configs/${PLATFORM}_defconfig,
                        depending on the architecture.

     "make ${PLATFORM}_defconfig"
                        Create a ./.config file by using the default
                        symbol values from
                        arch/$ARCH/configs/${PLATFORM}_defconfig.
                        Use "make help" to get a list of all available
                        platforms of your architecture.

     "make allyesconfig"
                        Create a ./.config file by setting symbol
                        values to 'y' as much as possible.

     "make allmodconfig"
                        Create a ./.config file by setting symbol
                        values to 'm' as much as possible.

     "make allnoconfig" Create a ./.config file by setting symbol
                        values to 'n' as much as possible.

     "make randconfig"  Create a ./.config file by setting symbol
                        values to random values.

     "make localmodconfig" Create a config based on current config and
                           loaded modules (lsmod). Disables any module
                           option that is not needed for the loaded modules.

                           To create a localmodconfig for another machine,
                           store the lsmod of that machine into a file
                           and pass it in as a LSMOD parameter.

                   target$ lsmod > /tmp/mylsmod
                   target$ scp /tmp/mylsmod host:/tmp

                   host$ make LSMOD=/tmp/mylsmod localmodconfig

                           The above also works when cross compiling.

     "make localyesconfig" Similar to localmodconfig, except it will convert
                           all module options to built in (=y) options.

   You can find more information on using the Linux kernel config tools
   in Documentation/kbuild/kconfig.txt.

 - NOTES on "make config":

    - Having unnecessary drivers will make the kernel bigger, and can
      under some circumstances lead to problems: probing for a
      nonexistent controller card may confuse your other controllers

    - Compiling the kernel with "Processor type" set higher than 386
      will result in a kernel that does NOT work on a 386.  The
      kernel will detect this on bootup, and give up.

    - A kernel with math-emulation compiled in will still use the
      coprocessor if one is present: the math emulation will just
      never get used in that case.  The kernel will be slightly larger,
      but will work on different machines regardless of whether they
      have a math coprocessor or not.

    - The "kernel hacking" configuration details usually result in a
      bigger or slower kernel (or both), and can even make the kernel
      less stable by configuring some routines to actively try to
      break bad code to find kernel problems (kmalloc()).  Thus you
      should probably answer 'n' to the questions for "development",
      "experimental", or "debugging" features.

COMPILING the kernel:

 - Make sure you have at least gcc 3.2 available.
   For more information, refer to Documentation/Changes.

   Please note that you can still run a.out user programs with this kernel.

 - Do a "make" to create a compressed kernel image. It is also
   possible to do "make install" if you have lilo installed to suit the
   kernel makefiles, but you may want to check your particular lilo setup first.

   To do the actual install, you have to be root, but none of the normal
   build should require that. Don't take the name of root in vain.

 - If you configured any of the parts of the kernel as `modules', you
   will also have to do "make modules_install".

 - Verbose kernel compile/build output:

   Normally, the kernel build system runs in a fairly quiet mode (but not
   totally silent).  However, sometimes you or other kernel developers need
   to see compile, link, or other commands exactly as they are executed.
   For this, use "verbose" build mode.  This is done by inserting
   "V=1" in the "make" command.  E.g.:

     make V=1 all

   To have the build system also tell the reason for the rebuild of each
   target, use "V=2".  The default is "V=0".

 - Keep a backup kernel handy in case something goes wrong.  This is 
   especially true for the development releases, since each new release
   contains new code which has not been debugged.  Make sure you keep a
   backup of the modules corresponding to that kernel, as well.  If you
   are installing a new kernel with the same version number as your
   working kernel, make a backup of your modules directory before you
   do a "make modules_install".

   Alternatively, before compiling, use the kernel config option
   "LOCALVERSION" to append a unique suffix to the regular kernel version.
   LOCALVERSION can be set in the "General Setup" menu.

 - In order to boot your new kernel, you'll need to copy the kernel
   image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
   to the place where your regular bootable kernel is found. 

 - Booting a kernel directly from a floppy without the assistance of a
   bootloader such as LILO, is no longer supported.

   If you boot Linux from the hard drive, chances are you use LILO, which
   uses the kernel image as specified in the file /etc/lilo.conf.  The
   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
   /boot/bzImage.  To use the new kernel, save a copy of the old image
   and copy the new image over the old one.  Then, you MUST RERUN LILO
   to update the loading map!! If you don't, you won't be able to boot
   the new kernel image.

   Reinstalling LILO is usually a matter of running /sbin/lilo. 
   You may wish to edit /etc/lilo.conf to specify an entry for your
   old kernel image (say, /vmlinux.old) in case the new one does not
   work.  See the LILO docs for more information. 

   After reinstalling LILO, you should be all set.  Shutdown the system,
   reboot, and enjoy!

   If you ever need to change the default root device, video mode,
   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or
   alternatively the LILO boot options when appropriate).  No need to
   recompile the kernel to change these parameters. 

 - Reboot with the new kernel and enjoy. 

IF SOMETHING GOES WRONG:

 - If you have problems that seem to be due to kernel bugs, please check
   the file MAINTAINERS to see if there is a particular person associated
   with the part of the kernel that you are having trouble with. If there
   isn't anyone listed there, then the second best thing is to mail
   them to me (torvalds@linux-foundation.org), and possibly to any other
   relevant mailing-list or to the newsgroup.

 - In all bug-reports, *please* tell what kernel you are talking about,
   how to duplicate the problem, and what your setup is (use your common
   sense).  If the problem is new, tell me so, and if the problem is
   old, please try to tell me when you first noticed it.

 - If the bug results in a message like

     unable to handle kernel paging request at address C0000010
     Oops: 0002
     EIP:   0010:XXXXXXXX
     eax: xxxxxxxx   ebx: xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx
     esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx
     ds: xxxx  es: xxxx  fs: xxxx  gs: xxxx
     Pid: xx, process nr: xx
     xx xx xx xx xx xx xx xx xx xx

   or similar kernel debugging information on your screen or in your
   system log, please duplicate it *exactly*.  The dump may look
   incomprehensible to you, but it does contain information that may
   help debugging the problem.  The text above the dump is also
   important: it tells something about why the kernel dumped code (in
   the above example, it's due to a bad kernel pointer). More information
   on making sense of the dump is in Documentation/oops-tracing.txt

 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
   as is, otherwise you will have to use the "ksymoops" program to make
   sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
   This utility can be downloaded from
   ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
   Alternatively, you can do the dump lookup by hand:

 - In debugging dumps like the above, it helps enormously if you can
   look up what the EIP value means.  The hex value as such doesn't help
   me or anybody else very much: it will depend on your particular
   kernel setup.  What you should do is take the hex value from the EIP
   line (ignore the "0010:"), and look it up in the kernel namelist to
   see which kernel function contains the offending address.

   To find out the kernel function name, you'll need to find the system
   binary associated with the kernel that exhibited the symptom.  This is
   the file 'linux/vmlinux'.  To extract the namelist and match it against
   the EIP from the kernel crash, do:

     nm vmlinux | sort | less

   This will give you a list of kernel addresses sorted in ascending
   order, from which it is simple to find the function that contains the
   offending address.  Note that the address given by the kernel
   debugging messages will not necessarily match exactly with the
   function addresses (in fact, that is very unlikely), so you can't
   just 'grep' the list: the list will, however, give you the starting
   point of each kernel function, so by looking for the function that
   has a starting address lower than the one you are searching for but
   is followed by a function with a higher address you will find the one
   you want.  In fact, it may be a good idea to include a bit of
   "context" in your problem report, giving a few lines around the
   interesting one. 

   If you for some reason cannot do the above (you have a pre-compiled
   kernel image or similar), telling me as much about your setup as
   possible will help.  Please read the REPORTING-BUGS document for details.

 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
   cannot change values or set break points.) To do this, first compile the
   kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
   clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

   After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
   You can now use all the usual gdb commands. The command to look up the
   point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
   with the EIP value.)

   gdb'ing a non-running kernel currently fails because gdb (wrongly)
   disregards the starting offset for which the kernel is compiled.