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

2020-01-28 Thread Davide Prina 

Hi,

I have try with the new linux-image-5.4.0-3-amd64 (I have see in the 
changelog that this version introduce various i915 modification).


The bug is present also in this version.
Probably it is less frequent (need more time to pop up).

It seem that I have the system freeze only if I use a particular web 
application for 3-4 hours (probably, as workaround, I can try to close 
the browser each hour and restart it). In a normal browser use 
(navigation) I never had a system freeze.


I will wait the 5.5 to see if it will fix this bug.

Ciao
Davide

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

2020-01-17 Thread Davide Prina 

Package: src:linux
Version: 5.4.8-1
Severity: grave
Justification: causes non-serious data loss

I have noted in the last days that sometime the desktop freeze from some 
fraction of second to some seconds and then the desktop is usable again 
without problems.


I have had a longer freeze, then I get a black screen with all blocked.
I have used the Magic Key Ctrl-AltGr-REISU, but I can only have the 
keyboard leds working, Ctrl-Alt-Fx working, but I cannot reach a console 
or the Desktop GUI, so I have done a Ctrl-AltGr-B to reboot.


After reboot, I see the following errors in the log:

Jan 15 11:37:33 prinad03 kernel: [ 9354.966794] i915 :00:02.0: GPU 
HANG: ecode 9:1:0x, hang on rcs0
Jan 15 11:37:33 prinad03 kernel: [ 9354.966797] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including users

pace.
Jan 15 11:37:33 prinad03 kernel: [ 9354.966798] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Inte

l
Jan 15 11:37:33 prinad03 kernel: [ 9354.966799] drm/i915 developers can 
then reassign to the right component if it's not a ker

nel issue.
Jan 15 11:37:33 prinad03 kernel: [ 9354.966800] The GPU crash dump is 
required to analyze GPU hangs, so please always attach i

t.
Jan 15 11:37:33 prinad03 kernel: [ 9354.966801] GPU crash dump saved to 
/sys/class/drm/card0/error
Jan 15 11:37:33 prinad03 kernel: [ 9354.967810] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:33 prinad03 kernel: [ 9354.968580] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request

: 0001, RESET_CTL: 0001}
Jan 15 11:37:33 prinad03 kernel: [ 9354.968680] i915 :00:02.0: 
Resetting chip for hang on rcs0
Jan 15 11:37:33 prinad03 kernel: [ 9354.970473] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request

: 0001, RESET_CTL: 0001}
Jan 15 11:37:33 prinad03 kernel: [ 9354.971264] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, 
RESET_CTL: 0001}
Jan 15 11:37:36 prinad03 kernel: [ 9358.166773] Asynchronous wait on 
fence i915:gnome-shell[1935]:184e0 timed out 
(hint:intel_atomic_commit_ready+0x0/0x50 [i915])
Jan 15 11:37:43 prinad03 kernel: [ 9364.950744] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:51 prinad03 kernel: [ 9372.950740] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:53 prinad03 kernel: [ 9374.966742] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:55 prinad03 kernel: [ 9376.950742] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:57 prinad03 kernel: [ 9378.966745] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:37:59 prinad03 kernel: [ 9380.950742] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:01 prinad03 kernel: [ 9382.966734] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:03 prinad03 kernel: [ 9384.950697] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:05 prinad03 kernel: [ 9386.966738] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:07 prinad03 kernel: [ 9388.950738] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:09 prinad03 kernel: [ 9390.966738] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:11 prinad03 kernel: [ 9392.950737] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:13 prinad03 kernel: [ 9394.966734] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:15 prinad03 kernel: [ 9396.950732] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:17 prinad03 kernel: [ 9398.966735] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:19 prinad03 kernel: [ 9400.950740] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:21 prinad03 kernel: [ 9402.966724] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:23 prinad03 kernel: [ 9404.950754] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:25 prinad03 kernel: [ 9406.966730] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:27 prinad03 kernel: [ 9408.950736] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0
Jan 15 11:38:29 prinad03 kernel: [ 9410.966733] i915 :00:02.0: 
Resetting rcs0 for hang on rcs0


$ cat /sys/class/drm/card0/error
No error state collected

Probably this is due because I have reboot the PC.

I have searched back to see if there are error for the previously 
momentaney freezes and I found the following line more than once.


kernel: [29704.922284] i915 :00:02.0: Resetting rcs0 for stuck wait 
on rcs0


I think that I get all the freezes when I'm using firefox.
I can reproduce the "dead" freeze when I use an internal web application 
for about 0,5h - 1h. The freeze seem to be random and not on a specific 
operation (I can do the last operation that generate the freeze after a 
reboot).


I have noted that the line before or near before is always the following 
(but

Bug#875781: initramfs-tools-core: /etc/initramfs-tools/initramfs.conf is not modified on upgrade/install/reconfigure

2017-09-16 Thread Davide Prina 

On 15/09/2017 20:28, Ben Hutchings wrote:


Which version did you start with before this?


$ ls -lt /etc/ | tail -n 1
[...] nov 20  1999 [...]

I think this can be the installation date, I have change all the 
hardware, but I have copied the system in the new disk without reinstalling.
If I don't mistake I have installed a stable, but after a while I have 
installed testing and never change it.



Was initramfs.conf modified?


I think I never modified it.


I tried this, starting with jessie (debootstrap'd chroot plus
initramfs-tools) and then changing APT sources to stretch.
initramfs.conf was upgraded as intended.


I have check this problem in two Debian box with testing and all have 
the same problem.


$ ls -l /etc/initramfs-tools/initramfs.conf
-rw-r--r-- 1 root root 947 lug  9  2012 /etc/initramfs-tools/initramfs.conf

But if you make a change to the initramfs.conf and than do
# apt install --reinstall initramfs-tools-core
is the file updated or are you asked if you want to install the DD version?

Ciao
Davide

Bug#875781: initramfs-tools-core: /etc/initramfs-tools/initramfs.conf is not modified on upgrade/install/reconfigure

2017-09-14 Thread Davide Prina 
Package: initramfs-tools-core
Version: 0.130
Severity: normal

Dear Maintainer,

# apt update; apt -u upgrade; apt -u dist-upgrade
# dpkg-reconfigure initramfs-tools-core
# apt install --reinstall initramfs-tools-core
[...]
$ mkdir /tmp/1
$ cd /tmp/1
$ ar x initramfs-tools-core_0.130_all.deb
$ tar Jxvf data.tar.xz
[...]
$ diff etc/initramfs-tools/initramfs.conf /etc/initramfs-tools/initramfs.conf
23c23
< # BUSYBOX: [ y | n | auto ]
---
> # BUSYBOX: [ y | n ]
25,27c25
< # Use busybox shell and utilities.  If set to n, klibc utilities will be used.
< # If set to auto (or unset), busybox will be used if installed and klibc will
< # be used otherwise.
---
> # Use busybox if available.
30c28
< BUSYBOX=auto
---
> BUSYBOX=y

Ciao
Davide

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

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

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 24-1
ii  udev 234-3

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

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

-- Configuration Files:
/etc/initramfs-tools/initramfs.conf changed:
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto


-- no debconf information

Bug#868066: linux-image-4.11.0-1-amd64: Error! Bad return status for module build on kernel (virtualbox 5.1.10 error: too few arguments)

2017-07-11 Thread Davide Prina 

Package: src:linux
Version: 4.11.6-1
Severity: normal

Dear Maintainer,

I upgraded my Buster system and I get the following error:
---8<-8<-8<-8<-8<-8<-8<-8<-8<--
Configurazione di linux-headers-4.11.0-1-amd64 (4.11.6-1)...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.11.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/5.1.10/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.11.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.1.10/build/make.log for more 
information.

---8<-8<-8<-8<-8<-8<-8<-8<-8<--



I have see that there is a patch:
https://www.virtualbox.org/ticket/16576




$ cat /var/lib/dkms/virtualbox/5.1.10/build/make.log
DKMS make.log for virtualbox-5.1.10 for kernel 4.11.0-1-amd64 (x86_64)
mar 11 lug 2017, 20.00.13, CEST
make: ingresso nella directory "/usr/src/linux-headers-4.11.0-1-amd64"
  LD  /var/lib/dkms/virtualbox/5.1.10/build/built-in.o
  LD  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/built-in.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/linux/SUPDrv-linux.o

  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M] 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: 
In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1067:18: 
error: too few arguments to function ‘get_user_pages_remote’

 rc = get_user_pages_remote(
  ^
In file included from 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
 from 
/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.11.0-1-common/include/linux/mm.h:1326:6: note: 
declared here

 long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
  ^
/usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:299: set 
di istruzioni per l'obiettivo 
"/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o" 
non riuscito
make[4]: *** 
[/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] 
Errore 1

make[4]: *** Attesa per i processi non terminati
/usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:558: set 
di istruzioni per l'obiettivo 
"/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv" non riuscito

make[3]: *** [/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv] Errore 2
/usr/src/linux-headers-4.11.0-1-common/Makefile:1509: set di istruzioni 
per l'obiettivo "_module_/var/lib/dkms/virtualbox/5.1.10/build" non riuscito

make[2]: *** [_module_/var/lib/dkms/virtualbox/5.1.10/build] Errore 2
Makefile:152: set di istruzioni per l'obiettivo "sub-make" non riuscito
make[1]: *** [sub-make] Errore 2
Makefile:8: set di istruzioni per l'obiettivo "all" non riuscito
make: *** [all] Errore 2
make: uscita dalla directory "/usr/src/linux-headers-4.11.0-1-amd64"

Ciao
Davide

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

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 2201
board_vendor: ASUSTeK Computer INC.
board_name: P5Q DELUXE
board_version: Rev 1.xx

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM 
Controller [8086:2e20] (rev 03)

Subsystem: ASUSTeK Computer Inc. P5Q Deluxe Motherboard [1043:82d3]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-06-25 Thread Davide Prina 
colliar wrote:

 Did you try the linux-image from jessie ?

yes, I'm using it.
For now I don't have had system freeze.

I only have sometimes (very rare) gnome-shell freeze, but this can be
resolved very fast with this workaround:

Ctrl-Alt-F1
- login as your user (not root)
$ killall -9 gnome-shell
$ exit
Alt-F7

Ciao
Davide

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-06-04 Thread Davide Prina 
I have had a freeze using LibreOffice and the last update of Linux in
testing.

I think that this bug severity can be raised because it can cause data lost.

Ciao
Davide

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-06-04 Thread Davide Prina 

On 04/06/2013 14:06, Ben Hutchings wrote:

On Tue, 2013-06-04 at 10:15 +0200, Davide Prina wrote:

I have had a freeze using LibreOffice and the last update of Linux in
testing.



I think that this bug severity can be raised because it can cause data
lost.


Do you want Debian to ever release again?  Then you must allow that not
every crasher bug is grave and release-critical.


but you can write in the release notes that if you have an Intel video 
card you can have freeze and to resolve (as workaround) you must use a 
linux-image not released in the stable Wheezy.



The kernel team agreed that 'data loss' covers corruption or silent
failure of disk writes or corruption of network transmissions.  You must
assume that memory is volatile (even UPS and batteries can fail).
Auto-save is your friend.


but here you have freeze and you can only use AltrGr-Stamp-b or the 
power button. This can also cause file/filesystem corruption and not 
only you can lose the last change you have made. And not all can be 
auto-saved...


I think that this type of bug can make users unhappy and Debian can lose 
users.


Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Petizione per uso di software interoperabile nell'UE:
http://openparliament.eu/
Non autorizzo la memorizzazione del mio indirizzo su outlook


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ae2a1f.9090...@gmail.com

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-05-29 Thread Davide Prina 

On 29/05/2013 14:04, JS Ubei wrote:


I am still able to reproduce this bug with my up to date wheezy.


I was not able to reproduce it with the last Wheezy update.
Some day ago I have upgrade to new version Jessy and also here I don't 
have freezes.



My computer freeze two time this morning when I was scrolling a libreoffice 
writer doc.


I'm using now less libreoffice write. I don't know if this can be the 
cause of the not freezing.



And no, I can't switch to a console to kill the X session, whole computer is 
frozen.


Yes, this can be done only with another problem. Only one time I have 
had access to the console with the freeze.


Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Petizione contro i brevetti software in Europa:
http://petition.stopsoftwarepatents.eu/
Non autorizzo la memorizzazione del mio indirizzo su outlook


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51a65ca2.8020...@gmail.com

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-05-17 Thread Davide Prina 
I think that this bug is not present with the latest Linux version 
entered in Wheezy two day ago.

I haven't no freeze in two days.

I have CC to all people so all you can confirm if the bug is not present 
in the last Wheezy Linux version.


@piruthiviraj natarajan

probably you have another bug. I don't know (have understand) what is 
the package responsible for that (gnome-shell?)
I think the bug you have can be resolved with the followings steps 
without killing the X session:


Ctrl-Alt-F1
- login as your user (not root)
$ killall -9 gnome-shell
$ exit
Alt-F7

You have all your windows working again and you don't lose nothing.

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Database: http://www.postgresql.org
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51967160.9000...@gmail.com

Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze

2013-03-22 Thread Davide Prina 
Package: src:linux
Version: 3.2.39-2
Severity: important

Dear Maintainer,

I think that the severity can be raised because it give you an
unusable system and data loss (all the data you don't have saved).

I have experienced some random system freeze: I can move only the
mouse cursors, the system is not responding, the keyboard led cannot
be switched on/off, I can't go to a terminal with Ctrl-Alt-F1, only
magic keys work and I can to the AltGr-Stamp-reisub to reboot my
system.

Only one time I have a system responding, I don't have a gnome-shell
process and I cannot activate a new one (it cannot found an X server);
in Ctrl-F7 I can see only one program and iteract to it (I cannot
switch to another one), if I close it I see another one and I can
operate with it. This time I have had an error in the logs:
Mar 21 10:44:09 lideb2 kernel: [ 8125.550475]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
hung
Mar 21 10:44:09 lideb2 kernel: [ 8125.550480] [drm] capturing error
event; look for more information in /debug/dri/0/i915_error_state

I have see that there are a lot of bug with this error for some intel
VGA controller, but I have found only old bug.

I'm using this system for about one year without a freeze.
I can completely solve the problem using the linux-image-3.2.0-3-amd64.

$ lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200
Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 2 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC
Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller
[RAID mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)


   * What led up to the situation?

upgrading the linux-image from linux-image-3.2.0-3-amd64 to
linux-image-3.2.0-4-amd64

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I use it for work and I'm not doing nothing special. Principally I'm
using LibreOffice at freeze time.

   * What was the outcome of this action?

the system freeze and I can only move the mouse or use the magic keys
to reboot the system.

   * What outcome did you expect instead?

an usable system! ;-)



-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc
version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64
root=UUID=97bbf21c-5e82-4108-9a56-7403591e29f9 ro quiet

** Tainted: IO (6144)
 * Working around severe firmware bug.
 * Out-of-tree module has been loaded.

** Kernel log:
[1.465649] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[1.465653] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1.465932] hub 2-1:1.0: USB hub found
[1.466044] hub 2-1:1.0: 8 ports detected
[1.597031] Refined TSC clocksource calibration: 2594.107 MHz.
[1.597037] Switching to clocksource tsc
[1.736938] usb 2-1.7: new low-speed USB device number 3 using ehci_hcd
[1.802488] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x1b
[1.804250] platform microcode: firmware: agent loaded
intel-ucode/06-2a-07 into memory
[1.804791] microcode: CPU0 updated to revision 0x28, date = 2012-04-24
[1.804834] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x1b
[1.806358] platform microcode: firmware: agent loaded
intel-ucode/06-2a-07 into memory
[1.806647] microcode: CPU1 updated to revision 0x28, date = 2012-04-24
[1.806680] microcode: Microcode Update Driver: v2.00
tig...@aivazian.fsnet.co.uk, Peter Oruba
[1.811012] device-mapper: uevent: version 1.0.3
[1.811128] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19)
initialised: dm-de...@redhat.com
[1.832207] usb 2-1.7: New USB device found, idVendor=0461, idProduct=4d64
[1.832212] usb 2-1.7: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[1.832215] usb 2-1.7: Product: USB Optical Mouse
[1.836872] input: USB Optical Mouse as

Bug#598810: linux-image-xen-amd64: bug in package description generation

2010-10-02 Thread Davide Prina 

Package: linux-image-xen-amd64
Version: bug in package description generation
Severity: minor

this package have the same bug of linux-image-2.6-xen-amd64:
#598648

Ciao
Davide

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

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

--
Dizionari: http://linguistico.sourceforge.net/wiki
Client di posta: http://www.mozilla.org/products/thunderbird
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ca6ecce.7000...@gmail.com

Bug#598648: linux-image-2.6-xen-amd64: typo in package description

2010-09-30 Thread Davide Prina 

Package: linux-image-2.6-xen-amd64
Severity: minor

In DDTSS I see:

Linux 2.6 for 64-bit PCs (meta-package), Xen dom0 support, Xen dom0 support

I think it must be:

Linux 2.6 for 64-bit PCs (meta-package), Xen dom0 support, Xen domU 
support   ^

__|

I also see (twice):

This kernel also runs on a Xen hypervisor. It supports both privileged 
(dom0) and unprivileged (domU) operation.

.
This kernel also runs on a Xen hypervisor. It supports both privileged 
(dom0) and unprivileged (domU) operation.


Ciao
Davide

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

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

--
Dizionari: http://linguistico.sourceforge.net/wiki
Browser: http://www.mozilla.org/products/firefox
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ca4dda1.6040...@gmail.com

Bug#544592: linux-image-2.6.30-1-686: sometimes failed to boot

2009-09-05 Thread Davide Prina 

Ben Hutchings wrote:

On Thu, 2009-09-03 at 22:17 +0200, Davide Prina wrote:

Ben Hutchings wrote:

On Tue, 2009-09-01 at 20:44 +0200, Davide Prina wrote:


sometimes the boot fail: after grub I see: Loading, please wait ..., 
but the hard disk is not used.
After a while busybox appear; here I can see that /proc/cmdline try to 
start something in directory /dev/disk/by-id, but this directory don't 
exists.



The problem there appeared to be that your custom kernel included two
different drivers that both supported your disk controller.



How can you found when a module is a duplication of another one?


In general, grep for the device id string in modules.alias.


I have done the following steps:

$ lspci
[...]
00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 
(FastTrak100 Lite/Ultra100) (rev 02)

[...]

$ cat /sys/bus/pci/devices/\:00\:11.0/vendor
0x105a
$ cat /sys/bus/pci/devices/\:00\:11.0/device
0x0d30


You can find drivers that claim this device using:

grep pci:v105Ad0D30 /lib/modules/$(uname -r)/modules.alias


If I use the 2.6.30-1-686 as $(uname -r) I have:

$ for i in $(grep pci: /lib/modules/$(uname -r)/modules.alias \
 | sed s/^.*:v\([^v]*\)v.*$/pci:v\1/); do \
   if [ $(grep $i /lib/modules/$(uname -r)/modules.alias | wc -l) \
-gt 1 ]; then \
echo $i - $(grep $i /lib/modules/$(uname -r)/modules.alias | \
  wc -l); \
   fi; \
  done

pci:v10ECd8139s - 2
[...]

$ grep ci:v10ECd8139s /lib/modules/2.6.30-1-686/modules.alias
alias pci:v10ECd8139sv*sd*bc*sc*i* 8139cp
alias pci:v10ECd8139sv*sd*bc*sc*i* 8139too

in fact I have 8139too, in my custom Linux I have:
$ grep ci:v10ECd8139s /lib/modules/2.6.30-custom/modules.alias
alias pci:v10ECd8139sv*sd*bc*sc*i* 8139too

why this duplication in 2.6.30-1-686 do not generate problems?
Only some duplication type can generate problems?

but still have problems. I noted that good boots have greatly increased 
over bad boots (I have made few reboots and nearly all are good now).


this is a wrong information.
Bad boot persist. Probably I have had a long good boot series.

When I have a bad boot I have the message saying that it is impossible 
to remove the SCSI_WAIT_SCAN module (I have disable the module 
unloading option).

[...]

Reenable CONFIG_MODULE_UNLOAD and see if you can boot.


done.
It seem that now the boot is ok.
I don't know if I'm in a long good boot series or the problem is resolved.

But how enabling the unloading module will solve the boot problems?
I don't understand.

I read this DD announce The future of the boot system in Debian

http://lists.debian.org/debian-devel-announce/2009/09/msg3.html

I think this can be the real problem I have encountered. Or not?

Very thanks for all your help

I will inform you next days if I have again bad boots

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Strumenti per l'ufficio: http://it.openoffice.org
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook



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

Bug#544592: linux-image-2.6.30-1-686: sometimes failed to boot

2009-09-03 Thread Davide Prina 

Ben Hutchings wrote:

On Tue, 2009-09-01 at 20:44 +0200, Davide Prina wrote:

Package: linux-image-2.6.30-1-686
Version: 2.6.30-6
Severity: important


Are you actually using the above packaged kernel or a custom kernel?


normally I use a custom kernel.

sometimes the boot fail: after grub I see: Loading, please wait ..., 
but the hard disk is not used.
After a while busybox appear; here I can see that /proc/cmdline try to 
start something in directory /dev/disk/by-id, but this directory don't 
exists.



The problem there appeared to be that your custom kernel included two
different drivers that both supported your disk controller.  In this
case the kernel effectively chooses one driver at random.  In packaged
kernel images we try to avoid this by avoiding such duplication or
blacklisting alternate drivers by default.


I don't know that a module can cause these problems. I have always think 
that a module is loaded only if needed and this process is deterministic.


How can you found when a module is a duplication of another one?

I have done the following steps:

$ lspci
[...]
00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 
(FastTrak100 Lite/Ultra100) (rev 02)

[...]

$ cat /sys/bus/pci/devices/\:00\:11.0/vendor
0x105a
$ cat /sys/bus/pci/devices/\:00\:11.0/device
0x0d30

$ grep -i 0x105a\|0x0d30 /usr/src/linux/include/linux/pci_ids.h | sort
#define PCI_DEVICE_ID_PROMISE_20265 0x0d30
#define PCI_VENDOR_ID_PROMISE   0x105a

$ grep -Rl PCI_DEVICE_ID_PROMISE_20265\|PCI_VENDOR_ID_PROMISE \
  /usr/src/linux
/usr/src/linux/arch/powerpc/platforms/powermac/pci.c
/usr/src/linux/drivers/ata/pata_pdc202xx_old.c
/usr/src/linux/drivers/block/sx8.c
/usr/src/linux/drivers/ide/pdc202xx_old.c
/usr/src/linux/drivers/message/i2o/pci.c
/usr/src/linux/include/linux/pci_ids.h

in file /usr/src/linux/drivers/ata/pata_pdc202xx_old.c I have found:
static const struct pci_device_id pdc202xx[]

in file /usr/src/linux/drivers/ide/pdc202xx_old.c I have found:
static const struct pci_device_id pdc202xx_pci_tbl[] = {

$ find /usr/src/linux/ -type f -name Makefile | xargs grep pdc202xx \
  | grep CONFIG_ | sed s/\/usr\/src\/linux\///
drivers/ata/Makefile:obj-$(CONFIG_PATA_PDC_OLD) += pata_pdc202xx_old.o
drivers/ide/Makefile:obj-$(CONFIG_BLK_DEV_PDC202XX_OLD) += pdc202xx_old.o
drivers/ide/Makefile:obj-$(CONFIG_BLK_DEV_PDC202XX_NEW) += pdc202xx_new.o

$ grep CONFIG_PATA_PDC_OLD\|CONFIG_BLK_DEV_PDC202XX_OLD \
  /boot/config-2.6.30-1-686
CONFIG_BLK_DEV_PDC202XX_OLD=m
# CONFIG_PATA_PDC_OLD is not set

$ grep CONFIG_PATA_PDC_OLD\|CONFIG_BLK_DEV_PDC202XX_OLD \
  /boot/config-2.6.30-1-custom
CONFIG_BLK_DEV_PDC202XX_OLD=m
CONFIG_PATA_PDC_OLD=m

I have recompiled and now I have
$ grep CONFIG_PATA_PDC_OLD\|CONFIG_BLK_DEV_PDC202XX_OLD \
  /boot/config-2.6.30-1-custom
CONFIG_BLK_DEV_PDC202XX_OLD=m
# CONFIG_PATA_PDC_OLD is not set

but still have problems. I noted that good boots have greatly increased 
over bad boots (I have made few reboots and nearly all are good now).
When I have a bad boot I have the message saying that it is impossible 
to remove the SCSI_WAIT_SCAN module (I have disable the module 
unloading option). When busybox appear I see the same problem 
(directory /dev/disk/by-id is missing).


$ grep SCSI_WAIT_SCAN /boot/config-2.6.30-custom CONFIG_SCSI_WAIT_SCAN=m
$ grep SCSI_WAIT_SCAN /boot/config-2.6.30-1-686
CONFIG_SCSI_WAIT_SCAN=m

I have done some wrong steps?
What else could I have done wrong?

Many thanks for your help

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Perché microsoft continua a compiere azioni illegali?:
http://linguistico.sf.net/wiki/doku.php?id=traduzioni:ms_illegal
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook




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

Bug#544592: linux-image-2.6.30-1-686: sometimes failed to boot

2009-09-01 Thread Davide Prina 

Package: linux-image-2.6.30-1-686
Version: 2.6.30-6
Severity: important

sometimes the boot fail: after grub I see: Loading, please wait ..., 
but the hard disk is not used.
After a while busybox appear; here I can see that /proc/cmdline try to 
start something in directory /dev/disk/by-id, but this directory don't 
exists.


Probably somethings crash of freeze and the boot fail.

To solve the problem I have to reboot X times (X = 0) with 
Ctrl-Alt-Canc or AltGr-RSyst-b.


I think this problem is related to the bug #543209. I don't have anymore 
the disks remapped, but I cannot boot sometimes (I think that the 
remapped problem is migrated into the boot fail problem).


Please if you think this bug is not related to the linux-image package 
than reassign. I have reported the bug to this package because bug 
#543209 start when I installed Linux 2.6.30 the first time and this bug 
appear when I have upgrade to the new Linux 2.6.30 subversion


Please don't close the bug as the #543209 with no explanation, please 
help me to understand the problem.


If you need more information let me know.

Ciao
Davide


-- Package-specific info:

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

Kernel: Linux 2.6.30-customized
Locale: lang=it...@euro, lc_ctype=it...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.27 Debian configuration 
management sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an 
initramfs
ii  module-init-tools 3.10-3 tools for managing Linux 
kernel mo


Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i6862.9-25 GNU C Library: Shared 
libraries [i


Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub-pc [grub]   1.96+20090808-1 GRand Unified Bootloader, 
version

pn  linux-doc-2.6.30 none  (no description available)

-- debconf information:
  linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true

linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: 
true

  linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686:
  linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false
  linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686:
  linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true

--
Dizionari: http://linguistico.sourceforge.net/wiki
Perché microsoft continua a compiere azioni illegali?:
http://linguistico.sf.net/wiki/doku.php?id=traduzioni:ms_illegal
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook




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

Bug#543209: linux-image-2.6.30-1-686: sometimes /dev/hdX are remapped as /dev/sdX

2009-08-28 Thread Davide Prina 

Package: linux-image-2.6.30-1-686
Version: 2.6.30-6
Severity: important

I set the severity to important because if you make a Linux upgrade when 
the disks are mapped as /dev/sdX, then your system will no boot anymore.


I have modify the /boot/grub/grub.cfg from knoppix to have a 
successfully boot (I was unable to do nothing with the grub command line)


Ciao
Davide

-- Package-specific info:

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

Kernel: Linux 2.6.30-customized
Locale: lang=it...@euro, lc_ctype=it...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.27 Debian configuration 
management sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an 
initramfs
ii  module-init-tools 3.9-2  tools for managing Linux 
kernel mo


Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i6862.9-23 GNU C Library: Shared 
libraries [i


Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub-pc [grub]   1.96+20090808-1 GRand Unified Bootloader, 
version

pn  linux-doc-2.6.30 none  (no description available)

-- debconf information:
  linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true

linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: 
true

  linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686:
  linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false
  linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686:
  linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true


--
Dizionari: http://linguistico.sourceforge.net/wiki
Client di posta: http://www.mozilla.org/products/thunderbird
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook




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