All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Peter Delevoryas <pdel@fb.com>
Cc: Billy Tsai <billy_tsai@aspeedtech.com>,
	OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: aspeed-adc driver kpanic
Date: Mon, 4 Oct 2021 17:25:17 -0500	[thread overview]
Message-ID: <YVt/TU4zANvubugD@heinlein> (raw)
In-Reply-To: <24AC6FDD-323D-4F37-818F-C965164544BF@fb.com>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On Mon, Oct 04, 2021 at 07:26:04PM +0000, Peter Delevoryas wrote:

> Oh yeah, this is probably not the driver’s fault, this is the fault of my QEMU
> patches. I only allowed 32-bit aligned reads. I bet if you apply this additional
> diff, it won’t crash

FWIW, applying this did get me past the kernel panic.  I don't really care about
any of the data right now.  I was trying to test something out in userspace.

> diff --git a/hw/adc/aspeed_adc.c b/hw/adc/aspeed_adc.c
> index fcd93d6853..58e3f18c6c 100644
> --- a/hw/adc/aspeed_adc.c
> +++ b/hw/adc/aspeed_adc.c
> @@ -234,9 +234,9 @@ static const MemoryRegionOps aspeed_adc_engine_ops = {
>      .write = aspeed_adc_engine_write,
>      .endianness = DEVICE_LITTLE_ENDIAN,
>      .valid = {
> -        .min_access_size = 4,
> +        .min_access_size = 1,
>          .max_access_size = 4,
> -        .unaligned = false,
> +        .unaligned = true,
>      },
>  };

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-10-04 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 18:34 aspeed-adc driver kpanic Patrick Williams
2021-10-04 18:54 ` Patrick Williams
2021-10-04 19:26   ` Peter Delevoryas
2021-10-04 22:25     ` Patrick Williams [this message]
2021-10-05  0:00 ` Joel Stanley

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=YVt/TU4zANvubugD@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=billy_tsai@aspeedtech.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=pdel@fb.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.