From: Thomas Bader <thomasb@trash.net>
To: linux-kernel@vger.kernel.org
Subject: [BUG] data_access_exception during chroot()
Date: Sun, 9 Dec 2001 14:16:09 +0100 [thread overview]
Message-ID: <20011209141609.A13900@trash.net> (raw)
Hi all
I'm running 2.4.17-pre6 on my SUN Ultra1. Further, I've got devfs, RAID and
LVM support in my kernel config.
Now I'm trying to chroot to a specific directory:
duke:~# mount
/dev/sda8 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
/dev/md/0 on /mnt type ext2 (rw)
duke:~# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md1 : active raid1 scsi/host0/bus0/target1/lun0/part2[1] scsi/host0/bus0/target]
627648 blocks [2/2] [UU]
md0 : active raid1 scsi/host0/bus0/target1/lun0/part1[1] scsi/host0/bus0/target]
3145664 blocks [2/2] [UU]
unused devices: <none>
duke:~# chroot --version
chroot (GNU sh-utils) 2.0.11
duke:~# chroot /mnt /bin/bash
data_access_exception: SFSR[0000000000801009] SFAR[fffff805b2bf6afc], going.
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
\__U_/
chroot(224): Dax
TSTATE: 0000000011009603 TPC: 0000000000503464 TNPC: 0000000000503468 Y: 070000d
g0: 0000000000000000 g1: fffee0058b199b00 g2: 0000000000000001 g3: fffee0058b19c
g4: fffff80000000000 g5: fffee0058b199b20 g6: fffff8002741c000 g7: 0000000000004
o0: 0000000000280108 o1: 0000000000000000 o2: fffff800276b60c0 o3: fffff80000ba0
o4: 0000000000000008 o5: 0000000000000001 sp: fffff8002741e891 ret_pc: fffff800c
l0: fffff80027a5d000 l1: fffff80027a5d448 l2: 00000000005aa400 l3: 0000000000002
l4: 0000000000000001 l5: fffff80024fa6da8 l6: fffff8002772f680 l7: 0000000000000
i0: fffed805b2bf6afc i1: 0000000000000000 i2: 0000000000000000 i3: 0000000000001
i4: 0000000000000000 i5: fffff80027a5d000 i6: fffff8002741e951 i7: 0000000000500
Caller[00000000005036c0]
l0: fffff80027a5d000 l1: fffff80027a5d448 l2: 00000000005aa400 l3: 0000000000002
l4: 0000000000000001 l5: fffff80024fa6da8 l6: fffff8002772f680 l7: 0000000000000
i0: fffed805b2bf6afc i1: 0000000000000000 i2: 0000000000000000 i3: 0000000000001
i4: 0000000000000000 i5: fffff80027a5d000 i6: fffff8002741e951 i7: 0000000000500
Caller[00000000005036c0]
Caller[00000000005059c0]
Caller[00000000004b9cd0]
Caller[00000000004b9dc0]
Caller[00000000004b9f90]
Caller[000000000046353c]
Caller[0000000000489a58]
Caller[0000000000477678]
Caller[00000000004779a8]
Caller[000000000048aa38]
Caller[000000000046bbe8]
Caller[000000000046c058]
Caller[000000000046c6cc]
Caller[000000000046966c]
Caller[000000000042f88c]
Caller[0000000000410674]
Caller[00000000700de224]
Instruction DUMP: 80a6c01c 02400038 8600ffdc <c4060000> 80a0a000 124ffff3 8
Killed
duke:~#
Cheers
--
.-. Thomas Bader · thomasb@trash.net.remove · http://www.t-bader.ch/ .-.
oo| oo|
/`'\ Einen Unix-Shellaccount gibt es unter http://www.trash.net/ /`'\
(\_;/) PGP Key-ID: 0x3A4B7F5D (RSA) 0x7584F5D8 (DSA/EG) (\_;/)
reply other threads:[~2001-12-09 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011209141609.A13900@trash.net \
--to=thomasb@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox