linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 210185] kernel BUG at fs/ext4/page-io.c:126!
Date: Wed, 18 Nov 2020 10:30:31 +0000	[thread overview]
Message-ID: <bug-210185-13602-LM8XHz3BnI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210185-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210185

--- Comment #4 from emchroma@gmail.com ---
(In reply to Theodore Tso from comment #3)

Hi Theodore,

> How easily can you reproduce the problem?  

on each invocation.

> Can you give us instructions for a reliable repro (e.g., download AutoCtk,
> run it with these options and this input file, and it will crash in N
> minutes)?

You'll need Anaconda, Ngspice and AutoCkt. I'm on debian and I've apt-get
ngspice. I'll try a step by step procedure for Anaconda and AutoCkt

We're using https://repo.anaconda.com/archive/Anaconda3-2020.02-Linux-x86_64.sh
Download and install Anaconda

# activate base environment
$ . .bashrc

# upgrade pip
$ pip install --upgrade pip

# download AutoCkt
$ git clone https://github.com/ksettaluri6/AutoCkt.git

# create autockt_updated environment, use the attached autockt_updated.yml,
# not the environment provided by AutoCkt
$ conda env create -f autockt_updated.yml

# activate environment autockt_upgraded
$ conda activate autockt_updated

# copy the attached parameter file to AutoCkt/autockt
$ cp val_autobag_ray_hyperparameter_tuning.py AutoCkt/autockt

# run AutoCkt
$ cd AutoCkt
$ python autockt/gen_specs.py --num_specs 600
$ ipython
$ run autockt/val_autobag_ray_hyperparameter_tuning.py # this is in the IPython
shell

AutoCkt creates a lot of files in /tmp/ckt_da and /tmp/ray. tmp is on the root
partition and
our root is rather small (100G), therefore we start a python script to delete
files/directories
older than 10 minutes in /tmp/ckt_da from a second shell

# cleanup /tmp/ckt_da
$ python auto_delete_old_tmp_ckt_da_files.py

AutoCkt is very verbose and you'll probably see some warnings, but it should
run. On our machines
it usually takes 10-15 minutes, sometimes up to 30 minutes until the bug
appears.

Not sure whether it matters, but we're using software raid1 for the root
partition.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-11-18 10:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:16 [Bug 210185] New: kernel BUG at fs/ext4/page-io.c:126! bugzilla-daemon
2020-11-13 20:10 ` [Bug 210185] " bugzilla-daemon
2020-11-13 22:03 ` bugzilla-daemon
2020-11-17 19:07 ` bugzilla-daemon
2020-11-18 10:30 ` bugzilla-daemon [this message]
2020-11-18 10:31 ` bugzilla-daemon
2020-11-18 10:33 ` bugzilla-daemon
2020-11-18 10:33 ` bugzilla-daemon
2020-11-18 13:09 ` bugzilla-daemon
2020-11-18 13:09 ` bugzilla-daemon
2020-11-20  7:49 ` bugzilla-daemon
2021-02-02 11:00 ` bugzilla-daemon
2021-02-02 16:23 ` bugzilla-daemon
2021-02-02 17:06 ` bugzilla-daemon
2021-02-03  8:19 ` bugzilla-daemon
2021-02-18 12:57 ` bugzilla-daemon

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=bug-210185-13602-LM8XHz3BnI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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).