Bug#962003: linux-image-5.10.0-20-amd64: Same problem in linux-image-5.10.0-20-amd64 5.10.158-2

2022-12-19 Thread Norbert Kiszka
Package: src:linux
Version: 5.10.158-2
Followup-For: Bug #962003
X-Debbugs-Cc: norb...@linux.pl


Also Lenovo T410 with integrated GPU on i915.



-- Package-specific info:
** Version:
Linux version 5.10.0-20-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.158-2 (2022-12-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-20-amd64 
root=UUID=a73a713e-e9c3-45ba-a787-fc2586ec8077 ro quiet

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[ 2871.039826] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2876.992815] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2882.062257] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2883.064172] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2884.065693] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2885.993010] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2887.071016] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2887.081434] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2887.084043] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2887.092486] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2888.073487] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2891.085125] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2891.086482] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2893.034328] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2894.997005] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2904.022479] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2904.026845] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2905.108058] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2908.995757] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2908.996317] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2918.138795] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2925.155841] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2928.163634] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2934.181978] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2934.186679] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2936.027759] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2936.031047] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2941.194390] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2941.197314] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2950.051319] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2950.051951] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2950.052890] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2952.116656] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.222055] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.225731] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.228881] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.230815] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.239887] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2953.995048] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2955.164202] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2955.991557] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2955.995363] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.002077] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.007957] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.008177] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.008377] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.008623] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.991599] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2956.992705] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may hang.
[ 2959.234550] i915 :00:02.0: [drm] *ERROR* Failed to wait for idle; VT'd 
may 

Bug#629842: Kernel BUG in ext3 filesystem creation

2011-06-09 Thread Norbert Kiszka
Dnia 2011-06-08, śro o godzinie 15:41 -0400, Daniel Richard G. pisze:
 Package: installation-reports
 
 Boot method: hard disk (netboot kernel + initrd) via grub
 Image version: 20110106+squeeze1 (files are dated 2011-03-14)
 
 Machine: Dell Dimension 2350
 Processor: Intel(R) Pentium(R) 4 CPU 2.20GHz
 Memory: 1GB
 Partitions: (fdisk -l output below)
 
 Disk /dev/sda: 120.0 GB, 120034123776 bytes
 255 heads, 63 sectors/track, 14593 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x0ea91612
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1   1   9   722616  FAT16
 /dev/sda2  10   14593   117145949+   5  Extended
 /dev/sda5  10 141 1060258+  82  Linux swap
 /dev/sda6 142 795 5253223+  83  Linux
 /dev/sda7   * 7961840 8393931   83  Linux
 /dev/sda81841   14593   102438441   83  Linux
 
 Output of lspci -knn (or lspci -nn): (see attached)
 
 Base System Installation Checklist:
 [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
 
 Initial boot:   [O]
 Detect network card:[O]
 Configure network:  [O]
 Detect CD:  [ ]
 Load installer modules: [O]
 Detect hard drives: [O]
 Partition hard drives:  [O]
 Install base system:[ ]
 Clock/timezone setup:   [ ]
 User/password setup:[ ]
 Install tasks:  [ ]
 Install boot loader:[ ]
 Overall install:[E]
 
 Comments/Problems:
 
 Everything worked fine up to the point of creating the root ext3
 filesystem. Then a kernel BUG occurred, and the installer remained stuck
 at a blue screen (with white underbar). The system is still responsive;
 I can switch to the other terminals and poke around, but the installer
 is horked.
 
 The console log, recorded via serial cable, is attached.
 
 Note that this error does not occur with testing/unstable installers.

Did You checked this hdd for bad sectors? Check SMART first if possible.

PS. Why 486 kernel instead 686?





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



Bug#576949: [CRASH] Uncaught exception AttributeError in Frontend/Gtk/ChangelogViewer.py:230

2010-04-08 Thread Norbert Kiszka
Package: update-manager-gnome
Version: 0.200.3-1
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ChangelogViewer.py
Severity: normal
Tags: squeeze
Tags: squeeze

*** Please type your report below this line *** Crash after click on bug
report
*** /tmp/update-manager-bugWnqGUu The
information below has been automatically generated. Please do not remove
this from your bug report.  - Exception Type: type
'exceptions.AttributeError' - Exception Value:
AttributeError('ProcessInfo' object has no attribute 'owner_ui',) -
Exception Origin: _MainThread(MainThread, started) - Exception
Traceback:   File
/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ChangelogViewer.py,
line 208, in button_press_event self.open_url(url)   File
/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ChangelogViewer.py,
line 230, in open_url command = ['sudo', '-u#' + pi.owner_ui, command]
-- System Information: Debian Release: squeeze/sid   APT prefers testing  
APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500,
'proposed- updates'), (500, 'stable') Architecture: amd64 (x86_64) 
Kernel: Linux 2.6.34-rc3 (SMP w/2 CPU cores; PREEMPT) Locale:
LANG=pl_PL.UTF-8,
LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Versions of packages update-manager-gnome depends on: ii  gconf2 2.28.0-1
GNOME
configuration database syste ii  gksu 2.0.2-2+b1  graphical frontend to su
ii python   2.5.4-9 An interactive high-level object-o
ii python-dbus  0.83.1-1 simple interprocess messaging
syst ii python-gconf 2.28.0-2 Python bindings for the
GConf conf ii python-gobject   2.20.0-1+b1 Python bindings for
the GObject li ii
python-gtk2  2.16.0-2 Python bindings for the GTK+ widge
ii python-support   1.0.7 automated rebuilding support for P
ii python-vte   1:0.22.5-3 Python bindings for the VTE
widget ii update-manager-core  0.200.3-1 APT update manager core
functional update-manager-gnome recommends no packages.  Versions of
packages update- manager-gnome suggests: ii  software- properties-gtk 
0.60.debian-1.1 manage the repositories that you i ii  update- notifier   
  0.70.7.debian-7 Daemon which notifies about packag





reportbug-update-manager-gnome-20100408-25410-ESsV06
Description: Binary data