From: Andrew Morton <akpm@osdl.org>
To: Calin Szonyi <caszonyi@rdslink.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory management problem with 2.6.0
Date: Sat, 27 Dec 2003 19:41:44 -0800 [thread overview]
Message-ID: <20031227194144.54d052d1.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0312271912350.511@grinch.ro>
caszonyi@rdslink.ro wrote:
>
> I have a small script:
> #!/bin/sh
> umount /mnt/cdrom
> eject /dev/hdb
> echo "Invalid system disk"
> echo "Insert and press any key when ready"
> read junk
> eject -t /dev/hdb
> sleep 1
> mount /mnt/cdrom
> /usr/sbin/hdparm -E 10 /dev/hdb
>
> It works all the time but today gave me this:
>
> sony@grinch -19:06:39- 0 jobs, ver 2.05b.0 1
> /~ $ cdin
> umount: /mnt/cdrom is not mounted (according to mtab)
> eject: unable to find or open device for: `/dev/hdb'
> Invalid system disk
> Insert and press any key when ready
>
> eject: unable to find or open device for: `/dev/hdb'
> mount: Cannot allocate memory
> /dev/hdb: Cannot allocate memory
>
> The permissions on the device are
>
> sony@grinch -19:07:54- 0 jobs, ver 2.05b.0 1
> /~ $ ls -l /dev/hdb
> brw-rw---- 1 root disk 3, 64 iun 9 2002 /dev/hdb
>
> In the logs I had:
> Dec 27 19:06:16 grinch kernel: eject: page allocation failure. order:4,
> mode:0xd0
Please, try
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0/2.6.0-mm1/broken-out/cdrom-allocation-try-harder.patch
and let me know?
next prev parent reply other threads:[~2003-12-28 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 17:34 Memory management problem with 2.6.0 caszonyi
2003-12-28 3:41 ` Andrew Morton [this message]
2004-01-01 4:05 ` caszonyi
2004-01-01 10:04 ` Andrew Morton
2004-01-03 1:01 ` caszonyi
2004-01-03 1:23 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-12-27 23:07 caszonyi
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=20031227194144.54d052d1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=caszonyi@rdslink.ro \
--cc=linux-kernel@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 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.