Matthew Fleming wrote:
> On Sun, Oct 3, 2010 at 7:16 PM, Steve Kargl
> wrote:
>> I suspect that 517 ( are not expected during boot.
>>
>>
>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
>> (((
It looks very strange. fcntl() always fails to delete lock file
and command.l_pid is always -6464. This issue is disclosed in
porting Google's Japanese input system called "mozc".
details follow:
http://code.google.com/p/mozc/issues/detail?id=40
% uname -a
FreeBSD parancell.ongs.co.jp 9.0-
On Sun, Oct 03, 2010 at 08:05:49PM -0700, Matthew Fleming wrote:
>
> Does this always happen with acd0?
The long string of '(' appeared in 5 out of 5
'shutdown -r now'. So, this is definitely
reproducible for me.
--
Steve
___
freebsd-current@freebs
On Sun, Oct 03, 2010 at 08:05:49PM -0700, Matthew Fleming wrote:
> On Sun, Oct 3, 2010 at 7:16 PM, Steve Kargl
> wrote:
> > I suspect that 517 ( are not expected during boot.
> >
> >
> > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
(517 '(' deleted)
> > cd0 at ata0 bus 0 scbus1 tar
On Sun, Oct 3, 2010 at 7:16 PM, Steve Kargl
wrote:
> I suspect that 517 ( are not expected during boot.
>
>
> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> (((
I suspect that 517 ( are not expected during boot.
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
((
On Sun, Oct 03, 2010 at 03:42:51PM -0700, Julian Elischer wrote:
> ...
> well you got the stacktrace of the keyboard handler since you got into
> ddb via the keyboard..
OK
> you need to see what ELSE is running.. especially the initial threads.
> and look at THOSE stacks
Ah. My lack of pr
On 10/3/10 6:14 AM, David Wolfskill wrote:
On Sun, Oct 03, 2010 at 02:52:19PM +0300, Andriy Gapon wrote:
on 03/10/2010 14:28 David Wolfskill said the following:
[snipped]
Can't you just drop to DDB prompt and examine where the threads are?
Eh -- thanks for the reality check; I needed that. :
On 2010-10-03 17:21, Dimitry Andric wrote:
Since gnash has about a gazillion dependencies, and I have the idea that
after 12 hours of building stuff, I will not be able to reproduce your
error message anyway, could you please post it (or upload it, if it is
very large)?
I cannot reproduce your
On Sun, Oct 3, 2010 at 12:50 PM, Roman Divacky wrote:
> On Sun, Oct 03, 2010 at 05:21:15PM +0200, Dimitry Andric wrote:
>> On 2010-10-03 15:41, Derek Tattersall wrote:
>> >In updating gnash to 8.8 the build failed while linking with libvgl.so. My
>> >current system was built last week, with both
On Sun, Oct 03, 2010 at 05:21:15PM +0200, Dimitry Andric wrote:
> On 2010-10-03 15:41, Derek Tattersall wrote:
> >In updating gnash to 8.8 the build failed while linking with libvgl.so. My
> >current system was built last week, with both kernel and world built
> >with clang. The linkage failure w
On 10/01/10 10:54, Andre Oppermann wrote:
> On 30.09.2010 19:51, Ivan Voras wrote:
>> On 09/30/10 18:37, Andre Oppermann wrote:
>>
>>> Both the vmmap and page table make use of splay trees to manage the
>>> entries and to speed up lookups compared to long to traverse linked
>>> lists or more memory
On 2010-10-03 15:41, Derek Tattersall wrote:
In updating gnash to 8.8 the build failed while linking with libvgl.so. My
current system was built last week, with both kernel and world built
with clang. The linkage failure was due to an inlined function,
"set4pixels" which is only referred to, as
* Rui Paulo [101003 09:57]:
> On 3 Oct 2010, at 14:41, Derek Tattersall wrote:
>
> > In updating gnash to 8.8 the build failed while linking with libvgl.so. My
> > current system was built last week, with both kernel and world built
> > with clang. The linkage failure was due to an inlined func
On 3 Oct 2010, at 14:41, Derek Tattersall wrote:
> In updating gnash to 8.8 the build failed while linking with libvgl.so. My
> current system was built last week, with both kernel and world built
> with clang. The linkage failure was due to an inlined function,
> "set4pixels" which is only refe
In updating gnash to 8.8 the build failed while linking with libvgl.so. My
current system was built last week, with both kernel and world built
with clang. The linkage failure was due to an inlined function,
"set4pixels" which is only referred to, as far as I can tell, within the
source file simp
On Sun, Oct 03, 2010 at 02:52:19PM +0300, Andriy Gapon wrote:
> on 03/10/2010 14:28 David Wolfskill said the following:
> [snipped]
>
> Can't you just drop to DDB prompt and examine where the threads are?
Eh -- thanks for the reality check; I needed that. :-}
OK; I enabled the KDB & DDB options
on 03/10/2010 14:28 David Wolfskill said the following:
[snipped]
Can't you just drop to DDB prompt and examine where the threads are?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
On Fri, Oct 01, 2010 at 08:38:59PM -0700, David Wolfskill wrote:
> On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
> > ...
> > > Any ideas on what mught be causing CURRENT to hang -- sometimes
> > > -- given that it appears to involve the Modular Bay (or the specific
> > > device tha
19 matches
Mail list logo
