Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

2017-08-03 Thread Patrick Matthäi 
severity #864642 normal
thanks


Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
> Control: tag -1 moreinfo
>
> Sven asked this, but forgot to add you to the recipients:
>
> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
>> Hi!
>>
>>> Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
> Note that this has been root-caused as a bug in the virtual device, not
> the driver.  (Though it would be nice if the driver could work around
> it.)
>
> Ben.

I can confirm, that the VMs do not crash anymore with vSphere 6.5 build
5969303 from 27.07.2017, that is why I lowered the severity.

But we have got still the issue with "Driver has suspect GRO
implementation, TCP performance may be compromised" and the fact, that
4.9.18-1 wasn't crashing and has not this message, while 4.9.30-1 was
crashing with the message.

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/




signature.asc
Description: OpenPGP digital signature

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

2017-07-13 Thread Patrick Matthäi 
forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201
thanks


Am 11.07.2017 um 10:24 schrieb Patrick Matthäi:
> found #864642 4.9.30-2+deb9u2
> thanks
>
> And it still crashes..
>
>
> Am 22.06.2017 um 14:58 schrieb Patrick Matthäi:
>> found #864642 4.9.30-2+deb9u1
>> thanks
>>
>>
>> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
>>> Package: src:linux
>>> Version: 4.9.30-1
>>> Severity: important
>>> File: linux
>>>
>>> Dear Maintainer,
>>>
>>> *** Reporter, please consider answering these questions, where
>>> appropriate ***
>>>
>>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
>>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
>>> "primary" interface this:
>>>
>>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
>>> be compromised.
>>>
>>> I can't see any performance impact. This happens on all our vSphere 6.0
>>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
>>> 350 G9 and so on).
>>>
>>> Why is this bug important? Because on one VM this also produces a kernel
>>> panic after some time (minutes or hours). I just could get the panic
>>> attached as screenshot. The only "big" difference between the crashing
>>> host and the others may be, that it is also running PM2, NPM, NodeJS and
>>> a NFS kernel server.
>>>
>>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
>>> ethtool -K ens192 gro off
>>> ethtool -K ens192 lro off
>>> .. it does not crash.
>>>
>>> Booting 4.9.18-1 and everything is completly fine ;)
>>>
>> The VM keeps on crashing after a few hours
>>

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

2017-07-11 Thread Patrick Matthäi 
found #864642 4.9.30-2+deb9u2
thanks

And it still crashes..


Am 22.06.2017 um 14:58 schrieb Patrick Matthäi:
> found #864642 4.9.30-2+deb9u1
> thanks
>
>
> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
>> Package: src:linux
>> Version: 4.9.30-1
>> Severity: important
>> File: linux
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where
>> appropriate ***
>>
>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
>> "primary" interface this:
>>
>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
>> be compromised.
>>
>> I can't see any performance impact. This happens on all our vSphere 6.0
>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
>> 350 G9 and so on).
>>
>> Why is this bug important? Because on one VM this also produces a kernel
>> panic after some time (minutes or hours). I just could get the panic
>> attached as screenshot. The only "big" difference between the crashing
>> host and the others may be, that it is also running PM2, NPM, NodeJS and
>> a NFS kernel server.
>>
>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
>> ethtool -K ens192 gro off
>> ethtool -K ens192 lro off
>> .. it does not crash.
>>
>> Booting 4.9.18-1 and everything is completly fine ;)
>>
> The VM keeps on crashing after a few hours
>

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

2017-06-22 Thread Patrick Matthäi 
found #864642 4.9.30-2+deb9u1
thanks


Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
> Package: src:linux
> Version: 4.9.30-1
> Severity: important
> File: linux
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
> appropriate ***
>
> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
> "primary" interface this:
>
> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
> be compromised.
>
> I can't see any performance impact. This happens on all our vSphere 6.0
> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
> 350 G9 and so on).
>
> Why is this bug important? Because on one VM this also produces a kernel
> panic after some time (minutes or hours). I just could get the panic
> attached as screenshot. The only "big" difference between the crashing
> host and the others may be, that it is also running PM2, NPM, NodeJS and
> a NFS kernel server.
>
> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
> ethtool -K ens192 gro off
> ethtool -K ens192 lro off
> .. it does not crash.
>
> Booting 4.9.18-1 and everything is completly fine ;)
>

The VM keeps on crashing after a few hours

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#854066: Severitiy set to non-rc

2017-02-05 Thread Patrick Matthäi 
Hi Ben,

first thanks for your good work for Debian especially for the Linux kernel!

But with #854066 I have to disagree / argue with you. You lowered the
severity to a non rc bug, but it is in my eyes. At the moment we have
got a project: Linux instead of Windows on Desktops for Developers.

So we switched many of our employe to Debian stretch (jessie would be
too old) and I have got an eye on the daily updates. With 4.9.x one
desktop (individual) does not boot at all, have to acc. it again. All
other desktopts do not wake up anymore (kernel panic?) if they fall in
sleep.

This is rc for me, if you think not, why? Many different hardware types
are affected
||

Bug#854066: linux-image-4.9.0-1-amd64: Several HP desktops do not wake up anymore since 4.9

2017-02-03 Thread Patrick Matthäi 
 cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.9.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.127
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-1-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.2

Versions of packages linux-image-4.9.0-1-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02~beta3-3
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-1-amd64 is related to:
ii  firmware-amd-graphics 20161130-2
pn  firmware-atheros  
ii  firmware-bnx2 20161130-2
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
ii  firmware-linux-nonfree20161130-2
ii  firmware-misc-nonfree 20161130-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20161130-2
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information


-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#844605: X11 segfault with AMD GPU since 4.8.x / Firmware issue

2016-11-17 Thread Patrick Matthäi 
 / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#815800: Activate support for WLAN USB N53 device

2016-02-24 Thread Patrick Matthäi 

Package: src:linux
Version: 4.4.2-3

Hello,

in jessie and sid the ASUS USB-N53 B1 (aka N600) adapter is not working 
=> no wlan device is detected.


On [0] I have found, that "rt2800usb - Include support for unknown (USB) 
devices (RT2800USB_UNKNOWN)" has to be activated, but the Debian 
configuration says:

# CONFIG_RT2800USB_UNKNOWN is not set

[0]: https://wikidevi.com/wiki/ASUS_USB-N53

--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#689429: vmxnet3 driver with package drops on ESXi 5.0

2012-10-02 Thread Patrick Matthäi 

Package: linux-2.6
Version: 2.6.32-46
Severity: important

Hello,

first, I can not check, if Wheezy is also affected.

Using ESXi 5.0 with Linux guests (in this case many amd64 Squeeze 
machines with three vmxnet3 adapter for each VM) could cause package 
drops, here especially on using UDP (name resolving). So I saw that some 
machines produced ~ 20 drops / day.

This has been fixed by VMware last week:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2032587

Could you please adopt this fix for Squeeze (maybe also Wheezy)?

Cheers


--
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/506af9a9.9040...@debian.org

Bug#657734: file build.save is not removed on purging package

2012-01-28 Thread Patrick Matthäi 
Package: linux-2.6
Version: 3.2.1-2
Severity: minor

Hello,

if you are building kernel modules on your own (or with dkms) the
symlink /lib/modules/version/build.save will be created with the
source /usr/src/version
If you purge all related version packages
(linux-{kbuild,image,headers}) the (now) broken symlink is not removed
and so on the whole folder /lib/modules/version will not be removed
(not empty dir).

So on purging the package (headers or image?) the build.save symlink
should be removed.

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



signature.asc
Description: OpenPGP digital signature

Bug#657737: Perl warnings (dpkg confmodule) on purging package

2012-01-28 Thread Patrick Matthäi 
Package: linux-2.6
Version: 3.2.1-2
Severity: minor

Hi,

this bug occurs here since a longer time. Everytime I purge a kernel
version, I get warnings from Perl on removing dkms modules.
I don't know if the fault is in dkms, debconf or linux-2.6, but here is
what I get:

# apt-get autoremove --purge linux-headers-3.1.0-1-common
linux-image-3.1.0-1-amd64 linux-kbuild-3.1
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Statusinformationen werden eingelesen... Fertig
Die folgenden Pakete werden ENTFERNT:
  libyajl1* linux-headers-3.1.0-1-amd64* linux-headers-3.1.0-1-common*
linux-image-3.1.0-1-amd64* linux-kbuild-3.1*
0 aktualisiert, 0 neu installiert, 5 zu entfernen und 0 nicht aktualisiert.
Nach dieser Operation werden 133 MB Plattenplatz freigegeben.
Möchten Sie fortfahren [J/n]? j
(Lese Datenbank ... 91849 Dateien und Verzeichnisse sind derzeit
installiert.)
Entfernen von libyajl1 ...
Löschen der Konfigurationsdateien von libyajl1 ...
Entfernen von linux-headers-3.1.0-1-amd64 ...
Entfernen von linux-headers-3.1.0-1-common ...
Entfernen von linux-image-3.1.0-1-amd64 ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 3.1.0-1-amd64
/boot/vmlinuz-3.1.0-1-amd64
dkms: removing: fglrx 12-1 (3.1.0-1-amd64) (x86_64)
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 3.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 9.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 11.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 18.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 20.
dkms: removing: virtualbox 4.1.8 (3.1.0-1-amd64) (x86_64)
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 22.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 28.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 30.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 37.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 38.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 45.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 46.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 53.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 54.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 61.
Use of uninitialized value $command in lc at
/usr/share/perl5/Debconf/ConfModule.pm line 123, GEN0 line 63.
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.1.0-1-amd64
/boot/vmlinuz-3.1.0-1-amd64
update-initramfs: Deleting /boot/initrd.img-3.1.0-1-amd64
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.1.0-1-amd64
/boot/vmlinuz-3.1.0-1-amd64
Generating grub.cfg ...
[..]

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



signature.asc
Description: OpenPGP digital signature

Bug#657734: file build.save is not removed on purging package

2012-01-28 Thread Patrick Matthäi 
Am 28.01.2012 16:14, schrieb Ben Hutchings:
 On Sat, 2012-01-28 at 14:09 +0100, Patrick Matthäi wrote:
 Package: linux-2.6
 Version: 3.2.1-2
 Severity: minor

 Hello,

 if you are building kernel modules on your own (or with dkms) the
 symlink /lib/modules/version/build.save will be created with the
 source /usr/src/version
 If you purge all related version packages
 (linux-{kbuild,image,headers}) the (now) broken symlink is not removed
 and so on the whole folder /lib/modules/version will not be removed
 (not empty dir).

 So on purging the package (headers or image?) the build.save symlink
 should be removed.
 
 If we don't create it, we shouldn't remove it.

Maybe it is created by depmod, dkms or whatever. But if you purge
linux-headers-version the symlink will become broken and it is not
required if you remove both (image and headers) packages. It just
prevents dpkg to remove /lib/modules/version :(

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



signature.asc
Description: OpenPGP digital signature

Re: [Pkg-fglrx-devel] Processed: Re: Processed: Re: Bug#642703: general: Scan lines appear in drop-down menus. LibreOffice also shows artifacts when starting. Might be something to do with the version

2011-09-26 Thread Patrick Matthäi 

reassign 642703 fglrx-driver
thanks

How often

It is NOT fglrx related

Am 26.09.2011 08:49, schrieb Debian Bug Tracking System:

Processing commands for cont...@bugs.debian.org:


unmerge 642703

Bug#642703: general: Scan lines appear in drop-down menus. LibreOffice also 
shows artifacts when starting. Might be something to do with the version of 
fglrx.
Bug is not marked as being merged with any others.


reassign 642703 fglrx-driver

Bug #642703 [linux-2.6] general: Scan lines appear in drop-down menus. 
LibreOffice also shows artifacts when starting. Might be something to do with 
the version of fglrx.
Bug reassigned from package 'linux-2.6' to 'fglrx-driver'.

thanks

Stopping processing here.

Please contact me if you need assistance.



--
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/4e802908.7010...@debian.org

Bug#628898: Pos. mis. firmware

2011-06-02 Thread Patrick Matthäi 
/Enclosure for module libahci
W: Possible missing firmware /lib/firmware/Management for module libahci
W: Possible missing firmware /lib/firmware/Message for module libahci
W: Possible missing firmware /lib/firmware/control for module libahci
W: Possible missing firmware /lib/firmware/(0 for module libahci
W: Possible missing firmware /lib/firmware/= for module libahci
W: Possible missing firmware /lib/firmware/off, for module libahci
W: Possible missing firmware /lib/firmware/1 for module libahci
W: Possible missing firmware /lib/firmware/= for module libahci
W: Possible missing firmware /lib/firmware/on) for module libahci
W: Possible missing firmware /lib/firmware/(int) for module libahci
W: Possible missing firmware /lib/firmware/marvell_enable:Marvell for
module ahci
W: Possible missing firmware /lib/firmware/SATA for module ahci
W: Possible missing firmware /lib/firmware/via for module ahci
W: Possible missing firmware /lib/firmware/AHCI for module ahci
W: Possible missing firmware /lib/firmware/(1 for module ahci
W: Possible missing firmware /lib/firmware/= for module ahci
W: Possible missing firmware /lib/firmware/enabled) for module ahci
W: Possible missing firmware /lib/firmware/(int) for module ahci
W: Possible missing firmware /lib/firmware/act:Disable for module thermal
W: Possible missing firmware /lib/firmware/or for module thermal
W: Possible missing firmware /lib/firmware/override for module thermal
W: Possible missing firmware /lib/firmware/all for module thermal
W: Possible missing firmware /lib/firmware/lowest for module thermal
W: Possible missing firmware /lib/firmware/active for module thermal
W: Possible missing firmware /lib/firmware/trip for module thermal
W: Possible missing firmware /lib/firmware/points. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
W: Possible missing firmware /lib/firmware/crt:Disable for module thermal
W: Possible missing firmware /lib/firmware/or for module thermal
W: Possible missing firmware /lib/firmware/lower for module thermal
W: Possible missing firmware /lib/firmware/all for module thermal
W: Possible missing firmware /lib/firmware/critical for module thermal
W: Possible missing firmware /lib/firmware/trip for module thermal
W: Possible missing firmware /lib/firmware/points. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
W: Possible missing firmware /lib/firmware/tzp:Thermal for module thermal
W: Possible missing firmware /lib/firmware/zone for module thermal
W: Possible missing firmware /lib/firmware/polling for module thermal
W: Possible missing firmware /lib/firmware/frequency, for module thermal
W: Possible missing firmware /lib/firmware/in for module thermal
W: Possible missing firmware /lib/firmware/1/10 for module thermal
W: Possible missing firmware /lib/firmware/seconds. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
W: Possible missing firmware /lib/firmware/nocrt:Set for module thermal
W: Possible missing firmware /lib/firmware/to for module thermal
W: Possible missing firmware /lib/firmware/take for module thermal
W: Possible missing firmware /lib/firmware/no for module thermal
W: Possible missing firmware /lib/firmware/action for module thermal
W: Possible missing firmware /lib/firmware/upon for module thermal
W: Possible missing firmware /lib/firmware/ACPI for module thermal
W: Possible missing firmware /lib/firmware/thermal for module thermal
W: Possible missing firmware /lib/firmware/zone for module thermal
W: Possible missing firmware /lib/firmware/critical for module thermal
W: Possible missing firmware /lib/firmware/trips for module thermal
W: Possible missing firmware /lib/firmware/points. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
W: Possible missing firmware /lib/firmware/off:Set for module thermal
W: Possible missing firmware /lib/firmware/to for module thermal
W: Possible missing firmware /lib/firmware/disable for module thermal
W: Possible missing firmware /lib/firmware/ACPI for module thermal
W: Possible missing firmware /lib/firmware/thermal for module thermal
W: Possible missing firmware /lib/firmware/support. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
W: Possible missing firmware /lib/firmware/psv:Disable for module thermal
W: Possible missing firmware /lib/firmware/or for module thermal
W: Possible missing firmware /lib/firmware/override for module thermal
W: Possible missing firmware /lib/firmware/all for module thermal
W: Possible missing firmware /lib/firmware/passive for module thermal
W: Possible missing firmware /lib/firmware/trip for module thermal
W: Possible missing firmware /lib/firmware/points. for module thermal
W: Possible missing firmware /lib/firmware/(int) for module thermal
root@gnu:~#

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth

Bug#611574: linux-image-2.6.37-trunk-amd64: 2.6.37 is quite slow at copying data (Desktop)

2011-01-30 Thread Patrick Matthäi 
Package: linux-2.6
Version: 2.6.37-1~experimental.1
Severity: normal
Tags: experimental

Hi,

I don't know what happened, but every Kernel since lenny was much faster :(
For example I am copying data from one ntfs-3g device to one ext3 harddisk, this
results in an unuseable system (also the transferspeed itself is slowed down).
Starting firefox took 5 minutes, opening an existing chat window from pidgin
took three minutes and I also have got bad results at copying data from one ext3
harddisk to another ext3 one :(

Don't know what usefull information I have to add to this report.. Maybe you
have got some ideas :)

And no, it is *not* fglrx related, the load also increase much more without any
fglrx/radeon/X11/whatever than with 2.6.36.

-- Package-specific info:
** Version:
Linux version 2.6.37-trunk-amd64 (Debian 2.6.37-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Thu Jan 6 
14:13:28 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.37-trunk-amd64 
root=UUID=8ce883ce-13bc-4d1e-aff8-d5efc1e40077 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[  862.856641] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  863.034401] usb 1-6: USB disconnect, address 19
[  886.560049] usb 1-6: new high speed USB device using ehci_hcd and address 20
[  886.692792] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[  886.692801] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  886.864965] usb 1-6: USB disconnect, address 20
[  910.388091] usb 1-6: new high speed USB device using ehci_hcd and address 21
[  910.520556] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[  910.520565] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  910.700822] usb 1-6: USB disconnect, address 21
[  934.224035] usb 1-6: new high speed USB device using ehci_hcd and address 22
[  934.357229] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[  934.357239] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  934.531016] usb 1-6: USB disconnect, address 22
[  958.056025] usb 1-6: new high speed USB device using ehci_hcd and address 23
[  958.189000] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[  958.189009] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  958.373303] usb 1-6: USB disconnect, address 23
[  981.896053] usb 1-6: new high speed USB device using ehci_hcd and address 24
[  982.029159] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[  982.029163] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  982.211574] usb 1-6: USB disconnect, address 24
[ 1005.736086] usb 1-6: new high speed USB device using ehci_hcd and address 25
[ 1005.868535] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1005.868538] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1006.050694] usb 1-6: USB disconnect, address 25
[ 1029.576050] usb 1-6: new high speed USB device using ehci_hcd and address 26
[ 1029.709134] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1029.709143] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1029.887076] usb 1-6: USB disconnect, address 26
[ 1053.412031] usb 1-6: new high speed USB device using ehci_hcd and address 27
[ 1053.545086] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1053.545095] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1053.715632] usb 1-6: USB disconnect, address 27
[ 1077.240036] usb 1-6: new high speed USB device using ehci_hcd and address 28
[ 1077.373482] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1077.373491] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1077.552412] usb 1-6: USB disconnect, address 28
[ 1101.076072] usb 1-6: new high speed USB device using ehci_hcd and address 29
[ 1101.208607] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1101.208616] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1101.382797] usb 1-6: USB disconnect, address 29
[ 1124.908029] usb 1-6: new high speed USB device using ehci_hcd and address 30
[ 1125.041120] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1125.041124] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1125.222172] usb 1-6: USB disconnect, address 30
[ 1148.744030] usb 1-6: new high speed USB device using ehci_hcd and address 31
[ 1148.877092] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1148.877097] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1149.060914] usb 1-6: USB disconnect, address 31
[ 1172.584045] usb 1-6: new high speed USB device using ehci_hcd and address 32
[ 1172.716683] usb 1-6: New USB device found, idVendor=13fd, idProduct=160e
[ 1172.716689] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1172.898094] usb 1-6: USB

Bug#586029: Fwd: Re: Bug#586029: udev: 3ware 8006 RAID controller gets a new controller, ID on each reboot

2011-01-14 Thread Patrick Matthäi 


Hello,

looks like a real (fixed) bug:

1) in the past (etch times) it does not happen
2) With squeeze and some more kernel versions + the issue occurs
3) Now - with 2.6.37 (maybe also with 2.6.36, just notified it now) it
isn't changing on each reboot again and again



--
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/4d3083aa.4070...@debian.org

Bug#590090: linux-image-2.6.35-rc5-686: HP Compaq 6715s with radeon KMS does not shutdown anymore

2010-07-23 Thread Patrick Matthäi 
Package: linux-2.6
Version: 2.6.35~rc5-1~experimental.1
Severity: important


Hello,

since I have updated from 2.6.34 from experimental to 2.6.35-rc5, my notebook 
does not shutdown anymore.
I am using KDE4 (and so on kdm). If I choose shutdown, kdm exits and then I can 
not do anything.
Switching to another console etc does not work and there is no shutdown :(

I am using the radeon driver with KMS (per default) enabled.


-- Package-specific info:
** Version:
Linux version 2.6.35-rc5-686 (Debian 2.6.35~rc5-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-6) ) #1 SMP Tue Jul 13 
16:16:00 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc5-686 
root=UUID=fc14f80e-bb68-45b3-b227-b76e7d9349c1 ro quiet

** Not tainted

** Kernel log:
[9.399137] ACPI: AC Adapter [C1EB] (off-line)
[9.488311] ACPI: Battery Slot [C1ED] (battery present)
[9.488512] ACPI: Battery Slot [C1EC] (battery absent)
[9.525607] ACPI: WMI: Mapper loaded
[9.913968] k8temp :00:18.3: Temperature readouts might be wrong - check 
erratum #141
[9.971567] acpi device:01: registered as cooling_device6
[9.972392] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/LNXVIDEO:00/input/input4
[9.972450] ACPI: Video Device [C08D] (multi-head: yes  rom: no  post: no)
[9.991457] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x2580b1, caps: 
0xa04793/0x30/0x0
[9.991463] serio: Synaptics pass-through port at isa0060/serio4/input0
[   10.031984] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input5
[   10.104149] piix4_smbus :00:14.0: SMBus Host Controller at 0x8200, 
revision 0
[   10.363810] cfg80211: Calling CRDA to update world regulatory domain
[   10.371204] input: HP WMI hotkeys as /devices/virtual/input/input6
[   10.817300] b43-phy0: Broadcom 4311 WLAN found (core revision 13)
[   11.355314] phy0: Selected rate control algorithm 'minstrel'
[   11.356004] Registered led device: b43-phy0::tx
[   11.356030] Registered led device: b43-phy0::rx
[   11.356052] Registered led device: b43-phy0::radio
[   11.356122] Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
[   11.573387] HDA Intel :00:14.2: power state changed by ACPI to D0
[   11.573433] HDA Intel :00:14.2: power state changed by ACPI to D0
[   11.573445] HDA Intel :00:14.2: PCI INT A - GSI 16 (level, low) - IRQ 
16
[   11.632993] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input7
[   13.204665] Adding 971928k swap on /dev/sda2.  Priority:-1 extents:1 
across:971928k 
[   13.462621] EXT3-fs (sda3): using internal journal
[   13.625575] loop: module loaded
[   14.981640] fuse init (API version 7.14)
[   16.443936] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input8
[   18.200398] apm: BIOS not found.
[   19.676954] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology 
TL-56 (2 cpu cores) (version 2.20.00)
[   19.677023] powernow-k8:0 : fid 0xa (1800 MHz), vid 0x12
[   19.677026] powernow-k8:1 : fid 0x8 (1600 MHz), vid 0x14
[   19.677029] powernow-k8:2 : fid 0x0 (800 MHz), vid 0x1e
[   20.173039] Clocksource tsc unstable (delta = -178542988 ns)
[   22.256921] tg3 :10:00.0: irq 43 for MSI/MSI-X
[   22.287685] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   22.764068] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[   22.850434] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   25.798950] pci :01:05.0: PCI INT B - GSI 19 (level, low) - IRQ 19
[   26.049163] [drm] Initialized drm 1.1.0 20060810
[   26.342856] [drm] radeon kernel modesetting enabled.
[   26.351239] [drm] initializing kernel modesetting (RS690 0x1002:0x791F).
[   26.351447] [drm] register mmio base: 0xD020
[   26.351453] [drm] register mmio size: 65536
[   26.351800] ATOM BIOS: ATI
[   26.351861] radeon :01:05.0: VRAM: 128M 0x7800 - 0x7FFF (128M 
used)
[   26.351869] radeon :01:05.0: GTT: 512M 0x8000 - 0x9FFF
[   26.352058] [drm] radeon: irq initialized.
[   26.352445] [drm] Detected VRAM RAM=128M, BAR=128M
[   26.352455] [drm] RAM width 128bits DDR
[   26.353256] [TTM] Zone  kernel: Available graphics memory: 443796 kiB.
[   26.353263] [TTM] Zone highmem: Available graphics memory: 972024 kiB.
[   26.353269] [TTM] Initializing pool allocator.
[   26.353320] [drm] radeon: 128M of VRAM memory ready
[   26.353326] [drm] radeon: 512M of GTT memory ready.
[   26.353376] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   26.371089] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[   26.391224] [drm] Loading RS690/RS740 Microcode
[   26.472365] [drm] radeon: ring at 0x8000
[   26.472395] [drm] ring test succeeded in 1 usecs
[   26.472751] [drm] radeon: ib pool ready.
[   26.472913] [drm] ib test succeeded in 0 usecs
[   26.473034] [drm] Default TV standard: NTSC
[   26.473322] [drm] Default TV standard: NTSC
[   26.473406] [drm] Radeon Display

Bug#584948: linux-image-2.6.34-1-amd64: Incompatible build without ABI bump

2010-06-07 Thread Patrick Matthäi 
Package: linux-2.6
Version: 2.6.34-1~experimental.2
Severity: important

As you can see in dmesg, vboxdrv and fglrx could not be loaded, because the ABI 
is incompatible with .1

-- Package-specific info:
** Version:
Linux version 2.6.34-1-amd64 (Debian 2.6.34-1~experimental.2) 
(b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-4) ) #1 SMP Sun Jun 6 
22:29:25 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.34-1-amd64 
root=UUID=8ce883ce-13bc-4d1e-aff8-d5efc1e40077 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[2.312353] generic-usb 0003:045E:00DD.0002: input,hidraw1: USB HID v1.11 
Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input0
[2.330164] input: Microsoft Comfort Curve Keyboard 2000 as 
/devices/pci:00/:00:02.0/usb2/2-2/2-2:1.1/input/input2
[2.330200] generic-usb 0003:045E:00DD.0003: input,hidraw2: USB HID v1.11 
Device [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input1
[7.076014] scsi2 : 3ware Storage Controller
[7.076068] 3w-: scsi2: Found a 3ware Storage Controller at 0xdc00, IRQ: 
19.
[7.076381] 8139cp :01:0a.0: This (id 10ec:8139 rev 10) is not an 8139C+ 
compatible chip, use 8139too
[7.076461] scsi 2:0:0:0: Direct-Access 3wareLogical Disk 0   1.2  
PQ: 0 ANSI: 0
[7.078466] 8139too: 8139too Fast Ethernet driver 0.9.28
[7.078963] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 18
[7.078969]   alloc irq_desc for 18 on node 0
[7.078971]   alloc kstat_irqs on node 0
[7.078981] 8139too :01:0a.0: PCI INT A - Link[LNKC] - GSI 18 (level, 
low) - IRQ 18
[7.079152] sd 2:0:0:0: Attached scsi generic sg5 type 0
[7.079915] 8139too :01:0a.0: eth0: RealTek RTL8139 at 
0xc967e800, 00:02:2a:df:47:10, IRQ 18
[7.080374] sd 2:0:0:0: [sdd] 586112656 512-byte logical blocks: (300 GB/279 
GiB)
[7.080386] sd 2:0:0:0: [sdd] Write Protect is off
[7.080388] sd 2:0:0:0: [sdd] Mode Sense: 00 00 00 00
[7.080690] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: disabled, 
supports DPO and FUA
[7.081666]  sdd: sdd1
[7.091252] sd 2:0:0:0: [sdd] Attached SCSI disk
[7.241709] PM: Starting manual resume from disk
[7.241713] PM: Resume from partition 8:2
[7.241714] PM: Checking hibernation image.
[7.241863] PM: Error -22 checking image file
[7.241864] PM: Resume from disk failed.
[7.271847] kjournald starting.  Commit interval 5 seconds
[7.271855] EXT3-fs (sda4): mounted filesystem with ordered data mode
[8.775766] udev: starting version 157
[9.155858] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[9.155869] ACPI: Power Button [PWRB]
[9.155988] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[9.155992] ACPI: Power Button [PWRF]
[9.242845] input: PC Speaker as /devices/platform/pcspkr/input/input5
[9.333492] k8temp :00:18.3: Temperature readouts might be wrong - check 
erratum #141
[9.457889] i2c i2c-0: nForce2 SMBus adapter at 0x2d00
[9.457924] i2c i2c-1: nForce2 SMBus adapter at 0x2e00
[9.573869] EDAC MC: Ver: 2.1.0 Jun  6 2010
[9.591603] EDAC amd64_edac:  Ver: 3.3.0 Jun  6 2010
[9.591853] EDAC amd64: This node reports that Memory ECC is currently 
disabled, set F3x44[22] (:00:18.3).
[9.591861] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[9.591862]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[9.591863]  (Note that use of the override may cause unknown side effects.)
[9.592002] amd64_edac: probe of :00:18.2 failed with error -22
[   10.057646] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[   10.057651]   alloc irq_desc for 20 on node 0
[   10.057653]   alloc kstat_irqs on node 0
[   10.057664] HDA Intel :00:07.0: PCI INT B - Link[LAZA] - GSI 20 
(level, low) - IRQ 20
[   10.057667] hda_intel: Disable MSI for Nvidia chipset
[   10.057763] HDA Intel :00:07.0: setting latency timer to 64
[   10.584016] hda_codec: ALC888: BIOS auto-probing.
[   10.824087] input: HDA Digital PCBeep as 
/devices/pci:00/:00:07.0/input/input6
[   11.136496] ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 17
[   11.136501]   alloc irq_desc for 17 on node 0
[   11.136503]   alloc kstat_irqs on node 0
[   11.136514] HDA Intel :04:00.1: PCI INT B - Link[LNEA] - GSI 17 
(level, low) - IRQ 17
[   11.136572]   alloc irq_desc for 29 on node 0
[   11.136574]   alloc kstat_irqs on node 0
[   11.136582] HDA Intel :04:00.1: irq 29 for MSI/MSI-X
[   11.136606] HDA Intel :04:00.1: setting latency timer to 64
[   15.320120] Adding 1951892k swap on /dev/sda2.  Priority:-1 extents:1 
across:1951892k 
[   15.629879] EXT3-fs (sda4): using internal journal
[   15.822259] loop: module loaded
[   15.841596] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 
5200+ processors (2 cpu cores)

Bug#572381: linux-base: Error at setting debconf question

2010-03-03 Thread Patrick Matthäi 
Package: linux-base
Version: 2.6.33-1~experimental.1
Severity: grave
Justification: renders package unusable

Hello,

linux-base fails to install here:

gnu:~# LC_ALL=C apt-get install linux-image-2.6.33-2-686
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-image-2.6.33-2-686 is already the newest version.
The following packages were automatically installed and are no longer required:
libxxf86misc1
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up linux-base (2.6.33-1~experimental.1) ...
Error setting debconf question linux-base/disk-id-convert-auto: 
linux-base/disk-id-convert-auto doesn't exist at 
/var/lib/dpkg/info/linux-base.postinst line 1384, STDIN line 2.
dpkg: error processing linux-base (--configure):
subprocess installed post-installation script returned error exit status 9
dpkg: dependency problems prevent configuration of linux-image-2.6.33-2-686:
linux-image-2.6.33-2-686 depends on linux-base (= 2.6.33); however:
Package linux-base is not configured yet.
dpkg: error processing linux-image-2.6.33-2-686 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-base
linux-image-2.6.33-2-686
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100303204358.4069.3351.report...@exez

Bug#562287: kdm/X crashs on first login

2009-12-24 Thread Patrick Matthäi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: linux-2.6
Version: 2.6.32-2
Severity: important

Hello,

I have got the following setup:

* two Debian Sid machines
* One i686 and one amd64
* amd64 with fglrx and i686 with the free radeon driver (dri enabled)
* KDE4 with kdm

since Kernel 2.6.32-trunk, the first (successful) login with kdm fails.
X/kdm restarts, the second login is fine.

I can not find any crash logs in syslog, dmesg, Xorg.log, kdm.log and so
on..
If I start my PC with 2.6.31, everything is fine again.

- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkszQUAACgkQ2XA5inpabMedeQCdEVEwg5zj2thgdxjP4Cdu/4xw
jXkAnA9i+SbNl/uVb1Y5hF7bSksUpx58
=LcRZ
-END PGP SIGNATURE-



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

Bug#562287: Bug#562026: kdm cannot open ConsoleKit session on first login attempt

2009-12-24 Thread Patrick Matthäi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sergiy Yegorov schrieb:
 Hi.
 Really, it causes only with 2.6.32 kernel. So this report is wrong.
 Sorry, my mistake.
 
 Thu 24 Dec 2009 12:32:03 Patrick Matthäi wrote:
 Hi,

 I have just reported this issue against the linux-2.6 package (no bug
 number, yet).

 I have got the same on all my machines, but only with kernel 2.6.32.

 

This is the bugnumber: #562287

- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkszbQMACgkQ2XA5inpabMeDEQCfXLRNGy6vKZbdbHWHdMRjcB4U
BrwAmwTHfRyOhCnqAkRK2n1hs05FLbBT
=yxtH
-END PGP SIGNATURE-



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

Re: [Pkg-fglrx-devel] Auto-building out-of-tree kernel modules

2009-10-17 Thread Patrick Matthäi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Hutchings schrieb:
 Due to bug #517130, linux-modules-extra-2.6 must be removed.
 linux-modules-nonfree-2.6 does not suffer the same licence compliance
 issue, but it is extremely fragile since proprietary drivers are often
 not updated for new kernel versions.  The kernel team will shortly be
 requesting its removal as well.
 
 If you want to continue having modules auto-built, we recommend that you
 consider integrating with DKMS.  You can trigger a build on installation
 or upgrade of the module source.  The dkms package then automatically
 rebuilds installed module sources when a new kernel version is
 installed.
 
 Why DKMS and not module-assistant?  Your packages presumably already
 work with m-a, but m-a doesn't automatically rebuild modules on upgrade.
 Also, DKMS is supported by other distributions, so many out-of-tree
 module sources already include the necessary configuration file.

Sorry, but I do not see any decision how to handle it, yet.

- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkrZ9nYACgkQ2XA5inpabMexxgCeJDQm+5Qkd6Wy5wbyMnKk2Vru
HDAAnjD+iKuYEe00wF8YE/ybXV1NifIo
=FfHT
-END PGP SIGNATURE-


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

Re: [Pkg-fglrx-devel] Auto-building out-of-tree kernel modules

2009-10-17 Thread Patrick Matthäi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Hutchings schrieb:
 On Sat, 2009-10-17 at 19:47 +0200, Patrick Matthäi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Ben Hutchings schrieb:
 Wasting time and bandwidth (fetching linux-headers etc)? Great...
 Building obscure modules for every kernel flavour on Debian's own
 auto-builders is also a waste, especially when just one broken module
 breaks the whole conglomeration package.
 It is a big difference if our auto-builders build them e.g. 12 times for
 every architecture or if they have to be built on every end-consumer PC,
 which are e.g. one million pcs. All those senseless lost of energy and
 performance..
 
 Please don't exaggerate.
 
 udd= select sum(insts) from popcon where package like 'fglrx-modules-%';
  sum 
 -
  892

I do not speak only for fglrx, also one million was choosen by the fair
random number generator.

 
 It is also not a good idea to switch to dkms, now where nothing is
 decided or it may end like with ia32-apt-get with many wasted developer
 ressources.
 
 What do you mean, 'nothing is decided'.  The kernel team made a
 decision, after consultation with representatives of the FTP team and
 the release team.

Where is the reference? This is not included in the bugreport.

- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkraNx8ACgkQ2XA5inpabMfSxwCfa4KiRcs5Tt4PGqHg0xoVk0UL
f4oAoI+AxT3dpAn0y396G54HL6MPsQ8u
=pnpg
-END PGP SIGNATURE-


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

Re: [Pkg-fglrx-devel] Auto-building out-of-tree kernel modules

2009-10-17 Thread Patrick Matthäi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Hutchings schrieb:
 On Sat, 2009-10-17 at 23:29 +0200, Patrick Matthäi wrote:
 [...]
 It is also not a good idea to switch to dkms, now where nothing is
 decided or it may end like with ia32-apt-get with many wasted developer
 ressources.
 What do you mean, 'nothing is decided'.  The kernel team made a
 decision, after consultation with representatives of the FTP team and
 the release team.
 Where is the reference? This is not included in the bugreport.
 
 Do you not believe I can speak for the kernel team?
 
 The minutes for the meeting where we decided this are in
 http://lists.debian.org/debian-kernel/2009/10/msg00613.html.  A
 summary of this will be posted to d-d-a shortly.

Okay thanks for clarification.

- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkraPqEACgkQ2XA5inpabMdGigCfSWfFkqid2UE9Oqciy1N4ro/x
WFAAoKSndcX1JB/3FvQ0cAAC6shft5UA
=TKgX
-END PGP SIGNATURE-


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

Bug#451166: HP Compaq 6715s won't halt

2007-11-13 Thread Patrick Matthäi 
2.6.1-6GNU C Library: Shared 
libraries [i


-- debconf information:
 shared/kernel-image/really-run-bootloader: true
 linux-image-2.6.22-3-k7/preinst/failed-to-move-modules-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/postinst/depmod-error-2.6.22-3-k7: false
 linux-image-2.6.22-3-k7/preinst/lilo-has-ramdisk:
 linux-image-2.6.22-3-k7/prerm/removing-running-kernel-2.6.22-3-k7: true
* linux-image-2.6.22-3-k7/preinst/already-running-this-2.6.22-3-k7:
 
linux-image-2.6.22-3-k7/prerm/would-invalidate-boot-loader-2.6.22-3-k7: true

 linux-image-2.6.22-3-k7/postinst/old-system-map-link-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/postinst/old-dir-initrd-link-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/postinst/kimage-is-a-directory:
 linux-image-2.6.22-3-k7/preinst/overwriting-modules-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/postinst/create-kimage-link-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/preinst/initrd-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/preinst/abort-install-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/preinst/lilo-initrd-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/postinst/depmod-error-initrd-2.6.22-3-k7: false
 linux-image-2.6.22-3-k7/postinst/old-initrd-link-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/preinst/elilo-initrd-2.6.22-3-k7: true
 linux-image-2.6.22-3-k7/postinst/bootloader-error-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/preinst/abort-overwrite-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/postinst/bootloader-test-error-2.6.22-3-k7:
 linux-image-2.6.22-3-k7/preinst/bootloader-initrd-2.6.22-3-k7: true

--
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi

E-Mail: [EMAIL PROTECTED]
Homepage: http://www.Linux-Dev.org/

Bug#412132:

2007-05-13 Thread Patrick Matthäi 

Hi,

could anyone tell me the status of this bug?

Regards,
   Patrick Matthäi

Bug#412132:

2007-03-19 Thread Patrick Matthäi 

Hi,

I'm sorry but when will the update with the fix available (ca ~).

Regards,
Patrick Matthäi

Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Patrick Matthäi 

Package: linux-image-2.6.18-4-vserver-amd64
Version: 2.6.18.dfsg.1-9
Severity: serious

Hello,

I think I've found a serious bug in the vserver image for amd64.
We're running a daemon, which is logging the traffic of all 
hostmachines. Now I've found a very big mistake in the 
/proc/virtual/id/cacct interface.


The daemon gets the informations of this cacct interface and will calc 
the caused traffic, here's the debug of my daemon:


|Fri Feb 23 15:42:01 2007 - cacct: 1472700147 o.cacct 1472517504 logged: 1495189052 now: 1495371695 method: 1 


Fri Feb 23 16:00:01 2007 - cacct: 18446744072641133818 o.cacct 3222831651 
logged: 3178567909 now: 18446744072596870076 method: 1

|The cacct variable is the value of all incoming / outcoming IPv4 and 
IPv6 traffic in bytes.
This debug would mean, that one customer has caused traffic more as 100 
TB in 20 minutes ( and that only with one ventrilo server! ).
First I thought, it's a bug in my daemon software, but that wasn't the 
problem, how this information will show:


|hostname:~/control# cat /proc/virtual/2/cacct
UNSPEC:0/0 0/0 0/0 

UNIX: 305586/28642976 267311/28642976  1/30 

INET:9058790/1149688302  9889025/18446744071736090069  47323/18446744072430740975 

INET6: 0/0 0/0 0/0 

OTHER: 0/0 0/0 0/0 


forks:  0|
|
|It seems as the kernel misscalced or overflowed after a cacct value 
over |1472700147.


It's the first and only example of this bug, because this is the first 
customer, with such a lot traffic.


Regards,
Patrick Matthäi
|

Bug#412132:

2007-02-23 Thread Patrick Matthäi 

Hi again,

I'm very sorry, I pasted the wrong debug lines:

Fri Feb 23 15:42:01 2007 - cacct: 39375996 o.cacct 39375996 logged: 
39375996 now: 39375996 method: 1
Fri Feb 23 16:00:01 2007 - cacct: 18446744072641133818 o.cacct 
3222831651 logged: 3178567909 now: 18446744072596870076 method: 1


This would be the right one, which would mean, that this error will 
cause maybe about 39375996 bytes ( ~ 4gb ).


Regards,
Patrick Matthäi

Bug#412132: Patch

2007-02-23 Thread Patrick Matthäi 

And hello again ;)

I talked about that problem with the people of linux-vserver.org. It's a 
known upstream bug, which is already fixed.


Here's the patch:
http://people.linux-vserver.org/~dhozac/p/k/delta-longatomic-fix01.diff

The counter overflows like I said at 4 GB ( like on a 32 bit system ).

I hope you can apply this patch fast, it's very important for us.

Thanks and regards,
Patrick Matthäi

Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Patrick Matthäi 

Hi,

I'm sorry, normaly it shouldn't be a very important bug, but please 
think about these ones, who have to log the caused traffic, that's very 
terrible. So could you please add it to the next upload?


Regards, Patrick Matthäi


Bastian Blank schrieb:

severity 412132 important
user debian-kernel@lists.debian.org
usertag dkt-waiting-etch-update
tags 412132 +patch
thanks

On Fri, Feb 23, 2007 at 11:19:57PM +0100, Patrick Matthäi wrote:
  

I think I've found a serious bug in the vserver image for amd64.
We're running a daemon, which is logging the traffic of all 
hostmachines. Now I've found a very big mistake in the 
/proc/virtual/id/cacct interface.



Known. Can be fixed with the first stable update, not security relevant.

Available patch, needs to be fixed to avoid abi change (use atomic_t and crop
at the printf):

diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h
2007-01-11 18:10:53.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h 
2007-02-02 18:17:38.0 +0100
@@ -6,8 +6,8 @@
 
 
 struct _vx_sock_acc {

-   atomic_t count;
-   atomic_t total;
+   atomic_long_t count;
+   atomic_long_t total;
 };
 
 /* context sub struct */

@@ -30,9 +30,9 @@ static inline void __dump_vx_cacct(struc
 
 		printk(\t [%d] =, i);

for (j=0; j3; j++) {
-   printk( [%d] = %8d, %8d, j,
-   atomic_read(ptr[j].count),
-   atomic_read(ptr[j].total));
+   printk( [%d] = %8ld, %8ld, j,
+   atomic_long_read(ptr[j].count),
+   atomic_long_read(ptr[j].total));
}
printk(\n);
}
diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h2007-01-11 
18:10:52.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h 
2007-02-02 18:18:14.0 +0100
@@ -38,8 +38,8 @@ static inline void __vx_acc_sock(struct 
 	if (vxi) {

int type = vx_sock_type(family);
 
-		atomic_inc(vxi-cacct.sock[type][pos].count);

-   atomic_add(size, vxi-cacct.sock[type][pos].total);
+   atomic_long_inc(vxi-cacct.sock[type][pos].count);
+   atomic_long_add(size, vxi-cacct.sock[type][pos].total);
}
 }
 
Bastian

Bug#383447: Fixed

2006-10-17 Thread Patrick Matthäi 

Hello,

Seems as this bug is since the 2.6.18 kernel fixed.
Bye and thanks.


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

Bug#386823: Add modul kqemu

2006-09-10 Thread Patrick Matthäi 

Package: linux-image-2.6.17-2-k7
Version: 2.6.17-8

Hello,
Could you maybe add the kernelmodul 'kqemu' into the current 
linux-image? In my opinion, it were a good decision, because qemu is in 
the repository and with that modul, it will run better.

Or maybe as a seperate package.

Patrick.


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

Bug#383447: ACPI problem, hdb timed out

2006-08-17 Thread Patrick Matthäi 

Package: linux-image-2.6.17-2-k7
Version: 2.6.17-6

Hello,
After the last update yesterday of the kernel ( from 2.6.17-1 up to 
2.6.17-2 ) I've get some problems.
After many boots, I'm getting at the point, where the kernel 
initialiazes the HID driver, that my hdb timed out and lost his 
interrupt, then he tried to readdress him an interrupt, but that's not 
working.



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

Bug#382720: Error at configure

2006-08-12 Thread Patrick Matthäi 

Package: initramfs-tools
Version: 0.73d

Hello,
The newest update of initramfs-tools seems to be broken by me.


Richte initramfs-tools ein (0.73d) ...
update-initramfs: Generating /boot/initrd.img-2.6.17-1-k7
/usr/sbin/mkinitramfs: line 206: [: /etc/initramfs-tools/conf.d/resume: 
binary operator expected


Richte thunderbird ein (1.5.0.5-1) ...
Returned debconf: Debian



the-me:/home/me# dpkg-reconfigure initramfs-tools
update-initramfs: Generating /boot/initrd.img-2.6.17-1-k7
/usr/sbin/mkinitramfs: line 206: [: /etc/initramfs-tools/conf.d/resume: 
binary operator expected

the-me:/home/me# cat /etc/initramfs-tools/conf.d/resume
RESUME=/dev/hda5

hda5 is the right partititon.


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

Bug#375432: One package is missing

2006-06-25 Thread Patrick Matthäi 

Package: linux-headers-2.6.17-1-k7
Version: 2.6.17-1

Hello,
I can't install the newest linux-headers, because the package 
linux-kbuild is missing:

Die folgenden Pakete haben nichterfüllte Abhängigkeiten:
 linux-headers-2.6.17-1-k7: Hängt ab: linux-kbuild-2.6.17 ist aber 
nicht installierbar