Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

[Stefan Pietsch]

On 30.12.22 11:42, Diederik de Haas wrote:

On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote:

Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and
linux-image-5.6.0-2-amd64 (5.6.14-1).>

This also affects 5.5.0-rc5-amd64.

(https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/l
inux/)

The kernel boot option "intel_iommu=igfx_off" prevents the error message.


This seems to be resolved in newer kernel versions.
I'm not able to reproduce this with kernel version 5.14.0-4-amd64
(5.14.16-1).


Great that it is resolved :-)

As many people are affected and the Stable kernel version still seems to
exhibit the problem, I want to ask a question:
Are you willing to help out to narrow down as much as possible which version
introduced the error and in which is was fixed? Wrt the latter, does 5.14.12-1
still show the issue?


[...]

Just a small update: kernel version 5.13.9-1~exp2 is also not affected by the 
problem.

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

[Stefan Pietsch]

On 07.06.20 08:48, Stefan Pietsch wrote:

On 2020-06-01 20:44, Stefan Pietsch wrote:


Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and 
linux-image-5.6.0-2-amd64 (5.6.14-1).


This also affects 5.5.0-rc5-amd64.

(https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/linux/)

The kernel boot option "intel_iommu=igfx_off" prevents the error message.


This seems to be resolved in newer kernel versions.
I'm not able to reproduce this with kernel version 5.14.0-4-amd64 (5.14.16-1).


Regards,
Stefan

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

[Stefan Pietsch]

On 08.04.21 11:50, Stefan Pietsch wrote:

On 30.03.21 13:35, maximilian attems wrote:

reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop


[18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: G    W 
5.10.0-5-amd64 #1 Debian 5.10.24-1
[18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W (1.59 
) 11/29/2019



Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17
to exclude this guy fault.



I upgraded the Lenovo T490 BIOS from 1.59 to 1.72.
That did not make any difference.



I cannot reproduce this with firmware version 46.9d0122c0.0 
9000-pu-b0-jf-b0-46.ucode from firmware-iwlwifi 20221012-1.
This seems to be fixed.

Regards,
Stefan

Bug#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

[Stefan Pietsch]

On 04.11.22 09:36, Joachim Reichel wrote:

Hi Stefan,

it would have been helpful if you had attached an image that shows this behavior. I have an idea what the problem might be, but having 
access to your test case for verification would be good. Feel free to send it directly to my email address if you prefer.


Best regards,
   Joachim



Hi Joachim,

I have uploaded the test picture here: 
https://salsa.debian.org/IPv4v6/debian-bug-1023303/-/blob/master/IMG_20221102_000230.jpg


Best regards,
Stefan

Bug#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

[Stefan Pietsch]

Package: jhead
Version: 1:3.06.0.1-3
Severity: grave


jhead version 1:3.06.0.1-3 deletes EXIF data when rotating images:

$ exiftool IMG_20221102_000230.jpg | wc -l

77



$ jhead -autorot IMG_20221102_000230.jpg



Nonfatal Error : 'IMG_20221102_000230.jpg' Command has invalid characters.



$ exiftool IMG_20221102_000230.jpg | wc -l

23





jhead 1:3.06.0.1-2 is not affected.

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

[Stefan Pietsch]

On 30.03.21 13:35, maximilian attems wrote:

reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop


[18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW 
5.10.0-5-amd64 #1 Debian 5.10.24-1
[18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W (1.59 
) 11/29/2019



Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17
to exclude this guy fault.



I upgraded the Lenovo T490 BIOS from 1.59 to 1.72.
That did not make any difference.


Regards,
Stefan

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

[Stefan Pietsch]

On 16.03.21 17:34, Debian FTP Masters wrote:
> Source: firmware-nonfree
> Source-Version: 20210315-1~exp1
> Done: maximilian attems 
>
> We believe that the bug you reported is fixed in the latest version of
> firmware-nonfree, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 963...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> maximilian attems  (supplier of updated firmware-nonfree 
package)

- snip -


I cannot confirm that the bug is fixed.

firmware-iwlwifi 20210315-2 is installed.



dmesg output when wireless interface stopped working:

[18654.227951] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[18654.228331] iwlwifi :00:14.3: Start IWL Error Log Dump:
[18654.228339] iwlwifi :00:14.3: Status: 0x0040, count: 6
[18654.228345] iwlwifi :00:14.3: Loaded firmware version: 46.6f9f215c.0 
9000-pu-b0-jf-b0-46.ucode
[18654.228353] iwlwifi :00:14.3: 0x3203 | ADVANCED_SYSASSERT
[18654.228358] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
[18654.228363] iwlwifi :00:14.3: 0x | trm_hw_status1
[18654.228368] iwlwifi :00:14.3: 0x00488C0E | branchlink2
[18654.228373] iwlwifi :00:14.3: 0x00478EDE | interruptlink1
[18654.228378] iwlwifi :00:14.3: 0x | interruptlink2
[18654.228383] iwlwifi :00:14.3: 0x0004 | data1
[18654.228388] iwlwifi :00:14.3: 0xDEADBEEF | data2
[18654.228393] iwlwifi :00:14.3: 0xDEADBEEF | data3
[18654.228398] iwlwifi :00:14.3: 0x | beacon time
[18654.228403] iwlwifi :00:14.3: 0x0290028A | tsf low
[18654.228408] iwlwifi :00:14.3: 0x | tsf hi
[18654.228412] iwlwifi :00:14.3: 0x | time gp1
[18654.228417] iwlwifi :00:14.3: 0x0290028B | time gp2
[18654.228422] iwlwifi :00:14.3: 0x0001 | uCode revision type
[18654.228427] iwlwifi :00:14.3: 0x002E | uCode version major
[18654.228432] iwlwifi :00:14.3: 0x6F9F215C | uCode version minor
[18654.228437] iwlwifi :00:14.3: 0x0312 | hw version
[18654.228442] iwlwifi :00:14.3: 0x00C89008 | board version
[18654.228447] iwlwifi :00:14.3: 0x8073FC28 | hcmd
[18654.228452] iwlwifi :00:14.3: 0x24022000 | isr0
[18654.228457] iwlwifi :00:14.3: 0x | isr1
[18654.228461] iwlwifi :00:14.3: 0x08201802 | isr2
[18654.228466] iwlwifi :00:14.3: 0x004168C0 | isr3
[18654.228471] iwlwifi :00:14.3: 0x | isr4
[18654.228476] iwlwifi :00:14.3: 0x0940001C | last cmd Id
[18654.228480] iwlwifi :00:14.3: 0xCEB6 | wait_event
[18654.228485] iwlwifi :00:14.3: 0x10D4 | l2p_control
[18654.228490] iwlwifi :00:14.3: 0x00018034 | l2p_duration
[18654.228495] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
[18654.228500] iwlwifi :00:14.3: 0x8100 | l2p_addr_match
[18654.228505] iwlwifi :00:14.3: 0x000D | lmpm_pmg_sel
[18654.228510] iwlwifi :00:14.3: 0x28010905 | timestamp
[18654.228514] iwlwifi :00:14.3: 0xD8B8 | flow_handler
[18654.228663] iwlwifi :00:14.3: Start IWL Error Log Dump:
[18654.228668] iwlwifi :00:14.3: Status: 0x0040, count: 7
[18654.228674] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
[18654.228679] iwlwifi :00:14.3: 0x | umac branchlink1
[18654.228684] iwlwifi :00:14.3: 0xC0088BBE | umac branchlink2
[18654.228689] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink1
[18654.228694] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink2
[18654.228699] iwlwifi :00:14.3: 0x0800 | umac data1
[18654.228704] iwlwifi :00:14.3: 0xC0084458 | umac data2
[18654.228708] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
[18654.228713] iwlwifi :00:14.3: 0x002E | umac major
[18654.228718] iwlwifi :00:14.3: 0x6F9F215C | umac minor
[18654.228723] iwlwifi :00:14.3: 0x029002A9 | frame pointer
[18654.228728] iwlwifi :00:14.3: 0xC088627C | stack pointer
[18654.228733] iwlwifi :00:14.3: 0x00660118 | last host cmd
[18654.228737] iwlwifi :00:14.3: 0x | isr status reg
[18654.228758] iwlwifi :00:14.3: Fseq Registers:
[18654.228769] iwlwifi :00:14.3: 0xA7691BFB | FSEQ_ERROR_CODE
[18654.228780] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[18654.228791] iwlwifi :00:14.3: 0x58F7C241 | FSEQ_CNVIO_INIT_VERSION
[18654.228802] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[18654.228813] iwlwifi :00:14.3: 0x2B29C823 | FSEQ_TOP_CONTENT_VERSION
[18654.228824] iwlwifi :00:14.3: 0x27FAB991 | FSEQ_ALIVE_TOKEN
[18654.228835] iwlwifi :00:14.3: 0xD01B76C3 | FSEQ_CNVI_ID
[18654.228846] iwlwifi :00:14.3: 0xC5454E1C | FSEQ_CNVR_ID
[18654.228857] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[18654.228870] iwlwifi :00:14.3: 0x013002

Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode

[Stefan Pietsch]

On 22.01.21 20:48, maximilian attems wrote:

Firmware 9000-pu-b0-jf-b0-46.ucode stops working when used with
hostapd as soon as a wireless client connects.


Is that still happening with latest 5.10 linux and newer
firmware-iwlwifi version >= 202011?



The problem still exists with firmware-iwlwifi 20201218-2.

# cat /proc/version
Linux version 5.10.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-5) 10.2.1 20210108, GNU ld (GNU 
Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.5-1 (2021-01-09)



# dmesg output #


[81668.281626] iwlwifi :00:14.3: Queue 9 is active on fifo 3 and stuck for 1 ms. SW [0, 2] HW [0, 0] FH 
TRB=0x0baef4f74

[81668.281924] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[81668.282306] iwlwifi :00:14.3: Start IWL Error Log Dump:
[81668.282313] iwlwifi :00:14.3: Status: 0x0040, count: 6
[81668.282319] iwlwifi :00:14.3: Loaded firmware version: 46.4d093a30.0 
9000-pu-b0-jf-b0-46.ucode
[81668.282325] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN
[81668.282330] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0
[81668.282335] iwlwifi :00:14.3: 0x | trm_hw_status1
[81668.282339] iwlwifi :00:14.3: 0x00488876 | branchlink2
[81668.282344] iwlwifi :00:14.3: 0x00478E36 | interruptlink1
[81668.282348] iwlwifi :00:14.3: 0x00478E36 | interruptlink2
[81668.282352] iwlwifi :00:14.3: 0x00011526 | data1
[81668.282356] iwlwifi :00:14.3: 0xFF00 | data2
[81668.282360] iwlwifi :00:14.3: 0xF008 | data3
[81668.282365] iwlwifi :00:14.3: 0x | beacon time
[81668.282369] iwlwifi :00:14.3: 0x00A556BB | tsf low
[81668.282373] iwlwifi :00:14.3: 0x | tsf hi
[81668.282377] iwlwifi :00:14.3: 0x | time gp1
[81668.282381] iwlwifi :00:14.3: 0x00A556BC | time gp2
[81668.282386] iwlwifi :00:14.3: 0x0001 | uCode revision type
[81668.282390] iwlwifi :00:14.3: 0x002E | uCode version major
[81668.282395] iwlwifi :00:14.3: 0x4D093A30 | uCode version minor
[81668.282399] iwlwifi :00:14.3: 0x0312 | hw version
[81668.282403] iwlwifi :00:14.3: 0x18C89008 | board version
[81668.282407] iwlwifi :00:14.3: 0x0049011C | hcmd
[81668.282412] iwlwifi :00:14.3: 0x00022000 | isr0
[81668.282416] iwlwifi :00:14.3: 0x | isr1
[81668.282420] iwlwifi :00:14.3: 0x08001802 | isr2
[81668.282424] iwlwifi :00:14.3: 0x00417CC0 | isr3
[81668.282428] iwlwifi :00:14.3: 0x | isr4
[81668.282433] iwlwifi :00:14.3: 0x00490191 | last cmd Id
[81668.282437] iwlwifi :00:14.3: 0x00011526 | wait_event
[81668.282441] iwlwifi :00:14.3: 0x4208 | l2p_control
[81668.282445] iwlwifi :00:14.3: 0x0020 | l2p_duration
[81668.282450] iwlwifi :00:14.3: 0x033F | l2p_mhvalid
[81668.282454] iwlwifi :00:14.3: 0xA000 | l2p_addr_match
[81668.282458] iwlwifi :00:14.3: 0x000D | lmpm_pmg_sel
[81668.282462] iwlwifi :00:14.3: 0x01102344 | timestamp
[81668.282466] iwlwifi :00:14.3: 0xB0D0 | flow_handler
[81668.282614] iwlwifi :00:14.3: Start IWL Error Log Dump:
[81668.282619] iwlwifi :00:14.3: Status: 0x0040, count: 7
[81668.282624] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST
[81668.282628] iwlwifi :00:14.3: 0x | umac branchlink1
[81668.282633] iwlwifi :00:14.3: 0xC0088BBE | umac branchlink2
[81668.282637] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink1
[81668.282641] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink2
[81668.282646] iwlwifi :00:14.3: 0x0100 | umac data1
[81668.282650] iwlwifi :00:14.3: 0xC0084458 | umac data2
[81668.282654] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
[81668.282658] iwlwifi :00:14.3: 0x002E | umac major
[81668.282662] iwlwifi :00:14.3: 0x4D093A30 | umac minor
[81668.282667] iwlwifi :00:14.3: 0x00A556AA | frame pointer
[81668.282671] iwlwifi :00:14.3: 0xC088627C | stack pointer
[81668.282675] iwlwifi :00:14.3: 0x00490191 | last host cmd
[81668.282679] iwlwifi :00:14.3: 0x | isr status reg
[81668.282699] iwlwifi :00:14.3: Fseq Registers:
[81668.282709] iwlwifi :00:14.3: 0xAF493BFB | FSEQ_ERROR_CODE
[81668.282720] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[81668.282730] iwlwifi :00:14.3: 0x58B74E41 | FSEQ_CNVIO_INIT_VERSION
[81668.282740] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[81668.282751] iwlwifi :00:14.3: 0x7A29D869 | FSEQ_TOP_CONTENT_VERSION
[81668.282761] iwlwifi :00:14.3: 0x46FAB991 | FSEQ_ALIVE_TOKEN
[81668.282771] iwlwifi :00:14.3: 0x901A6683 | FSEQ_CNVI_ID
[81668.282781] iwlwifi :00:14.3: 0xC545CE1C | FSEQ_CNVR_ID
[81668.282792] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[81668.282805] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
[81668.282818] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[81668.282861] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_S

Bug#976996: qemu-system: qemu doesn't support video mode qxl anymore and fails to load spice libraries

[Stefan Pietsch]

On 12/9/20 8:14 PM, bauen1 wrote:

Package: qemu-system
Version: 1:5.2+dfsg-1
Severity: important
X-Debbugs-Cc: j24...@gmail.com

Dear Maintainer,

I've just upgraded qemu-system and related packages, now I can't launch any 
libvirt virtual machiness with the virtual machine manager frontend anymore.
It appears that this is caused by qemu no longer being build with support for 
the qxl video mode, or at least not advertising it anymore.
When ran with spice qemu now also fails to load the 
/usr/lib/x86_64-linux-gnu/qemu/ui-spice-core.so library due to unresolved 
symbols `console_gl_check_format`.

This appears to be a regression from 1:5.1+dfsg-4+b2


I can confirm this.

Steps to reproduce:

$ qemu-system-x86_64 -vga qxl
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/ui-spice-core.so: 
undefined symbol: console_gl_check_format
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/hw-display-qxl.so: 
undefined symbol: qemu_spice_cursor_refresh_bh
qemu-system-x86_64: QXL VGA not available


To use "vga qxl" you have to downgrade to 1:5.1+dfsg-4.

Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode

[Stefan Pietsch]

Package: firmware-iwlwifi
Version: 20190717-2
Severity: important

Firmware 9000-pu-b0-jf-b0-46.ucode stops working when used with hostapd as soon 
as a wireless client connects.
This also affects firmware 9000-pu-b0-jf-b0-41.ucode.

I was not able to reproduce this with firmware 9000-pu-b0-jf-b0-38.ucode


##


# lspci output of wireless controller

00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] (rev 30)
Subsystem: Intel Corporation Cannon Point-LP CNVi [Wireless-AC]
Flags: fast devsel, IRQ 16, IOMMU group 5
Memory at c9738000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Null
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 

Kernel modules: iwlwifi


##


# cat /proc/version
Linux version 5.6.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-13)) #1 SMP Debian 
5.6.14-2 (2020-06-09)



##


# dmesg with 9000-pu-b0-jf-b0-41.ucode loaded

[ 1368.793833] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[ 1368.794275] iwlwifi :00:14.3: Start IWL Error Log Dump:
[ 1368.794282] iwlwifi :00:14.3: Status: 0x0040, count: 6
[ 1368.794287] iwlwifi :00:14.3: Loaded firmware version: 41.fc1a7aea.0 
9000-pu-b0-jf-b0-41.ucode
[ 1368.794293] iwlwifi :00:14.3: 0x3203 | ADVANCED_SYSASSERT
[ 1368.794298] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
[ 1368.794302] iwlwifi :00:14.3: 0x | trm_hw_status1
[ 1368.794306] iwlwifi :00:14.3: 0x004885AA | branchlink2
[ 1368.794310] iwlwifi :00:14.3: 0x0047A3E2 | interruptlink1
[ 1368.794313] iwlwifi :00:14.3: 0x | interruptlink2
[ 1368.794317] iwlwifi :00:14.3: 0x0004 | data1
[ 1368.794323] iwlwifi :00:14.3: 0xDEADBEEF | data2
[ 1368.794327] iwlwifi :00:14.3: 0xDEADBEEF | data3
[ 1368.794331] iwlwifi :00:14.3: 0x | beacon time
[ 1368.794335] iwlwifi :00:14.3: 0x0489CF77 | tsf low
[ 1368.794338] iwlwifi :00:14.3: 0x | tsf hi
[ 1368.794342] iwlwifi :00:14.3: 0x | time gp1
[ 1368.794346] iwlwifi :00:14.3: 0x0489CF77 | time gp2
[ 1368.794350] iwlwifi :00:14.3: 0x0001 | uCode revision type
[ 1368.794354] iwlwifi :00:14.3: 0x0029 | uCode version major
[ 1368.794358] iwlwifi :00:14.3: 0xFC1A7AEA | uCode version minor
[ 1368.794370] iwlwifi :00:14.3: 0x0312 | hw version
[ 1368.794391] iwlwifi :00:14.3: 0x18C89008 | board version
[ 1368.794407] iwlwifi :00:14.3: 0x8069FC28 | hcmd
[ 1368.794422] iwlwifi :00:14.3: 0x24022000 | isr0
[ 1368.794435] iwlwifi :00:14.3: 0x | isr1
[ 1368.794447] iwlwifi :00:14.3: 0x0820180A | isr2
[ 1368.794459] iwlwifi :00:14.3: 0x00416CC0 | isr3
[ 1368.794474] iwlwifi :00:14.3: 0x | isr4
[ 1368.794486] iwlwifi :00:14.3: 0x00490191 | last cmd Id
[ 1368.794494] iwlwifi :00:14.3: 0x | wait_event
[ 1368.794498] iwlwifi :00:14.3: 0x10D4 | l2p_control
[ 1368.794502] iwlwifi :00:14.3: 0x00018034 | l2p_duration
[ 1368.794506] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
[ 1368.794510] iwlwifi :00:14.3: 0x8100 | l2p_addr_match
[ 1368.794514] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
[ 1368.794518] iwlwifi :00:14.3: 0x04100930 | timestamp
[ 1368.794521] iwlwifi :00:14.3: 0x502C | flow_handler
[ 1368.794669] iwlwifi :00:14.3: Start IWL Error Log Dump:
[ 1368.794674] iwlwifi :00:14.3: Status: 0x0040, count: 7
[ 1368.794679] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
[ 1368.794683] iwlwifi :00:14.3: 0x | umac branchlink1
[ 1368.794687] iwlwifi :00:14.3: 0xC0087F22 | umac branchlink2
[ 1368.794691] iwlwifi :00:14.3: 0xC0083C9C | umac interruptlink1
[ 1368.794695] iwlwifi :00:14.3: 0xC0083C9C | umac interruptlink2
[ 1368.794699] iwlwifi :00:14.3: 0x0800 | umac data1
[ 1368.794703] iwlwifi :00:14.3: 0xC0083C9C | umac data2
[ 1368.794707] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
[ 1368.794710] iwlwifi :00:14.3: 0x0029 | umac major
[ 1368.794714] iwlwifi :00:14.3: 0xFC1A7AEA | umac minor
[ 1368.794718] iwlwifi :00:14.3: 0xC0886280 | frame pointer
[ 1368.794722] iwlwifi :00:14.3: 0xC0886280 | stack pointer
[ 1368.794725] iwlwifi :00:14.3: 0x004A0118 | last host cmd
[ 1368.794729] iwlwifi :00:14.3: 0x | isr status reg
[ 1368.794751] iwlwifi :00:14.3: Fseq Registers:
[ 1368.794774] iwlwifi :00:14.3: 0xA7493BFB | FSEQ_ERROR_CODE
[ 1368.794794] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[ 1368.794816] iwlwifi :00:14.3: 0x58

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

[Stefan Pietsch]

On 2020-06-01 20:44, Stefan Pietsch wrote:

Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and 
linux-image-5.6.0-2-amd64 (5.6.14-1).


This also affects 5.5.0-rc5-amd64.

(https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/linux/)

The kernel boot option "intel_iommu=igfx_off" prevents the error message.

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

[Stefan Pietsch]

Package: linux-image-amd64
Version: 5.6.14-1


Starting with Linux kernel package linux-image-5.6.0-1-amd64 (5.6.7-1) I 
get the following error message that is repeating every few seconds:


kernel: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait 
for idle; VT'd may hang.



Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and 
linux-image-5.6.0-2-amd64 (5.6.14-1).


The error message does not appear with linux-image-5.4.0-4-amd64 
(5.4.19-1).


Hardware is a Lenovo T410 with integrated Intel graphics controller.

Bug#932711: 404 for http://standards.ieee.org/regauth/oui/oui.txt

[Stefan Pietsch]

On 2019-07-22 06:54, Harald Dunkel wrote:

Package: ieee-data
Version: 20150531.1~deb8u2

The monthly cron job returns

# export BASEDIR=/var/lib/ieee-data/
# bash -x /usr/bin/update-oui -f -q
:
:
+ goAndGet http://standards.ieee.org/regauth/oui/oui.txt oui.txt
+ true
+ wget -q -O- http://standards.ieee.org/regauth/oui/oui.txt
+ Die 'wget -q -O- http://standards.ieee.org/regauth/oui/oui.txt exit 
with 8'

+ true
+ exit 1

Looking closely:

% cd /tmp/
% wget -Ncv http://standards.ieee.org/regauth/oui/oui.txt
converted 'http://standards.ieee.org/regauth/oui/oui.txt' 
(ANSI_X3.4-1968) -> 'http://standards.ieee.org/regauth/oui/oui.txt' (UTF-8)

--2019-07-22 08:49:40--  http://standards.ieee.org/regauth/oui/oui.txt
Resolving standards.ieee.org (standards.ieee.org)... 18.235.140.50
Connecting to standards.ieee.org 
(standards.ieee.org)|18.235.140.50|:80... connected.

HTTP request sent, awaiting response... 302 Found
Location: https://standards.ieee.org/regauth/oui/oui.txt [following]
converted 'https://standards.ieee.org/regauth/oui/oui.txt' 
(ANSI_X3.4-1968) -> 'https://standards.ieee.org/regauth/oui/oui.txt' 
(UTF-8)

--2019-07-22 08:49:41--  https://standards.ieee.org/regauth/oui/oui.txt
Connecting to standards.ieee.org 
(standards.ieee.org)|18.235.140.50|:443... connected.

HTTP request sent, awaiting response... 404 Not Found
2019-07-22 08:49:42 ERROR 404: Not Found.



I suppose the bug won't be fixed in Debian 8.

The current package from Debian buster (20180805.1) works to download 
the OUI files.


Regards,
Stefan

Bug#955330: iproute2: corrupted output of "altname"

[Stefan Pietsch]

On 2020-04-03 11:16, Luca Boccassi wrote:

On Tue, 31 Mar 2020 04:12:38 +0200 Adam Borowski 
wrote:

Control: tags -1 -moreinfo

On Mon, Mar 30, 2020 at 10:36:03AM +0100, Luca Boccassi wrote:

On Mon, 2020-03-30 at 02:55 +0200, Adam Borowski wrote:

On a system with a bridge "ip a" says:

3: br0:  mtu 1500 qdisc noqueue
state UP group default qlen 1000
 link/ether 76:29:4f:cd:bd:87 brd ff:ff:ff:ff:ff:ff
 altname �
  ��
 altname ��!���



Kernel: Linux 5.6.0-00076-gbbfc4289910d (SMP w/4 CPU cores;

PREEMPT)



Those strings come from the kernel via netlink, and you seem to

have a

custom kernel. Can you reproduce with Debian's kernel?


Yeah, I've just tried.  With 5.5.0-1 it's:

0270  20 20 61 6c 74 6e 61 6d  65 20 c0 4e c2 b0 ff

ff  |  altname .N|

0280  0a 20 20 20 20 61 6c 74  6e 61 6d 65 20 d0 29

be  |.altname .).|

0290  b9 aa aa 0a 20 20 20 20  69 6e 65 74 20 31 30

2e  |inet 10.|




Ok, I'll have a look once the 5.5 kernel hits backports, as it's
necessary to reproduce it.


Reproducible with kernel 5.5.13 from Debian unstable:

root@lt490:~# ip tuntap add mode tap footap1

root@lt490:~# ip link show footap1
8: footap1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether c2:20:9b:e6:0a:0a brd ff:ff:ff:ff:ff:ff
altname ??M?
altname ??M?

root@lt490:~# uname -a
Linux lt490 5.5.0-1-amd64 #1 SMP Debian 5.5.13-2 (2020-03-30) x86_64 GNU/Linux


Regards,
Stefan

Bug#861907: scrot not supporting multiple displays

[Stefan Pietsch]

On 2017-05-05 15:47, Dale Harris wrote:

Package: scrot
Version: 0.8-18
Severity: normal

Dear Maintainer,

Trying to use scrot -m or --multidisp doesn't appear to work. Man page
says it should grab a shot from each display and then merge the image,
however it only appears to be taking a shot from one. Is there something
else that has to be configured/installed to allow this to work?


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

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

Versions of packages scrot depends on:
ii  giblib11.2.4-11
ii  libc6  2.24-10
ii  libimlib2  1.4.8-1
ii  libx11-6   2:1.6.4-3

scrot recommends no packages.

scrot suggests no packages.

-- no debconf information



Dear bug reporter and maintainer,

this is not reproducible with scrot version 1.2-2 from Debian unstable.

Regards,
Stefan

Bug#951367: [PATCH] don't pass an empty arg to wget when --verbose is applied (Closes: #951367)

[Stefan Pietsch]

On 2020-02-18 20:47, Daniel Kahn Gillmor wrote:

If NVSWITCH is empty, the old code was running wget '' …

But this causes wget to fail to fetch the empty URL, which means the
return code ends up being non-zero.  This breaks sbuild-createchroot,
which apparently always passes --verbose to debootstrap.

This error was introduced in 14f0b7aafb4d568b027baeecee08cfac6c4f874d,
so is relatively recent.
---
  functions | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/functions b/functions
index a3c93e9..d6725f7 100644
--- a/functions
+++ b/functions
@@ -93,7 +93,7 @@ wgetprogress () {
ret=$({ { wget $@ 2>&1 >/dev/null || echo $? >&2; } | "$PKGDETAILS" "WGET%" "$PROGRESS_NOW" 
"$PROGRESS_NEXT" "$PROGRESS_END" >&3; } 2>&1)
: ${ret:=0}
else
-   wget "$NVSWITCH" "$@"
+   wget $NVSWITCH "$@"
ret=$?
fi
return $ret



I can confirm the bug and the solutions. Either omitting "--verbose" or 
patching /usr/share/debootstrap/functions helps.



Regards,
Stefan

Bug#940057: qemu 4.1: qxl driver does not resize display / received empty monitor config

[Stefan Pietsch]

Package: qemu
Version: 1:4.1-1+b1
Severity: normal

QEMU 4.1 has a problem when using the vga qxl driver.

$ qemu-system-x86_64 -machine accel=kvm \
-m 1024 -cdrom grml64-full_2018.12.iso -vga qxl \
-spice port=,disable-ticketing



Connect with the Spice viewer and start Grml in Graphical Mode.

$ remote-viewer spice://127.0.0.1: --spice-debug

Now resize with "xrandr -s 1680x1050".

### remote-viewer debug output ###

(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-channel.c:2926 test 
cap 0 in 0x1: yes
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-util.c:270 
spice_make_scancode:  scancode 28
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-util.c:270 
spice_make_scancode: release scancode 28
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-cursor.c:542 
cursor-4:0: cursor_handle_reset, init_done: 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-display.c:1951 
display-2:0: 0: FIXME primary destroy, but is display really disabled?
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: spice-widget.c:3046 0:0 
cursor_reset
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-cursor.c:542 
cursor-4:0: cursor_handle_reset, init_done: 0
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: spice-widget.c:1926 0:0 
focus_out_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1860 0:0 
leave_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:945 0:0 
ungrab keyboard
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1860 0:0 
leave_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:3046 0:0 
cursor_reset
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:496 0:0 
grab_broken (implicit: 0, keyboard: 1)
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:498 0:0 
grab_broken (SpiceDisplay::GdkWindow 0x560258aaec60, event->grab_window: (nil))
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1536 0:0 
release_keys
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-display.c:1909 
surface flags: 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-display.c:947 
display-2:0: Create primary canvas
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-cursor.c:387 
cursor-4:0: set_cursor: flags 1, size 0
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:300 0:0 
update monitor area
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:2573 0:0 
update area +0+0 1024x768
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:2599 0:0 
primary: 1680x1050
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:1300 0:0 
recalc geom monitor: 0:0, guest +0+0:1024x768, window 1024x768, zoom 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:1890 0:0 
focus_in_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.641: spice-channel.c:2926 test 
cap 1 in 0x1052: yes
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.653: spice-widget.c:1845 0:0 
enter_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.653: spice-widget.c:867 0:0 grab 
keyboard
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.654: spice-widget.c:1845 0:0 
enter_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.657: channel-display.c:1123 
display-2:0: display_handle_mark
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.660: spice-widget.c:2852 0:0 
widget mark: 1, display 0x560258d60680
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.661: decode-glz.c:352 
decode_header: 1680x1050, id 17193, ref 17187
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.670: channel-display.c:1975 
display-2:0: received empty monitor config
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.670: decode-glz.c:352 
decode_header: 1680x1050, id 17194, ref 17189
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.684: decode-glz.c:352 
decode_header: 1680x1050, id 17195, ref 17192

### remote-viewer debug output ###



If you disconnect the Spice viewer and try to reconnect the viewer only shows 
the text "Connected to graphic server".

### remote-viewer debug output ###

(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-widget.c:300 0:0 
update monitor area
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-widget.c:313 0:0 
update monitor: no monitor 0
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-channel.c:2926 test 
cap 1 in 0x1052: yes
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-widget.c:317 0:0 
waiting until MonitorsConfig is received
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-channel.c:2926 test 
cap 1 in 0x1052: yes
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: spice-channel.c:1298 
inputs-3:0: channel up, state 3
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422: channel-base.c:81 main-1:0: 
spice_channel_handle_notify -- warn!!! #0: keyboard channel is insecure
(remote-viewer:27738): GSpice-DEBUG: 21:51:40.429: channel-display.c:1975 
display-2:0: received empty monitor config
(r

Bug#939928: ovmf 0~20190606.20d2e5a1-4: VM does not start with UEFI BIOS

[Stefan Pietsch]

Package: ovmf
Version: 0~20190606.20d2e5a1-4
Severity: grave

It is not possible to start a virtual machine with UEFI BIOS.


qemu-system-x86_64 -bios /usr/share/qemu/OVMF.fd

The QEMU window shows: "Guest has not initialized the display (yet)."


Downgrading ovmf to 0~20181115.85588389-3 solves this.


$ qemu-system-x86_64 -version
QEMU emulator version 4.1.0 (Debian 1:4.1-1+b1)

Bug#935098: nmap 7.80: random segfaults while scanning

[Stefan Pietsch]

Package: nmap
Version: 7.80+dfsg1-1
Severity: normal


nmap randomly stops while doing a scan.


Starting program: /usr/bin/nmap -vv --stats-every=60s -Pn -sV -O -sS -p1-65535 
-oA report [IP address]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Starting Nmap 7.80 ( https://nmap.org ) at 2019-08-19 14:04 CEST
NSE: Loaded 45 scripts for scanning.
Initiating Parallel DNS resolution of 1 host. at 14:04
Completed Parallel DNS resolution of 1 host. at 14:04, 0.02s elapsed
Initiating SYN Stealth Scan at 14:04
Scanning [IP address] [65535 ports]
Discovered open port 443/tcp on [IP address]
Discovered open port 80/tcp on [IP address]
SYN Stealth Scan Timing: About 20.44% done; ETC: 14:07 (0:02:01 remaining)
Stats: 0:01:00 elapsed; 0 hosts completed (1 up), 1 undergoing SYN Stealth Scan
SYN Stealth Scan Timing: About 48.34% done; ETC: 14:06 (0:01:04 remaining)
Completed SYN Stealth Scan at 14:06, 103.47s elapsed (65535 total ports)
Initiating Service scan at 14:06
Scanning 2 services on [IP address]
Stats: 0:02:00 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan
Service scan Timing: About 50.00% done; ETC: 14:07 (0:00:17 remaining)
Stats: 0:03:02 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan
Service scan Timing: About 50.00% done; ETC: 14:09 (0:01:19 remaining)
Stats: 0:04:02 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan
Service scan Timing: About 50.00% done; ETC: 14:11 (0:02:19 remaining)
Completed Service scan at 14:08, 143.88s elapsed (2 services on 1 host)
Initiating OS detection (try #1) against [IP address]
Retrying OS detection (try #2) against [IP address]
NSE: Script scanning [IP address].
NSE: Starting runlevel 1 (of 2) scan.
Initiating NSE at 14:09

Program received signal SIGSEGV, Segmentation fault.
0x779064c7 in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
(gdb) bt
#0  0x779064c7 in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#1  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#2  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#3  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#4  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#5  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#6  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#7  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#8  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#9  0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#10 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#11 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#12 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#13 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#14 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#15 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#16 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#17 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#18 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#19 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
#20 0x779064cc in hascaptures () from 
/usr/lib/x86_64-linux-gnu/liblua5.3-lpeg.so.2
[.]

Bug#919027: wireshark: missing executables

[Stefan Pietsch]

Package: wireshark-common
Version: 2.6.6-1
Severity: normal

The wireshark-common package is missing these executable files:

- captype
- idl2wrs
- randpkt

Bug#884775: /usr/bin/rustc: Error Compiling Code: "attempt to use impure library"

[Stefan Pietsch]

On Tue, 19 Dec 2017 17:19:31 +0300 Frederick Muriithi
 wrote:
> Package: rustc
> Version: 1.14.0+dfsg1-3
> Severity: important
> File: /usr/bin/rustc
> 
> Dear Maintainer,
> 
> 
> I wanted to learn rust, following the tutorial/book at
> https://doc.rust-lang.org/book/second-edition/
> 
> I first of all, installed rust using the rustup tool as directed in the book 
> at
> https://doc.rust-lang.org/book/second-edition/ch01-01-installation.html
> 
> On compiling, the code failed with the error :
> 
> error: linking with `cc` failed: exit code: 1

[...]

> After giving it a while, I thought it might be the interaction between
> the rustc installed via rustup
> and the system libraries that was causing the errors, so I unistalled
> that via rustup, and installed
> the rustc that is present in the Debian repository, rustc
> (1.14.0+dfsg1-3) and tried to compile the
> hello world program again.
> I got a similar error with this rustc too:
> 
> error: linking with `cc` failed: exit code: 1
>   |
>   = note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L"
> "/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib" "main.0.o" "-o" "main"
> "-Wl,--gc-sections" "-pie" "-nodefaultlibs" "-L"


I cannot reproduce this with rustc 1.14.0+dfsg1-3 in Debian stretch.

$ cat main.rs
fn main() {
println!("Hello, world!");
}

$ rustc main.rs

$ ./main
Hello, world!


Regards,
Stefan

Bug#883676: tilix: crash when selecting menu->about

[Stefan Pietsch]

On Wed, 06 Dec 2017 12:26:53 +0100 Xavier Bestel 
wrote:
> Package: tilix
> Version: 1.7.1-2
> Severity: important
> 
> Dear Maintainer,
> 
> When selecting "about" in the Tilix menu, it
> segfaulted. Backtrace without symbols below.
> 
> HTH,
>   Xav
> 
> #0  0x55a93d90 in gdk_x11_get_server_time ()
> #1  0x74650627 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #2  0x746506f6 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #3  0x74650fe5 in gtk_clipboard_set_with_owner () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #4  0x744c772f in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #5  0x744c9efe in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #6  0x72c0e1d6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #7  0x72c2976f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #8  0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #9  0x7462bdfa in gtk_widget_grab_focus () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #10 0x744c8ed8 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #11 0x744de38b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #12 0x72c0deb1 in g_closure_invoke () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #13 0x72c20728 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #14 0x72c28e1f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #15 0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #16 0x7462cb36 in gtk_widget_child_focus () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #17 0x744154fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #18 0x744de38b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #19 0x72c0deb1 in g_closure_invoke () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #20 0x72c20728 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #21 0x72c28e1f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #22 0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #23 0x7462cb36 in gtk_widget_child_focus () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #24 0x744154fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #25 0x744de38b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #26 0x72c0deb1 in g_closure_invoke () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #27 0x72c20728 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #28 0x72c28e1f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #29 0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #30 0x7462cb36 in gtk_widget_child_focus () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #31 0x7464496b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #32 0x744de38b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #33 0x72c0df9d in g_closure_invoke () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #34 0x72c20728 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #35 0x72c28e1f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #36 0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #37 0x7462cb36 in gtk_widget_child_focus () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #38 0x74644859 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #39 0x72c10041 in g_cclosure_marshal_VOID__BOOLEANv () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #40 0x72c0e1d6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #41 0x72c2976f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #42 0x72c2a378 in g_signal_emit_by_name () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #43 0x7444995f in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #44 0x72c0e1d6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #45 0x72c2976f in g_signal_emit_valist () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #46 0x72c29e9f in g_signal_emit () at 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #47 0x74637062 in gtk_widget_map () at 
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0


Tilix also crashes when clicking the title bar:


Thread 1 "tilix" received signal SIGSEGV, Segmentation fault.
0x55a93d90 in gdk_x11_get_server_time ()
(gdb) bt
#0  0x55a93d90 in gdk_x11_get_server_time ()
#1  0x746501b7 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x74650286 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x74650b75 in gtk_clipboard_set_with_owner () fr

Bug#882740: hostapd installation error

[Stefan Pietsch]

Package: hostapd
Version: 2:2.6-7
Severity: normal


The installation of hostapd in Debian sid fails.


Preparing to unpack .../hostapd_2%3a2.6-7_amd64.deb ...
Unpacking hostapd (2:2.6-7) ...
Setting up hostapd (2:2.6-7) ...
Job for hostapd.service failed because the control process exited with
error code.
See "systemctl  status hostapd.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript hostapd, action "start" failed.
● hostapd.service - Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP
Authenticator
   Loaded: loaded (/lib/systemd/system/hostapd.service; disabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-11-26 12:22:12 CET;
4ms ago
  Process: 6579 ExecStart=/usr/sbin/hostapd -P /run/hostapd.pid -B
$DAEMON_OPTS ${DAEMON_CONF} (code=exited, status=1/FAILURE)

Nov 26 12:22:12 lx270 systemd[1]: Starting Advanced IEEE 802.11 AP and
IEEE 802.1X/WPA/WPA2/EAP Authenticator...
Nov 26 12:22:12 lx270 hostapd[6579]: Configuration file:
Nov 26 12:22:12 lx270 hostapd[6579]: Could not open configuration file
'' for reading.
Nov 26 12:22:12 lx270 hostapd[6579]: Failed to set up interface with
Nov 26 12:22:12 lx270 hostapd[6579]: Failed to initialize interface
Nov 26 12:22:12 lx270 systemd[1]: hostapd.service: Control process
exited, code=exited status=1
Nov 26 12:22:12 lx270 systemd[1]: hostapd.service: Failed with result
'exit-code'.
Nov 26 12:22:12 lx270 systemd[1]: Failed to start Advanced IEEE 802.11
AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
dpkg: error processing package hostapd (--configure):
 installed hostapd package post-installation script subprocess returned
error exit status 1
Processing triggers for systemd (235-3) ...
Processing triggers for man-db (2.7.6.1-4) ...
Errors were encountered while processing:
 hostapd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#871629: same here

[Stefan Pietsch]

On Fri, 11 Aug 2017 10:38:10 +0200 Adrian Ban  wrote:
> Hi,
> 
> Yesterday after upgrading my Laptop and a VM both on Debian Sid I've 
> notice exactly the same issues mentioned here.
> .
> In the begging I thought is my Laptop issue
>   but after checking the VM I've notice that is a Thunderbird/system issue .
> 
> Which is the fastest way to fix this issue?
> 
> Kind regards,
> Adrian


I'm using Debian sid and downgraded Thunderbird to 52.2.1-4.

Regards,
Stefan

Bug#857138: mock: missing dependency

[Stefan Pietsch]

Package: mock
Version: 1.3.2-1
Severity: normal


mock in Debian stretch does not work without the Python module 'six'.


$ mock
Traceback (most recent call last):
  File "/usr/sbin/mock", line 56, in 
from six.moves import configparser
ImportError: No module named 'six'


You have to install python3-six.

Bug#844025: sslscan: static build

[Stefan Pietsch]

Package: sslscan
Version: 1.11.5-rbsec-1
Severity: normal


sslscan in Debian unstable does not support SSLv2 and v3.

$ sslscan --version
1.11.5
OpenSSL 1.0.2j  26 Sep 2016
OpenSSL version does not support SSLv2
SSLv2 ciphers will not be detected
OpenSSL version does not support SSLv3
SSLv3 ciphers will not be detected


Build sslscan statically to support legacy protocols for testing.

Bug#784656: Re: [Pkg-samba-maint] Bug#784656: winbind: PANIC when trying to authenticate user

[Stefan Pietsch]

On 18.05.2015 11:50, Robert Ramięga wrote:
> Hi
> 
> Last week I've fiddled with my smb.conf trying to get more SSO behaviour
> on my workstation and started to get panics in samba.
> Workaround is to disable:
> 
> kerberos method = secrets and keytab
> 
> in smb.conf and restart.
> 
> I've also found this
> https://lists.samba.org/archive/samba/2015-February/189032.html
> From quick glance it looks like the problem root is missing
> /etc/krb5.keytab It should be created while joing ADS but (at least on
> my workstation) it does not exists (and I've joined domain couple years
> ago)


I can confirm this.

Commenting out "kerberos method" solves it, but we have a valid
/etc/krb5.keytab file that got created when joining the domain.

So without a "kerberos method" statement it defaults to "secrets only"
according to the documentation.


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

Bug#784656: [Pkg-samba-maint] Bug#784656: winbind: PANIC when trying to authenticate user

[Stefan Pietsch]

On 08.05.2015 16:25, Jelmer Vernooij wrote:
> Samba shouldn't panic in this case, but rather just print that error message
> and exit.
> 
> Have you joined Samba to the domain?

Yes, the machine is member of the domain.


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

Bug#784656: winbind: PANIC when trying to authenticate user

[Stefan Pietsch]

I've captured a core dump of winbindd.

This is the output of gdb bt full:


GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/winbindd...Reading symbols from 
/usr/lib/debug/.build-id/34/57ae6fbec871533769977a9457fd82790df635.debug...done.
done.
[New LWP 11360]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/winbindd -d 10'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fa056449107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
(gdb) #0  0x7fa056449107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 11360
selftid = 11360
#1  0x7fa05644a4e8 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0xd, sa_sigaction = 0xd}, 
sa_mask = {__val = {140734198539432, 140326728297984, 140326732697095, 1, 0, 0,
  140326618639656, 2001, 140326728297984, 140734198539280, 
140326732722981, 140326726098576, 140326730488285, 140326730488016, 
140734198537008, 6}},
  sa_flags = 1005149472, sa_restorer = 0x7fff3be95bd0}
sigs = {__val = {32, 0 }}
#2  0x7fa05878197a in dump_core () at ../source3/lib/dumpcore.c:336
called = true
__FUNCTION__ = "dump_core"
#3  0x7fa05876b41b in smb_panic_s3 (why=) at 
../source3/lib/util.c:808
cmd = 
result = 
__FUNCTION__ = "smb_panic_s3"
#4  0x7fa05ca95caf in smb_panic (why=why@entry=0x7fa05caa25fc "internal 
error") at ../lib/util/fault.c:159
No locals.
#5  0x7fa05ca95ecf in fault_report (sig=) at 
../lib/util/fault.c:77
counter = 1
#6  sig_fault (sig=) at ../lib/util/fault.c:88
No locals.
#7  
No locals.
#8  krb5_storage_free (sp=0x0) at store.c:292
No locals.
#9  0x7fa05728a665 in fkt_end_seq_get (context=0x7fa05dff8e80, 
id=, cursor=0x7fff3be96410) at keytab_file.c:507
No locals.
#10 0x7fa059301e06 in fill_mem_keytab_from_system_keytab 
(krbctx=krbctx@entry=0x7fa05dff8e80, mkeytab=mkeytab@entry=0x7fa05dfc7db0)
at ../source3/librpc/crypto/gse_krb5.c:478
zero_csr = {fd = 0, sp = 0x0, data = 0x0}
ret = 13
keytab = 0x7fa05dfc9c40
kt_cursor = {fd = -1, sp = 0x0, data = 0x0}
kt_entry = {principal = 0x0, vno = 0, keyblock = {keytype = 0, keyvalue 
= {length = 0, data = 0x0}}, timestamp = 0, flags = 0, aliases = 0x0}
valid_princ_formats = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}
entry_princ_s = 0x0
my_name = "ABBY\000\000\000\000
v{V\240\177\000\000\022\000\000\000\000\000\000\000\000\363\377]\240\177\000\000\200\216\377]\240\177\000\000\300f\351;\377\177\000\000\000\000\000\000\000\000\000\000p\000IV\240\177\000\000\000\000\000\000\000\000\000\000\300\271\374]\240\177\000\000\022\000\000\000\000\000\000\000
v{V\240\177\000\000\016\000\000\000\000\000\000\000\230f\351;\377\177\000\000\000\000\000\000\377\177\000\000\300f\351;\377\177\000\000\000\000\000\000\000\000\000\000p\000IV\240\177\000\000\000\000\000\000\240\177\000\000\016\000\000\000\000\000\000\000\030\363\377]\240\177\000\000\340o\370]\240\177\000\000\000\000\000\000\240\177\000\000
a\376]\240\177\000\000\200\216\377]\240\177\000\000"...
my_fqdn = 
"abby.corp.lsexperts.de\000\000\327\023\060Y\240\177\000\000\000\000\000\000\240\177",
 '\000' , "\356\312\\\240\177\000\000\016", '\000'
, " a\376]\240\177", '\000' ,
"\220\243\377]\240\177\000\000\016\000\000\000\000\000\000\000\240\065\371]\240\177\000\000\b\354\377]\240\177\000\000\070\006RY\240\177\000\000
a\376]\240\177\000\000\000\000\000\000\000\000\000\000\235\377\377\377\000\000\000\000\016\000\000\000\000\000\000\000\240\065\371]\240\177\000\000\b\272LU",
 '\000' ...
i = 
__FUNCTION__ = "fill_mem_keytab_from_system_keytab"
#11 0x7fa05930232b in gse_krb5_get_server_keytab (krbctx=0x7fa05dff8e80, 
keytab=0x7fa05dfc7db0) at ../source3/librpc/crypto/gse_krb5.c:602
ret = 
ret1 = 0
ret2 = 0
__FUNCTION__ = "gse_krb5_get_server_keytab"
#12 0x7fa05930403a in gse_init_server (_gse_ctx=, 
add_gss_c_flags=, do_seal=, do_sign=,
mem_ctx=) at ../source3/librpc/crypto/gse.c:345
gse_ctx = 0x

Bug#784656: winbind: PANIC when trying to authenticate user

[Stefan Pietsch]

Package: winbind
Version: 2:4.1.17+dfsg-2
Severity: grave

We have a Debian jessie machine that is not able to authenticate a user
against a Samba 4 domain controller with winbind. When the domain user
tries to logon with the correct password, winbind crashes.

Running winbind in debug level 10 gives us:


# log.wb-CORP #

[2015/05/07 10:59:03.245096, 10, pid=30054, effective(2001, 0),
real(2001, 0)]
../source3/librpc/crypto/gse_krb5.c:279(fill_mem_keytab_from_secrets)
  ../source3/librpc/crypto/gse_krb5.c:279: no prev machine password
[2015/05/07 10:59:03.245231, 10, pid=30054, effective(2001, 0),
real(2001, 0)] ../source3/lib/util.c:1868(name_to_fqdn)
  name_to_fqdn: lookup for ABBY -> abby.corp.lsexperts.de.
[2015/05/07 10:59:03.245317,  1, pid=30054, effective(2001, 0),
real(2001, 0)]
../source3/librpc/crypto/gse_krb5.c:416(fill_mem_keytab_from_system_keytab)
  ../source3/librpc/crypto/gse_krb5.c:416: krb5_kt_start_seq_get failed
(Permission denied)
[2015/05/07 10:59:03.245381,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../lib/util/fault.c:72(fault_report)
  ===
[2015/05/07 10:59:03.246279,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../lib/util/fault.c:73(fault_report)
  INTERNAL ERROR: Signal 11 in pid 30054 (4.1.17-Debian)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2015/05/07 10:59:03.247275,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../lib/util/fault.c:75(fault_report)
  ===
[2015/05/07 10:59:03.247942,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../source3/lib/util.c:785(smb_panic_s3)
  PANIC (pid 30054): internal error
[2015/05/07 10:59:03.249204,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../source3/lib/util.c:896(log_stack_trace)
  BACKTRACE: 27 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a)
[0x7fa0f68972ca]
   #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20)
[0x7fa0f68973b0]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f)
[0x7fa0fabc1caf]
   #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1cecf)
[0x7fa0fabc1ecf]
   #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7fa0faff18d0]
   #5 /usr/lib/x86_64-linux-gnu/libkrb5.so.26(krb5_storage_free+0x1)
[0x7fa0f53d12a1]
   #6 /usr/lib/x86_64-linux-gnu/libkrb5.so.26(+0x47665) [0x7fa0f53b6665]
   #7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x8e06) [0x7fa0f742de06]
   #8
/usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0xeb)
[0x7fa0f742e32b]
   #9 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xb03a) [0x7fa0f743003a]
   #10 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x72)
[0x7fa0f78bfab2]
   #11
/usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_oid+0x26)
[0x7fa0f78bfd96]
   #12 /usr/sbin/winbindd(kerberos_return_pac+0x42c) [0x7fa0fb447cac]
   #13 /usr/sbin/winbindd(winbindd_dual_pam_auth+0x1150) [0x7fa0fb46d5a0]
   #14 /usr/sbin/winbindd(+0x5fd5c) [0x7fa0fb481d5c]
   #15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x92cb) [0x7fa0f48f22cb]
   #16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fa0f48f0797]
   #17 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d)
[0x7fa0f48ecf9d]
   #18 /usr/sbin/winbindd(+0x620d8) [0x7fa0fb4840d8]
   #19 /usr/sbin/winbindd(+0x627d5) [0x7fa0fb4847d5]
   #20
/usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0xd4)
[0x7fa0f48ed7c4]
   #21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x908e) [0x7fa0f48f208e]
   #22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fa0f48f0797]
   #23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d)
[0x7fa0f48ecf9d]
   #24 /usr/sbin/winbindd(main+0xad4) [0x7fa0fb447024]
   #25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
[0x7fa0f4561b45]
   #26 /usr/sbin/winbindd(+0x25699) [0x7fa0fb447699]
[2015/05/07 10:59:03.254728,  0, pid=30054, effective(2001, 0),
real(2001, 0)] ../source3/lib/dumpcore.c:312(dump_core)
  unable to change to /var/log/samba/cores/winbindd
  refusing to dump core

# log.wb-CORP #


# log.winbindd #

[2015/05/07 10:59:03.121241,  1, pid=30049, effective(0, 0), real(0, 0)]
../librpc/ndr/ndr.c:333(ndr_print_function_debug)
   wbint_LookupName: struct wbint_LookupName
  out: struct wbint_LookupName
  type : *
  type : SID_NAME_DOM_GRP (2)
  sid  : *
  sid  :
S-1-5-21-1063204605-3499843724-851943503-1135
  result   : NT_STATUS_OK
[2015/05/07 10:59:03.121463, 10, pid=30049, effective(0, 0), real(0, 0),
class=winbind] ../source3/winbindd/winbindd.c:755(wb_request_done)
  wb_request_done[29718:LOOKUPNAME]: NT_STATUS_OK
[2015/05/07 10:59:03.121570, 10, pid=30049, effective(0, 0), real(0, 0),
class=winbind]
../source3/winbind

Bug#492359: [Pkg-openldap-devel] Bug#492359: ldap-utils: ldapsearch fails to connect to MS AD with user certificate

[Stefan Pietsch]

On 20.05.2014 07:08, Ryan Tandy wrote:

> On 15/02/09 04:56 PM, Quanah Gibson-Mount wrote:
>> --On Monday, February 16, 2009 12:48 AM +0100 Stefan Pietsch
>>  wrote:
>>
>>> After changing "configure.options" to "--with-tls=openssl" and
>>> recompiling openldap I can connect to the domain controller.
>>>
>>> So there seems to be something wrong with GnuTLS.
>>
>> Try with OpenLDAP 2.4.14 or later (not that anything later exists right
>> at this moment. ;) ).
> 
> Did you ever get a chance to test this with a more recent version of
> openldap, like Quanah suggested?
> 
> I don't have access to a Windows domain controller, so I'm not able to
> verify this bug myself.


I can confirm that it works in wheezy with ldap-utils 2.4.31-1+nmu2 and
Windows 2003 SP2 on the other side.

Regards,
Stefan


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

Bug#755669: udev: /dev/net/tun missing

[Stefan Pietsch]

On 22.07.2014 13:27, Michael Biebl wrote:
> 
> Am 22.07.2014 10:28, schrieb Stefan Pietsch:
>> Package: udev
>> Version: 208-6
>> Severity: important
>>
>> udev 208-6 does not create /dev/net/tun.
>>
>> Downgrading to 204-14 solves this.
> 
> Are you still using sysvinit as init system?


Right, installing systemd did it.

Thanks. Please close this bug report.


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

Bug#755669: udev: /dev/net/tun missing

[Stefan Pietsch]

Package: udev
Version: 208-6
Severity: important

udev 208-6 does not create /dev/net/tun.

Downgrading to 204-14 solves this.



Regards,
Stefan


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

Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption

[Stefan Pietsch]

Package: xserver-xorg-video-intel
Version: 2:2.21.15-1+b2
Severity: important

The xserver-xorg-video-intel update from 2:2.21.14-4 to 2:2.21.15-1
shows this error in Xorg.0.log:

intel(0): Failed to submit batch buffer, expect rendering corruption:
Resource deadlock avoided.


Moving windows is jerky after the error appears in the log file.
Downgrading to 2.21.14-4 solves this problem.

The machine is a Thinkpad X60s.


Regards,
Stefan


-


lspci:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition
Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port
1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port
2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port
3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port
4 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface
Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7-M Family)
SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
Controller
03:00.0 Ethernet controller: Qualcomm Atheros AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b4)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller
(rev 09)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro
Host Adapter (rev 18)


-


Xorg.0.log:


[34.995]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[34.996] X Protocol Version 11, Revision 0
[34.996] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[34.996] Current Operating System: Linux hostname 3.10-2-686-pae #1
SMP Debian 3.10.7-1 (2013-08-17) i686
[34.996] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10-2-686-pae
root=/dev/mapper/VG1-root ro quiet
[34.996] Build Date: 22 August 2013  05:27:51PM
[34.996] xorg-server 2:1.12.4-6.2 (Michael Stapelberg
)
[34.996] Current version of pixman: 0.30.2
[34.996]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[34.996] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[34.996] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep  2
10:39:00 2013
[35.001] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[35.005] (==) No Layout section.  Using the first Screen section.
[35.005] (==) No screen section available. Using defaults.
[35.005] (**) |-->Screen "Default Screen Section" (0)
[35.005] (**) |   |-->Monitor ""
[35.009] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[35.009] (==) Automatically adding devices
[35.009] (==) Automatically enabling devices
[35.023] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[35.056]Entry deleted from font path.
[35.086] (WW) The directory
"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist.
[35.086]Entry deleted from font path.
[35.086] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[35.086] (==) ModulePath set to "/usr/lib/xorg/modules"
[35.086] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[35.086] (II) Loader magic: 0xb77275a0
[35.086] (II) Module ABI versions:
[35.086]X.Org ANSI C Emulation: 0.4
[35.086]X.Org Video Driver:

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 26.06.2013 12:47, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
>> On 24.06.2013 14:30, Gleb Natapov wrote:
>>> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
>>>> As soon as I remove "kvmvapic.bin" the virtual machine boots with
>>>> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
>>>> "emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make
>>>> no difference.
>>>>
>>>> Please send your patches.
>>> Here it is, run with it and kvmvapic.bin present. See what is printed in
>>> dmesg after the failure.
>>>
>>>
>>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>>> index f4a5b3f..65488a4 100644
>>> --- a/arch/x86/kvm/vmx.c
>>> +++ b/arch/x86/kvm/vmx.c
>>> @@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
>>>  {
>>> struct vcpu_vmx *vmx = to_vmx(vcpu);
>>> u32 ar;
>>> +   unsigned long rip;
>>>  
>>> if (vmx->rmode.vm86_active && seg != VCPU_SREG_LDTR) {
>>> *var = vmx->rmode.segs[seg];
>>> @@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
>>> var->db = (ar >> 14) & 1;
>>> var->g = (ar >> 15) & 1;
>>> var->unusable = (ar >> 16) & 1;
>>> +   rip = kvm_rip_read(vcpu);
>>> +   if ((rip == 0xc101611c || rip == 0xc101611a) && seg == VCPU_SREG_FS)
>>> +   printk("base=%p limit=%p selector=%x ar=%x\n", var->base, 
>>> var->limit, var->selector, ar);
>>>  }
>>>  
>>>  static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
>>
>>
>> Booting kernel Linux 3.10-rc5 with your patch applied produces these
>> messages in dmesg when starting a virtual machine:
>>
>> emulate_invalid_guest_state=0
>> [  118.732151] base= limit=  (null) selector=ffff ar=0
>> [  118.732341] base= limit=  (null) selector=ffff ar=0
>>
> I've butchered printk format, but it gives me the idea of what is going
> on anyway. Can you try the patch below with
> emulate_invalid_guest_state=0|1?
> 
> 
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index f4a5b3f..eb062ce 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -3395,19 +3395,20 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
>   var->selector = vmx_read_guest_seg_selector(vmx, seg);
>   return;
>   }
> +
>   var->base = vmx_read_guest_seg_base(vmx, seg);
>   var->limit = vmx_read_guest_seg_limit(vmx, seg);
>   var->selector = vmx_read_guest_seg_selector(vmx, seg);
>   ar = vmx_read_guest_seg_ar(vmx, seg);
> + var->unusable = (ar >> 16) & 1;
>   var->type = ar & 15;
>   var->s = (ar >> 4) & 1;
>   var->dpl = (ar >> 5) & 3;
> - var->present = (ar >> 7) & 1;
> + var->present = !var->unusable;
>   var->avl = (ar >> 12) & 1;
>   var->l = (ar >> 13) & 1;
>   var->db = (ar >> 14) & 1;
>   var->g = (ar >> 15) & 1;
> - var->unusable = (ar >> 16) & 1;
>  }
>  
>  static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)


Kernel 3.10-rc5 with your latest patch applied can successfully boot the
virtual machine with emulate_invalid_guest_state 0 or 1.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 24.06.2013 14:30, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
>> As soon as I remove "kvmvapic.bin" the virtual machine boots with
>> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
>> "emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make
>> no difference.
>>
>> Please send your patches.
> Here it is, run with it and kvmvapic.bin present. See what is printed in
> dmesg after the failure.
> 
> 
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index f4a5b3f..65488a4 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
>  {
>   struct vcpu_vmx *vmx = to_vmx(vcpu);
>   u32 ar;
> + unsigned long rip;
>  
>   if (vmx->rmode.vm86_active && seg != VCPU_SREG_LDTR) {
>   *var = vmx->rmode.segs[seg];
> @@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
>   var->db = (ar >> 14) & 1;
>   var->g = (ar >> 15) & 1;
>   var->unusable = (ar >> 16) & 1;
> + rip = kvm_rip_read(vcpu);
> + if ((rip == 0xc101611c || rip == 0xc101611a) && seg == VCPU_SREG_FS)
> + printk("base=%p limit=%p selector=%x ar=%x\n", var->base, 
> var->limit, var->selector, ar);
>  }
>  
>  static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)


Booting kernel Linux 3.10-rc5 with your patch applied produces these
messages in dmesg when starting a virtual machine:

emulate_invalid_guest_state=0
[  118.732151] base= limit=  (null) selector=ffff ar=0
[  118.732341] base= limit=  (null) selector=ffff ar=0

emulate_invalid_guest_state=1
[  196.481653] base= limit=  (null) selector=ffff ar=0
[  196.481700] base= limit=  (null) selector=ffff ar=0
[  196.481706] base= limit=  (null) selector=ffff ar=0
[  196.481711] base= limit=  (null) selector=ffff ar=0
[  196.481716] base= limit=  (null) selector=ffff ar=0
[  196.481720] base= limit=  (null) selector=ffff ar=0
[  196.481725] base= limit=  (null) selector=ffff ar=0
[  196.481730] base= limit=  (null) selector=ffff ar=0
[  196.481735] base= limit=  (null) selector=ffff ar=0
[  196.481739] base= limit=  (null) selector=ffff ar=0
[  196.481777] base= limit=  (null) selector=ffff ar=0
[  196.482068] base= limit=  (null) selector=ffff ar=0
[  196.482073] base= limit=  (null) selector=ffff ar=0
[  196.482079] base= limit=  (null) selector=ffff ar=0
[  196.482084] base= limit=  (null) selector=ffff ar=0
[  196.482131] base= limit=  (null) selector=ffff ar=0
[  196.482136] base= limit=  (null) selector=ffff ar=0
[  196.482142] base= limit=  (null) selector=ffff ar=0
[  196.482146] base= limit=  (null) selector=ffff ar=0
[  196.482193] base= limit=  (null) selector=ffff ar=0
[  196.482198] base= limit=  (null) selector=ffff ar=0
[  196.482203] base= limit=  (null) selector=ffff ar=0
[  196.482208] base= limit=  (null) selector=ffff ar=0
[  196.482255] base= limit=  (null) selector=ffff ar=0
[  196.482259] base= limit=  (null) selector=ffff ar=0
[  196.482265] base= limit=  (null) selector=ffff ar=0
[  196.482269] base= limit=  (null) selector=ffff ar=0
[  196.482316] base= limit=  (null) selector=ffff ar=0
[  196.482321] base= limit=  (null) selector=ffff ar=0
[  196.482326] base= limit=  (null) selector=ffff ar=0
[  196.482331] base= limit=  (null) selector=ffff ar=0
[  196.482378] base= limit=  (null) selector=ffff ar=0
[  196.482382] base= limit=  (null) selector=ffff ar=0
[  196.482388] base= limit=  (null) selector=ffff ar=0
[  196.482392] base= limit=  (null) selector=ffff ar=0
[  196.482439] base= limit=  (null) selector=ffff ar=0
[  196.482444] base= limit=  (null) selector=ffff ar=0
[  196.482449] base= limit=  (null) selector=ffff ar=0
[  196.482454] base= limit=  (null) selector=ffff ar=0
[  196.482501] base= limit=  (null) selector=ffff ar=0
[  196.482505] base= limit=  (null) selector=ffff ar=0
[  196.482511] base= limit=  (null) selector=ffff ar=0
[  196.482516] base= limit=  (null) selector=ffff ar=0
[  196.482562] base= limit=  (null) selector=ffff ar=0
[  196.482567] base= limit=  (null) selector=ffff ar=0
[  196.482573] base= limit=  (null) selector=f000

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 24.06.2013 13:47, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
>> On 23.06.2013 19:36, Gleb Natapov wrote:
>>> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
>>>> On 23.06.2013 09:51, Gleb Natapov wrote:
>>>>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
>>>>>>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
>>>>>>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
>>>>>>> monitor after the hang.
>>>>>>
>>>>>>
>>>>>> 25391454e73e3156202264eb3c473825afe4bc94
>>>>>>  emulate_invalid_guest_state=0
>>>>>>
>>>>> Very interesting. Looks like somewhere during TPR access FS
>>>>> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin
>>>>> and try again? This will disable some code paths during TPR access and
>>>>> will narrow down the issue.
>>>>
>>>>
>>>> Doing this, qemu complains
>>>> "Could not open option rom 'kvmvapic.bin': No such file or directory",
>>>> but the virtual machine boots successful with
>>>> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1.
>>>>
>>> Hmm, I think we ate close. Can you try with upstream qemu?
>>>
>>>> kvmvapic.bin comes with Debian package "seabios 1.7.2-3".
>>
>> I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4.
> And it didn't work? Mind trying some debug kernel patches? I suspect
> your CPU does something no CPU I have do, so I want to verify it.


As soon as I remove "kvmvapic.bin" the virtual machine boots with
qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
"emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make
no difference.

Please send your patches.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 23.06.2013 19:36, Gleb Natapov wrote:
> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
>> On 23.06.2013 09:51, Gleb Natapov wrote:
>>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
>>>>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
>>>>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
>>>>> monitor after the hang.
>>>>
>>>>
>>>> 25391454e73e3156202264eb3c473825afe4bc94
>>>>  emulate_invalid_guest_state=0
>>>>
>>> Very interesting. Looks like somewhere during TPR access FS
>>> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin
>>> and try again? This will disable some code paths during TPR access and
>>> will narrow down the issue.
>>
>>
>> Doing this, qemu complains
>> "Could not open option rom 'kvmvapic.bin': No such file or directory",
>> but the virtual machine boots successful with
>> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1.
>>
> Hmm, I think we ate close. Can you try with upstream qemu?
> 
>> kvmvapic.bin comes with Debian package "seabios 1.7.2-3".

I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 23.06.2013 09:51, Gleb Natapov wrote:
> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
>>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
>>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
>>> monitor after the hang.
>>
>>
>> 25391454e73e3156202264eb3c473825afe4bc94
>>  emulate_invalid_guest_state=0
>>
> Very interesting. Looks like somewhere during TPR access FS
> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin
> and try again? This will disable some code paths during TPR access and
> will narrow down the issue.


Doing this, qemu complains
"Could not open option rom 'kvmvapic.bin': No such file or directory",
but the virtual machine boots successful with
emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1.

kvmvapic.bin comes with Debian package "seabios 1.7.2-3".


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 19.06.2013 16:38, Gleb Natapov wrote:
> On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote:
>> On 19.06.2013 15:41, Gleb Natapov wrote:
>>> On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
>>>>
>>>> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
>>>> KVM: VMX: don't clobber segment AR of unusable segments.
>>>>
>>>>
>>>> 25391454e73e3156202264eb3c473825afe4bc94
>>>> emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed"
>>>> emulate_invalid_guest_state=1 -> hangs
>>>>
>>> With emulate_invalid_guest_state=1 the commit does nothing. Can you
>>> double check that 218e763f458c44f30041c1b48b4371e130fd4317 works for you
>>> with emulate_invalid_guest_state=1?
>>
>>
>> 218e763f458c44f30041c1b48b4371e130fd4317
>> emulate_invalid_guest_state=0 -> works
>> emulate_invalid_guest_state=1 -> hangs
>>
>> 25391454e73e3156202264eb3c473825afe4bc94 broke
>> emulate_invalid_guest_state=0.
> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
> monitor after the hang.


25391454e73e3156202264eb3c473825afe4bc94
 emulate_invalid_guest_state=0

(qemu) info registers
EAX= EBX=0001 ECX=f000 EDX=f000
ESI=00195e93 EDI= EBP=de84c000 ESP=de84df64
EIP=c101611c EFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =007b   00c0f300 DPL=3 DS   [-WA]
CS =0060   00c09b00 DPL=0 CS32 [-RA]
SS =0068   00c09300 DPL=0 DS   [-WA]
DS =007b   00c0f300 DPL=3 DS   [-WA]
FS =  ffff 00f0ff00 DPL=3 CS64 [CRA]
GS =00e0 c1438b40 0018 00409100 DPL=0 DS   [--A]
LDT=  ffff 00f0ff00 DPL=3 CS64 [CRA]
TR =0080 c1400f00 206b 8b00 DPL=0 TSS32-busy
GDT= c13f6000 00ff
IDT= c13f5000 07ff
CR0=8005003b CR2= CR3=014bc000 CR4=0690
DR0= DR1= DR2=0007
DR3=
DR6=0ff0 DR7=0400
EFER=
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80
FPR0=f44d002c6000 400d FPR1=80847fe7 400e
FPR2=fa007fa24000 400e FPR3=80e88055f000 400e
FPR4=ea61009c4000 400d FPR5=ea62009c4000 400c
FPR6=800bf600 4015 FPR7= 
XMM00=
XMM01=
XMM02=
XMM03=
XMM04=
XMM05=
XMM06=
XMM07=

(qemu) x/20i $pc-20
0xc1016108:  (bad)
0xc1016109:  decl   0x158bc310(%ecx)
0xc101610f:  les-0x7b723ec0(%ebx),%eax
0xc1016115:  adc%al,(%eax)
0xc1016117:  sar$0xff,%bh
0xc101611a:  mov(%eax),%eax
0xc101611c:  ret
0xc101611d:  jmp0xc1016121
0xc101611f:  pause
0xc1016121:  mov(%eax),%edx
0xc1016123:  test   %edx,%edx
0xc1016125:  je 0xc101611f
0xc1016127:  ret
0xc1016128:  cmp$0xfe,%eax
0xc101612d:  setle  %al
0xc1016130:  movzbl %al,%eax
0xc1016133:  ret
0xc1016134:  mov0xc1407b64,%edx
0xc101613a:  mov$0x20,%eax
0xc101613f:  call   *0x9c(%edx)


last 20 lines of the trace:
 qemu-system-x86-4042  [000]   295.592694: vcpu_match_mmio:  gva
0xb0d0 gpa 0xfee000d0 Read GVA
 qemu-system-x86-4042  [000]   295.592694: kvm_apic:
apic_read APIC_LDR = 0x100
 qemu-system-x86-4042  [000]   295.592695: kvm_mmio: mmio
read len 4 gpa 0xfee000d0 val 0x100
 qemu-system-x86-4042  [000]   295.592696: kvm_entry:vcpu 0
 qemu-system-x86-4042  [000]   295.592699: kvm_exit: reason
EXCEPTION_NMI rip 0xc101611a info b080 8b0e
 qemu-system-x86-4042  [000]   295.592700: kvm_page_fault:   address
b080 error_code 9
 qemu-system-x86-4042  [000]   295.592701: kvm_emulate_insn:
0:c101611a:8b 00 (prot32)
 qemu-system-x86-4042  [000]   295.592702: vcpu_match_mmio:  gva
0xb080 gpa 0xfee00080 Read GVA
 qemu-system-x86-4042  [000]   295.592703: kvm_apic:
apic_read APIC_TASKPRI = 0x0
 qemu-system-x86-4042  [000]   295.592703: kvm_mmio: mmio
read len 4 gpa 0xfee00080 val 0x0
 qemu-system-x86-4042  [000]   295.592704: kvm_userspace_exit:   reason
KVM_EXIT_TPR_ACCESS (12)
 qemu-system-x86-4042  [000]   295.592805: kvm_entry:vcpu 0
 qemu-system-x86-4042  [000]   295.592808: kvm_exit: reason
 rip 0xc101611c info 0 8b0e
 qemu-system-x86-4042  [000]   295.592809: kvm_userspace_exit:   reason
KVM_EXIT_FAIL_ENTRY (9)
 qemu-sy

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 19.06.2013 15:41, Gleb Natapov wrote:
> On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
>>
>> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
>> KVM: VMX: don't clobber segment AR of unusable segments.
>>
>>
>> 25391454e73e3156202264eb3c473825afe4bc94
>> emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed"
>> emulate_invalid_guest_state=1 -> hangs
>>
> With emulate_invalid_guest_state=1 the commit does nothing. Can you
> double check that 218e763f458c44f30041c1b48b4371e130fd4317 works for you
> with emulate_invalid_guest_state=1?


218e763f458c44f30041c1b48b4371e130fd4317
emulate_invalid_guest_state=0 -> works
emulate_invalid_guest_state=1 -> hangs

25391454e73e3156202264eb3c473825afe4bc94 broke
emulate_invalid_guest_state=0.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 17.06.2013 18:07, Paolo Bonzini wrote:
> Il 16/06/2013 02:25, Stefan Pietsch ha scritto:
>> Bisecting leads to
>>
>> git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
>> git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
>> git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1
>> git bisect good 286da4156dc65c8a054580fdd96b7709132dce8d
>> git bisect bad 25391454e73e3156202264eb3c473825afe4bc94
>> git bisect good 218e763f458c44f30041c1b48b4371e130fd4317
>>
>>
>> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
>> KVM: VMX: don't clobber segment AR of unusable segments.
>>
>> 25391454e73e3156202264eb3c473825afe4bc94
>> emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed"
>> emulate_invalid_guest_state=1 -> hangs
>>
>> Please note, I had to compile some revisions with
>> 3f0c3d0bb2bcc4b88b22452a7cf0073ee9a0f1e6 applied, caused by
>> 9ae9febae9500a0a6f5ce29ee4b8d942b5332529.
> 
> Can you please execute "info registers" and "x/10i $pc" from the QEMU
> monitor at the time of the hang, and include the output?  Using
> "-monitor stdio" or the new GTK+ interface can help.
> 
> Also, can you run under tracing (for information on how to do this, see
> http://www.linux-kvm.org/page/Tracing) and include the bottom of the log?

Tested with 25391454e73e3156202264eb3c473825afe4bc94
 emulate_invalid_guest_state=1


(qemu) info registers
EAX=00010286 EBX= ECX=c12c527c EDX=
ESI=00010286 EDI=c14c4744 EBP=c10161f5 ESP=de84df10
EIP=c1014a8d EFL=00010286 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =007b   00c0f300 DPL=3 DS   [-WA]
CS =0060   00c09b00 DPL=0 CS32 [-RA]
SS =0068   00c09300 DPL=0 DS   [-WA]
DS =007b   00c0f300 DPL=3 DS   [-WA]
FS =  ffff 00f0ff00 DPL=3 CS64 [CRA]
GS =00e0 c1438b40 0018 00409100 DPL=0 DS   [--A]
LDT=  ffff 00f0ff00 DPL=3 CS64 [CRA]
TR =0080 c1400f00 206b 8b00 DPL=0 TSS32-busy
GDT= c13f6000 00ff
IDT= c13f5000 07ff
CR0=8005003b CR2= CR3=014bc000 CR4=0690
DR0= DR1= DR2=0007
DR3=
DR6=0ff0 DR7=0400
EFER=
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80
FPR0=f44d002c6000 400d FPR1=80847fe7 400e
FPR2=fa007fa24000 400e FPR3=80e88055f000 400e
FPR4=ea61009c4000 400d FPR5=ea62009c4000 400c
FPR6=800bf600 4015 FPR7= 
XMM00=
XMM01=
XMM02=
XMM03=
XMM04=
XMM05=
XMM06=
XMM07=

(qemu) x/10i $pc
0xc1014a8d:  lea0x0(%esi),%esi
0xc1014a91:  ret
0xc1014a92:  cli
0xc1014a93:  nop
0xc1014a94:  lea0x0(%esi),%esi
0xc1014a98:  ret
0xc1014a99:  push   %eax
0xc1014a9a:  call   0xc1014a84
0xc1014a9f:  mov%eax,(%esp)
0xc1014aa2:  call   0xc1014a92


last 20 lines of the trace:
 qemu-system-x86-3575  [000]   542.279800: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279802: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279802: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279803: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279804: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279805: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279806: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279807: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279808: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279809: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279810: kvm_entry:vcpu 0
 qemu-system-x86-3575  [000]   542.279811: kvm_inj_virq: irq 48
 qemu-system-x86-3575  [000]   542.279812: kvm_entry:vcpu 0
 qemu-system-x86-3573  [001]   542.280010: kvm_set_irq:  gsi 0
level 1 source 0
 qemu-system-x86-3573  [001]   542.280013: kvm_pic_set_irq:  chip 0
pin 0 (edge|masked)
 qemu-system-x86-3573  [001]   542.280015: kvm_apic_accept_irq:  apicid
0 vec 48 (LowPrio|edge) (coalesced)
 qemu-system-x86-3573  [001]   542.280015: kvm_ioapic_set_irq:   pin 2
dst 1 vec=48 (LowPrio|logical|edge) (coalesced)
 qemu-system-x86-3573  [001]   542.280016: kvm_set_irq:  gsi 0
level 0 source 0
 qemu-system-x86-3573  [001]   542.280017: kvm_pic_set_irq:  chip 0
pin 0 (edge|masked)
 qemu-system-x86-3573  [001]   542.280017: kvm_ioapic_set_irq:   pin 2
dst 1 vec=48 (LowPrio|logical|edge)


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 13.06.2013 16:59, Stefan Pietsch wrote:
> On 13.06.2013 15:42, Paolo Bonzini wrote:
>> Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
>>> git bisect tells me:
>>> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
>>
>> This is an s390 commit, so the bisect somehow went wrong.  Can you
>> confirm that 3.7 works and 3.8 doesn't?
> 
> Confirmed. Something went wrong.
> I replayed the bisect log and now I have
> 
> git bisect bad 9626357371b519f2b955fef399647181034a77fe
> git bisect good ef4e359d9b9e2dc022f79840fd207796b524a893
> git bisect good b5c78e04dd061b776978dad61dd85357081147b0
> git bisect good 9e2d59ad580d590134285f361a0e80f0e98c0207
> git bisect bad 69086a78bdc973ec0b722be790b146e84ba8a8c4
> git bisect good 9ecf9b085a0926e07c78c08a07296bbfd1c37d07
> git bisect bad 21fbd5809ad126b949206d78e0a0e07ec872ea11
> git bisect bad 79fd50c67f91136add9726fb7719b57a66c6f763
> git bisect bad aa11e3a8a6d9f92c3fe4b91a9aca5d8c23d55d4d
> git bisect good 66cdd0ceaf65a18996f561b770eedde1d123b019
> git bisect bad d99e415275dd3f757b75981adad8645cdc26da45
> 
> So please wait for my results.


Bisecting leads to

git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1
git bisect good 286da4156dc65c8a054580fdd96b7709132dce8d
git bisect bad 25391454e73e3156202264eb3c473825afe4bc94
git bisect good 218e763f458c44f30041c1b48b4371e130fd4317


first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
KVM: VMX: don't clobber segment AR of unusable segments.


25391454e73e3156202264eb3c473825afe4bc94
emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed"
emulate_invalid_guest_state=1 -> hangs

Please note, I had to compile some revisions with
3f0c3d0bb2bcc4b88b22452a7cf0073ee9a0f1e6 applied, caused by
9ae9febae9500a0a6f5ce29ee4b8d942b5332529.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 13.06.2013 15:42, Paolo Bonzini wrote:
> Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
>> git bisect tells me:
>> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
> 
> This is an s390 commit, so the bisect somehow went wrong.  Can you
> confirm that 3.7 works and 3.8 doesn't?

Confirmed. Something went wrong.
I replayed the bisect log and now I have

git bisect bad 9626357371b519f2b955fef399647181034a77fe
git bisect good ef4e359d9b9e2dc022f79840fd207796b524a893
git bisect good b5c78e04dd061b776978dad61dd85357081147b0
git bisect good 9e2d59ad580d590134285f361a0e80f0e98c0207
git bisect bad 69086a78bdc973ec0b722be790b146e84ba8a8c4
git bisect good 9ecf9b085a0926e07c78c08a07296bbfd1c37d07
git bisect bad 21fbd5809ad126b949206d78e0a0e07ec872ea11
git bisect bad 79fd50c67f91136add9726fb7719b57a66c6f763
git bisect bad aa11e3a8a6d9f92c3fe4b91a9aca5d8c23d55d4d
git bisect good 66cdd0ceaf65a18996f561b770eedde1d123b019
git bisect bad d99e415275dd3f757b75981adad8645cdc26da45

So please wait for my results.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 09.06.2013 11:43, Gleb Natapov wrote:
> On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote:
>> On 06.06.2013 13:40, Gleb Natapov wrote:
>>> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
>>
>>>> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
>>>>
>>>> The machine hangs after "Enabling APIC mode:  Flat.  Using 1 I/O APICs".
>>> OK, since it looks like it hangs during timer initialization can you try
>>> to disable kvmclock? Add -cpu qemu64,-kvmclock to your command line.
>>> Also can you provide the output of "cat /proc/cpuinfo" on your host? And
>>> complete serial output before hang.
>>
>>
>> command line:
>> qemu-system-i386 -machine accel=kvm -m 512 -cpu qemu64,-kvmclock -cdrom
>> grml32-full_2013.02.iso -serial file:ttyS0.log
>>
>>
>> ttyS0.log:
>> ##
>>
> 
> Nothing out of ordinary here. Since you can reproduce the hang and I
> cannot, can you try and bisect it? Also can trace kvm during the hang
> http://www.linux-kvm.org/page/Tracing? Start the trace as close to hang
> as possible and stop it as quick after it as possible too to make trace
> file smaller.


git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit


This is my bisect log:

git bisect start
git bisect bad 9626357371b519f2b955fef399647181034a77fe
git bisect good ef4e359d9b9e2dc022f79840fd207796b524a893
git bisect good b5c78e04dd061b776978dad61dd85357081147b0
git bisect good 9e2d59ad580d590134285f361a0e80f0e98c0207
git bisect bad 69086a78bdc973ec0b722be790b146e84ba8a8c4
git bisect good 9ecf9b085a0926e07c78c08a07296bbfd1c37d07
git bisect bad 21fbd5809ad126b949206d78e0a0e07ec872ea11
git bisect bad 79fd50c67f91136add9726fb7719b57a66c6f763
git bisect good 66cdd0ceaf65a18996f561b770eedde1d123b019


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 06.06.2013 13:40, Gleb Natapov wrote:
> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:

>> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
>>
>> The machine hangs after "Enabling APIC mode:  Flat.  Using 1 I/O APICs".
> OK, since it looks like it hangs during timer initialization can you try
> to disable kvmclock? Add -cpu qemu64,-kvmclock to your command line.
> Also can you provide the output of "cat /proc/cpuinfo" on your host? And
> complete serial output before hang.


command line:
qemu-system-i386 -machine accel=kvm -m 512 -cpu qemu64,-kvmclock -cdrom
grml32-full_2013.02.iso -serial file:ttyS0.log



/proc/cpuinfo:
##

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 14
model name  : Intel(R) Core(TM) Duo CPU  L2400  @ 1.66GHz
stepping: 12
microcode   : 0x54
cpu MHz : 1000.000
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm dtherm
bogomips: 3325.02
clflush size: 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 14
model name  : Intel(R) Core(TM) Duo CPU  L2400  @ 1.66GHz
stepping: 12
microcode   : 0x54
cpu MHz : 1000.000
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm dtherm
bogomips: 3325.02
clflush size: 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:



ttyS0.log:
##

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.7-1-grml-486 (t...@grml.org) (gcc version
4.7.2 (Debian 4.7.2-5) ) #1 Debian 3.7.9-1+grml.1
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff]
usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009]
reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f]
reserved
[0.00] BIOS-e820: [mem 0x0010-0x1fffdfff]
usable
[0.00] BIOS-e820: [mem 0x1fffe000-0x1fff]
reserved
[0.00] BIOS-e820: [mem 0xfeffc000-0xfeff]
reserved
[0.00] BIOS-e820: [mem 0xfffc-0x]
reserved
[0.00] Notice: NX (Execute Disable) protection cannot be
enabled: non-PAE kernel!
[0.00] SMBIOS 2.4 present.
[0.00] Hypervisor detected: KVM
[0.00] e820: last_pfn = 0x1fffe max_arch_pfn = 0x10
[0.00] PAT not supported by CPU.
[0.00] found SMP MP-table at [mem 0x000fdb00-0x000fdb0f] mapped
at [c00fdb00]
[0.00] init_memory_mapping: [mem 0x-0x1fffdfff]
[0.00] RAMDISK: [mem 0x1f33-0x1ffdbfff]
[0.00] ACPI: RSDP 000fd9a0 00014 (v00 BOCHS )
[0.00] ACPI: RSDT 1fffe4b0 00034 (v01 BOCHS  BXPCRSDT 0001
BXPC 0001)
[0.00] ACPI: FACP 1f80 00074 (v01 BOCHS  BXPCFACP 0001
BXPC 0001)
[0.00] ACPI: DSDT 1fffe4f0 011A9 (v01   BXPC   BXDSDT 0001
INTL 20100528)
[0.00] ACPI: FACS 1f40 00040
[0.00] ACPI: SSDT 1800 00735 (v01 BOCHS  BXPCSSDT 0001
BXPC 0001)
[0.00] ACPI: APIC 16e0 00078 (v01 BOCHS  BXPCAPIC 0001
BXPC 0001)
[0.00] ACPI: HPET 16a0 00038 (v01 BOCHS  BXPCHPET 0001
BXPC 0001)
[0.00] 0MB HIGHMEM available.
[0.00] 511MB LOWMEM available.
[0.00]   mapped low ram: 0 - 1fffe000
[0.00]   low ram: 0 - 1fffe000
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x0001-0x00ff]
[0.00]   Normal   [mem 0x0100-0x1fffdfff]
[0.00]   HighMem  empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x0001-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x1fffdfff]
[0.00] Using APIC driver 

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 06.06.2013 08:42, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
>> On 05.06.2013 14:10, Gleb Natapov wrote:
>>> On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
>>>> On 19.05.2013 14:32, Gleb Natapov wrote:
>>>>> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>>>>>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>>>>>> at least on a 32-bit host.  Stefan found this when running GRML, a live
>>>>>> distribution which can be downloaded from:
>>>>>> <http://download.grml.org/grml32-full_2013.02.iso>.  His original
>>>>>> reported is at <http://bugs.debian.org/707257>.
>>>>>>
>>>>> Can you verify with latest linux.git HEAD? It works for me there on
>>>>> 64bit. There were a lot of problems fixed in this area in 3.9/3.10 time 
>>>>> frame,
>>>>> so it would be helpful if you'll test 32bit before I install one myself.
>>>>
>>>>
>>>> Kernel version 3.9.4-1 (linux-image-3.9-1-686-pae) made things worse.
>>>>
>>>> The virtual machine tries to boot the kernel, but stops after a few
>>>> seconds and the kern.log shows:
>>> At what point does it stop?
>>
>>
>> The machine stops at:
>>
>> Performance Events: Broken PMU hardware detected, using software events
>> only.
>> Failed to access perfctr msr (MSR c1 is 0)
>> Enabling APIC mode:  Flat.  Using 1 I/O APICs
> Timer initialization is what comes next.
> 
> I tried 32bit kernel compiled from kvm.git "next" (3.10.0-rc2+) branch and 
> upstream
> qemu and I cannot reproduce the problem. The guest boots fine.


I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).

The machine hangs after "Enabling APIC mode:  Flat.  Using 1 I/O APICs".


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 05.06.2013 14:10, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
>> On 19.05.2013 14:32, Gleb Natapov wrote:
>>> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>>>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>>>> at least on a 32-bit host.  Stefan found this when running GRML, a live
>>>> distribution which can be downloaded from:
>>>> <http://download.grml.org/grml32-full_2013.02.iso>.  His original
>>>> reported is at <http://bugs.debian.org/707257>.
>>>>
>>> Can you verify with latest linux.git HEAD? It works for me there on
>>> 64bit. There were a lot of problems fixed in this area in 3.9/3.10 time 
>>> frame,
>>> so it would be helpful if you'll test 32bit before I install one myself.
>>
>>
>> Kernel version 3.9.4-1 (linux-image-3.9-1-686-pae) made things worse.
>>
>> The virtual machine tries to boot the kernel, but stops after a few
>> seconds and the kern.log shows:
> At what point does it stop?


The machine stops at:

Performance Events: Broken PMU hardware detected, using software events
only.
Failed to access perfctr msr (MSR c1 is 0)
Enabling APIC mode:  Flat.  Using 1 I/O APICs


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 19.05.2013 14:32, Gleb Natapov wrote:
> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>> at least on a 32-bit host.  Stefan found this when running GRML, a live
>> distribution which can be downloaded from:
>> .  His original
>> reported is at .
>>
> Can you verify with latest linux.git HEAD? It works for me there on
> 64bit. There were a lot of problems fixed in this area in 3.9/3.10 time frame,
> so it would be helpful if you'll test 32bit before I install one myself.


Kernel version 3.9.4-1 (linux-image-3.9-1-686-pae) made things worse.

The virtual machine tries to boot the kernel, but stops after a few
seconds and the kern.log shows:

kernel: [13851.000412] kvm [7482]: vcpu0 disabled perfctr wrmsr: 0xc1
data 0x


virtual machine was started with:
qemu-system-i386 -machine accel=kvm -m 512 -cdrom grml32-full_2013.02.iso

qemu-system-x86: 1.5.0+dfsg-3


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 19.05.2013 14:32, Gleb Natapov wrote:
> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>> at least on a 32-bit host.  Stefan found this when running GRML, a live
>> distribution which can be downloaded from:
>> .  His original
>> reported is at .
>>
> Can you verify with latest linux.git HEAD? It works for me there on
> 64bit. There were a lot of problems fixed in this area in 3.9/3.10 time frame,
> so it would be helpful if you'll test 32bit before I install one myself.


Ben,

can you provide a 3.9 series kernel package?

Thanks.


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 09.05.2013 20:56, Stefan Pietsch wrote:
> On 09.05.2013 03:08, Ben Hutchings wrote:
> 
>> Please could you test some of the intermediate versions at
>> <http://snapshot.debian.org/package/linux/> to find the first upstream
>> version where this was broken.
> 
> The first version which does not work is 3.6.4-1~experimental.1.
> 3.5.5-1~experimental.1 works.


I was able to start KVM under kernel version 3.8.12-1 after loading the
"kvm_intel" module with the option "emulate_invalid_guest_state=0".


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

On 09.05.2013 03:08, Ben Hutchings wrote:

> Please could you test some of the intermediate versions at
>  to find the first upstream
> version where this was broken.

The first version which does not work is 3.6.4-1~experimental.1.
3.5.5-1~experimental.1 works.


Regards,
Stefan


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

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

[Stefan Pietsch]

Package: linux-image-3.8-1-686-pae
Version: 3.8.11-1


KVM fails with the unstable kernel 3.8.11-1.


#

kvm -m 512 -cdrom grml32-full_2013.02.iso

KVM: entry failed, hardware error 0x8021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX= EBX=0001 ECX=f000 EDX=f000
ESI=00195e78 EDI= EBP=de84c000 ESP=de84df64
EIP=c101611c EFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =007b   00c0f300 DPL=3 DS   [-WA]
CS =0060   00c09b00 DPL=0 CS32 [-RA]
SS =0068   00c09300 DPL=0 DS   [-WA]
DS =007b   00c0f300 DPL=3 DS   [-WA]
FS =  ffff 00f0ff00 DPL=3 CS64 [CRA]
GS =00e0 c1438b40 0018 00409100 DPL=0 DS   [--A]
LDT=  ffff 00f0ff00 DPL=3 CS64 [CRA]
TR =0080 c1400f00 206b 8b00 DPL=0 TSS32-busy
GDT= c13f6000 00ff
IDT= c13f5000 07ff
CR0=8005003b CR2= CR3=014bc000 CR4=0690
DR0= DR1= DR2=0007
DR3=
DR6=0ff0 DR7=0400
EFER=
Code=ff ff 89 10 c3 8b 15 c4 83 40 c1 8d 84 10 00 c0 ff ff 8b 00  eb
02 f3 90 8b 10 85 d2 74 f8 c3 3d fe 00 00 00 0f 9e c0 0f b6 c0 c3 8b 15
64 7b 40 c1

#


Host CPU: Intel(R) Core(TM) Duo CPU  L2400  @ 1.66GHz
QEMU KVM Package: qemu-kvm 1.1.2+dfsg-6

Running KVM works on this host with the kernel package
linux-image-3.2.0-4-686-pae 3.2.41-2.


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

Bug#673140: cifs-utils: mount.cifs does not work

[Stefan Pietsch]

Package: cifs-utils
Version: 2:5.4-1
Severity: important

Dear Maintainer,

mount.cifs in cifs-utils 5.4-1 does not prompt for a password.
I'm not able to mount a CIFS share.

cifs-utils 5.3-2 does not show this behaviour.


Regards,
Stefan



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (300, 'stable'), (1,
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cifs-utils depends on:
ii  libc6 2.13-32
ii  libcap2   1:2.22-1.1
ii  libkeyutils1  1.5.5-2
ii  libkrb5-3 1.10.1+dfsg-1
ii  libtalloc22.0.7+git20120207-1
ii  libwbclient0  2:3.6.5-2
ii  samba-common  2:3.6.5-2

Versions of packages cifs-utils recommends:
pn  keyutils  1.5.5-2
pn  winbind   

Versions of packages cifs-utils suggests:
ii  smbclient  2:3.6.5-2

-- no debconf information




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

Bug#667636: virt-manager qemu+ssh connects with wrong user

[Stefan Pietsch]

Package: python-libvirt
Version: 0.9.11-1
Severity: normal

After updating python-libvirt and libvirt0 from 0.9.9-3 to 0.9.11-1 the
virt-manager connection with qemu+ssh fails.

---

Example:

$ virt-manager -c qemu+ssh://root@192.168.20.37/system


Unable to connect to libvirt.

Cannot recv data: Permission denied (publickey).
: Connection reset by peer

Verify that the 'libvirtd' daemon is running
on the remote host.

Libvirt URI is: qemu+ssh://root@192.168.20.37/system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1185,
in _open_thread
self.vmm = self._try_open()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1167,
in _try_open
flags)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 102, in
openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Cannot recv data: Permission denied (publickey).
: Connection reset by peer

---


The SSH connection uses my login name on the local machine instead of
the user "root" as in the qemu+ssh URI.

On the server we see in the auth.log:
sshd[19002]: Invalid user stefan from 192.168.20.101



Regards,
Stefan




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

Bug#575126: virt-manager: cannot change ISO image

[Stefan Pietsch]

Changing ISO images in running virtual machines is fixed in libvirt
release 0.8.1.

http://packages.debian.org/changelogs/pool/main/libv/libvirt/libvirt_0.8.1-1/changelog




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

Bug#575126: virt-manager: cannot change ISO image

[Stefan Pietsch]

It is not possible to eject and insert an ISO image as long as a virtual
machine is running.

I already wrote to the virt-tools-list and got no answer so far:

https://www.redhat.com/archives/virt-tools-list/2010-April/msg00035.html




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

Bug#512109: icewm: cannot move window to secondary display when using extended desktop

[Stefan Pietsch]

I have the same problem. After changing the screen setup with xrandr, it
is not possible to move a window to the second screen completely.

icewm 1.2.37-1




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

Bug#492359: ldap-utils: ldapsearch fails to connect to MS AD with user certificate

[Stefan Pietsch]

After changing "configure.options" to "--with-tls=openssl" and
recompiling openldap I can connect to the domain controller.

So there seems to be something wrong with GnuTLS.



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

Bug#492359: ldap-utils: ldapsearch fails to connect to MS AD with user certificate

[Stefan Pietsch]

Package: ldap-utils
Version: 2.4.10-2+lenny1
Severity: normal


lenny ldapsearch cannot connect to MS AD with a user certificate using this 
command:

# ldapsearch -H ldap://192.168.x.x -Y EXTERNAL -Z
SASL/EXTERNAL authentication started
ldap_sasl_interactive_bind_s: Unknown authentication method (-6)


ldaprc:
TLS_CERT./pietsch.pem
TLS_KEY ./privkey.pem
TLS_REQCERT never



This configuration works on etch!

libldap installed on etch:
ii  libldap-2.3-0   2.3.30-5+etch1   OpenLDAP libraries

libldap-2.3-0
  Depends: libc6
  Depends: libsasl2-2
  Depends: libssl0.9.8
  Depends: libldap2


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ldap-utils depends on:
ii  libc62.7-10  GNU C Library: Shared libraries
ii  libgnutls26  2.4.1-1 the GNU TLS library - runtime libr
ii  libldap-2.4-22.4.10-2+lenny1 OpenLDAP libraries
ii  libsasl2-2   2.1.22.dfsg1-21 Cyrus SASL - authentication abstra

Versions of packages ldap-utils recommends:
ii  libsasl2-modules 2.1.22.dfsg1-21 Cyrus SASL - pluggable authenticat

ldap-utils suggests no packages.

-- debconf information excluded



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