linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: linux-usb@vger.kernel.org, linux-serial@vger.kernel.org,
	debian-kernel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: alloc_tty_driver fails with ENOMEM
Date: Tue, 6 Oct 2015 09:19:03 +0100	[thread overview]
Message-ID: <20151006081903.GA19357@kroah.com> (raw)
In-Reply-To: <20151006080345.GE2472@tarshish>

On Tue, Oct 06, 2015 at 11:03:46AM +0300, Baruch Siach wrote:
> Hi Greg,
> 
> On Tue, Oct 06, 2015 at 08:53:07AM +0100, Greg KH wrote:
> > On Tue, Oct 06, 2015 at 09:44:24AM +0300, Baruch Siach wrote:
> > > Since upgrading to kernel version from 4.1.x to 4.2.1 on Debian testing I 
> > > am getting on my PC the following usbserial module init failure when 
> > > connecting my PC to the i.MX6 SabreSD FTDI USB/serial connector:
> > > 
> > > [39987.092021] usb 1-5.1: new full-speed USB device number 4 using ehci-pci
> > > [39987.190805] usb 1-5.1: New USB device found, idVendor=0403, idProduct=6001
> > > [39987.190810] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > > [39987.190813] usb 1-5.1: Product: FT232R USB UART
> > > [39987.190817] usb 1-5.1: Manufacturer: FTDI
> > > [39987.190820] usb 1-5.1: SerialNumber: A903PDKT
> > > [39989.127918] systemd-udevd: page allocation failure: order:4, mode:0x2040d0
> > 
> > This shows that you have some serious memory issues happening here :(
> 
> Which part is showing this? Is the order too high? Unusual mode?

The page allocation failure of a "normal" allocation means that
something is going wrong outside of the USB subsystem.

thanks,

greg k-h

      reply	other threads:[~2015-10-06  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  6:44 alloc_tty_driver fails with ENOMEM Baruch Siach
2015-10-06  7:53 ` Greg KH
2015-10-06  8:03   ` Baruch Siach
2015-10-06  8:19     ` Greg KH [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=20151006081903.GA19357@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baruch@tkos.co.il \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).