Bug#1053736: amdgpu firmware are not looked up in all possible paths

2023-10-09 Thread Vincent Bernat
Source: linux
Version: 6.5.6-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

When amdgpu firmware are in /lib/firmware/updates, they are not detected by the
"amdgpu-firmware-required" patch, preventing the module to load while the
correct firmwares are present.

https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/patches/bugfix/all/radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch

Also, maybe the situation in 2013 is not the same in 2023 and we should just
drop the patch?


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmUkcSYSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5b1EQAJvTSc0ZV3duNoF/rjNbkfWJOcbu63Fu
tmSYaWHzuCAgoXUZIFt+6BZTRbVMGFMFeNHhuR/qd8cq6Rh/qdH5AiICR5aV3Xts
c/TYVbrJNsj0fpsO7+sbaDMzvnJ7Ccu6qWbDfo/YLkNzU7AAHJS8M8pkepAwY830
najSkl3NeQPADp268V42HfpF+O8okTxuHXUpbzYlYODSw+kj7MCCJUvSPb5NtQOg
EyF32bOQZ86TtM99atbMdywGKwGN5q8qbiuJmQJuKsF0I7CaYDYewfOkpnAaps4n
3SFhiEBDu1Xhvif89umt6K/AU9Qp6Fz2wXycEmDgUArIuDc9Y2hddNneKXe93tE4
kN0OeyyEWebmwwWJlGBIios7EYugA6p7n9yNkS3fL5YaRkPm3GAWEruU9bLrLVVZ
xXfq7PqzBxSl1lzkZwi6fN85LZ2HOwcHDKP9yFiQG+bXse0/4VRhXePgTlXY+DXV
Pi/apu1kGMlOOOhs4uniH+3EHGwvHNOofPoCd2WG0aQ/c+VHlqD/0Bc5/bg7inX9
oicyKKhLZvvURp1wgQrEpqUuPopecDgNkyY16iyi2cpMrIFM6HchRUIyBnto1Nay
IyBL5XgxEnfj8ZcIKiQf8Yx9CfXUluJghWCqpKG5LQpkEWB/pCLZrnctM5ywDXF5
Tzoiu8OLqeXH
=6yHp
-END PGP SIGNATURE-



Bug#1031912: Package cirrus/ directory

2023-02-25 Thread Vincent Bernat
Source: firmware-nonfree
Version: 20230210-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

The Cirrus Logic CS35L41 is a DSP with firmwares shipped upstream in the cirrus/
directory. It would be nice to build a package for that (firmware-cirrus?).

Thanks!


- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmP5ySASHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5hDYP/0+bw+0ar+FW4QdtfObxjhSr6IAS10DR
avdy4linMxK8rdmn3PV44F4sC5A1TnfCILthLtLgM8urraJj9CD0kNR+WHL2hxI7
qrmSXYoBIFlMtP6rR4ICupzM1HAU2Gb4XCTVJz5CFt/w0JBGXXkKfeQA8b0HRWDy
LiSbS9qWY+kJpmvSbzIJzChz5N64TJziRNPhDsy8vHAzMXBkcc5G4oyU2jdoAyuk
VfXgHFyJ2kZYiv1/dvvzGy3bXYK9pv+Q/oYq86Ty9LPwudI5xBVMiEAwOKq126HX
1ZtGvEDXV1JgRKap1+9Rhyvkf1j5F4ANGfnr/GmOL94uhdpDOh0Hrdasgw6/klBt
HiwBXzFQkZjXE5RhKeAjXMiCSkpbvPY5o8aJZTfqMjhV17qUN2yw7lGfVfl4rDOG
2xdK+c+/UHfgprAcPCXUCCZ1GROYXXh36KJlX2v5UNGKm37rXKvxmcbBsWj5SPIc
UCy1zOUdKvKig01WrGkS5tAVK8jKWMOPGidD+DMVN0LcbdemPkG3LTYbXZDg4qSy
leKJ+wOlrHhX03thPl3q3KzU0Ufpr8FGPQwcM2Ku3g0u+fKYwoPjNXPrl5znGEnf
IYHUBNS/muIfPS3e6vFqMma8VWpj9PaqZGR60iEOygMavDwDDMG92oScD3bPq6wu
sbPxjVIqIU4S
=iiuL
-END PGP SIGNATURE-



Bug#689962: linux: Compile with CONFIG_VIRTIO_CONSOLE=y

2022-12-05 Thread Vincent Bernat

  ❦ 24 avril 2021 16:15 +02, Salvatore Bonaccorso:


Is this still something we should consider, or can the bug be closed?


I suppose that's since almost nobody chimes in in all these years, there
is no need.


Now that 989153 and 989181 have been merged into this one and the bug is
reopened, then the next question becomes: how to proceed.

The current setting in debian/config/config (ie: globally) is this:
CONFIG_VIRTIO_CONSOLE=m

I can make a MR to change that to =y, but I'm not familiar with VIRTIO_CONSOLE
and thus can't assess whether it's useful on all architectures.

https://salsa.debian.org/kernel-team/linux/-/commit/e83e9da65cce7c870acc6b601738dd5d71bdc842
is where the above setting was made ... on 2008-09-04.

The helptext in drivers/char/Kconfig says:
"Virtio console for use with hypervisors."


Unfortunately, I don't know either for other architectures. It is useful 
at least for AMD64 (to make it work on VM with no ISA bus). For ARM64, I 
don't know if the platform has a better mechanism for serial consoles.




Bug#1021157: missing firmwares for Qualcomm NFA725A

2022-10-29 Thread Vincent Bernat

On 2022-10-29 20:05, Diederik de Haas wrote:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to hw2.1

qca/rampatch_usb_00130201.bin is also present in the upstream repo, but
searching for nvm_usb_00130201_gf.bin did not yield any results.

So this looks like upstream does have most of the needed files, albeit a
slightly older version?
I don't know if anything should be done based on this, but figured I'd share
my findings.


I suppose the search engine only works for stuff mentioned directly in 
commit messages. The file present in the repository: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qca/nvm_usb_00130201_gf.bin.




Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-29 Thread Vincent Bernat

On 2022-10-29 09:23, Salvatore Bonaccorso wrote:

So question is,.. would it make sense to request that linux-image-amd64
depends on the signed | unsigned version?


No unfortunately we cannot do that. The reason is similar to what lead
to
https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
or caused bugs like #916927.

In meanwhile furthermore linux-image-amd64 is anyway not anymore from
a separate metapackage but built from linux-signed-amd64.

The signed packages need always longer as this needs action of signing
them trough a seprate manual process of ftp-masters.


What about linux-image-amd64-unsigned?



Bug#1021157: missing firmwares for Qualcomm NFA725A

2022-10-28 Thread Vincent Bernat

On 2022-10-29 07:15, Vincent Bernat wrote:

  07:14 ❱ dpkg -L firmware-atheros | grep -E '(WCM6855|nvm_usb_00130201)'


I made a typo in WCN, but the files are not here either.



Bug#1021157: missing firmwares for Qualcomm NFA725A

2022-10-28 Thread Vincent Bernat

On 2022-10-29 00:50, Diederik de Haas wrote:


The card works just fine with a 5.19 kernel after installing these files
in /usr/lib/firmware/ath11k/WCN6855/hw2.0/:
https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLAN.H
SP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/amss.bin
https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLAN.
HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/m3.bin
https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/board-2.b
in
https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/regdb.bin

And then creating a symlink from /usr/lib/firmware/ath11k/WCN6855/hw2.1/
to hw2.0/ .

(I do not understand the structure of the directories in
WCN6855/hw2.0/1.1/, so I choose the newest files.)

Some other firmwares from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
/tree/qca are needed for Bluetooth support and are missing as well:

qca/rampatch_usb_00130201.bin
qca/nvm_usb_00130201_gf.bin


I found all the mentioned file names in the buildd log for 20220913-1, so I
guess the issue is fixed.
Can you verify that and update/close the bug accordingly?


They are not present.

 07:14 ❱ dpkg -L firmware-atheros | grep -E '(WCM6855|nvm_usb_00130201)'



Signing initramfs with MOK

2021-08-21 Thread Vincent Bernat
Hey!

Looking at https://wiki.debian.org/SecureBoot, I wonder if it is
possible to sign the initramfs using the MOK. Is it documented
somewhere?

Thanks.
-- 
Every cloud engenders not a storm.
-- William Shakespeare, "Henry VI"



Bug#689962: linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y

2021-04-25 Thread Vincent Bernat
 ❦ 24 avril 2021 16:15 +02, Salvatore Bonaccorso:

> Is this still something we should consider, or can the bug be closed?

I suppose that's since almost nobody chimes in in all these years, there
is no need.
-- 
Watch out for off-by-one errors.
- The Elements of Programming Style (Kernighan & Plauger)



Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image

2021-04-11 Thread Vincent Bernat
 ❦ 11 avril 2021 18:44 -07, Josh Triplett:

>> > Whether you have an initramfs or not is orthogonal to DHCP
>> > configuration. The kernel's built-in DHCP configuration works even if
>> > you're not using a network filesystem as the root filesystem.
>> 
>> The initramfs is supposed to take responsibility for handling all of
>> the legacy boot parameters.  Moving this to initramfs-tools and merging
>> it with the existing bug there.
>
> That wouldn't actually solve the issue as reported. I was hoping
> specifically for the in-kernel support.
>
> I'd like to use this on a cloud instance that uses ext4 on NVMe, and
> thus doesn't currently need an initramfs.

I think your concern is around making VM boot fast. I don't want to put
words in your mouth, but if I am correct, this may help your argument.
-- 
Water, taken in moderation cannot hurt anybody.
-- Mark Twain



Bug#962134: add Sound Open Firmware

2020-06-04 Thread Vincent Bernat
 ❦  4 juin 2020 16:56 +08, Paul Wise:

>> My understanding is the SOF team didn't want to use intel-firmware but 
>> I'm trying to find the discussion on the SOF mailing list as to why.
>
> I'm not sure what you mean by intel-firmware. Based on the Repology
> website I guess you mean the Intel CPU microcode, which is shipped in
> Debian in the intel-microcode package.
>
> https://repology.org/project/intel-firmware/packages
> https://repology.org/project/intel-microcode/packages

I think this is firmware-intel-sound (source package is fimware-nonfree).
-- 
Test programs at their boundary values.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Re: debplate - A template system for Debian packages

2020-05-24 Thread Vincent Bernat
 ❦ 24 mai 2020 01:46 +01, Ben Hutchings:

>> I'm going to talk about this at MiniDebConf Online next week, but since
>> I'm developing it with some of the kernel team's packages in mind I
>> thought I would give some advance notice here.
>
> Something I forgot to mention is that this depends on jinja-vanish,
> which is currently in the NEW queue.  My packaging repo for that is at:
> https://salsa.debian.org/benh/jinja-vanish

About Jinja templating, I usually find easier to have these options:

trim_blocks=True,
lstrip_blocks=True,
keep_trailing_newline=True,

You can still cancel them with "{%+" when needed.
-- 
Write clearly - don't be too clever.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#955232: Please add 9p kernel module to the cloud image.

2020-03-30 Thread Vincent Bernat
 ❦ 30 mars 2020 01:36 +01, Ben Hutchings:

>> Please consider adding kernel module '9p' to the cloud image. It is
>> impossible to passthrough filesystem from hypervisor with the current cloud
>> image and there are no additional packages to install it. The only way that
>> I know to passthrough filesystem currently is to remove
>> linux-image-cloud-amd64 and install linux-image-amd64.
>
> The "cloud" images are specifically meant for running on public clouds,
> and don't support everything that could possibly be exposed to a VM.
>
> Is there a public cloud that supports 9p passthrough?

Dunno about OP, but for me, it's also useful when using nested
virtualisation. Also, the limitation to "public" cloud seems quite
restrictive. Cloud kernel is used by cloud images, which can be used
directly with libvirt, for example.
-- 
Things past redress and now with me past care.
-- William Shakespeare, "Richard II"


signature.asc
Description: PGP signature


Bug#950254: initramfs-tools: Please make libpthread pull in libgcc_s

2020-02-03 Thread Vincent Bernat
Package: initramfs-tools
Version: 0.136
Followup-For: Bug #950254

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

I was also hit by this bug. The issue is that the upload of gcc-10
moved libgcc_s.so to /lib instead of /lib/x86_64-linux-gnu. The hack
in cryptroot hook doesn't find it anymore. As a workaround, I have
modified the find line to:

find -L /lib -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do
copy_exec "$so"
done

(hardcoding /lib).

- -- Package-specific info:
- -- initramfs sizes
- -rw-r--r-- 1 root root 19M Feb  1 08:26 /boot/initrd.img-5.4.0-2-amd64
- -rw-r--r-- 1 root root 20M Feb  3 13:20 /boot/initrd.img-5.4.0-3-amd64
- -- /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.4.0-3-amd64 root=/dev/mapper/guybrush--vg-root ro splash 
quiet

- -- resume
RESUME=/dev/mapper/guybrush--vg-swap
- -- /proc/filesystems
ext3
ext2
ext4
vfat
fuseblk

- -- lsmod
Module  Size  Used by
xt_addrtype16384  2
xt_MASQUERADE  20480  1
ip6t_REJECT16384  11
nf_reject_ipv6 20480  1 ip6t_REJECT
ip6t_rpfilter  16384  1
xt_tcpudp  20480  6
ipt_REJECT 16384  2
nf_reject_ipv4 16384  1 ipt_REJECT
xt_conntrack   16384  15
nft_counter16384  291
ip6_tables 36864  2
ip_tables  32768  0
nft_compat 20480  40
sctp  405504  22
binfmt_misc24576  1
veth   32768  0
cpuid  16384  0
uinput 20480  0
snd_usb_audio 290816  2
snd_usbmidi_lib40960  1 snd_usb_audio
snd_rawmidi45056  1 snd_usbmidi_lib
usbhid 65536  0
snd_seq_device 16384  1 snd_rawmidi
cdc_ether  24576  0
usbnet 49152  1 cdc_ether
r8152  77824  0
mii16384  2 usbnet,r8152
fuse  139264  3
xfrm_user  40960  1
xfrm_algo  16384  1 xfrm_user
br_netfilter   28672  0
bridge200704  1 br_netfilter
stp16384  1 bridge
llc16384  2 bridge,stp
overlay   135168  0
tun57344  2
ctr16384  0
ccm20480  0
rfcomm 90112  4
cmac   16384  1
nft_chain_nat  16384  8
nf_nat 49152  2 nft_chain_nat,xt_MASQUERADE
nf_conntrack  159744  3 xt_conntrack,nf_nat,xt_MASQUERADE
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 16384  1 nf_conntrack
libcrc32c  16384  3 nf_conntrack,nf_nat,sctp
ip_set 53248  0
nf_tables 167936  421 nft_compat,nft_counter,nft_chain_nat
nfnetlink  16384  5 nft_compat,nf_tables,ip_set
bnep   28672  2
btusb  57344  0
btrtl  24576  1 btusb
btbcm  16384  1 btusb
btintel28672  1 btusb
bluetooth 659456  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
uvcvideo  114688  0
videobuf2_vmalloc  20480  1 uvcvideo
videobuf2_memops   20480  1 videobuf2_vmalloc
videobuf2_v4l2 28672  1 uvcvideo
videobuf2_common   57344  2 videobuf2_v4l2,uvcvideo
drbg   28672  1
videodev  249856  3 videobuf2_v4l2,uvcvideo,videobuf2_common
ansi_cprng 16384  0
ecdh_generic   16384  2 bluetooth
mc 57344  5 
videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
ecc32768  1 ecdh_generic
snd_sof_pci20480  0
snd_sof_intel_hda_common73728  1 snd_sof_pci
msr16384  0
snd_sof_intel_hda  20480  1 snd_sof_intel_hda_common
snd_sof_intel_byt  20480  1 snd_sof_pci
snd_sof_intel_ipc  20480  1 snd_sof_intel_byt
snd_sof   118784  4 
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc
snd_sof_xtensa_dsp 16384  1 snd_sof_pci
snd_hda_codec_hdmi 73728  1
intel_rapl_msr 20480  0
snd_soc_skl   180224  0
snd_soc_hdac_hda   24576  2 snd_sof_intel_hda_common,snd_soc_skl
snd_hda_ext_core   32768  4 
snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_sst_ipc20480  1 snd_soc_skl
snd_soc_sst_dsp40960  1 snd_soc_skl
snd_soc_acpi_intel_match32768  3 
snd_sof_pci,snd_sof_intel_hda_common,snd_soc_skl
x86_pkg_temp_thermal20480  0
snd_soc_acpi   16384  3 snd_sof_pci,snd_soc_acpi_intel_match,snd_soc_skl
intel_powerclamp   20480  0
coretemp   20480  0
snd_soc_core  270336  4 
snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl
snd_hda_codec_realtek   126976  1
joydev 28672  0
snd_hda_codec_generic94208  1 snd_hda_codec_realtek
snd_compress   28672  1 snd_soc_core
iwlmvm307200  0
kvm_intel 303104  

Bug#861115: Please consider increasing net.ipv6.route.max_size default value

2020-01-21 Thread Vincent Bernat
 ❦ 21 janvier 2020 23:51 +00, Tim Bray :

>> This setting is for the size of the route cache. You can have far more
>> routes. In the past, there were bugs where each lookup will be put in
>> cache, but since 4.2, only the PMTU exceptions are stored in cache. See
>> 
>>
>> Do you have a lot of entries in `ip -6 route show cache`?
>
>
> No entries at all in
> `ip -6 route show cache`
>
> and none in `ip -6 route show table cache`
>
> It is a quiet time of day, so I'll check again.
>
> What prompted me to look at net.ipv6.route.max_size was because I built my 
> own newer kernel (in desperation).
>
> Linux version 5.4.11 (from kernel.org, .config from debian buster, make 
> olddefconfig) gives out in dmesg:
>
> Route cache is full: consider increasing sysctl net.ipv[4|6].route.max_size.
>
>
> I've never seen this message on 4.19 Debian buster, but increasing
> net.ipv6.route.max_size made all the network hangs go away, both on
> 5.4.11 and 4.19

The message was addeed in 5.1. I'll test later today to check if "ip -6
route show cache" still works.
-- 
Parenthesise to avoid ambiguity.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#861115: Please consider increasing net.ipv6.route.max_size default value

2020-01-21 Thread Vincent Bernat
 ❦ 21 janvier 2020 18:58 +00, Tim Bray :

> I also agree.
>
> I've just spent a month tracking down an issue where IPv6 networking
> connections hang.  Using Debian buster, 4.19.0-6-amd64.
>
> Machine carries a full IPv6 table, received via BGP. About 80k routes.
>
> Symptoms were BFD dropping out.  Connectivity hangs.
>
> setting net.ipv6.route.max_size to 2147483647 fixed all issues.   
> (aware this might be too big)
>
> Later kernels  (5.4.11) cause a dmesg when full.

This setting is for the size of the route cache. You can have far more
routes. In the past, there were bugs where each lookup will be put in
cache, but since 4.2, only the PMTU exceptions are stored in cache. See


Do you have a lot of entries in `ip -6 route show cache`?
-- 
Avoid multiple exits from loops.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#949178: linux-image-5.4.0-2-amd64: system freeze with i915 with error: 0000:00:02.0: Resetting rcs0 for hang on rcs0

2020-01-17 Thread Vincent Bernat
 ❦ 17 janvier 2020 20:23 +01, Davide Prina :

> Jan 15 11:37:33 prinad03 kernel: [ 9354.966794] i915 :00:02.0: GPU
> HANG: ecode 9:1:0x, hang on rcs0

You may want to follow this thread. 5.3 and 5.4 seem to be difficult
kernels for Intel graphic cards. It's unknown if 5.5 will fix it once
and for all.

https://gitlab.freedesktop.org/drm/intel/issues/451

On an old generation of hardware, I had issue on 5.3, fixed on 5.4. On a
new generation, I have issue with 5.4 and not 5.3.
-- 
I dote on his very absence.
-- William Shakespeare, "The Merchant of Venice"


signature.asc
Description: PGP signature


Bug#940813: firmware-iwlwifi: iwlwifi-9000-pu-b0-jf-b0-46.ucode is broken

2020-01-14 Thread Vincent Bernat
Package: firmware-iwlwifi
Version: 20190717-2
Followup-For: Bug #940813

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

I was running in this problem (as well as some unreliability with the
Bluetooth). Instead of downgrading to -41, I have updated the -46 to
the version in linux-firmware.git. There has been one additional
version (and more for Bluetooth):

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/iwlwifi-9000-pu-b0-jf-b0-46.ucode

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

Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.135

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl4eLQsSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5QUYP/0CPAAZKVJPFnA2uKctgfLbiM4A5Sub7
AzLzTkeUjSajrZT8t001HZN/XYreXcfA5GhDHm9BgJ2Xh5/1qThmfe8+l0ZOEss2
gLG0DC+QMx49OUddCX09U36N8Fml3fCMbO2RU2XIWmyjZou/s7Mxv5P9C+04uO/b
OEtiFF1UX/cCgW9uezND2nqNQh+hRtEELnzdCb2F8ymWWA5f7zJsmiTBf1RVgDB0
pZ4TlzIRPcrTELxelkz+jkuqAHANxbJKwWIDFsJ58EbIp6hHSQTC4s+rL1ErEipA
NkPxoBe5a3QPQ3zJ1XzB9Z7X7w4mSRdDLP22BocFHDeREhFQ0hoVgL2T0SkxPzAe
9M638NMiQUvtKh4fsj55Y7iF77x31/jvqoCvh+52aj1DHdzfOZI7SkNtl9uzLmEg
Np96couiDk3wHrAmWyrzti1VEu/vHTHD25T0pGdNZ7n8ec8b7v0ArYp2rGMAf7zp
Uki+98Qit7w/uf0MiwaKsXIm+eHttCdjdQL2j7qmXsDDpmgGTzum0nhyGlgA60O8
uTIwfvx7fKoVae7rntyZas2Dn//oDrG8UrSUkYaS2bgIxo1FZ2IRN8XSBPjVfQjn
sUopj4RcosxM+nLN7M284qD2fp+tunpYFJ1vyatvnBptmAAwVLkTn2gH9sYDtEzZ
lXbPmor0thvQ
=fKGB
-END PGP SIGNATURE-



Re: Why don't we have linux-5.0 instead of 4.19.0-4 which is the running kernel in Debian 'buster' i.e. testing ?

2019-04-06 Thread Vincent Bernat
 ❦  6 avril 2019 02:14 +00, shirish शिरीष :

> Currently we are using 4.19.0-4 according to the lastest updated
> systems on buster .
>
> $ uname -r
> 4.19.0-4-amd64
>
> I see that 4.20 has been taken out of the archive and the 5.0 is there
> but in experimental -
>
> $ apt-cache policy linux-image-5.0.0-trunk-amd64
> linux-image-5.0.0-trunk-amd64:
>   Installed: (none)
>   Candidate: 5.0.2-1~exp1
>   Version table:
>  5.0.2-1~exp1 1
>   1 http://cdn-fastly.deb.debian.org/debian experimental/main
> amd64 Packages
>
> What's stopping it to move to unstable and have an unblock and be for buster ?

4.19 is a LTS kernel. 4.20 and 5.0 are not.
-- 
Format a program to help the reader understand it.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Re: linux-image-amd64 in sid

2017-07-05 Thread Vincent Bernat
 ❦  5 juillet 2017 13:25 +0200, matecs  :

> i've noticed that linux-image-amd64 and linux-image-686-pae points to
> 4.9.0-3,

The metapackage handling those ones is currently in the NEW queue. It
should be here in a few days.
-- 
ROMEO:  Courage, man; the hurt cannot be much.
MERCUTIO:   No, 'tis not so deep as a well, nor so wide
as a church-door; but 'tis enough, 'twill serve.


signature.asc
Description: PGP signature


Bug#855596: Compile with CONFIG_GDB_SCRIPTS

2017-02-20 Thread Vincent Bernat
Package: src:linux
Version: 4.9.10-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

When debugging a kernel problem, it is quite useful to get
vmlinux-gdb.py. This can be compiled with CONFIG_GDB_SCRIPTS and could
be included with the dbgsym package (or with kbuild?).

Thanks!

- -- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlirFDYSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5bCIQAJ3aG78mb3wbc3jYEVo5OZ1kHm9kCfoq
/xWnf5jvrDI7PDmOUCrb3uuRndgZitZqFBpB8maNpysna6USl8+PMKBtvlV0U9hD
gqcmcvHUCuHeu0YUxEprcRxPpC5T+5FzbRfiOR7yVo7DC6Oud/NFG0Gv2frxIhGQ
y0Nk0mA7ZVQ1uabTr5cMQupacyjEI4JRao+nrazC60wlq5DPaDX8LNyUQlyVooDH
XeC/Qa+XtgH4FsJAGNZ225SkcnjQTQALfb2vtpAnjCG0a2B/wRG7jP+rZUFh7Gyr
96xsavnAff1sC6kbVKiZH/sXGF+ounzfE8iXG2Hlp+r3fVyt/2zVAaACIPPEFhJ5
k146krxUE6FB2YM3b+IgfMJczyVztg1UhE4RsCCs6Ka625uHcOyel8VoT3Wm7nNH
oANf6Xlxknhqlgfrz39UFZ/Udhp2eftL9kqi/BEGc0SY89b4v4l6cLXNYz5G9dKA
DYhZ5pQYn7moo+9CuHoGOwv3Rfaq5IOjwDnKHYqT3g/AEW7OVxh50ae7CvqIKlus
h1/2kIB5WRvJShlug7iQoAo5TkyKABelVvOq4nt8cLIPBFhlijLKhfx+RaBVGrFf
255YVlvtt+EaP4DFF0HgWOSOL/WO+8tiZg++0A2tH1F5hoqRKpJVANcAkzwjeh4D
n/3M6shfKQmm
=E93K
-END PGP SIGNATURE-



Bug#847325: Unable to copy symlinks with copy_file

2016-12-07 Thread Vincent Bernat
 ❦  8 décembre 2016 02:08 GMT, Ben Hutchings  :

> (Annoyingly, I couldn't reproduce this at first because I tried just
> adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
> *not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
> not fatal.)

I should have said that I got the error through plymouth hook.
-- 
Civilization is the limitless multiplication of unnecessary necessities.
-- Mark Twain


signature.asc
Description: PGP signature


Bug#847325: Unable to copy symlinks with copy_file

2016-12-07 Thread Vincent Bernat
Package: initramfs-tools-core
Version: 0.125
Severity: normal
File: /usr/share/initramfs-tools/hook-functions

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

Today, new firmware-misc-nonfree package contains some symlinks:

lrwxrwxrwx 1 root root   26 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_bl.bin -> ../../gm200/gr/fecs_bl.bin
- -rw-r--r-- 1 root root 1968 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_data.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_inst.bin -> ../../gm200/gr/fecs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_sig.bin
lrwxrwxrwx 1 root root   27 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin -> ../../gm200/gr/gpccs_bl.bin
- -rw-r--r-- 1 root root 2056 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_data.bin
lrwxrwxrwx 1 root root   29 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_inst.bin -> ../../gm200/gr/gpccs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_sig.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin -> 
../../gm200/gr/sw_bundle_init.bin
lrwxrwxrwx 1 root root   25 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_ctx.bin -> ../../gm200/gr/sw_ctx.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_method_init.bin -> 
../../gm200/gr/sw_method_init.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_nonctx.bin -> ../../gm200/gr/sw_nonctx.bin

I have this error on update-initramfs -u -vv:

Adding firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
Adding firmware /usr/lib/firmware/nvidia/gm200/gr/gpccs_inst.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
Removing /boot/initrd.img-4.8.0-2-amd64.dpkg-bak
update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.

I have traced to this:

+ copy_file firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ local type src target link_target
+ type=firmware
+ src=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ target=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ [ -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -d /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -e /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ mkdir -p /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr
+ [ -h /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ readlink -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ link_target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ /usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin != 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ y = y ]
+ echo Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ ln -rs 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin 
/var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ src=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ -e 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
+ return 1

Maybe the check should also use cmp.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 
'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 23-1
ii  udev 232-7

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.1-4.3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlhH6JcSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5r14P/ReRizb2CEv6yNYqJXgwpM8BdwgRkOPJ
6xVzf/gLYuZaxEtCnH2bi9Z6Y3f1ExBJE9G5bNmfSrF9Q8Zpaignifp392a1/HS7
ZE2Q4g6O6LkOB/N29711jd9lEoJfuNYh1g3X77fFO27htZohpkR3sN39k3fJdajd
fTvlm7qnUIyeBT7iC2nq8AZMDWJuY5xZ5ziSDoYB9oxNvCGSJIg+0Q+4XTKmunvA
EcQHrM+0AvaEMkikgoM/Bg7HIEBSp0xtlHPT2hQf1R127zd8urUdpIwzxriWattg
UVdIPGY0GbpIGO8eWNEbsCaEP1oX0cQqnT+e9gqdqCkeFPbxqVGthRKfNX4IEzBc
ZnOFB38t5pt+J9DScj5ZpK2WFJTgaY1Q/ckdK2zRcnNb9hJdOHxUjDRFCI8AOvFx
ouNMxU1hnNgEf1GFri8xwYfDDyS1PoXREY6odYRsvZkrR7a0NWQV2EXf8HSQzewb
vB79DOFw5+vpkaW/RI3YHCMM7hiNOPCiIGw1JLmGA5TXRnsK++k4dtN+mZP5Eptd
ud7zpaCu2RyFaENdVca0yXvw8AenuxOXLEneGAKmElyWIIlwShGrKp5Ru0L56J0J
fz3vNvgf111CC5cQwNRV+FvqRoy+9vzgU9ZTSyAS4oVk2zwtgBfHA1xw+AN0Ub/b

Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

2016-07-24 Thread Vincent Bernat
control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=95176

 ❦ 24 juillet 2016 19:10 CEST, Bram Bolder  :

> It was set to 1, changing it to 0 did not solve the problem (I stopped xdm,
> set the 0 and started it again).
>
> I did some further checking (kernel 4.5 has enable_psr=0 as default). I also
> noticed that producing load removed the flickering (e.g. glxgears). It's 
> definitively
> a power saving feature.
>
> I then tried to set i915.enable_psr=0 as commandline option in grub and this 
> solved
> my problem! Hooray!
>
>
> My question now is how to proceed with this problem. I'm quite sure that you 
> don't want
> everyone with my (or a similar) hardware setup to file a bugreport to you. 
> Maybe this
> problem gets fixes upstream at some point...

The functionality exists since quite some time but has been disabled
until 4.6. On my laptop (Haswell), it started working correctly from 4.6
too. Previous kernels where exhibiting the same problems that you
observed (but I was able to enable/disable this functionnality without
restarting anything). Therefore, it seems that upstream put some work
into this functionnality but it doesn't work for everyone.

> Do you want to close this ticket? The problem is solved for me, but
> maybe other users might experience the same problem.

I can't say, I am not the maintainer of the kernel in Debian, just a
user. You can try 4.7-rc7 in experimental. It seems the bug is already
reported upstream (and not solved in 4.7-rc7):

https://bugs.freedesktop.org/show_bug.cgi?id=96704
https://bugs.freedesktop.org/show_bug.cgi?id=96736
https://bugs.freedesktop.org/show_bug.cgi?id=96916
https://bugs.freedesktop.org/show_bug.cgi?id=95124
https://bugs.freedesktop.org/show_bug.cgi?id=95176

I mark the last one as a forwarded address for this bug (this seems the
most active one).
-- 
Use uniform input formats.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

2016-07-24 Thread Vincent Bernat
 ❦ 24 juillet 2016 13:45 CEST, Bram Bolder  :

> after upgrading the meta package 'linux-image-amd64' from 
> linux-image-4.5.0-2-amd64
> to linux-image-4.6.0-1-amd64 (and rebooting), my laptop screen started to 
> flicker
> annoyingly. At first I thought it was a hardware defect (backlight lamp 
> reaching
> its end of life), but booting an Ubuntu or reverting to the 4.5.0-2 does not 
> show
> any flickering. The normal terminals (alt-F1 through alt-F6) do not flicker.
>
> My laptop has seen many generations of Linux images while using 'Debian 
> testing',
> all without problems, so it must be related to this latest kernel version.
> I tried a clean installation of SID (i.e. without explicitly configuring 
> xorg),
> but it reproduces the flickering.

Is /sys/module/i915/parameters/enable_psr set to 1? If yes, can you try
to set it to 0 and check if the problem goes away (no need to restart
anything).
-- 
Don't just echo the code with comments - make every comment count.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#815125: Boot failure with Debian linux 4.4.2 package

2016-02-21 Thread Vincent Bernat
 ❦ 21 février 2016 03:45 GMT, Ben Hutchings  :

>> Apparently "earlyprintk=efi,keep" is likely to work better.  Jim Barber
>> was able to get a traceback this way.
>> 
>> It looks like the efi-bgrt driver is crashing, and there is an upstream
>> fix for it.  I'll upload a test version of the package shortly.
>
> This test version is now available at
> https://people.debian.org/~benh/packages/unstable/
>
> Please report back whether this does or doesn't fix the problem for
> you.

It works fine for me. Thanks!
-- 
Make sure special cases are truly special.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#815125: Boot failure with Debian linux 4.4.2 package

2016-02-20 Thread Vincent Bernat
 ❦ 20 février 2016 17:43 GMT, Ben Hutchings  :

> I apologise for this regression, which of course didn't affect any of
> the several machines I was able to test on.

No problem. That's what unstable is for!

> Please can you each reply to the bug address with the following
> details:
>
> - Does the affected system boot using the BIOS boot protocol
>   (including CSM) or UEFI boot protocol?

Dunno what CSM is, but boot UEFI without compat mode.

> - If you boot with the added kernel parameter "earlyprintk=vga" or
>   "earlyprintk=serial" (and without "quiet"), do any boot messages
>   appear before the hang/reboot?  PLease send them (a photo is fine).

Yep, same problem with earlyprintk=vga.

It never leaves the Grub screen:

Loading initial ramdisk ...
_

And that's all.

> - If it boots with UEFI, does the kernel parameter "efi=noruntime"
>   work around the problem?

Yes. The kernel boots.

> - If you haven't already reported this, does the Linux 4.5-rc4 package
>   from experimental have the same problem?

Yep, same problem with this one.
-- 
Avoid unnecessary branches.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#815126: linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'

2016-02-19 Thread Vincent Bernat
 ❦ 19 février 2016 07:34 GMT, Jim Barber  :

> I upgraded from linux-image-4.3.0-1-amd64 (version 4.3.5-1) to 
> linux-image-4.4.0-1-amd64.
> On rebooting the system I am presented with grub, and then start booting into 
> Linux.
> I only get to see 2 lines with the cursor below them on the lefthand side.
>
>   Loading Linux 4.4.0-1 ...
>   Loading initial ramdisk ...
>   _
>
> The system freezes at this point and is unresponsive.
> I have to hold my power button down for approx 10s to power off the laptop.
> Booting back into linux-4.3.0-1-amd64 works fine.

I am in the same situation. I am also on the same system (Thinkpad X1
Carbon, but 2nd).

> Because the boot hangs so early I can't provide any useful diagnostic
> information.

Ditto. I tried modeset=0, without any change.
-- 
Choose variable names that won't be confused.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#798512: linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM

2015-09-10 Thread Vincent Bernat
 ❦ 10 septembre 2015 13:56 +0200, Lucas Nussbaum  :

>> > Dmesg output during the hangs:
>> > [  876.069592] e1000e :00:19.0 eth0: Detected Hardware Unit Hang:
>> 
>> You can try disabling some of the offloading functions:
>> 
>>ethtool -K eth0 tso off gro off gso off lro off
>
> Yes, I saw that mentioned somewhere. But I haven't tried yet. And it's
> not really a suitable long-term fix. :)
> If that helps to understand the root issue, I can try that next week or
> the week after (but the machine is in production now, so it's not that
> easy).

Whatever the result is, it's just a workaround. The "Detected Hardware
Unit Hang" error is quite generic and I have never found a way to get a
probable root cause.

It depends on how much you need those offload features. Disabling them
will reduce the performance but also will prevent a whole class of
problems from happening (bugs or pacing-related).
-- 
Must I hold a candle to my shames?
-- William Shakespeare, "The Merchant of Venice"


signature.asc
Description: PGP signature


Bug#798512: linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM

2015-09-10 Thread Vincent Bernat
 ❦ 10 septembre 2015 09:35 +0200, Lucas Nussbaum  :

> Dmesg output during the hangs:
> [  876.069592] e1000e :00:19.0 eth0: Detected Hardware Unit Hang:

You can try disabling some of the offloading functions:

   ethtool -K eth0 tso off gro off gso off lro off
-- 
Harp not on that string.
-- William Shakespeare, "Henry VI"


signature.asc
Description: PGP signature


Live patching of Debian Kernel

2015-08-17 Thread Vincent Bernat
Hey!

After the presentation of Ben about the new features of Linux, I have
looked a bit at how the live patching could be used. I am just
presenting what I have discovered, it is likely that I drop the ball
just here.

I have tried kpatch only.

 1. We need to enable both CONFIG_KALLSYMS_ALL and CONFIG_LIVEPATCH (the
first is needed by the second but is also needed for itself). This
was already asked in #660288 but wasn't done due to the context.

To avoid reocmpiling the whole official Debian kernel repeatedly on my
laptop, I have then switched to a vanilla 4.1 kernel with far less
options.

 2. Despite the documentation, it is possible to compile the kpatch
module without running the kernel to be patched. Just make
KPATCH_BUILD=/path/to/kernel/source. This also builds the tools to
build the patch and to load the patch.

 3. Building the patch can also be done without running the kernel to
patch: kpatch-build also accepts the path to the kernel
source. Just ./kpatch-build/kpatch-build -s /path/to/kernel/source
patch-to-apply.patch.

 4. Currently, kpatch wants to use set_memory_rw/ro. Those have been
unexported in 4.1. The appropriate patch could just be reverted:

   
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6bbb614ec478961c7443086bdf7fd6784479c14a
   https://github.com/dynup/kpatch/issues/496

After this step, we have two .ko files (one for kpatch and one for the
patch we want). The kpatch utils just loads the module. We can keep it
or just load the appropriate modules ourselves (in postinst, after a
debconf question, this kernel fixes some vulnerabilities and provides
patches for your current kernel, would you like to apply them?).

For testing, I have tried the patch fixing CVE-2015-5156. It loads
correctly but unfortunately, it doesn't seem to have any effect. But, it
modifies virtnet_probe(), so it is expected that nothing happens if the
module is loaded and maybe the patch is lost if the module is unloaded
then loaded. In all cases, no change in
/sys/class/net/eth0/device/features.

So, I have tried the provided example which trivially modifies the
output of /proc/meminfo. Unfortunately, the kernel panics on load. I
have reported the bug upstream:

 https://github.com/dynup/kpatch/issues/497

That's all. I didn't check kgraft. I didn't check if others have
provided tested patches for various CVE that would lessen the work.
-- 
Program defensively.
- The Elements of Programming Style (Kernighan  Plauger)



Bug#775177: unable to load bluetooth firmware on resume

2015-08-07 Thread Vincent Bernat
 ❦ 12 janvier 2015 08:52 +0100, Vincent Bernat ber...@debian.org :

 When resuming, loading of bluetooth firmware fails:

The issue still exists with 4.1 in unstable. It's easy to trigger a
successful load of the firmware with rfkill block bluetooth  rfkill
unblock bluetooth.
-- 
Use variable names that mean something.
- The Elements of Programming Style (Kernighan  Plauger)


signature.asc
Description: PGP signature


Bug#779019: aufs is leaking original paths in /proc/*/map_files

2015-02-23 Thread Vincent Bernat
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: wishlist
File: /boot/vmlinuz-3.16.0-4-amd64
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

aufs is leaking the layer paths when looking at /proc/*/map_files:

$ ls -l /proc/$$/map_files | head
total 0
lr 1 root root 64 févr. 23 10:25 40-4aa000 - 
/tmp/target/ro/bin/zsh5
lr 1 root root 64 févr. 23 10:25 6a9000-6aa000 - 
/tmp/target/ro/bin/zsh5
lr 1 root root 64 févr. 23 10:25 6aa000-6b - 
/tmp/target/ro/bin/zsh5
lr 1 root root 64 févr. 23 10:25 7fd1a73e1000-7fd1a73f1000 - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/computil.so
lr 1 root root 64 févr. 23 10:25 7fd1a73f1000-7fd1a75f - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/computil.so
lr 1 root root 64 févr. 23 10:25 7fd1a75f-7fd1a75f1000 - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/computil.so
lr 1 root root 64 févr. 23 10:25 7fd1a75f1000-7fd1a75f2000 - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/computil.so
lr 1 root root 64 févr. 23 10:25 7fd1a75f3000-7fd1a75f5000 - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/zleparameter.so
lr 1 root root 64 févr. 23 10:25 7fd1a75f5000-7fd1a77f4000 - 
/tmp/target/ro/usr/lib/x86_64-linux-gnu/zsh/5.0.7/zsh/zleparameter.so
 ro

This has been fixed in more recent versions of aufs (for example, the
one applied for 3.17 in experimental Debian packages). I don't have a
clean patch, but look at:

 
http://lists.alioth.debian.org/pipermail/kernel-svn-changes/2014-November/019612.html

I suppose the patch could be:

#v+
diff --git a/fs/proc/base.c b/fs/proc/base.c
index baf852b..6389b5e 100644
- --- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -1764,7 +1764,7 @@ static int proc_map_files_get_link(struct dentry *dentry, 
struct path *path)
down_read(mm-mmap_sem);
vma = find_exact_vma(mm, vm_start, vm_end);
if (vma  vma-vm_file) {
- - *path = vma-vm_file-f_path;
+   *path = vma_pr_or_file(vma)-f_path;
path_get(path);
rc = 0;
}
#v-

Filed as wishlist as it may be too late to fix that for Jessie.

- -- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20A7005UMZ
product_version: ThinkPad X1 Carbon 2nd
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: GRET39WW (1.16 )
board_vendor: LENOVO
board_name: 20A7005UMZ
board_version: SDK0E50510 Pro

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 0b)
Subsystem: Lenovo Device [17aa:2218]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Device [17aa:2218]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 43
Region 0: Memory at f000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 3000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller 
[8086:0a0c] (rev 0b)
Subsystem: Lenovo Device [17aa:2218]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 42
Region 0: Memory at f053 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC 
[8086:9c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Lenovo Device [17aa:2218]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 46
Region 0: Memory at f052 (64-bit, non-prefetchable) [size=64K]
Capabilities: access denied
Kernel driver in use: xhci_hcd

00:16.0 

Bug#775177: unable to load bluetooth firmware on resume

2015-01-12 Thread Vincent Bernat
Package: src:linux
Version: 3.18-1~exp1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

When resuming, loading of bluetooth firmware fails:

Jan 12 09:16:11 zoro kernel: [144940.102172] PM: resume of devices complete 
after 996.215 msecs
Jan 12 09:16:11 zoro kernel: [144940.115289] Bluetooth: hci0: read Intel 
version: 370710018002030d00
Jan 12 09:16:11 zoro kernel: [144940.115292] [ cut here 
]
Jan 12 09:16:11 zoro kernel: [144940.115295] WARNING: CPU: 2 PID: 21529 at 
/build/linux-WI0hIK/linux-3.18/drivers/base/firmware_class.c:1126 
_request_firmware+0x571/0xbb0()
Jan 12 09:16:11 zoro kernel: [144940.115315] Modules linked in: cpuid btusb ufs 
qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c xt_addrtype ipt_MASQUERADE 
nf_nat_masquerade_ipv4 cdc_mbim cdc_wdm cdc_ncm dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag nf_conntrack_netbios_ns nf_conntrack_broadcast ccm 
usb_serial_simple usbserial uinput ecb snd_usb_audio snd_usbmidi_lib 
snd_rawmidi snd_seq_device cdc_ether hid_generic bnep bluetooth xt_tcpudp 
ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack 
ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security 
ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security 
iptable_raw iptable_filter ip_tables x_tables cpufreq_conservative binfmt_misc 
cpufreq_stats cpufreq_userspace cpufreq_powersave deflate ctr twofish_
 generic 
 twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common 
camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 
serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic 
blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic 
cast_common des_generic cbc cmac xcbc rmd160 sha512_ssse3 sha512_generic 
sha256_ssse3 sha256_generic hmac crypto_null af_key xfrm_algo nls_utf8 
nls_cp437 vfat fat usbnet mii arc4 uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core v4l2_common videodev hid_multitouch media iTCO_wdt 
iTCO_vendor_support iwlmvm mac80211 x86_pkg_temp_thermal snd_hda_codec_realtek 
intel_powerclamp intel_rapl snd_hda_codec_hdmi coretemp snd_hda_codec_generic 
kvm_intel kvm efi_pstore efivars psmouse pcspkr serio_raw iwlwifi i2c_i801 
cfg80211 snd_hda_intel snd_hda_controller thinkpad_acpi snd_hda_codec ac nvram 
snd_hwdep battery snd_pcm rfkill tpm_tis snd_timer tpm snd 
i2c_designware_platform
  soundco
 re intel_smartconnect i2c_designware_core xhci_pci evdev xhci_hcd mei_me 
lpc_ich mei shpchp mfd_core processor fuse parport_pc ppdev lp parport autofs4 
ext4 crc16 mbcache jbd2 btrfs xor raid6_pq algif_skcipher af_alg dm_crypt 
dm_mod md_mod sg sd_mod usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ahci libahci libata scsi_mod i915 ehci_pci i2c_algo_bit ehci_hcd 
drm_kms_helper usbcore e1000e drm usb_common ptp pps_core i2c_core thermal wmi 
video thermal_sys button [last unloaded: btusb]
Jan 12 09:16:11 zoro kernel: [144940.115361] CPU: 2 PID: 21529 Comm: 
kworker/u17:1 Tainted: GW  3.18.0-trunk-amd64 #1 Debian 3.18-1~exp1
Jan 12 09:16:11 zoro kernel: [144940.115362] Hardware name: LENOVO 
20A7005UMZ/20A7005UMZ, BIOS GRET39WW (1.16 ) 06/06/2014
Jan 12 09:16:11 zoro kernel: [144940.115368] Workqueue: hci0 hci_power_on 
[bluetooth]
Jan 12 09:16:11 zoro kernel: [144940.115369]   0009 
8153df71 
Jan 12 09:16:11 zoro kernel: [144940.115370]  8106a1c7 880152827d10 
8802126296a0 88019dc0b940
Jan 12 09:16:11 zoro kernel: [144940.115371]  8800718f2b28 fff5 
813d7951 8800718f2b28
Jan 12 09:16:11 zoro kernel: [144940.115371] Call Trace:
Jan 12 09:16:11 zoro kernel: [144940.115376]  [8153df71] ? 
dump_stack+0x41/0x51
Jan 12 09:16:11 zoro kernel: [144940.115380]  [8106a1c7] ? 
warn_slowpath_common+0x77/0x90
Jan 12 09:16:11 zoro kernel: [144940.115381]  [813d7951] ? 
_request_firmware+0x571/0xbb0
Jan 12 09:16:11 zoro kernel: [144940.115382]  [813d7fbc] ? 
request_firmware+0x2c/0x40
Jan 12 09:16:11 zoro kernel: [144940.115383]  [a0e3f17b] ? 
btusb_setup_intel+0x1ab/0x7a0 [btusb]
Jan 12 09:16:11 zoro kernel: [144940.115386]  [813cf2c7] ? 
rpm_check_suspend_allowed+0x67/0xd0
Jan 12 09:16:11 zoro kernel: [144940.115390]  [a0b97f47] ? 
hci_dev_do_open+0xc7/0xa70 [bluetooth]
Jan 12 09:16:11 zoro kernel: [144940.115393]  [a0b9906c] ? 
hci_power_on+0x2c/0x1e0 [bluetooth]
Jan 12 09:16:11 zoro kernel: [144940.115395]  [8153f44d] ? 
__schedule+0x2cd/0x7f0
Jan 12 09:16:11 zoro kernel: [144940.115397]  [81081c5e] ? 
process_one_work+0x14e/0x3f0
Jan 

Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up

2014-12-16 Thread Vincent Bernat
 ❦ 16 décembre 2014 09:22 +0900, Mike Hommey mh+report...@glandium.org :

 Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all
 versions before that.

 My setup involves a luks encrypted root file system, so I get a prompt
 during boot for the passphrase. When booting with the kernel from
 linux-image-3.18.0-trunk-amd64, I simply can't type that passphrase with
 a usb keyboard.

 Note that before linux-image-3.18.0-trunk-amd64, it did work, but not
 immediately: at the time the prompt showed up, it would not actually
 work, and it would take a few seconds for the keyboard to be recognized,
 but it would eventually be useable to type the passphrase. This, in
 turn, may be related to the fact that the keyboard doesn't work in grub
 either, probably because the old bios compatibility doesn't work. If it
 did, I guess there would actually be no problem with the cryptsetup
 prompt.

I have the same problem but my keyboard works with Grub. I suppose that
the appropriate HID driver or evdev doesn't get loaded in the initramfs
but without a keyboard, that's a bit difficult to test. update-initramfs
doesn't show evdev being used but hid stuff is here.
-- 
Reader, suppose you were an idiot.  And suppose you were a member of
Congress.  But I repeat myself.
-- Mark Twain


signature.asc
Description: PGP signature


Bug#769953: Kernel oops after resume on SYSC_newlstat

2014-11-17 Thread Vincent Bernat
Package: src:linux
Version: 3.16.7-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

Since my upgrade to 3.16.7, I am getting into a kernel oops after each
resume on the SYSC_newlstat syscall. It happens when I sync my desktop
computer with my laptop. It doesn't happen on its own, so I don't know
if this is the first time such a syscall is invoked (I doubt that). I
didn't have the problem with 3.16.5. I am currently running 3.17 from
experimental to check if the problem is still here.

I have manually run some fsck on all filesystems without any
problem. The problem never happens on a fresh boot. I am using suspend
hybrid (systemctl hybrid-sleep). For some reason, my computer shuts
down instead of sleeping, however, this problem is here still some
time so it should be unrelated. Therefore, the computer wakes up from
disk.

Kernel is:

Nov 17 20:32:18 neo kernel: [0.00] CPU0 microcode updated early to 
revision 0x1c, date = 2014-07-03
Nov 17 20:32:18 neo kernel: [0.00] Initializing cgroup subsys cpuset
Nov 17 20:32:18 neo kernel: [0.00] Initializing cgroup subsys cpu
Nov 17 20:32:18 neo kernel: [0.00] Initializing cgroup subsys cpuacct
Nov 17 20:32:18 neo kernel: [0.00] Linux version 3.16.0-4-amd64 
(debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP 
Debian 3.16.7-2 (2014-11-06)
Nov 17 20:32:18 neo kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/neo-root ro splash 
init=/bin/systemd splash


Here are a few of those oopses:

Nov 17 20:28:30 neo kernel: [141868.942923] BUG: unable to handle kernel NULL 
pointer dereference at 000c
Nov 17 20:28:30 neo kernel: [141868.943730] IP: [811ae3bd] 
lookup_real+0xd/0x50
Nov 17 20:28:30 neo kernel: [141868.944487] PGD c8a30067 PUD c6972067 PMD 0 
Nov 17 20:28:30 neo kernel: [141868.945197] Oops:  [#1] SMP 
Nov 17 20:28:30 neo kernel: [141868.945885] Modules linked in: sch_fq_codel 
ipt_MASQUERADE nfnetlink 8021q garp mrp nf_conntrack_netbios_ns 
nf_conntrack_broadcast nfsd auth_rpcgss oid_registry nfs_acl lockd sunrpc bnep 
bluetooth 6lowpan_iphc xt_tcpudp cpufreq_conservative cpufreq_userspace 
cpufreq_powersave cpufreq_stats ip6t_rpfilter ip6t_REJECT ipt_REJECT 
xt_conntrack cfg80211 rfkill ebtable_nat ebtable_broute bridge stp llc 
ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 
nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter 
ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat 
nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter 
ip_tables x_tables binfmt_misc tun nct6775 hwmon_vid uinput iTCO_wdt 
ipmi_watchdog iTCO_vendor_support x86_pkg_temp_thermal intel_powerclamp 
intel_rapl coretemp snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_realtek 
snd_hda_codec_generic ipmi_poweroff psmouse ipmi_de
 vintf pc
 spkr serio_raw ipmi_msghandler i2c_i801 fuse lpc_ich mfd_core snd_hda_intel 
snd_hda_controller battery snd_hda_codec tpm_infineon intel_smartconnect 
snd_hwdep tpm_tis mei_me tpm snd_pcm mei shpchp snd_timer evdev snd soundcore 
processor parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq sha256_ssse3 
sha256_generic algif_skcipher af_alg hid_generic usbhid hid dm_crypt md_mod 
ext4 crc16 jbd2 mbcache dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log 
dm_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common 
mxm_wmi ehci_pci crc32_pclmul xhci_hcd ehci_hcd crc32c_intel 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915 glue_helper 
ablk_helper ahci cryptd libahci i2c_algo_bit drm_kms_helper libata drm i2c_core 
scsi_mod r8169 mii usbcore usb_common fan thermal wmi video thermal_sys button
Nov 17 20:28:30 neo kernel: [141868.952810] CPU: 1 PID: 22011 Comm: unison 
Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.7-2
Nov 17 20:28:30 neo kernel: [141868.953748] Hardware name: MSI MS-7850/Z87-G41 
PC Mate(MS-7850), BIOS V1.8 07/21/2014
Nov 17 20:28:30 neo kernel: [141868.954695] task: 880109d19670 ti: 
8800c7964000 task.ti: 8800c7964000
Nov 17 20:28:30 neo kernel: [141868.955647] RIP: 0010:[811ae3bd]  
[811ae3bd] lookup_real+0xd/0x50
Nov 17 20:28:30 neo kernel: [141868.956606] RSP: 0018:8800c7967ce0  EFLAGS: 
00010282
Nov 17 20:28:30 neo kernel: [141868.957557] RAX: 880216a06018 RBX: 
880216a06018 RCX: 
Nov 17 20:28:30 neo kernel: [141868.958513] RDX:  RSI: 
880216a06018 RDI: 
Nov 17 20:28:30 neo kernel: [141868.959468] RBP: 880216a06018 R08: 
b5685b3d37a84d53 R09: 8802151de038
Nov 17 20:28:30 neo kernel: [141868.960424] R10: 000a R11: 
 R12: 880216a06018
Nov 17 20:28:30 neo kernel: [141868.961379] R13: 8800c7967e00 R14: 
ff9c R15: 7f540660a6b8
Nov 17 20:28:30 neo kernel: [141868.962336] FS:  7f54073bb700() 

Bug#765590: libdrm-intel1: 3D-graphics freeze using new libdrm-intel1

2014-10-24 Thread Vincent Bernat
 ❦ 16 octobre 2014 17:11 +0400, Max maxobser...@mail.ru :

 Today I've upgraded Debian successfully and everything was OK. But
 when I've started my OpenSceneGraph-based application with
 3d-graphics, OS stopped responding on mouse and keyboard. Htop utility
 stopped updating. Even keyboard stopped responding to Num-lock,
 Caps-lock etc. I've restarted my PC with Reset button, started my
 3d-application and got the same situation again.  I've worked on my
 OSG-based application for last 3-4 weeks. I did system upgrade every
 day and everything worked without any problems.

I got something similar while playing a video in XBMC. I reported the
bug upstream:
 https://bugs.freedesktop.org/show_bug.cgi?id=85412
-- 
Make the coupling between modules visible.
- The Elements of Programming Style (Kernighan  Plauger)


signature.asc
Description: PGP signature


Bug#765590: libdrm-intel1: 3D-graphics freeze using new libdrm-intel1

2014-10-24 Thread Vincent Bernat
 ❦ 24 octobre 2014 19:11 +0200, Vincent Bernat ber...@debian.org :

 Today I've upgraded Debian successfully and everything was OK. But
 when I've started my OpenSceneGraph-based application with
 3d-graphics, OS stopped responding on mouse and keyboard. Htop utility
 stopped updating. Even keyboard stopped responding to Num-lock,
 Caps-lock etc. I've restarted my PC with Reset button, started my
 3d-application and got the same situation again.  I've worked on my
 OSG-based application for last 3-4 weeks. I did system upgrade every
 day and everything worked without any problems.

 I got something similar while playing a video in XBMC. I reported the
 bug upstream:
  https://bugs.freedesktop.org/show_bug.cgi?id=85412

They suggest to apply commit 6c308fecb4d1f928d52f9586d976f79b37149388.
-- 
Don't diddle code to make it faster - find a better algorithm.
- The Elements of Programming Style (Kernighan  Plauger)


signature.asc
Description: PGP signature


Bug#758469: Enable CONFIG_FUNCTION_TRACER and friends

2014-08-17 Thread Vincent Bernat
Package: src:linux
Version: 3.16-1~exp1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

Please, enable CONFIG_FUNCTION_TRACER and friends
(CONFIG_FUNCTION_GRAPH_TRACER, CONFIG_STACK_TRACER). They are quite
useful to make tools like trace-cmd and tools from Brendan Gregg [1]
work.

https://github.com/brendangregg/perf-tools/

I understand this has been requested here:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563847

But this has been disabled because of:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568025

As Sparc is not a supported architecture anymore, the feature could be
reenabled.
 
- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT8QRjAAoJEJWkL+g1NSX5GDQP/1ctwsXl6M5RkUIAIiQDizim
k/LKwDILKjFAyea85dMuArTOGPcY+X+SxTREeW5rX0HTpHaZG8kxZ/isXCH6IRq8
yH7oIKFrfPPCtYzaWgAblraYyVpoEhA+F7BFXK3RNsBniIe1MwvF2f7o+sTnL8f/
uJ1jQWBAVQ6UeenjDcWKE9eEUn5W/Dw2Nws8Z90bPRBJj+TDZRYrUfEaY0mbuzzc
VK40cPuj8Q4NOIFOO2ewkigvtGfn17ovvdm8J4MLgFNORFwiSDOvNirzgO1Skb/8
viqj/J3b3o356jhjLQR6bH79Kit4v0TLNVyAtVrthV7wSDBqE5Y8k03mujK5/5zg
XCVZfR4kc2NLvBUMiCFI2MUTVyPHI9V7c76FyfGfIAaJOBymP8xx1GrRxOvDTrc1
y+qRNkT1A8ESuHkypFGqK3YnK+Q54B8dGr/essTd6k8uhJgpHAicpUB6d68hlOWa
8hmpQRqdenyvyX77rLJgAmaIY0Y9LjN3CbpcVLKEP5Jk5Jx046qiv6YfZOpAxEf/
tfPB1pP7yJCxcPg8f9BFHmdGvCdMqv+3/VwU5vgFZlszMcj/p12m/iYtwTEx3kUL
4Tc4E1FdiYDootP3JloO0j8Q4AZSLnE3nas6+BGoYkALUCnqpkJXNt07amHcQr4y
vO2HC+mNO8GSJxGoNEmY
=tDHz
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140817193711.22499.14741.report...@neo.luffy.cx



Bug#758469: Enable CONFIG_FUNCTION_TRACER and friends

2014-08-17 Thread Vincent Bernat
 ❦ 17 août 2014 21:37 +0200, Vincent Bernat ber...@debian.org :

 Please, enable CONFIG_FUNCTION_TRACER and friends
 (CONFIG_FUNCTION_GRAPH_TRACER, CONFIG_STACK_TRACER). They are quite
 useful to make tools like trace-cmd and tools from Brendan Gregg [1]
 work.

Also:

CONFIG_FTRACE_SYSCALLS=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_FTRACE_MCOUNT_RECORD=y

would be useful.
-- 
Use the good features of a language; avoid the bad ones.
- The Elements of Programming Style (Kernighan  Plauger)


signature.asc
Description: PGP signature


Bug#757813: Unload aufs module causes an oops

2014-08-11 Thread Vincent Bernat
Package: src:linux
Version: 3.16-1~exp1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

When unload aufs module, without using it first, I get this bug:

[ 2750.132114] [ cut here ]
[ 2750.133598] kernel BUG at /build/linux-4q9NiZ/linux-3.16/kernel/module.c:903!
[ 2750.135120] invalid opcode:  [#1] SMP
[ 2750.136630] Modules linked in: 8021q garp mrp nf_conntrack_netbios_ns 
nf_conntrack_broadcast xt_addrtype aufs(C-) bnep xt_CHECKSUM ipt_MASQUERADE tun 
xt_tcpudp ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_conntrack nfsd auth_rpcgss 
oid_registry nfs_acl lockd sunrpc cfg80211 ebtable_nat ebtable_broute bridge 
stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 
nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter 
ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat 
nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter 
ip_tables x_tables cpufreq_conservative cpufreq_userspace cpufreq_powersave 
cpufreq_stats binfmt_misc snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support 
x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp
[ 2750.141235]  kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm 
pcspkr ecb psmouse serio_raw i2c_i801 btusb bluetooth rfkill lpc_ich mfd_core 
snd_hda_intel shpchp snd_hda_controller mei_me i915 snd_hda_codec mei snd_hwdep 
snd_pcm snd_timer snd soundcore battery tpm_infineon tpm_tis tpm evdev uinput 
processor fuse parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq 
sha256_ssse3 sha256_generic dm_crypt md_mod nbd nouveau i2c_algo_bit 
drm_kms_helper ttm drm i2c_core ext4 crc16 jbd2 mbcache dm_snapshot dm_bufio 
dm_mirror dm_region_hash dm_log dm_mod hid_generic usbhid hid sg sd_mod 
crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common crc32_pclmul 
crc32c_intel ghash_clmulni_intel mxm_wmi aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd ahci libahci libata scsi_mod
[ 2750.144314]  ehci_pci r8169 mii ehci_hcd xhci_hcd usbcore usb_common fan 
thermal wmi video thermal_sys button
[ 2750.146406] CPU: 1 PID: 5404 Comm: modprobe Tainted: G C
3.16-trunk-amd64 #1 Debian 3.16-1~exp1
[ 2750.147460] Hardware name: MSI MS-7850/Z87-G41 PC Mate(MS-7850), BIOS V1.7 
05/30/2014
[ 2750.148540] task: 8801e125cac0 ti: 8800abf38000 task.ti: 
8800abf38000
[ 2750.149675] RIP: 0010:[810d17ea]  [810d17ea] 
__symbol_put+0x7a/0x80
[ 2750.150742] RSP: 0018:8800abf3bed0  EFLAGS: 00010246
[ 2750.151798] RAX:  RBX:  RCX: 0010
[ 2750.152892] RDX:  RSI:  RDI: a0af4bf0
[ 2750.154001] RBP: a0af8ce0 R08: 810cfc70 R09: 0008
[ 2750.154001] R10: 88021fa94d08 R11: 0006 R12: 0800
[ 2750.154001] R13: 0001 R14: 7ff56a1e5350 R15: 7ff56a1e53f0
[ 2750.154002] FS:  7ff568987700() GS:88021fa8() 
knlGS:
[ 2750.154002] CS:  0010 DS:  ES:  CR0: 80050033
[ 2750.154002] CR2: 0216ee70 CR3: 0001e1126000 CR4: 001407e0
[ 2750.154003] Stack:
[ 2750.154004]  814e3269  a0af8ce0 
0800
[ 2750.154004]  a0af1a7c a0af2f72 810d2354 
e125d110
[ 2750.154005]  a0af8ce0 0800 8800abf3bf0c 
73667561
[ 2750.154005] Call Trace:
[ 2750.154007]  [814e3269] ? mutex_lock+0x9/0x25
[ 2750.154011]  [a0af1a7c] ? au_loopback_fin+0xc/0x20 [aufs]
[ 2750.154012]  [a0af2f72] ? aufs_exit+0x16/0xa4 [aufs]
[ 2750.154013]  [810d2354] ? SyS_delete_module+0x154/0x210
[ 2750.154017]  [81012d99] ? do_notify_resume+0x59/0x90
[ 2750.154018]  [814e4caa] ? int_signal+0x12/0x17
[ 2750.154019]  [814e49ed] ? system_call_fast_compare_end+0x10/0x15
[ 2750.154026] Code: 00 48 8b 1d 29 60 7d 00 48 85 db 74 1c 48 8b 03 90 48 8b 
7b 08 48 83 c3 10 4c 89 e2 48 89 ee ff d0 48 8b 03 48 85 c0 75 e8 eb c4 0f 0b 
0f 1f 40 00 41 54 55 53 48 89 fb e8 44 f4 fa ff 85 c0 74
[ 2750.154027] RIP  [810d17ea] __symbol_put+0x7a/0x80
[ 2750.154027]  RSP 8800abf3bed0
[ 2750.159119] ---[ end trace 0960f3e1a55858bc ]---


- -- Package-specific info:
** Version:
Linux version 3.16-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-7) ) #1 SMP Debian 3.16-1~exp1 (2014-08-09)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16-trunk-amd64 root=/dev/mapper/neo-root ro 
acpi_osi=Linux init=/bin/systemd

** Tainted: DC (1152)
 * Kernel has oopsed before.
 * Module from drivers/staging has been loaded.

** Kernel log:
[   12.007250] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input15
[   12.007325] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[   12.007505] ACPI Warning: SystemIO range 

Re: Bug#750661: uninstallable

2014-06-28 Thread Vincent Bernat
 ❦ 28 juin 2014 12:22 +0300, Andrei POPESCU andreimpope...@gmail.com :

  Severity: grave
  
  seems to depend on absent linux-kbuild-3.15 
 
  As far as I understand, at this point you are expected to build your own 
  linux-kbuild package. Closing this bug, but CC -kernel in case they want 
  to comment.
 
 Why would a user be expected to build its own packages to satisfy a
 dependency? Why not provide the appropriate package in experimental?

 This is a question for the Kernel Team actually (CCd).

 Kind regards,
 Andrei (looking after bugs filed against unknown packages)

OK, I understood only later that the bug was reported against an unknown
package. I suppose that the original submitter did try to install kernel
headers some time after installing the kernel package itself.

Meantime, I have reassigned to src:linux with the appropriate version in
experimental. I have left the severity to grave but it seems a bit
excessive since it only affects experimental.

I have tried to build linux-kbuild-3.15 but this is not that easy.
-- 
die_if_kernel(Kernel gets FloatingPenguinUnit disabled trap, regs);
2.2.16 /usr/src/linux/arch/sparc/kernel/traps.c


signature.asc
Description: PGP signature


Bug#750661: uninstallable

2014-06-28 Thread Vincent Bernat
 ❦ 28 juin 2014 15:02 +0200, maximilian attems m...@stro.at :

 OK, I understood only later that the bug was reported against an unknown
 package. I suppose that the original submitter did try to install kernel
 headers some time after installing the kernel package itself.

 read ml for why not provided, in any case OOT modules are not
 recommended.

I suppose the answer is in this message:
 https://lists.debian.org/debian-kernel/2014/06/msg00255.html

It doesn't say much why the package is not in experimental while this
was the case in the past. It seems that this bug is recurrent so I
understand why you are scarce on details. There are several bugs about
this, like #573483 and its merged neighbors. So far, none of them seem
to tell why the package doesn't exist in experimental.

I tried to build it:

apt-get source linux-kbuild-3.14
cd linux-tools-3.14
uscan --report
(nothing)

debian/rules get-orig-source
(no such rule)

./debian/bin/genorig.py -V 3.15-1 ~/download/linux-3.15.1.tar.xz
Traceback (most recent call last):
  File ./debian/bin/genorig.py, line 202, in module
Main(args, options.override_version)()
  File ./debian/bin/genorig.py, line 60, in __init__
version = VersionLinux('%s-undef' % override_version)
  File debian/lib/python/debian_linux/debian.py, line 148, in __init__
raise RuntimeError(uInvalid debian linux version)
RuntimeError: Invalid debian linux version
(removing this undef on line 60)

Untar the tarball, copy debian/ and modify debian/changelog to tell
3.15.

One build failure about libudev missing, another one about usbip.h not
being here. I suppose I could dig a bit more but I am unsure of what to
do from here. I really don't know why usbip is the only stuff still in
drivers/ directory. I suppose this is on purpose since there is a patch
for that. I also suppose I could patch it to use kernel header instead
of uapi one.

It doesn't seem so easy to get such a package. While writing this email,
I noticed this was documented in this wiki page:
 
https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage#How_to_build_linux-kbuild-2.6_yourself

But no clue on the specific problem I get. So, not that easy.
-- 
printk(ufs_read_super: fucking Sun blows me\n);
2.0.38 /usr/src/linux/fs/ufs/ufs_super.c


signature.asc
Description: PGP signature


Bug#749273: Enable CONFIG_INTEL_SMARTCONNECT

2014-05-25 Thread Vincent Bernat
Package: src:linux
Version: 3.14.4-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

SmartConnect is a new feature from Intel allowing a computer to wake
up at regular interval to do some tasks like retrieving mails or stuff
like that.

On my PC, when enabled, it makes suspend or resume randomly
fail. There is a module to support this new feature. Currently, it
just disables it to avoid any problem since Linux doesn't know how to
handle that (I suppose this is not a regular wake up).

My guess is that compiling this module would avoid problems with
configurations like mine without disabling SmartConnect in the BIOS
(which may be difficult to know about).

- -- Package-specific info:
** Version:
Linux version 3.14-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.2 
(Debian 4.8.2-21) ) #1 SMP Debian 3.14.4-1 (2014-05-13)

** Command line:
BOOT_IMAGE=/vmlinuz-3.14-1-amd64 root=/dev/mapper/neo-root ro i8042.reset=1 
acpi_osi=Linux init=/bin/systemd

** Tainted: WCO (5632)
 * Taint on warning.
 * Module from drivers/staging has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[353899.448375] pci :03:00.0:   bridge window [mem 0xdf60-0xdf7f]
[353899.448380] pci :03:00.0:   bridge window [mem 0xdf80-0xdf9f 
64bit pref]
[353899.448392] pci :03:00.0: no hotplug settings from platform
[353900.501910] r8169 :02:00.0 eth0: link up
[353900.788033] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[353904.523048] Suspending console(s) (use no_console_suspend to debug)
[353904.523351] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[353904.523362] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[353904.523512] sd 0:0:0:0: [sda] Stopping disk
[353904.546738] sd 1:0:0:0: [sdb] Stopping disk
[353904.624080] hub 1-0:1.0: port 4 not suspended yet
[353905.624118] PM: suspend of devices complete after 1100.960 msecs
[353905.624201] PM: late suspend of devices complete after 0.081 msecs
[353905.624401] r8169 :02:00.0: System wakeup enabled by ACPI
[353905.640098] ehci-pci :00:1d.0: System wakeup enabled by ACPI
[353905.644117] ehci-pci :00:1a.0: System wakeup enabled by ACPI
[353905.652045] xhci_hcd :00:14.0: System wakeup enabled by ACPI
[353905.656399] PM: noirq suspend of devices complete after 32.196 msecs
[353905.656591] ACPI: Preparing to enter system sleep state S3
[353905.656821] PM: Saving platform NVS memory
[353905.657347] Disabling non-boot CPUs ...
[353905.658553] kvm: disabling virtualization on CPU1
[353905.760020] smpboot: CPU 1 is now offline
[353905.761457] kvm: disabling virtualization on CPU2
[353905.864010] smpboot: CPU 2 is now offline
[353905.865370] kvm: disabling virtualization on CPU3
[353905.968010] smpboot: CPU 3 is now offline
[353905.968111] ACPI: Low-level resume complete
[353905.968111] PM: Restoring platform NVS memory
[353905.968111] Enabling non-boot CPUs ...
[353905.968111] x86: Booting SMP configuration:
[353905.968111] smpboot: Booting Node 0 Processor 1 APIC 0x2
[353905.658554] kvm: enabling virtualization on CPU1
[353905.980382] Intel pstate controlling: cpu 1
[353905.980416] CPU1 is up
[353905.980469] smpboot: Booting Node 0 Processor 2 APIC 0x4
[353905.761459] kvm: enabling virtualization on CPU2
[353905.992491] Intel pstate controlling: cpu 2
[353905.992521] CPU2 is up
[353905.992575] smpboot: Booting Node 0 Processor 3 APIC 0x6
[353905.865371] kvm: enabling virtualization on CPU3
[353906.004606] Intel pstate controlling: cpu 3
[353906.004636] CPU3 is up
[353906.007136] ACPI: Waking up from system sleep state S3
[353906.016045] xhci_hcd :00:14.0: System wakeup disabled by ACPI
[353906.024042] ehci-pci :00:1a.0: System wakeup disabled by ACPI
[353906.032040] ehci-pci :00:1d.0: System wakeup disabled by ACPI
[353906.052234] PM: noirq resume of devices complete after 44.635 msecs
[353906.052338] PM: early resume of devices complete after 0.086 msecs
[353906.052426] snd_hda_intel :00:03.0: irq 43 for MSI/MSI-X
[353906.052497] mei_me :00:16.0: irq 45 for MSI/MSI-X
[353906.052582] r8169 :02:00.0: System wakeup disabled by ACPI
[353906.052725] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X
[353906.094429] r8169 :02:00.0 eth0: link down
[353906.396058] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[353906.396856] ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
[353906.496373] ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
[353906.496432] ata2.00: configured for UDMA/133
[353906.496609] sd 1:0:0:0: [sdb] Starting disk
[353907.804061] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[353907.850450] r8169 :02:00.0 eth0: link up
[353911.428041] ata1: link is slow to respond, please be patient (ready=0)
[353911.932060] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[353911.965782] ata1.00: configured for UDMA/133
[353911.965846] sd 0:0:0:0: [sda] Starting disk
[353911.977187] PM: resume of devices complete after 5924.848 msecs

Bug#737423: qemu-system-x86_64: virtio: trying to map MMIO memory

2014-02-02 Thread Vincent Bernat
Package: src:linux
Version: 3.12.8-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

When running the current Linux kernel from unstable in kvm with a 9P
rootfs, I get this message during udev settle:

  qemu-system-x86_64: virtio: trying to map MMIO memory

I have searched a bit and it seems to be a bug in the virtio
driver. See the following thread:

 http://www.spinics.net/lists/linux-virtualization/msg21650.html

The report is consistent with what I see as I suppose that during udev
settle, some modules are probed. I don't quite understand if the fix
is already here or not.

If you need to reproduce, this is quite easy. Execute the following
self-contained script:
 https://github.com/vincentbernat/network-lab/blob/master/lab-generic/setup

- -- Package-specific info:
** Version:
Linux version 3.12-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.2 
(Debian 4.8.2-10) ) #1 SMP Debian 3.12.6-2 (2013-12-29)

** Command line:
BOOT_IMAGE=/vmlinuz-3.12-1-amd64 root=/dev/mapper/guybrush-root ro quiet 
init=/bin/systemd

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[195470.669662] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:60:c5:47:7b:a5:b4:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=25958 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195489.719868] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:bc:52:b7:1b:42:de:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=45281 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195490.846351] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:04:f7:e4:ba:a5:67:08:00 
SRC=192.168.101.113 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=997 
PROTO=UDP SPT=5353 DPT=5353 LEN=57 
[195490.846505] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:04:f7:e4:ba:a5:67:08:00 
SRC=192.168.101.113 DST=224.0.0.251 LEN=103 TOS=0x00 PREC=0x00 TTL=255 ID=55790 
PROTO=UDP SPT=5353 DPT=5353 LEN=83 
[195491.665722] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:04:f7:e4:ba:a5:67:08:00 
SRC=192.168.101.113 DST=224.0.0.251 LEN=103 TOS=0x00 PREC=0x00 TTL=255 ID=16828 
PROTO=UDP SPT=5353 DPT=5353 LEN=83 
[195491.768176] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:04:f7:e4:ba:a5:67:08:00 
SRC=192.168.101.113 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=20581 
PROTO=UDP SPT=5353 DPT=5353 LEN=57 
[195493.714157] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:04:f7:e4:ba:a5:67:08:00 
SRC=192.168.101.113 DST=224.0.0.251 LEN=103 TOS=0x00 PREC=0x00 TTL=255 ID=47196 
PROTO=UDP SPT=5353 DPT=5353 LEN=83 
[195503.956395] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:5c:96:9d:41:6e:9d:08:00 
SRC=10.99.7.185 DST=224.0.0.251 LEN=251 TOS=0x00 PREC=0x00 TTL=255 ID=33445 
PROTO=UDP SPT=5353 DPT=5353 LEN=231 
[195503.956595] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:5c:96:9d:41:6e:9d:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=1051 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195525.874540] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:f0:c1:f1:b2:d4:1e:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=58543 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195528.537383] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:f0:c1:f1:b2:d4:1e:08:00 
SRC=192.168.101.114 DST=224.0.0.251 LEN=134 TOS=0x00 PREC=0x00 TTL=255 ID=51002 
PROTO=UDP SPT=5353 DPT=5353 LEN=114 
[19.229302] IN=docker0 OUT= MAC= SRC=172.17.42.1 DST=172.17.255.255 LEN=247 
TOS=0x00 PREC=0x00 TTL=64 ID=46280 DF PROTO=UDP SPT=138 DPT=138 LEN=227 
[19.229368] IN=docker0 OUT= MAC= SRC=172.17.42.1 DST=172.17.255.255 LEN=237 
TOS=0x00 PREC=0x00 TTL=64 ID=46281 DF PROTO=UDP SPT=138 DPT=138 LEN=217 
[195556.191934] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:4c:8d:79:0c:d0:4e:08:00 
SRC=192.168.101.107 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=21204 
PROTO=UDP SPT=5353 DPT=5353 LEN=57 
[195561.109412] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:f0:f6:1c:3a:b4:84:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=10710 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195562.233976] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:f0:f6:1c:3a:b4:84:08:00 
SRC=192.168.101.100 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=31442 
PROTO=2 
[195581.284030] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:f0:f6:1c:6b:f3:39:08:00 
SRC=192.168.101.120 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39414 
PROTO=2 
[195582.820537] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:7c:c5:37:7c:c3:b8:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=22420 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195584.869565] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:54:e4:3a:e4:25:e3:08:00 
SRC=192.168.1.8 DST=224.0.0.251 LEN=99 TOS=0x00 PREC=0x00 TTL=255 ID=61376 
PROTO=UDP SPT=5353 DPT=5353 LEN=79 
[195584.869845] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:54:e4:3a:e4:25:e3:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=58421 
PROTO=UDP SPT=68 DPT=67 LEN=308 
[195584.870143] IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:54:e4:3a:e4:25:e3:08:00 
SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=58422 

Bug#724976: Use CFLAGS=-grecord-gcc-switches to help debugging

2013-09-30 Thread Vincent Bernat
Source: linux
Version: 3.10.11-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

Tools, like systemtap, need to circumvent some bugs in GCC, notably in
the way it reports debugging data for highly-optimized programs. For
example, the use of -mfentry flag can cause troubles. Systemtap
includes workarounds but they are only reliable when the kernel is
using some options. Therefore, systemtap needs to know with which
option GCC was invoked.

This can be done by using CFLAGS=-grecord-gcc-switches.

Currently, there is no known bug in GCC that would need to be
workaround. However, when a bug is spotted, it is usually too late to
ask for a workaround by including this flag. So, I think this flag
could be added for all next uploads to help future debugging.

Thanks.


- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBCAAGBQJSSSDwAAoJEJWkL+g1NSX5PIMP/2e/jG1Hau6WIqhzrT9vuG3M
mk7RSKYKaV7hjv5S/7kuIbnz5SLK5MytExWcJuH26kVIW3LOE/BqP4jqjJkJsdx6
gKz8L9MBZLjNS/ItU/mVxF6FmDU5Zu4PR8vFzEob7lZNQdxHhZ1iLDlxKBcET360
ORc5UytiNRywtRnFQsKSWuPk0+E6nkQ7wZ72WsqO4DG+xSGgLnzkJ2dP2KI/ScOQ
j2q7xRPvaB7Pxs1ZfQvEJbSLXEDYf0RLusS/i1f4uzmaC8zE2H3E0PqP5E/n7I/J
z4FJQMJcxaAr4FD/10lEm5Ns2VqFEPjKH/KEh8kmcLv9s05BSATLx46AN5GIHrqz
LKNZN0j9j5OcQUzTIDBpph5yNgemsbYkSgDmpiTDw7bcArqlRTSTCyZ3dQQt65oR
ISYawFC8yQRNZoKxaZy3v4btvaToWFuXMS+8RxYTT3pMg95ucLhSyT/O2y7nGBVg
p7IMhQZhtTu/FxH1TjmAl0MyU1wwa5h9Z7wMSeIVrjrp4VPUdGcq5/rMeL8iII1W
iiRiIc32hrZev+vRG7kJ1Ru5+gr9gjFnXgsQwgfR+jv4Wxb9hfUbHIUR2QtrTAAw
Y++/OfNRfzy8+bmuP6ZfKn1uJ9+Nc+JUrHh075E66WWDzFqBB5TVQ7l/0ptkwW7/
NM2wpLyCgIiYwxjedKsp
=8mZG
-END PGP SIGNATURE-


-- 
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/20130930065756.18212.29191.report...@neo.luffy.cx



Bug#694884: Enable CONFIG_DYNAMIC_DEBUG

2012-12-01 Thread Vincent Bernat
Package: src:linux
Version: 3.6.8-1~experimental.1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

It would be neat to enable CONFIG_DYNAMIC_DEBUG in Debian kernel. This
would allow one to dynamically enable more verbose output to debug a
problem in the kernel with no performance impact for users not
fiddling with this parameter.

The no performance impact comes from this document (section 4):
 http://kernel.org/doc/ols/2009/ols2009-pages-39-46.pdf

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQulVlAAoJEJWkL+g1NSX5TG8P+wTB+XyLsz4laTUOVrc9FmzK
bFAjsF/XVsWg82owopKWX5Ee+7sbKISNcsrO2jGFlG82EVx8nA5tMPnoOKXocLaA
dlzIY1TA7OPfDUzTCCQDxQ0WhhKnGvsXqUXvLxnmE0GQndJLLGJVqCg1WigwyB3j
Rwr4DV2L0eAbWEesZX2U+Db1zMMmjaqVHwdrZq9dzjeZp4N3KpV4rmrL/r3P5kZg
zZpsoau10acrtgn0Ah+Oxm1q6nfw+s89qgtclgHfN5Qd//27lqSafWY7KUO5+L9z
D1Q05J68iedaK12Uh1+B3TjPTzSJ/tSan/E+T+8iedO6tggAfum9Cd0oeDQjjkyY
CInU8Omv50cED5CHJBNW9FKkEmY3vzrLvHwV5bSsPceBxHqqNdzYSQ/oEleU3n2m
LdmZ5LyjxbiqTGpfi+jDONNPbx4Wieg5bWLRkcrx3D8/8UphdzXaMlaHA2594wwA
HgTodvbBiWKadcWbZbF4DBJCHfV2dDnfnFXjAHaXWG2ZXtQKJhM1IwTKnUh2HxsI
hILmxbyyx2FDfCHj6RKJbhW/91UnvMR4qEliRDltSqKGDzK+vJJIzFrBn3BaO5wH
yJN4hs0Z96QN9nXJnObXUHHKKLtyRZpXVCakq83m8/Gs3eCRBJET/d8V0U1Zq1ZQ
6PKEP1bmCtP3dfpoA4uC
=UULy
-END PGP SIGNATURE-


-- 
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/20121201190722.7256.15040.report...@neo.luffy.cx



Bug#689962: linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y

2012-10-13 Thread Vincent Bernat
 ❦  8 octobre 2012 15:27 CEST, Vincent Bernat ber...@debian.org :

 When using a virtio console, we cannot get early boot messages since
 it is only available as a module. Wouldn't it make sense to compile it
 in-kernel to get the same behaviour as with a serial console?

In fact, as of 3.6, it is not possible to use virtconsole as an initial
console. I don't know if this will be fixed later but this makes the bug
for this specific kernel moot.

Feel free to close if you think there is nothing to do here.

Thanks.
-- 
printk(KERN_ERR msp3400: chip reset failed, penguin on i2c bus?\n);
2.2.16 /usr/src/linux/drivers/char/msp3400.c


pgpz2l8wvJFew.pgp
Description: PGP signature


Bug#689962: linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y

2012-10-08 Thread Vincent Bernat
Package: linux-image-3.2.0-4-amd64
Version: 3.2.30-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

When using a virtio console, we cannot get early boot messages since
it is only available as a module. Wouldn't it make sense to compile it
in-kernel to get the same behaviour as with a serial console?

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

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQctS5AAoJEJWkL+g1NSX5Se4P/05wBAIPeTcq3rCTXcTeC1JE
jIhLlNy/IOoyb+rPOAn0ZZxteqw1kUgqQATwfj0reClx/TPGUWkIw5K1fnAlHLYh
zI88YYF9ISalCTQsmV/XTxGxQhH+lMeYD8NLqDaIdIN2I71x/tyiwnfyI8u4VMI2
cnW7F1zn1/m2ACAzYY9zIP5UJmU0vAYjOveMXvo+p+FxUd/9fko6TzqNYi2fIwxu
NBKgTW1j/NJT2dxU+00KUepgLZf1a0IqX/rfTVTNvdoVUouHIp73FsiQLCVE/Thm
uEVk4hkSaoF0IU6Q3KBi7bAhC1XY43G/OxRvM5OTTseEId+oCWuLSYRvim1NevDp
MknIoxhmBrdSlcI3K/tEl7eUXcTMntKjAhsyop4TXQC4+O0ZjbY5O1pww9+i/PtU
uL3vv1EMa/7aN7HWKmPNY3mvMgwJSPZqk2jsACqWtY5N6G05RRL5hoTFsOALILyE
+bk0VoXgJjhMcseXeyD8YL/XsjpEvm0NXpn/jJOmsEfqmobJzGMAijCXHHfO8Zk1
Q0L9jsxqYY73Ela7mhz973jkME93abQhSrZ5/PuiYgEdWoH1mAupL4D7gil/m+jP
Te1j651KcD6CTeKjug7IsoxhlvovHeoGePpk6wSDbdylnTutu4B9cR6JX1Z1PEBo
NdW1MGiUqHdWLOWa6eps
=PZqV
-END PGP SIGNATURE-


-- 
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/20121008132726.14397.67082.report...@guybrush.luffy.cx



Re: Increasing minimum 'i386' processor

2011-11-22 Thread Vincent Bernat
OoO Lors de  la soirée naissante du mardi 22  novembre 2011, vers 18:28,
Bastian Blank wa...@debian.org disait :

  The 486-class processors that would no longer be supported are:
  1. All x86 processors with names including '486'
 I'm still running the machine below, and it would be irritating to
 have to replace it.

 vendor_id: CentaurHauls
 model name   : VIA Samuel 2

 I don't see any 486 in this name.

This processor  does not run with a  686 kernel and needs  a 486 kernel.
If   I  remember   correctly,   it   is  because   the   lack  of   CMOV
instruction. Therefore, no problem with 586.
-- 
Vincent Bernat ☯ http://vincent.bernat.im

Indent to show the logical structure of a program.
- The Elements of Programming Style (Kernighan  Plauger)


pgpjR0ImIUXpH.pgp
Description: PGP signature


Bug#629401: linux-image-2.6.39-1-amd64: Enable CONFIG_IP_SET

2011-06-06 Thread Vincent Bernat
Package: linux-2.6
Version: 2.6.39-1+b1
Severity: wishlist

Hi!

Please include CONFIG_IP_SET. This allows use of sets of IP with
Netfilter. Those sets can be modified on the fly with ipset (whose
correct version is not yet packaged in Debian). 

-- Package-specific info:
** Version:
Linux version 2.6.39-1-amd64 (Debian 2.6.39-1) 
(buildd_amd64-bra...@buildd.debian.org) (gcc version 4.4.6 (Debian 4.4.6-3) ) 
#1 SMP Tue May 24 14:34:19 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.39-1-amd64 root=/dev/mapper/naruto-root ro quiet splash

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[4.792165] generic-usb 0003:0A5C:4502.0003: input,hidraw2: USB HID v1.11 
Keyboard [HID 0a5c:4502] on usb-:00:1a.7-1.4.1/input0
[4.864132] usb 1-1.4.2: new full speed USB device number 6 using ehci_hcd
[4.958758] usb 1-1.4.2: New USB device found, idVendor=0a5c, idProduct=4503
[4.958761] usb 1-1.4.2: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[4.961418] input: HID 0a5c:4503 as 
/devices/pci:00/:00:1a.7/usb1/1-1/1-1.4/1-1.4.2/1-1.4.2:1.0/input/input5
[4.961472] generic-usb 0003:0A5C:4503.0004: input,hidraw3: USB HID v1.11 
Mouse [HID 0a5c:4503] on usb-:00:1a.7-1.4.2/input0
[5.032135] usb 1-1.4.3: new full speed USB device number 7 using ehci_hcd
[5.127503] usb 1-1.4.3: New USB device found, idVendor=0a5c, idProduct=2148
[5.127507] usb 1-1.4.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[5.127509] usb 1-1.4.3: Product: BCM92046DG-CL1ROM
[5.127511] usb 1-1.4.3: Manufacturer: Broadcom Corp
[5.127513] usb 1-1.4.3: SerialNumber: 000272A8445E
[5.671740] udevd[321]: starting version 170
[6.116519] wmi: Mapper loaded
[6.122370] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[6.150273] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 
18
[6.208632] ACPI: acpi_idle registered with cpuidle
[6.213186] Monitor-Mwait will be used to enter C-1 state
[6.215367] parport_pc 00:06: reported by Plug and Play ACPI
[6.215420] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[6.228771] input: Dell WMI hotkeys as /devices/virtual/input/input6
[6.726304] Bluetooth: Core ver 2.16
[6.726322] NET: Registered protocol family 31
[6.726323] Bluetooth: HCI device and connection manager initialized
[6.726325] Bluetooth: HCI socket layer initialized
[6.726327] Bluetooth: L2CAP socket layer initialized
[6.726362] Bluetooth: SCO socket layer initialized
[6.757542] Bluetooth: Generic Bluetooth USB driver ver 0.6
[6.757686] usbcore: registered new interface driver btusb
[6.788582] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 
16
[6.788625] HDA Intel :00:1b.0: irq 50 for MSI/MSI-X
[6.788647] HDA Intel :00:1b.0: setting latency timer to 64
[7.345492] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input7
[8.164013] CE: hpet4 increased min_delta_ns to 7500 nsec
[8.164019] CE: hpet4 increased min_delta_ns to 11250 nsec
[8.488911] EXT3-fs (dm-0): using internal journal
[8.618898] loop: module loaded
[9.503199] Adding 511996k swap on /dev/mapper/naruto-swap_1.  Priority:-1 
extents:1 across:511996k 
[   12.044003] CE: hpet2 increased min_delta_ns to 7500 nsec
[   12.044011] CE: hpet2 increased min_delta_ns to 11250 nsec
[   12.044014] hrtimer: interrupt took 5350 ns
[   12.404005] CE: hpet3 increased min_delta_ns to 7500 nsec
[   12.404011] CE: hpet3 increased min_delta_ns to 11250 nsec
[   12.415423] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: 
(null)
[   12.420030] EXT3-fs: barriers not enabled
[   12.421921] kjournald starting.  Commit interval 5 seconds
[   12.422483] EXT3-fs (dm-4): using internal journal
[   12.422487] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[   12.450120] EXT3-fs: barriers not enabled
[   12.457774] kjournald starting.  Commit interval 5 seconds
[   12.457971] EXT3-fs (dm-2): using internal journal
[   12.457975] EXT3-fs (dm-2): mounted filesystem with ordered data mode
[   12.483022] EXT3-fs: barriers not enabled
[   12.490909] kjournald starting.  Commit interval 5 seconds
[   12.491121] EXT3-fs (dm-3): using internal journal
[   12.491125] EXT3-fs (dm-3): mounted filesystem with ordered data mode
[   12.503416] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: 
(null)
[   12.538334] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: 
(null)
[   12.668878] EXT3-fs: barriers not enabled
[   12.669037] kjournald starting.  Commit interval 5 seconds
[   12.669209] EXT3-fs (sda5): using internal journal
[   12.669213] EXT3-fs (sda5): mounted filesystem with ordered data mode
[   15.541556] Bridge firewalling registered
[   15.587790] device eth0 entered promiscuous mode
[   15.652526] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.654966] 

Bug#521515: This also affects the build of userland programs

2009-04-25 Thread Vincent Bernat
Hi!

This bug also affects how some userland programs are built. For example,
keepalived  checks kernel version  and presence  of net/ip_vs.h  file. I
suppose that there exists other  programs that need kernel include files
not available from libc.

Since 2.6.29, configuring keepalived will not build IPVS support because
ip_vs.h file  is not  found. If --kernel-dir  is passed  to ./configure,
then, it is  unable to find the kernel version  because while ip_vs.h is
in -common, utsrelease.h is in -amd64 (for example).

Debian package circumvents this  difficulty by shipping ip_vs.h. But the
point  is that  a lambda  user will  have difficulties  to  compile this
program from upstream sources.
-- 
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE SEIZURES
-+- Bart Simpson on chalkboard in episode 8F23


pgpsbGEklVmXO.pgp
Description: PGP signature


Bug#418977: initramfs-tools: Missing esp.ko module for SCSI controller on Sparc

2007-04-13 Thread Vincent Bernat
Package: initramfs-tools
Version: 0.85g
Severity: important
Tags: patch

Hi !

esp.ko is missing from SCSI drivers installed in initrd. On a Sparc 4,
this leads to being unable to mount the root file system.


-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/debian-root ro resume=/dev/sda1 vga=791 

-- /proc/filesystems
ext3

-- lsmod
Module  Size  Used by
saa7134   135464  0 
ir_kbd_i2c 12560  1 saa7134
button 11296  0 
psmouse42192  0 
nvidia   7750232  32 
ac  8200  0 
battery13256  0 
tun14336  3 
sit14248  0 
ipv6  291712  17 sit
acpi_cpufreq   11912  1 
cpufreq_ondemand   11472  1 
freq_table  7680  2 acpi_cpufreq,cpufreq_ondemand
tuner  63976  0 
ide_cd 43232  0 
cdrom  38312  1 ide_cd
tsdev  11008  0 
usbhid 28256  0 
usblp  17152  0 
snd_hda_intel  23648  3 
snd_hda_codec 198080  1 snd_hda_intel
snd_pcm_oss46816  0 
snd_mixer_oss  19712  1 snd_pcm_oss
snd_pcm86664  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy   6532  0 
snd_seq_oss34944  0 
snd_seq_midi   11584  0 
snd_rawmidi28896  1 snd_seq_midi
snd_seq_midi_event 10496  2 snd_seq_oss,snd_seq_midi
snd_seq57024  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  26632  3 snd_pcm,snd_seq
snd_seq_device 10964  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
video_buf  29188  1 saa7134
compat_ioctl32 11136  1 saa7134
snd64360  14 
snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
ir_common  35140  2 saa7134,ir_kbd_i2c
videodev   29760  1 saa7134
jmicron 7232  0 [permanent]
evdev  13376  4 
soundcore  11296  1 snd
v4l2_common27968  4 saa7134,tuner,compat_ioctl32,videodev
v4l1_compat14404  2 saa7134,videodev
pcspkr  5824  0 
serio_raw   9924  0 
i2c_i801   11092  0 
i2c_core   26432  5 saa7134,ir_kbd_i2c,nvidia,tuner,i2c_i801
uhci_hcd   27096  0 
snd_page_alloc 12752  2 snd_hda_intel,snd_pcm
intel_agp  28544  1 
ide_core  143140  2 ide_cd,jmicron
ehci_hcd   34572  0 
r8169  34248  0 
ata_generic11524  0 
thermal18064  0 
processor  37160  2 acpi_cpufreq,thermal
fan 7816  0 
ext3  127184  6 
mbcache12104  1 ext3
jbd66352  1 ext3
dm_snapshot19400  0 
dm_mirror  24000  0 
dm_mod 63504  13 dm_snapshot,dm_mirror
lzf 5696  0 
sd_mod 22912  4 
ahci   26308  3 
libata113504  2 ata_generic,ahci
scsi_mod  114616  3 sd_mod,ahci,libata

-- kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes

postinst_hook = /usr/sbin/update-grub
postrm_hook = /usr/sbin/update-grub
do_bootloader = no
do_initrd = Yes


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

Kernel: Linux 2.6.20-rc4-neo.3 (SMP w/2 CPU cores)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.1.3-4  Tiny utilities for small and embed
ii  cpio  2.6-17 GNU cpio -- a program to manage ar
ii  klibc-utils   1.5-2  small statically-linked utilities 
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  udev  0.105-4/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information
--- initramfs-tools-0.85g/hook-functions~   2006-12-19 14:49:53.0 
+0100
+++ initramfs-tools-0.85g/hook-functions2007-04-13 08:14:01.0 
+0200
@@ -185,7 +185,7 @@
for x in 3w-9xxx 3w- a100u2x aacraid advansys ahci \
aic79xx aic7xxx aic94xx arcmsr ata_piix atari_scsi \
atp870u BusLogic cciss ch cpqarray DAC960 dc395x \
-   dmx3191d dpt_i2o eata fdomain gdth hptiop ibmvscsic \
+   dmx3191d dpt_i2o eata esp fdomain gdth hptiop ibmvscsic \
initio ipr ips isp1020 lasi700 lpfc max_scsi mac53c94 \
megaraid megaraid_mbox megaraid_mm megaraid_sas \
 

Bug#379660: 2.6.17-5 still not corrected

2006-08-03 Thread Vincent Bernat
OoO Lors de la soirée naissante  du jeudi 03 août 2006, vers 18:04, je
disais:

 Even if the changelog says  that 2.6.17-5 is up-to-date with 2.6.17.7,
 this is not the case. The patch available here :
  http://marc.theaimsgroup.com/?l=linux-kernelm=115315508506996w=2
 still applies.

Sorry, the patch was correctly applied. My mistake.
-- 
panic(huh?\n);
2.2.16 /usr/src/linux/arch/i386/kernel/smp.c



Bug#379660: 2.6.17-5 still not corrected

2006-08-03 Thread Vincent Bernat
Hi,

Even if the changelog says  that 2.6.17-5 is up-to-date with 2.6.17.7,
this is not the case. The patch available here :
 http://marc.theaimsgroup.com/?l=linux-kernelm=115315508506996w=2
still applies.
-- 
Use data arrays to avoid repetitive control sequences.
- The Elements of Programming Style (Kernighan  Plauger)


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



Bug#378204: linux-image-2.6.17-1-486: oops when loading 8250_pnp with output redirected to the serial console

2006-07-14 Thread Vincent Bernat
Package: linux-image-2.6.17-1-486
Version: 2.6.17-3
Severity: normal

Hi !

I get the following oops when the kernel is booting with its output
redirected to serial console :

LILO 22.6.1 Loading
Linux...
BIOS data check successful
Linux version 2.6.17-1-486 (Debian 2.6.17-3) ([EMAIL PROTECTED]) (gcc
version 4.1.2 20060708 (prerelease) (Debian 4.1.1-8)) #1 Thu Jul 13
14:04:16 UTC 2006
BIOS-provided physical RAM map:
 BIOS-e820:  - 000a (usable)
  BIOS-e820: 000f - 0010 (reserved)
   BIOS-e820: 0010 - 0f80 (usable)
BIOS-e820:  - 0001 (reserved)
248MB LOWMEM available.
DMI 2.2 present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 1000 (gap:
0f80:f07f)
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=Linux ro root=302 console=tty0
console=ttyS0,115200n8
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Detected 533.440 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 24k/253952k available (1452k kernel code, 9020k reserved,
558k data, 228k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay using timer specific routine.. 1068.77 BogoMIPS
(lpj=2137545)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: Centaur VIA Samuel 2 stepping 03
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 0k freed
checking if image is initramfs... it is
Freeing initrd memory: 4091k freed
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=1
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xb00fbda0
PnPBIOS: PnP BIOS version 1.0, entry 0xf:0xbdd0, dseg 0xf
PnPBIOS: 11 nodes reported by PnP BIOS; 11 recorded by driver
PCI: Probing PCI hardware
PCI: Using IRQ router default [1106/0601] at :00:00.0
PCI: Bridge: :00:01.0
  IO window: disabled.
MEM window: e000-e2ff
  PREFETCH window: 1000-100f
  NET: Registered protocol family 2
  IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
  TCP established hash table entries: 8192 (order: 3, 32768 bytes)
  TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
  TCP: Hash tables configured (established 8192 bind 4096)
  TCP reno registered
  audit: initializing netlink socket (disabled)
  audit(1152861071.260:1): initialized
  VFS: Disk quotas dquot_6.5.1
  Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
  Initializing Cryptographic API
  io scheduler noop registered
  io scheduler anticipatory registered (default)
  io scheduler deadline registered
  io scheduler cfq registered
  isapnp: Scanning for PnP cards...
  isapnp: No Plug  Play device found
  Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
EISA: Probing bus 0 at eisa.0
EISA: Detected 0 cards.
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI Shortcut mode
Freeing unused kernel memory: 228k freed
Loading, please wait...
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
FATAL: Error inserting fan
(/lib/modules/2.6.17-1-486/kernel/drivers/acpi/fan.ko): No such device
FATAL: Error inserting thermal
(/lib/modules/2.6.17-1-486/kernel/drivers/acpi/thermal.ko): No such
device
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
eth0: VIA Rhine II at 0x1dc00, 00:40:63:c0:b9:a6, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link
45e1.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx

Bug#376941: initramfs-tools: crypttab not handled correctly

2006-07-05 Thread Vincent Bernat
Package: initramfs-tools
Version: 0.67
Severity: normal

Hi !

While /etc/crypttab allows key and options to be left blank,
initramfs-tools says this when this happens :
/usr/share/initramfs-tools/hooks/cryptroot: failed to determine cipher options 
to use


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.1-zoro.12
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.1.3-2  Tiny utilities for small and embed
ii  cpio  2.6-15 GNU cpio -- a program to manage ar
ii  klibc-utils   1.4.8-1small statically-linked utilities 
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo
ii  udev  0.093-1/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information


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



Bug#321236: Should not kernel-image-2.6.8-2-sparc64 compiled with CONFIG_IP_ADVANCED_ROUTER ?

2005-08-10 Thread Vincent Bernat
reassign 321236 linux-image-2.6.12-1-sparc64
thanks

OoO En cette fin de nuit blanche du vendredi 05 août 2005, vers 05:18,
Horms [EMAIL PROTECTED] disait:

 Package: kernel-image-2.6.8-2-sparc64
 Version: 2.6.8-15
 Severity: wishlist
 
 kernel-image-2.6.8-2-sparc64 is compiled without CONFIG_IP_ADVANCED_ROUTER
 contrary to other architectures (at least 686 and k7). Is it possible to
 add this option ?

 The 2.6.8 kernel is basically in maintenance mode for Sarge.
 And as such enabling of new options isn't really on the cards.
 Is it possible for you to try one of the newer upstream kernel
 versions that are available in unstable. kernel-image-2.6.11-1-sparc64.
 2.6.12 is also on its way, likely as linux-image-2.6.12-1-sparc64.
 Watch this space http://ftp.debian.org/debian/pool/main/l/linux-2.6/

2.6.12-1 does not have CONFIG_IP_ADVANCED_ROUTER too.
-- 
10.0 times 0.1 is hardly ever 1.0.
- The Elements of Programming Style (Kernighan  Plauger)



Bug#321236: Should not kernel-image-2.6.8-2-sparc64 compiled with CONFIG_IP_ADVANCED_ROUTER ?

2005-08-04 Thread Vincent Bernat
Package: kernel-image-2.6.8-2-sparc64
Version: 2.6.8-15
Severity: wishlist

kernel-image-2.6.8-2-sparc64 is compiled without CONFIG_IP_ADVANCED_ROUTER
contrary to other architectures (at least 686 and k7). Is it possible to
add this option ?

-- System Information:
Debian Release: 3.1
Architecture: sparc (sparc64)
Kernel: Linux 2.6.8-2-sparc64
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kernel-image-2.6.8-2-sparc64 depends on:
ii  initrd-tools  0.1.81.1   tools to create initrd image for p
ii  module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information


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