>How I got around this was to apply Thomas Schwinge's fix_have_kernel_resources
>branch to libpthread. Basically, the first thread structure allocated is not
>zeroed out,
>so have_kernel_resources is some random non-zero number, and thus the thread
>neither gets a wakeup port, nor does the kernel_
- Original Message -
From: Richard Braun
To: Thomas Thomas
Cc: bug-hurd@gnu.org
Sent: Wednesday, August 15, 2012 3:24 AM
Subject: Re: Compiling ext2fs.static with pthreads
>On Tue, May 08, 2012 at 07:16:09PM -0700, Thomas Thomas wrote:
>> So, it runs as a translator. Spews
On Wed, Aug 15, 2012 at 11:24:20AM +0200, Richard Braun wrote:
> What prevents _hurdsig_init from being called unconditionally and
> earlier ?
In the meantime, I merely made sigstate_is_global_rcv check that
_hurd_global_sigstate isn't NULL. Now I have a subhurd completely
populated by pthreads-en
On Tue, May 08, 2012 at 07:16:09PM -0700, Thomas Thomas wrote:
> So, it runs as a translator. Spews out some unexpected debugging info that
> Barry
> added, but I can add files, delete files, list directories, etc. I haven't
> tested it under
> load, however. Thank you for the link on debugging t
Some notes here, now that I've thought some more and done some more:
>> I caught the output of make to get the full compile command and added
>> ../libpthread/cancel-cond.o into it manually, and saved it as a shell script.
>> Barry, or someone, rewrote cancel-cond.c from cthreads into a pthreads
I haven't
> tested it under
> load, however.
Oh great! I'm not sure if somebody already had gotten that far before
you. :-)
If you can, please do some more testing. If you're confident you can
also use it for your main system's rootfs or any other mount points (be
> Hi!
Howdy.
>On Sun, 6 May 2012 09:25:11 -0700 (PDT), Thomas Thomas
>wrote:
>> I played around and got it to compile, though how I did so is a nasty hack.
>What kind of?
I caught the output of make to get the full compile command and added
../libpthread/cancel-cond.o into it manually, and
Hi!
On Sun, 6 May 2012 09:25:11 -0700 (PDT), Thomas Thomas
wrote:
> I played around and got it to compile, though how I did so is a nasty hack.
What kind of?
> Should ext2fs.static compiled with pthreads be able to run on cthreads Hurd?
> It's a statically linked program that
I played around and got it to compile, though how I did so is a nasty hack.
Should ext2fs.static compiled with pthreads be able to run on cthreads Hurd?
It's a statically linked program that should have no external dependencies,
so it should run in any environment, right?
Thomas D
I've applied Barry's patch, and removed all cthreads references that I can find
(in the code that gets compiled). I compiled everything in the source tree,
so I clobbered the linker script version of libpthread.a. In attempting to run
ext2fs.static, I get an assertion failure in pthread
Follow-up Comment #1, bug #17131 (project hurd):
This is old, but still would be help to new Hurd users. The only blocksize
supported is 4096. Do "mkfs.ext2 -b 4096 /target/location" and then you can
mount it as "settrans -ca /mount/point /hurd/ext2fs /target/location"
___
Hello!
On Sun, Aug 06, 2006 at 01:57:34PM -0700, Roland McGrath wrote:
> > Samuel Thibault, le Sat 05 Aug 2006 02:45:34 +0200, a écrit :
> > > Samuel Thibault, le Sat 05 Aug 2006 02:27:35 +0200, a écrit :
> > > > assert (! __spin_lock_locked (&ss->critical_section_lock));
> > > > __spin_lock (
> Samuel Thibault, le Sat 05 Aug 2006 02:45:34 +0200, a écrit :
> > Samuel Thibault, le Sat 05 Aug 2006 02:27:35 +0200, a écrit :
> > > assert (! __spin_lock_locked (&ss->critical_section_lock));
> > > __spin_lock (&ss->critical_section_lock);
> > >
> > > Why should one check that a spinlock i
Samuel Thibault, le Sat 05 Aug 2006 02:45:34 +0200, a écrit :
> Samuel Thibault, le Sat 05 Aug 2006 02:27:35 +0200, a écrit :
> > assert (! __spin_lock_locked (&ss->critical_section_lock));
> > __spin_lock (&ss->critical_section_lock);
> >
> > Why should one check that a spinlock is free befor
Samuel Thibault, le Sat 05 Aug 2006 02:27:35 +0200, a écrit :
> assert (! __spin_lock_locked (&ss->critical_section_lock));
> __spin_lock (&ss->critical_section_lock);
>
> Why should one check that a spinlock is free before taking it?? Here the
> purpose is to cancel _another_ thread, so it _c
Hi,
I've met this bug again (it was reported almost 7 years ago in debian
bts as #46859 and periodically noticed again), and a quick look at the
code upsets me:
assert (! __spin_lock_locked (&ss->critical_section_lock));
__spin_lock (&ss->critical_section_lock);
Why should one check that a s
Update of bug #8497 (project hurd):
Status:None => Works For Me
Open/Closed:Open => Closed
Reproducibility:None => Once
_
Follow-up Comment #1, bug #8497 (project hurd):
I tried to reproduce that old bug. I made some big ext2fs.static, one with
27MB, everyone worked. So, there are some possibilities to that problem.
1) It was already solved by others patchs.
2) It was never an GNU Mach bug, but a bug of an broken
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=17131>
Summary: Different behavior of ext2fs and ext2fs.static
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Monday 07/17/06 at 11:37
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=17130>
Summary: Different behavior of ext2fs and ext2fs.static
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Monday 07/17/06 at 11:35
[CCed to bug-hurd.]
On Mon, Apr 03, 2006 at 02:46:53PM +0300, Constantine Kousoulos wrote:
> The problem appears when the binary /hurd/ext2fs.static executes.
>
> Don't i need the source file as well to debug the binary?
Uh, I don't really know how I'd start to debug `ex
> Oh, Jeroen noted that this won't work with gcc 3.3, but with >
> 3.3 it works.
Really? libc's defines __attribute_used__ using
`used' for gcc 3.1 and later, and `unused' for earlier. What does
"won't work" mean? Does 3.3 not accept the `used' attribute, or
does it still eli
> Oh, Jeroen noted that this won't work with gcc 3.3, but with > 3.3 it
> works.
Really? libc's defines __attribute_used__ using `used'
for gcc 3.1 and later, and `unused' for earlier. What does "won't work" mean?
Does 3.3 not accept the `used' attribute, or does it still elide the
definition
Oh, Jeroen noted that this won't work with gcc 3.3, but with > 3.3 it
works.
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
The following fixes the problem:
2005-09-24 Alfred M. Szmidt <[EMAIL PROTECTED]>
* store.h (STORE_STD_CLASS): Changed attributed `unused' to
`used'.
--- libstore/store.h
+++ libstore/store.h
@@ -627,7 +627,7 @@
#define STORE_STD_CLASS(name) \
static const struct store_cla
Currently, ext2fs.static fails as follows:
(gdb) rr
ext2fs.static: ../../src/libdiskfs/init-main.c:40: diskfs_init_main: Unexpected
error: Invalid argument.
Program received signal SIGABRT, Aborted.
0x080b3a0c in mach_msg_trap () at lock-intern.h:77
77 lock-intern.h: No such file or
On Thu, Apr 07, 2005 at 10:34:35AM +0200, Thomas Schwinge wrote:
> Last night, while I was compiling GNU Mach, I got the following assertion
> failure:
> #v+
> ext2fs.static: thread_cancel.c:55: hurd_thread_cancel: Assertion `!
> __spin_lock_locked (&ss->critical_secti
Hello!
Last night, while I was compiling GNU Mach, I got the following assertion
failure:
#v+
ext2fs.static: thread_cancel.c:55: hurd_thread_cancel: Assertion `!
__spin_lock_locked (&ss->critical_section_lock)' failed.
#v-
GNU Mach did not enter the kernel debugger, but was just han
Hi,
Thanks for your reply Patrick Strasser.
--- Patrick Strasser <[EMAIL PROTECTED]>
wrote:
> > Partition check (DOS partitions):
> > hd0: hd0: status timeout: status=0xff { Busy }
> > hd1: disabled DMA
> > hd0: drive not ready for command
>
> Tell us more about your IDE configuration:
> Do
Shakthi Kannan wrote:
Greetings!
Rebooted to grub.At grub prompt,
("find /boot/gnumach.gz" returns (hd0,2)
Once You've found gnumach.gz you've found your working partition.
You can set your default partition for the following commands with "root":
root (hd0,2)
For the "kernel" and "module" comm
Alfred M. Szmidt wrote:
Other suggestions for what? You didn't tell us what your current
problem was (atleast, I couldn't see it).
His booting stopped after saying
start (hd0,2)/hurd/ext2fs.static:
(hd0,2)/hurd/ext2fs.static:
(as he described in his original post, and is still in
Actually, I am typing everything in one line in the
grub prompt.
Why don't you use menu.lst? It will save you a bit of useless
typing... See the grub manual for details.
I hit an enter while posting in the mailing list for readability.
Please don't, always always leave the input and
ule (hd0,2)/hurd/ext2fs.static
--multiboot-command-line=${kernel-command-line}
--host-priv-port=${host-port}
--device-master-port=${device-port}
--exec-server-task=${exec-task} -T typed
Actually, I am typing everything in one line in the
grub prompt. I hit an enter while posting in the
mailing list
(hd0,2)/hurd/ext2fs.static
--multiboot-command-line=${kernel-command-line} --host-priv-port=${host-port}
--device-master-port=${device-port} --exec-server-task=${exec-task} -T typed
And that is obciously _still_ wrong. It should look like this:
module /hurd/ext2fs.static --multiboot-command-line=${ke
should be one line:
module (hd0,2)/hurd/ext2fs.static
--multiboot-command-line=${kernel-command-line} --host-priv-port=${host-port}
--device-master-port=${device-port} --exec-server-task=${exec-task} -T typed
If you want multiple lines, end the line with a ba
hd0: status timeout: status=0xff { Busy}
end_request: I/O error, dev 03:00, sector 0
hd0: drive not ready for command
unable to read partition table
hd1: hd1s1 hd1s2 hd1s3 hd1s4
...
2 multiboot modules
...
task loaded: (hd0,2)/lib/ld.so.1 /hurd/exec
start (hd0,2)/hurd/ext2fs.static:
(hd0,2
ot/gnumach.gz
root=device:hd1s3 -s
grub>module (hd0,2)/hurd/ext2fs.static
--multiboot-command-line=${kernel-command-line}
--host-priv-port=${host-port}
--device-master-port=${device-port}
--exec-server-task=${exec-task} -T typed
${root}
$(task-creat
Hi,
When libc0.3-dev 2.3.2.ds1-12.0.1 by Michael Banck is installed,
compilation of the Hurd leads to bad ext2fs.static that always signals
SEGV. (ext2fs and other executables seem fine.) When older 2.3.1-5 is
installed, ext2fs.static is fine.
Unfortunately, it's too difficult for
Ognyan Kulev wrote:
Barry deFreese wrote:
No messages. It hangs as soon as it tries to load ext2fs.static. So
now my machine is borked so no, I haven't tried it on other fs's yet.
:-(
Just to be sure that you won't reinstall everything: use dpkg-hurd
found in root d
Barry deFreese wrote:
No messages. It hangs as soon as it tries to load ext2fs.static. So
now my machine is borked so no, I haven't tried it on other fs's yet. :-(
Just to be sure that you won't reinstall everything: use dpkg-hurd found
in root directory. It's intended to
Ognyan Kulev wrote:
Barry deFreese wrote:
I just recompiled Hurd with gcc-3.3 with Ogi's patches and now the
machine hangs with ext2fs.static... :-(
Any assertion messages? Which version of the patch did you use? Does
it hang right after ext2fs.static is started or after some time?
Barry deFreese wrote:
I just recompiled Hurd with gcc-3.3 with Ogi's patches and now the
machine hangs with ext2fs.static... :-(
Any assertion messages? Which version of the patch did you use? Does
it hang right after ext2fs.static is started or after some time? Have
you tried
On Wed, Apr 28, 2004 at 02:38:06PM -0700, Barry deFreese wrote:
> I just recompiled Hurd with gcc-3.3 with Ogi's patches and now the
> machine hangs with ext2fs.static... :-(
Uhm, so here's a bit of advice until the demi-gods jump in:
I /seem/ to remember that people said th
I just recompiled Hurd with gcc-3.3 with Ogi's patches and now the
machine hangs with ext2fs.static... :-(
What gives?
--
Barry deFreese
Debian 3.0r1 "Woody"
GNU/Hurd
Registered Linux "Newbie" #302256 - Hurd H4XX0r wannabe
"Programming today is a race between
mary: GNU Mach panics if ext2fs.static is too big
Original Submission: Hi,
we have one report by an user that GNU Mach panics with a message like "unable to
allocate contiguous memory" when ext2fs.static is not stripped (>13MB), while it works
if ext2fs.static is stripped. The u
Package: hurd
Version: 20020804-1
Tags: unreproducible
After some builds of oskit and gnumach I got the following assertion
failure:
ext2fs.static: thread-cancel.c:55: Assertion `! __spin_lock_locked
(&ss->critical_section_lock)' failed.
libc0.3 is 2.3.1-5.
P.S. The most interes
I got a different Hurd crash than normal. I don't have any more
information than this, sorry. This occured when I was doing an
autobuilder run:
extfs.static: thread-cancel.c:55: hurd_thread_cancel: Assertion `! __spin_lock_locked
(&ss->critical_section_lock)' failed.
The crash is unusual in t
47 matches
Mail list logo
