Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote: > This needs to be fixed before linux 6.3.0-2-* can migrate to testing, > otherwise it will break dkms module building for everyone still having > linux-headers-6.3.0-1-* installed (which is probably for the currently > running kernel). On one

Bug#1051844: initramfs-tools-core: the man pages have U+2010 HYPHEN characters instead of U+002D HYPHEN-MINUS

Package: initramfs-tools-core Version: 0.142 Severity: minor In the initramfs-tools(7) man page: Both /usr/share/initramfs‐tools/scripts and /etc/initramfs‐ tools/scripts contains the following subdirectories. where the dashes are U+2010 HYPHEN. This is incorrect and breaks copy-pa

Bug#970557: Closing this bug (BTS maintenance for src:linux bugs)

Hi, On 2023-09-22 17:10:37 +0200, car...@debian.org wrote: > This bug was filed for a very old kernel or the bug is old itself > without resolution. > > If you can reproduce it with > > - the current version in unstable/testing > - the latest kernel from backports [...] Just a note to say that

Bug#939079: nouveau: screen dimensions and resolution are wrong

Control: found -1 6.1.55-1 On 2019-09-01 04:11:15 +0200, Vincent Lefevre wrote: > With the nouveau driver, I get: > > $ xdpyinfo > [...] > screen #0: > dimensions:3200x1800 pixels (846x476 millimeters) > resolution:96x96 dots per inch > [...] > > whi

Bug#712740: linux-image-3.9-1-amd64: please turn off ptrace protection

Package: src:linux Version: 3.9.6-1 Severity: wishlist As of 3.9, the Debian kernel includes Yama, which switches on ptrace protection by default. This is a bad idea, because: * It isn't a real protection. As said in bug 712663, to be able to use ptrace in a useful way is equivalent to have

Bug#712740: the default is fine

On 2013-06-19 10:44:39 -0700, Kees Cook wrote: > This is what /etc/sysctl.d/ is for: changing defaults. Yes, but IMHO, the default is not fine (see below). > There are, in fact, real protections with this change. Namely, the delay of > attack expansion. Take the case of a server being attacked. I

Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps

Package: initramfs-tools Version: 0.113 Severity: important Tags: security I've noticed that when running update-initramfs, a core dump was generated in the current directory, which is in itself a first bug. After looking at this problem with strace, I saw that this came from: /usr/bin/ldd /li

Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps

On 2013-08-25 00:47:36 +0100, Ben Hutchings wrote: > What? It belongs to glibc; > > $ dpkg -S /libx32 > libc6-x32: /libx32 If libc6-x32 is not installed, this directory doesn't belong to anything! $ dpkg -S /libx32 dpkg-query: no path found matching pattern /libx32 So, there's nothing wrong in

Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps

On 2013-08-25 09:53:07 +0100, Ben Hutchings wrote: > No, this has a defined meaning in FHS: > > http://www.pathname.com/fhs/pub/fhs-2.3.html#LIBLTQUALGTALTERNATEFORMATESSENTIAL OK (both the French and English versions of the Wikipedia article didn't mention these directories... I've updated them

Bug#869511: dependency on linux-headers-*-common

On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote: > The "linux-headers-4.11.0-2-common" fault is uncorrected? Not on my machine. It is still not possible to upgrade. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Wo

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

Package: linux-image-amd64 Version: 4.11+83 Severity: grave Justification: renders package unusable linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is no longer installable (bug 869511). But since this bug 869511 has been fixed in linux/4.12.6-1 only and has been closed, it seems th

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

On 2017-08-13 23:49:21 +0200, Vincent Lefevre wrote: > linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is > no longer installable (bug 869511). But since this bug 869511 has > been fixed in linux/4.12.6-1 only and has been closed, it seems > that linux-image-4.11.0-

Bug#869511: dependency on linux-headers-*-common

On 2017-08-13 23:36:53 +0200, Vincent Lefevre wrote: > On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote: > > The "linux-headers-4.11.0-2-common" fault is uncorrected? > > Not on my machine. It is still not possible to upgrade. I assume that since this bug has been clos

Bug#823017: linux-image-4.5.0-1-amd64: can't read some files of a DVD+R: udf_read_inode: ... failed !bh

Package: src:linux Version: 4.5.1-1 Severity: important Trying to copy some files of a DVD+R yields errors: cp: cannot stat '...': Input/output error In the logs: Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 453) failed !bh Apr 30 01:52:28 zira kernel: UDF-fs:

Bug#823017: linux-image-4.5.0-1-amd64: can't read some files of a DVD+R: udf_read_inode: ... failed !bh

Control: found -1 4.6.4-1 Control: retitle -1 can't read some files of a DVD+R: udf_read_inode: ... failed !bh (regression) Sorry for the late reply. On 2016-04-30 12:53:23 +0200, Ben Hutchings wrote: > On Sat, 2016-04-30 at 02:34 +0200, Vincent Lefevre wrote: > > Reading most o

Bug#789266: nouveau: unable to locate usable image (regression)

Package: src:linux Version: 4.0.5-1 Severity: important When I boot on 4.0.0-2-amd64, I get an error with nouveau: [ 14.178206] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x108390a1 [ 14.178208] nouveau [ DEVICE][:01:00.0] Chipset: GK208 (NV108) [ 14.178210] nouveau [ DEVICE][:0

Bug#791335: linux-image-3.16.0-4-amd64: automatic save of the system clock to RTC doesn't work

Package: src:linux Version: 3.16.7-ckt11-1 Severity: important According to http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html referenced by http://www.freedesktop.org/wiki/Software/systemd/timedated/ the Linux kernel syncs the system clock to the RTC every 11 minutes

Bug#791335: linux-image-3.16.0-4-amd64: automatic save of the system clock to RTC doesn't work

On 2015-07-03 23:35:30 +0100, Ben Hutchings wrote: > Which NTP implementation are you using? openntpd 1:5.7p4-1 -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP,

Bug#791335: linux-image-3.16.0-4-amd64: automatic save of the system clock to RTC doesn't work

Control: tag -1 - moreinfo Control: reassign -1 openntpd 1:5.7p4-1 Control: retitle -1 openntpd: should set the clock status (ADJ_STATUS) to have the RTC updated by the kernel On 2015-07-04 00:25:19 +0100, Ben Hutchings wrote: > On Sat, 2015-07-04 at 01:10 +0200, Vincent Lefevre wrote: >

Bug#789266: nouveau: unable to locate usable image (regression)

Control: tags -1 upstream Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=89047 There seems to be a fix, but available in 4.1 only, which has another blocking problem (kernel hangs): https://bugs.freedesktop.org/show_bug.cgi?id=90626 -- Vincent Lefèvre - Web:

Bug#792778: nouveau: screen sometimes remains blank after "xset dpms force off"

Package: src:linux Version: 3.16.7-ckt11-1 Severity: normal After I blank the screen of my laptop with "xset dpms force off", it is usually unblanked as expected when I type a key or move the mouse, but not always. When this occurs, the screen is no longer off, in the sense I can see some light on

Bug#793793: linux-image-3.16.0-4-amd64: nouveau can make suspend fail: suspend failed with -16 [NV108 Quadro K610M]

Package: src:linux Version: 3.16.7-ckt11-1+deb8u2 Severity: important The last suspend of my ZBook 15 G2 failed. I didn't notice, and the laptop was switched off when I wanted to wake it up. The syslog file contains, starting from the initial Sleep event: Jul 27 10:12:12 zira systemd[1]: Reached

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Package: src:linux Version: 4.8.11-1 Severity: important After suspending my laptop (13:54:33 below), when I pressed the power button to resume (19:35:53 below), the laptop was automatically powered off. This is a regression (tried twice, occurred twice, but there was no such problem in the past,

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Control: severity -1 grave because it can corrupt files. When this occurred on December 23, the log file of monit got corrupted: [CET Dec 22 07:35:07] info : 'zira' Monit reloaded [CET Dec 22 07:35:07] error: Queued event file: unable to read event size -- end of file [CET Dec 23 10:51:

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 15:09:49 +, Ben Hutchings wrote: > Unless you can show that some data had been written *and flushed* to > disk by the application, but was not readable afterward - this does not > count. Writes are buffered, and user space has to deal with that. If I understand the journalctl lo

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

-01-11 16:20:35 +0100, Vincent Lefevre wrote: > On 2017-01-11 15:09:49 +, Ben Hutchings wrote: > > Unless you can show that some data had been written *and flushed* to > > disk by the application, but was not readable afterward - this does not > > count. Writes are buffere

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: > Am 11.01.2017 um 18:05 schrieb Michael Biebl: > > Why is this no normal shutdown? Services are not stopped as usual. > > Did you actually have a file corruption? Yes, /var/log/monit.log, which got null bytes in it, and some other file created

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 18:36:30 +0100, Michael Biebl wrote: > Am 11.01.2017 um 18:28 schrieb Michael Biebl: > > Am 11.01.2017 um 18:25 schrieb Vincent Lefevre: > >> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: > >>> Am 11.01.2017 um 18:05 schrieb Michael Biebl: > &g

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

On 2017-01-11 17:40:09 +, Ben Hutchings wrote: > On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote: > > On 2017-01-11 15:09:49 +, Ben Hutchings wrote: > > > Unless you can show that some data had been written *and flushed* to > > > disk by the applic

Bug#847198: src:linux: dmesg should be allowed to print the kernel ring buffer for admins

Package: src:linux Severity: wishlist In the past, admins could get dmesg output without running it as root, but this is no longer possible: * security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root users reading the kernel log by default (sysctl: kernel.dmesg_restrict) (in ch

Bug#809149: linux-image-4.3.0-1-amd64: Microcode SW error detected / Hardware became unavailable during restart

Package: src:linux Version: 4.3.3-2 Severity: normal I sometimes have wifi disconnections, and automatic reconnections, but this time, wicd constantly said "No wireless networks found.". Restarting the wicd daemon and the GUI did not solve this problem. There are 8 visible wifi access points, so t

Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps

Control: tags -1 - moreinfo On 2016-01-22 02:36:44 +, Ben Hutchings wrote: > Do you think there is still a bug to fix here, or can this be closed? Well, the core dump problem has been fixed in the kernel. Now, I think that if there is an issue, it is in ldd. It is still not clear whether /lib

Bug#757356: evtest: doesn't output scan codes for some keys

Control: retitle -1 Scan code event not generated for some keys of the Appple keyboard Control: found -1 4.3.3-7 Things have improved since now the normal keys have their scan code. This is not the case of the Fn key, but this may be normal since this is a special key that modifies other keys. Bu

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

Package: src:linux Version: 4.18.20-2 Severity: normal I get the following errors at boot time: Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique processor _UID (0xff) Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get unique processor _UID (0xff) Nov 29 09:04:20 c

Bug#898814: When I log in, it hangs until crng init done

On 2018-12-14 10:24:51 +0100, Yves-Alexis Perez wrote: > Something puzzles me with all those issues: as far as I can tell, on most > install, systemd-random-seed.service should save a seed at shutdown and > restore it at startup, and this (I think) should be enough to properly init > the RNG. > >

Bug#898814: When I log in, it hangs until crng init done

On 2018-12-14 11:23:39 +0100, Vincent Lefevre wrote: > Interesting. On a machine where I have no such issues, I can see > in journalctl info at shutdown: > > Dec 13 15:44:14 zira systemd[1]: Stopping Load/Save Random Seed... > [...] > Dec 13 15:44:14 zira systemd[1]: Stopped Loa

Bug#918096: linux-image-4.19.0-1-amd64: disk and keyboard do not work - unusable even in recovery mode

Note: I have the same issue with the 4.9 kernel from stable, which I have just installed, so that initrd.img-4.9.0-8-amd64 is recent (this might matter). See also bug 917607 (I get the same error), reported against udev. -- Vincent Lefèvre - Web: 100% accessible valida

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

On 2019-01-11 11:17:03 -0500, Benjamin Redelings wrote: > Package: src:linux > Version: 4.18.20-2 > Followup-For: Bug #914967 > > Dear Maintainer, > > Starting with package 4.18.0-3, my computer fails to finish booting. I see > the message > > acpi LNXCPU:bf: Failed to get unique processor

Bug#887061: linux-image-4.9.0-5-amd64: KPTI (kaiser.c): please, no silent disable for Xen guests

Package: src:linux Version: 4.9.65-3+deb9u2 Severity: wishlist Hi, My VM is a Xen guest, and I was confused not to find any information about KPTI in the kernel logs. This is due to the silent_disable case here: In arch/x86/mm/kaiser.c: void __init kaiser_check_boottime_disable(void) { [...]

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

Package: src:linux Version: 3.16.7-ckt11-1+deb8u4 Severity: important At my lab, with NFS accounts, some machines have been reinstalled with Debian 8. and on these machines, NFS rename sometimes hangs for 15 seconds (the NFS server isn't particularly loaded), while this problem never occurs under

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

I can simply reproduce the problem by reading the target on some machine, then moving a file to the target on another (Debian 8) machine. For instance: cassis% echo foo > file1 cassis% cp file1 file2 fraise% cat file2 foo then back on cassis (a Debian 8 machine): cassis% time mv file1 file2 mv

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

On 2015-09-23 13:42:25 +0200, Vincent Lefevre wrote: > I can simply reproduce the problem by reading the target on some > machine, then moving a file to the target on another (Debian 8) > machine. For instance: > > cassis% echo foo > file1 > cassis% cp file1 file2 > &

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

Mount information: filer.lip.ens-lyon.fr:/export/home/vlefevre on /home/vlefevre type nfs4 (rw,nosuid,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=140.77.14.11,local_lock=none,addr=140.77.14.5) -- Vincent Lefèvre - Web: <

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

According to Peter Ludikovsky in the debian-user list: Am 25.09.2015 um 14:04 schrieb Vincent Lefevre: > On 2015-09-25 10:11:10 +0200, Peter Ludikovsky wrote: >> My guess is: Due to the rather large wsize/rsize, th

Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

Here are the traces done at my lab. I recall the test between hosts A and B (see the prompt): A% echo foo > file1 A% cp file1 file2 B% cat file2 A% time mv file1 file2 Test 1: A = Debian 8 - debian-8_20.pcap (15s delay between the 2 RENAME) B = Debian 7 - debian-7_20.pcap Test 2: A = Debia

Bug#789266: nouveau: unable to locate usable image (regression)

Control: retitle -1 HP ZBook 15 nouveau driver doesn't work for Linux kernel >= 4.0 Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=90626 On 2015-07-16 02:43:17 +0200, Vincent Lefevre wrote: > There seems to be a fix, but available in 4.1 only, which has another

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

Package: src:linux Version: 4.2.6-1 Severity: important This is the second time I get a sudden USB disconnection, in two days. See the logs below for the latest one. This corresponds to my USB keyboard. Mapping is lost, and though I can remap the keyboard manually, this still breaks all the xterm'

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

On 2015-11-15 14:01:06 +0100, Vincent Lefevre wrote: > This is the second time I get a sudden USB disconnection, in two > days. See the logs below for the latest one. This corresponds to my > USB keyboard. Mapping is lost, and though I can remap the keyboard > manually, this still br

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

Control: severity -1 grave On 2015-11-15 16:24:38 +0100, Vincent Lefevre wrote: > On 2015-11-15 14:01:06 +0100, Vincent Lefevre wrote: > > This is the second time I get a sudden USB disconnection, in two > > days. See the logs below for the latest one. This corresponds to my &

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

On 2015-11-16 12:12:06 +0100, Vincent Lefevre wrote: > On 2015-11-15 16:24:38 +0100, Vincent Lefevre wrote: > > On 2015-11-15 14:01:06 +0100, Vincent Lefevre wrote: > > > This is the second time I get a sudden USB disconnection, in two > > > days. See the logs bel

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

Control: found -1 4.2.5-1 On 2015-11-17 01:01:30 +0100, Vincent Lefevre wrote: > This has just occurred again on the first machine (still with 4.2.6-1). The bug also occurred after downgrading to 4.2.5-1 and rebooting. > I forgot to say that this also breaks mouse clicks over te root

Bug#805168: linux-image-4.2.0-1-amd64: sudden USB disconnect

On 2015-11-16 12:12:06 +0100, Vincent Lefevre wrote: > This has now happened on a different machine (see below). After looking at this problem more closely, this is a hardware bug with this machine (actually the screen and its USB hub). The fact that this bug got triggered just a few days ago

Bug#323452: "hda: dma_timer_expiry: dma status == 0x21" errors + freeze (VIA VT82C686 chipset)

Package: kernel-image-2.4.27-2-386 Version: 2.4.27-10 Severity: important On this machine, I get the following error several times by hour: hda: dma_timer_expiry: dma status == 0x21 hda: error waiting for DMA hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } and the who

Bug#323452: "hda: dma_timer_expiry: dma status == 0x21" errors + freeze (VIA VT82C686 chipset)

On 2005-08-17 00:34:15 +0200, maximilian attems wrote: > On Tue, 16 Aug 2005, Vincent Lefevre wrote: > > > On this machine, I get the following error several times by hour: > > > > hda: dma_timer_expiry: dma status == 0x21 > > hda: error waiting for DMA > >

Bug#323452: "hda: dma_timer_expiry: dma status == 0x21" errors + freeze (VIA VT82C686 chipset)

On 2005-08-17 13:25:07 +0900, Horms wrote: > I agree with Maximilian's advice that it is highly likely that > errors like this typically indicate that a disk is failing and > that you should back up your data and replace the disk. Then is there any reason why SMART doesn't detect any problem exce

Bug#323452: "hda: dma_timer_expiry: dma status == 0x21" errors + freeze (VIA VT82C686 chipset)

On 2005-08-17 12:11:24 -0400, Andres Salomon wrote: > What exactly are the SMART errors? If you force a smart short or long test, > do you get errors? No errors for short and long tests. I've attached the output of "smartctl -a". -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web:

Bug#356090: kernel: Can't access PCMCIA card adapter

Same problem on my PowerBook G4, with both a 2-GB SD card and a 1-GB SD card. The 1-GB card reads fine on my Zaurus (2.4.18 Linux kernel). For instance, with the 2-GB card: Sep 19 20:37:01 ay kernel: [70398.753418] pccard: PCMCIA card inserted into slot 0 Sep 19 20:37:01 ay kernel: [70398.757405]

Bug#356090: kernel: Can't access PCMCIA card adapter

BTW, I had no problem with the same PCMCIA adapter + 1-GB SD card with Linux kernel 2.6.6 in July 2004. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire pr

Bug#356090: kernel: Can't access PCMCIA card adapter

On 2008-09-21 16:11:45 +0200, Bastian Blank wrote: > On Fri, Sep 19, 2008 at 10:07:36PM +0200, Vincent Lefevre wrote: > > Same problem on my PowerBook G4, with both a 2-GB SD card and a 1-GB SD > > card. The 1-GB card reads fine on my Zaurus (2.4.18 Linux kernel). For > > in

Bug#356090: kernel: Can't access PCMCIA card adapter

There's something wrong with one of the drivers: On 2008-09-21 19:31:45 +0200, Vincent Lefevre wrote: > I've tried with another 1-GB card, a microSD this time (with a microSD > to SD adapter between the PCMCIA adapter and the memory card), and I get > the following errors: [...

Bug#413742: unreproducible

On 2007-06-15 20:56:32 +0200, Bastian Blank wrote: > I can't reproduce this with both client and server with 2.6.18-4. > Please provide more informations about the setup. I don't know about the server. On the client side, "nfsstat -m" was giving: /home/vlefevre from lip-filer:/export/home/vlefevr

Bug#413742: unreproducible

On 2007-06-16 09:16:44 +0200, Bastian Blank wrote: > So you can't even say if this is a bug on the client or server side? Well, the current server is a Linux-machine (Debian/woody), but I've had similar errors with "rm -r" (rm: cannot remove `...': No such file or directory) a few years ago with a

Bug#431055: linux-image-2.6.18-4-686-bigmem: hotplug doesn't detect when DHCP server becomes available

Package: linux-image-2.6.18-4-686-bigmem Version: 2.6.18.dfsg.1-12etch2 Severity: important I've put the following lines in my /etc/network/interfaces file: allow-hotplug eth0 iface eth0 inet dhcp as recommended by http://groups.google.fr/group/linux.debian.user/msg/0d277efaae1aa7e4 I've tri

Bug#431055: closed by maximilian attems <[EMAIL PROTECTED]> (Re: Bug#431055: linux-image-2.6.18-4-686-bigmem: hotplug doesn't detect when DHCP server becomes available)

reopen 431055 thanks On 2007-06-29 10:24:05 +, Debian Bug Tracking System wrote: > no evidence of any kernel error, > for userspace handling please ask on debian-user > instead of submitting "support bug reports". This is *exactly* what I've done. Perhaps you should read bug reports entirely.

Bug#432155: cramfsprogs: mkcramfs sometimes crashes (bus error in zlib)

Package: cramfsprogs Version: 1.1-6 Severity: normal mkcramfs sometimes crashes due to a bus error, but if I run the same command again, it doesn't crash. ay:~> gdb mkcramfs core GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General

Bug#413742: unreproducible

On 2007-06-16 13:52:34 +0200, Vincent Lefevre wrote: > On 2007-06-16 09:16:44 +0200, Bastian Blank wrote: > > So please show why you think it is a bug on the client, for example > > with a dump of the rpc communication. > > I can't reproduce the problem currently. I c

Re: CONFIG_LEGACY_PTYS is not set on PowerPC

On 2007-08-27 11:54:44 +0200, Marco d'Itri wrote: > [EMAIL PROTECTED] wrote: > >> Any one knows why official PowerPC kernels are configured with > >> CONFIG_LEGACY_PTYS unset? This makes programs using some pty's > >> fail to work. See bug 430632 for instance. > >It might help if you asked the kern

Re: CONFIG_LEGACY_PTYS is not set on PowerPC

On 2007-08-27 13:14:09 +0200, maximilian attems wrote: > software that relies on the oldstyle BSD ptys is dead. > > we didn't want to disable it late in the etch game, > but for lenny the decision is made. It seems that oldstyle BSD ptys have always been disabled in the PowerPC kernels (contrary

Bug#381902: linux-image-2.6.17-1-powerpc: USB connection to Zaurus using usbnet often freezes on PowerPC

On 2007-01-17 16:26:16 +0100, maximilian attems wrote: > how is linux image 2.6.18 doing? No such problem with the 2.6.18-3-powerpc kernel from the Debian package linux-image-2.6.18-3-powerpc. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTM

Bug#407386: linux-image-2.6.18-3-powerpc: No audio out on PowerBook3,2 (regression vs 2.6.17)

Package: linux-image-2.6.18-3-powerpc Version: 2.6.18-8 Severity: important I upgraded the kernel from 2.6.17-1 to 2.6.18-3 and I no longer get sound on my PowerBook G4 (PowerBook3,2). I tried with both ogg123 and VLC, both with the speakers and the headphones. Setting the volume to the maximum di

Bug#407386: linux-image-2.6.18-3-powerpc: No audio out on PowerBook3,2 (regression vs 2.6.17)

On 2007-01-18 10:59:38 +0100, maximilian attems wrote: > On Thu, Jan 18, 2007 at 03:25:03AM +0100, Vincent Lefevre wrote: > > > > I upgraded the kernel from 2.6.17-1 to 2.6.18-3 and I no longer get > > sound on my PowerBook G4 (PowerBook3,2). I tried with both ogg123 >

Bug#407386: linux-image-2.6.18-3-powerpc: No audio out on PowerBook3,2 (regression vs 2.6.17)

On 2007-01-22 11:46:08 +0100, maximilian attems wrote: > On Thu, 18 Jan 2007, Vincent Lefevre wrote: > > A new snd-aoa driver was mentioned in bug 381658, but I couldn't find > > a NEWS file in /usr/share/doc/linux-image-2.6.18-3-powerpc, so I don't > > know what&#x

Bug#407386: linux-image-2.6.18-3-powerpc: No audio out on PowerBook3,2 (regression vs 2.6.17)

On 2007-01-26 20:31:45 +0100, Elimar Riesebieter wrote: > On Fri, 26 Jan 2007 the mental interface of > Vincent Lefevre told: > > [...] > > In fact, installing alsa-base solved the problem. But I've noticed > > that the snd_aoa module isn't loaded. Should

Re: Bug#408746: ALSA no longer works after installing udev

On 2007-01-28 13:03:52 +0100, Marco d'Itri wrote: > On Jan 28, Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > > I can see that the snd* modules are no longer loaded. > I can see that you did not read README.Debian. I did, but if you meant that I should add the dr

Bug#413742: linux-2.6: [NFS] Unlinked files still seen in directory stream after a rewinddir

Package: linux-2.6 Severity: important [important since this affects a very common utility: "rm"] The coreutils snapshot (upstream) does the following in a "rm -r": * Files are unlinked in a first pass: lstat("/proc/self/fd/4/config.h.in", {st_mode=S_IFREG|0644, st_size=27828, ...}) = 0 access

Bug#381902: linux-image-2.6.17-1-powerpc: USB connection to Zaurus using usbnet often freezes on PowerPC

Package: linux-image-2.6.17-1-powerpc Version: 2.6.17-5 Severity: important I sometimes connect to my Zaurus SL-C860 with a USB connection (using usbnet) from my PowerBook and the connection often freezes. For instance, if I type "ssh -t -l zaurus 192.168.129.201 /usr/local/bin/zsh -l", then "ls /

Bug#381902: linux-image-2.6.17-1-powerpc: USB connection to Zaurus using usbnet often freezes on PowerPC

On 2006-08-07 19:21:52 +0200, Vincent Lefevre wrote: > Package: linux-image-2.6.17-1-powerpc > Version: 2.6.17-5 > Severity: important > > I sometimes connect to my Zaurus SL-C860 with a USB connection (using > usbnet) from my PowerBook and the connection often freezes. For ins

Bug#386226: same problem with linux-image-2.6.18-1-686-bigmem

I have the same problem with linux-image-2.6.18-1-686-bigmem. The bug should probably be reassigned to the linux-2.6 source. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer ari

Bug#386226: linux-image-2.6.16-2-686-smp: Will not set clock and loses interrupts when rtc is used

On 2006-10-20 20:54:45 +0200, Norbert Warmuth wrote: > Workarounds (both tested successfully): > 1. boot with hpet=disable > 2. build the kernel with CONFIG_RTC=y But is it normal that even when the rtc module is loaded (according to lsmod), I get the following error? # hwclock --systohc select

Bug#457308: CD: missing files and corrupt filenames

On 2007-12-21 15:05:28 +0100, Vincent Lefevre wrote: > If I mount the CD-ROM with "-o norock", then its contents are correct > (correct filenames, no missing files). So, it seems that there are > problems with the Rock Ridge extensions. Now that I know this comes from the Ro

Bug#457308: CD: missing files and corrupt filenames

Package: linux-2.6 Severity: important After mounting a CD-ROM, I have the following problems when reading it, concerning its contents: * One of the files (that is present on the CD) is missing; there's no way for the user to have access to it. However, its name isn't special: "svnpriv-m

Bug#457308: CD: missing files and corrupt filenames

On 2007-12-21 13:22:14 +0100, Vincent Lefevre wrote: > * One of the files (that is present on the CD) is missing; there's > no way for the user to have access to it. However, its name isn't > special: "svnpriv-md5". In fact, I've noticed that other tw

Bug#457308: CD: missing files and corrupt filenames

On 2007-12-21 14:50:21 +0100, Vincent Lefevre wrote: > I don't know how isoinfo obtains the information, but it shows that > the files are on the CD, with the correct names (FYI, the CD can be > read without any problem under Mac OS X, and this is consistent to > what isoinfo giv

Bug#457308: CD: missing files and corrupt filenames

On 2007-12-21 13:50:12 +0100, maximilian attems wrote: > On Fri, Dec 21, 2007 at 01:22:14PM +0100, Vincent Lefevre wrote: > > > > After mounting a CD-ROM, I have the following problems when reading it, > > concerning its contents: > > * One of the files (that is pr

Bug#457308: CD: missing files and corrupt filenames

reassign 457308 mount retitle 457308 iso9660: missing files and corrupt filenames with Rock Ridge extensions thanks On 2007-12-21 18:14:47 +0100, maximilian attems wrote: > as suspected not a kernel trouble. > it is not the kernel that sets the mount option. > > unless a kernel oops or something

Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

Package: linux-image-2.6.18-5-powerpc Version: 2.6.18.dfsg.1-13etch6 Severity: important At about 00:25, the system completely froze: the mouse and the keyboard were no longer working (even Ctrl-Alt-Del), and the network connection was no longer working either. Not much in the log files before the

Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

On 2007-12-24 01:01:53 +0100, Vincent Lefevre wrote: > I think I didn't have any such problem before (except when using the > smartmontools long self-test), in the last few years. I had another freeze with linux-image-2.6.18-5-powerpc. Then I rebooted with linux-image-2.6.18-3-powerpc,

Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

On 2007-12-24 14:53:58 +0100, Bastian Blank wrote: > And on the console? After the freeze, I can't see what is printed on the text console (because the system is completely frozen, and I can't do anything). However, I have an xterm started with the -C option, but there was nothing on it. > Are yo

Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

Some news about the crashes: ay:~> last -axf /var/log/wtmp.1 | grep crash lefevre tty1 Mon Dec 31 15:40 - crash (11:00) lefevre tty1 Sat Dec 29 22:41 - crash (1+16:57) lefevre tty1 Sat Dec 29 17:43 - crash (04:57) lefevre tty1 Sat Dec 29 04:18 - crash (13:23)

Bug#467009: linux-image-2.6.24-1-amd64: mounting /cdrom froze the system and corrupted the X server

On 2008-02-22 13:47:34 +0100, Vincent Lefevre wrote: > After a "mount /cdrom" (corresponding device is /dev/hda), the system > completely froze. I couldn't reboot with the keyboard. I had to press > the power button. After the reboot, the X server was no longer working

Bug#467009: linux-image-2.6.24-1-amd64: mounting /cdrom froze the system and corrupted the X server

severity 467009 important thanks since the CD-ROM is completely unusable with this kernel and boot time is very slow due to all these timeouts on /dev/hda. On 2008-02-22 14:35:23 +0100, Vincent Lefevre wrote: > On 2008-02-22 13:47:34 +0100, Vincent Lefevre wrote: > > After a &quo

Bug#298643: kernel-image-2.6.10-powerpc: Network (eth0) doesn't work

Package: kernel-image-2.6.10-powerpc Version: 2.6.10-3 Severity: important The network (via eth0) doesn't work at all with the 2.6.10 kernel on my PowerBook G4. For instance, I get "Destination Host Unreachable" errors when doing a ping. Note: I have the following errors concerning the package:

Bug#253802: tkmixer on 2.6.9-powerpc

On 2005-03-11 21:29:03 +, Nikita Schmidt wrote: > Note that I was surprised to learn that bss is not zeroed out when a > module is loaded, thus breaking the convention that all non-initialised > statics automatically initialise to 0. But it appears to be so. This is more than a convention. Th

Bug#304944: kernel-image-2.6.11-powerpc: eth0 and eth1 are swapped

Package: kernel-image-2.6.11-powerpc Version: 2.6.11-1 Severity: important I was wondering why the network didn't work... With older kernels (e.g. 2.6.8), dmesg gives: [...] ieee1394: Initialized config rom entry `ip1394' ohci1394: $Rev: 1223 $ Ben Collins <[EMAIL PROTECTED]> ohci1394: fw-host0:

Bug#305234: kernel-image-2.6.11-powerpc: USB device not always taken into account when plugged in

Package: kernel-image-2.6.11-powerpc Version: 2.6.11-1 Severity: normal When I plugged in my Zaurus to the USB port, the usb0 network interface didn't appear. This happened with both kernels 2.6.9 (kernel-image-2.6.9-powerpc package) and 2.6.11 (kernel I've compiled from kernel-source-2.6.11). dme

Bug#304944: kernel-image-2.6.11-powerpc: eth0 and eth1 are swapped

On 2005-04-21 23:47:13 +0200, maximilian attems wrote: > please send in the output of lspci -vv on your box? :00:0b.0 Host bridge: Apple Computer Inc. UniNorth AGP Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+

Bug#304944: acknowledged by developer (Re: Bug#304944: kernel-image-2.6.11-powerpc: eth0 and eth1 are swapped)

On 2005-05-06 19:18:03 -0700, Debian Bug Tracking System wrote: > the kernel never guarantees ethX ordering. > there for closing. OK, I've just seen the "KNOWN BUGS/LIMITATIONS" note in the interfaces(5) man page (that probably wasn't there when I configured the interfaces files several years ago.

Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

2.6.18-6-powerpc I've just installed 2.6.24-1-powerpc. Let's see if it has the same problem... On 2008-01-16 17:27:55 +0100, Vincent Lefevre wrote: > Since January 1, I haven't got any crash. In fact, the crashes occurred > only when I was on holidays. The two differences from norm

Bug#467227: [powerpc] oops when resume

On 2008-05-28 01:14:02 +0200, maximilian attems wrote: > how is 2.6.25 from unstable doing? No problem with 2.6.25 (linux-image-2.6.25-2-powerpc 2.6.25-3). -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog:

Bug#467227: [powerpc] oops when resume

On 2008-05-28 11:24:14 +0200, maximilian attems wrote: > Version: 2.6.25-3 > > On Wed, May 28, 2008 at 04:29:53AM +0200, Vincent Lefevre wrote: > > On 2008-05-28 01:14:02 +0200, maximilian attems wrote: > > > how is 2.6.25 from unstable doing? > > > > No probl

  1   2   3   4   >