On Tue, Jul 31, 2012 at 03:06:11PM +0200, Lars-Peter Clausen wrote:
> On 07/31/2012 02:55 PM, Fengguang Wu wrote:
> >>> The panic happens while trying to dereference the NULL indio_dev->buffer:
> >>>
> >>> 266 int iio_buffer_register(struct iio_dev *indio_dev,
> >>> 267
On 07/31/2012 02:55 PM, Fengguang Wu wrote:
>>> The panic happens while trying to dereference the NULL indio_dev->buffer:
>>>
>>> 266 int iio_buffer_register(struct iio_dev *indio_dev,
>>> 267 const struct iio_chan_spec *channels,
>>> 268
> > The panic happens while trying to dereference the NULL indio_dev->buffer:
> >
> > 266 int iio_buffer_register(struct iio_dev *indio_dev,
> > 267 const struct iio_chan_spec *channels,
> > 268 int num_channels)
> > 2
On 07/31/2012 12:31 PM, Fengguang Wu wrote:
>> [7.623739] BUG: unable to handle kernel NULL pointer dereference at
>> 00b0
>
> I managed to root cause it:
>
> [2.108085] BUG: unable to handle kernel NULL pointer dereference
> at 0060
> [2.112015] EIP:
Hi Jonathan,
I got this boot error when testing kernel in kvm, built with the attached
config:
[7.618723] kobject: 'tpci200' (8800072f8798): kobject_add_internal:
parent: 'drivers', set: 'drivers'
[7.620602] kobject: 'tpci200' (8800072f8798): kobject_uevent_env
[7.621875] ko
5 matches
Mail list logo