LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Harald Arnesen" <skogtun.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, tomof@acm.org
Subject: Re: Latest git oopses during boot
Date: Wed, 6 Feb 2008 14:47:32 -0800	[thread overview]
Message-ID: <20080206144732.5a1a2c3b.akpm@linux-foundation.org> (raw)
In-Reply-To: <8120cfd40802060832w2dd3631foad324b3633427230@mail.gmail.com>

On Wed, 6 Feb 2008 17:32:22 +0100
"Harald Arnesen" <skogtun.linux@gmail.com> wrote:

> Photo of screen attached (no serial terminal, and alas, no decent
> tripod either).

Thanks, but you've disabled so many debug options that the trace isn't
very useful.

> git-bisect gives me this:
> 
> 6b7b651055221127304a4e373ee9b762398d54d7 is first bad commit
> commit 6b7b651055221127304a4e373ee9b762398d54d7
> Author: FUJITA Tomonori <tomof@acm.org>
> Date:   Mon Feb 4 22:27:55 2008 -0800
> 
>     iommu sg merging: add device_dma_parameters structure
> 
>     IOMMUs merges scatter/gather segments without considering a low level
>     driver's restrictions. The problem is that IOMMUs can't access to the
>     limitations because they are in request_queue.
> 
>     This patchset introduces a new structure, device_dma_parameters,
>     including dma information. A pointer to device_dma_parameters is added
>     to struct device. The bus specific structures (like pci_dev) includes
>     device_dma_parameters. Low level drivers can use dma_set_max_seg_size
>     to tell IOMMUs about the restrictions.
> 
>     We can move more dma stuff in struct device (like dma_mask) to struct
>     device_dma_parameters later (needs some cleanups before that).
> 
>     This includes patches for all the IOMMUs that could merge sg (x86_64,
>     ppc, IA64, alpha, sparc64, and parisc) though only the ppc patch was
>     tested. The patches for other IOMMUs are only compile tested.
> 
> $ gcc -v
> Using built-in specs.
> Target: i686-pc-linux-gnu
> Configured with: ../configure --prefix=/opt/gcc
> Thread model: posix
> gcc version 4.2.3
> 
> Config:
>
> ...
> 
> # CONFIG_DEBUG_BUGVERBOSE is not set
>

This one really should be enabled at all times, please.

Can you please set it and retry?

  reply	other threads:[~2008-02-06 22:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 16:32 Harald Arnesen
2008-02-06 22:47 ` Andrew Morton [this message]
     [not found]   ` <8120cfd40802070144l79830c2cs6329c302697ecc8b@mail.gmail.com>
2008-02-07 10:02     ` Andrew Morton
2008-02-07 11:14       ` Harald Arnesen
2008-02-07 11:16         ` Christoph Hellwig
2008-02-07 14:32         ` FUJITA Tomonori
     [not found]           ` <8120cfd40802070933r42a98537v78feb7ee8e748a94@mail.gmail.com>
2008-02-07 18:18             ` Linus Torvalds
     [not found]               ` <8120cfd40802071248x20ed938dh52cd9e314219613b@mail.gmail.com>
2008-02-07 21:14                 ` Linus Torvalds
2008-02-07 21:39                   ` Harald Arnesen
2008-02-07 22:12                     ` Linus Torvalds
2008-02-07 22:24                       ` Harald Arnesen
2008-02-08  0:10                         ` FUJITA Tomonori
2008-02-06 23:06 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080206144732.5a1a2c3b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skogtun.linux@gmail.com \
    --cc=tomof@acm.org \
    --subject='Re: Latest git oopses during boot' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).