Bug#1057399: firmware-amd-graphics: Unintended consequence of /usr merge - video output ceases
Package: firmware-amd-graphics Version: 20230625-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A long time ago on a motherboard far away lived an AMD graphics card code-named Cedar. Cedar was missing its firmware so its owner copied the firmware to /lib/firmware/radeon and all was well. The graphics card was later moved to another pc (after Cedar firmware was packaged), replaced by an R7 250 graphics card and all was well. Later on the motherboard went to the great scrap metal recovery yard, replaced by a motherboard with an AMD APU, and its graphics unit was code-named Aruba and all was well. Then, an early present arrived in the form of /usr merge for AMD graphics firmware. A small message said: "unable to remove /lib/firmware/radeon - directory not empty" and all was well until update-initramfs was run and a reboot. For update-initramfs had found the old /lib/firmware/radeon and its Cedar firmware, but stopped searching for /usr/lib/firmware/radeon, which contained Aruba firmware. Module radeon was loaded but Aruba firmware was not found, and no further video output appeared. (The boot process continued but not all stages were successful, preventing a remote shell into the machine). * What exactly did you do (or not do) that was effective (or ineffective)? Finally solved by running a rescue DVD, checking the package update log, and blacklisting the radeon module, then deleting /lib/firmware/radeon and running update-initramfs -u - k all * What was the outcome of this action? Possible solutions: if dh_movetousr would result in both /lib/firmware/radeon and /usr/lib/firmware/radeon, report this as an error rather than an informational message, probably better here than in update-initramfs-tools. Circumstances that lead to problems: 1. Manually adding a missing firmware file, 2. Changing graphics card, 3. /usr merge leaving manually added firmware behind, with just an informational message rather than an error 4. update-initramfs searching for old or new firmware locations but only loading the first location (old) if both exist 5. radeon module ceasing video output (and possible further problems) if no firmware found 6. Forgetting how to blacklist a module from grub. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.7.0-rc3+ (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.142 -- no debconf information
Bug#861151: W: initramfs-tools configuration sets RESUME=UUID=... warning even though RESUME=none
Ben Hutchings wrote on 26/04/17 12:41: Control: tag -1 moreinfo On Tue, 25 Apr 2017 17:18:28 +0200 Sven Joachim <svenj...@gmx.de> wrote: On 2017-04-25 12:52 +0930, Arthur Marsh wrote: Package: initramfs-tools Version: 0.129 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? set RESUME=none in /etc/initramfs-tools/initramfs.conf but still get messages: W: initramfs-tools configuration sets RESUME=UUID=604db355-002c-4f41-b31c-438fe788b26d That may be coming from a stale file /etc/initramfs-tools/conf.d/resume, which is the location where the RESUME variable had to be set in versions prior to 0.129. AFAICS mkinitramfs sources /etc/initramfs-tools/initramfs.conf before any files in /etc/initramfs-tools/conf.d which does not look quite right, but maybe there are reasons for that. [...] Yes, that's what it does - and this is documented at the top of initramfs.conf(5). Arthur, please confirm whether RESUME is set somewhere else. Ben. Thanks for your help, /etc/initramfs-tools/conf.d/resume did exist. After removing it, there was no longer any warning message on running update-initramfs and the machine rebooted without attempting a resume. Please close the bug report. Arthur.
Bug#861151: W: initramfs-tools configuration sets RESUME=UUID=... warning even though RESUME=none
Sven Joachim wrote on 26/04/17 00:48: On 2017-04-25 12:52 +0930, Arthur Marsh wrote: Package: initramfs-tools Version: 0.129 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? set RESUME=none in /etc/initramfs-tools/initramfs.conf but still get messages: W: initramfs-tools configuration sets RESUME=UUID=604db355-002c-4f41-b31c-438fe788b26d That may be coming from a stale file /etc/initramfs-tools/conf.d/resume, which is the location where the RESUME variable had to be set in versions prior to 0.129. AFAICS mkinitramfs sources /etc/initramfs-tools/initramfs.conf before any files in /etc/initramfs-tools/conf.d which does not look quite right, but maybe there are reasons for that. W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/sda4 I: (UUID=0e388c35-a730-4a86-ac45-e11486b3e992) I: Set the RESUME variable to override this. As far as I can tell, on boot up there is no attempt to resume from that UUID. Did you hibernate first? Cheers, Sven There was an old /etc/initramfs-tools/conf.d/resume file. I had never used hibernation. Removing the /etc/initramfs-tools/conf.d/resume file fixed things. Thanks for your help! Arthur.
Bug#861151: W: initramfs-tools configuration sets RESUME=UUID=... warning even though RESUME=none
Package: initramfs-tools Version: 0.129 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? set RESUME=none in /etc/initramfs-tools/initramfs.conf but still get messages: W: initramfs-tools configuration sets RESUME=UUID=604db355-002c-4f41-b31c-438fe788b26d W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/sda4 I: (UUID=0e388c35-a730-4a86-ac45-e11486b3e992) I: Set the RESUME variable to override this. As far as I can tell, on boot up there is no attempt to resume from that UUID. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 16M Mar 28 2015 /boot/initrd.img-4.0.0-rc5+119 -rw-r--r-- 1 root root 19M Feb 20 21:01 /boot/initrd.img-4.10.0 -rw-r--r-- 1 root root 20M Feb 5 13:20 /boot/initrd.img-4.10.0-rc6-amd64 -rw-r--r-- 1 root root 20M Feb 24 05:21 /boot/initrd.img-4.10.0-trunk-amd64 -rw-r--r-- 1 root root 19M Mar 7 19:33 /boot/initrd.img-4.11.0-rc1 -rw-r--r-- 1 root root 19M Mar 13 12:40 /boot/initrd.img-4.11.0-rc2 -rw-r--r-- 1 root root 19M Apr 3 15:49 /boot/initrd.img-4.11.0-rc5 -rw-r--r-- 1 root root 19M Apr 10 10:36 /boot/initrd.img-4.11.0-rc6 -rw-r--r-- 1 root root 19M Apr 16 16:32 /boot/initrd.img-4.11.0-rc6+ -rw-r--r-- 1 root root 19M Apr 18 19:26 /boot/initrd.img-4.11.0-rc7 -rw-r--r-- 1 root root 19M Apr 24 15:36 /boot/initrd.img-4.11.0-rc7+ -rw-r--r-- 1 root root 19M Apr 24 17:38 /boot/initrd.img-4.11.0-rc8 -rw-r--r-- 1 root root 19M Apr 25 12:46 /boot/initrd.img-4.11.0-rc8+ -rw-r--r-- 1 root root 18M Dec 15 05:05 /boot/initrd.img-4.9.0 -rw-r--r-- 1 root root 19M Mar 30 23:55 /boot/initrd.img-4.9.0-2-amd64 -rw-r--r-- 1 root root 25M Apr 1 11:37 /boot/initrd.img-4.9.0-2-grsec-amd64 -rw-r--r-- 1 root root 19M Mar 30 23:56 /boot/initrd.img-4.9.0-2-rt-amd64 -rw-r--r-- 1 root root 15M Mar 29 2015 /boot/initrd.img-rc5+116 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.11.0-rc8 root=UUID=39706f53-7c27-4310-b22a-36c7b042d1a1 ro radeon.audio=1 page_owner=on -- resume # RESUME=/dev/sda5 RESUME='UUID=604db355-002c-4f41-b31c-438fe788b26d' -- /proc/filesystems btrfs ext3 ext2 ext4 fuseblk xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs -- lsmod Module Size Used by ufs73728 0 qnx4 16384 0 hfsplus 106496 0 hfs57344 0 minix 36864 0 ntfs 102400 0 vfat 20480 0 msdos 20480 0 fat65536 2 msdos,vfat jfs 176128 0 xfs 1212416 0 libcrc32c 16384 1 xfs dm_mod114688 0 cpuid 16384 0 arc4 16384 0 ecb16384 0 md416384 0 hmac 16384 1 nls_utf8 16384 4 cifs 692224 5 ccm20480 0 dns_resolver 16384 1 cifs fscache65536 1 cifs bnep 20480 2 bluetooth 561152 7 bnep nfc 118784 0 rfkill 28672 7 bluetooth,nfc cpufreq_userspace 16384 0 cpufreq_conservative16384 0 snd_hrtimer16384 1 cpufreq_powersave 16384 0 binfmt_misc20480 1 fuse 102400 2 snd_emu10k1_synth 20480 0 snd_emux_synth 40960 1 snd_emu10k1_synth snd_seq_midi_emul 16384 1 snd_emux_synth snd_seq_virmidi16384 1 snd_emux_synth snd_seq_midi 16384 0 snd_seq_midi_event 16384 2 snd_seq_virmidi,snd_seq_midi snd_seq65536 6 snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul,snd_seq_midi,snd_emux_synth max665016384 0 ib_iser49152 0 rdma_cm61440 1 ib_iser iw_cm 40960 1 rdma_cm ib_cm 45056 1 rdma_cm ib_core 200704 4 ib_iser,ib_cm,rdma_cm,iw_cm configfs 40960 2 rdma_cm iscsi_tcp 20480 0 libiscsi_tcp 20480 1 iscsi_tcp libiscsi 57344 3 ib_iser,libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 4 ib_iser,libiscsi,iscsi_tcp parport_pc 28672 0 ppdev 20480 0 lp 20480 0 parport49152 3 lp,parport_pc,ppdev ir_lirc_codec 16384 0 lirc_dev 20480 1 ir_lirc_codec rtl2832_sdr36864 0 videobuf2_vmalloc 16384 1 rtl2832_sdr videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 24576 1 rtl2832_sdr
Bug#818646: linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set
Julien Cristau wrote on 19/03/16 20:09: On Sat, Mar 19, 2016 at 15:46:46 +1030, Arthur Marsh wrote: I usually run custom kernels based off the configuration of recent Debian kernels. I notice that as of 4.4.0-1-amd64 (and hence also linux-image-4.5.0-rc7-amd64) that CONFIG_ZONE_DMA is not set and that disables the EMU10K ALSA sound driver which is needed for a card that I was considering adding to this machine. I do not know if this was an upstream or Debian change, intentional or not, but it is an unpleasant surprise to discover hardware support removed especially as at least one ALSA developer runs this hardware himself. See bugs #814855 and #815787. Cheers, Julien Thanks, but the rationale was really deeply buried in the bug reports rather than in the Debian changelog, which would have been more helpful if it stated what the change was to support and what modules would no longer be in the Debian kernel package as a result. My Athlon64 machine's onboard sound had one of its inputs fail and I wanted to use the Soundblaster Audigy card from this machine. Although I like building custom kernels, it is also really helpful to be able to run a stock kernel to compare things if a custom kernel has a problem. Regards, Arthur.
Bug#818646: linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set
Package: src:linux Version: 4.4.6-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I usually run custom kernels based off the configuration of recent Debian kernels. I notice that as of 4.4.0-1-amd64 (and hence also linux-image-4.5.0-rc7-amd64) that CONFIG_ZONE_DMA is not set and that disables the EMU10K ALSA sound driver which is needed for a card that I was considering adding to this machine. I do not know if this was an upstream or Debian change, intentional or not, but it is an unpleasant surprise to discover hardware support removed especially as at least one ALSA developer runs this hardware himself. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1701 board_vendor: ASUSTeK Computer INC. board_name: M3A78 PRO board_version: Rev 1.xx ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RS780 Host Bridge [1002:7910] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) [1022:9603] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) [1022:9606] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390] (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1043:82f1] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4398] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 3a) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream
This is no way an acceptable patch. The driver needs to be converted properly to the Linux 2.6+ device model, instead of adding further kluges to it. Ben. Thanks, that patch wasn't provided by me. The old driver just broke during other updates and that patch was provided as a workaround to me. Arthur.
Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream
Package: src:linux
Version: 4.3.3-2
Severity: normal
Tags: upstream patch
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to load a kernel later than 4.2.0.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reported the problem to the developer and linux-scsi mailing list, a patch
was created that worked but it has not been applied upstream even though I
have confirmed that the patch works.
See:
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg45283.html
diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
index d7ffd66..8321c46 100644
--- a/drivers/pci/pci-driver.c
+++ b/drivers/pci/pci-driver.c
@@ -391,6 +391,7 @@ int __weak pcibios_alloc_irq(struct pci_dev *dev)
{
return 0;
}
+EXPORT_SYMBOL_GPL(pcibios_alloc_irq);
void __weak pcibios_free_irq(struct pci_dev *dev)
{
diff --git a/drivers/scsi/eata.c b/drivers/scsi/eata.c
index 227dd2c..7e6eaf8 100644
--- a/drivers/scsi/eata.c
+++ b/drivers/scsi/eata.c
@@ -1061,6 +1061,7 @@ static void enable_pci_ports(void)
driver_name, dev->bus->number, dev->devfn);
#endif
+pcibios_alloc_irq(dev);
if (pci_enable_device(dev))
printk
("%s: warning, pci_enable_device failed, bus %d devfn 0x%x.\n",
@@ -1520,6 +1521,7 @@ static void add_pci_ports(void)
if (!(dev = pci_get_class(PCI_CLASS_STORAGE_SCSI << 8, dev)))
break;
+pcibios_alloc_irq(dev);
if (pci_enable_device(dev)) {
#if defined(DEBUG_PCI_DETECT)
printk
## end
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available
** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge
[1106:0204]
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge [1106:0204]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: agpgart-amd64
00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge
[1106:1204]
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge [1106:1204]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
00:0f.0 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 07)
(prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc.
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE [1106:0571]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: pata_via
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: uhci_hcd
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: uhci_hcd
00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: uhci_hcd
00:10.3 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
[1106:3038]
Control: I/O+ Mem+
Bug#764572: initramfs-tools: fails to finish booting with dirty filesystem(s)
Ben Hutchings wrote on 07/12/15 09:33: Control: reassign -1 src:linux 3.17-1~exp1 Control: tag -1 moreinfo On Sat, 18 Oct 2014 23:42:56 +1030 Arthur Marsh <arthur.ma...@internode.on.net> wrote: [...] Hi, I still have the issue that with initramfstools later than 0.116 (ie 0.117 and 0.118) that with the disks corrupted, the boot process would hang. With initramfs-tools 0.116, the boot process proceeded normally and successfully run fsck on the filesystems to be mounted (the disk above with a HPA was not listed in /etc/fstab to have any filesystems mounted). I'm not sure how to reproduce this bug without resorting to somehow deliberately corrupting a filesystem and/or disk partition table. I think this must be a kernel or hardware bug that is triggered by slightly different behaviour in initramfs-tools. Have you seen this issue recur with more recent kernel versions? Ben. I haven't seen this issue more recently but haven't had a dirty filesystem apart from those caused by a few power failures. Part of the problem may be that the forced filesystem checks with later than 0.116 version of initramfs-tools do not display any visible progress on the console, so it's not always clear what is happening. Is there a way to make the forced fsck progress (e.g. for the root filesystem) visible on the console with current versions of initramfs-tools? Arthur.
Bug#781239: initramfs-tools: when fsck of root file system forced, no feedback / fsck
Package: initramfs-tools Version: 0.119 Followup-For: Bug #781239 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After reproducing the problem by using: tune2fs -C 99 on the root filesystem of my machine running in 64 bit mode, I tried the same thing on my other machine running in 32 bit mode (which I am reporting from now) and fsck of the root filesystem ran successfully with feedback of the process. I am left wondering what is different between the configurations that would cause the failure to occur on the machine running in 64 bit mode but not on this machine. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jul 1 2013 /boot/initrd.img-3.10.0 -rw-r--r-- 1 root root 12M Sep 4 2013 /boot/initrd.img-3.11.0 -rw-r--r-- 1 root root 13M Nov 4 2013 /boot/initrd.img-3.12.0 -rw-r--r-- 1 root root 13M Jan 20 2014 /boot/initrd.img-3.13.0 -rw-r--r-- 1 root root 14M Mar 31 2014 /boot/initrd.img-3.14.0 -rw-r--r-- 1 root root 15M Aug 4 2014 /boot/initrd.img-3.16.0 -rw-r--r-- 1 root root 15M Mar 2 16:41 /boot/initrd.img-3.16.0-4-686-pae -rw-r--r-- 1 root root 16M Oct 6 15:48 /boot/initrd.img-3.17.0 -rw-r--r-- 1 root root 15M Dec 8 17:41 /boot/initrd.img-3.18.0 -rw-r--r-- 1 root root 15M Feb 9 21:38 /boot/initrd.img-3.19.0 -rw-r--r-- 1 root root 16M Mar 11 10:20 /boot/initrd.img-3.19.0-trunk-amd64 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.5.0 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.6.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.7.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.8.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.9.0 -rw-r--r-- 1 root root 15M Feb 23 19:48 /boot/initrd.img-4.0.0-rc1 -rw-r--r-- 1 root root 15M Mar 4 09:59 /boot/initrd.img-4.0.0-rc2 -rw-r--r-- 1 root root 15M Mar 9 12:47 /boot/initrd.img-4.0.0-rc3 -rw-r--r-- 1 root root 15M Mar 16 21:14 /boot/initrd.img-4.0.0-rc4 -rw-r--r-- 1 root root 15M Mar 23 17:42 /boot/initrd.img-4.0.0-rc5 -rw-r--r-- 1 root root 15M Mar 28 18:49 /boot/initrd.img-4.0.0-rc5+ -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.19.0+ root=UUID=96c96a61-8615-4715-86d0-09cb8c62638c ro -- resume RESUME=/dev/hda6 -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by snd_hrtimer16384 0 nfc94208 0 cpufreq_stats 16384 0 cpufreq_conservative16384 0 cpufreq_powersave 16384 0 cpufreq_userspace 16384 0 bnep 20480 2 binfmt_misc20480 1 nfnetlink_queue24576 0 nfnetlink_log 20480 0 nfnetlink 16384 2 nfnetlink_log,nfnetlink_queue bluetooth 450560 5 bnep rfkill 24576 3 nfc,bluetooth nls_utf8 16384 4 nls_cp437 16384 4 vfat 20480 4 fat61440 1 vfat hwmon_vid 16384 0 tun28672 0 snd_emu10k1_synth 16384 0 snd_emux_synth 36864 1 snd_emu10k1_synth snd_seq_midi_emul 16384 1 snd_emux_synth snd_seq_virmidi16384 1 snd_emux_synth snd_seq_midi_event 16384 1 snd_seq_virmidi snd_seq57344 4 snd_seq_midi_event,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul cuse 16384 3 fuse 86016 1 cuse lp 20480 0 uas20480 0 usb_storage49152 2 uas ppdev 20480 0 powernow_k824576 1 snd_emu10k1 135168 4 snd_emu10k1_synth snd_util_mem 16384 2 snd_emux_synth,snd_emu10k1 snd_hwdep 16384 2 snd_emux_synth,snd_emu10k1 snd_rawmidi28672 2 snd_seq_virmidi,snd_emu10k1 snd_seq_device 16384 4 snd_seq,snd_rawmidi,snd_emu10k1_synth,snd_emu10k1 snd_ac97_codec106496 1 snd_emu10k1 snd_pcm90112 2 snd_ac97_codec,snd_emu10k1 psmouse 106496 0 snd_timer 28672 4 snd_hrtimer,snd_pcm,snd_seq,snd_emu10k1 snd69632 16 snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_seq_device radeon 1359872 3 ac97_bus 16384 1 snd_ac97_codec soundcore 16384 1 snd pcspkr 16384 0 amd64_edac_mod 32768 0 evdev 20480 9 serio_raw 16384 0 edac_mce_amd 24576 1 amd64_edac_mod edac_core 53248 2 amd64_edac_mod k8temp 16384 0 i2c_viapro 16384 0 emu10k1_gp 16384 0
Bug#763516: initramfs-tools: fails to boot with dirty root filesystem
Package: initramfs-tools Followup-For: Bug #763516 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** version 0.119 of initramfs-tools fixed this problem but left one without any feedback on the progress of a forced fsck of the root filesystem nor the means to interrupt it (bug #781239). * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jul 1 2013 /boot/initrd.img-3.10.0 -rw-r--r-- 1 root root 12M Sep 8 2013 /boot/initrd.img-3.11.0 -rw-r--r-- 1 root root 13M Nov 4 2013 /boot/initrd.img-3.12.0 -rw-r--r-- 1 root root 14M Jan 20 2014 /boot/initrd.img-3.13.0 -rw-r--r-- 1 root root 14M Mar 31 2014 /boot/initrd.img-3.14.0 -rw-r--r-- 1 root root 15M Aug 5 2014 /boot/initrd.img-3.16.0 -rw-r--r-- 1 root root 15M Mar 2 16:38 /boot/initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 15M Oct 6 13:16 /boot/initrd.img-3.17.0 -rw-r--r-- 1 root root 15M Dec 8 15:09 /boot/initrd.img-3.18.0 -rw-r--r-- 1 root root 15M Feb 9 15:28 /boot/initrd.img-3.19.0 -rw-r--r-- 1 root root 16M Mar 11 10:24 /boot/initrd.img-3.19.0-trunk-amd64 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.5.0 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.6.0 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.7.0 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.8.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.9.0 -rw-r--r-- 1 root root 15M Feb 23 21:53 /boot/initrd.img-4.0.0-rc1 -rw-r--r-- 1 root root 15M Mar 4 08:12 /boot/initrd.img-4.0.0-rc2 -rw-r--r-- 1 root root 16M Mar 9 14:41 /boot/initrd.img-4.0.0-rc3 -rw-r--r-- 1 root root 16M Mar 16 13:36 /boot/initrd.img-4.0.0-rc4 -rw-r--r-- 1 root root 16M Mar 23 14:53 /boot/initrd.img-4.0.0-rc4+ -rw-r--r-- 1 root root 16M Mar 23 15:59 /boot/initrd.img-4.0.0-rc5 -rw-r--r-- 1 root root 16M Mar 29 00:50 /boot/initrd.img-4.0.0-rc5+ -rw-r--r-- 1 root root 16M Mar 28 23:58 /boot/initrd.img-4.0.0-rc5+119 -rw-r--r-- 1 root root 15M Mar 29 00:49 /boot/initrd.img-rc5+116 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.0.0-rc5+ root=UUID=39706f53-7c27-4310-b22a-36c7b042d1a1 ro radeon.audio=1 -- resume # RESUME=/dev/sda5 RESUME='UUID=604db355-002c-4f41-b31c-438fe788b26d' -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by rfcomm 69632 4 arc4 16384 0 ecb16384 0 md416384 0 hmac 16384 1 nls_utf8 16384 4 cifs 557056 5 dns_resolver 16384 1 cifs fscache65536 1 cifs cpufreq_userspace 16384 0 cpufreq_conservative16384 0 nfc 106496 0 cpufreq_stats 16384 0 bnep 20480 2 bluetooth 499712 8 bnep,rfcomm rfkill 28672 4 nfc,bluetooth cpufreq_powersave 16384 0 binfmt_misc20480 1 uinput 20480 1 max665016384 0 fuse 94208 3 parport_pc 28672 0 ppdev 20480 0 lp 20480 0 parport45056 3 lp,ppdev,parport_pc snd_hda_codec_hdmi 49152 1 ir_sharp_decoder 16384 0 ir_mce_kbd_decoder 16384 0 ir_lirc_codec 16384 0 lirc_dev 20480 1 ir_lirc_codec ir_sanyo_decoder 16384 0 ir_xmp_decoder 16384 0 ir_sony_decoder16384 0 ir_rc5_decoder 16384 0 ir_nec_decoder 16384 0 ir_jvc_decoder 16384 0 ir_rc6_decoder 16384 0 fc0012 16384 1 rtl283224576 1 i2c_mux16384 1 rtl2832 snd_hda_codec_realtek77824 1 dvb_usb_rtl28xxu 32768 0 dvb_usb_v2 36864 1 dvb_usb_rtl28xxu dvb_core 118784 2 rtl2832,dvb_usb_v2 snd_hda_codec_generic69632 1 snd_hda_codec_realtek rc_core28672 14 ir_sharp_decoder,ir_xmp_decoder,lirc_dev,ir_lirc_codec,dvb_usb_rtl28xxu,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,ir_mce_kbd_decoder,ir_jvc_decoder,dvb_usb_v2,ir_rc6_decoder,ir_sanyo_decoder snd_hda_intel 32768 5 radeon 1478656 2 snd_hda_controller 32768 1 snd_hda_intel kvm_amd61440 0 kvm 491520 1 kvm_amd snd_hda_codec 143360 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller psmouse 114688 0 snd_hwdep 16384 1 snd_hda_codec snd_pcm_oss49152 0 snd_mixer_oss 24576 1 snd_pcm_oss snd_pcm 102400 5
Bug#764572: initramfs-tools: fails to finish booting with dirty filesystem(s)
Ben Hutchings wrote, on 13/10/14 06:16: On Mon, 2014-10-13 at 02:38 +1030, Arthur Marsh wrote: Package: initramfs-tools Version: 0.116 Followup-For: Bug #764572 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Another datapoint. I have a hard disk whose filesystems are *not* mounted at start-up, but after a corruption issue, the disk's state causes a lock-up requiring a hardware reset and a second start-up (not helpful if this was a remote machine). On the second (successful) start-up I saw these messages: $ dmesg|grep sdc [4.934246] sd 2:0:1:0: [sdc] 66055248 512-byte logical blocks: (33.8 GB/31.4 GiB) [4.934523] sd 2:0:1:0: [sdc] Write Protect is off [4.934580] sd 2:0:1:0: [sdc] Mode Sense: 00 3a 00 00 [4.934703] sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.967651] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc3 [4.968073] sdc: p3 size 1950 extends beyond EOD, enabling native capacity [...] This means: your hard drive has an HPA https://en.wikipedia.org/wiki/Host_Protected_Area configured, but you actually use that area under Linux. Linux automatically enables access to the HPA when it detects this. This was implemented in 2.6.34 and backported to squeeze; you just didn't notice the messages before. Ben. Hi, I still have the issue that with initramfstools later than 0.116 (ie 0.117 and 0.118) that with the disks corrupted, the boot process would hang. With initramfs-tools 0.116, the boot process proceeded normally and successfully run fsck on the filesystems to be mounted (the disk above with a HPA was not listed in /etc/fstab to have any filesystems mounted). I'm not sure how to reproduce this bug without resorting to somehow deliberately corrupting a filesystem and/or disk partition table. Regards, Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54426758.2020...@internode.on.net
Bug#764572: initramfs-tools: fails to finish booting with dirty filesystem(s)
Package: initramfs-tools Version: 0.116 Followup-For: Bug #764572 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Another datapoint. I have a hard disk whose filesystems are *not* mounted at start-up, but after a corruption issue, the disk's state causes a lock-up requiring a hardware reset and a second start-up (not helpful if this was a remote machine). On the second (successful) start-up I saw these messages: $ dmesg|grep sdc [4.934246] sd 2:0:1:0: [sdc] 66055248 512-byte logical blocks: (33.8 GB/31.4 GiB) [4.934523] sd 2:0:1:0: [sdc] Write Protect is off [4.934580] sd 2:0:1:0: [sdc] Mode Sense: 00 3a 00 00 [4.934703] sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.967651] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc3 [4.968073] sdc: p3 size 1950 extends beyond EOD, enabling native capacity [5.173494] sd 2:0:1:0: [sdc] 78242976 512-byte logical blocks: (40.0 GB/37.3 GiB) [5.174584] sdc: detected capacity change from 33820286976 to 40060403712 [5.226390] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc3 [5.228297] sdc: detected capacity change from 0 to 40060403712 [5.228595] sd 2:0:1:0: [sdc] Attached SCSI disk Somehow this error the first time round was partially fixed and then caused a lock-up, then on the second boot attempt completed. * What exactly did you do (or not do) that was effective (or ineffective)? A hardware reset was required when the boot process hung. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jul 1 2013 /boot/initrd.img-3.10.0 -rw-r--r-- 1 root root 12M Sep 4 2013 /boot/initrd.img-3.11.0 -rw-r--r-- 1 root root 13M Nov 4 2013 /boot/initrd.img-3.12.0 -rw-r--r-- 1 root root 13M Jan 20 2014 /boot/initrd.img-3.13.0 -rw-r--r-- 1 root root 14M Mar 31 2014 /boot/initrd.img-3.14.0 -rw-r--r-- 1 root root 16M Sep 21 09:27 /boot/initrd.img-3.16-2-686-pae -rw-r--r-- 1 root root 16M Oct 11 13:29 /boot/initrd.img-3.16-3-686-pae -rw-r--r-- 1 root root 15M Aug 4 14:06 /boot/initrd.img-3.16.0 -rw-r--r-- 1 root root 16M Sep 20 09:42 /boot/initrd.img-3.17-rc5-686-pae -rw-r--r-- 1 root root 16M Oct 6 15:48 /boot/initrd.img-3.17.0 -rw-r--r-- 1 root root 15M Oct 13 01:48 /boot/initrd.img-3.17.0+ -rw-r--r-- 1 root root 12M Jul 29 22:37 /boot/initrd.img-3.2.0-4-686-pae -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.5.0 -rw-r--r-- 1 root root 11M Jun 14 2013 /boot/initrd.img-3.6.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.7.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.8.0 -rw-r--r-- 1 root root 12M Jun 14 2013 /boot/initrd.img-3.9.0 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.17.0 root=UUID=96c96a61-8615-4715-86d0-09cb8c62638c ro -- resume RESUME=/dev/hda6 -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by snd_hrtimer12648 1 nfc83473 0 cpufreq_stats 13111 0 cpufreq_conservative14802 0 cpufreq_powersave 12554 0 cpufreq_userspace 12771 0 bnep 18829 2 nfnetlink_queue17836 0 nfnetlink_log 17591 0 nfnetlink 14466 2 nfnetlink_log,nfnetlink_queue bluetooth 389817 5 bnep rfkill 21695 3 nfc,bluetooth binfmt_misc13111 1 nls_utf8 12493 4 nls_cp437 12751 4 vfat 17166 4 fat55862 1 vfat cuse 13213 3 fuse 81416 1 cuse tun26628 0 snd_emu10k1_synth 13104 1 snd_emux_synth 33539 2 snd_emu10k1_synth snd_seq_midi_emul 13529 1 snd_emux_synth snd_seq_virmidi13248 1 snd_emux_synth snd_seq_midi_event 14503 1 snd_seq_virmidi snd_seq52764 6 snd_seq_midi_event,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul w83627hf 27081 0 hwmon_vid 12687 1 w83627hf max665013931 0 lp 17395 0 uas22763 0 usb_storage48591 2 uas radeon 1292179 2 ttm73197 1 radeon drm_kms_helper 82292 1 radeon ppdev 17363 0 drm 248829 5 ttm,drm_kms_helper,radeon psmouse95744 0 evdev 17449 9 snd_emu10k1 137141 2 snd_emu10k1_synth i2c_algo_bit 13190 1 radeon serio_raw 13210 0 pcspkr 12630 0 snd_util_mem 13821 2 snd_emux_synth,snd_emu10k1 snd_hwdep 13272 2 snd_emux_synth,snd_emu10k1 emu10k1_gp 12550 0 snd_ac97_codec101724 1
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Hi, I just did: aplay file-on-server.wav where the file was several minutes long and I could repeatedly restart the samba server if I wanted to, but if I had a crash it happened on the first restart of the server. WAV files have the advantage in testing of a constant and fairly high data rate for playback. Regards, Arthur. Steve French wrote, on 04/10/14 02:29: I was trying to reproduce this with totem playing a 30 second FLAC file over the network mount but wasn't able to - how did you repro it? On Thu, Oct 2, 2014 at 4:33 AM, Pavel Shilovsky pshilov...@samba.org wrote: 2014-10-01 15:34 GMT+04:00 Arthur Marsh arthur.ma...@internode.on.net: I managed to complete a git bisect -- fs/cifs: git bisect good 69cebd75606f8b9162ad5d0104367370ceabeeba is the first bad commit commit 69cebd75606f8b9162ad5d0104367370ceabeeba Author: Pavel Shilovsky pshilov...@samba.org Date: Tue Jun 24 13:42:03 2014 +0400 CIFS: Fix rsize usage in readpages If a server changes maximum buffer size for read (rsize) requests on reconnect we can fail on repeating with a big size buffer on -EAGAIN error in readpages. Fix this by checking rsize all the time before repeating requests. Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 8ed2e10a1581bab7b47a7dab4c5763bfdebe0e69 9eca94b68e9a21e1e5e6712fd37012cfe6e7d6d6 M fs am64:/usr/src/linux# git bisect log git bisect start '--' 'fs/cifs' # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # bad: [0ada36b244e8316bb47b46b84b33c5a507bed7a4] CIFS: Separate page reading from user read git bisect bad 0ada36b244e8316bb47b46b84b33c5a507bed7a4 # good: [619aa48edbab47367fa8a65e568f63fd64d6b4af] CIFS: Separate page sending from writepages git bisect good 619aa48edbab47367fa8a65e568f63fd64d6b4af # good: [43de94eadf0ceda54509335343bdc1349a2c5ab3] CIFS: Separate writing from iovec write git bisect good 43de94eadf0ceda54509335343bdc1349a2c5ab3 # good: [cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1] CIFS: Use multicredits for SMB 2.1/3 writes git bisect good cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1 # bad: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages git bisect bad 69cebd75606f8b9162ad5d0104367370ceabeeba # good: [387eb92ac6892518fb67e423f65fcaca76e256a8] CIFS: Separate page search from readpages git bisect good 387eb92ac6892518fb67e423f65fcaca76e256a8 # first bad commit: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages It points to a different first bad commit and I apologise if this has made it more difficult to locate the problem. I am happy to try more tests to help identify the problem. Thank you for pointing it out! I've reproduced and created a patch that fixes the problem to me (see the attachment). Can you test it, please? -- Best regards, Pavel Shilovsky. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542ede1e.6040...@internode.on.net
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Sorry, I only tried doing a service restart rather than a service stop, wait, service start. I assumed the problem happened when the client was starved for input when smbd was stopped. I notice that the patches for this have come through to Linus' tree. I am rebuilding the kernel with them after removing Pavel's test patch. Regards, Arthur. Steve French wrote, on 04/10/14 04:29: Retried (slightly earlier build) but instead of doing ifconfig lo down I did a killall of smbd - I then got a system hang within a few seconds of killing samba. Did you ever get the failure early, before restarting Samba? On Fri, Oct 3, 2014 at 12:34 PM, Arthur Marsh arthur.ma...@internode.on.net wrote: Hi, I just did: aplay file-on-server.wav where the file was several minutes long and I could repeatedly restart the samba server if I wanted to, but if I had a crash it happened on the first restart of the server. WAV files have the advantage in testing of a constant and fairly high data rate for playback. Regards, Arthur. Steve French wrote, on 04/10/14 02:29: I was trying to reproduce this with totem playing a 30 second FLAC file over the network mount but wasn't able to - how did you repro it? On Thu, Oct 2, 2014 at 4:33 AM, Pavel Shilovsky pshilov...@samba.org wrote: 2014-10-01 15:34 GMT+04:00 Arthur Marsh arthur.ma...@internode.on.net: I managed to complete a git bisect -- fs/cifs: git bisect good 69cebd75606f8b9162ad5d0104367370ceabeeba is the first bad commit commit 69cebd75606f8b9162ad5d0104367370ceabeeba Author: Pavel Shilovsky pshilov...@samba.org Date: Tue Jun 24 13:42:03 2014 +0400 CIFS: Fix rsize usage in readpages If a server changes maximum buffer size for read (rsize) requests on reconnect we can fail on repeating with a big size buffer on -EAGAIN error in readpages. Fix this by checking rsize all the time before repeating requests. Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 8ed2e10a1581bab7b47a7dab4c5763bfdebe0e69 9eca94b68e9a21e1e5e6712fd37012cfe6e7d6d6 M fs am64:/usr/src/linux# git bisect log git bisect start '--' 'fs/cifs' # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # bad: [0ada36b244e8316bb47b46b84b33c5a507bed7a4] CIFS: Separate page reading from user read git bisect bad 0ada36b244e8316bb47b46b84b33c5a507bed7a4 # good: [619aa48edbab47367fa8a65e568f63fd64d6b4af] CIFS: Separate page sending from writepages git bisect good 619aa48edbab47367fa8a65e568f63fd64d6b4af # good: [43de94eadf0ceda54509335343bdc1349a2c5ab3] CIFS: Separate writing from iovec write git bisect good 43de94eadf0ceda54509335343bdc1349a2c5ab3 # good: [cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1] CIFS: Use multicredits for SMB 2.1/3 writes git bisect good cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1 # bad: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages git bisect bad 69cebd75606f8b9162ad5d0104367370ceabeeba # good: [387eb92ac6892518fb67e423f65fcaca76e256a8] CIFS: Separate page search from readpages git bisect good 387eb92ac6892518fb67e423f65fcaca76e256a8 # first bad commit: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages It points to a different first bad commit and I apologise if this has made it more difficult to locate the problem. I am happy to try more tests to help identify the problem. Thank you for pointing it out! I've reproduced and created a patch that fixes the problem to me (see the attachment). Can you test it, please? -- Best regards, Pavel Shilovsky. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542f475b.2020...@internode.on.net
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Pavel Shilovsky wrote, on 02/10/14 19:03: 2014-10-01 15:34 GMT+04:00 Arthur Marsh arthur.ma...@internode.on.net: I managed to complete a git bisect -- fs/cifs: git bisect good 69cebd75606f8b9162ad5d0104367370ceabeeba is the first bad commit commit 69cebd75606f8b9162ad5d0104367370ceabeeba Author: Pavel Shilovsky pshilov...@samba.org Date: Tue Jun 24 13:42:03 2014 +0400 CIFS: Fix rsize usage in readpages If a server changes maximum buffer size for read (rsize) requests on reconnect we can fail on repeating with a big size buffer on -EAGAIN error in readpages. Fix this by checking rsize all the time before repeating requests. Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 8ed2e10a1581bab7b47a7dab4c5763bfdebe0e69 9eca94b68e9a21e1e5e6712fd37012cfe6e7d6d6 M fs am64:/usr/src/linux# git bisect log git bisect start '--' 'fs/cifs' # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # bad: [0ada36b244e8316bb47b46b84b33c5a507bed7a4] CIFS: Separate page reading from user read git bisect bad 0ada36b244e8316bb47b46b84b33c5a507bed7a4 # good: [619aa48edbab47367fa8a65e568f63fd64d6b4af] CIFS: Separate page sending from writepages git bisect good 619aa48edbab47367fa8a65e568f63fd64d6b4af # good: [43de94eadf0ceda54509335343bdc1349a2c5ab3] CIFS: Separate writing from iovec write git bisect good 43de94eadf0ceda54509335343bdc1349a2c5ab3 # good: [cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1] CIFS: Use multicredits for SMB 2.1/3 writes git bisect good cb7e9eabb2b584884db0d11ae0376d31ac1cfdc1 # bad: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages git bisect bad 69cebd75606f8b9162ad5d0104367370ceabeeba # good: [387eb92ac6892518fb67e423f65fcaca76e256a8] CIFS: Separate page search from readpages git bisect good 387eb92ac6892518fb67e423f65fcaca76e256a8 # first bad commit: [69cebd75606f8b9162ad5d0104367370ceabeeba] CIFS: Fix rsize usage in readpages It points to a different first bad commit and I apologise if this has made it more difficult to locate the problem. I am happy to try more tests to help identify the problem. Thank you for pointing it out! I've reproduced and created a patch that fixes the problem to me (see the attachment). Can you test it, please? I've tested it on AMD64 and confirms that it works. Thanks very much! Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542d777f.6070...@internode.on.net
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Pavel Shilovsky wrote, on 01/10/14 10:32: 2014-09-30 18:49 GMT+04:00 Arthur Marsh arthur.ma...@internode.on.net: Pardon the top post but I tried the same thing on my dual core Pentium 4 machine mounting via cifs a filesytem on my AMD64 (quad core) machine, then running aplay /mnt/remotefilesystem/somefile.wav then restarting samba on the serving machine. The results were the same as what I've posted before with the client being on the quad-core AMD64 machine and the server being the Pentium 4 machine, a nasty lock-up pointing to similar code. Has anyone else been able to reproduce this problem? Regards, Arthur Marsh. Arthur Marsh wrote, on 27/09/14 01:45: Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Pardon the top post but I tried the same thing on my dual core Pentium 4 machine mounting via cifs a filesytem on my AMD64 (quad core) machine, then running aplay /mnt/remotefilesystem/somefile.wav then restarting samba on the serving machine. The results were the same as what I've posted before with the client being on the quad-core AMD64 machine and the server being the Pentium 4 machine, a nasty lock-up pointing to similar code. Has anyone else been able to reproduce this problem? Regards, Arthur Marsh. Arthur Marsh wrote, on 27/09/14 01:45: Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes git bisect good 7f6c50086a6f5bc0fee46548afc836070a439313 # first bad commit: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
I also reproduced the general protection fault with the current Linus git head (3.17-rc6+) and trying each of vers=1.0 and vers=2.0 and vers=3.0. I am really surprised if no-one else has experienced this problem given how I have been able to reproduce it across all the 3.17.0-r1 to 3.17.0-rc6 kernel versions. Arthur. Steve French wrote on 27/09/14 02:02: Am curious whether it also fails with vers=3.0 on mount On Fri, Sep 26, 2014 at 9:32 AM, Steve French smfre...@gmail.com wrote: cifs mount (default mount options) or mount with SMB2 or SMB3 (vers=2.02 or vers=3.0)? On Fri, Sep 26, 2014 at 9:15 AM, Arthur Marsh arthur.ma...@internode.on.net wrote: Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes git bisect
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes git bisect good 7f6c50086a6f5bc0fee46548afc836070a439313 # first bad commit: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5425911c.3050...@internode.on.net
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
Steve French wrote on 27/09/14 02:02: cifs mount (default mount options) or mount with SMB2 or SMB3 (vers=2.02 or vers=3.0)? On Fri, Sep 26, 2014 at 9:15 AM, Arthur Marsh arthur.ma...@internode.on.net wrote: Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes git bisect good 7f6c50086a6f5bc0fee46548afc836070a439313 # first bad commit: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write mount -t cifs //192.168.1.100/homes /mnt/homes //192.168.1.100/homes on /mnt/homes type cifs (rw,relatime,vers=1.0,cache=strict,username=root,domain=VICTORIA,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.100,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1) Regards
Bug#762306: lockup when accessing cifs-mounted file on 3.17.0-rc1 and later when remote samba server is restarted
I tried each of the -o vers=2.0 and the -o vers=3.0 options to the mount -t cifs command with kernel 3.17.0-rc6 and also received a general protection fault. Arthur. Steve French wrote on 27/09/14 02:02: Am curious whether it also fails with vers=3.0 on mount On Fri, Sep 26, 2014 at 9:32 AM, Steve French smfre...@gmail.com wrote: cifs mount (default mount options) or mount with SMB2 or SMB3 (vers=2.02 or vers=3.0)? On Fri, Sep 26, 2014 at 9:15 AM, Arthur Marsh arthur.ma...@internode.on.net wrote: Arthur Marsh wrote on 16/09/14 03:17: Arthur Marsh wrote, on 14/09/14 21:15: On 3.16.0 kernels, whether compiled by myself or the stock Debian kernel, if I have program accessing a file on a CIFS-mounted file system (specifically playing an audio file), and restart the samba server on the remote machine, I might get a brief pause, but no major problems. On 3.17.0-rc1 and later I get a complete machine lock-up. Illustration: https://pbs.twimg.com/media/BxfPkdgCcAAlpUo.jpg:large Has anyone else experienced similar? I'm happy to supply any further details and try test fixes. Arthur. I'm still getting the problem with kernel 3.17.0-rc5 Has anyone been able to reproduce the problem? Arthur. I was off sick this past week but completed the bisect: git bisect good 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 is the first bad commit commit 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 Author: Pavel Shilovsky pshilov...@samba.org Date: Fri Jun 20 15:48:40 2014 +0400 CIFS: Separate filling pages from iovec write Reviewed-by: Shirish Pargaonkar spargaon...@suse.com Signed-off-by: Pavel Shilovsky pshilov...@samba.org Signed-off-by: Steve French smfre...@gmail.com :04 04 1be960992f3d75b4998082fda3f3c2fca213b9e5 318c46c63c983fe898480e1b88e97b818af1e502 M fs git bisect log: git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9] Linux 3.17-rc1 git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 # good: [ae045e2455429c418a418a3376301a9e5753a0a8] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good ae045e2455429c418a418a3376301a9e5753a0a8 # good: [44c916d58b9ef1f2c4aec2def57fa8289c716a60] Merge tag 'cleanup-for-3.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc git bisect good 44c916d58b9ef1f2c4aec2def57fa8289c716a60 # skip: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect skip 023f78b02c729070116fa3a7ebd4107a032d3f5c # skip: [908790fa3b779d37365e6b28e3aa0f6e833020c3] dcache: d_splice_alias mustn't create directory aliases git bisect skip 908790fa3b779d37365e6b28e3aa0f6e833020c3 # bad: [58d08e3b2c2033354b91467da33deffa06360c28] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform git bisect bad 58d08e3b2c2033354b91467da33deffa06360c28 # good: [27d438c56009e5ae632de36fe70985d1aab5e344] Revert drm/i915: Enable PSR by default. git bisect good 27d438c56009e5ae632de36fe70985d1aab5e344 # good: [ee34fb97a96ceac3334705ebab8b541ca291699f] ARM: dts: exynos5420: remove disp_pd git bisect good ee34fb97a96ceac3334705ebab8b541ca291699f # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # good: [95484b57265caa671a57efed06e322d56461774b] drm/nouveau/ltc: s/ltcg/ltc/ + cleanup git bisect good 95484b57265caa671a57efed06e322d56461774b # good: [63b12bdb0d21aca527996fb2c547387bfd3e14b8] Merge branch 'signal-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc git bisect good 63b12bdb0d21aca527996fb2c547387bfd3e14b8 # bad: [96784de59fb35077c2bb33c39328992b836d87d3] Merge branch 'stable-3.17' of git://git.infradead.org/users/pcmoore/selinux git bisect bad 96784de59fb35077c2bb33c39328992b836d87d3 # bad: [25f402598d2c8f0808d93715ad33e43b265c1604] CIFS: Fix rsize usage in user read git bisect bad 25f402598d2c8f0808d93715ad33e43b265c1604 # good: [90ac1387c2dfcd9b4bd302fce03b9ddff73d0093] CIFS: Separate pages initialization from writepages git bisect good 90ac1387c2dfcd9b4bd302fce03b9ddff73d0093 # skip: [6ec0b01b2691d1465bb7219e031e8bf38ccd9397] CIFS: Fix wsize usage in iovec write git bisect skip 6ec0b01b2691d1465bb7219e031e8bf38ccd9397 # bad: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write git bisect bad 66386c08be5d1a2eefc1f7ab8c008561b6c811e5 # good: [66231a47965c551d3056d5104f8b06688065748c] CIFS: Fix wsize usage in writepages git bisect good 66231a47965c551d3056d5104f8b06688065748c # good: [7f6c50086a6f5bc0fee46548afc836070a439313] CIFS: Fix cifs_writev_requeue when wsize changes git bisect good 7f6c50086a6f5bc0fee46548afc836070a439313 # first bad commit: [66386c08be5d1a2eefc1f7ab8c008561b6c811e5] CIFS: Separate filling pages from iovec write
Bug#749955: linux-image-3.14-1-rt-amd64: locks up at Switched to clocksource hpet
Package: src:linux Version: 3.14.4-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Attempting to boot linux-image-3.14-1-rt-amd64 on this machine. Last message displayed before lock-up was: Switched to clocksource hpet * What exactly did you do (or not do) that was effective (or ineffective)? ran a non-rt kernel instead. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1701 board_vendor: ASUSTeK Computer INC. board_name: M3A78 PRO board_version: Rev 1.xx ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:7910] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) [1022:9603] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: fea0-feaf Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) [1022:9606] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: feb0-febf Prefetchable memory behind bridge: fdf0-fdff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (prog-if 01 [AHCI 1.0]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: I/O ports at c000 [size=8] Region 1: I/O ports at b000 [size=4] Region 2: I/O ports at a000 [size=8] Region 3: I/O ports at 9000 [size=4] Region 4: I/O ports at 8000 [size=16] Region 5: Memory at fe9ff800 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at fe9fe000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci
Bug#551393: drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream
Jonathan Nieder wrote, on 15/01/12 11:38: tags 551393 + moreinfo quit Hi Arthur, Andres Salomon wrote: Arthur Marsharthur.ma...@internode.on.net wrote: I attempted to run extremetuxracer on this machine with radeon9200se and radeon driver and received the following output: How reproducible is this? Does it occur every time you run tuxracer (even after rebooting), or does it only happen every once in a while? Sorry for the long quiet. Do you still have the affected hardware? If so, does it still reproduce this bug? And if not, do you remember approximately when it was fixed? (/var/log/dpkg.log* might help) Curious, Jonathan Hi, I haven't tried playing etracer with the Radeon 9200SE until this last week when the old motherboard was replaced. I've been able to play etracer (slowly) with the new motherboard (ASUS P4S800, Pentium 4 / Sis chip-set) and Radeon 9200SE, and the only problem that I struck only happened once: Jan 13 01:53:10 localhost kernel: [21016.246298] [TTM] Failed to find memory space for buffer 0xf73fb42c eviction. Jan 13 01:53:10 localhost kernel: [21016.246308] [TTM] No space for f73fb42c (2731 pages, 10924K, 10M) Jan 13 01:53:10 localhost kernel: [21016.246312] [TTM] placement[0]=0x00070002 (1) Jan 13 01:53:10 localhost kernel: [21016.246315] [TTM] has_type: 1 Jan 13 01:53:10 localhost kernel: [21016.246317] [TTM] use_type: 1 Jan 13 01:53:10 localhost kernel: [21016.246320] [TTM] flags: 0x0002 Jan 13 01:53:10 localhost kernel: [21016.246322] [TTM] gpu_offset: 0xD800 Jan 13 01:53:10 localhost kernel: [21016.246325] [TTM] size: 16384 Jan 13 01:53:10 localhost kernel: [21016.246328] [TTM] available_caching: 0x0006 Jan 13 01:53:10 localhost kernel: [21016.246330] [TTM] default_caching: 0x0004 Jan 13 01:53:10 localhost kernel: [21016.246335] [TTM] 0x-0x0001:1: used Jan 13 01:53:10 localhost kernel: [21016.246339] [TTM] 0x0001-0x0101: 256: used Jan 13 01:53:10 localhost kernel: [21016.246342] [TTM] 0x0101-0x0201: 256: used Jan 13 01:53:10 localhost kernel: [21016.246346] [TTM] 0x0201-0x024c: 75: free Jan 13 01:53:10 localhost kernel: [21016.246349] [TTM] 0x024c-0x0252:6: used Jan 13 01:53:10 localhost kernel: [21016.246352] [TTM] 0x0252-0x0258:6: used Jan 13 01:53:10 localhost kernel: [21016.246356] [TTM] 0x0258-0x025e:6: used Jan 13 01:53:10 localhost kernel: [21016.246359] [TTM] 0x025e-0x0264:6: used Jan 13 01:53:10 localhost kernel: [21016.246362] [TTM] 0x0264-0x0287: 35: free Jan 13 01:53:10 localhost kernel: [21016.246365] [TTM] 0x0287-0x07dd: 1366: used Jan 13 01:53:10 localhost kernel: [21016.246369] [TTM] 0x07dd-0x0fde: 2049: free Jan 13 01:53:10 localhost kernel: [21016.246372] [TTM] 0x0fde-0x1534: 1366: used Jan 13 01:53:10 localhost kernel: [21016.246375] [TTM] 0x1534-0x17df: 683: free Jan 13 01:53:10 localhost kernel: [21016.246378] [TTM] 0x17df-0x1835: 86: used Jan 13 01:53:10 localhost kernel: [21016.246382] [TTM] 0x1835-0x188b: 86: used Jan 13 01:53:10 localhost kernel: [21016.246385] [TTM] 0x188b-0x18e1: 86: used Jan 13 01:53:10 localhost kernel: [21016.246388] [TTM] 0x18e1-0x1937: 86: used Jan 13 01:53:10 localhost kernel: [21016.246392] [TTM] 0x1937-0x198d: 86: used Jan 13 01:53:10 localhost kernel: [21016.246395] [TTM] 0x198d-0x1ccd: 832: free Jan 13 01:53:10 localhost kernel: [21016.246398] [TTM] 0x1ccd-0x1ce3: 22: used Jan 13 01:53:10 localhost kernel: [21016.246401] [TTM] 0x1ce3-0x24a5: 1986: free Jan 13 01:53:10 localhost kernel: [21016.246404] [TTM] 0x24a5-0x29fb: 1366: used Jan 13 01:53:10 localhost kernel: [21016.246408] [TTM] 0x29fb-0x2f51: 1366: used Jan 13 01:53:10 localhost kernel: [21016.246411] [TTM] 0x2f51-0x305c: 267: free Jan 13 01:53:10 localhost kernel: [21016.246414] [TTM] 0x305c-0x30b2: 86: used Jan 13 01:53:10 localhost kernel: [21016.246417] [TTM] 0x30b2-0x31b4: 258: free Jan 13 01:53:10 localhost kernel: [21016.246421] [TTM] 0x31b4-0x320a: 86: used Jan 13 01:53:10 localhost kernel: [21016.246424] [TTM] 0x320a-0x3260: 86: used Jan 13 01:53:10 localhost kernel: [21016.246427] [TTM] 0x3260-0x32b6: 86: used Jan 13 01:53:10 localhost kernel: [21016.246430] [TTM] 0x32b6-0x330c: 86: free Jan 13 01:53:10 localhost kernel: [21016.246434] [TTM] 0x330c-0x3362: 86: used Jan 13 01:53:10 localhost kernel: [21016.246437] [TTM] 0x3362-0x33b8: 86: used Jan 13 01:53:10 localhost kernel: [21016.246440] [TTM] 0x33b8-0x3534: 380: free Jan 13 01:53:10 localhost kernel: [21016.246443] [TTM] 0x3534-0x3544: 16:
Bug#649873: linux-tools: how to create for a new kernel release
Package: linux-tools Severity: wishlist I'd like to be able to build a linux-tools package for a kernel built from git source. Is that currently possible? -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-rc2+ (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/2024132900.25135.86333.reportbug@localhost
Bug#624217: linux-image-2.6.39-rc4-686-pae: many BUG: soft lockup - CPU#0 stuck for ... errors in 2.6.39-rc4
maximilian attems wrote, on 10/05/11 04:24: On Wed, 27 Apr 2011, Arthur Marsh wrote: Package: linux-2.6 Version: 2.6.39~rc4-1~experimental.1 Severity: normal In both the Debian and kernel.org 2.6.39-rc? kernels, I am experiencing numerous BUG: soft lockup - CPU#0 stuck for xxs! errors where xx is between 61 and 64. could you check against newest 2.6.39~rc6 ? This problem did not occur in 2.6.38 kernels. Previous attempts at git-bisecting the kernel.org kernels have been inconclusive. [ 300.238900] BUG: soft lockup - CPU#0 stuck for 63s! [konversation:3329] thanks for your report. Hi, I've had only one lockup using 2.6.39-rc6-git2 from kernel.org: May 9 00:55:47 victoria kernel: [214214.294673] INFO: task egrep:5360 blocked for more than 120 seconds. May 9 00:55:47 victoria kernel: [214214.294710] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. May 9 00:55:47 victoria kernel: [214214.294736] egrep D c2a8 0 5360623 0x May 9 00:55:47 victoria kernel: [214214.294781] c01e8820 0086 38a66c53 c2a8 d4ea7000 c2a8 c140b300 May 9 00:55:47 victoria kernel: [214214.294848] c01e89c0 c140b300 c01e8c30 d6c04020 c100191c c01e8820 c01e8c30 c01e8a34 May 9 00:55:47 victoria kernel: [214214.294912] 0004 1b47ab34 0660dd1a c3c33e60 c1047751 d6c06300 May 9 00:55:47 victoria kernel: [214214.294976] Call Trace: May 9 00:55:47 victoria kernel: [214214.295040] [c100191c] ? __switch_to+0x81/0xf4 May 9 00:55:47 victoria kernel: [214214.295091] [c1047751] ? timekeeping_get_ns+0x12/0x56 May 9 00:55:47 victoria kernel: [214214.295129] [c1047b46] ? ktime_get_ts+0x7a/0x82 May 9 00:55:47 victoria kernel: [214214.295184] [c1280d61] ? io_schedule+0x4a/0x5f May 9 00:55:51 victoria kernel: [214214.295233] [c108754c] ? sleep_on_page+0x5/0x8 May 9 00:55:53 victoria kernel: [214214.295271] [c1281247] ? __wait_on_bit+0x2f/0x54 May 9 00:55:53 victoria kernel: [214214.295304] [c1087547] ? lock_page+0x1d/0x1d May 9 00:55:53 victoria kernel: [214214.295339] [c1087651] ? wait_on_page_bit+0x57/0x5e May 9 00:55:53 victoria kernel: [214214.295377] [c1041343] ? autoremove_wake_function+0x29/0x29 May 9 00:55:53 victoria kernel: [214214.295419] [c1088c86] ? __lock_page_or_retry+0x2b/0x30 May 9 00:55:53 victoria kernel: [214214.295483] [c109d478] ? handle_pte_fault+0x3af/0x717 May 9 00:55:53 victoria kernel: [214214.295524] [c109d96b] ? handle_mm_fault+0x18b/0x19a May 9 00:55:53 victoria kernel: [214214.295574] [c1284646] ? do_page_fault+0x2e3/0x2fc May 9 00:55:53 victoria kernel: [214214.295615] [c1284363] ? spurious_fault+0x95/0x95 May 9 00:55:53 victoria kernel: [214214.295648] [c1282567] ? error_code+0x67/0x6c May 8 18:19:46 victoria kernel: [190453.077531] INFO: task lockfile-touch:32046 blocked for more than 120 seconds. May 8 18:19:46 victoria kernel: [190453.077567] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. May 8 18:19:46 victoria kernel: [190453.077593] lockfile-touch D ad16 0 32046 32039 0x May 8 18:19:46 victoria kernel: [190453.077637] d693a080 0086 8c79e376 ad16 d7880418 d4ea7000 ad16 c140b300 May 8 18:19:46 victoria kernel: [190453.077705] d693a220 c140b300 c057ddc0 d7880418 0001 0246 c112e69d c057ddc0 May 8 18:19:46 victoria kernel: [190453.077769] 0057ddb4 05abef16 c057dddc c1047751 d6c06300 May 8 18:19:46 victoria kernel: [190453.077833] Call Trace: May 8 18:19:46 victoria kernel: [190453.077917] [c112e69d] ? blk_flush_plug_list+0x16e/0x176 May 8 18:19:46 victoria kernel: [190453.077969] [c1047751] ? timekeeping_get_ns+0x12/0x56 May 8 18:19:46 victoria kernel: [190453.078007] [c1047b46] ? ktime_get_ts+0x7a/0x82 May 8 18:19:46 victoria kernel: [190453.078061] [c1280d61] ? io_schedule+0x4a/0x5f May 8 18:19:46 victoria kernel: [190453.078109] [c108754c] ? sleep_on_page+0x5/0x8 May 8 18:19:46 victoria kernel: [190453.078147] [c1281247] ? __wait_on_bit+0x2f/0x54 May 8 18:19:46 victoria kernel: [190453.078180] [c1087547] ? lock_page+0x1d/0x1d May 8 18:19:46 victoria kernel: [190453.078215] [c1087651] ? wait_on_page_bit+0x57/0x5e May 8 18:19:46 victoria kernel: [190453.078252] [c1041343] ? autoremove_wake_function+0x29/0x29 May 8 18:19:46 victoria kernel: [190453.078294] [c1088c86] ? __lock_page_or_retry+0x2b/0x30 May 8 18:19:46 victoria kernel: [190453.078329] [c1088e1a] ? filemap_fault+0x18f/0x2f9 May 8 18:19:46 victoria kernel: [190453.078392] [c109ab9e] ? __do_fault+0x40/0x2eb May 8 18:19:46 victoria kernel: [190453.078456] [c10221e3] ? finish_task_switch+0x36/0x92 May 8 18:19:46 victoria kernel: [190453.078501] [c109d348] ? handle_pte_fault+0x27f/0x717 May 8 18:19:46 victoria kernel: [190453.078549] [c10507ed] ? arch_local_irq_save+0xf/0x14 May 8 18:19:46 victoria kernel: [190453.078603] [c1043a86
Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
maximilian attems wrote, on 02/02/10 00:38: tags 541656 moreinfo stop On Sat, 15 Aug 2009, Arthur Marsh wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6~snapshot.14108 Severity: normal When attempting to upgrade I get: Setting up linux-image-2.6.30-1-686 (2.6.30-6~snapshot.14108) ... Running depmod. Running update-initramfs. Other valid candidates: update-initramfs mkinitrd.yaird update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img. dpkg: error processing linux-image-2.6.30-1-686 (--configure): subprocess installed post-installation script returned error exit status 17 can you still reproduce with 2.6.32 in squeeze/sid? No, it works fine now: $ ls -al /|grep init* lrwxrwxrwx 1 root root 32 Dec 10 22:50 initrd.img - boot/initrd.img-2.6.32-trunk-686 what is the output of cat /etc/kernel-img.conf $ cat /etc/kernel-img.conf # Do not create symbolic links in / do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = /usr/sbin/update-grub postrm_hook = /usr/sbin/update-grub sorry for the late answer, thanks for the report. Feel free to close this bug if you want. Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540022: linux-image-2.6.31-rc5-686: pcspkr no longer included, but snd-pcsp fails to load - no beeps
Moritz Muehlenhoff wrote, on 2009-12-30 11:51: On Wed, Aug 05, 2009 at 05:59:25PM +0930, Arthur Marsh wrote: Package: linux-image-2.6.31-rc5-686 Version: 2.6.31~rc5-1~experimental.1~snapshot.14082 Severity: normal In recent kernel builds, pcspkr is not included as a compiled module. This made my pc silent when I wanted to retain the beeps. I tried using snd-pcsp with the following result: Aug 5 17:00:18 victoria kernel: [12610.011216] Platform driver 'pcspkr' needs updating - please use dev_pm_ops Aug 5 17:00:19 victoria kernel: [12610.012153] input: PC Speaker as /devices/platform/pcspkr/input/input3 Aug 5 17:00:19 victoria kernel: [12610.012579] PCSP: Timer resolution is not sufficient (4000250nS) Aug 5 17:00:19 victoria kernel: [12610.012604] PCSP: Make sure you have HPET and ACPI enabled. Aug 5 17:00:19 victoria kernel: [12610.012652] PC-Speaker initialization failed. Aug 5 17:00:19 victoria kernel: [12610.013267] pcspkr: probe of pcspkr failed with error -5 This machine has a 1998 BIOS (Intel 440BX chipset) and does not seem to be compatible with snd-pcsp. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz Hi, pcspkr loads fine and I get the speaker beeps with kernel 2.6.32 from Debian Unstable thanks. Regards, Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551393: drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream
Package: linux-2.6 Version: 2.6.31-1~experimental.2 Severity: normal I attempted to run extremetuxracer on this machine with radeon9200se and radeon driver and received the following output: $ etracer Extreme TuxRacer SVN Development -- http://www.extremetuxracer.com (c) 2007 The ETRacer team (c) 2004-2005 The PPRacer team (c) 1999-2001 Jasmin F. Patryjfpa...@sunspirestudios.com ETRacer comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See http://www.gnu.org/copyleft/gpl.html for details. %%% etracer warning: Attempt to bind to Texture unloaded texture: `b-herring _run_icon' drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info. dmesg reported: [ 7176.628457] etracer: page allocation failure. order:4, mode:0xd0 [ 7176.628505] Pid: 28556, comm: etracer Not tainted 2.6.31 #1 [ 7176.628526] Call Trace: [ 7176.628607] [c1083110] ? __alloc_pages_nodemask+0x430/0x474 [ 7176.628669] [c109f35d] ? cache_alloc_refill+0x242/0x40c [ 7176.628711] [c109f5aa] ? __kmalloc+0x83/0xda [ 7176.628973] [d93ebac6] ? radeon_cp_cmdbuf+0xfb/0x117a [radeon] [ 7176.629304] [d939e33b] ? drm_ioctl+0x68/0x22b [drm] [ 7176.629489] [d939e485] ? drm_ioctl+0x1b2/0x22b [drm] [ 7176.629573] [d93eb9cb] ? radeon_cp_cmdbuf+0x0/0x117a [radeon] [ 7176.629624] [c1082da7] ? __alloc_pages_nodemask+0xc7/0x474 [ 7176.629685] [c102510a] ? __rcu_read_unlock+0x1b/0x25 [ 7176.629744] [c10ac367] ? vfs_ioctl+0x58/0x72 [ 7176.629784] [c10ac882] ? do_vfs_ioctl+0x45c/0x49c [ 7176.629839] [c108d143] ? __inc_zone_state+0xc/0x5b [ 7176.629887] [c10853a5] ? __lru_cache_add+0x6d/0x88 [ 7176.629926] [c124ece4] ? _spin_unlock+0x18/0x22 [ 7176.629963] [c1091af1] ? handle_mm_fault+0x5c6/0x5d7 [ 7176.630027] [c1032286] ? __do_softirq+0x157/0x195 [ 7176.630068] [c10ac906] ? sys_ioctl+0x44/0x64 [ 7176.630111] [c1002953] ? sysenter_do_call+0x12/0x28 [ 7176.630138] Mem-Info: [ 7176.630156] DMA per-cpu: [ 7176.630177] CPU0: hi:0, btch: 1 usd: 0 [ 7176.630196] Normal per-cpu: [ 7176.630217] CPU0: hi: 186, btch: 31 usd: 0 [ 7176.630260] Active_anon:20214 active_file:14730 inactive_anon:28389 [ 7176.630273] inactive_file:14536 unevictable:2765 dirty:1 writeback:50 unstable:0 [ 7176.630288] free:1545 slab:6338 mapped:8837 pagetables:1552 bounce:0 [ 7176.630334] DMA free:1560kB min:100kB low:124kB high:148kB active_anon:3808kB inactive_anon:5316kB active_file:2384kB inactive_file:2160kB unevictable:0kB present:15864kB pages_scanned:0 all_unreclaimable? no [ 7176.630370] lowmem_reserve[]: 0 365 365 365 [ 7176.630431] Normal free:4620kB min:2392kB low:2988kB high:3588kB active_anon:77048kB inactive_anon:108240kB active_file:56536kB inactive_file:55984kB unevictable:11060kB present:373888kB pages_scanned:0 all_unreclaimable? no [ 7176.630469] lowmem_reserve[]: 0 0 0 0 [ 7176.630508] DMA: 14*4kB 0*8kB 0*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1560kB [ 7176.630611] Normal: 951*4kB 74*8kB 10*16kB 2*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 4620kB [ 7176.630714] 42204 total pagecache pages [ 7176.630732] 12152 pages in swap cache [ 7176.630755] Swap cache stats: add 141416, delete 129264, find 37695/48129 [ 7176.630776] Free swap = 1988000kB [ 7176.630793] Total swap = 2200864kB [ 7176.665915] 98303 pages RAM [ 7176.665943] 0 pages HighMem [ 7176.665958] 1989 pages reserved [ 7176.665975] 48507 pages shared [ 7176.665990] 72565 pages non-shared I am running: xserver-xorg-video-radeon version 1:6.12.3-1 X.Org X server -- ATI Radeon display driver -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 64 Region 0: Memory at e800 (32-bit, prefetchable) [size=64M] Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: c000-cfff Memory behind bridge: ec00-edff Prefetchable memory behind bridge: d800-e7ff Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+
Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
Package: linux-image-2.6.30-1-686 Version: 2.6.30-6~snapshot.14108 Severity: normal When attempting to upgrade I get: Setting up linux-image-2.6.30-1-686 (2.6.30-6~snapshot.14108) ... Running depmod. Running update-initramfs. Other valid candidates: update-initramfs mkinitrd.yaird update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img. dpkg: error processing linux-image-2.6.30-1-686 (--configure): subprocess installed post-installation script returned error exit status 17 -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.31-rc5 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.13-5 Yet Another mkInitRD Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-24 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub-pc [grub] 1.96+20090808-2 GRand Unified Bootloader, version pn linux-doc-2.6.30 none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524643: closed by Ben Hutchings b...@decadent.org.uk (Re: linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption)
Just for anyone's interest, the problem was caused by not clearing/resetting the BIOS settings after upgrading the BIOS. Regards, Arthur. Debian Bug Tracking System wrote, on 01/06/09 07:42: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #524643: linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption It has been closed by Ben Hutchings b...@decadent.org.uk. ... Subject: Re: linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption From: Ben Hutchings b...@decadent.org.uk Date: Sun, 31 May 2009 23:07:50 +0100 To: 524643-d...@bugs.debian.org To: 524643-d...@bugs.debian.org I seem to remember that we discussed this bug on IRC, but the conclusions were not recorded here. However, my understanding is that these problems resulted from enabling APIC in the kernel while disabling it in the BIOS. This is considered to be misconfiguration and not a kernel bug. Ben. Subject: linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption From: Arthur Marsh arthur.ma...@internode.on.net Date: Sun, 19 Apr 2009 03:20:01 +0930 To: Debian Bug Tracking System sub...@bugs.debian.org To: Debian Bug Tracking System sub...@bugs.debian.org Package: linux-2.6 Severity: normal I recently purchase a pc with a dual-core AMD64 cpu and Asus M3A78 Pro motherboard. I experienced very poor disk i/o performance and filesystem corruption when I enabled the BIOS option ACPI APIC Support, to the extent that an ext3 filesystem had unrecoverable errors. The BIOS manual describes the option: ACPI APIC Support When set to enabled, the ACPI APIC table pointer is included in the RSDT pointer list. Since I've disabled ACPI APIC Support I have had no hard disk i/o problems, but since the patch http://patchwork.kernel.org/patch/1473/ has been applied to the kernel source, the kernel has disabled the use of the second CPU core. I've backed out that patch and recompiled the kernel to make both CPU cores available, but would rather a fix that doesn't require manually patching the kernel source. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524643: linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption
Package: linux-2.6 Severity: normal I recently purchase a pc with a dual-core AMD64 cpu and Asus M3A78 Pro motherboard. I experienced very poor disk i/o performance and filesystem corruption when I enabled the BIOS option ACPI APIC Support, to the extent that an ext3 filesystem had unrecoverable errors. The BIOS manual describes the option: ACPI APIC Support When set to enabled, the ACPI APIC table pointer is included in the RSDT pointer list. Since I've disabled ACPI APIC Support I have had no hard disk i/o problems, but since the patch http://patchwork.kernel.org/patch/1473/ has been applied to the kernel source, the kernel has disabled the use of the second CPU core. I've backed out that patch and recompiled the kernel to make both CPU cores available, but would rather a fix that doesn't require manually patching the kernel source. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524643: Acknowledgement (linux-2.6: enabling APIC on Asus M3A78 Pro motherboard causes disk i/o problems and corruption)
I should also mention that this disk i/o and filesystem corruption with ACPI APIC enabled was apparent when using the 2.6.26 kernel but not necessarily restricted to just that kernel. Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
http://patchwork.kernel.org/patch/1473/ causes kernel to only use 1 cpu core on Asus M3A78 Pro motherboard
Hi, I just went through a kernel bisection to find out why my Asus M3A78 Pro motherboard with dual core AMD64 cpu was only seeing one cpu core on 2.6.29 kernels, but showed and used both cores on earlier kernels such as 2.6.26. The kernel and applications I have been using were compiled for x86-64 architecture (64-bit). After bisection identified commit 7b37b5fd9ba32c0c5afc3537eed7e7466f2173e2 which added patch http://patchwork.kernel.org/patch/1473/ I rebuilt the current 2.6.29 kernel from http://kernel-archive.buildserver.net with that patch backed out, and again I had multiple cores available: $ dmesg|grep SMP [0.00] Linux version 2.6.29 (2.6.29) (r...@am64) (gcc version 4.3.3 (Debian 4.3.3-8) ) #1 SMP PREEMPT Sun Apr 19 02:19:00 CST 2009 [0.00] found SMP MP-table at [880ff780] 000ff780 [0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs I am happy to provide any further information to help identify why this patch caused the kernel to only see and use one core and identify a solution that does not cause the problems that the above patch was designed to fix. ACPI 2.0 is enabled in the BIOS. I disabled ACPI APIC support in the BIOS due to disk read/write problems and file system corruption, which I've just reported as Debian bug #524643 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524643 ) The Asus M4A78A Pro motherboard manual states: ACPI APIC Support When set to enabled, the ACPI APIC table pointer is included in the RSDT pointer list. Regards, Arthur Marsh. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524534: initramfs-tools: returns error when attempting to remove an already removed initrd
maximilian attems wrote, on 2009-04-19 01:31: On Sat, 18 Apr 2009, Arthur Marsh wrote: Package: initramfs-tools Version: 0.93.2 Severity: normal I was trying to remove a 2.6.27 kernel I had built from source and somehow the initrd was removed before initramfs-tools tried to remove it. can you put an set -x on top of /etc/kernel/postrm.d/initramfs-tools when trying to purge that one. thanks Note that the kernels I had problems removing were kernels built with make deb-pkg rather than kernel-package's make-kpkg. Removing linux-2.6.28-rc9 ... + '[' -z 2.6.28-rc9 ']' + '[' -z '' ']' + update-initramfs -d -k 2.6.28-rc9 update-initramfs: Deleting /boot/initrd.img-2.6.28-rc9 Purging configuration files for linux-2.6.28-rc9 ... + '[' -z 2.6.28-rc9 ']' + '[' -z '' ']' + update-initramfs -d -k 2.6.28-rc9 Cannot delete /boot/initrd.img-2.6.28-rc9, doesn't exist. run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1 dpkg: error processing linux-2.6.28-rc9 (--purge): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: linux-2.6.28-rc9 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Press return to continue. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: http://patchwork.kernel.org/patch/1473/ causes kernel to only use 1 cpu core on Asus M3A78 Pro motherboard
Arthur Marsh wrote, on 2009-04-19 03:39: Hi, I just went through a kernel bisection to find out why my Asus M3A78 Pro motherboard with dual core AMD64 cpu was only seeing one cpu core on 2.6.29 kernels, but showed and used both cores on earlier kernels such as 2.6.26. The kernel and applications I have been using were compiled for x86-64 architecture (64-bit). After bisection identified commit 7b37b5fd9ba32c0c5afc3537eed7e7466f2173e2 which added patch http://patchwork.kernel.org/patch/1473/ I rebuilt the current 2.6.29 kernel from http://kernel-archive.buildserver.net with that patch backed out, and again I had multiple cores available: $ dmesg|grep SMP [0.00] Linux version 2.6.29 (2.6.29) (r...@am64) (gcc version 4.3.3 (Debian 4.3.3-8) ) #1 SMP PREEMPT Sun Apr 19 02:19:00 CST 2009 [0.00] found SMP MP-table at [880ff780] 000ff780 [0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs I am happy to provide any further information to help identify why this patch caused the kernel to only see and use one core and identify a solution that does not cause the problems that the above patch was designed to fix. ACPI 2.0 is enabled in the BIOS. I disabled ACPI APIC support in the BIOS due to disk read/write problems and file system corruption, which I've just reported as Debian bug #524643 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524643 ) The Asus M4A78A Pro motherboard manual states: ACPI APIC Support When set to enabled, the ACPI APIC table pointer is included in the RSDT pointer list. I have since been unable to reproduce any problems with ACPI APIC enabled in the BIOS for kernels 2.6.26 and 2.6.29 so I have re-compiled the 2.6.29 to enable patch http://patchwork.kernel.org/patch/1473/ and now I get reported: $ dmesg|grep SMP [0.00] Linux version 2.6.29 (2.6.29) (r...@am64) (gcc version 4.3.3 (Debian 4.3.3-8) ) #1 SMP PREEMPT Sun Apr 19 04:59:40 CST 2009 [0.00] found SMP MP-table at [880ff780] 000ff780 [0.00] Using ACPI (MADT) for SMP configuration information [0.00] SMP: Allowing 4 CPUs, 2 hotplug CPUs Thanks to those who suggested that the ACPI APIC should be enabled. My conclusion is that corrupt BIOS settings after a BIOS upgrade caused the initial disk i/o problems which I wrongly attributed to the ACPI APIC enabled setting. By reseting the BIOS to defaults (but also disabling the default ACPI APIC enabled setting), further problems were avoided, but I didn't re-check the ACPI APIC enabled setting until the last few hours. Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524534: initramfs-tools: returns error when attempting to remove an already removed initrd
Package: initramfs-tools Version: 0.93.2 Severity: normal I was trying to remove a 2.6.27 kernel I had built from source and somehow the initrd was removed before initramfs-tools tried to remove it. This resulted in a failure to remove the kernel from the packaging system. See also bug #524499. The error message I was left with was: Cannot delete /boot/initrd.img-2.6.27, doesn't exist. run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1 dpkg: error processing linux-2.6.27 (--purge): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: linux-2.6.27 E: Sub-process /usr/bin/dpkg returned an error code (1) So this is a problem with /etc/kernel/postrm.d/initramfs-tools I temporarily added exit 0 to the start of /etc/kernel/postrm.d/initramfs-tools to force the removal of kernel-2.6.27. Right. We need to get the script in /etc/kernel/postrm.d/initramfs-tools fixed. Any idea where it came from? -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.26-2-amd64 root=UUID=39706f53-7c27-4310-b22a-36c7b042d1a1 ro -- /proc/filesystems ext3 vfat -- lsmod Module Size Used by battery16776 0 ipv6 288328 20 vfat 14976 0 fat51128 1 vfat nls_base 12932 2 vfat,fat it87 28952 0 hwmon_vid 7296 1 it87 loop 19468 0 snd_hda_intel 436440 0 snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81672 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 7428 0 snd_seq_oss33280 0 snd_seq_midi 11072 0 snd_rawmidi26784 1 snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 25744 2 snd_pcm,snd_seq snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd63688 10 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device i2c_piix4 13072 0 soundcore 12064 1 snd psmouse42268 0 i2c_core 27936 1 i2c_piix4 k8temp 9216 0 snd_page_alloc 13072 2 snd_hda_intel,snd_pcm pcspkr 7040 0 serio_raw 9860 0 shpchp 34208 0 pci_hotplug32056 1 shpchp wmi11712 0 button 11680 0 evdev 14208 3 ext3 124944 1 jbd51240 1 ext3 mbcache12804 1 ext3 sg 36576 0 sr_mod 19652 0 cdrom 37928 1 sr_mod sd_mod 29376 3 ata_generic10116 0 ide_pci_generic 9220 0 [permanent] ahci 33036 2 atiixp 8324 0 [permanent] libata165600 2 ata_generic,ahci ohci_hcd 25092 0 ide_core 128284 2 ide_pci_generic,atiixp scsi_mod 160760 4 sg,sr_mod,sd_mod,libata ehci_hcd 35980 0 dock 14112 1 libata r8169 31492 0 thermal22816 0 processor 42304 1 thermal fan 9352 0 thermal_sys17728 3 thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9.90-3 GNU cpio -- a program to manage ar ii findutils 4.4.0-3utilities for finding files--find, ii klibc-utils 1.5.15-1 small utilities built with klibc f ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo ii udev 0.140-2/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of
Bug#494009: linux-2.6: are the ATI firmware-nonfree files available?
Ben Hutchings wrote, on 10/03/09 14:13: On Fri, 2009-03-06 at 01:56 +1030, Arthur Marsh wrote: Package: linux-2.6 Followup-For: Bug #494009 I couldn't find any files containing ATI firmware at http://ftp.debian.org/debian/pool/non-free/f/firmware-nonfree/ Are these files available anywhere? They're in the Subversion repository for this package and will be in the next release. Note that the change to remove them from kernel images is also unreleased. Hi, I'd just found out that the non-DFSG-free firmware had been removed from the 2.6.29-rc* kernels at kernel-archive.buildserver.net, so I was interested to know if the firmware had been packaged anywhere. Regards, Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494009: linux-2.6: are the ATI firmware-nonfree files available?
Package: linux-2.6 Followup-For: Bug #494009 I couldn't find any files containing ATI firmware at http://ftp.debian.org/debian/pool/non-free/f/firmware-nonfree/ Are these files available anywhere? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.28 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511057: FTBFS: cpia2 module fails
Package: linux-source-2.6.28 Version: 2.6.28-1~experimental.1~snapshot.12545 Severity: normal I copied the kernel config from the most recent 686 binary to the 2.6.28 source directory, ran make menuconfig only changing some unrelated cpu options, leaving drivers at default, then make-kpkg --initrd linux-image and had the error: HOSTCC firmware/ihex2fw IHEX2FW firmware/keyspan_pda/keyspan_pda.fw IHEX2FW firmware/keyspan_pda/xircom_pgs.fw make[2]: *** No rule to make target `firmware/cpia2/stv0672_vp4.bin', needed by `__fw_modbuild'. Stop. make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-source-2.6.28' make: *** [debian/stamp/build/kernel] Error 2 I have removed the cpia2 driver using make menuconfig and have recommenced kernel compilation. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.28 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.28 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.28 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-18 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.28 suggests: ii kernel-package11.015 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20081220-1 developer's libraries and docs for ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded) -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: [Fwd: Patch added to scsi-rc-fixes-2.6: [SCSI] eata: fix the data buffer accessors conversion regression]
Please close this bug as it will be fixed in kernel 2.6.28. Regards, Arthur. Original Message Subject: Patch added to scsi-rc-fixes-2.6: [SCSI] eata: fix the data buffer accessors conversion regression Date: Tue, 23 Dec 2008 19:49:58 GMT From: James Bottomley j...@kernel.org To: Arthur Marsh arthur.ma...@internode.on.net,FUJITA Tomonori fujita.tomon...@lab.ntt.co.jp,James Bottomley james.bottom...@hansenpartnership.com,sta...@kernel.org Your commit: [SCSI] eata: fix the data buffer accessors conversion regression This fixes the regression introduced by the commit 58e2a02eb18393e76a469580fedf7caec190eb5e (eata: convert to use the data buffer accessors), reported: http://marc.info/?t=12298762136r=1w=2 - fix DMA_NONE handling in map_dma() - this driver can't use scsi_dma_map since host-shost_gendev.parent is not set properly (it uses scsi_register). Signed-off-by: FUJITA Tomonori fujita.tomon...@lab.ntt.co.jp Reported-by: Arthur Marsh arthur.ma...@internode.on.net Tested-by: Arthur Marsh arthur.ma...@internode.on.net Cc: sta...@kernel.org Signed-off-by: James Bottomley james.bottom...@hansenpartnership.com has been added to the upstream SCSI tree You can find it here: http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=508859405e33797342d42cda3e731464c2bcd7a8 This patch is scheduled to be pushed for 2.6.28 James Bottomley P.S. If you find this email unwanted, set up a procmail rule junking on the header: X-Git-Tree: SCSI -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: BUG: bad: [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use the data buffer accessors
I had a look at the current Debian 2.6.27 source and applied your patch
manually against it.
It will take me a few hours to compile the new kernel and I should be
able to test it in about 7 hours time.
Thanks again,
Arthur.
FUJITA Tomonori wrote, on 2008-12-22 12:39:
On Mon, 22 Dec 2008 02:38:16 +1030
Arthur Marsh arthur.ma...@internode.on.net wrote:
I've recently installed Debian on a PII-266 machine with DPT2044W SCSI
controller.
Kernels 2.6.18-2.6.22 work fine, and kernels 2.6.23-2.6.27 lock up after
loading the eata module using modprobe, with the error:
modprobe exited with preempt_count 1
I've run a git bisection and have a few more passes to go, but suspect
the commit in the subject line,
[58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use
the data buffer accessors
to be the patch which triggers the problem.
I'm not a C programmer, let alone a kernel programmer, but can build and
check any suggested patches.
Is anyone successfully using the eata module since the data buffer
accessors patch?
Is anyone able to examine the code to see if anything was done wrong in
the data buffer accessors patch?
Sorry about the problem. Can you try this patch?
diff --git a/drivers/scsi/eata.c b/drivers/scsi/eata.c
index a73a6bb..976cdd5 100644
--- a/drivers/scsi/eata.c
+++ b/drivers/scsi/eata.c
@@ -1626,8 +1626,15 @@ static void map_dma(unsigned int i, struct hostdata *ha)
cpp-sense_len = SCSI_SENSE_BUFFERSIZE;
- count = scsi_dma_map(SCpnt);
- BUG_ON(count 0);
+ if (!scsi_sg_count(SCpnt)) {
+ cpp-data_len = 0;
+ return;
+ }
+
+ count = pci_map_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+ pci_dir);
+ BUG_ON(!count);
+
scsi_for_each_sg(SCpnt, sg, count, k) {
cpp-sglist[k].address = H2DEV(sg_dma_address(sg));
cpp-sglist[k].num_bytes = H2DEV(sg_dma_len(sg));
@@ -1655,7 +1662,9 @@ static void unmap_dma(unsigned int i, struct hostdata *ha)
pci_unmap_single(ha-pdev, DEV2H(cpp-sense_addr),
DEV2H(cpp-sense_len), PCI_DMA_FROMDEVICE);
- scsi_dma_unmap(SCpnt);
+ if (scsi_sg_count(SCpnt))
+ pci_unmap_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+pci_dir);
if (!DEV2H(cpp-data_len))
pci_dir = PCI_DMA_BIDIRECTIONAL;
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: BUG: bad: [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use the data buffer accessors
FUJITA Tomonori wrote, on 22/12/08 12:39:
Sorry about the problem. Can you try this patch?
diff --git a/drivers/scsi/eata.c b/drivers/scsi/eata.c
index a73a6bb..976cdd5 100644
--- a/drivers/scsi/eata.c
+++ b/drivers/scsi/eata.c
@@ -1626,8 +1626,15 @@ static void map_dma(unsigned int i, struct hostdata *ha)
cpp-sense_len = SCSI_SENSE_BUFFERSIZE;
- count = scsi_dma_map(SCpnt);
- BUG_ON(count 0);
+ if (!scsi_sg_count(SCpnt)) {
+ cpp-data_len = 0;
+ return;
+ }
+
+ count = pci_map_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+ pci_dir);
+ BUG_ON(!count);
+
scsi_for_each_sg(SCpnt, sg, count, k) {
cpp-sglist[k].address = H2DEV(sg_dma_address(sg));
cpp-sglist[k].num_bytes = H2DEV(sg_dma_len(sg));
@@ -1655,7 +1662,9 @@ static void unmap_dma(unsigned int i, struct hostdata *ha)
pci_unmap_single(ha-pdev, DEV2H(cpp-sense_addr),
DEV2H(cpp-sense_len), PCI_DMA_FROMDEVICE);
- scsi_dma_unmap(SCpnt);
+ if (scsi_sg_count(SCpnt))
+ pci_unmap_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+pci_dir);
if (!DEV2H(cpp-data_len))
pci_dir = PCI_DMA_BIDIRECTIONAL;
Thanks, I applied the patch manually against the Debian 2.6.27 kernel
source at http://kernel-archive.buildserver.net/ and after starting the
patched kernel, the eata module loaded successfully. I mounted the
filesystems on the attached scsi disk and ran ls -alR on all filesystems
successfully.
dmesg reported:
[ 168.343910] PCI: setting IRQ 5 as level-triggered
[ 168.343944] pci :00:0a.0: found PCI INT A - IRQ 5
[ 168.346548] EATA/DMA 2.0x: Copyright (C) 1994-2003 Dario Ballabio.
[ 168.346657] EATA config options - tm:1, lc:y, mq:16, rs:y, et:n,
ip:y, ep:n, pp:y.
[ 168.346769] EATA0: 2.0C, PCI 0xe010, IRQ 5, BMST, SG 122, MB 64.
[ 168.346863] EATA0: wide SCSI support enabled, max_id 16, max_lun 8.
[ 168.346958] EATA0: SCSI channel 0 enabled, host target ID 7.
[ 168.411912] scsi0 : EATA/DMA 2.0x rev. 8.10.00
[ 169.953101] scsi 0:0:6:0: Direct-Access IBM DCAS-34330W
S65A PQ: 0 ANSI: 2
[ 169.953239] scsi 0:0:6:0: cmds/lun 16, sorted, simple tags.
[ 172.189180] Driver 'sd' needs updating - please use bus_type methods
[ 172.193186] sd 0:0:6:0: [sda] 8466688 512-byte hardware sectors (4335 MB)
[ 172.230078] sd 0:0:6:0: [sda] Write Protect is off
[ 172.230191] sd 0:0:6:0: [sda] Mode Sense: b3 00 00 08
[ 172.251052] sd 0:0:6:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 172.254288] sd 0:0:6:0: [sda] 8466688 512-byte hardware sectors (4335 MB)
[ 172.263454] sd 0:0:6:0: [sda] Write Protect is off
[ 172.263551] sd 0:0:6:0: [sda] Mode Sense: b3 00 00 08
[ 172.284232] sd 0:0:6:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 172.284375] sda: sda1 sda2 sda5
[ 172.322394] sd 0:0:6:0: [sda] Attached SCSI disk
As with 2.6.22 kernels gnu fdisk had problems with the scsi drive, but
cfdisk and sfdisk were ok:
[ 222.575704] fdisk[1996]: segfault at 60 ip 41b6d443 sp bff98034 error
4 in libc-2.7.so[41af7000+155000]
[ 249.063672] lfdisk[1998]: segfault at 60 ip 41b6d443 sp bfe50084
error 4 in libc-2.7.so[41af7000+155000]
The gfdisk/lfdisk error was reported as Debian Bug#463720:
Thanks very much for the rapid response to this bug report!
Arthur.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: BUG: bad: [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use the data buffer accessors
I've recently installed Debian on a PII-266 machine with DPT2044W SCSI controller. Kernels 2.6.18-2.6.22 work fine, and kernels 2.6.23-2.6.27 lock up after loading the eata module using modprobe, with the error: modprobe exited with preempt_count 1 I've run a git bisection and have a few more passes to go, but suspect the commit in the subject line, [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use the data buffer accessors to be the patch which triggers the problem. I'm not a C programmer, let alone a kernel programmer, but can build and check any suggested patches. Is anyone successfully using the eata module since the data buffer accessors patch? Is anyone able to examine the code to see if anything was done wrong in the data buffer accessors patch? Regards, Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: [Fwd: Re: BUG: bad: [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use the data buffer accessors]
I received this reply but do not know how to apply the patch.
Arthur.
Original Message
Subject: Re: BUG: bad: [58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI]
eata: convert to use the data buffer accessors
Date: Mon, 22 Dec 2008 11:09:17 +0900
From: FUJITA Tomonori fujita.tomon...@lab.ntt.co.jp
To: arthur.ma...@internode.on.net
CC: linux-s...@vger.kernel.org, ballabio_da...@emc.com
References: 494e69f0.3060...@internode.on.net
On Mon, 22 Dec 2008 02:38:16 +1030
Arthur Marsh arthur.ma...@internode.on.net wrote:
I've recently installed Debian on a PII-266 machine with DPT2044W SCSI
controller.
Kernels 2.6.18-2.6.22 work fine, and kernels 2.6.23-2.6.27 lock up after
loading the eata module using modprobe, with the error:
modprobe exited with preempt_count 1
I've run a git bisection and have a few more passes to go, but suspect
the commit in the subject line,
[58e2a02eb18393e76a469580fedf7caec190eb5e] [SCSI] eata: convert to use
the data buffer accessors
to be the patch which triggers the problem.
I'm not a C programmer, let alone a kernel programmer, but can build and
check any suggested patches.
Is anyone successfully using the eata module since the data buffer
accessors patch?
Is anyone able to examine the code to see if anything was done wrong in
the data buffer accessors patch?
Sorry about the problem. Can you try this patch?
diff --git a/drivers/scsi/eata.c b/drivers/scsi/eata.c
index a73a6bb..976cdd5 100644
--- a/drivers/scsi/eata.c
+++ b/drivers/scsi/eata.c
@@ -1626,8 +1626,15 @@ static void map_dma(unsigned int i, struct
hostdata *ha)
cpp-sense_len = SCSI_SENSE_BUFFERSIZE;
- count = scsi_dma_map(SCpnt);
- BUG_ON(count 0);
+ if (!scsi_sg_count(SCpnt)) {
+ cpp-data_len = 0;
+ return;
+ }
+
+ count = pci_map_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+ pci_dir);
+ BUG_ON(!count);
+
scsi_for_each_sg(SCpnt, sg, count, k) {
cpp-sglist[k].address = H2DEV(sg_dma_address(sg));
cpp-sglist[k].num_bytes = H2DEV(sg_dma_len(sg));
@@ -1655,7 +1662,9 @@ static void unmap_dma(unsigned int i, struct
hostdata *ha)
pci_unmap_single(ha-pdev, DEV2H(cpp-sense_addr),
DEV2H(cpp-sense_len), PCI_DMA_FROMDEVICE);
- scsi_dma_unmap(SCpnt);
+ if (scsi_sg_count(SCpnt))
+ pci_unmap_sg(ha-pdev, scsi_sglist(SCpnt), scsi_sg_count(SCpnt),
+pci_dir);
if (!DEV2H(cpp-data_len))
pci_dir = PCI_DMA_BIDIRECTIONAL;
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: started git bisection
I've obtained adsl2+ service and re-partitioned my hard disk and have commenced a git bisection based on: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=summary 2.6.23test/.git/refs/bisect$ cat bad good* 4367388f04eea72e78347dc9b299698bf4275f92 7dcca30a32aadb0520417521b0c44f42d09fe05c As kernel compilation takes around 12 hours on this machine (PII-266, 384 MiB RAM), it may take some weeks to identify the change that broke DPT-2044W SCSI support on this machine. Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506835: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created
Arthur Marsh wrote, on 2008-12-08 19:58: I'm still trying to get to the source of the bug that prevents me from using a DPT2044W SCSI card that uses the eata module, and have narrowed down the working and non-working Debian kernel images to between linux-image-2.6.22-3-686 version 2.6.22-6.lenny1 which works, and linux-image-2.6.23-1-686 version 2.6.23-1 which fails. There appear to be a large number of changes between the two and I am unfamiliar with how to generate an intermediate kernel source with Debian changes and config to build and test. Thanks all for the comments on building kernel.org source under Debian. What I'm seeing is that I could do a git clone of a kernel.org 2.6.24 tree (once I get adsl2+ up and running and buy an extra hard disk) and build intermediate kernels (bisection), but surely there must be a way of generating intermediate *Debian* kernels to narrow down the source of the problem with running the DPT 2044W SCSI card under later kernels. Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: Info received ([Fwd: Re: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created])
I tried booting kernel 2.6.18-4-686 version 2.6.18.dfsg.1-12etch2 and was able to successfully modprobe eata and get the device files created. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created
Arthur Marsh wrote, on 28/11/08 20:33: The 2.6.18.dfsg.1-12etch2 kernel allowed me to modprobe eata and I received similar messages to those quoted above. The next newest kernel I can download is 2.6.24-etchnhalf.1-686. kernel 2.6.24-etchnhalf.1-686 had problems after modprobe eata Is there any site that has precompiled Debian kernels between 2.6.18.dfsg.1-1etch2 and 2.6.24-etchnhalf.1-686 ? Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: [Fwd: Re: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created]
Forwarded from Debian-user: Original Message Subject: Re: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created Date: Fri, 28 Nov 2008 17:02:35 +1030 From: Arthur Marsh [EMAIL PROTECTED] Newsgroups: gmane.linux.debian.user References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] lee wrote, on 2008-11-28 04:19: I've tried a kernel recompile from linux-source-2.6.27 and experienced the same problems. I get a kernel stack trace that ends in: note: scsi_scan0 [240] exited with preempt_count 1 Did you compile eata into the kernel or as a module? compiled into the kernel. and the machine locks up after the line: clock source tsc unstable http://www.google.com/search?hl=ensa=Xoi=spellresnum=1ct=resultcd=1q=%22clocksource+tsc+unstable%22spell=1 http://kerneltrap.org/node/8306 http://lkml.indiana.edu/hypermail/linux/kernel/0707.1/0621.html nothing much there, but thanks for the links. Any suggestions? No good ones ... You could put the SCSI controller into another slot and see what happens then --- I've had some SCSI controllers that won't work in one slot but in another, and I've seen network cards working just fine in one board but not in another. You could try older kernels. Yes, I'll try 2.6.18 (2.6.18.dfsg.1-12etch2 is the earliest Debian 2.6 kernel I can get hold of from my current archives) http://grox.net/doc/linux/howto-OLD-VERSIONS/Module-HOWTO-html/Module-HOWTO-6.html http://ubuntuforums.org/showthread.php?t=472253 https://bugs.launchpad.net/ubuntu/+bug/120426 http://www.google.com/search?hl=enq=modprobe+eatabtnG=Search The sysrescuecd 0.30 beta that found the SCSI controller and hard disk identified its kernel version as: Linux sysrescuecd 2.6.18.3-fd01 #1 Tue Dec 5 11:20:14 UTC 2006 i686 Pentium II (Klamath) GenuineIntel GNU/Linux SCSI-related lines from the dmesg output of the sysrescuecd were: SCSI subsystem initialized Loading iSCSI transport class v1.1-646.Loading Adaptec I2O RAID: Version 2.4 Build 5go scsi: fdomain Detection failed (no card) Emulex LightPulse Fibre Channel SCSI driver 8.1.9 Failed initialization of WD-7000 SCSI card! EATA0: wide SCSI support enabled, max_id 16, max_lun 8. EATA0: SCSI channel 0 enabled, host target ID 7. scsi2 : EATA/DMA 2.0x rev. 8.10.00 Type: Direct-Access ANSI SCSI revision: 02 scsi 2:0:6:0: cmds/lun 16, unsorted, no tags. ipr: IBM Power RAID SCSI Device Driver version: 2.1.3 (March 29, 2006) SCSI device sda: 8466688 512-byte hdwr sectors (4335 MB) SCSI device sda: drive cache: write back SCSI device sda: 8466688 512-byte hdwr sectors (4335 MB) SCSI device sda: drive cache: write back sd 2:0:6:0: Attached scsi disk sda sd 2:0:6:0: Attached scsi generic sg0 type 0 The current eata.c from 2.6.27 source on kernel-archive.buildserver.net has: eata.c: .name = EATA/DMA 2.0x rev. 8.10.00 so it appears that the eata.c file hasn't changed significantly since the working eata code built-in to the sysrescuecd kernel. I'll download the 2.6.18.dfsg.1-12etch2 kernel and try it. Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: Acknowledgement (linux-image-2.6.26-1-686: DPT SCSI controller module eata not automatically loaded, modprobe eata locks up)
I tried compiling the kernel with scsi and eata built-in and suffered the same problem. Error messages I saw included: note: scsi_scan0[240] exited with preempt_count 1 and the lock-up occurred after the message: clock source tsc unstable Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: linux-image-2.6.26-1-686: DPT SCSI controller module eata not automatically loaded, modprobe eata locks up
Package: linux-image-2.6.26-1-686 Version: 2.6.26-11~snapshot.12403 Severity: normal I have a DPT 2044W SCSI adaptor in this machine. Module eata does not get loaded automatically, and when I try to load it manually with modprobe I get a kernel stack trace then lock-up. lspci -vv 00:0a.0 SCSI storage controller: Adaptec (formerly DPT) SmartCache/Raid I-IV Controller (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 160 (1000ns min, 2000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 5 BIST result: 00 Region 0: I/O ports at e000 [size=32] Expansion ROM at ef00 [disabled] [size=32K] $ lsmod|grep -i scsi scsi_mod 131388 1 libata I can access the disk fine with sysrescuecd which has module eata built-in (does not use initrd). -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.27 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.13-5 Yet Another mkInitRD Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-16 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub-pc [grub] 1.96+20080724-12 GRand Unified Bootloader, version pn linux-doc-2.6.26none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502049: linux-source-2.6.27: image built with .config from image .deb needs zlib1g-dev
Package: linux-source-2.6.27 Version: 2.6.27~rc9-1~experimental.1~snapshot.12290 Severity: normal I tried to build the above source using the .config from linux-image-2.6.27-rc9-686 but hit errors due to zlib1g-dev not being installed. zlib1g-dev isn't recommended or even suggested by the source package, but should be. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.27-rc7 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.27 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.27 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-14 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.27 suggests: ii kernel-package11.007 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.6+20081004-1 developer's libraries and docs for ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded) -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problems with cirrusfb.ko
I've reported this to [EMAIL PROTECTED] but wondered if anyone has experienced any successes or failures in using framebuffer support with the Cirrus Logic GD 5465 [Laguna] VGA card. Arthur. Arthur Marsh wrote, on 2008-08-20 16:23: I'm running the Linux kernel 2.6.27-rc3. When trying to load cirrusfb.ko I received the following dmesg output: [ 6185.202286] CLgenfb: Unknown memory size! [ 6185.202286] RAM (1024 kB) at 0xe400, Cirrus Logic chipset on PCI bus [ 6185.202286] cirrusfb: Driver for Cirrus Logic based graphic boards, v2.0-pre2 [ 6185.206301] cirrusfb: Warning: Unknown board type [ 6185.206301] cirrusfb: This board has 1048576 bytes of DRAM memory [ 6185.206301] cirrusfb: Warning: Unknown board type [ 6185.210294] cirrusfb: This board has 1048576 bytes of DRAM memory [ 6185.210294] Console: switching to colour frame buffer device 80x30 [ 6257.515628] cirrusfb: Warning: Unknown board type [ 6257.519638] cirrusfb: This board has 1048576 bytes of DRAM memory This board is identified as: 01:00.0 VGA compatible controller: Cirrus Logic GD 5465 [Laguna] (rev 03) Subsystem: Cirrus Logic Device Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (4000ns min, 4000ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at e400 (32-bit, non-prefetchable) [size=32M] Region 1: Memory at e700 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at 2000 [disabled] [size=32K] Capabilities: [80] AGP version 1.0 Status: RQ=1 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=none Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Kernel driver in use: cirrusfb Kernel modules: cirrusfb I've tried enabling the 15-16 MB memory hole in the BIOS, but I'm still not getting anything visible when I switch away from vt7. Any suggestions? (I'd like to run a radeon 9200 or 9600 but have yet to find one). A few more pieces of information: Xorg reports: X.org VideoRAM: 4096 kByte The motherboard is an Intel 440LX, and the kernel is using the Debian config options, with 686 architecture and low latency desktop selected. Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481525: linux-image-2.6.25-2-686: task hald-addon-stor blocked for more than 120 seconds
Package: linux-image-2.6.25-2-686
Version: 2.6.25-5
Followup-For: Bug #481525
This sounds like the problem I've had with an MSI cd-rw drive going bad:
Jun 24 09:03:13 victoria kernel: [39238.824892] INFO: task
hald-addon-stor:3675 blocked for more than 120 seconds.
Jun 24 09:03:13 victoria kernel: [39238.824941] echo 0
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Jun 24 09:03:13 victoria kernel: [39238.824965] hald-addon-st D e604b3ed
0 3675 3619
Jun 24 09:03:13 victoria kernel: [39238.824995]d22019c0 0082
000c e604b3ed 01b1 d2201b4c c128b0e0
Jun 24 09:03:13 victoria kernel: [39238.825048] d48a15ce
0004a099 d48382ac 0088 d2f83d08
Jun 24 09:03:13 victoria kernel: [39238.825099]7fff 7fff
d2f83c74 0002 c02bcd28 d4838260 0092
Jun 24 09:03:13 victoria kernel: [39238.825149] Call Trace:
Jun 24 09:03:13 victoria kernel: [39238.825261] [d48a15ce]
cdrom_start_packet_command+0xb6/0xbd [ide_cd_mod]
Jun 24 09:03:13 victoria kernel: [39238.825390] [c02bcd28]
schedule_timeout+0x13/0x86
Jun 24 09:03:13 victoria kernel: [39238.825474] [c0180c61]
do_sys_poll+0x267/0x2e7
Jun 24 09:03:13 victoria kernel: [39238.825567] [c02bc441]
wait_for_common+0xd3/0x140
Jun 24 09:03:13 victoria kernel: [39238.825616] [c011c52f]
default_wake_function+0x0/0x8
Jun 24 09:03:13 victoria kernel: [39238.825696] [d4826ef2]
ide_do_drive_cmd+0xd6/0xf2 [ide_core]
Jun 24 09:03:13 victoria kernel: [39238.825943] [d48a1c65]
ide_cd_queue_pc+0x35/0xb4 [ide_cd_mod]
Jun 24 09:03:13 victoria kernel: [39238.825992] [c0110070]
lapic_watchdog_init+0x71/0xfc
Jun 24 09:03:13 victoria kernel: [39238.826059] [c02bcb67]
schedule+0x64c/0x66d
Jun 24 09:03:13 victoria kernel: [39238.826159] [d48a1f03]
cdrom_check_status+0x5a/0x65 [ide_cd_mod]
Jun 24 09:03:13 victoria kernel: [39238.826428] [c01d698f]
blk_end_sync_rq+0x0/0x25
Jun 24 09:03:13 victoria kernel: [39238.826518] [d48a38df]
ide_cdrom_check_media_change_real+0x1b/0x36 [ide_cd_mod]
Jun 24 09:03:13 victoria kernel: [39238.826582] [d489806e]
media_changed+0x40/0x6e [cdrom]
Jun 24 09:03:13 victoria kernel: [39238.826667] [c0195d7c]
check_disk_change+0x13/0x57
Jun 24 09:03:13 victoria kernel: [39238.826716] [d489bf2a]
cdrom_open+0x882/0x8f8 [cdrom]
Jun 24 09:03:13 victoria kernel: [39238.826777] [c017c1f3]
do_lookup+0x53/0x145
Jun 24 09:03:13 victoria kernel: [39238.826838] [c01843ea]
dput+0x15/0xbb
Jun 24 09:03:13 victoria kernel: [39238.826876] [c017e1a9]
__link_path_walk+0xa5b/0xb67
Jun 24 09:03:13 victoria kernel: [39238.826930] [c01de860]
kobject_get+0xf/0x13
Jun 24 09:03:13 victoria kernel: [39238.826993] [c01d860d]
get_disk+0x33/0x49
Jun 24 09:03:13 victoria kernel: [39238.827041] [c01d862a]
exact_lock+0x7/0xd
Jun 24 09:03:13 victoria kernel: [39238.827073] [c0241e22]
kobj_lookup+0xe4/0x10e
Jun 24 09:03:13 victoria kernel: [39238.827144] [d48a14f1]
idecd_open+0x44/0x6b [ide_cd_mod]
Jun 24 09:03:13 victoria kernel: [39238.827212] [c019637b]
do_open+0xa1/0x278
Jun 24 09:03:13 victoria kernel: [39238.827281] [c01966cd]
blkdev_open+0x0/0x4d
Jun 24 09:03:13 victoria kernel: [39238.827309] [c01966f2]
blkdev_open+0x25/0x4d
Jun 24 09:03:13 victoria kernel: [39238.827353] [c0174aeb]
__dentry_open+0x10d/0x1fc
Jun 24 09:03:13 victoria kernel: [39238.827431] [c0174bf6]
nameidata_to_filp+0x1c/0x2c
Jun 24 09:03:13 victoria kernel: [39238.827484] [c017f38a]
do_filp_open+0x34f/0x6b0
Jun 24 09:03:13 victoria kernel: [39238.827571] [d4899322]
cdrom_release+0x179/0x1ae [cdrom]
Jun 24 09:03:13 victoria kernel: [39238.827628] [d4a45183]
snd_emu10k1_playback_pointer+0x2a/0x52 [snd_emu10k1]
Jun 24 09:03:13 victoria kernel: [39238.827806] [d4a4724d]
snd_emu10k1_voice_intr_ack+0x15/0x52 [snd_emu10k1]
Jun 24 09:03:13 victoria kernel: [39238.827987] [c0174908]
do_sys_open+0x40/0xb0
Jun 24 09:03:13 victoria kernel: [39238.828051] [c01749bc]
sys_open+0x1e/0x23
Jun 24 09:03:13 victoria kernel: [39238.828102] [c0105863]
sysenter_past_esp+0x78/0xb1
This problem happened with a large number of test kernels as well (can't
be sure if any recent kernels *didn't* show this problem).
It would be nice if the kernel could handle cd drives going bad more
gracefully. This problem also locked up dosbox.
After changing to a known good pioneer dvd-rw drive, I started getting
the following errors when playing an audio cd:
Jun 24 22:51:57 victoria kernel: [ 7076.365804] hdc: command error:
status=0x51 { DriveReady SeekComplete Error }
Jun 24 22:51:57 victoria kernel: [ 7076.365876] hdc: command error:
error=0x50 { LastFailedSense=0x05 }
Jun 24 22:51:57 victoria kernel: [ 7076.365909] ide: failed opcode was:
unknown
Jun 24 22:51:57 victoria kernel: [ 7076.366282] ATAPI device hdc:
Jun 24 22:51:57 victoria kernel: [ 7076.366301] Error: Illegal request
-- (Sense key=0x05)
Jun 24 22:51:57 victoria kernel: [ 7076.366335] Illegal mode for this
Bug#472698: initramfs-tools: more serious than important
Package: initramfs-tools Version: 0.91e Followup-For: Bug #472698 Thanks to the previous poster I was able to recover a system that wouldn't boot. My method of recovery was to use the Etch installation CD in recovergui mode, pick the correct root filesystem, chroot into it and run aptitude to downgrade busybox to the version in testing, then run: update-initramfs -k all -u Without the previous poster's information I would not have been able to recover the machine that failed to reboot. -- Package-specific info: -- /proc/cmdline root=/dev/hda5 ro noisapnp -- /proc/filesystems ext3 fuseblk vfat -- lsmod Module Size Used by binfmt_misc11400 1 ppdev 8452 0 lp 10828 0 apm20860 2 microcode 10832 0 ipv6 251612 28 cifs 201192 2 nls_utf82080 5 nls_cp437 5792 3 vfat 12320 3 fat46784 1 vfat nls_base7684 5 cifs,nls_utf8,nls_cp437,vfat,fat fuse 44860 1 dm_snapshot17636 0 dm_mirror 26436 0 dm_mod 57236 2 dm_snapshot,dm_mirror snd_emu10k1_synth 6848 0 snd_emux_synth 31104 1 snd_emu10k1_synth snd_seq_virmidi 7264 1 snd_emux_synth snd_seq_midi_emul 5888 1 snd_emux_synth snd_emu10k1 123844 2 snd_emu10k1_synth snd_seq_dummy 3748 0 snd_seq_oss29500 0 snd_seq_midi8032 0 snd_seq_midi_event 6976 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi snd_seq46884 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_rawmidi22944 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi firmware_class 9472 2 microcode,snd_emu10k1 snd_ac97_codec 91876 1 snd_emu10k1 ac97_bus1920 1 snd_ac97_codec snd_pcm_oss38464 0 snd_mixer_oss 15520 1 snd_pcm_oss snd_pcm68900 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss snd_seq_device 7660 8 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi snd_timer 22056 3 snd_emu10k1,snd_seq,snd_pcm snd_page_alloc 10024 2 snd_emu10k1,snd_pcm snd_util_mem4608 2 snd_emux_synth,snd_emu10k1 snd_hwdep 9124 2 snd_emux_synth,snd_emu10k1 parport_pc 25556 1 parport34548 3 ppdev,lp,parport_pc snd50072 15 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_seq_oss,snd_seq,snd_rawmidi,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep emu10k1_gp 3648 0 i2c_piix4 8204 0 soundcore 8008 1 snd i2c_core 22932 1 i2c_piix4 gameport 14636 2 emu10k1_gp shpchp 30004 0 pci_hotplug28068 1 shpchp intel_agp 24924 1 agpgart32276 1 intel_agp pcspkr 3072 0 rtc13856 0 evdev 11648 1 ext3 120904 2 jbd46964 1 ext3 mbcache 8452 1 ext3 raid1 23104 1 md_mod 75644 2 raid1 usbhid 40164 0 hid35724 1 usbhid ff_memless 5416 1 usbhid ide_cd_mod 32740 1 cdrom 31900 1 ide_cd_mod ide_disk 13792 10 ata_generic 7908 0 libata143584 1 ata_generic scsi_mod 140212 1 libata ohci_hcd 21508 0 ehci_hcd 31980 0 8139cp 21440 0 uhci_hcd 22544 0 floppy 53172 0 piix7048 0 [permanent] 8139too25056 0 mii 5280 2 8139cp,8139too usbcore 130672 5 usbhid,ohci_hcd,ehci_hcd,uhci_hcd ide_pci_generic 4196 0 [permanent] ide_core 101240 4 ide_cd_mod,ide_disk,piix,ide_pci_generic -- /etc/kernel-img.conf # Do not create symbolic links in / do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = /usr/sbin/update-grub postrm_hook = /usr/sbin/update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25-rc6 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
maximilian attems wrote, on 2008-01-09 06:32: did you try 2.6.24-rc7 from trunk, see apt lines - http://wiki.debian.org/DebianKernel No. I am about to download it and try to compile it with gcc-4.3 please report back on it, by default we currently use gcc-4.1 Same error: CC lib/div64.o CC lib/sort.o CC lib/parser.o CC lib/halfmd4.o CC lib/debug_locks.o CC lib/random32.o CC lib/bust_spinlocks.o CC lib/hexdump.o CC lib/kasprintf.o CC lib/bitmap.o CC lib/iomap.o CC lib/iomap_copy.o CC lib/devres.o CC lib/check_signature.o CC lib/hweight.o CC lib/kernel_lock.o CC lib/plist.o CC lib/smp_processor_id.o CC lib/bitrev.o HOSTCC lib/gen_crc32table GEN lib/crc32table.h CC lib/crc32.o CC lib/genalloc.o CC lib/textsearch.o CC lib/percpu_counter.o CC lib/audit.o LD lib/built-in.o CC lib/argv_split.o CC lib/bug.o CC lib/cmdline.o CC lib/cpumask.o CC lib/ctype.o CC lib/dec_and_lock.o CC lib/dump_stack.o CC lib/extable.o CC lib/idr.o CC lib/int_sqrt.o CC lib/ioremap.o CC lib/irq_regs.o CC lib/klist.o CC lib/kobject.o CC lib/kobject_uevent.o CC lib/kref.o CC lib/prio_heap.o CC lib/prio_tree.o CC lib/proportions.o CC lib/radix-tree.o CC lib/rbtree.o CC lib/reciprocal_div.o CC lib/rwsem.o CC lib/semaphore-sleepers.o CC lib/sha1.o CC lib/string.o CC lib/vsprintf.o AR lib/lib.a LD lib/reed_solomon/built-in.o LD lib/zlib_deflate/built-in.o LD lib/zlib_inflate/built-in.o CC arch/x86/lib/msr-on-cpu.o LD arch/x86/lib/built-in.o CC arch/x86/lib/bitops_32.o AS arch/x86/lib/checksum_32.o CC arch/x86/lib/delay_32.o AS arch/x86/lib/getuser_32.o CC arch/x86/lib/memcpy_32.o AS arch/x86/lib/putuser_32.o AS arch/x86/lib/semaphore_32.o CC arch/x86/lib/string_32.o CC arch/x86/lib/strstr_32.o CC arch/x86/lib/usercopy_32.o AR arch/x86/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 kernel/built-in.o: In function `getnstimeofday': (.text+0x1d9f9): undefined reference to `__umoddi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1dab1): undefined reference to `__udivdi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1dad4): undefined reference to `__umoddi3' kernel/built-in.o: In function `timekeeping_resume': timekeeping.c:(.text+0x1dbcc): undefined reference to `__udivdi3' timekeeping.c:(.text+0x1dbef): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2c8): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2eb): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e387): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e3b1): undefined reference to `__umoddi3' make[1]: *** [.tmp_vmlinux1] Error 1 make[1]: Leaving directory `/usr/src/linux-source-2.6.24-rc7' make: *** [debian/stamp-build-kernel] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
Bastian Blank wrote, on 09/01/08 21:32: On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote: When compiling for Athlon using gcc-4.3: gcc-4.3 --version gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk revision 131316] Does Linux upstream already bless gcc 4.3? I doubt. kernel/built-in.o: In function `getnstimeofday': (.text+0x1d927): undefined reference to `__umoddi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1d9e9): undefined reference to `__udivdi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1da0c): undefined reference to `__umoddi3' kernel/built-in.o: In function `timekeeping_resume': timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3' timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e214): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e237): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2d3): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2fd): undefined reference to `__umoddi3' New references into libgcc, which is not available in the kernel. __umoddi3: modulo operation on unsigned double wide integer or so, with overflow checking. Bastian Would the workaround suggested at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044#c28 You need to add -fno-tree-scev-cprop to the KBUILD_CFLAGS work when applied the particular source files in the kernel where the error is occurring? Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
Package: linux-source-2.6.23 Version: 2.6.23-3~snapshot.10051 Severity: normal When compiling for Athlon using gcc-4.3: gcc-4.3 --version gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk revision 131316] and make-kpkg --initrd linux-image modules-image compilation proceeded fine up until: CC arch/i386/lib/msr-on-cpu.o LD arch/i386/lib/built-in.o CC arch/i386/lib/bitops.o AS arch/i386/lib/checksum.o CC arch/i386/lib/delay.o AS arch/i386/lib/getuser.o CC arch/i386/lib/memcpy.o CC arch/i386/lib/mmx.o AS arch/i386/lib/putuser.o AS arch/i386/lib/semaphore.o CC arch/i386/lib/string.o CC arch/i386/lib/strstr.o CC arch/i386/lib/usercopy.o AR arch/i386/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 kernel/built-in.o: In function `getnstimeofday': (.text+0x1d927): undefined reference to `__umoddi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1d9e9): undefined reference to `__udivdi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1da0c): undefined reference to `__umoddi3' kernel/built-in.o: In function `timekeeping_resume': timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3' timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e214): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e237): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2d3): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2fd): undefined reference to `__umoddi3' make[1]: *** [.tmp_vmlinux1] Error 1 make[1]: Leaving directory `/usr/src/linux-source-2.6.23' make: *** [debian/stamp-build-kernel] Error 2 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.23 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.23 depends on: ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina ii bzip2 1.0.4-2 high-quality block-sorting file co Versions of packages linux-source-2.6.23 recommends: ii gcc 4:4.2.2-1 The GNU C compiler ii libc6-dev [libc-dev] 2.7-5 GNU C Library: Development Librari ii make 3.81-3 The GNU version of the make util -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
maximilian attems wrote, on 2008-01-09 03:06: On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote: Package: linux-source-2.6.23 Version: 2.6.23-3~snapshot.10051 Severity: normal grrr reportbug-ng misses quite a lot of important info, thinking of automaticaly dropping such, please use reportbug until reportbug-ng is fixed to use the bug scripts. Hi, I was using reportbug and have not installed reportbug-ng. When compiling for Athlon using gcc-4.3: gcc-4.3 --version gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk revision 131316] and make-kpkg --initrd linux-image modules-image compilation proceeded fine up until: CC arch/i386/lib/msr-on-cpu.o LD arch/i386/lib/built-in.o CC arch/i386/lib/bitops.o AS arch/i386/lib/checksum.o CC arch/i386/lib/delay.o AS arch/i386/lib/getuser.o CC arch/i386/lib/memcpy.o CC arch/i386/lib/mmx.o AS arch/i386/lib/putuser.o AS arch/i386/lib/semaphore.o CC arch/i386/lib/string.o CC arch/i386/lib/strstr.o CC arch/i386/lib/usercopy.o AR arch/i386/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 kernel/built-in.o: In function `getnstimeofday': (.text+0x1d927): undefined reference to `__umoddi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1d9e9): undefined reference to `__udivdi3' kernel/built-in.o: In function `do_gettimeofday': (.text+0x1da0c): undefined reference to `__umoddi3' kernel/built-in.o: In function `timekeeping_resume': timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3' timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e214): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e237): undefined reference to `__umoddi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2d3): undefined reference to `__udivdi3' kernel/built-in.o: In function `update_wall_time': (.text+0x1e2fd): undefined reference to `__umoddi3' make[1]: *** [.tmp_vmlinux1] Error 1 make[1]: Leaving directory `/usr/src/linux-source-2.6.23' make: *** [debian/stamp-build-kernel] Error 2 what arch, what .config? i386 architecture and .config based on linux-image-2.6.23-1-686 with the following changes: selected processor type to Athlon set pre-emption model to low latency desktop enabled pre-empting the big kernel lock enabled default security capabilities as a module The same error happened when the selected processor type was Pentium II (pre-coppermine). did you try 2.6.24-rc7 from trunk, see apt lines - http://wiki.debian.org/DebianKernel No. I am about to download it and try to compile it with gcc-4.3 Regards, Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394974: linux-source-2.6.18: had to recompile modules when upgrading from 2.6.18-5 to 2.6.18-6
Package: linux-source-2.6.18 Version: 2.6.18-6 Followup-For: Bug #394974 As I've read in the bug reports, it appears that from time to time module compatibility breaks with minor version upgrades. In my case when I tried to load ALSA and realtime-lsm modules compiled against 2.6.18-5 source on a hand-compiled kernel based on 2.6.18-6 source, I received errors of the form: snd: disagrees about version of symbol struct_module realtime: disagrees about version of symbol struct_module It would be good to have warning at least in /usr/share/doc/linux-source-2.6.18 when modules would need to be recompiled, and hopefully some proper versioning would take place so that one can have multiple kernels installed that can work with separately packaged modules. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-source-2.6.18 depends on: ii binutils 2.17-3 The GNU assembler, linker and bina ii bzip2 1.0.3-6high-quality block-sorting file co Versions of packages linux-source-2.6.18 recommends: ii gcc 4:4.1.1-13 The GNU C compiler ii libc6-dev [libc-dev] 2.3.6.ds1-8 GNU C Library: Development Librari ii make 3.81-3 The GNU version of the make util -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382740: /usr/sbin/mkinitramfs: line 206: [: /etc/initramfs-tools/conf.d/resume: binary operator expected
Package: initramfs-tools Version: 0.73d Severity: important When installing initramfs-tools I get: Setting up initramfs-tools (0.73d) ... update-initramfs: Generating /boot/initrd.img-2.6.17 /usr/sbin/mkinitramfs: line 206: [: /etc/initramfs-tools/conf.d/resume: binary operator expected I: mdadm: RAID support installed to mount all RAID arrays during boot. I: mdadm: use `dpkg-reconfigure -plow mdadm` to change this. The script does appear to successfully make a new initramfs -- Package-specific info: -- /proc/cmdline root=/dev/hda5 ro noisapnp -- /proc/filesystems cramfs ext3 vfat -- lsmod Module Size Used by iptable_filter 3072 0 ip_tables 13380 1 iptable_filter x_tables 13508 1 ip_tables binfmt_misc11304 1 ppdev 8516 0 lp 10948 0 apm20176 1 realtime3976 0 commoncap 6944 1 realtime ipv6 223648 20 cifs 185664 2 nls_iso8859_1 4224 1 nls_utf82176 4 nls_cp437 5888 3 vfat 11936 3 fat46780 1 vfat dm_snapshot15716 0 dm_mirror 19504 0 dm_mod 50712 2 dm_snapshot,dm_mirror snd_emu10k1_synth 6912 0 snd_emux_synth 31360 1 snd_emu10k1_synth snd_seq_virmidi 7296 1 snd_emux_synth snd_seq_midi_emul 5920 1 snd_emux_synth snd_seq_dummy 3940 0 snd_seq_oss30400 0 snd_seq_midi8128 0 snd_seq_midi_event 7008 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi shpchp 34504 0 pci_hotplug27908 1 shpchp snd_seq47536 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event tsdev 7424 0 mousedev 10824 1 snd_emu10k1 103524 2 snd_emu10k1_synth snd_rawmidi23008 3 snd_seq_virmidi,snd_seq_midi,snd_emu10k1 snd_ac97_codec 83232 1 snd_emu10k1 snd_ac97_bus2400 1 snd_ac97_codec snd_pcm_oss36800 0 snd_mixer_oss 16704 1 snd_pcm_oss snd_pcm75652 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss snd_seq_device 7916 8 snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_emu10k1,snd_rawmidi snd_timer 21316 3 snd_seq,snd_emu10k1,snd_pcm snd_page_alloc 9544 2 snd_emu10k1,snd_pcm snd_util_mem4608 2 snd_emux_synth,snd_emu10k1 snd_hwdep 8996 2 snd_emux_synth,snd_emu10k1 snd50148 16 snd_emux_synth,snd_seq_virmidi,snd_seq_dummy,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep psmouse34728 0 parport_pc 32324 1 parport33640 3 ppdev,lp,parport_pc emu10k1_gp 3840 0 gameport 14728 2 emu10k1_gp serio_raw 6596 0 evdev 9088 1 intel_agp 21148 1 agpgart30028 1 intel_agp i2c_piix4 8560 0 i2c_core 19968 1 i2c_piix4 pcspkr 3072 0 8250_pnp8736 0 rtc12564 0 floppy 54596 0 soundcore 9600 1 snd ext3 119080 2 jbd53044 1 ext3 mbcache 8452 1 ext3 raid1 21216 1 md_mod 69748 2 raid1 ide_cd 35712 0 cdrom 32544 1 ide_cd ide_disk 15200 10 generic 4452 0 [permanent] usbhid 35840 0 piix9508 0 [permanent] ohci_hcd 18564 0 ehci_hcd 28296 0 uhci_hcd 20680 0 ide_core 112264 4 ide_cd,ide_disk,generic,piix usbcore 112544 5 usbhid,ohci_hcd,ehci_hcd,uhci_hcd 8139cp 20832 0 8139too25088 0 mii 5312 2 8139cp,8139too processor 25736 0 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages initramfs-tools depends on: ii busybox 1:1.1.3-2 Tiny utilities for small and embed ii cpio 2.6-17 GNU cpio -- a program to manage ar ii klibc-utils 1.4.19-1 small statically-linked utilities ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii udev 0.093-1/dev/ and hotplug
Bug#376699: linux-image-2.6.17-1-686: locks up when playing MIDI file to EMU10K1 soundcard and hard disk activity
Package: linux-image-2.6.17-1-686 Version: 2.6.17-2 Severity: important Please refer to: [Pkg-alsa-devel] Bug#376382: ALSA MIDI playback lock-up on kernel 2.6.17-686, not on kernel 2.6.16-2-686 The 2.6.17-1-686 has lockups when I attempt to play MIDI files to a SoundBlaster Live! 5.1 model 0220 PCI sound card using its onboard MIDI synth and there is significant hard disk activity. I have not had this problem since reverting to the 2.6.16-2-686 kernel. I'm running a PII-266 with 256 MiB of RAM. lspci reports: $ lspci 00:00.0 Host bridge: Intel Corporation 440LX/EX - 82443LX/EX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440LX/EX - 82443LX/EX AGP bridge (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01) 00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) 00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) 00:0a.0 USB Controller: NEC Corporation USB (rev 43) 00:0a.1 USB Controller: NEC Corporation USB (rev 43) 00:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 01:00.0 VGA compatible controller: Cirrus Logic GD 5465 [Laguna] (rev 03) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-1-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-15 Yet Another mkInitRD Versions of packages linux-image-2.6.17-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: false linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/kimage-is-a-directory: linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true * linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/depmod-error-initrd-2.6.17-1-686: false linux-image-2.6.17-1-686/preinst/abort-install-2.6.17-1-686: linux-image-2.6.17-1-686/prerm/would-invalidate-boot-loader-2.6.17-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376699: linux-image-2.6.17-1-686: locks up when playing MIDI file to EMU10K1 soundcard and hard disk activity
maximilian attems wrote: On Tue, Jul 04, 2006 at 08:51:54PM +0930, Arthur Marsh wrote: Severity: important over exagerated. ok, but is the only thing that has locked up Debian for me (-: Please refer to: [Pkg-alsa-devel] Bug#376382: ALSA MIDI playback lock-up on kernel 2.6.17-686, not on kernel 2.6.16-2-686 The 2.6.17-1-686 has lockups when I attempt to play MIDI files to a SoundBlaster Live! 5.1 model 0220 PCI sound card using its onboard MIDI synth and there is significant hard disk activity. I have not had this problem since reverting to the 2.6.16-2-686 kernel. are you sure that 2.6.16-2-686 works? it was the first kernel with CONFIG_HZ_250 previous had 1000, i would suspect the difference to be between 2.6.16-2-686 and 2.6.16-1-686 I'm running a PII-266 with 256 MiB of RAM. Yes 2.6.16-2-686 works, 2.6.17-1-686 locks up. Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376699: FIXED Bug#376699: linux-image-2.6.17-1-686: locks up when playing MIDI file to EMU10K1 soundcard and hard disk activity
By recompiling and installing the ALSA modules with the alsa-timer-irqsave-patch available at http://www.lxtec.de/debarchiv for kernel 2.6.17-1-686, I no longer have problems with MIDI playback on my SoundBlaster Live! 5.1 model 0220 sound card under kernel 2.6.17-1-686. Regards, Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#375492: linux-image-2.6.17-1-686: bug #374145 still applies (module lp no installed automatically after parallel port detected)
Package: linux-image-2.6.17-1-686 Version: 2.6.17-1 Severity: normal I still have to manually add lp to /etc/modules for /dev/lp0 to be created, even though the parallel port is detected, previously reported for linux-image-2.6.16-2-686 as bug #374145. Regards... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-1-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-14 Yet Another mkInitRD Versions of packages linux-image-2.6.17-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: false linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/kimage-is-a-directory: linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/depmod-error-initrd-2.6.17-1-686: false linux-image-2.6.17-1-686/preinst/abort-install-2.6.17-1-686: linux-image-2.6.17-1-686/prerm/would-invalidate-boot-loader-2.6.17-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374145: linux-image-2.6.16-2-686: parallel port detected but not reported until much later
Package: linux-image-2.6.16-2-686 Version: 2.6.16-14 Severity: normal Recently I've run into the problem of the notification of the parallel port's existance not being passed onto udev until around half an hour after boot-up: Jun 17 22:24:05 localhost kernel: parport: PnPBIOS parport detected. Jun 17 22:24:05 localhost kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA] Jun 17 22:24:05 localhost kernel: parport0: Printer, Canon BJC-3000 Jun 17 22:49:46 localhost kernel: lp0: using parport0 (interrupt-driven). /dev/lp0 doesn't get created until the time of the last message listed above, and the printer isn't accessible to CUPS until /dev/lp0 is created, so printing doesn't work until long after boot-up. I've tried a few different BIOS settings for the parallel port and the problem has stayed the same. Apart from buying a parallel port card, are there any ways to pinpoint the problem? Regards, Arthur Marsh. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-14 Yet Another mkInitRD Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374145: linux-image-2.6.16-2-686: lp in /etc/modules successful workaround
Package: linux-image-2.6.16-2-686 Version: 2.6.16-14 Followup-For: Bug #374145 After adding the line: lp to /etc/modules, a reboot enabled /dev/lp0 to be just after printer detection: Jun 18 00:00:54 localhost kernel: parport: PnPBIOS parport detected. Jun 18 00:00:54 localhost kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA] Jun 18 00:00:54 localhost kernel: parport0: Printer, Canon BJC-3000 Jun 18 00:00:54 localhost kernel: lp0: using parport0 (interrupt-driven). crw-rw 1 root lp 6, 0 2006-06-18 00:00 /dev/lp0 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-14 Yet Another mkInitRD Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345934: linux-image-2.6.15-1-686: postinstal failure observed here also
Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Followup-For: Bug #345934 I also noted: -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.15-1-686.postinst line 579. The new kernel is installed and usable, but the package remains listed as partly installed and attempts to complete installation each time I add or update packages with aptitude. Regards, Arthur. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.15-1-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.5-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: linux-image-2.6.15-1-686/preinst/overwriting-modules-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/depmod-error-initrd-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/bootloader-error-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/bootloader-test-error-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-686/preinst/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/abort-install-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/abort-overwrite-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/lilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-dir-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/already-running-this-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/initrd-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/depmod-error-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/create-kimage-link-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/removing-running-kernel-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343048: linux-image-2.6.14-2-686: fails to boot
Package: linux-image-2.6.14-2-686 Version: 2.6.14-5 Followup-For: Bug #343048 Same thing happens here. I also had problems trying to install loop-aes at the same time as upgrading from 2.6.14-4 to 2.6.14-5. The installation went ahead if I upgraded the kernel in aptitude first then the loop-aes stuff. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.14-2-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-1 Yet Another mkInitRD Versions of packages linux-image-2.6.14-2-686 recommends: ii libc6-i6862.3.5-8.1 GNU C Library: Shared libraries [i -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336561: linux-image-2.6.14-1-686: CONFIG_SECURITY_CAPABILITIES=y in 2.6.14 prevents realtime-lsm being used with a stock kernel
Package: linux-image-2.6.14-1-686 Version: 2.6.14-1 Severity: normal Tags: patch Hi, I tried to build the realtime-lsm against 2.6.14 and it complained that it couldn't do so unless CONFIG_SECURITY_CAPABILITIES was built into the kernel as a module. Fix: CONFIG_SECURITY_CAPABILITIES=m I'm just about to try installing the realtime-lsm against a kernel rebuilt with CONFIG_SECURITY_CAPABILITIES=m Regards, Arthur. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.14-1-686 depends on: ii module-init-tools 3.2-pre9-3 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-9 Yet Another mkInitRD linux-image-2.6.14-1-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336561: linux-image-2.6.14-1-686: CONFIG_SECURITY_CAPABILITIES=y in 2.6.14 prevents realtime-lsm being used with a stock kernel
OK, as it turned out, realtime.ko built against the 2.6.14 kernel source wouldn't load on 2.6.14 even after 2.6.14 had been rebuilt with CONFIG_SECURITY_CAPABILITIES=M. The motivation for attempting it in the first place was to give xmms the ability to run in realtime mode (and xmms runs here fine without realtime). It's not a big problem, just that I hadn't seen the discussion on the change to CONFIG_SECURITY_CAPABILITIES. Regards, Arthur. Sven Luther wrote: reassign 336561 realtime-lsm thanks On Mon, Oct 31, 2005 at 06:32:58PM +1030, Arthur Marsh wrote: Package: linux-image-2.6.14-1-686 Version: 2.6.14-1 Severity: normal Tags: patch Hi, I tried to build the realtime-lsm against 2.6.14 and it complained that it couldn't do so unless CONFIG_SECURITY_CAPABILITIES was built into the kernel as a module. Fix: CONFIG_SECURITY_CAPABILITIES=m I'm just about to try installing the realtime-lsm against a kernel rebuilt with CONFIG_SECURITY_CAPABILITIES=m This has been discussed in the past, but it seems there are security issues why building CONFIG_SECURITY_CAPABILITIES as modules is not a good idea. Also, it seems that realtime-lsm is rather broken if it really needs a modular CONFIG_SECURITY_CAPABILITIES, and should be fixed, reassigning to it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303970: kernel-image-2.6.11-1-386: in /lib/modules, source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386
Package: kernel-image-2.6.11-1-386 Version: 2.6.11-2 Severity: normal /lib/modules/2.6.11-1-386 as installed has the following symbolic link: source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.11-1-386 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
