Re: Ability to further support 32bit architectures

[Rene Engelhard]

Hi,

Am 13.01.24 um 13:59 schrieb rhys:

No.

You are AGAIN assuming what I am talking about.

Maybe because of how you write...

I know the difference between a 32-bit processor and a 64-bit processor.


Obviously you don't. Or at least are not aware about consequences.


Since you still offer 32bit machines of which Debian has enough of. (64 
bit kernel probably but it doesn't matter) where it does not matter at all.



You ignore the stated fact in this thread that on a 32bit processor one 
process can't get more than 3GB or even less of RAM (regardless of what 
memory extension stuff exists).


In  https://lists.debian.org/debian-kernel/2024/01/msg00191.html (where 
the quoting is a problem, one doesn't know what is yours and what not) 
you ignored what YunQiang said in the post you replied to:


https://lists.debian.org/debian-kernel/2024/01/msg00189.html

Quoting again just for you:

"[...] It is about some limitation of 32bit.
2 examples for it:
   1. if we use 32bit value for time, it will overflow in 2038, then
your time will be shown as 1900.
   https://en.wikipedia.org/wiki/Year_2038_problem
   2. A single process (or maybe APP, not precisely), can only use UP
to 4GiB RAM.
   In fact on most system the value is less than 4GiB:
  on intel32, it is 3GiB
  on mips32, it is 2GiB
   But currently, it is not enough, for example, when we build a
big APP, it will need much more RAM.
   The RAM does install in your Rack, but you can NOT use it.
  https://en.wikipedia.org/wiki/3_GB_barrier

"

And THAT (2.) is the problem here for linking big applications/compile 
units. Not the lack of machines.


And that is a limitation of *the architecture*.

Putting more "32bit machines" on it do not change anything of that 
except that there were more machines which cannot build big stuff.



Regards,


Rene

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

[Rene Engelhard]

notfound 883938 3.16.43-2+deb8u5
found 883938 3.16.51-2
thanks

Hi,

On Sat, Dec 09, 2017 at 06:23:04PM +0100, debbug wrote:
> Package: src:linux
> Version: 3.16.43-2+deb8u5
> Severity: grave
> Justification: renders package unusable
> 
> (Note: This bug affects version 3.16.51-2, not 3.16.43-2+deb8u5,
> but that's the version that "reportbug" filled in after downgrading
> to get this system back up running)

Then you should have edited the report accordingly...

Regards,

Rene

Bug#880979: libreoffice-calc: Crash after starting NLPsolver

[Rene Engelhard]

severity 880979 grave
reassign 880979 src:linux
forcemerge 880979 865303 
affects 880979 libreoffice-wiki-publisher
affects 880979 libreoffice-nlpsolver
affects 880979 libreoffice-calc
thanks

Hi,

On Mon, Nov 06, 2017 at 04:36:29PM +0100, Sulyok Attila wrote:
> I experinenced an immediate crach when starting NLPsolver extension.  

The NLPsolver extension is in libreoffice-nlpsolver, not in -calc...

> I am regular user of this non-linear extension package.
> Recently, I updated my Libreoffice-set to 5.4.2 from stretch-backport.

... and your kernel, probably ... longer ago...

> I have worked on my sheets for a week, and now I started an NLPsolver step 
> that caused a prompt crash.

Yes, known. It's Java.

> I repeated it a few times with the same crashing end.
> I checked the installation and everything was good.
> I deleted and reinstalled the NLP extension, but it did not help.
> 
> A cleared the whole libreoffice installation and went back to the 5.2.7 
> version of the stable, beacause it worked well previously.
> I received the same crashing result.

Exactly. Because it's not LO at fault.

> Because the NLP package itself is not a new one, I assume there is some 
> glitch in the debian package and/or there is 
> some faulty error treating in the LibreOffice.

No, in Java and the kernel.

> Now I see two problems.
> 1. It is not a normal situation if the Calc of LibreOffice crashes when 
> something is not proper in its environment.

Correct.

> 2. What do I need to do to restore my LibreOffice ability to use the NLP 
> again ?

Fix the Linux kernel and/or Java. Or use amd64 instead of i386. This is
a know problem and doesn't happen on amd64.

See

#865303 [G|u|=☣] [src:linux] libreoffice: Libreoffice Java features crash with 
Linux 3.16.43-2+deb8u1

(and the bugs merged with it)

#876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
#876068 [i|+|☣] [openjdk-7-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield

and

#876069 [i|+|☺☣] [openjdk-9-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield 

(I just noticed that this fixed, not available in stable yet. Maybe I should
force that newe(er) OpenJDK 9 for i386 for buster/sid/stretch-backports if it's
available there.)

See also the press coverage months ago:

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Regards,

Rene

Bug#876021: Aw: Re: Bug#876021: libreoffice-writer: launching writer makes libreoffice crash

[Rene Engelhard]

Hi,

As I said: Stuff using Java crashes

This means e.g. Wruter when initializing the wiki publisher and ESPECIALLY Base 
since Bases internal database is pure Java.
So there is no real work around for Base except maybe connecting via odbc or to 
MySQL/PostgreSQL directly via the respective connectors...

As said, the bug needs to be fixed in the kernel and/or Java.

Regards

Rene

> Gesendet: Freitag, 13. Oktober 2017 um 21:13 Uhr
> Von: "Jérôme Bouat" <jerome.bo...@wanadoo.fr>
> An: "Rene Engelhard" <r...@debian.org>
> Cc: 876...@bugs.debian.org
> Betreff: Re: Bug#876021: libreoffice-writer: launching writer makes 
> libreoffice crash
>
> Hello.
> 
> FYI,
> I removed the libreoffice-wiki-publisher package. Next I achieved to use 
> Writer. However I experienced a crash when I tried to create a new LO Base 
> file.
> 
>

Bug#877809: libreoffice writer java kernel crash

[Rene Engelhard]

reassign 877809 src:linux
forcemerge 865303 877809
thanks

On Thu, Oct 05, 2017 at 10:19:18PM +0100, Andrew Rule wrote:
> I recently upgraded to libreoffice 5.4.1-1 i386, and experienced the following
> problem:
> 
> While using
> openjdk-8-jre version 8u144-b01-1 i386
> kernel 4.9.21 i686 built from source

Yes, that kernel didn't have the bug. It doesn't have the Stack Clash
security fix either I think?

> then there is no problem at all, but,
> 
> with either
> kernel 4.9.51 i686 built from source, or
> kernel 4.12.0-2-686-pae Debian 4.12.13-1 i686

Those have.

> then using openjdk-8-jre in LibreOffice Calc works fine, Impress works fine,
> but Writer crashes on load, with exit +139, both on an Intel i3 and an AMD A4.
> If you turn off Java, or use the Free Software Foundation (gcj) it works and
> does not crash.

And you didn't even dare to check the libreoffice-writer bug list?

Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)

#865303 [G|Mu|=☣] [src:linux] libreoffice: Libreoffice Java features crash with 
Linux 3.16.43-2+deb8u1
Outstanding bugs -- Important bugs; Patch Available (2 bugs)

#876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
#876069 [i|+|☣] [openjdk-9-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield

directly on the top

You yourself say "libreoffice writer java kernel crash".

The first bug says:

Found in versions linux/4.9.30-2+deb9u1, linux/4.11.6-1, linux/3.2.89-1, 
linux/4.9.30-2+deb9u2, linux/3.16.43-2+deb8u1

and has many "friends" merged with it.

> I have also amd64 architecture on the AMD A4, and have not experienced the
> problem with that architecture.

Yes, that is i386 only.

See also

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Yes, this is still unfixed, but a kernel/OpenJDK bug. LO just calls
JNI_StartJVM or how it's called. _OpenJDK_ crashes then.

> ii  libreoffice-wiki-publisher  1.2.0+LibO5.4.1-1

You can try removing this, this is just recommended to have a "full"
LO install if one did apt-get install libreoffice. That one's Java
and seems to be initialized on (most) "normal" writer startups, too
-> the Java crash.

Or use a architecture which wasn't already obsolete last decade. As you
say yourself: amd64 works.

Regards,

Rene

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

[Rene Engelhard]

Hi,

sent to early.

On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote:
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  

OpenJDK.

> Identifier: com.sun.wiki-publisher
>   Version: 1.2.0
>   URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
>   is registered: yes
>   Media-Type: application/vnd.sun.star.package-bundle
>   Description: The Wiki Publisher enables you to create Wiki articles on 
> MediaWiki servers without having to know the syntax of the MediaWiki markup 
> language. Publish your new and existing documents transparently with the 
> Writer to a wiki page.

Ah, there it is.

> Identifier: com.sun.star.comp.Calc.NLPSolver
>   Version: 0.9
>   URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
>   is registered: yes
>   Media-Type: application/vnd.sun.star.package-bundle
>   Description: This extension integrates into Calc and offers new Solver 
> engines to use for optimizing nonlinear programming models.

Also Java

> -- System Information:
> Debian Release: 9.1
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)

And there we have a big point, this regression is 32-bit/i386 only. If you
used amd64 it wouldn't happen..

Regards,

Rene

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

[Rene Engelhard]

retitle 877339 libreoffice-core: libreoffice SEGV in _expand_stack_to on most 
documents
reassign 877339 src:linux
forcemerge 865303 877339
thanks

Hi,

On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote:
> I've found stable's version of libreoffice basically unusable (I
> previously found oldoldstable's just fine), crashing on nearly

oldoldstables would also crash the same way if it happened to initialize
someting Javaish (e.g. libreoffice-wiki-publisher).

And wiki-publisher is installed by the libreoffice metapackage in stretch...
(Recommends:, which is installed per default.)

> everything I try and open with it. Unfortunately, most of the
> Office docs I have to interact with are confidential. I've finally
> found one that isn't, so I'll attach it to this bug report.
> 
> The failure mode is always the same - libreoffice gets much of the way
> through start up, often opening a window, and then core dumps:
> 
> matthew@aragorn:~$ gdb /usr/lib/libreoffice/program/soffice.bin core
> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging 
> symbols found)...done.
> [New LWP 25365]
> [New LWP 25380]
> [New LWP 25367]
> [New LWP 25370]
> [New LWP 25374]
> [New LWP 25372]
> [New LWP 25371]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/lib/libreoffice/program/soffice.bin 
> firefox-downloads/it_manager_person_sp'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> [Current thread is 1 (Thread 0x483dc180 (LWP 25365))]
> (gdb) bt
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so

There we go. The infamous Stack Clash kernel regression (maybe also a bug in
OpenJDK).

A simple look at the mostly affected modules (Base, Writer if wiki-publisher
is installed) would have shown you that bugs:

Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)

#865303 [G|Mu|=☣] [src:linux] libreoffice: Libreoffice Java features crash with 
Linux 3.16.43-2+deb8u1
Outstanding bugs -- Important bugs; Patch Available (2 bugs)

#876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
#876069 [i|+|☣] [openjdk-9-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
[...]
#876068 [i|+|☣] [openjdk-7-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield

See the above bugs, especially on the kernel and

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Yes, everything here is _still_ unfixed.

Regards,

Rene

Bug#875269: libreoffice-base: LibreOffice-Base crashes when trying to open Tables view in Debian 9 Stretch.

[Rene Engelhard]

severity 875269 grave
reassign 875269 src:linux
forcemerge 865866 875269 
thanks

On Sun, Sep 10, 2017 at 01:57:15PM +0700, DocTom wrote:
> I upgraded from Debian 8 Jessie to Debian 9 Stretch and the problem was
> immediate. I used LO Base for 2 years with the same hardware, and the Debian 8
> Jessie OS with Cinnamon desktop.  There were no problems of any note.

Jessie should have had the same problem if you upgraded the kernel..

> I upgraded to Debian 9 Stretch about 2 months ago, retaining the Cinnamon
> desktop, and all appeared to go smoothly. But now at the first attempt to open
> my Base files since upgrading, I find that Base will not work properly as
> described.
[...]
> LO Writer would not open at all at first, but after applying a fix that I 
> found
> on the net (removing two files), it now appears to be working normally also.

You searched the net? Then you should have seen the reason of this bug in Base.

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Still unfixed.

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303 and "friends".
Somewhere there is also the boot option to disable the security(!) fix
to make Java work again.

> There is no error message - after crash, on re-opening Base, a LibreOffice
> Recovery window appears, and recovery appears to be successful. 

In crashes there seldomly is. What would be needed is a backtrace but I won't
ask for one as I think it's clear that it's the above bug. If you want, though:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information

> -- System Information:
> Debian Release: 9.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: i386 (i686)

Wouldn't have happened if you wouldn't use a architecture which was already
obsolete in the last decade.

Regards,

Rene

Re: Kernel: Fix for CVE-2017-1000364 (mm: enlarge stack guard gap) breaks java application

[Rene Engelhard]

Hi,

On Tue, Jun 27, 2017 at 10:13:25PM +0200, Salvatore Bonaccorso wrote:
> We issued a regression update:
> 
> https://lists.debian.org/debian-security-announce/2017/msg00160.html
> 
> To answer your question still, if you set the kernel parameter to
> stack_guard_gap=1 this wuould effectively revert the fix for
> CVE-2017-1000364.
> 
> Hope this helps?

Apparently not on i386...

https://buildd.debian.org/status/fetch.php?pkg=libreoffice=i386=1%3A5.3.4-1=1498741441=0:

[...]
[build CUT] dbaccess_RowSetClones
S=/<> && I=$S/instdir && W=$S/workdir &&mkdir -p 
$W/CppunitTest/ && rm -fr $W/CppunitTest/dbaccess_RowSetClones.test.user && 
mkdir $W/CppunitTest/dbaccess_RowSetClones.test.user &&rm -fr 
$W/CppunitTest/dbaccess_RowSetClones.test.core && mkdir 
$W/CppunitTest/dbaccess_RowSetClones.test.core && cd 
$W/CppunitTest/dbaccess_RowSetClones.test.core && (  
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program":$W/UnpackedTarball/cppunit/src/cppunit/.libs
   MALLOC_CHECK_=2 MALLOC_PERTURB_=153  
$W/LinkTarget/Executable/cppunittester 
$W/LinkTarget/CppunitTest/libtest_dbaccess_RowSetClones.so --headless 
"-env:BRAND_BASE_DIR=file://$S/instdir" "-env:BRAND_SHARE_SUBDIR=share" 
"-env:UserInstallation=file://$W/CppunitTest/dbaccess_RowSetClones.test.user"   
"-env:CONFIGURATION_LAYERS=xcsxcu:file://$I/share/registry 
xcsxcu:file://$W/unittest/registry"  
"-env:UNO_TYPES=file://$I/program/types/offapi.rdb 
file://$I/program/types/oovbaapi.rdb file://$I/program/types.rdb"  
"-env:UNO_SERVICES=file://$W/Rdb/ure/services.rdb 
file://$W/ComponentTarget/basic/util/sb.component 
file://$W/ComponentTarget/comphelper/util/comphelp.component 
file://$W/ComponentTarget/configmgr/source/configmgr.component 
file://$W/ComponentTarget/connectivity/source/drivers/hsqldb/hsqldb.component 
file://$W/ComponentTarget/connectivity/source/drivers/jdbc/jdbc.component 
file://$W/ComponentTarget/connectivity/source/manager/sdbc2.component 
file://$W/ComponentTarget/dbaccess/util/dba.component 
file://$W/ComponentTarget/dbaccess/util/dbu.component 
file://$W/ComponentTarget/dbaccess/util/sdbt.component 
file://$W/ComponentTarget/dbaccess/source/filter/xml/dbaxml.component 
file://$W/ComponentTarget/filter/source/config/cache/filterconfig1.component 
file://$W/ComponentTarget/forms/util/frm.component 
file://$W/ComponentTarget/framework/util/fwk.component 
file://$W/ComponentTarget/i18npool/util/i18npool.component 
file://$W/ComponentTarget/linguistic/source/lng.component 
file://$W/ComponentTarget/oox/util/oox.component 
file://$W/ComponentTarget/package/source/xstor/xstor.component 
file://$W/ComponentTarget/package/util/package2.component 
file://$W/ComponentTarget/sax/source/expatwrap/expwrap.component 
file://$W/ComponentTarget/scripting/source/basprov/basprov.component 
file://$W/ComponentTarget/scripting/util/scriptframe.component 
file://$W/ComponentTarget/sfx2/util/sfx.component 
file://$W/ComponentTarget/sot/util/sot.component 
file://$W/ComponentTarget/svl/source/fsstor/fsstorage.component 
file://$W/ComponentTarget/svl/util/svl.component 
file://$W/ComponentTarget/toolkit/util/tk.component 
file://$W/ComponentTarget/ucb/source/core/ucb1.component 
file://$W/ComponentTarget/ucb/source/ucp/file/ucpfile1.component 
file://$W/ComponentTarget/ucb/source/ucp/tdoc/ucptdoc1.component 
file://$W/ComponentTarget/unotools/util/utl.component 
file://$W/ComponentTarget/unoxml/source/rdf/unordf.component 
file://$W/ComponentTarget/unoxml/source/service/unoxml.component 
file://$W/ComponentTarget/uui/util/uui.component 
file://$W/ComponentTarget/xmloff/util/xo.component"  
-env:URE_INTERNAL_LIB_DIR=file://$I/program -env:LO_LIB_DIR=file://$I/program 
-env:LO_JAVA_DIR=file://$I/program/classes --protector 
$W/LinkTarget/Library/unoexceptionprotector.so unoexceptionprotector 
--protector $W/LinkTarget/Library/unobootstrapprotector.so 
unobootstrapprotector   --protector 
$W/LinkTarget/Library/libvclbootstrapprotector.so vclbootstrapprotector   
"-env:CPPUNITTESTTARGET=$W/CppunitTest/dbaccess_RowSetClones.test"   > 
$W/CppunitTest/dbaccess_RowSetClones.test.log 2>&1 || ( RET=$?; 
$S/solenv/bin/gdb-core-bt.sh $W/LinkTarget/Executable/cppunittester 
$W/CppunitTest/dbaccess_RowSetClones.test.core $RET >> 
$W/CppunitTest/dbaccess_RowSetClones.test.log 2>&1; cat 
$W/CppunitTest/dbaccess_RowSetClones.test.log; 
$S/solenv/gbuild/platform/unittest-failed-default.sh Cppunit 
dbaccess_RowSetClones))
Segmentation fault (core dumped)

It looks like /<>/workdir/LinkTarget/Executable/cppunittester 
generated a core file at 
/<>/workdir/CppunitTest/dbaccess_RowSetClones.test.core/core
Backtraces:
[New LWP 9516]
[New LWP 9520]
[New LWP 9519]
[New LWP 9517]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `/<>/workdir/LinkTarget/Executable/cppun'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xead5a975 in 

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Rene Engelhard]

Hi,

On Wed, Jun 21, 2017 at 12:34:28AM +0100, Ben Hutchings wrote:
> > LibreOffice isn't and is also affected (#865303)
> 
> Does LibreOffice run Java code in its main thread?  I think that might
> be a common factor that makes a difference.  It *appears* that the
> 'java' command doesn't run Java code in the main thread, but JNI users
> may do.  And new threads are created through glibc aren't affected by
> this kernel change.

Assume so, yes. It doesn't run "java" either but directly jumps into the
JVM via its libs (ttbomk)

Regards,

Rene

Re: Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Rene Engelhard]

Hi,

On Wed, Jun 21, 2017 at 02:12:38AM +0100, Ben Hutchings wrote:
> On Tue, 2017-06-20 at 23:23 +0200, Rene Engelhard wrote:
> [...]
> > Indeed, LOs Java stuff crash :(. Checked with "just" creating a database.
> > (which uses hsqldb.)
> > 
> > Downgrading _the kernel_ (and of course rebooting) fixes it. 
> > 
> > No idea whether only LOs Java stuff is affected or more JDK usage (besides
> > #865311...), but...
> 
> I don't have a suitable VM to test this, so could you check whether it
> also crashes under linux 4.11.6-1 (from unstable)?  That has a later
> version of the stack clash fix.

_Seems_ so.

It also seems to me that stretch isn't affected. I can create a
database wiithout it immediately crashing. (Creating table has some problems,
though, no idea whether related or not.)

Need to do more tests when I have more time I guess.

Regards,

Rene

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Rene Engelhard]

Hi,

On Tue, Jun 20, 2017 at 09:52:05PM +0100, Ben Hutchings wrote:
> On Tue, 2017-06-20 at 21:47 +0100, Ben Hutchings wrote:
> > Control: tag -1 - moreinfo
> > Control: notfound -1 4.9.30-2
> > Control: found -1 4.9.30-2+deb9u1
> > Control: found -1 3.16.43-2+deb8u1
> > 
> > Thanks for the extra information.
> 
> One more question: are these applications started using jsvc?

LibreOffice isn't and is also affected (#865303)

Regards,

Rene

Re: Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Rene Engelhard]

tag 865303 - unreproducible
severity 865303 important
severity 865303 libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
reassign 865303 src:linux
found 865303 3.16.43-2+deb8u1
affects 865303 libreoffice
thanks

Hi,

On Tue, Jun 20, 2017 at 09:55:51PM +0200, Rene Engelhard wrote:
> On Tue, Jun 20, 2017 at 09:33:22PM +0200, Eduardo Casais wrote:
> > >I installed a fresh jessie inside a libvirt VM. The installer alraedy
> > >applies the security updates - thus I got the new kernel and libc6 etc.
> > >(libffi isn't used by LO)
> > >
> > >Starts fine for me...
> > >
> > >-> unreproducible
> [...]
> > As a complement to the installation of LibreOffice, following extensions had
> > been set up:
> > 
> > terminologie-1.3.1.oxt
> 
> https://extensions.libreoffice.org/extensions/correcteur-terminologique-francais
> 
> seriously? tested only with 3.5?
[...]
> They should simply be data, so no. Except maybe terminologie which I can't
> download but it links to https://github.com/portaildulibre/CTLO/ which shows
> it's Java...

OK; that was the clue. I already saw openjdk accessed in your strace but that's
the case also in normal startup if you have Java stuff.

Indeed, LOs Java stuff crash :(. Checked with "just" creating a database.
(which uses hsqldb.)

Downgrading _the kernel_ (and of course rebooting) fixes it. 

No idea whether only LOs Java stuff is affected or more JDK usage (besides
#865311...), but...

Regards,
 
Rene

Re: Bug#616093: libreoffice: on file open dialog the whole system gets halted

[Rene Engelhard]

severity 616093 important
reassign 616093 xserver-xorg-video-nouveau,linux-image-2.6.37-2-amd64
affects 616093 libreoffice
thanks

On Wed, Mar 02, 2011 at 08:17:55PM +0100, Martin Künstner wrote:
 on my system this bug is reproducable.
 
 How can i provide further information.

He wrote me a private mail and agreed that it's either a X/nouveau or
a kernel bug. So reassigning.

FTR, I asked on #debian.de yesterday and another person wasn't able
to reproduce it either after a dist-upgrade to sid. i386, though, but I don't
kknow his nvidia/kernel combination.

Grüße/Regards,

René


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110303085732.gr4...@rene-engelhard.de

Re: Bug#616093: libreoffice: on file open dialog the whole system gets halted

[Rene Engelhard]

Hi,

On Wed, Mar 02, 2011 at 03:55:37PM +0100, Rene Engelhard wrote:
  on the file open dialog libre office get stuck and the whole system gets 
  frozen
  no user interaction is possible any more
  mous is moving but every otner action is no more possible
  you cant even change to console via STRG+F1
  system is not more responding
  i user the nuveau driver for my x setup
 
 There's no nuveau driver. And what if you try sith an other driver?
 I thankfuzlly don't have a unstable system with nvidia hardware in it
 so I can't test either way.
 
 Besides that I don't see how file-open (which works in 99.9% of all users
 obviously, otherwise there would have been a report for this far earlier)
 is related to X or the system at large.
 
 I'd seriously bet on a local problem.

... or a bug in nouveau (and/or the kernel). I think is it works with
an other driver this bug simply should be reassigned there. And yes,
a nouveau/kernel bug *can* make the system freeze. This doesn't make it
a LibO bug, though.

CCing kernel and X teams.

FTR, from the initial report:

 Kernel: Linux 2.6.37-2-amd64 (SMP w/2 CPU cores)

Grüße/Regards,

René


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110302151233.gj4...@rene-engelhard.de

Re: Bug#616093: libreoffice: on file open dialog the whole system gets halted

[Rene Engelhard]

Hi,

On Wed, Mar 02, 2011 at 08:17:55PM +0100, Martin Künstner wrote:
 I opened a terminal with the syslog open and than started libreoffice
 and i didn't see anything abnormal there.

Of course not, LibO doesn't write to syslog, neither does X.

 Is there a log to post?

A log for a GUI app?

   There's no nuveau driver. And what if you try sith an other driver?
 i meant the nouveau driver for nvidia graphic cards

I know.

   I thankfuzlly don't have a unstable system with nvidia hardware in it
   so I can't test either way.
   
   Besides that I don't see how file-open (which works in 99.9% of all users
   obviously, otherwise there would have been a report for this far earlier)
   is related to X or the system at large.
   
   I'd seriously bet on a local problem.
 i don't think its a local problem, because last week all worked fine.

Aha. Last week unstable already had 3.3.1-1. (And before that it had rc2 which
is the same as 3.3.1 final upstream)

 the probleme came with new packages.

But then from X or nouveau or the kernel. Look in your aptitude or dpkg log 
please what
you upgraded.

  CCing kernel and X teams.

And why did you strip those CCs?

Grüße/Regards,

René


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110302194748.gl4...@rene-engelhard.de

Re: Bug#616093: libreoffice: on file open dialog the whole system gets halted

[Rene Engelhard]

Hi again,

On Wed, Mar 02, 2011 at 08:47:48PM +0100, Rene Engelhard wrote:
 On Wed, Mar 02, 2011 at 08:17:55PM +0100, Martin Künstner wrote:
  I opened a terminal with the syslog open and than started libreoffice
  and i didn't see anything abnormal there.
 
 Of course not, LibO doesn't write to syslog, neither does X.
 
  Is there a log to post?
 
 A log for a GUI app?

I forgot here:

Maybe it helps giving us the X log and/or kernel log, as it apparently only
happens on some systems (nouveau?)

   CCing kernel and X teams.
 
 And why did you strip those CCs?

Especially helpful for those teams.

Grüße/Regards,

René


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110302195804.gm4...@rene-engelhard.de

Re: Bug#599473: Bug is in NFS and not OOo

[Rene Engelhard]

reasisgn 599473 nfs-common
found 599473 1.2.2-1
severity 599473 important
tag 599473 - unreproducible
forcemerge 599473 600871
thanks

On Thu, Oct 21, 2010 at 12:52:02PM -0500, Peter Hombach wrote:
 After spending a lot of time in tracking this bug, it turned out to be  
 in nfs-common 1.2.2, the version in BPO. OpenOffice works fine after  

Which is also the version (though 1.2.2-4) which is in squeeze/sid...

 downgrade to nfs-common 1.1.1, the version in lenny. See also  
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600871

Ah, thanks, merging.

 Sorry for the confusion, but this was not that obvious, I think

Actually, it is. nfs with OOo is a constant source of disaster and
you should knew that you upgraded nfs-commonfrom bpo that you did that.

But thanks for confirming.

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101023162623.gd1...@rene-engelhard.de

Re: Processed: Re: Bug#577438: base: b43 driver won't work anymore

[Rene Engelhard]

reassign 577438 linux-image-2.6.32-3-amd64
thanks

Hi,

On Mon, Apr 12, 2010 at 10:09:14AM +, Debian Bug Tracking System wrote:
 Processing commands for cont...@bugs.debian.org:
 
  reassign 577438 b43-fwcutter
 Bug #577438 [base] base: b43 driver won't work anymore
 Bug reassigned from package 'base' to 'b43-fwcutter'.
  thanks
 Stopping processing here.

Why is a driver not working a fault of the package just there for extracting
the firmware?

From the upstream website:

--- snip ---
You are using the b43 driver from linux-2.6.25 or newer

Follow these instructions if you are using the b43 driver from linux-2.6.25 and 
newer or compat-wireless-2.6, or from any current GIT tree.

Use version 012 of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-012.tar.bz2
tar xjf b43-fwcutter-012.tar.bz2
cd b43-fwcutter-012
make
cd ..

Use version 4.150.10.5 of Broadcom's proprietary driver.
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR=/lib/firmware
wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2
tar xjf broadcom-wl-4.150.10.5.tar.bz2
cd broadcom-wl-4.150.10.5/driver
sudo ../../b43-fwcutter-012/b43-fwcutter -w $FIRMWARE_INSTALL_DIR 
wl_apsta_mimo.o

Note that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. 
The standard place where firmware is installed to is /lib/firmware. However 
some distributions put firmware in a different place. 
--- snip ---

We do, if you looked at what the package installed. Of course,
when you use a evice with a low-power PHY you need a newer one beginning
with 2.6.32 to ttbomk this is not true for the 4318.

--- snip ---
You are using the b43 driver with an LP-PHY card (e.g. BCM4312)

Follow these instructions if you are using the b43 driver from linux-2.6.32 and 
newer or compat-wireless-2.6, or from any current GIT tree, and have a device 
with a low-power PHY:

Use the current Git version of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..

Use version 4.174.64.19 of Broadcom's proprietary driver. (The tarball is 
mislabeled as 4.178.10.4, but it is actually 4.174.64.19.)
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR=/lib/firmware
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w $FIRMWARE_INSTALL_DIR wl_apsta.o

Note that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. 
The standard place where firmware is installed to is /lib/firmware. However 
some distributions put firmware in a different place. 
--- snip ---

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100412224804.gb25...@rene-engelhard.de

Bug#521083: b43-fwcutter: Lots of b43-phy0 ERROR: PHY transmission error

[Rene Engelhard]

Hi,

Julien Valroff wrote:
  Julien Valroff wrote:
   Using kernel 2.6.28 and latest b43-fwcutter from Lenny, I get a lot of
   b43-phy0 ERROR: PHY transmission error lines in my syslog.
  
  And it's a probably a driver problem. Already on the kernel buglist
  as #505252
 
 Thanks, I haven't been able to find it. However, this report doesn't
 mention the errors I see in my logs, hence *maybe* not the same issue.

Maybe. Maybe not. At oleast both talk about PHY transmission errors.

  That's the firmware you want to have. See the Homaepage. It says
  you want 4.150.10.5 for = 2.6.25, and 2.6.28 is = 2.6.25.
 
 And I see 410.2160 in my log, how am I supposed to know that it is the
 correct version?!

Because b43-fwcutter does per definiton get the right version, see the
Homepage: and install_bcm43xx_firmware.sh..

 Sorry, but I cannot understand why you react as you do. Can this be so

Id you would get those reports often without any ground, ans even unneeded
RC bugs - you would react like this, too.

Normally, b43-fwcutter would not even get the firmware. This is just
for convenience. I also could have just packaged b43-fwcutter and just
left all people with the burden to go to the homepage, read the instructions
and do it manually). Maybe I should have done that...

 hard to be a bit more patient with users reporting bugs, even not
 against the right package?

No. I do have for non-obvious things, but this is a obvious thing that
b43-fwcutter is not to blame for driver stuff when it gets the correct
firmware. (At least according to the Homepage)

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: 248AEB73
   `-   Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

reassign 505252 to linux-2.6, reassign 521083 to linux-2.6, forcibly merging 505252 521083

[Rene Engelhard]

reassign 505252 linux-2.6 
reassign 521083 linux-2.6 
forcemerge 505252 521083


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#508385: linux-image-2.6.27-1-amd64: autofs not working?

[Rene Engelhard]

Package: linux-image-2.6.27-1-amd64
Version: 2.6.27-1~experimental.1~snapshot.12488
Severity: important

Hi,

I wanted to try 2.6.27 because it has ath9k which supports by
wireless card and thus I can finally get rid of madwifi.

But I am using Steves solution for automounting a usb key with
the gpg (and in my case also ssh, vpn etc) keys: url

This does't work anymore in 2.6.27 since it first appeared on buildserver;
as we see in dmesg the USB key is detected but any access to /auto.pen/pen
does not cause it to be mounted.

Regards,

Rene

-- Package-specific info:
** Version:
Linux version 2.6.27-1-amd64 (Debian 2.6.27-1~experimental.1~snapshot.12488) 
([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 
4.1.2-23+1)) #1 SMP Wed Dec 10 04:03:39 UTC 2008

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.27-1-amd64 
root=UUID=5b6e0092-4404-407a-884f-c9d86f9182e8 ro resume=/dev/sda4

** Not tainted

** Kernel log:
[4.877008] sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00
[4.877037] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.877124]  sda: sda1 sda2 sda3 sda4 sda5
[4.954550] sd 0:0:1:0: [sda] Attached SCSI disk
[5.328009] PM: Starting manual resume from disk
[5.384839] kjournald starting.  Commit interval 5 seconds
[5.384932] EXT3-fs: mounted filesystem with ordered data mode.
[7.359034] udevd version 125 started
[8.347103] ACPI: Battery Slot [BAT0] (battery present)
[8.398591] agpgart-intel :00:00.0: Intel 945GM Chipset
[8.399661] agpgart-intel :00:00.0: detected 16124K stolen memory
[8.415225] agpgart-intel :00:00.0: AGP aperture is 256M @ 0x4000
[8.417765] input: Power Button (FF) as /class/input/input5
[8.481095] ACPI: Power Button (FF) [PWRF]
[8.481241] input: Lid Switch as /class/input/input6
[8.513160] ACPI: Lid Switch [LID0]
[8.513307] ACPI: AC Adapter [ADP1] (on-line)
[8.513429] input: Power Button (CM) as /class/input/input7
[8.577093] ACPI: Power Button (CM) [PWRB]
[8.577239] input: Sleep Button (CM) as /class/input/input8
[8.641095] ACPI: Sleep Button (CM) [SLPB]
[8.641589] input: Video Bus as /class/input/input9
[8.685080] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[9.022157] firmware: requesting isight.fw
[9.145663] Unable to load isight firmware
[9.145777] usbcore: registered new interface driver isight_firmware
[9.202120] appletouch: Geyser mode initialized.
[9.202251] input: appletouch as /class/input/input10
[9.245178] input: PC Speaker as /class/input/input11
[9.269900] intel_rng: FWH not detected
[9.271638] usbcore: registered new interface driver appletouch
[9.291258] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 
19
[9.291346] ACPI: I/O resource :00:1f.3 [0xefa0-0xefbf] conflicts with 
ACPI region SMBI [0xefa0-0xefaf]
[9.291436] ACPI: Device needs an ACPI driver
[9.334828] ath9k: 0.1
[9.334955] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[9.335037] ath9k :02:00.0: setting latency timer to 64
[9.463510] phy0: Selected rate control algorithm 'ath9k_rate_control'
[9.485049] pnp: the driver 'rtc_cmos' has been registered
[9.485140] rtc_cmos 00:08: rtc core: registered rtc_cmos as rtc0
[9.485248] rtc0: alarms up to one month, y3k, hpet irqs
[9.487524] rtc_cmos 00:08: driver attached
[9.536455] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[9.536607] iTCO_wdt: Found a ICH7-M TCO device (Version=2, TCOBASE=0x0460)
[9.536728] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[9.588973] phy0: Atheros 5416: mem=0xc2000452, irq=17
[9.614337] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 
22
[9.614448] HDA Intel :00:1b.0: setting latency timer to 64
[9.645423] hda_codec: STAC922x, Apple subsys_id=106b2200
[   10.792757] Adding 1048568k swap on /dev/sda4.  Priority:-1 extents:1 
across:1048568k
[   11.312725] EXT3 FS on sda3, internal journal
[   11.899400] loop: module loaded
[   12.110985] device-mapper: uevent: version 1.0.3
[   12.54] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: 
[EMAIL PROTECTED]
[   12.08] fuse init (API version 7.9)
[   13.209465] kjournald starting.  Commit interval 5 seconds
[   13.209943] EXT3 FS on sda5, internal journal
[   13.210065] EXT3-fs: mounted filesystem with ordered data mode.
[   14.342551] NET: Registered protocol family 15
[   16.904079] sky2 eth0: enabling interface
[   16.942707] Initializing XFRM netlink socket
[   18.571742] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
[   21.083096] NET: Registered protocol family 10
[   21.083335] lo: Disabled Privacy Extensions
[   22.029574] pnp: the driver 'parport_pc' has been registered
[   22.031271] lp: driver loaded but no devices found
[   22.063212] ppdev: user-space parallel port driver
[   

Bug#498381: /dev/vboxdrv is root:root 660 - should be roor:vboxdrv?

[Rene Engelhard]

Package: virtualbox-ose-modules-2.6.26-1-amd64
Version: 2.6.26+1.6.2-dfsg-3

Hi,

On a fresh lenny with virtualbox-ose and the modules just installed (both from 
the archive):

$ virtualbox
WARNING: /dev/vboxdrv not writable for some reason. If you recently added the
 current user to the vboxusers group then you have to logout and
 re-login to take the change effect.

 You will not be able to start VMs until this problem is fixed.

Hrm, but I did do that...
Re-check:

$ groups
users disk cdrom sudo plugdev vboxusers sbuild

Hmm, yes...

$ ls -l /dev/vboxdrv
crw-rw 1 root root 10, 60  9. Sep 14:46 /dev/vboxdrv

Ah.

Shouldn't that be root:vboxusers? Otherwise the hint to vboxusers might
not make that much sense :-)

Regards,

Rene

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#392065: known, fixed in 2.6.18.1

[Rene Engelhard]

tag 392065 + fixed-upstream
thanks

Hi,

known bug in 2.6.18 AFAIS. SHould be fixed in 2.6.18.1 according to
the bcm43xx developers.

Regards,

René


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#360708: marked as done (bcm43xx-modules-2.6.15-1-powerpc: bcm43* card is only capable to receive date)

[Rene Engelhard]

reopen 360708
thanks

err, of course this shouldn't have been closed. *sigh*

Debian Bug Tracking System wrote:
[...]
 From: Emil Nowak [EMAIL PROTECTED]
 To: Debian Bug Tracking System [EMAIL PROTECTED]
 Subject: bcm43xx-modules-2.6.15-1-powerpc: bcm43* card is only capable to 
 receive date
 X-Mailer: reportbug 3.19
 Date: Tue, 04 Apr 2006 11:59:17 +0200
 
 Package: bcm43xx-modules-2.6.15-1-powerpc
 Version: 20060212-3
 Severity: normal
 
 I have ibook G4 1,07Ghz, with airport card:
 0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g 
 Wireless LAN Controller (rev 02)
 
 I have installed bcm43xx modules for my kernel, and I used bcm43xx-fwcutter to
 extract firmware from my macos partition.
 
 After reading README from driver I made everything as it said: First I
 interface up, then iwscan, then iwconfig.
 
 After this It seems that my card is unable to send any data. I can't even 
 ping my
 AccesPoint. It seems that card is not sending anything.
 
 However If I run ethereal I can see all packets from my second laptop. 
 
 To make sure that I'm doing everything right with command-line tools I have
 installed netapplet package. Which gives simmilar tool to MacOS thing (you
 just click on it, and it selects network). But it doesn't help either.
 
 There are no useful information in dmesg. The only thing related to bcm43xx
 is:
 
 bcm43xx: TODO: Incomplete code in keymac_write() at 
 /home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060212/drivers/net/wireless/bcm43xx/bcm43xx_main.c:1265
 bcm43xx: TODO: Incomplete code in keymac_write() at 
 /home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060212/drivers/net/wireless/bcm43xx/bcm43xx_main.c:1265
 bcm43xx: TODO: Incomplete code in keymac_write() at 
 /home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060212/drivers/net/wireless/bcm43xx/bcm43xx_main.c:1265
 and it is reapeted many times.
 
 -- System Information:
 Debian Release: testing/unstable
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: powerpc (ppc)
[...]
 Date: Tue, 27 Jun 2006 15:40:51 +0200
 From: Rene Engelhard [EMAIL PROTECTED]
 To: [EMAIL PROTECTED], [EMAIL PROTECTED],
   [EMAIL PROTECTED], [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: fixed?
 User-Agent: Mutt/1.5.11+cvs20060403
 
 reassign 352208 linux-2.6
 reassign 360708 linux-2.6
 thanks
 
 Hi,
 
 are those bugs still present in Linux 2.6.17-1 (which contains bcm43xx
 now)? If not, please close.
 
 Regards,
 
 Rene



signature.asc
Description: Digital signature

Bug#353461: [2.6.16-rc3,powerpc] asm/highmem.h not found (ARCH=ppc vs. ARCH=powerpc)

[Rene Engelhard]

Package: linux-2.6
Severity: important
Version: 2.6.15+2.6.16-rc3-0experimental.0snapshot.5916

[ Sven tells me to file a bug here; although this package is unofficial
and not-in-Debian I'll do so. complain at him if you think like me... ]

Hi,

while trying to build bcm43xx against 2.6.16-rc3:

mkdir -p 
/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx/.tmp_versions
make -f scripts/Makefile.build 
obj=/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx
  gcc 
-Wp,-MD,/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx/.bcm43xx_main.o.d
  -nostdinc -isystem /usr/lib/gcc/powerpc-linux-gnu/4.0.3/include -D__KERNEL__ 
-Iinclude  -include include/linux/autoconf.h -Iarch/powerpc 
-Iarch/powerpc/include -DCONFIG_BCM43XX=1 -DCONFIG_BCM43XX_DMA=1 
-DCONFIG_BCM43XX_PIO=1 -DCONFIG_BCM43XX_DEBUG=1   -DMODULE -DKBUILD_STR(s)=#s 
-DKBUILD_BASENAME=KBUILD_STR(bcm43xx_main)  
-DKBUILD_MODNAME=KBUILD_STR(bcm43xx) -c -o 
/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx/.tmp_bcm43xx_main.o
 
/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx/bcm43xx_main.c
In file included from include/linux/skbuff.h:27,
 from include/linux/if_ether.h:110,
 from include/linux/netdevice.h:29,
 from include/linux/if_arp.h:26,
 from 
/home/rene/Debian/Pakete/bcm43xx/bcm43xx-20060215/drivers/net/wireless/bcm43xx/bcm43xx_main.c:34:
include/linux/highmem.h:12:25: error: asm/highmem.h: No such file or directory
[...]

neither linux/highmem.h nor asm/highmem.h are included by the driver but by
linux' headers.

there only is /usr/src/linux-headers-2.6.16-rc3/include/asm-ppc/highmem.h,
obviously not found when building with ARCH=powerpc (default) because of

a) lrwxrwxrwx 1 root root 11 2006-02-18 14:12 asm - asm-powerpc

and

b) asm-powerpc doesn't contain a highmem.h link. But asm-ppc does

ARCH=ppc doesn't work because there's no arch/ppc/Makefile anymore

Works with 2.6.15-1, didn't yet try building against normal upstream
2.6.16-rc3

Regards,

Rene

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


signature.asc
Description: Digital signature

Re: Instead of the amd64 GR: rudimentary amd64 support for sarge, need sponsor.

[Rene Engelhard]

Daniel Burrows wrote:
   gcc-3.4 is part of base, since it provides libgcc1 now.

and gcc-3.3 also because of libstdc++5...

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73
   `-   Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73
  


signature.asc
Description: Digital signature