Bug 22943 - Problem with linux emulation
Summary: Problem with linux emulation
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 4.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-emulation (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-18 17:40 UTC by nasko_b
Modified: 2003-11-01 20:30 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nasko_b 2000-11-18 17:40:00 UTC 
Executing Linux binaries in chrooted enviroment cause crash.

How-To-Repeat: mount -t ext2fs /dev/ad0s4 /mnt
chroot /mnt /usr/bin/mc
___crash if few seconds___
Comment 1 Johan Karlsson freebsd_committer freebsd_triage 2000-12-15 21:54:00 UTC 
Responsible Changed
From-To: freebsd-bugs->marcel

Marcel, do you feel this is in your area (linux emu) or 
is it a chroot problem?
Comment 2 krentel 2001-10-28 20:24:04 UTC 
> Executing Linux binaries in chrooted enviroment cause crash.

Another possibility here is that the crash has nothing to do with the
chroot environment.  It is known from PR kern/19407 that running Linux
binaries on an ext2fs partition prior to 4.2-Release can cause panics.
The bug was fixed in 4.2, so update your system and try it again.

My guess is that both this and PR kern/22942 are duplicates of
PR kern/19407 and thus were fixed in 4.2.

--Mark
Comment 3 Marcel Moolenaar freebsd_committer freebsd_triage 2001-11-18 06:19:31 UTC 
Responsible Changed
From-To: marcel->emulation

Assign to emulation@FreeBSD.org. It is not going to be addressed if 
it's assigned to me and I don't do it. Maintainership of the Linuxulator 
has been passed on to emulation@FreeBSD.org as well.
Comment 4 perisa 2002-05-29 01:51:31 UTC 
Please close the PR due to feedback timeout

Thanks

Marc
Comment 5 Eric Anholt freebsd_committer freebsd_triage 2003-11-01 20:29:30 UTC 
State Changed
From-To: open->closed

Feedback timeout, followup suggests problem was fixed in 4.2.