Re: dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)

2017-11-30 Thread Michal Hocko
On Thu 30-11-17 22:01:03, Wu Fengguang wrote: > On Thu, Nov 30, 2017 at 02:50:16PM +0100, Michal Hocko wrote: > > On Thu 30-11-17 21:38:40, Wu Fengguang wrote: > > > Hello, > > > > > > It looks like a regression in 4.15.0-rc1 -- the test case simply run a > > > set of parallel dd's and there seems

Re: dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 10:08:04PM +0800, Fengguang Wu wrote: [ 78.848629] dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null) [ 78.857841] dd cpuset=/ mems_allowed=0-1 [ 78.862502] CPU: 0 PID: 6131 Comm: dd Tainted: G O 4.15.0-rc1 #1 [ 78.870

Re: dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)

2017-11-30 Thread Fengguang Wu
[ 78.848629] dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null) [ 78.857841] dd cpuset=/ mems_allowed=0-1 [ 78.862502] CPU: 0 PID: 6131 Comm: dd Tainted: G O 4.15.0-rc1 #1 [ 78.870437] Call Trace: [ 78.873610] [ 78.876342] dump_stack+0x

Re: dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 02:50:16PM +0100, Michal Hocko wrote: On Thu 30-11-17 21:38:40, Wu Fengguang wrote: Hello, It looks like a regression in 4.15.0-rc1 -- the test case simply run a set of parallel dd's and there seems no reason to run into memory problem. It occurs in 1 out of 4 tests.

Re: dd: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)

2017-11-30 Thread Michal Hocko
On Thu 30-11-17 21:38:40, Wu Fengguang wrote: > Hello, > > It looks like a regression in 4.15.0-rc1 -- the test case simply run a > set of parallel dd's and there seems no reason to run into memory problem. > > It occurs in 1 out of 4 tests. This is an atomic allocations. So the failure really d

Re: dd/mke2fs on loopback hangs

2007-11-13 Thread Petar Bogdanovic
On Tue, Nov 06, 2007 at 10:04:51PM +0100, Milan Broz wrote: > Petar Bogdanovic wrote: > > I experience some strange problems with my loopback-on-ext3-setup. > > After creating a plain `zeroed' dummy-file and doing a /dev/loop/0 on > > it, every dd or mke2fs hangs while doing certain write()s. Here

Re: dd/mke2fs on loopback hangs

2007-11-07 Thread Petar Bogdanovic
On Tue, Nov 06, 2007 at 10:04:51PM +0100, Milan Broz wrote: > Petar Bogdanovic wrote: > > I experience some strange problems with my loopback-on-ext3-setup. > > After creating a plain `zeroed' dummy-file and doing a /dev/loop/0 on > > it, every dd or mke2fs hangs while doing certain write()s. Here

Re: dd/mke2fs on loopback hangs

2007-11-06 Thread Milan Broz
Petar Bogdanovic wrote: > I experience some strange problems with my loopback-on-ext3-setup. > After creating a plain `zeroed' dummy-file and doing a /dev/loop/0 on > it, every dd or mke2fs hangs while doing certain write()s. Here are the > steps just in order to show, how simple the setup is: ...

Re: dd

2007-02-07 Thread Mike Frysinger
On 2/8/07, Oleg Verych <[EMAIL PROTECTED]> wrote: > Check to see if `${CROSS_COMPILE}mkimage` exists and if not, fall back to > the standard `mkimage` Why this can't be done by PATH=$CROSS_COMPILE:$PATH in your environment? because it wouldnt matter ? the tool is called "$CROSS_COMPILE-mk

Re: dd

2007-02-07 Thread Andrew Morton
On Thu, 8 Feb 2007 06:24:40 +0100 Oleg Verych <[EMAIL PROTECTED]> wrote: > If that matter, `type -path' is bashizm (BloAted SHell), and "blackbox" > with "dash" (very good `sh' equivalents) will fail. Does the kernel presently build with that shell? - To unsubscribe from this list: send the line

Re: `dd` problem from cdrom

2005-03-16 Thread Rafael EspĂ­ndola
On Wed, 16 Mar 2005 15:31:14 +0100, Colin Leroy <[EMAIL PROTECTED]> wrote: > Hi, > > Using 2.6.10 and 2.6.11, trying to use dd from the ide cdrom in my > Ibook G4 fails like this: > /dev/hdc: > HDIO_GET_MULTCOUNT failed: Invalid argument > IO_support = 0 (default 16-bit) > unmaskirq= 1