Re: Latest git oopses during boot

[Andrew Morton]

On Wed, 6 Feb 2008 17:32:22 +0100
"Harald Arnesen" <skogtun.linux@xxxxxxxxx> 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@xxxxxxx>
> 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/