public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@kernel.org,
	"kernel list" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
	clayton@craftyguy.net, martijn@brixit.nl,
	sakari.ailus@linux.intel.com,
	"Filip Matijević" <filip.matijevic.pz@gmail.com>,
	stern@rowland.harvard.edu, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org
Subject: Re: v4.18-rc0: ohci-platform on n900 oops-es on reboot
Date: Fri, 15 Jun 2018 13:39:19 +0200	[thread overview]
Message-ID: <20180615113919.GA28328@amd> (raw)
In-Reply-To: <20180614194449.GB17808@amd>

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

Hi!

> When I enable
> 
> CONFIG_USB_OHCI_HCD=y
> CONFIG_USB_OHCI_HCD_OMAP3=y
> CONFIG_USB_OHCI_HCD_PLATFORM=y
> 
> on n900 (I need it on droid4 and want common config), I get oops when
> attempting to reboot the system. I believe problem is there in v4.17,
> too.
> 
> I'll try to build it as a module and debug, but if you have better
> idea, let me know...

It oopses in the ohci_shutdown, see the "oopses here" below.

Any ideas?
								Pavel

+       printk(KERN_CRIT "ohci_shutdown... have pointers %lx, %lx\n", hcd, ohci);
        ohci_writel(ohci, (u32) ~0, &ohci->regs->intrdisable);
+       printk(KERN_CRIT "ohci_shutdown... disable done\n");
+       udelay(1000);
+       printk(KERN_CRIT "ohci_shutdown... disable done\n");
 
        /* Software reset, after which the controller goes into SUSPEND */
        ohci_writel(ohci, OHCI_HCR, &ohci->regs->cmdstatus);
+       printk(KERN_CRIT "ohci_shutdown... writel done\n");
        ohci_readl(ohci, &ohci->regs->cmdstatus);       /* flush the writes */
+       /* It oopses here */
+       printk(KERN_CRIT "ohci_shutdown... readl done\n");
        udelay(10);
 
+       printk(KERN_CRIT "ohci_shutdown... reset done\n");      
        ohci_writel(ohci, ohci->fminterval, &ohci->regs->fminterval);
        ohci->rh_state = OHCI_RH_HALTED;
+
+       printk(KERN_CRIT "ohci_shutdown... all ok?\n"); 

	
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2018-06-15 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14 19:44 v4.18-rc0: ohci-platform on n900 oops-es on reboot Pavel Machek
2018-06-15 11:39 ` Pavel Machek [this message]

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=20180615113919.GA28328@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=abcloriens@gmail.com \
    --cc=clayton@craftyguy.net \
    --cc=filip.matijevic.pz@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=martijn@brixit.nl \
    --cc=pali.rohar@gmail.com \
    --cc=patrikbachan@gmail.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=serge@hallyn.com \
    --cc=sre@kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox