Re[4]: resume file
But I wonder whether this configuration file is really needed for most system. Couldn't we use blkid to find the swap partition automagically? (The configuration file would still be necessary if there are multiple swap partitions.) Imagine the following: there is Debian on /dev/sda1, Debian on /dev/sda2 and swap on /dev/sda3. Debian on sda2 configured to use sda3. Debian on sda1 doesn't use swap. Debian on sda2 suspends to sda3. Then user runs Debian on sda1. Initramfs from sda1 looks at the sda3 and says: Oh! There is swap. Let's wake up from it. And initramfs performs waking up from wrong partition. So, don't search swap at the resume time. initramfs-tools has its own resume configuration file, but so far as I can see the uswsusp package does not use it. So there would be no reason for you to modify it - would there? No, resume file is really used. It used by early userspace. I just created virtual machine with fresh jessie and without swap and performed the following test: 1. Installed uswsusp. uswsusp said to me that I have no swap and I should add it and run dpkg-reconfigure uswsusp. 2. I added swap 3. Rebooted 4. I ran dpkg-reconfigure uswsusp. uswsusp found my swap and it was happy. It asked me a lot of questions. Then uswsusp triggered initramfs rebuilding 5. Rebooted 6. I ran s2disk and I could not wake up. So, this is a bug. 7. I created resume file (there was no such file before) and I put RESUME=UUID=... to it. 8. I ran s2disk and it failed again (of course, because /etc/initramfs-tools/conf.d/resume alone is not enough, there should be /conf/conf.d/resume in initramfs). 9. I ran dpkg-reconfigure uswsusp, it triggered initramfs (so, /conf/conf.d/resume was created) 10. I successfully performed s2disk In fact, s2disk works (without manual editing configs) only if you created swap at installing of Debian. The uswsusp package can edit its own configuration file though I do not recommend it. I think it would be better to leave the resume device unspecified in /etc/uswsusp.conf by default, and then to select it automatically (both at suspend and resume time) if possible. As I said, selecting automatically at resume time is bad idea. At suspend time is probably, too, because two systems can have one swap. Ideally, there should be some guarantee that if user didn't edit configs himself and it performed suspend then he guaranteed wakes up successfully. Of course, such guarantee is very important because user can have a lot of opened programs, unsaved documents etc. Ideally, s2disk should perform some checks (for example, it can check configs) that all is OK, before doing real suspending. If uswsusp detects swap automatically, then there was no such guarantee. For example, let's assume, uswsusp detects swap automatically, and let's assume this bug #632627 is fixed (i. e. dpkg-reconfigure uswsusp writes resume). User just added new swap and didn't run any dpkg-reconfigure yet. Then he ran s2disk. s2disk detected his swap, suspended. And then this user cannot wake up, because dpkg-reconfigure is not done and resume is not written. Askar Safin
Bug#716827: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it
Package: src:linux Version: 3.9.8-1 Followup-For: Bug #716827 Dear Maintainer, The bug can be closed. * What exactly did you do (or not do) that was effective (or ineffective)? The reported camera had been deactivated by hardware by mean of a rather bizarre key combination. After realizing that, I activated it. Now the camera is working without any problem. Sorry for the annoyance. I really didn't know that it is possible to change the camera state in this way. robert -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/nyxVG-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 17.132399] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251) [ 17.132409] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.132413] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 17.132670] ACPI Warning: 0xf040-0xf05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) [ 17.132698] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.133041] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [ 17.140257] iTCO_vendor_support: vendor-support=0 [ 17.140857] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 17.140901] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [ 17.140993] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 17.153707] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input7 [ 17.153863] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 17.154003] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 17.173250] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 582762 [ 17.208092] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input10 [ 17.460063] ACPI: AC Adapter [AC] (off-line) [ 17.461015] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461027] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461033] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461043] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461056] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.461287] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461299] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461304] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461314] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461325] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.461878] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461906] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461911] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461919] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461933] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.467192] ACPI: Marking method ADJP as Serialized because of AE_ALREADY_EXISTS error [ 17.468112] ACPI: Marking method _PSR as Serialized because of AE_ALREADY_EXISTS error [ 17.775074] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 17.975784] ACPI: Battery Slot [BAT0] (battery present) [ 17.976227] wmi: Mapper loaded [ 18.315303] Adding 8785916k swap on /dev/mapper/nyxVG-swap. Priority:-1 extents:1 across:8785916k SS [ 18.340752] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 18.442669] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [ 18.712810] fuse init (API version 7.21) [ 18.725937] loop: module loaded [ 19.039358] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 19.472002] RPC: Registered named UNIX socket transport module. [ 19.472008] RPC: Registered udp transport
Bug#716827: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it
And what exactly was/is the key combination in case others (like me) need it and have no clue about it? :-) On 7/29/13, robert robert.carde...@gmail.com wrote: Package: src:linux Version: 3.9.8-1 Followup-For: Bug #716827 Dear Maintainer, The bug can be closed. * What exactly did you do (or not do) that was effective (or ineffective)? The reported camera had been deactivated by hardware by mean of a rather bizarre key combination. After realizing that, I activated it. Now the camera is working without any problem. Sorry for the annoyance. I really didn't know that it is possible to change the camera state in this way. robert -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/nyxVG-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 17.132399] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251) [ 17.132409] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.132413] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 17.132670] ACPI Warning: 0xf040-0xf05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) [ 17.132698] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.133041] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [ 17.140257] iTCO_vendor_support: vendor-support=0 [ 17.140857] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 17.140901] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [ 17.140993] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 17.153707] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input7 [ 17.153863] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 17.154003] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 17.173250] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 582762 [ 17.208092] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input10 [ 17.460063] ACPI: AC Adapter [AC] (off-line) [ 17.461015] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461027] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461033] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461043] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461056] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.461287] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461299] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461304] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461314] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461325] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.461878] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dswload2-330) [ 17.461906] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20130117/psobject-222) [ 17.461911] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461919] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537) [ 17.461933] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter state (20130117/ac-122) [ 17.467192] ACPI: Marking method ADJP as Serialized because of AE_ALREADY_EXISTS error [ 17.468112] ACPI: Marking method _PSR as Serialized because of AE_ALREADY_EXISTS error [ 17.775074] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 17.975784] ACPI: Battery Slot [BAT0] (battery present) [ 17.976227] wmi: Mapper loaded [ 18.315303] Adding 8785916k swap on /dev/mapper/nyxVG-swap. Priority:-1 extents:1 across:8785916k SS [ 18.340752] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 18.442669] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [ 18.712810] fuse init (API version 7.21) [ 18.725937]
Bug#717473: [PATCH] adm64_edac: Fix single-channel setups
It can happen that configurations are running in a single-channel mode even with a dual-channel memory controller, by, say, putting the DIMMs only on the one channel and leaving the other empty. This causes a problem in init_csrows which implicitly assumes that when the second channel is enabled, i.e. channel 1, the struct dimm hierarchy will be present. Which is not. So always allocate two channels unconditionally. This provides for the nice side effect that the data structures are initialized so some day, when memory hotplug is supported, it should just work out of the box when all of a sudden a second channel appears. Reported-and-tested-by: Roger Leigh rle...@debian.org Signed-off-by: Borislav Petkov b...@suse.de --- drivers/edac/amd64_edac.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c index 8b6a0343c220..8b3d90143514 100644 --- a/drivers/edac/amd64_edac.c +++ b/drivers/edac/amd64_edac.c @@ -2470,8 +2470,15 @@ static int amd64_init_one_instance(struct pci_dev *F2) layers[0].size = pvt-csels[0].b_cnt; layers[0].is_virt_csrow = true; layers[1].type = EDAC_MC_LAYER_CHANNEL; - layers[1].size = pvt-channel_count; + + /* +* Always allocate two channels since we can have setups with DIMMs on +* only one channel. Also, this simplifies handling later for the price +* of a couple of KBs tops. +*/ + layers[1].size = 2; layers[1].is_virt_csrow = false; + mci = edac_mc_alloc(nid, ARRAY_SIZE(layers), layers, 0); if (!mci) goto err_siblings; -- 1.8.3 -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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/20130729124501.ga6...@pd.tnic
Re: Re[4]: resume file
Askar Safin safinas...@mail.ru escribió: But I wonder whether this configuration file is really needed for most system. Couldn't we use blkid to find the swap partition automagically? (The configuration file would still be necessary if there are multiple swap partitions.) Imagine the following: there is Debian on /dev/sda1, Debian on /dev/sda2 and swap on /dev/sda3. Debian on sda2 configured to use sda3. Debian on sda1 doesn't use swap. Debian on sda2 suspends to sda3. Then user runs Debian on sda1. Initramfs from sda1 looks at the sda3 and says: Oh! There is swap. Let's wake up from it. And initramfs performs waking up from wrong partition. So, don't search swap at the resume time. initramfs-tools has its own resume configuration file, but so far as I can see the uswsusp package does not use it. So there would be no reason for you to modify it - would there? No, resume file is really used. It used by early userspace. I just created virtual machine with fresh jessie and without swap and performed the following test: 1. Installed uswsusp. uswsusp said to me that I have no swap and I should add it and run dpkg-reconfigure uswsusp. 2. I added swap 3. Rebooted 4. I ran dpkg-reconfigure uswsusp. uswsusp found my swap and it was happy. It asked me a lot of questions. Then uswsusp triggered initramfs rebuilding 5. Rebooted 6. I ran s2disk and I could not wake up. So, this is a bug. 7. I created resume file (there was no such file before) and I put RESUME=UUID=... to it. 8. I ran s2disk and it failed again (of course, because /etc/initramfs-tools/conf.d/resume alone is not enough, there should be /conf/conf.d/resume in initramfs). 9. I ran dpkg-reconfigure uswsusp, it triggered initramfs (so, /conf/conf.d/resume was created) 10. I successfully performed s2disk In fact, s2disk works (without manual editing configs) only if you created swap at installing of Debian. The uswsusp package can edit its own configuration file though I do not recommend it. I think it would be better to leave the resume device unspecified in /etc/uswsusp.conf by default, and then to select it automatically (both at suspend and resume time) if possible. As I said, selecting automatically at resume time is bad idea. At suspend time is probably, too, because two systems can have one swap. Ideally, there should be some guarantee that if user didn't edit configs himself and it performed suspend then he guaranteed wakes up successfully. Of course, such guarantee is very important because user can have a lot of opened programs, unsaved documents etc. Ideally, s2disk should perform some checks (for example, it can check configs) that all is OK, before doing real suspending. If uswsusp detects swap automatically, then there was no such guarantee. For example, let's assume, uswsusp detects swap automatically, and let's assume this bug #632627 is fixed (i. e. dpkg-reconfigure uswsusp writes resume). User just added new swap and didn't run any dpkg-reconfigure yet. Then he ran s2disk. s2disk detected his swap, suspended. And then this user cannot wake up, because dpkg-reconfigure is not done and resume is not written. Askar Safin So, initramfs-tools should read /etc/uswsusp.conf and add the resume device to the resume file? Then, when the user run dpkg-reconfigure uswsusp, update-initramfs-tools will update the initrd resume file and then the system know where find the resume file. kix -- .''`. : :' : Rodolfo García Peñas (kix) k...@debian.org `. `'` Proud Debian Developer `- -- 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/20130729130751.horde.ggzmg5ghlboc4fcibdrm...@mail.kix.es
Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package
Source: linux Version: 3.10.3-1 Severity: normal Build ends here with error: install -m 644 debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.builtin debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.order debian/kernel-image-3.10-1-parisc-di/lib/modules/3.10-1-parisc/ install -D -m 644 debian/linux-image-3.10-1-parisc/boot/System.map-3.10-1-parisc debian/kernel-image-3.10-1-parisc-di/boot/System.map-3.10-1-parisc kernel-wedge copy-modules 3.10-1 parisc 3.10-1-parisc kernel-wedge find-dups 3.10-1-parisc some modules are in more than one package debian/ext4-modules-3.10-1-parisc-di lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko debian/ext3-modules-3.10-1-parisc-di lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko command exited with status 1 make[2]: *** [install-udeb_hppa] Error 2 make[2]: Leaving directory `/mnt/debian/linux/linux-3.10.3' make[1]: *** [binary-arch_hppa] Error 2 make[1]: Leaving directory `/mnt/debian/linux/linux-3.10.3' make: *** [binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Build command 'cd linux-3.10.3 dpkg-buildpackage -b -uc' failed. Fetched 76.5 MB in 41s (1,838 kB/s) -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 3.11.0-rc2+ (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/blu0-smtp436d0bf5e4cbe26f7d540d97...@phx.gbl
Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.
Source: linux Version: 3.10.3-1 Severity: important Justification: fails to build from source (but built successfully in the past) Hi, the latest Linux kernel source package fails to build: […] make[2]: Entering directory `/tmp/buildd/linux-3.10.3' dh_testdir dh_prep kernel-wedge install-files 3.10-1 could not find kernel image at /usr/share/kernel-wedge/commands/install-files line 101, KVERS line 2. make[2]: *** [install-udeb_m68k] Error 2 make[2]: Leaving directory `/tmp/buildd/linux-3.10.3' make[1]: *** [binary-arch_m68k] Error 2 […] Full log attached. -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 3.2.0-4-atari Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static -- 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/20130729144615.4763.81228.report...@ara3.mirbsd.org
Bug#718271: linux: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.
Sorry, of course I forgot the attachment… bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” (#nosec)‣‣‣ Please let MySQL and MariaDB finally die! linux_3.10.3-1_m68k.build.gz Description: Binary data
Bug#717473: [PATCH] adm64_edac: Fix single-channel setups
There's a typo in the subject line. :-) Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package
Processing control commands: tag -1 patch Bug #718270 [src:linux] linux: FTBFS on hppa: module mbcache.ko is in more than one package Added tag(s) patch. -- 718270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b718270.137511046731876.transcr...@bugs.debian.org
Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package
Control: tag -1 patch On Mon, 2013-07-29 at 10:03 -0400, John David Anglin wrote: Source: linux Version: 3.10.3-1 Severity: normal Build ends here with error: install -m 644 debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.builtin debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.order debian/kernel-image-3.10-1-parisc-di/lib/modules/3.10-1-parisc/ install -D -m 644 debian/linux-image-3.10-1-parisc/boot/System.map-3.10-1-parisc debian/kernel-image-3.10-1-parisc-di/boot/System.map-3.10-1-parisc kernel-wedge copy-modules 3.10-1 parisc 3.10-1-parisc kernel-wedge find-dups 3.10-1-parisc some modules are in more than one package debian/ext4-modules-3.10-1-parisc-di lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko debian/ext3-modules-3.10-1-parisc-di lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko command exited with status 1 make[2]: *** [install-udeb_hppa] Error 2 make[2]: Leaving directory `/mnt/debian/linux/linux-3.10.3' make[1]: *** [binary-arch_hppa] Error 2 make[1]: Leaving directory `/mnt/debian/linux/linux-3.10.3' make: *** [binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Build command 'cd linux-3.10.3 dpkg-buildpackage -b -uc' failed. Fetched 76.5 MB in 41s (1,838 kB/s) Does this patch (applied with -p0) fix it? --- debian/installer/hppa/modules/hppa/core-modules (revision 0) +++ debian/installer/hppa/modules/hppa/core-modules (working copy) @@ -0,0 +1 @@ +#include core-modules --- END --- Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.
On Mon, 2013-07-29 at 14:46 +, Thorsten Glaser wrote: Source: linux Version: 3.10.3-1 Severity: important Justification: fails to build from source (but built successfully in the past) [...] Well you gave us the new m68k configuration. I kind of hoped you'd at least done a full build test. The installer udeb configuration under debian/installer/m68k still refers to three flavours that were removed. You can either try to fix it straight away or we can delete it and not try to build the udebs at all. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#717473: [PATCH] adm64_edac: Fix single-channel setups
On Mon, Jul 29, 2013 at 04:00:52PM +0100, Ben Hutchings wrote: There's a typo in the subject line. :-) Yep, looks like I've gradually gotten unnaccustomed to typing amd ... it's not in the fingers anymore. :-) Thanks, fixed. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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/20130729151814.gf6...@pd.tnic
Bug#716827: marked as done (linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it)
Your message dated Mon, 29 Jul 2013 16:19:52 +0100 with message-id 137592.2546.73.ca...@deadeye.wl.decadent.org.uk and subject line Re: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it has caused the Debian Bug report #716827, regarding linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 716827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.9.8-1 Severity: normal Dear Maintainer, I installed Wheezy on March when frozen. This was version 3.2.35-2 of the linux-image. The tested the webcam using Cheese because the laptop was recently adquired. It worked out-of-the-box. The installer logged it as /var/log/installer/hardware-summary: usb-list: Bus 03 Device 03: BisonCam, NB Pro [5986:0400] usb-list:Level 02 Parent 02 Port 00 Class ef(misc ) Subclass 02 Protocol 01 usb-list:Manufacturer: Bison usb-list:Interface 00: Class 0e(video) Subclass 01 Protocol 00 Driver none usb-list:Interface 01: Class 0e(video) Subclass 02 Protocol 00 Driver none usb-list: A month after releasing Wheezy as stable, I updated to Jessie. Last week I wanted to use the webcam with Cheese again. The program started but nothing was displayed. Messages in ~/.xsession-errors said that there was not any device. I installed Camorama obtaining similar behavior and errors. After searching, I was aware that any application can use /dev/video* because it does not exist on my system. Neither any module related with a webcam is loaded when booting the system (uvcvideo, ...). I loaded it manually via modprobe and automatically using /etc/modules. The modules are loaded well but nothing else happens (absence of /dev/video* file). Any log file in /var/log/* makes reference to a webcam. Not a word using lspci and lsusb. I am only a user and I have run out of ideas. If necessary, I can provide the initial installation log files. Thank you in advance, robert -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/nyxVG-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 19.154782] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 [ 19.154787] ACPI: Sleep Button [SLPB] [ 19.154849] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3 [ 19.155499] ACPI: Lid Switch [LID0] [ 19.155580] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 19.155585] ACPI: Power Button [PWRF] [ 19.156091] ACPI: Requesting acpi_cpufreq [ 19.159414] ACPI: AC Adapter [AC] (on-line) [ 19.160613] ACPI: Battery Slot [BAT0] (battery absent) [ 19.166408] wmi: Mapper loaded [ 19.171240] mei :00:16.0: setting latency timer to 64 [ 19.171307] mei :00:16.0: irq 44 for MSI/MSI-X [ 19.181240] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 19.183319] ACPI Warning: 0x0428-0x042f SystemIO conflicts with Region \PMIO 1 (20130117/utaddress-251) [ 19.183325] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.183330] ACPI Warning: 0x0530-0x053f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251) [ 19.183334] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.183335] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251) [ 19.183339] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.183340] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 19.185048] ACPI Warning: 0xf040-0xf05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) [ 19.185055] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.195962] cfg80211: Calling CRDA to update world regulatory domain [ 19.206250] [drm] Initialized drm 1.1.0 20060810 [ 19.216139] [drm] Memory usable by graphics device = 2048M [
Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.
Ben Hutchings dixit: Well you gave us the new m68k configuration. I kind of hoped you'd at least done a full build test. I wasn’t quick enough, it all takes a lot of time. I literally could not have finished before you uploaded. The installer udeb configuration under debian/installer/m68k still refers to three flavours that were removed. You can either try to fix it straight away or we can delete it and not try to build the udebs at all. Oh, I see. Everything else built fine, and you can inspect that at https://www.freewrt.org/~tg/dp/dists/hacks/clean/Notyet/ for things like module list and ABI files already. Wouter, will you update the d-i modules again, like you usually do? Thanks and sorry for the mess, //mirabilos -- 22:20⎜asarch The crazy that persists in his craziness becomes a master 22:21⎜asarch And the distance between the craziness and geniality is only measured by the success 18:35⎜asarch Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent -- 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/pine.bsm.4.64l.1307291606490.16...@herc.mirbsd.org
Bug#714295: [PATCH libata/for-3.11-fixes] libata: make it clear that sata_inic162x is experimental
Hello, Greg. I think the following commit should go into -stable but forgot to cc stable. It's now in Linus' tree. Can you please include it in -stable? Thanks! On Mon, Jul 22, 2013 at 05:13:07PM -0400, Tejun Heo wrote: From bb9696192826a7d9279caf872e95b41bc26c7eff Mon Sep 17 00:00:00 2001 From: Tejun Heo t...@kernel.org Date: Mon, 22 Jul 2013 16:53:36 -0400 sata_inic162x never reached a state where it's reliable enough for production use and data corruption is a relatively common occurrence. Make the driver generate warning about the issues and mark the Kconfig option as experimental. If the situation doesn't improve, we'd be better off making it depend on CONFIG_BROKEN. Let's wait for several cycles and see if the kernel message draws any attention. Signed-off-by: Tejun Heo t...@kernel.org Reported-by: Martin Braure de Calignon braur...@free.fr Reported-by: Ben Hutchings b...@decadent.org.uk Reported-by: risc4...@yahoo.com --- drivers/ata/Kconfig | 2 +- drivers/ata/sata_inic162x.c | 14 ++ 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig index 80dc988..5cddaf8 100644 --- a/drivers/ata/Kconfig +++ b/drivers/ata/Kconfig @@ -107,7 +107,7 @@ config SATA_FSL If unsure, say N. config SATA_INIC162X - tristate Initio 162x SATA support + tristate Initio 162x SATA support (Very Experimental) depends on PCI help This option enables support for Initio 162x Serial ATA. diff --git a/drivers/ata/sata_inic162x.c b/drivers/ata/sata_inic162x.c index e451317..5c54d95 100644 --- a/drivers/ata/sata_inic162x.c +++ b/drivers/ata/sata_inic162x.c @@ -6,6 +6,18 @@ * * This file is released under GPL v2. * + * WARNING + * + * This driver never worked properly and unfortunately data corruption is + * relatively common. There isn't anyone working on the driver and there's + * no support from the vendor. Do not use this driver in any production + * environment. + * + * http://thread.gmane.org/gmane.linux.debian.devel.bugs.rc/378525/focus=54491 + * https://bugzilla.kernel.org/show_bug.cgi?id=60565 + * + * * + * * This controller is eccentric and easily locks up if something isn't * right. Documentation is available at initio's website but it only * documents registers (not programming model). @@ -807,6 +819,8 @@ static int inic_init_one(struct pci_dev *pdev, const struct pci_device_id *ent) ata_print_version_once(pdev-dev, DRV_VERSION); + dev_alert(pdev-dev, inic162x support is broken with common data corruption issues and will be disabled by default, contact linux-...@vger.kernel.org if in production use\n); + /* alloc host */ host = ata_host_alloc_pinfo(pdev-dev, ppi, NR_PORTS); hpriv = devm_kzalloc(pdev-dev, sizeof(*hpriv), GFP_KERNEL); -- 1.8.3.1 -- tejun -- 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/20130729165229.gf22...@mtj.dyndns.org
Bug#716827: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it
Hi, And what exactly was/is the key combination in case others (like me) need it and have no clue about it? :-) Neither did I. That was the problem. The key combination is Alt-F10. I do not know if this is a standard key combination because it it my first notebook. So I probably pressed it without noticing it. Moreover, this model (Clevo W55) does not have the led lights to show the state (enabled/disabled) of some of its hardware like the numeric keypad and wifi card even though I really knew they can be enabled/disabled by similar key combinations. If more information is needed, let me know. robert -- 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/1375117475.4208.31.camel@nyx
Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package
On 29-Jul-13, at 11:07 AM, Ben Hutchings wrote: Does this patch (applied with -p0) fix it? --- debian/installer/hppa/modules/hppa/core-modules (revision 0) +++ debian/installer/hppa/modules/hppa/core-modules (working copy) @@ -0,0 +1 @@ +#include core-modules --- END --- With the patch, the build completes successfully. On a different subject, could the build version of gcc be bumped from 4.4 to 4.7 or 4.8? Thanks for the quick response, Dave -- John David Anglin dave.ang...@bell.net -- 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/blu0-smtp26811ad399150e8c0c1fd897...@phx.gbl
Bug#589855: marked as done (linux-image-2.6.32-bpo.5-amd64: p54pci doesn't work with ISL3890 based card)
Your message dated Mon, 29 Jul 2013 21:28:28 +0200 with message-id 20130729192828.ge27...@inutil.org and subject line Re: p54pci doesn't work with ISL3890 based card has caused the Debian Bug report #589855, regarding linux-image-2.6.32-bpo.5-amd64: p54pci doesn't work with ISL3890 based card to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 589855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-15~bpo50+1 Severity: important This card worked with the original prism54 driver. The p54pci driver causes problems. I have tried different versions of the firmware (see the kernel log below) with the same error message: 'phyX: device does not respond!' As advised @ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497873 I am filing a new bug against 2.6.32. Is there any workaround, except for enabling PRISM54? -- Package-specific info: ** Version: Linux version 2.6.32-bpo.5-amd64 (Debian 2.6.32-15~bpo50+1) (norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Fri Jun 11 08:42:31 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-bpo.5-amd64 root=/dev/mapper/vg1-lvroot ro ** Not tainted ** Kernel log: [ 14.544299] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 14.544355] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.544408] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.544456] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.544514] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.544566] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 14.544617] cfg80211: Calling CRDA for country: US [ 14.582886] parport_pc 00:08: reported by Plug and Play ACPI [ 14.582973] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 14.714351] alloc irq_desc for 20 on node -1 [ 14.714354] alloc kstat_irqs on node -1 [ 14.714361] p54pci :03:00.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 14.714460] p54pci :03:00.0: firmware: requesting isl3886pci [ 15.094039] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 15.096509] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 19 [ 15.537927] p54pci :03:00.0: Cannot find firmware (isl3886pci) [ 15.537982] p54pci :03:00.0: firmware: requesting isl3886 [ 15.541913] p54pci :03:00.0: PCI INT A disabled [ 15.541972] p54pci: probe of :03:00.0 failed with error -2 [ 17.040407] EXT3 FS on dm-1, internal journal [ 17.712759] loop: module loaded [ 19.214173] kjournald starting. Commit interval 5 seconds [ 19.244415] EXT3 FS on md0, internal journal [ 19.244483] EXT3-fs: mounted filesystem with ordered data mode. [ 19.604744] kjournald starting. Commit interval 5 seconds [ 19.644375] EXT3 FS on dm-3, internal journal [ 19.64] EXT3-fs: mounted filesystem with ordered data mode. [ 20.779403] tun: Universal TUN/TAP device driver, 1.6 [ 20.779472] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 20.841492] Bridge firewalling registered [ 20.845808] device tap10 entered promiscuous mode [ 20.852680] device tap11 entered promiscuous mode [ 20.855180] device eth0 entered promiscuous mode [ 20.856311] alloc irq_desc for 26 on node -1 [ 20.856314] alloc kstat_irqs on node -1 [ 20.856327] atl1c :02:00.0: irq 26 for MSI/MSI-X [ 20.856422] atl1c :02:00.0: atl1c: eth0 NIC Link is Up1000 Mbps Full Duplex [ 20.858874] br0: port 3(eth0) entering learning state [ 20.858921] br0: port 2(tap11) entering learning state [ 20.858964] br0: port 1(tap10) entering learning state [ 30.860011] br0: no IPv6 routers present [ 30.864090] eth0: no IPv6 routers present [ 30.992017] tap10: no IPv6 routers present [ 31.644019] tap11: no IPv6 routers present [ 35.856507] br0: port 3(eth0) entering forwarding state [ 35.856558] br0: port 2(tap11) entering forwarding state [ 35.856605] br0: port 1(tap10) entering forwarding state [ 112.560011] tap0: no IPv6 routers present [ 4094.553141] p54pci :03:00.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 4094.553254] p54pci :03:00.0: firmware: requesting isl3886pci [ 4094.556691] p54pci :03:00.0: Cannot find firmware (isl3886pci) [ 4094.556731] p54pci :03:00.0: firmware: requesting isl3886 [ 4094.560454] p54pci :03:00.0: PCI INT A disabled [ 4094.560496] p54pci: probe of :03:00.0 failed with error -2 [ 4382.629133] p54pci :03:00.0: PCI
Processed: Re: [hyr...@gmail.com: Re: [bluetooth] Modifier keys (ctrl, shift, alt) do not stack]
Processing commands for cont...@bugs.debian.org: reassign 614936 src:linux Bug #614936 [linux-2.6] Modifier keys (ctrl, shift, alt) not working - Bluetooth keyboard Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #614936 to the same values previously set Ignoring request to alter fixed versions of bug #614936 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 614936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13751263563029.transcr...@bugs.debian.org
Processed: Re: Bug#647011: update
Processing commands for cont...@bugs.debian.org: reassign 647011 src:linux Bug #647011 [linux-2.6] udev randomly stuck on boot while running udevadm settle Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #647011 to the same values previously set Ignoring request to alter fixed versions of bug #647011 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 647011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13751263593066.transcr...@bugs.debian.org
Bug#603469: marked as done (radeon: atombios stuck executing F6D8 (screen randomly goes black with no way to get it back))
Your message dated Mon, 29 Jul 2013 21:27:57 +0200 with message-id 20130729192756.ga27...@inutil.org and subject line Re: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back has caused the Debian Bug report #603469, regarding radeon: atombios stuck executing F6D8 (screen randomly goes black with no way to get it back) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 603469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-ati Version: 1:6.13.1-2 Severity: important after some random time period my screen goes black and nothing i do short of rebooting can bring it back ... i have gotten quite good at switching to a new console and logging in and rebooting without being able to see what i'm doing btw the system is still running normally but no display at all i am using the open source ati driver with a Thinkpad T500 ... KMS is enabled and the DRM module is loading correctly -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Dec 27 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733468 Oct 10 14:03 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 22:47:19 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 33504 Nov 14 13:50 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.23-dsa-ia32 i686 Debian Current Operating System: Linux BUZZ 2.6.32-5-686 #1 SMP Sat Oct 30 22:47:19 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=564cf89a-18e1-46e3-acd0-159224283f2e ro quiet Build Date: 10 October 2010 11:57:07AM xorg-server 2:1.7.7-8 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 14 13:50:44 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) 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, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:9591:17aa:2117 ATI Technologies Inc Mobility Radeon HD 3650 rev 0, Mem @ 0xd000/268435456, 0xcfff/65536, I/O @ 0x2000/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension
Bug#647011: update
reassign 647011 src:linux thanks On Oct 29, Christoph Keller keller.christop...@googlemail.com wrote: Then i switched back to tty1 and executed exec /sbin/init single - freeze Great, then this is not my problem. I suggest that you use udev.exec-delay and udev.children-max=1 as explained in udevd(8) to identify the driver which crashes your system. Does this bug still occur with more recent kernels, e.g. Wheezy? Cheers, Moritz -- 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/20130729192840.gh27...@inutil.org
Bug#607533: marked as done (udev hangs at boot for 180 sec because of a C$R570 bios version)
Your message dated Mon, 29 Jul 2013 21:28:32 +0200 with message-id 20130729192832.gf27...@inutil.org and subject line Re: 180-second hang loading ipmi_si module has caused the Debian Bug report #607533, regarding udev hangs at boot for 180 sec because of a C$R570 bios version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 607533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udev Version: 0.125-7+lenny3 Severity: important because of a nasty machine version (see lshw below), udev stops for about 180 seconds at boot. i tried the udev package from stable and testing with the same result. LSHW node01 description: Tower Computer product: CELSIUS R570-2 vendor: FUJITSU version: C$R570 serial: YL7E002389 width: 64 bits capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32 configuration: boot=normal chassis=tower uuid=739B94BB-D11E-69A0-AA3A-0019998A2FC1 [...] -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 64 -rw-r--r-- 1 root root 3801 2009-08-26 12:27 50-udev.rules -rw-r--r-- 1 root root 1601 2009-08-26 12:27 60-persistent-input.rules -rw-r--r-- 1 root root 4873 2009-08-26 12:27 60-persistent-storage.rules -rw-r--r-- 1 root root 1488 2009-08-26 12:27 60-persistent-storage-tape.rules -rw-r--r-- 1 root root 523 2009-08-26 12:27 60-persistent-v4l.rules -rw-r--r-- 1 root root 991 2009-05-07 13:03 65_mdadm.vol_id.rules -rw-r--r-- 1 root root 700 2010-10-20 16:31 70-persistent-cd.rules -rw-r--r-- 1 root root 578 2010-10-20 16:31 70-persistent-net.rules -rw-r--r-- 1 root root 452 2009-08-26 12:27 75-cd-aliases-generator.rules -rw-r--r-- 1 root root 4427 2009-08-26 12:27 75-persistent-net-generator.rules -rw-r--r-- 1 root root 2507 2009-08-26 12:27 80-drivers.rules -rw-r--r-- 1 root root 4559 2009-08-26 12:27 91-permissions.rules -rw-r--r-- 1 root root 593 2009-08-26 12:27 95-late.rules -- /sys/: /sys/dev /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3/dev /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2/dev /sys/devices/pci:00/:00:1a.0/usb1/dev /sys/devices/pci:00/:00:1a.1/usb2/dev /sys/devices/pci:00/:00:1a.2/usb3/dev /sys/devices/pci:00/:00:1a.7/usb7/dev /sys/devices/pci:00/:00:1b.0/input/input5/event5/dev /sys/devices/pci:00/:00:1b.0/sound/card0/controlC0/dev /sys/devices/pci:00/:00:1b.0/sound/card0/hwC0D2/dev /sys/devices/pci:00/:00:1b.0/sound/card0/pcmC0D0c/dev /sys/devices/pci:00/:00:1b.0/sound/card0/pcmC0D0p/dev /sys/devices/pci:00/:00:1b.0/sound/card0/pcmC0D1p/dev /sys/devices/pci:00/:00:1d.0/usb4/dev /sys/devices/pci:00/:00:1d.1/usb5/dev /sys/devices/pci:00/:00:1d.2/usb6/dev /sys/devices/pci:00/:00:1d.7/usb8/dev /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/dev /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1/dev /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2/dev /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/bsg/0:0:0:0/dev /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/scsi_generic/sg0/dev /sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/block/sr0/dev /sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0/dev /sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/scsi_generic/sg1/dev /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/block/sdb/dev /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/block/sdb/sdb1/dev /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/block/sdb/sdb2/dev /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/bsg/3:0:0:0/dev /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/scsi_generic/sg2/dev /sys/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdc/dev /sys/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdc/sdc1/dev /sys/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdc/sdc2/dev /sys/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0/dev /sys/devices/pci:00/:00:1f.2/host4/target4:0:0/4:0:0:0/scsi_generic/sg3/dev /sys/devices/platform/i8042/serio0/input/input1/event1/dev /sys/devices/platform/pcspkr/input/input4/event4/dev /sys/devices/platform/pcspkr/sound/card1/controlC1/dev /sys/devices/platform/pcspkr/sound/card1/pcmC1D0p/dev /sys/devices/platform/serial8250/tty/ttyS1/dev
Bug#614936: [hyr...@gmail.com: Re: [bluetooth] Modifier keys (ctrl, shift, alt) do not stack]
reassign 614936 src:linux thanks The most recent kernel was 3.2.7 with aptosid tweaks of sorts. Wheezy is based on more recent 3.2 kernels. Does it work for you with Wheezy? Cheers, Moritz -- 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/20130729192836.gg27...@inutil.org
Bug#718297: linux-source-3.10: broken binary package contains uncompressed member data.tar.gz
Package: linux-source-3.10 Version: 3.10.3-1 Severity: important The binary package linux-source-3.10 does not comply to man 5 deb. It contains a data.tar.gz, that is not a valid gzip file. While the cause is in dpkg (see #718295). I ask you to work around this issue, by passing -z1 instead of -z0. Helmut -- 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/20130729194117.ga26...@alf.mars
Bug#713943: linux kernel drivers/macintosh: windfarm module is not working any more
Comparing two Debian kernels: $ uname -rv 3.2.0-4-powerpc64 #1 SMP Debian 3.2.41-2 $ lsmod | grep windfarm windfarm_cpufreq_clamp 4265 1 windfarm_max6690_sensor 6030 1 windfarm_lm75_sensor 6521 1 windfarm_smu_sensors 7587 1 windfarm_smu_controls 7770 7 windfarm_pm112 14636 0 windfarm_smu_sat8271 5 windfarm_pm112 windfarm_pid4095 1 windfarm_pm112 windfarm_core 12117 7 windfarm_smu_sat,windfarm_pm112,windfarm_smu_controls,windfarm_smu_sensors,windfarm_lm75_sensor,windfarm_max6690_sensor,windfarm_cpufreq_clamp $ dmesg | grep windfarm [5.184978] windfarm: initializing for dual-core desktop G5 [ 10.488713] windfarm: CPUs control loops started. [ 13.914914] windfarm: Backside control loop started. [ 13.965432] windfarm: Slots control loop started. [ 14.070479] windfarm: Drive bay control loop started. $ ls /sys/devices/platform/windfarm.0/ backside-fan cpufreq-clampcpu-power-1 cpu-temp-1 driver slots-fan backside-temp cpu-front-fan-0 cpu-rear-fan-0 cpu-voltage-0 hd-temp slots-power cpu-current-0 cpu-front-fan-1 cpu-rear-fan-1 cpu-voltage-1 modalias subsystem cpu-current-1 cpu-power-0 cpu-temp-0 drive-bay-fan power uevent $ cat /sys/devices/platform/windfarm.0/cpu-front-fan-* 524 524 $ cat /sys/devices/platform/windfarm.0/cpu-rear-fan-* 562 562 $ uname -rv 3.10-1-powerpc64 #1 SMP Debian 3.10.3-1 (2013-07-27) $ lsmod | grep windfarm windfarm_cpufreq_clamp 4001 1 windfarm_max6690_sensor 4843 0 windfarm_lm75_sensor 5305 0 windfarm_smu_sensors 7691 1 windfarm_smu_controls 7954 7 windfarm_pm112 14588 0 windfarm_smu_sat8348 1 windfarm_pm112 windfarm_pid3975 1 windfarm_pm112 windfarm_core 12029 7 windfarm_cpufreq_clamp,windfarm_pm112,windfarm_smu_sensors,windfarm_smu_sat,windfarm_lm75_sensor,windfarm_max6690_sensor,windfarm_smu_controls $ dmesg | grep windfarm [5.130698] windfarm: initializing for dual-core desktop G5 $ ls /sys/devices/platform/windfarm.0/ backside-fan cpu-front-fan-0 cpu-rear-fan-0 drive-bay-fan modalias slots-fansubsystem cpufreq-clamp cpu-front-fan-1 cpu-rear-fan-1 driver power slots-power uevent $ cat /sys/devices/platform/windfarm.0/cpu-front-fan-* 0 RPM 0 RPM $ cat /sys/devices/platform/windfarm.0/cpu-rear-fan-* 0 RPM 0 RPM You can help a lot, if you can build and upload kernel packages for vanilla 3.5.x, 3.6.x, 3.7.x, and 3.8.x. That's how we can find a working one (good) kernel very fast. Then we can bisect kernel git source repo for first bad commit. On Sun, Jul 28, 2013 at 4:45 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2013-07-28 at 12:25 -0400, Douglas Mencken wrote: Right, we have this big stockpile of hardware we could test on I can provide SSH access to the G5 box. P.S. Sadly, I have no microphone to show you how noisy it is on 6000 rpm of 8 fans :) Is anyone able to investigate this, or suggest how to proceeed? It's apparently a regression between 3.8 and 3.9, but the windfarm driver itself appears unchanged between those versions. Ben. -- Ben Hutchings All extremists should be taken out and shot.
Re[2]: Bug#632627: Re[2]: resume file
1. uswsusp will use the initramfs resume device. So, uswsusp should read the file included in the initrd image at conf/conf.d/resume. Is ok? If you mean configure time (i. e. dpkg-reconfigure uswsusp) or suspending time, then, of course, no. Because this requires unpacking initramfs, and this is slow. Use /etc/initramfs-tools/conf.d/resume . Of course, at wake up time use /conf/conf.d/resume. 6. What file should read s2disk and s2both to find the resume device when they save the image? They should use same device which used by early userspace when this userspace perform waking up (to be sure waking up is possible). So, we should read /etc/initramfs-tools/conf.d/resume . 8a. I am not sure about this, because initramfs-tools is required by the kernel, but there are case that uswsusp doesn't depends on initramfs-tools and use the resume device in /etc/uswsusp.conf if initramfs-tools is not installed? Could be initramfs-tools not installed and uswsusp installed? Yes. Kernel depends on initramfs-tools | linux-initramfs-tool and linux-initramfs-tool is virtual package provided by initramfs-tools and dracut. So, this is possible if you using dracut instead of initramfs-tools. (This information is about sid.) 8. debian/control file: uswsusp will depends on initramfs-tools? uswsusp triggers initramfs rebuilding. So, if you want initramfs-tools, add dependency initramfs-tools. If you can work with both initramfs-tools and dracut, add dependency initramfs-tools | linux-initramfs-tool. So, initramfs-tools should read /etc/uswsusp.conf and add the resume device to the resume file? I think, yes. Then, when the user run dpkg-reconfigure uswsusp, update-initramfs-tools will update the initrd resume file and then the system know where find the resume file. Yes Askar
Processed: tagging 718270
Processing commands for cont...@bugs.debian.org: tags 718270 + pending Bug #718270 [src:linux] linux: FTBFS on hppa: module mbcache.ko is in more than one package Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 718270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.1375136552765.transcr...@bugs.debian.org
Bug#718312: linux-image-3.10-1-amd64: Kernel panic crashes drm_kms_helper causing hard lockup
The mei_me resetting crapflood is intermittent and I have not reproduced it. Looks like this: https://bbs.archlinux.org/viewtopic.php?pid=1305751 -- Ben Caradoc-Davies b...@wintersun.org -- 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/51f701ef.3030...@wintersun.org
Re: Bug#632627: Re[2]: Bug#632627: Re[2]: resume file
On Tue, 30 Jul 2013, Askar Safin escribió:
1. uswsusp will use the initramfs resume device. So, uswsusp should read the
file included in the initrd image at conf/conf.d/resume. Is ok?
If you mean configure time (i. e. dpkg-reconfigure uswsusp) or suspending
time, then, of course, no. Because this requires unpacking initramfs, and
this is slow.
Use /etc/initramfs-tools/conf.d/resume . Of course, at wake up time use
/conf/conf.d/resume.
6. What file should read s2disk and s2both to find the resume device when
they save the image?
They should use same device which used by early userspace when this userspace
perform waking up (to be sure waking up is possible). So, we should read
/etc/initramfs-tools/conf.d/resume .
8a. I am not sure about this, because initramfs-tools is required by the
kernel, but there are case that uswsusp doesn't depends on initramfs-tools
and use the resume device in /etc/uswsusp.conf if initramfs-tools is not
installed? Could be initramfs-tools not installed and uswsusp installed?
Yes. Kernel depends on initramfs-tools | linux-initramfs-tool and
linux-initramfs-tool is virtual package provided by initramfs-tools and
dracut. So, this is possible if you using dracut instead of initramfs-tools.
(This information is about sid.)
8. debian/control file: uswsusp will depends on initramfs-tools?
uswsusp triggers initramfs rebuilding. So, if you want initramfs-tools, add
dependency initramfs-tools. If you can work with both initramfs-tools and
dracut, add dependency initramfs-tools | linux-initramfs-tool.
So, initramfs-tools should read /etc/uswsusp.conf and add the resume
device to the resume file?
I think, yes.
Then, when the user run dpkg-reconfigure uswsusp,
update-initramfs-tools will update the initrd resume file and then the
system know where find the resume file.
Yes
Askar
Hi Askar,
thanks a lot for your reply. Could this initramfs-tools patch solve the problem?
Some tips:
1. The patch reads the /etc/uswsusp.conf, and check if the file exists. The
value is not changed to UUID.
2. I check if uswsusp is installed if the s2disk binary exists. Checking the
config file only could be an error if the package was removed (not purged).
3. The resume device is created always, not only when initramfs-tools is
installed. Because the user can change the device.
Comments are welcome.
Cheers,
kix
diff -ur initramfs-tools-0.113.orig/debian/initramfs-tools.preinst initramfs-tools-0.113/debian/initramfs-tools.preinst
--- initramfs-tools-0.113.orig/debian/initramfs-tools.preinst 2013-07-30 01:46:30.0 +0200
+++ initramfs-tools-0.113/debian/initramfs-tools.preinst 2013-07-30 01:11:08.0 +0200
@@ -2,43 +2,9 @@
set -e
-chrooted() {
- # borrowed from udev's postinst
- if [ $(stat -c %d/%i /) = $(stat -Lc %d/%i /proc/1/root 2/dev/null) ]; then
- # the devicenumber/inode pair of / is the same as that of
- # /sbin/init's root, so we're *not* in a chroot and hence
- # return false.
- return 1
- fi
- return 0
-}
-
case $1 in
install)
mkdir -p /etc/initramfs-tools/conf.d
-
- # First time install. Can we autodetect the RESUME partition?
- if [ -r /proc/swaps ]; then
- RESUME=$(grep ^/dev/ /proc/swaps | sort -rk3 \
-| head -n 1 | cut -d -f 1)
- if command -v blkid /dev/null 21; then
-UUID=$(blkid -s UUID -o value $RESUME || true)
- # FIXME: post-Wheezy remove vol_id invocations
- elif command -v vol_id /dev/null 21; then
-UUID=$(vol_id -u $RESUME || true)
- elif [ -x /lib/udev/vol_id ]; then
-UUID=$(/lib/udev/vol_id -u $RESUME || true)
- fi
- if [ -n $UUID ]; then
-RESUME=UUID=$UUID
- fi
- fi
-
- # write conf.d/resume if not in a chroot
- if [ -n ${RESUME} ] ! chrooted; then
- echo RESUME=${RESUME} /etc/initramfs-tools/conf.d/resume
- fi
-
;;
esac
diff -ur initramfs-tools-0.113.orig/update-initramfs initramfs-tools-0.113/update-initramfs
--- initramfs-tools-0.113.orig/update-initramfs 2013-07-30 01:46:30.0 +0200
+++ initramfs-tools-0.113/update-initramfs 2013-07-30 01:48:19.0 +0200
@@ -68,7 +68,7 @@
# return false.
return 1
fi
-return 0
+ return 0
}
mild_panic()
@@ -161,6 +161,45 @@
verbose Removing ${initramfs_bak}
}
+# Update the resume device
+update_resume_device()
+{
+ USWSUSPCFG=/etc/uswsusp.conf
+ S2DISK=/usr/sbin/s2disk
+
+ # If uswsusp installed, use that swap device
+ if [ -r ${USWSUSPCFG} ] [ -x ${S2DISK} ]; then
+ RESUME=`sed -n 's/^[[:space:]]*'resume device'[[:space:]]*[=:][[:space:]]*\([^[:space:]]*\)/\1/ p' $USWSUSPCFG`
+
+ if [ ! -e ${RESUME} ]; then
+ RESUME=
+ fi
+ fi
+
+ # If not found in uswsusp config, get from running system
+ if [ -z ${RESUME} ]; then
+ if [ -r /proc/swaps ]; then
+ RESUME=$(grep ^/dev/ /proc/swaps | sort -rk3 \
+| head -n 1 | cut -d -f 1)
+ if command -v blkid /dev/null 21; then
+UUID=$(blkid -s UUID -o value $RESUME || true)
+ # FIXME: post-Wheezy remove vol_id
Bug#718312: linux-image-3.10-1-amd64: Kernel panic crashes drm_kms_helper causing hard lockup
The resumed again and the mei_me crapflood has started: [ 1361.814786] mei_me :00:16.0: reset: wrong host start response [ 1361.814789] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1361.814802] mei_me :00:16.0: reset: unexpected enumeration response hbm. [ 1361.814805] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1361.814821] mei_me :00:16.0: reset: wrong host start response [ 1361.814824] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1361.814837] mei_me :00:16.0: reset: unexpected enumeration response hbm. [ 1361.814839] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1361.814856] mei_me :00:16.0: reset: wrong host start response [ 1361.814859] mei_me :00:16.0: unexpected reset: dev_state = RESETTING And now: [ 1691.872331] mei_me :00:16.0: reset: init clients timeout hbm_state = 1. [ 1691.872339] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1721.902336] mei_me :00:16.0: reset: init clients timeout hbm_state = 1. [ 1721.902345] mei_me :00:16.0: unexpected reset: dev_state = RESETTING [ 1751.932326] mei_me :00:16.0: reset: init clients timeout hbm_state = 1. [ 1751.932335] mei_me :00:16.0: unexpected reset: dev_state = RESETTING And a new one of these every 30 seconds. -- Ben Caradoc-Davies b...@wintersun.org -- 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/51f70d71.70...@wintersun.org
