Re: crash repeatable, not observable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> trivial scripts that reliably, repeatably, crash Linux-2.6.5 ...

My particular specific example today is as follows.

The udf.ko folk have kindly volunteered to chase this fact in parallel,
in a thread those subscriber-only archives title "x687334 received when
xBA687334 sent".

I imagine I the newbie could help more if I could trace the start of the
crash, rather than only the end.  But ssh of `tail -f /var/log/messages`
tells me nothing.  I see messages only if I run the script via ssh with
the console left dedicated to dumping messages.  Because of the scroll I
only see the last of the messages, not the first of them.  Transcribed
by hand, they were something like:

...
b_state=0x00000010, b_size=2048
block=18446744073709551615, b_blocknr=4294967294
...
block=18446744073709551615, b_blocknr=4294967294
b_state=0x00000010, b_size=2048
...

Pat LaVarre

--- ~/bin/die-udfg

#!/bin/bash -x
sudo -v
rm dd0.bin
dd of=dd0.bin if=/dev/zero bs=1M seek=1023 count=1
sudo mkdir /mnt/loop0/
sudo losetup /dev/loop0 dd0.bin
sudo mkudffs /dev/loop0
sudo mount /dev/loop0 /mnt/loop0
sudo chown `id -g`:`id -u` /mnt/loop0/.
sync
cd /mnt/loop0
dd of=sparse.bin if=/dev/zero bs=1 seek=2987654321 count=1
cd -
sync
sudo umount /dev/loop0
sudo losetup -d /dev/loop0

---



--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux