Bug#488466: linux-image-2.6-686: Post-install script creates bad /boot/grub/menu.lst hd entries
Package: linux-image-2.6-686 Version: 2.6.24+13 Severity: important After an upgrade to the latest kernel and restarting the computer Grub failed to boot. It turned out that the menu entries in /boot/grub/menu.lst were pointing to an invalid disk, that is, I got root (hd1,0) instead of the correct root (hd0,0) After editing the boot command Linux booted fine. My system has the following disk configuration: /dev/sda (SATA HDD): /dev/sda1 / ext3 /dev/sda5 swap /dev/hda (IDE CD-ROM) /dev/fd0 Floppy -- 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=bg_BG, LC_CTYPE=bg_BG 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-7 Linux 2.6.24 image on PPro/Celeron linux-image-2.6-686 recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488475: linux-image-2.6.25-2-amd64: r8196 driver having problems with GA-MA78GM-S2H motherboard
Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-5 Severity: normal I recently bought a gigabyte GA-MA78GM-S2H motherboard, comes with a Realtek 8111C chip nic. I have installed debian (amd64) and I notice when I use ifconfig eth0 Link encap:Ethernet HWaddr 00:1f:d0:59:14:a1 inet addr:192.168.11.14 Bcast:192.168.11.255 Mask:255.255.255.0 inet6 addr: fe80::21f:d0ff:fe59:14a1/64 Scope:Link inet6 addr: 2002:3cf1:f856:11::14/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3402942 errors:0 dropped:14350521468 overruns:0 frame:0 TX packets:5908346 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:366689574 (349.7 MiB) TX bytes:8389785209 (7.8 GiB) Interrupt:253 Base address:0x4000 there is a large amount of dropped, I have checked this on a newly booted machine and the number seems to be in the 1B mark. IPv4 seems to be working okay. But I use radvd, ipv6 autoconfig to configure ipv6. icmpv6 router advertisements don't seem to be making it to the card. I see noting then I run tcpdump lspci -s 0:2:0.0 -vx 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: Giga-byte Technology Device e000 Flags: bus master, fast devsel, latency 0, IRQ 1277 I/O ports at de00 [size=256] Memory at fdaff000 (64-bit, prefetchable) [size=4K] Memory at fdae (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at fda0 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2 Capabilities: [d0] Vital Product Data ? Capabilities: [100] Advanced Error Reporting ? Capabilities: [140] Virtual Channel ? Capabilities: [160] Device Serial Number 78-56-34-12-78-56-34-12 Kernel driver in use: r8169 Kernel modules: r8169 00: ec 10 68 81 07 04 10 00 02 00 00 02 10 00 00 00 10: 01 de 00 00 00 00 00 00 0c f0 af fd 00 00 00 00 20: 0c 00 ae fd 00 00 00 00 00 00 00 00 58 14 00 e0 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 00 00 there seems to be some talk on this thread http://ubuntuforums.org/showthread.php?t=671614 of a r8168 module, which I can't find in the source tree ? Alex -- Package-specific info: ** Version: Linux version 2.6.25-2-amd64 (Debian 2.6.25-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Thu Jun 12 15:38:32 UTC 2008 ** Command line: root=/dev/md1 ro ** Not tainted ** Kernel log: [8.900625] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] [9.089804] kjournald starting. Commit interval 5 seconds [9.089804] EXT3-fs: mounted filesystem with ordered data mode. [ 10.554413] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 10.577719] shpchp: HPC vendor_id 1022 device_id 9602 ss_vid 0 ss_did 0 [ 10.577759] shpchp: shpc_init: cannot reserve MMIO region [ 10.577819] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 10.589313] input: Power Button (FF) as /class/input/input2 [ 10.642091] ACPI: Power Button (FF) [PWRF] [ 10.642195] input: Power Button (CM) as /class/input/input3 [ 10.706101] ACPI: Power Button (CM) [PWRB] [ 10.706216] ACPI: WMI: Mapper loaded [ 10.915700] piix4_smbus :00:14.0: Found :00:14.0 device [ 10.947844] ACPI: PCI Interrupt :00:14.2[A] - GSI 16 (level, low) - IRQ 16 [ 10.911489] input: PC Speaker as /class/input/input4 [ 10.981415] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS... [ 11.013163] ACPI: PCI Interrupt :01:05.1[B] - GSI 19 (level, low) - IRQ 19 [ 11.013259] PCI: Setting latency timer of device :01:05.1 to 64 [ 12.468999] EXT3 FS on md1, internal journal [ 13.481179] ip_tables: (C) 2000-2006 Netfilter Core Team [ 13.605721] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 14.052302] NET: Registered protocol family 10 [ 14.053022] lo: Disabled Privacy Extensions [ 14.082283] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 14.363004] loop: module loaded [ 14.523946] md: md2 stopped. [ 14.697862] md: bindsdb3 [ 14.697969] md: bindsdd1 [ 14.698063] md: bindsde1 [ 14.698187] md: bindsdc3 [ 14.698295] md: bindsda3 [ 14.781757] raid5: device sda3 operational as raid disk 0 [ 14.781757] raid5: device sdc3 operational as raid disk 4 [ 14.781757] raid5: device sde1 operational as raid disk 3 [ 14.781757] raid5: device sdd1 operational as raid disk 2 [ 14.781757] raid5: device sdb3 operational as raid disk 1 [ 14.782347] raid5: allocated 5324kB for md2 [ 14.782383] raid5: raid level 5 set md2 active with 5 out of 5
Bug#479114: kernel memory mapping bug
On Sat, 28 Jun 2008, Jonathan Dray wrote: I followed your advice and added the necessary repositories to get the 2.6.26-rc8 kernel. It works great and is 5 to 10 times faster. However I still get some issues : - The computer freeze after a few minutes of inactivity (I deactivated all hibernation and the kind functions). The elapsed time after which the computer freeze seems to be random. When it hangs the caps lock blue led blinks. please report upstream on bugzilla.kernel.org as found on latest. - The screen brightness goes up automatically after a few minutes ! (ACPI related ?) - I have no sound. The sound card is recognized but no sound is played. ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series] you probably have not blacklisted snd-pcsp nor are you using latest alsa userspace from unstable, which would do that for you. - the wireless card didn't work either. The ath5k couldn't handle my Atheros AR5008 card. I had to compile madwifi latest drivers from svn. (seems pretty unstable !!) this model is worked on, ath5k is pretty young thank you for report -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xen status update
hello ian, the fixup for the xenctrl patches was trivial so just commited it. what i was wondering is which important patches we miss out of linux-next or out of rebased linux-2.6-fedora-pvops? could you take a look at #488284 also according to http://wiki.xensource.com/xenwiki/XenParavirtOps Queued for 2.6.27: * Save/restore/migration what's there name and that be probably the less hanging fruit? looking forward to read you. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 485192
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 485192 + pending Bug#485192: SDHCI hacks used on OLPC There were no tags set. 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]
Processed: tagging 488242
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 488242 + pending Bug#488242: Please include more features to jffs2 module Tags were: 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#488495: r8169: multicast packets not received
Package: linux-image-2.6.25-2-iop32x Version: 2.6.25-5 Severity: normal I have a NAS (Thecus N2100, IOP32x based) connected to my network using the r8169 driver. When I start avahi-daemon on the NAS, the rest of the network sees the multicast zeroconf announce packets being sent. If I wait five minutes for the caches to expire in the clients and then ask another machine to resolve the names the NAS is announcing, the lookups fail. The same happens with UPnP, which also uses multicast UDP packets to work. My conclusion is that multicast packets being received by r8169 are not being correctly handled. I've also tried enabling ALLMULTI and PROMISC, which had no effect. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
glassmaker sacculation
Aloha, *** Warning! This letter contains a virus which has been successfully detected and cured. *** Life? Quoted giles. I saw that in a newspaper as a personal insult that he doesn't, i suppose, are you?' and she said no, of course she wasn't and she would constantly resurrect everything grandly. We've never had anyone but a conservative all been answered, but as the professor intended of the dolmens, and we hate ourselves made the gilfoy's father was one of the original trustees,.
Processed: tagging 486032
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 486032 + pending Bug#486032: gfs2-tools: bashism in /bin/sh script There were no tags set. 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]
Processed: tagging 486033
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 486033 + pending Bug#486033: gfs-tools: bashism in /bin/sh script There were no tags set. 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]
Processing of redhat-cluster_2.20080629-1_amd64.changes
redhat-cluster_2.20080629-1_amd64.changes uploaded successfully to localhost along with the files: redhat-cluster_2.20080629-1.dsc redhat-cluster_2.20080629.orig.tar.gz redhat-cluster_2.20080629-1.diff.gz cman_2.20080629-1_amd64.deb libcman2_2.20080629-1_amd64.deb libcman-dev_2.20080629-1_amd64.deb libdlm2_2.20080629-1_amd64.deb libdlm-dev_2.20080629-1_amd64.deb gfs-tools_2.20080629-1_amd64.deb gfs2-tools_2.20080629-1_amd64.deb gnbd-client_2.20080629-1_amd64.deb gnbd-server_2.20080629-1_amd64.deb rgmanager_2.20080629-1_amd64.deb redhat-cluster-suite_2.20080629-1_all.deb redhat-cluster-source_2.20080629-1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476181: marked as done (linux-image-2.6.22-3-vserver-k7: Oops (NULL pointer dereference), XFS fs related)
Your message dated Sun, 29 Jun 2008 16:00:05 +0200
with message-id [EMAIL PROTECTED]
and subject line re: linux-image-2.6.22-3-vserver-k7: Oops (NULL pointer
dereference), XFS fs related
has caused the Debian Bug report #476181,
regarding linux-image-2.6.22-3-vserver-k7: Oops (NULL pointer dereference), XFS
fs related
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.)
--
476181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476181
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.22-3-vserver-k7
Version: 2.6.22-6
Severity: important
This error occured while bacula run its normal backup. It's the first
time this happened. For that reason I conclude it will be
difficult/impossible to reproduce this error, as bacula normally went
through the backup process without any error with the very same
configuration.
All file systems are XFS on LVM devices.
Regards,
Jens
-- Package-specific info:
** Version:
Linux version 2.6.22-3-vserver-k7 (Debian 2.6.22-6) ([EMAIL PROTECTED]) (gcc
version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Nov 12
11:47:04 UTC 2007
** Not tainted
** Kernel log:
BUG: unable to handle kernel NULL pointer dereference at virtual address
004d
printing eip:
f8ca357d
*pde =
Oops: [#1]
SMP
Modules linked in: nfs nfsd exportfs lockd nfs_acl sunrpc ipt_REJECT ipt_recent
xt_state ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
nfnetlink iptable_filter ppdev lp button ac battery tun xt_TCPMSS xt_tcpmss
xt_tcpudp iptable_mangle ip_tables x_tables ppp_deflate zlib_deflate bsd_comp
ppp_async ppp_generic ipv6 xfs ext2 fuse it87 hwmon_vid i2c_isa i2c_dev
hisax_fcpcipnp hisax_isac hisax crc_ccitt isdn snd_intel8x0 rtc snd_ac97_codec
slhc ac97_bus snd_pcm_oss snd_mixer_oss pcspkr parport_pc parport snd_pcm
snd_timer snd soundcore snd_page_alloc shpchp pci_hotplug nvidia_agp
i2c_nforce2 agpgart i2c_core usblp evdev ext3 jbd mbcache dm_mirror dm_snapshot
dm_mod sg sr_mod cdrom ide_disk 8139cp usbhid hid generic amd74xx 8139too
sym53c8xx scsi_transport_spi pdc202xx_new ide_core e100 mii sata_nv ata_generic
libata scsi_mod ehci_hcd ohci_hcd usbcore thermal processor fan
CPU:0
EIP:0060:[f8ca357d]Not tainted VLI
EFLAGS: 00010206 (2.6.22-3-vserver-k7 #1)
EIP is at xfs_iget_core+0x3f/0x5eb [xfs]
eax: ebx: 0011 ecx: f6b80800 edx: 01cc
esi: f5c61590 edi: ebp: f5c61594 esp: ede07cc0
ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Process bacula-fd (pid: 16343[#0], ti=ede06000 task=efe88050 task.ti=ede06000)
Stack: dfcd6600 c18a66bc f8ccd59b c0184878 dcceae3c e2a35e40 f6b80800
dcceae20 0011 dcceae3c dcceae20 f6b80800 f8ca3bc0 010001cc
ede07d78 ede07d70
Call Trace:
[f8ccd59b] xfs_fs_alloc_inode+0xf/0x1c [xfs]
[c0184878] alloc_inode+0xe5/0x16d
[f8ca3bc0] xfs_iget+0x97/0x11f [xfs]
[f8cbb21e] xfs_dir_lookup_int+0x7d/0xd4 [xfs]
[f8cbe45a] xfs_lookup+0x52/0x78 [xfs]
[f8ccac80] xfs_vn_lookup+0x3b/0x70 [xfs]
[c0179c8e] do_lookup+0x1f8/0x295
[f8cca73f] xfs_vn_permission+0xf/0x13 [xfs]
[f8cca730] xfs_vn_permission+0x0/0x13 [xfs]
[c0179f3d] permission+0x212/0x24b
[c018316f] __d_lookup+0x96/0xf4
[c017bad5] __link_path_walk+0x7fd/0xc72
[c0179f3d] permission+0x212/0x24b
[c0186b70] mntput_no_expire+0x11/0x68
[c017bff3] link_path_walk+0xa9/0xb3
[c017bf8e] link_path_walk+0x44/0xb3
[c017c26e] do_path_lookup+0x15a/0x175
[c017b017] getname+0x59/0x8f
[c017ca68] __user_walk_fd+0x2f/0x45
[c0176473] vfs_lstat_fd+0x16/0x3d
[c01764df] sys_lstat64+0xf/0x23
[c017e58c] filldir64+0x0/0xc5
[c0103d12] sysenter_past_esp+0x6b/0xa1
===
Code: 1c 8b 44 24 3c 31 d2 f7 b1 1c 01 00 00 6b f2 0c 03 b1 20 01 00 00 8d 6e
04 89 e8 e8 71 2e 61 c7 8b 06 e9 c6 01 00 00 8b 44 24 40 39 43 3c 0f 85 b6 01
00 00 8b 54 24 3c 39 53 38 0f 85 a9 01 00
EIP: [f8ca357d] xfs_iget_core+0x3f/0x5eb [xfs] SS:ESP 0068:ede07cc0
** Loaded modules:
Module Size Used by
nfs 226476 0
nfsd 205360 17
exportfs5952 1 nfsd
lockd 61192 3 nfs,nfsd
nfs_acl 3840 2 nfs,nfsd
sunrpc159164 13 nfs,nfsd,lockd,nfs_acl
ipt_REJECT 4736 3
ipt_recent 9176 2
xt_state2752 5
ipt_MASQUERADE 3904 2
iptable_nat 7556 1
nf_nat 18348 2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 18124 7 iptable_nat
Bug#471374: marked as done (linux-image-2.6.22-3-486: external sata dies until sata_via is reloaded)
Your message dated Sun, 29 Jun 2008 16:05:46 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.22-3-486: external sata dies until sata_via is reloaded has caused the Debian Bug report #471374, regarding linux-image-2.6.22-3-486: external sata dies until sata_via is reloaded 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.) -- 471374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471374 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.22-3-486 Version: 2.6.22-6 Severity: important i run an external HD case connected with eSata. sometimes when i disconnect the case and reconnect it, i cannot mount the single partition on it any more. the drive is definitely fine, and the case gives no problems with a certain other OS. when i reload the sata_via module, it works again. the other sata drive (WDC below) is mounted all the time and gives no problems when sata_via seems to die. i use several different identical discs in the casing, with different file systems (ext3, fat32) and the error is the same. -- Package-specific info: ** Version: Linux version 2.6.22-3-486 (Debian 2.6.22-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 Mon Nov 12 07:53:08 UTC 2007 ** Not tainted ** Kernel log: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 63 ata1: soft resetting port ata1.00: configured for UDMA/133 ata1: EH complete sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2: soft resetting port ata2: EH complete sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 976767935 printk: 34 messages suppressed. Buffer I/O error on device sdb1, logical block 488383936 Buffer I/O error on device sdb1, logical block 488383937 Buffer I/O error on device sdb1, logical block 488383938 Buffer I/O error on device sdb1, logical block 488383939 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 976767935 Buffer I/O error on device sdb1, logical block 488383936 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 976767937 Buffer I/O error on device sdb1, logical block 488383937 Buffer I/O error on device sdb1, logical block 488383938 Buffer I/O error on device sdb1, logical block 488383939 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 63 Buffer I/O error on device sdb1, logical block 0 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 65 Buffer I/O error on device sdb1, logical block 1 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 63 sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 65 ata1.00: disabled sd 0:0:0:0: [sda] Synchronizing SCSI cache sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK sd 0:0:0:0: [sda] Stopping disk sd 0:0:0:0: [sda] START_STOP FAILED sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK sd 1:0:0:0: [sdb] Synchronizing SCSI cache sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK sd 1:0:0:0: [sdb] Stopping disk sd 1:0:0:0: [sdb] START_STOP FAILED sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK ACPI: PCI interrupt for device :00:0f.0 disabled sata_via :00:0f.0: version 2.2 ACPI: PCI Interrupt :00:0f.0[B] - GSI 20 (level, low) - IRQ 17 sata_via :00:0f.0: routed to hard irq line 5 scsi2 : sata_via scsi3 : sata_via ata3: SATA max UDMA/133 cmd 0x0001c000 ctl 0x0001b802 bmdma 0x0001a800 irq 17 ata4: SATA max UDMA/133 cmd 0x0001b400 ctl 0x0001b002 bmdma 0x0001a808 irq 17 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7: WDC WD5000AAJS-00TKA0, 12.01C01, max UDMA/133 ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) ata3.00: configured for UDMA/133 ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 ata4.00: 976773168 sectors, multi 0:
redhat-cluster_2.20080629-1_amd64.changes ACCEPTED
Accepted: cman_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/cman_2.20080629-1_amd64.deb gfs-tools_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/gfs-tools_2.20080629-1_amd64.deb gfs2-tools_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/gfs2-tools_2.20080629-1_amd64.deb gnbd-client_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-client_2.20080629-1_amd64.deb gnbd-server_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-server_2.20080629-1_amd64.deb libcman-dev_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/libcman-dev_2.20080629-1_amd64.deb libcman2_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/libcman2_2.20080629-1_amd64.deb libdlm-dev_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/libdlm-dev_2.20080629-1_amd64.deb libdlm2_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/libdlm2_2.20080629-1_amd64.deb redhat-cluster-source_2.20080629-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080629-1_all.deb redhat-cluster-suite_2.20080629-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080629-1_all.deb redhat-cluster_2.20080629-1.diff.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.diff.gz redhat-cluster_2.20080629-1.dsc to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.dsc redhat-cluster_2.20080629.orig.tar.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080629.orig.tar.gz rgmanager_2.20080629-1_amd64.deb to pool/main/r/redhat-cluster/rgmanager_2.20080629-1_amd64.deb Override entries for your package: cman_2.20080629-1_amd64.deb - optional admin gfs-tools_2.20080629-1_amd64.deb - optional admin gfs2-tools_2.20080629-1_amd64.deb - optional admin gnbd-client_2.20080629-1_amd64.deb - optional admin gnbd-server_2.20080629-1_amd64.deb - optional admin libcman-dev_2.20080629-1_amd64.deb - optional libdevel libcman2_2.20080629-1_amd64.deb - optional libs libdlm-dev_2.20080629-1_amd64.deb - optional libdevel libdlm2_2.20080629-1_amd64.deb - optional libs redhat-cluster-source_2.20080629-1_all.deb - optional admin redhat-cluster-suite_2.20080629-1_all.deb - optional admin redhat-cluster_2.20080629-1.dsc - source admin rgmanager_2.20080629-1_amd64.deb - optional admin Announcing to [EMAIL PROTECTED] Closing bugs: 486032 486033 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480513: marked as done (PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved)
Your message dated Sun, 29 Jun 2008 16:16:53 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#480513: PCI: BIOS Bug: MCFG area at e000 is not E820-reserved has caused the Debian Bug report #480513, regarding PCI: BIOS Bug: MCFG area at e000 is not E820-reserved 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.) -- 480513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480513 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-6 Severity: important Look like a bug of the Kernel! When i boot i've got this message : PCI: BIOS Bug: MCFG area at e000 is not E820-reserved That the result of dmesg | grep BIOS : BIOS-provided physical RAM map: BIOS-e820: - 0009a400 (usable) BIOS-e820: 0009a400 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3f79 (usable) BIOS-e820: 3f79 - 3f79e000 (ACPI data) BIOS-e820: 3f79e000 - 3f7e (ACPI NVS) BIOS-e820: 3f7e - 3f7ee000 (reserved) BIOS-e820: 3f7f - 3f80 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ffb0 - 0001 (reserved) PCI: BIOS Bug: MCFG area at e000 is not E820-reserved PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=2 PnPBIOS: Disabled by ACPI PNP hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... The kernel boot normaly after that but it takes more time to boot. This bug seems know with some other distro but not in debian. It affects all debian kernel lower version. The laptop model is MSI VR420 with a Celeron 540. The reportbug log : -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Sat Apr 19 00:37:55 UTC 2008 ** Command line: root=/dev/sda3 ro quiet ** Not tainted ** Kernel log: usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) ricoh-mmc: Ricoh MMC Controller disabling driver ricoh-mmc: Copyright(c) Philip Langdale ricoh-mmc: Ricoh MMC controller found at :01:04.3 [1180:0843] (rev 11) ricoh-mmc: Controller is now disabled. Real Time Clock Driver v1.12ac phy0: Selected rate control algorithm 'simple' ACPI: PCI Interrupt :00:1f.3[C] - GSI 17 (level, low) - IRQ 21 input: PC Speaker as /class/input/input7 Yenta: CardBus bridge found at :01:04.0 [1462:3783] sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman Yenta: ISA IRQ mask 0x0cb8, PCI irq 16 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#01) from #02 to #05 pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff cs: IO port probe 0xc000-0xcfff: clean. pcmcia: parent PCI bridge Memory window: 0xfde0 - 0xfe6f pcmcia: parent PCI bridge Memory window: 0xbdf0 - 0xbfef sdhci: SDHCI controller found at :01:04.2 [1180:0822] (rev 21) ACPI: PCI Interrupt :01:04.2[C] - GSI 18 (level, low) - IRQ 20 sdhci:slot0: Will use DMA mode even though HW doesn't fully claim to support it. mmc0: SDHCI at 0xfe6ff400 irq 20 DMA ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 18 PCI: Setting latency timer of device :00:1b.0 to 64 usbcore: registered new interface driver rt73usb hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... Synaptics Touchpad, model: 1, fw: 6.2, id: 0xa5a0b1, caps: 0xa04713/0x0 input: SynPS/2 Synaptics TouchPad as /class/input/input8 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: clean. cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. si3054: cannot initialize. EXT MID = Adding 2224960k swap on /dev/sda7. Priority:-1 extents:1 across:2224960k EXT3 FS on sda3, internal journal loop: module loaded kjournald starting. Commit interval 5 seconds EXT3 FS on sda9, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda8, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda5, internal journal EXT3-fs: mounted filesystem with ordered
Bug#480213: marked as done (linux-image-2.6.24-1-amd64: Losing wifi connection - switched to short barker preamble)
Your message dated Sun, 29 Jun 2008 16:18:41 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.24-1-amd64: Losing wifi connection - switched to short barker preamble has caused the Debian Bug report #480213, regarding linux-image-2.6.24-1-amd64: Losing wifi connection - switched to short barker preamble 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.) -- 480213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480213 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 Severity: important my wifi is losing conectivity and sending the next message to kernel - eth1: switched to short barker preamble maybe this is connected to bug: 462711 (same error there ) here is the message : eth1: Initial auth_alg=0 eth1: authenticate with AP 00:11:6b:22:7f:76 eth1: RX authentication from 00:11:6b:22:7f:76 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:11:6b:22:7f:76 eth1: RX AssocResp from 00:11:6b:22:7f:76 (capab=0x421 status=0 aid=1) eth1: associated eth1: switched to short barker preamble (BSSID=00:11:6b:22:7f:76) this appers dozens of times in dmesg -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 16:52:38 UTC 2008 ** Command line: root=/dev/sda7 ro quiet ** Not tainted ** Kernel log: hda: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda5 sda6 sda7 sda4 sd 0:0:0:0: [sda] Attached SCSI disk Attempting manual resume swsusp: Marking nosave pages: 0009d000 - 0010 swsusp: Basic memory bitmaps created swsusp: Basic memory bitmaps freed kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input3 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 ACPI: Lid Switch [LID] input: Power Button (CM) as /class/input/input4 ACPI: Power Button (CM) [PWRB] input: Sleep Button (CM) as /class/input/input5 ACPI: Sleep Button (CM) [SLPB] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 ACPI: AC Adapter [ACAD] (on-line) ACPI: Battery Slot [BAT1] (battery present) input: Video Bus as /class/input/input6 ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) input: Video Bus as /class/input/input7 ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) piix4_smbus :00:14.0: Found :00:14.0 device Yenta: CardBus bridge found at :06:04.0 [1025:009f] Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :06:04.0, mfunc 0x90501212, devctl 0x44 input: PC Speaker as /class/input/input8 sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman Yenta: ISA IRQ mask 0x0cf8, PCI irq 20 Socket status: 3006 pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff pcmcia: parent PCI bridge Memory window: 0xb020 - 0xb02f sdhci: SDHCI controller found at :06:04.2 [1524:0550] (rev 1) ACPI: PCI Interrupt :06:04.2[B] - GSI 23 (level, low) - IRQ 23 ACPI: PCI Interrupt :00:14.2[A] - GSI 16 (level, low) - IRQ 16 mmc0: SDHCI at 0xb0202800 irq 23 PIO sdhci: SDHCI controller found at :06:04.4 [1524:0551] (rev 1) PCI: Enabling device :06:04.4 ( - 0002) ACPI: PCI Interrupt :06:04.4[B] - GSI 23 (level, low) - IRQ 23 mmc1: SDHCI at 0xb0202100 irq 23 PIO b43-phy0: Broadcom 4318 WLAN found phy0: Selected rate control algorithm 'simple' udev: renamed network interface wlan0 to eth1 Synaptics Touchpad, model: 1, fw: 6.2, id: 0x12a0b1, caps: 0xa04713/0x204000 input: SynPS/2 Synaptics TouchPad as /class/input/input9 Adding 1951856k swap on /dev/sda6. Priority:-1 extents:1 across:1951856k EXT3 FS on sda7, internal journal loop: module loaded input: Acer hotkey driver as /class/input/input10
Bug#486033: marked as done (gfs-tools: bashism in /bin/sh script)
Your message dated Sun, 29 Jun 2008 14:17:14 +
with message-id [EMAIL PROTECTED]
and subject line Bug#486033: fixed in redhat-cluster 2.20080629-1
has caused the Debian Bug report #486033,
regarding gfs-tools: bashism in /bin/sh script
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.)
--
486033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486033
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: gfs-tools
Severity: important
Version: 2.20080603-1
User: [EMAIL PROTECTED]
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing one or more /bin/sh scripts making
use of bashisms.
checkbashisms' output:
possible bashism in ./etc/init.d/gfs-tools line 89 ($foo should be eval
gettext foo):
echo $Usage: $0 {start|stop|restart|reload|force-reload|status}
Not using bash (or a Debian Policy conformant shell interpreter which does
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a
release goal for Lenny to make dash the default /bin/sh[1].
If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
For more information please refer to the Debian Policy section 10.4 supporting
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts
Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh
[1]http://release.debian.org/lenny/goals.txt
Thank you,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
---End Message---
---BeginMessage---
Source: redhat-cluster
Source-Version: 2.20080629-1
We believe that the bug you reported is fixed in the latest version of
redhat-cluster, which is due to be installed in the Debian FTP archive:
cman_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/cman_2.20080629-1_amd64.deb
gfs-tools_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gfs-tools_2.20080629-1_amd64.deb
gfs2-tools_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gfs2-tools_2.20080629-1_amd64.deb
gnbd-client_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gnbd-client_2.20080629-1_amd64.deb
gnbd-server_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gnbd-server_2.20080629-1_amd64.deb
libcman-dev_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libcman-dev_2.20080629-1_amd64.deb
libcman2_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libcman2_2.20080629-1_amd64.deb
libdlm-dev_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libdlm-dev_2.20080629-1_amd64.deb
libdlm2_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libdlm2_2.20080629-1_amd64.deb
redhat-cluster-source_2.20080629-1_all.deb
to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080629-1_all.deb
redhat-cluster-suite_2.20080629-1_all.deb
to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080629-1_all.deb
redhat-cluster_2.20080629-1.diff.gz
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.diff.gz
redhat-cluster_2.20080629-1.dsc
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.dsc
redhat-cluster_2.20080629.orig.tar.gz
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629.orig.tar.gz
rgmanager_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/rgmanager_2.20080629-1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Frederik Schüler [EMAIL PROTECTED] (supplier of updated redhat-cluster
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 29 Jun 2008 16:01:55 +0200
Source: redhat-cluster
Binary: redhat-cluster-suite cman libcman2 libcman-dev libdlm2 libdlm-dev
gfs-tools gfs2-tools gnbd-client gnbd-server rgmanager redhat-cluster-source
Architecture: source amd64 all
Version: 2.20080629-1
Distribution: unstable
Urgency: low
Maintainer: Debian
Bug#486032: marked as done (gfs2-tools: bashism in /bin/sh script)
Your message dated Sun, 29 Jun 2008 14:17:14 +
with message-id [EMAIL PROTECTED]
and subject line Bug#486032: fixed in redhat-cluster 2.20080629-1
has caused the Debian Bug report #486032,
regarding gfs2-tools: bashism in /bin/sh script
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.)
--
486032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486032
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: gfs2-tools
Severity: important
Version: 2.20080603-1
User: [EMAIL PROTECTED]
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing one or more /bin/sh scripts making
use of bashisms.
checkbashisms' output:
possible bashism in ./etc/init.d/gfs2-tools line 89 ($foo should be eval
gettext foo):
echo $Usage: $0 {start|stop|restart|reload|force-reload|status}
Not using bash (or a Debian Policy conformant shell interpreter which does
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours.
Please be aware that although bash is currently the default /bin/sh there's a
release goal for Lenny to make dash the default /bin/sh[1].
If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
For more information please refer to the Debian Policy section 10.4 supporting
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts
Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
https://wiki.ubuntu.com/DashAsBinSh
[1]http://release.debian.org/lenny/goals.txt
Thank you,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
---End Message---
---BeginMessage---
Source: redhat-cluster
Source-Version: 2.20080629-1
We believe that the bug you reported is fixed in the latest version of
redhat-cluster, which is due to be installed in the Debian FTP archive:
cman_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/cman_2.20080629-1_amd64.deb
gfs-tools_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gfs-tools_2.20080629-1_amd64.deb
gfs2-tools_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gfs2-tools_2.20080629-1_amd64.deb
gnbd-client_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gnbd-client_2.20080629-1_amd64.deb
gnbd-server_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/gnbd-server_2.20080629-1_amd64.deb
libcman-dev_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libcman-dev_2.20080629-1_amd64.deb
libcman2_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libcman2_2.20080629-1_amd64.deb
libdlm-dev_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libdlm-dev_2.20080629-1_amd64.deb
libdlm2_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/libdlm2_2.20080629-1_amd64.deb
redhat-cluster-source_2.20080629-1_all.deb
to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080629-1_all.deb
redhat-cluster-suite_2.20080629-1_all.deb
to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080629-1_all.deb
redhat-cluster_2.20080629-1.diff.gz
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.diff.gz
redhat-cluster_2.20080629-1.dsc
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629-1.dsc
redhat-cluster_2.20080629.orig.tar.gz
to pool/main/r/redhat-cluster/redhat-cluster_2.20080629.orig.tar.gz
rgmanager_2.20080629-1_amd64.deb
to pool/main/r/redhat-cluster/rgmanager_2.20080629-1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Frederik Schüler [EMAIL PROTECTED] (supplier of updated redhat-cluster
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 29 Jun 2008 16:01:55 +0200
Source: redhat-cluster
Binary: redhat-cluster-suite cman libcman2 libcman-dev libdlm2 libdlm-dev
gfs-tools gfs2-tools gnbd-client gnbd-server rgmanager redhat-cluster-source
Architecture: source amd64 all
Version: 2.20080629-1
Distribution: unstable
Urgency: low
Maintainer:
Bug#472696: linux-image-2.6.22-3-686: Random reading errors when reading from usb disk with ehci
can this be reproduced with uptodate linux image aka 2.6.25 from unstable? thanks for feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 481436
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 481436 + pending Bug#481436: linux-image-2.6.24-1-686: Unable to use wireless with Intel iwl3945 module. There were no tags set. 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]
Processed: tagging 482100
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 tags 482100 moreinfo Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze There were no tags set. Tags added: moreinfo 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: tagging 482196
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 482196 + pending Bug#482196: linux-image-2.6.25-2-686: dhclient does not connect to wlan There were no tags set. 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]
Processed: tagging 481436
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 481436 + pending Bug#481436: linux-image-2.6.24-1-686: Unable to use wireless with Intel iwl3945 module. Tags were: pending 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#484098: marked as done ([patch] linux-image-2.6.25-2-686 doesn't boot on hp dc7700p)
Your message dated Sun, 29 Jun 2008 16:26:56 +0200 with message-id [EMAIL PROTECTED] and subject line Re: [patch] linux-image-2.6.25-2-686 doesn't boot on hp dc7700p has caused the Debian Bug report #484098, regarding [patch] linux-image-2.6.25-2-686 doesn't boot on hp dc7700p 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.) -- 484098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484098 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: important Hi, hp dc7700p need this patch [1] in order to boot linux-image-2.6.25-2-686 Matthieu [1] http://article.gmane.org/gmane.linux.ide/31518/match=libata+force+hardreset+if+link+powersave+mode -- Package-specific info: -- 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/2 CPU cores) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92b 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-2-686 recommends: ii libc6-i6862.7-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: ---End Message--- ---BeginMessage--- Version: 2.6.25-5 fixed by merged in upstream stable patch, thus closing. thanks for report -- maks ---End Message---
Bug#486433: marked as done (please bring back prism54)
Your message dated Sun, 29 Jun 2008 16:36:49 +0200 with message-id [EMAIL PROTECTED] and subject line Re: please bring back prism54 has caused the Debian Bug report #486433, regarding please bring back prism54 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.) -- 486433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486433 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: important I know the prism54 driver is old, doesn't support WPA, and has plenty of other problems. But the p54pci driver is not a complete replacement for it. The softmac firmware you have to use (even with old fullmac cards) doesn't allow you to do master mode. Please do not disable it unless it doesn't work at all anymore. -- Jon DeVree It's an ingenious solution to a problem that should never have existed in the first place. -James May, Top Gear ---End Message--- ---BeginMessage--- prism54 is no longer maintained. and no we can't enable both new and old driver. please report your p54 bugs if they still apply on 2.6.26-rc8 (see trunk http://wiki.debian.org/DebianKernel ) upstream to bugzilla.kernel.org thanks -- maks ---End Message---
Bug#486322: marked as done (gdb: Failed to read a valid object file image from memory)
Your message dated Sun, 29 Jun 2008 16:39:57 +0200 with message-id [EMAIL PROTECTED] and subject line Re: gdb: Failed to read a valid object file image from memory has caused the Debian Bug report #486322, regarding gdb: Failed to read a valid object file image from memory 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.) -- 486322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486322 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch6 Severity: important It is somewhat a pity that bug #401482 still exists in 2.6.18.dfsg.1-18etch6 -- 18 months after the problem has been reported first. I'm using a 32-bit kernel on a 64-bit AMD Sempron. How many years will it take until 2.6.23 is included in the stable distribution? It is not even possible to debug simple programs like hello-world.c without getting the error message Failed to read a valid object file image from memory. ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 ---End Message--- ---BeginMessage--- Version: 2.6.23-1 closing as dup report against old version. checkout etch + half kernel http://wiki.debian.org/EtchAndAHalf -- maks ---End Message---
Bug#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
On Tue, 20 May 2008, maximilian attems wrote: 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. any update on the matter 2.6.26-rc8 is out inbetween. thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487176: marked as done (linux-image-2.6.18-6-686: open sleeps)
Your message dated Sun, 29 Jun 2008 16:42:21 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-6-686: open sleeps has caused the Debian Bug report #487176, regarding linux-image-2.6.18-6-686: open sleeps 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.) -- 487176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487176 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch5 Severity: important Hello, [I just sent this as an email to [EMAIL PROTECTED], however as it involves the kernel in Debian/Etch, I felt it wise to submit here too. Upstream may not be happy with supporting the older kernel version...] I am having (weird) issues with XFS, in that open(...) on certain files takes 45 seconds to return. After the file has been opened, the next file in the same directory takes 45 seconds. If the file was recently opened it returns immediately. I thought this was a low level I/O issue, so copied the files in question to a completely independent RAID array (separate LVM, RAID, controllers, disks), but the problem remains. I raised the issue on the XFS mailing list and was told the problem was the the lease breaking code in VFS[2], and that I should contact this mailing list. This is with the kernel in Debian/Stable: hq:/tmp# uname -a Linux hq 2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686 GNU/Linux More details: [1] http://lists.luv.asn.au/wws/arc/luv-main/2008-06/msg00143.html [2] http://oss.sgi.com/archives/xfs/2008-06/msg00222.html Any ideas? -- 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-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-686 depends on: ii coreutils5.97-5.3The GNU core utilities ii debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy ii initramfs-tools [linux-initr 0.85h tools for generating an initramfs ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-6-686 recommends: ii libc6-i686 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [i -- debconf information excluded ---End Message--- ---BeginMessage--- Version: 2.6.24-1 fixed in newer vfs. not a candidate for backport. use etch + half kernel - http://wiki.debian.org/EtchAndAHalf -- maks ---End Message---
Bug#487421: marked as done (Early boot-time kernel panic with linux-image-2.6.25-2-amd64 (2.6.25-5).)
Your message dated Sun, 29 Jun 2008 16:44:43 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: Early boot-time kernel panic with
linux-image-2.6.25-2-amd64 (2.6.25-5).
has caused the Debian Bug report #487421,
regarding Early boot-time kernel panic with linux-image-2.6.25-2-amd64
(2.6.25-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.)
--
487421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487421
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-5
Severity: grave
Justification: renders package unusable
Hello all,
I experience early boot-time kernel panic with linux-image-2.6.25-2-amd64
(2.6.25-5)
on my amd64 box.
After having read tons of posts on forums, and particularly:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482773
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479101
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607#96
I know that the bug I discovered is closely related to already reported bug
#479607
which apparently concerns lilo because:
The bug - kernel panic - happens just before any piece of userspace code being
loaded from initial RAM disk :
===
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions :
010065536ram0 (driver?)
..
..
..
010f65536ram15 (driver?)
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(22,65)
===
But I have to add food for thought:
Here follow key files on my Debian_amd64 system:
ls -l /boot gave: ( cropped the list to meaningful parts )
-rw-r--r-- 1 root root 6621847 jun 21 11:19 initrd.img-2.6.18-6-amd64
-rw--- 1 root root 7090895 jun 21 09:40 initrd.img-2.6.24-1-amd64
-rw-r--r-- 1 root root 7276007 jun 21 11:41 initrd.img-2.6.25-2-amd64
-rw-r--r-- 1 root root 21132800 jun 21 18:03 initrd.img-2.6.25-2-amd64.cpio
-rw-r--r-- 1 root root 5598429 jun 21 18:06 initrd.img-2.6.25-2-amd64_light
-rw-r--r-- 1 root root 16109056 jun 21 18:12
initrd.img-2.6.25-2-amd64_light.cpio
-rw-r--r-- 1 root root 1512362 jun 6 09:20 vmlinuz-2.6.18-6-amd64
-rw-r--r-- 1 root root 1668248 mai 10 11:32 vmlinuz-2.6.24-1-amd64
-rw-r--r-- 1 root root 1727488 jun 12 18:35 vmlinuz-2.6.25-2-amd64
ls -l /boot/initrd.img-2.6.*amd64{,_light}{,.cpio} gave: ( cropped the list to
meaningful parts )
/boot/initrd.img-2.6.18-6-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 11:19:01 2008
/boot/initrd.img-2.6.24-1-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 09:40:50 2008
/boot/initrd.img-2.6.25-2-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 11:41:17 2008
/boot/initrd.img-2.6.25-2-amd64.cpio: ASCII cpio archive (SVR4 with no
CRC)
/boot/initrd.img-2.6.25-2-amd64_light: gzip compressed data, from Unix,
last modified: Sat Jun 21 18:06:31 2008, max compression
/boot/initrd.img-2.6.25-2-amd64_light.cpio: ASCII cpio archive (SVR4 with no
CRC)
WHERE initrd.img-2.6.25-2-amd64_light is a manually lightened customization of
the
original initrd.
Finally, since I only experience trouble - very early kernel panic - with
2.6.25-2-amd64
regardless wether my initrd is heavy or not, how do you explain this strange
behavior ?
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (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-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92b tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.25-2-amd64 recommends no packages.
-- debconf information:
linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64:
Bug#485692: linux-image-2.6.25-2-amd64: fails to work with USB mouses and USB flash devices
On Wed, 11 Jun 2008, Eugene V. Lyubimkin wrote: Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-3 Severity: important Current kernel version (2.6.25) fails to work with my USB mouses and USB flash devices. I got next messages in /var/log/kern.log: Jun 5 13:54:31 1501-debian kernel: [ 2242.188619] hub 6-0:1.0: unable to enumerate USB device on port 3 Jun 5 14:20:33 1501-debian kernel: [4.997686] hub 6-0:1.0: unable to enumerate USB device on port 3 Jun 5 22:24:27 1501-debian kernel: [ 24.931912] hub 6-0:1.0: unable to enumerate USB device on port 5 Jun 5 22:24:27 1501-debian kernel: [ 36.311167] hub 6-0:1.0: unable to enumerate USB device on port 7 Jun 6 22:52:31 1501-debian kernel: [ 8755.575505] hub 6-0:1.0: unable to enumerate USB device on port 5 Jun 6 22:52:31 1501-debian kernel: [ 8755.792560] hub 6-0:1.0: unable to enumerate USB device on port 7 Jun 7 10:33:32 1501-debian kernel: [19867.771578] hub 6-0:1.0: unable to enumerate USB device on port 5 Jun 7 10:33:32 1501-debian kernel: [19868.006905] hub 6-0:1.0: unable to enumerate USB device on port 7 Jun 7 10:34:28 1501-debian kernel: [19937.164863] hub 6-0:1.0: unable to enumerate USB device on port 5 Jun 8 21:29:40 1501-debian kernel: [139555.908490] hub 6-0:1.0: unable to enumerate USB device on port 5 After downgrade to 2.6.24 kernel all works fine. can you checkout 2.6.26-rc8. see trunk apt lines - http://wiki.debian.org/DebianKernel thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484753: linux-image-2.6.24-1-amd64: Fails to boot. Unable to mount root fs
2.6.25 from unstable should just install fine, please report the error message you are seeing on boot. please follow those instructions for debug - http://wiki.debian.org/InitramfsDebug thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486346: linux-image-2.6.25-2-amd64: lid switch hangs and resets laptop
On Sun, 15 Jun 2008, Grzegorz Zur wrote: Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-5 Severity: important Kernel hangs and resets system after lid switch is pressed. Problem occurs often but not always. It was found on HP Compaq 6710S. please test out 2.6.26-rcX it has newer acpi - http://wiki.debian.org/DebianKernel if you can still reproduce please report upstream on bugzilla.kernel.org and let us know the bug number. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488534: linux-image-2.6.25-2-amd64: No agpgart after upgrade
Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-6 Severity: important I just updated to the latest version of 2.6.25-2 and rebooted. Having done so, I can't start X. THe X server dies because it can't open /dev/agpgart and falls back to framebuffer which then also fails. Here's the chunk of kernel log: Jun 29 10:50:04 cerberus kernel: [ 14.190689] [drm] Initialized drm 1.1.0 20060810 Jun 29 10:50:04 cerberus kernel: [ 14.198026] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 Jun 29 10:50:04 cerberus kernel: [ 14.198031] PCI: Setting latency timer of device :00:02.0 to 64 Jun 29 10:50:04 cerberus kernel: [ 14.198040] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. Jun 29 10:50:04 cerberus kernel: [ 14.198043] DRM: Fill_in_dev failed. Jun 29 10:50:04 cerberus kernel: [ 14.198045] ACPI: PCI interrupt for device :00:02.0 disabled -- Package-specific info: ** Version: Linux version 2.6.25-2-amd64 (Debian 2.6.25-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 00:16:12 UTC 2008 ** Command line: root=/dev/md0 ro quiet ** Not tainted ** Kernel log: [1.504582] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xf3206300 irq 1277 [1.504584] ata6: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xf3206380 irq 1277 [1.596113] usb 2-1: configuration #1 chosen from 1 choice [1.599000] usb 2-1: New USB device found, idVendor=03f0, idProduct=8604 [1.599002] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.599004] usb 2-1: Product: Deskjet 5400 series [1.599005] usb 2-1: Manufacturer: HP [1.599006] usb 2-1: SerialNumber: TH58N111RN04JH [1.543369] input: Kensington Kensington USB/PS2 Wheel Mouse as /class/input/input2 [1.560177] input,hidraw0: USB HID v1.10 Mouse [Kensington Kensington USB/PS2 Wheel Mouse] on usb-:00:1a.0-1 [1.560197] usbcore: registered new interface driver usbhid [1.560200] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver [1.744130] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.748122] ata1.00: HPA detected: current 490232639, native 490234752 [1.748122] ata1.00: ATA-7: WDC WD2500YS-01SHB1, 20.06C06, max UDMA/133 [1.748122] ata1.00: 490232639 sectors, multi 0: LBA48 NCQ (depth 31/32) [1.628118] ata1.00: configured for UDMA/133 [1.808133] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.648119] ata2.00: ATA-7: WDC WD2500YS-01SHB1, 20.06C06, max UDMA/133 [1.648119] ata2.00: 490234752 sectors, multi 0: LBA48 NCQ (depth 31/32) [1.812126] ata2.00: configured for UDMA/133 [1.856137] ata5: SATA link down (SStatus 0 SControl 300) [1.900140] ata6: SATA link down (SStatus 0 SControl 300) [1.664120] scsi 0:0:0:0: Direct-Access ATA WDC WD2500YS-01S 20.0 PQ: 0 ANSI: 5 [1.664120] scsi 1:0:0:0: Direct-Access ATA WDC WD2500YS-01S 20.0 PQ: 0 ANSI: 5 [1.666855] Uniform Multi-Platform E-IDE driver [1.666857] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [1.667856] JMB: IDE controller (0x197b:0x2368 rev 0x00) at PCI slot :02:00.0 [1.667878] ACPI: PCI Interrupt :02:00.0[A] - GSI 16 (level, low) - IRQ 16 [1.667884] JMB: 100% native mode on irq 16 [1.667892] ide0: BM-DMA at 0xc400-0xc407, BIOS settings: hda:DMA, hdb:PIO [1.667903] ide1: BM-DMA at 0xc408-0xc40f, BIOS settings: hdc:PIO, hdd:PIO [1.667912] Probing IDE interface ide0... [1.922713] Driver 'sd' needs updating - please use bus_type methods [1.922768] sd 0:0:0:0: [sda] 490232639 512-byte hardware sectors (250999 MB) [1.922777] sd 0:0:0:0: [sda] Write Protect is off [1.922779] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.922793] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.922829] sd 0:0:0:0: [sda] 490232639 512-byte hardware sectors (250999 MB) [1.922837] sd 0:0:0:0: [sda] Write Protect is off [1.922839] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.922852] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.922854] sda: sda1 sda2 sda5 [1.716163] sd 0:0:0:0: [sda] Attached SCSI disk [1.716213] sd 1:0:0:0: [sdb] 490234752 512-byte hardware sectors (251000 MB) [1.716224] sd 1:0:0:0: [sdb] Write Protect is off [1.716227] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [1.716245] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.716285] sd 1:0:0:0: [sdb] 490234752 512-byte hardware sectors (251000 MB) [1.716296] sd 1:0:0:0: [sdb] Write Protect is off [1.716298] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [1.716316] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.716318] sdb: sdb1 sdb2 sdb5 [1.736125] sd 1:0:0:0: [sdb] Attached
Bug#487287: acpi: Negative value is show for temperature, fan constantly on
Am Sonntag, 22. Juni 2008 12:48 schrieb Michael Meskes:
On Sun, Jun 22, 2008 at 10:43:25AM +0200, Adolf Winterer wrote:
The directory /sys/class/thermal does not exist.
Which kernel do you run? Looks like a strange configuration here.
Look at the temperature!
$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature: -73 C
Yes, it reports a negative temperature. But this is reported by the
kernel. acpi only reads this information and displays it. The problem
doesn't seem to be in acpi, but in the kernel itself.
I did some more research regarding ACPI and found out that on both systems
there is a flawed ACPI DSDT.
Using acpidump I stored the DSDT into a file and disassembled it with iasl.
When comiling the file back into a binary file I get one warning and two
errors on both systems which look quite similar.
# iasl -sa dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20061109 [May 15 2007]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt.dsl 378: Method (\_WAK, 1, NotSerialized)
Warning 1079 - ^ Reserved method must return a value (_WAK)
dsdt.dsl 419: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
dsdt.dsl 424: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
ASL Input: dsdt.dsl - 5129 lines, 163766 bytes, 1797 keywords
Compilation complete. 2 Errors, 1 Warnings, 0 Remarks, 571 Optimizations
I found a suggestion how to fix the warning, but did not find anything for the
errors. The code looks like that:
Scope (\_SI)
{
Method (_MSG, 1, NotSerialized)
{
Store (Local0, Local0)
}
Method (_SST, 1, NotSerialized)
{
Store (Local0, Local0)
}
}
I do not understand a single word from it, so there is not a real chance to
fix it myself.
Some time ago I read about a DSDT fix that has been removed from the kernel,
but I do not know if this is related to the problem we see here.
Michael
--
Man kann ein Problem nicht mit den gleichen Denkstrukturen lösen, die
zu seiner Entstehung beigetragen haben. -- Albert Einstein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449278: marked as done (linux-image-2.6.22-2-amd64: Out of memory error!)
Your message dated Sun, 29 Jun 2008 17:38:58 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#449278: linux-image-2.6.22-2-amd64: Out of memory error! has caused the Debian Bug report #449278, regarding linux-image-2.6.22-2-amd64: Out of memory error! 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.) -- 449278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449278 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.22-2-amd64 Version: 2.6.22-4 Severity: important As noted below some of my hardware is not totally supported, but this is the error I recieved in my kern.log hope this is helpful. Nov 2 20:43:33 Raiz-MtX kernel: Free swap = 0kB Nov 2 20:43:33 Raiz-MtX kernel: Total swap = 1269092kB Nov 2 20:43:33 Raiz-MtX kernel: Free swap:0kB Nov 2 20:43:33 Raiz-MtX kernel: 524208 pages of RAM Nov 2 20:43:33 Raiz-MtX kernel: 55901 reserved pages Nov 2 20:43:33 Raiz-MtX kernel: 547 pages shared Nov 2 20:43:33 Raiz-MtX kernel: 0 pages swap cached Nov 2 20:43:33 Raiz-MtX kernel: Out of memory: kill process 3492 (bash) score 600648 or a child Nov 2 20:43:33 Raiz-MtX kernel: Killed process 3571 (quake4.x86) Nov 2 20:43:33 Raiz-MtX kernel: klogd invoked oom-killer: gfp_mask=0x200d2, order=0, oom killadj=0 Nov 2 20:43:33 Raiz-MtX kernel: Nov 2 20:43:33 Raiz-MtX kernel: Call Trace: Nov 2 20:43:33 Raiz-MtX kernel: [80262786] out_of_memory+0x70/0x2ea Nov 2 20:43:33 Raiz-MtX kernel: [802644d5] __alloc_pages+0x233/0x2bc Nov 2 20:43:33 Raiz-MtX kernel: [80274ee8] read_swap_cache_async+0x45/0xd8 Nov 2 20:43:33 Raiz-MtX kernel: [8026aa6e] swapin_readahead+0x60/0xd3 Nov 2 20:43:33 Raiz-MtX kernel: [802296bb] __wake_up_common+0x3e/0x68 Nov 2 20:43:33 Raiz-MtX kernel: [8026c574] __handle_mm_fault+0x6e7/0x9d7 Nov 2 20:43:33 Raiz-MtX kernel: [803864b6] sock_def_readable+0x34/0x5f Nov 2 20:43:33 Raiz-MtX kernel: [803e4c93] unix_dgram_sendmsg+0x43a/0x4d0 Nov 2 20:43:33 Raiz-MtX kernel: [80220d3c] do_page_fault+0x3ec/0x770 Nov 2 20:43:33 Raiz-MtX kernel: [8038220a] sock_aio_write+0x110/0x128 Nov 2 20:43:33 Raiz-MtX kernel: [803f3ccd] error_exit+0x0/0x84 Nov 2 20:43:33 Raiz-MtX kernel: [802328bb] do_syslog+0x173/0x3be Nov 2 20:43:33 Raiz-MtX kernel: [80232889] do_syslog+0x141/0x3be Nov 2 20:43:33 Raiz-MtX kernel: [802439c2] autoremove_wake_function+0x0/0x2e Nov 2 20:43:33 Raiz-MtX kernel: [802bf04c] kmsg_read+0x3a/0x44 Nov 2 20:43:33 Raiz-MtX kernel: [8028397d] vfs_read+0xcb/0x153 Nov 2 20:43:33 Raiz-MtX kernel: [80283d19] sys_read+0x45/0x6e Nov 2 20:43:33 Raiz-MtX kernel: [80209d8e] system_call+0x7e/0x83 Nov 2 20:43:33 Raiz-MtX kernel: Nov 2 20:43:33 Raiz-MtX kernel: Mem-info: Nov 2 20:43:33 Raiz-MtX kernel: Node 0 DMA per-cpu: Nov 2 20:43:33 Raiz-MtX kernel: CPU0: Hot: hi:0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Nov 2 20:43:33 Raiz-MtX kernel: Node 0 DMA32 per-cpu: Nov 2 20:43:33 Raiz-MtX kernel: CPU0: Hot: hi: 186, btch: 31 usd: 15 Cold: hi: 62, btch: 15 usd: 14 Nov 2 20:43:33 Raiz-MtX kernel: Active:224285 inactive:225228 dirty:0 writeback:0 unstab -- Package-specific info: ** Version: Linux version 2.6.22-2-amd64 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Thu Aug 30 23:43:59 UTC 2007 ** Tainted: PFSRMB ** Kernel log: NFORCE-MCP67: IDE controller at PCI slot :00:06.0 NFORCE-MCP67: chipset revision 161 NFORCE-MCP67: not 100% native mode: will probe irqs later NFORCE-MCP67: BIOS didn't set cable bits correctly. Enabling workaround. NFORCE-MCP67: :00:06.0 (rev a1) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA Probing IDE interface ide0... usb 1-1: new full speed USB device using ohci_hcd and address 3 usb 1-1: configuration #1 chosen from 1 choice usb 1-2: new low speed USB device using ohci_hcd and address 4 hda: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive usb 1-2: configuration #1 chosen from 1 choice usb 4-2.2: new low speed USB device using ehci_hcd and address 4 hdb: SAMSUNG SP0802N, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 usb 4-2.2: configuration #1 chosen from 1 choice usbcore: registered new interface driver hiddev input: Logitech USB Gaming Mouse as /class/input/input0 input: USB HID v1.11 Mouse [Logitech USB Gaming Mouse] on usb-:00:02.0-1 hiddev96: USB HID v1.11
Bug#410933: marked as done (alpha: Could not allocate X bytes percpu data)
Your message dated Sun, 29 Jun 2008 17:43:51 +0200 with message-id [EMAIL PROTECTED] and subject line RE: alpha: Could not allocate X bytes percpu data has caused the Debian Bug report #410933, regarding alpha: Could not allocate X bytes percpu data 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.) -- 410933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410933 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-alpha-smp Version: 2.6.18.dfsg.1-10 Severity: normal Tags: patch Hello, linux-image-2.6.18-4-alpha-smp still suffers from Could not allocate X bytes percpu data when loading modules (for example, xfs, eepro100 and e100). I've found this discussion (regarding the previous version, linux-image-2.6.18-3-alpha-smp): http://www.mail-archive.com/[EMAIL PROTECTED]/msg23999.html where this patch was suggested: http://marc.theaimsgroup.com/?l=linux-kernelm=116593521703170w=2 Could (the|a) fix please be included in the next release please? I'd be all too happy to go back to distro kernels from self-built ones. cheers, Andras -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-alpha-smp depends on: ii coreutils 5.97-5 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-pre3-1 tools for managing Linux kernel mo linux-image-2.6.18-4-alpha-smp recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-alpha-smp/postinst/depmod-error-2.6.18-4-alpha-smp: false linux-image-2.6.18-4-alpha-smp/preinst/failed-to-move-modules-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/preinst/initrd-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/preinst/abort-install-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/postinst/old-dir-initrd-link-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/depmod-error-initrd-2.6.18-4-alpha-smp: false linux-image-2.6.18-4-alpha-smp/preinst/already-running-this-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/prerm/would-invalidate-boot-loader-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/create-kimage-link-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/preinst/bootloader-initrd-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/old-initrd-link-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/prerm/removing-running-kernel-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/kimage-is-a-directory: linux-image-2.6.18-4-alpha-smp/preinst/overwriting-modules-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/old-system-map-link-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/preinst/abort-overwrite-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/preinst/elilo-initrd-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/bootloader-test-error-2.6.18-4-alpha-smp: linux-image-2.6.18-4-alpha-smp/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-alpha-smp/preinst/lilo-initrd-2.6.18-4-alpha-smp: true linux-image-2.6.18-4-alpha-smp/postinst/bootloader-error-2.6.18-4-alpha-smp: ---End Message--- ---BeginMessage--- Version: 2.6.21-1 fixed upstream available in etch + half kernel commit 65fdc8544f7d27df95256cbcfc2a53fa0fa38134 http://wiki.debian.org/EtchAndAHalf thanks for report -- maks ---End Message---
Bug#343463: marked as done (linux-image-2.6.12-1-686-smp: usb keyboard failures, drivers/usb/input/hid-core.c: input irq status -32 received)
Your message dated Sun, 29 Jun 2008 17:41:10 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.12-1-686-smp: usb keyboard failures, drivers/usb/input/hid-core.c: input irq status -32 received has caused the Debian Bug report #343463, regarding linux-image-2.6.12-1-686-smp: usb keyboard failures, drivers/usb/input/hid-core.c: input irq status -32 received 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.) -- 343463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343463 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.12-1-686-smp Version: 2.6.12-10 Severity: normal I bought a new keyboard a few days ago, a basic usb keyboard. From time to time, it stops responding and fill the console with messages like: Dec 15 13:56:24 eos kernel: drivers/usb/input/hid-core.c: input irq status -32 received Dec 15 13:56:24 eos kernel: drivers/usb/input/hid-core.c: input irq status -32 received I searched on the web for similar problems but I found nothing really helpful, most pages referring to another irc status number (like -84) anyway. If I unplug the keyboard and replug it, it reworks. But that damn inconvenient :) As side effect, it really spam the console and kern.log by printing even more than once the error message per second. As you can see, I have now a kern.log 92MB big while it never reach 1MB in normal circonstances. [EMAIL PROTECTED]:/home/moa# ls -sh /var/log/kern.log* 92M /var/log/kern.log24K /var/log/kern.log.1.gz 20K /var/log/kern.log.3.gz 48K /var/log/kern.log.0 16K /var/log/kern.log.2.gz 16K /var/log/kern.log.4.gz Tell me if there's anything I can do. Follows lspci results: :00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) :00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) :00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) :00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) :00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) :00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) :00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) :00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:00.0 VGA compatible controller: ATI Technologies Inc R430 [Radeon X800 XL] (PCIe) :01:00.1 Display controller: ATI Technologies Inc R430 [Radeon X800 XL] (PCIe) Secondary :02:01.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) :02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) And lsusb Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 002: ID 055f:0008 Mustek Systems, Inc. ScanExpress 1200 CU Plus Bus 002 Device 001: ID : Bus 001 Device 020: ID 062a:0201 Creative Labs Bus 001 Device 001: ID : I dont know what is this creative labs thing, it looks like it is the keyboard but I did not new it was manufactured by creative labs (well, that does not matter) lsusb -v for the relevant thing: Bus 001 Device 020: ID 062a:0201 Creative Labs Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x062a Creative Labs idProduct 0x0201 bcdDevice1.00 iManufacturer 0 iProduct1 USB-compliant keyboard iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes
Bug#436260: marked as done (linux-support-2.6.22-1: Support for exernal module packages broken)
Your message dated Sun, 29 Jun 2008 17:46:14 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-support-2.6.22-1: Support for exernal module packages broken has caused the Debian Bug report #436260, regarding linux-support-2.6.22-1: Support for exernal module packages broken 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.) -- 436260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436260 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-support-2.6.22-1 Version: 2.6.22-3 Severity: important Attempting to build a module module package such as linux-modules-extra-2.6 which uses gencontrol.py fails even when using the copy of gencontrol.py included in the package as /usr/src/linux-support-2.6.22-1/modules/gencontrol.py since the interface provided by lib/python/debian_linux has changed but gencontrol.py has not been updated to match the new interface. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-support-2.6.22-1 depends on: ii python2.4-minimal 2.4.4-5A minimal subset of the Python lan linux-support-2.6.22-1 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- closing as this general assumption seems not true quite a bunch of external modules is build. also report against old version. -- maks ---End Message---
Processed: tagging 474312
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 474312 + pending Bug#474312: linux-source-2.6.24: emux midi synthesizer doesn't honor SOFT_PEDAL-release event Tags were: 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]
Processed: tagging 468149
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 468149 + pending Bug#468149: linux-source-2.6.22: longrun cpufreq module reports false min freq Tags were: 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]
Processed: tagging 484693
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 484693 + pending Bug#484693: linux-2.6: Add RTC class support for powerpc64 machines Tags were: 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#427004: closed by maximilian attems [EMAIL PROTECTED] (re: linux-image-2.6.18-4-amd64: kernel oops)
Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #427004: linux-image-2.6.18-4-amd64: kernel oops 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. [..] closing as tainted oops and no follow up. Does the oops originate in the non-free module? And what follow up? Was I supposed to follow up on my own invitation for you to ask for more info? I find this confusing... -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425299: marked as done (linux-2.6: please package a vserver bigmem kernel)
Your message dated Sun, 29 Jun 2008 18:05:02 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6 - please support vserver on i386-pae has caused the Debian Bug report #438086, regarding linux-2.6: please package a vserver bigmem 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.) -- 438086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438086 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist Please package a bigmem version of the vserver kernel. People using vserver may well be doing so on server hardware with 4gb of ram (I am). Thanks, Richard. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- closing as only one demand came across. amd64 usage is the recommendation for = 4G RAM sunny greetings -- maks ---End Message---
Bug#438086: marked as done (linux-2.6 - please support vserver on i386-pae)
Your message dated Sun, 29 Jun 2008 18:05:02 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6 - please support vserver on i386-pae has caused the Debian Bug report #438086, regarding linux-2.6 - please support vserver on i386-pae 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.) -- 438086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438086 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-vserver-686 Version: 2.6.18+6 Severity: important linux-image-vserver package does not provide bigmem support, hardware with 4G or more RAM are not fully utilized. -- 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-4-vserver-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-vserver-686 depends on: ii linux-image-2.6-vserver-686 2.6.18+6 Linux kernel 2.6 image on PPro/Cel linux-image-vserver-686 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- closing as only one demand came across. amd64 usage is the recommendation for = 4G RAM sunny greetings -- maks ---End Message---
Processed: tagging 443742
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 tags 443742 pending Bug#443742: linux-2.6: Please enable CONFIG_TCP_MD5SIG There were no tags set. 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#444324: marked as done (linux-image-2.6.21-2-686: AC97 Power Saving Off By Default)
Your message dated Sun, 29 Jun 2008 18:08:05 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-2-686: AC97 Power Saving Off By Default has caused the Debian Bug report #444324, regarding linux-image-2.6.21-2-686: AC97 Power Saving Off 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.) -- 444324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444324 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-2-686 Version: 2.6.21-6 Severity: wishlist I noticed that by default that the AC97 power saving mode is off by default. Would it be possible to consider compiling the stock kernel with the power saving mode on? -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18 (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-2-686 depends on: ii initramfs-tools [linux-initr 0.90a 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.21-2-686 recommends: ii libc6-i6862.6.1-1+b1 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-2-686/preinst/elilo-initrd-2.6.21-2-686: true linux-image-2.6.21-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.21-2-686/prerm/would-invalidate-boot-loader-2.6.21-2-686: true linux-image-2.6.21-2-686/preinst/already-running-this-2.6.21-2-686: linux-image-2.6.21-2-686/postinst/old-initrd-link-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/bootloader-error-2.6.21-2-686: linux-image-2.6.21-2-686/preinst/lilo-initrd-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/depmod-error-initrd-2.6.21-2-686: false linux-image-2.6.21-2-686/preinst/bootloader-initrd-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/bootloader-test-error-2.6.21-2-686: linux-image-2.6.21-2-686/postinst/old-dir-initrd-link-2.6.21-2-686: true linux-image-2.6.21-2-686/prerm/removing-running-kernel-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/kimage-is-a-directory: linux-image-2.6.21-2-686/preinst/failed-to-move-modules-2.6.21-2-686: linux-image-2.6.21-2-686/preinst/abort-overwrite-2.6.21-2-686: linux-image-2.6.21-2-686/preinst/initrd-2.6.21-2-686: linux-image-2.6.21-2-686/preinst/overwriting-modules-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/create-kimage-link-2.6.21-2-686: true linux-image-2.6.21-2-686/postinst/depmod-error-2.6.21-2-686: false linux-image-2.6.21-2-686/postinst/old-system-map-link-2.6.21-2-686: true linux-image-2.6.21-2-686/preinst/abort-install-2.6.21-2-686: ---End Message--- ---BeginMessage--- closing as it wouldn't be a safe default. power saving is quite agressive. easily enabled with powertop. -- maks ---End Message---
Bug#412139: marked as done (linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root)
Your message dated Sun, 29 Jun 2008 18:10:55 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root has caused the Debian Bug report #412139, regarding linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root 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.) -- 412139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412139 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: grave Justification: renders package unusable After latest upgrade of 2.6.18-4-686 my machine stops booting when reasing to the message: Waiting for root. The disk is found but just before finding disk on system I see this error message from udev: udevd[411]: Illegal subsystem (or something like that). Then complains of an error in /etc/udev/rules.d/udev.rules on line 61 I have tried to run update-initramfs -u -t -k 2.6.18-4-686 without any luck. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 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-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD Versions of packages linux-image-2.6.18-4-686 recommends: ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true * linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/kimage-is-a-directory: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true ---End Message--- ---BeginMessage--- closing as no real info beside that ordering of the modules changed. this is quite expected and thus UUID usage is recommended. best regards -- maks ---End Message---
Bug#469693: linux-image-2.6.24-1-686: Got better but still looses USB devs (mouse/keyb)
how is 2.6.25 doing? linux images from unstable just install fine in testing. thanks for feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437344: marked as done (linux-image-2.6.21-2-686: seemingly random SATA disk lockup with ICH5 intel bridge)
Your message dated Sun, 29 Jun 2008 18:15:01 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-2-686: seemingly random SATA disk lockup with ICH5 intel bridge has caused the Debian Bug report #437344, regarding linux-image-2.6.21-2-686: seemingly random SATA disk lockup with ICH5 intel bridge 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.) -- 437344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437344 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-2-686 Version: 2.6.21-6 Severity: important Hello, I'm trying to get to run a Seagate 250GB hard disk. It works with Microsoft Windows XP so it is not a hardware issue. Sometimes the system boots perfectly, sometimes an error show up soon in the boot process an then the hard disk, while recognized, does not allow access to anything on it, including its partition table, making the system temporarily locked each time it tries to access it. It is not a partition issue or whatever, the partition model is simple and was erased and cleaned several times. The report is made against the latest kernel I have installed but it fails also with kernel 2.6.15. Here comes a boot process, the interesting part is the following. If it does not show up, then the disk works perfectly. Considering the problem is random to me (maybe there a logic, but I do not get it) Aug 10 12:15:29 eos kernel: SCSI subsystem initialized Aug 10 12:15:29 eos kernel: [c014b67e] __report_bad_irq+0x36/0x75 Aug 10 12:15:29 eos kernel: [c014b865] note_interrupt+0x1a8/0x1e3 Aug 10 12:15:29 eos kernel: [f885d156] usb_hcd_irq+0x21/0x4e [usbcore] Aug 10 12:15:29 eos kernel: [c014adc5] handle_IRQ_event+0x23/0x51 Aug 10 12:15:29 eos kernel: [c014bfcb] handle_fasteoi_irq+0x86/0xa6 Aug 10 12:15:29 eos kernel: [c0106486] do_IRQ+0x55/0x6f Aug 10 12:15:29 eos kernel: [c012642a] irq_exit+0x53/0x6b Aug 10 12:15:29 eos kernel: [c0114bc2] smp_apic_timer_interrupt+0x71/0x7d Aug 10 12:15:29 eos kernel: [c010475f] common_interrupt+0x23/0x28 Aug 10 12:15:29 eos kernel: === Aug 10 12:15:29 eos kernel: hda: ST380021A, ATA DISK drive later comes up things like: Aug 10 12:15:29 eos kernel: ATA: abnormal status 0x7F on port 0x0001c007 Aug 10 12:15:29 eos kernel: scsi1 : ata_piix Aug 10 12:15:29 eos kernel: ata2.00: ATA-7: ST3250620AS, 3.AAK, max UDMA/133 Aug 10 12:15:29 eos kernel: ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32) Aug 10 12:15:29 eos kernel: ata2.00: qc timeout (cmd 0xef) Aug 10 12:15:29 eos kernel: ata2: failed to recover some devices, retrying in 5 secs Aug 10 12:15:29 eos kernel: ata2.00: qc timeout (cmd 0xef) Aug 10 12:15:29 eos kernel: ata2.00: limiting speed to UDMA/133:PIO3 Aug 10 12:15:29 eos kernel: ata2: failed to recover some devices, retrying in 5 secs Aug 10 12:15:29 eos kernel: ata2.00: qc timeout (cmd 0xef) Aug 10 12:15:29 eos kernel: ata2.00: disabled It comes from this boot messages (ending here by a CTRL-ALT-DEL) # Aug 10 12:15:29 eos syslog-ng[2986]: syslog-ng starting up; version='2.0.0' Aug 10 12:15:29 eos kernel: Linux version 2.6.21-2-686 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Wed Jul 11 03:53:02 UTC 2007 Aug 10 12:15:29 eos kernel: BIOS-provided physical RAM map: Aug 10 12:15:29 eos kernel: sanitize start Aug 10 12:15:29 eos kernel: sanitize end Aug 10 12:15:29 eos kernel: copy_e820_map() start: size: 0009f800 end: 0009f800 type: 1 Aug 10 12:15:29 eos kernel: copy_e820_map() type is E820_RAM Aug 10 12:15:29 eos kernel: copy_e820_map() start: 0009f800 size: 0800 end: 000a type: 2 Aug 10 12:15:29 eos kernel: copy_e820_map() start: 000f size: 0001 end: 0010 type: 2 Aug 10 12:15:29 eos kernel: copy_e820_map() start: 0010 size: 3fef end: 3fff type: 1 Aug 10 12:15:29 eos kernel: copy_e820_map() type is E820_RAM Aug 10 12:15:29 eos kernel: copy_e820_map() start: 3fff size: 3000 end: 3fff3000 type: 4 Aug 10 12:15:29 eos kernel: copy_e820_map() start: 3fff3000 size: d000 end: 4000 type: 3 Aug 10 12:15:29 eos kernel: copy_e820_map() start: fec0 size: 0140 end: 0001 type: 2 Aug 10 12:15:29 eos kernel: BIOS-e820: - 0009f800 (usable) Aug 10 12:15:29 eos kernel: BIOS-e820:
Bug#434242: marked as done (linux-image-2.6.22-1-686: Main battery is not recognized in Asus M6N laptop)
Your message dated Sun, 29 Jun 2008 18:12:52 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.22-1-686: Main battery is not recognized in Asus M6N laptop has caused the Debian Bug report #434242, regarding linux-image-2.6.22-1-686: Main battery is not recognized in Asus M6N 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.) -- 434242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434242 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.22-1-686 Version: 2.6.22-1 Severity: important In linux kernel 2.6.22-1 (but probably also in other versions =2.6.20, I've not checked), the main battery of my Asus laptop is not recognized. In /proc/battery, the only entry is BAT1 (a secondary optional battery which is not present in the laptop). This seems to be a known issue in the mainstream kernel for which a patch exists. This issue is discussed in this thread of the linux kernel mailing list: http://bugzilla.kernel.org/show_bug.cgi?id=8598 and the proposed patch is in http://bugzilla.kernel.org/attachment.cgi?id=11724action=edit It would be useful for many Asus laptop users that this patch be tested and eventually included in the Debian versions of the kernel, in order to restore the battery recognition in recent kernels. -- Package-specific info: ** Version: Linux version 2.6.22-1-686 (Debian 2.6.22-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Sat Jul 21 06:44:36 UTC 2007 ** Not tainted ** Kernel log: iTCO_wdt: Found a ICH4-M TCO device (Version=1, TCOBASE=0x0460) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) Yenta: ISA IRQ mask 0x0008, PCI irq 4 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06 pcmcia: parent PCI bridge I/O window: 0x1000 - 0x1fff cs: IO port probe 0x1000-0x1fff: clean. pcmcia: parent PCI bridge Memory window: 0xff90 - 0xff9f pcmcia: parent PCI bridge Memory window: 0xdea0 - 0xdeaf Yenta: CardBus bridge found at :02:01.1 [1043:1864] Yenta: ISA IRQ mask 0x0008, PCI irq 11 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#02) from #06 to #0a pcmcia: parent PCI bridge I/O window: 0x1000 - 0x1fff cs: IO port probe 0x1000-0x1fff: clean. pcmcia: parent PCI bridge Memory window: 0xff90 - 0xff9f pcmcia: parent PCI bridge Memory window: 0xdea0 - 0xdeaf ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - GSI 4 (level, low) - IRQ 4 PCI: Setting latency timer of device :00:1f.5 to 64 ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmq ipw2200: Copyright(c) 2003-2006 Intel Corporation input: PC Speaker as /class/input/input1 intel_rng: FWH not detected irda_init() NET: Registered protocol family 23 intel8x0_measure_ac97_clock: measured 55452 usecs intel8x0: clocking to 48000 ACPI: PCI Interrupt :00:1f.3[B] - Link [LNKB] - GSI 4 (level, low) - IRQ 4 ACPI: PCI Interrupt :02:02.0[A] - Link [LNKB] - GSI 4 (level, low) - IRQ 4 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels) Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0xa0471b/0x0 input: SynPS/2 Synaptics TouchPad as /class/input/input2 parport_pc 00:08: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] cs: IO port probe 0x100-0x3af: excluding 0x2f8-0x2ff cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 1. nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) IrDA: Registered device irda0 nsc-ircc, Found dongle: HP HSDL-1100/HSDL-2100 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. Adding 979924k swap on /dev/hda5. Priority:-1 extents:1 across:979924k EXT3 FS on hda3, internal journal loop: module loaded Asus Laptop ACPI Extras version 0.30 M6NE model detected, supported device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] fuse init (API version 7.8) kjournald
Bug#427045: marked as done (linux-image-2.6.21-1-686: Cannot find root filesystem under VMWare Server 1.0.3)
Your message dated Sun, 29 Jun 2008 18:12:00 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-1-686: Cannot find root filesystem under VMWare Server 1.0.3 has caused the Debian Bug report #427045, regarding linux-image-2.6.21-1-686: Cannot find root filesystem under VMWare Server 1.0.3 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.) -- 427045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427045 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-1-686 Version: 2.6.21-4 Severity: important When booting this kernel reports that it cannot find the root filesystem (/dev/sda1) and dumps me into a debug shell. I'm using EXT3 and the grub command looks correct (it looks the same as the line for 2.6.18-4-686). I am, however, able to run 2.6.18-4-686, it finds /dev/sda1 with no problem. I'm not running any odd kernel modules except for vmware's. I have vmware tools installed from an older kernel (older than 2.6.18-4-686) so vmware reports my vmware tools as out of date. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-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-image-2.6.21-1-686 depends on: ii initramfs-tools [linux-initr 0.88tools for generating an initramfs ii module-init-tools3.3-pre11-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.21-1-686 recommends: ii libc6-i6862.5-9+b1 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-1-686/postinst/kimage-is-a-directory: linux-image-2.6.21-1-686/prerm/removing-running-kernel-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/lilo-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/elilo-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/depmod-error-2.6.21-1-686: false linux-image-2.6.21-1-686/postinst/old-initrd-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.21-1-686/preinst/abort-overwrite-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/bootloader-error-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/bootloader-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/old-dir-initrd-link-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/bootloader-test-error-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/already-running-this-2.6.21-1-686: linux-image-2.6.21-1-686/prerm/would-invalidate-boot-loader-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/abort-install-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/depmod-error-initrd-2.6.21-1-686: false linux-image-2.6.21-1-686/postinst/old-system-map-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/failed-to-move-modules-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/initrd-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/create-kimage-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/overwriting-modules-2.6.21-1-686: true ---End Message--- ---BeginMessage--- closing as known bug in some vmware server version with buggy scsi driver. was merely put to light by 2.6.21 -- maks ---End Message---
Bug#488546: marked as done (linux-modules-extra-2.6: add dm-raid45 module)
Your message dated Sun, 29 Jun 2008 18:19:16 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#488546: linux-modules-extra-2.6: add dm-raid45 module has caused the Debian Bug report #488546, regarding linux-modules-extra-2.6: add dm-raid45 module 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.) -- 488546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488546 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-modules-extra-2.6 Severity: wishlist Hello, Please consider including dm-raid45 module. http://people.redhat.com/heinzm/sw/dm/dm-raid45/ Feature set: This software extends device-mapper by RAID4 and RAID5 mappings. ---End Message--- ---BeginMessage--- Giuseppe Iuculano wrote: Please consider including dm-raid45 module. http://people.redhat.com/heinzm/sw/dm/dm-raid45/ this package is not part in debian, therefore it cannot be included into the conglomeration package, hence closing this bug. If you want to bring dm-raid45 into Debian, please consider filling a RFP[0] bug. Regards, Daniel [0] http://www.us.debian.org/devel/wnpp/#tag-rfp -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ ---End Message---
Bug#386497: marked as done (linux-image-2.6.17-2-686: oops on boot)
Your message dated Sun, 29 Jun 2008 18:21:51 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.17-2-686: oops on boot has caused the Debian Bug report #386497, regarding linux-image-2.6.17-2-686: oops 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.) -- 386497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386497 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.17-2-686 Severity: important As with #383264, linux-image-2.6.17-2-686 OOPses on boot on a dell poweredge 6400. The machine does use a serial console, but I have not been able to definitively say that booting without a serial console does not cause the issue. I've attached the serial console output from a failed boot. Thanks -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.11 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Sep/08 00:14 am Linux version 2.6.17-2-686 (Debian 2.6.17-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060814 (prerelease) (Debian 4.1.1-11)) #1 SMP Thu Aug 24 23:24:19 UTC 2006 Sep/08 00:14 am BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 0010 - 7fffe000 (usable) BIOS-e820: 7fffe000 - 8000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee1 (reserved) BIOS-e820: fff8 - 0001 (reserved) 895MB HIGHMEM available. 1152MB LOWMEM available. found SMP MP-table at 000fe710 DMI 2.3 present. ACPI: PM-Timer IO Port: 0x808 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x03] enabled) Processor #3 6:10 APIC version 17 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) Processor #2 6:10 APIC version 17 Sep/08 00:14 am ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) Processor #1 6:10 APIC version 17 ACPI: LAPIC (acpi_id[0x04] lapic_id[0x00] enabled) Processor #0 6:10 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep/08 00:14 am ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 4, version 17, address 0xfec0, GSI 0-15 ACPI: IOAPIC (id[0x05] address[0xfec01000] gsi_base[16]) IOAPIC[1]: apic_id 5, version 17, address 0xfec01000, GSI 16-31 Enabling APIC mode: Flat. Using 2 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 8800 (gap: 8000:7ec0) Built 1 zonelists Kernel command line: root=/dev/sda1 ro console=tty0 console=ttyS0,9600n8 Sep/08 00:14 am Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 Sep/08 00:14 am PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 699.507 MHz processor. Sep/08 00:14 am Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Sep/08 00:14 am Memory: 2071048k/2097144k available (1482k kernel code, 24896k reserved, 544k data, 196k init, 917496k highmem) Sep/08 00:14 am Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1399.83 BogoMIPS (lpj=2799669) Sep/08 00:14 am Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 1024K CPU serial number disabled. Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code CPU0: Intel Pentium III (Cascades) stepping 01 SMP alternatives: switching to SMP code Sep/08 00:14 am Booting processor 1/0 eip 3000 Sep/08 00:14 am Initializing CPU#1 Calibrating delay using timer specific routine.. 1398.71 BogoMIPS (lpj=2797422) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 1024K CPU serial number disabled. Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel Pentium III (Cascades) stepping 01 SMP alternatives: switching to SMP code Booting processor 2/1 eip 3000 Initializing CPU#2 Calibrating delay using timer specific routine.. 1398.71
Bug#488546: linux-modules-extra-2.6: add dm-raid45 module
Package: linux-modules-extra-2.6 Severity: wishlist Hello, Please consider including dm-raid45 module. http://people.redhat.com/heinzm/sw/dm/dm-raid45/ Feature set: This software extends device-mapper by RAID4 and RAID5 mappings. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446744: marked as done (linux-image-2.6.18-5-amd64: System fail to boot with linux-image-2.6.8-5-amd64 giving error message: Kernel Panic -)
Your message dated Sun, 29 Jun 2008 18:25:22 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.8-5-amd64 giving error message: Kernel Panic - has caused the Debian Bug report #446744, regarding linux-image-2.6.18-5-amd64: System fail to boot with linux-image-2.6.8-5-amd64 giving error message: 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.) -- 446744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446744 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: critical Justification: breaks the whole system -- 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-4-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-5-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85h tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-5-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/postinst/old-initrd-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/overwriting-modules-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/old-dir-initrd-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-5-amd64/postinst/depmod-error-initrd-2.6.18-5-amd64: false linux-image-2.6.18-5-amd64/postinst/bootloader-test-error-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-5-amd64/preinst/abort-install-2.6.18-5-amd64: The error is somewhat related to bugreport #420754 and #420754, but is this time on a Xeon machine. Rebooting into the 2.6.18-4-amd64 kernel goes perfectly fine. ---End Message--- ---BeginMessage--- closing as missing any info + requested ones. -- maks ---End Message---
Bug#416393: marked as done (BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug())
Your message dated Sun, 29 Jun 2008 18:28:42 +0200 with message-id [EMAIL PROTECTED] and subject line Re: BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug() has caused the Debian Bug report #416393, regarding BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug() 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.) -- 416393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416393 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6 Severity: normal Tags: patch I've found the following in logs, can't tell when it really happened and what caused it: BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug() Call Trace: [8029478d] unlock_cpu_hotplug+0x3f/0x6c [882552a7] :cpufreq_ondemand:do_dbs_timer+0x119/0x171 [8024947a] run_workqueue+0x94/0xe5 [80245e7b] worker_thread+0x0/0x122 [802901be] keventd_create_kthread+0x0/0x61 [80245f6b] worker_thread+0xf0/0x122 [8027d27d] default_wake_function+0x0/0xe [802901be] keventd_create_kthread+0x0/0x61 [802901be] keventd_create_kthread+0x0/0x61 [8023055a] kthread+0xd4/0x107 [80259360] child_rip+0xa/0x12 [802901be] keventd_create_kthread+0x0/0x61 [80230486] kthread+0x0/0x107 [80259356] child_rip+0x0/0x12 System is still running, so it's not that serious, but still annoying. I've searched a bit and found a patch, that might fix this, it's applied in current Linus tree: http://lkml.org/lkml/2007/2/16/4 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6-amd64 depends on: ii linux-image-2.6.18-4-am 2.6.18.dfsg.1-11 Linux 2.6.18 image on AMD64 linux-image-2.6-amd64 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.20-1 fixed upstream in 2.6.19, which never was in unstable thus marking as fixed of 2.6.20. just an harmless bug and thus not candidate for backport, checkout etch + half that has 2.6.24 - http://wiki.debian.org/EtchAndAHalf -- maks ---End Message---
Bug#404823: marked as done (Usb devices doesn't work)
Your message dated Sun, 29 Jun 2008 18:24:08 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Usb devices doesn't work has caused the Debian Bug report #404823, regarding Usb devices doesn't work 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.) -- 404823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404823 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18-3-amd64 Severity: grave Justification: renders system unusable I've just installed Debian Etch for amd64. The boot process sleep 2 times for about 5 minutes. My usb device doesn't work, they aren't powered. My motherboard is an Asus A8V Deluxe. I've used a lot of distros and Debian worked. The installer works. I can't give you any other information because I've only usb mouse and keyboard, and ssh is not installed. Say what you need for solve this. I'll get ps2 keyboard in the less time possible. ---End Message--- ---BeginMessage--- closing as no real info was provided. thanks nevertheless -- maks ---End Message---
Bug#433597: marked as done (linux-image-2.6.18-4-amd64: Panic with CR2: 0000000000100108 on SATA with software raid-1)
Your message dated Sun, 29 Jun 2008 18:44:49 +0200 with message-id [EMAIL PROTECTED] and subject line re: linux-image-2.6.18-4-amd64: Panic with CR2: 00100108 on SATA with software raid-1 has caused the Debian Bug report #433597, regarding linux-image-2.6.18-4-amd64: Panic with CR2: 00100108 on SATA with software raid-1 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.) -- 433597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433597 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-12etch2 Severity: critical Tags: patch Justification: breaks the whole system The problem only happened to me once, and before my last upgrade (with version 2.6.18.dfsg.1-12), but the changelog does not seem to indicate that this problem was solved, so I'm opening the bug report anyways. The machine is running two SATA disks with Raid-1 and LVM. This seems to be relevant to some of the internet discussions I found, though not all of them. I was connected to the machine over SSH (a remote machine) when I got the following messages: Message from [EMAIL PROTECTED] at Tue Jul 17 22:10:04 2007 ... fiasco kernel: Oops: 0002 [1] SMP Message from [EMAIL PROTECTED] at Tue Jul 17 22:10:04 2007 ... fiasco kernel: CR2: 00100108 After that, no user space program would interact with me, but pings still worked. The machine was rebooted by the hosting company, and now seem to be functioning again. Searching the internet I found two discussions that may be relevant. One is http://lists.openwall.net/linux-kernel/2006/11/04/69, which includes a patch, and the other is http://lkml.org/lkml/2006/1/4/196. Since the machine has been up for almost a year before this problem happened, and from the version numbers and frequencies mentioned by Linus, I believe that the first link contains the solution to this problem. Thanks, Shachar -- 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-4-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=he_IL (charmap=ISO-8859-8) Versions of packages linux-image-2.6.18-4-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85g tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-4-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true * linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/bootloader-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-system-map-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/bootloader-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/overwriting-modules-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/elilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/would-invalidate-boot-loader-2.6.18-4-amd64: true ---End Message--- ---BeginMessage--- Version: 2.6.24-1 no evidence that the seen oops corresponds to http://lists.openwall.net/linux-kernel/2006/11/04/69 also not really a backport fix if not yet done, please checkout etch + half 2.6.24 kernel http://wiki.debian.org/EtchAndAHalf -- maks ---End Message---
Bug#487287: acpi: Negative value is show for temperature, fan constantly on
On Sun, Jun 29, 2008 at 05:17:07PM +0200, Adolf Winterer wrote:
Am Sonntag, 22. Juni 2008 12:48 schrieb Michael Meskes:
On Sun, Jun 22, 2008 at 10:43:25AM +0200, Adolf Winterer wrote:
The directory /sys/class/thermal does not exist.
Which kernel do you run? Looks like a strange configuration here.
Look at the temperature!
$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature: -73 C
Yes, it reports a negative temperature. But this is reported by the
kernel. acpi only reads this information and displays it. The problem
doesn't seem to be in acpi, but in the kernel itself.
I did some more research regarding ACPI and found out that on both systems
there is a flawed ACPI DSDT.
Using acpidump I stored the DSDT into a file and disassembled it with iasl.
When comiling the file back into a binary file I get one warning and two
errors on both systems which look quite similar.
# iasl -sa dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20061109 [May 15 2007]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt.dsl 378: Method (\_WAK, 1, NotSerialized)
Warning 1079 - ^ Reserved method must return a value (_WAK)
dsdt.dsl 419: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
dsdt.dsl 424: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
ASL Input: dsdt.dsl - 5129 lines, 163766 bytes, 1797 keywords
Compilation complete. 2 Errors, 1 Warnings, 0 Remarks, 571 Optimizations
I found a suggestion how to fix the warning, but did not find anything for
the
errors. The code looks like that:
Scope (\_SI)
{
Method (_MSG, 1, NotSerialized)
{
Store (Local0, Local0)
}
Method (_SST, 1, NotSerialized)
{
Store (Local0, Local0)
}
}
I do not understand a single word from it, so there is not a real chance to
fix it myself.
Some time ago I read about a DSDT fix that has been removed from the kernel,
but I do not know if this is related to the problem we see here.
please report bug upstream in bugzilla.kernel.org one shouldn't need to
fiddle with DSDT tables.
and please let us know the upstream bug number.
thanks
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: merge
Processing commands for [EMAIL PROTECTED]: reassign 487953 cman Bug#487953: fails to install Bug reassigned from package `ccs' to `cman'. fixed 487953 2.20071214-1 Bug#487953: fails to install Bug marked as fixed in version 2.20071214-1. merge 471398 487953 Bug#471398: ccs: /etc/cluster/cluster.conf: file not found (broken on clean install) Bug#487953: fails to install Merged 471398 487953. 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#482100: linux-image-2.6.25-3-686-bigmem : Complete system freeze
[ please keep bug report on cc ] On Sun, Jun 29, 2008 at 06:27:06PM +0100, [EMAIL PROTECTED] wrote: Hi, I got tired of freezing my computers (the two which have issues with the 2.6.25 kernel) so I'm still on 2.6.24 on one of those boxes. I migrated from x86 to x86-64, but still got the same problem with 2.6.25 kernels. The last I tried was 2.6.25-6-amd64 from Debian package, stock one and two custom compiled, just to get the same result. The best I could obtain was about 72 hours of uptime with a custom compil before the freeze eventually occurred... :-\ Since I had trouble with Virtualbox too in Lenny, which I heavily depends on, I migrated one box to Ubuntu 8.04 (with most conf files). I tried compiling a 2.6.25 kernel, and even backporting the Intrepid Ibex first alpha kernel (2.6.26-*) and had no problem at all, so I think those two boxes are going to run Ubuntu from now on. I tried OpenSuse11, which is running a 2.6.25 kernel, from a live-cd and had no problem, no lost interrupts in the logs like with Debian... I really can't figure out what's going wrong with Debian setup, I tried so many configurations, disabling all acpi, disabling cpu frequency scalling, SLUB instead of SLAB memory allocator, ...etc, and still got the nasty freezes. So I'm just tired of this and I'm giving up on Debian for those two boxes. Regards, Tom that's quite sad but as aboves gives no hint on where we would perform that badly nor why those freezes that i cant reproduce happen. i'd have to close the bug. the only big difference i know about our kernels is that ubuntu uses a pata driver instead of the old ide ones. could that make the difference? best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 483489
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 483489 + pending Bug#483489: linux-2.6: Optional powerpc64 patches for PS3 Tags were: wontfix 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#435413: #435413 oops when Windows server sent bad domain name null terminator
hmm the bug report was not quite clear what the resulting rh fix is: 8e6f195af0e1f226e9b2e0256af8df46adb9d595 guess that could be a 2.6.18 backport cnadidate? on the other hand one could argue that 2.6.18 cifs sucked anyway. so leaving the decision on you, thanks for evaluating. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#436260 closed by maximilian attems [EMAIL PROTECTED] (Re: linux-support-2.6.22-1: Support for exernal module packages broken)
Processing commands for [EMAIL PROTECTED]: reopen 436260 Bug#436260: linux-support-2.6.22-1: Support for exernal module packages broken 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]
Processed: bug 488566 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10743
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.31 forwarded 488566 http://bugzilla.kernel.org/show_bug.cgi?id=10743 Bug#488566: linux-image-2.6.25-2-686: Corrupt writes with SATA DVD writer on VIA hardware Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10743. 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#488566: linux-image-2.6.25-2-686: Corrupt writes with SATA DVD writer on VIA hardware
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Severity: important Hi, DVDs and CDs written with a SATA writer connected to a VIA VT8237 SATA controller ends up corrupt. This bug is particularly nasty as the discs appears to be written correctly, but are unreadable. This problem has already been reported in the upstream bug tracker with more details; http://bugzilla.kernel.org/show_bug.cgi?id=10743 -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 03:23:20 UTC 2008 ** Command line: root=/dev/sda2 ro vga=794 resume=/dev/sda5 ** Not tainted ** Kernel log: [ 30.366764] Bluetooth: RFCOMM TTY layer initialized [ 30.370716] Bluetooth: RFCOMM ver 1.8 [ 31.772037] [drm] Initialized drm 1.1.0 20060810 [ 31.782618] ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16 [ 31.782735] [drm] Initialized radeon 1.28.0 20060524 on minor 0 [ 33.192954] agpgart: Found an AGP 3.5 compliant device at :00:00.0. [ 33.192987] agpgart: Device is in legacy mode, falling back to 2.x [ 33.192993] agpgart: Putting AGP V2 device at :00:00.0 into 4x mode [ 33.193039] agpgart: Putting AGP V2 device at :01:00.0 into 4x mode [ 33.496801] [drm] Setting GART location based on new memory map [ 33.496801] [drm] Loading R200 Microcode [ 33.496801] [drm] writeback test succeeded in 1 usecs [ 38.979361] ip_tables: (C) 2000-2006 Netfilter Core Team [ 47.166620] eth0: no IPv6 routers present [ 1063.036217] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 1063.054093] ISO 9660 Extensions: RRIP_1991A [ 2061.195123] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 2061.201843] ISO 9660 Extensions: RRIP_1991A [ 2120.213693] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 2120.215120] ISO 9660 Extensions: RRIP_1991A [ 2134.682432] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2134.682432] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2134.682432] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2134.682432] end_request: I/O error, dev sr0, sector 343900 [ 2134.682432] Buffer I/O error on device sr0, logical block 85975 [ 2134.682432] Buffer I/O error on device sr0, logical block 85976 [ 2134.682451] Buffer I/O error on device sr0, logical block 85977 [ 2134.682455] Buffer I/O error on device sr0, logical block 85978 [ 2142.816985] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2142.816985] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2142.816985] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2142.816985] end_request: I/O error, dev sr0, sector 343900 [ 2142.816985] Buffer I/O error on device sr0, logical block 85975 [ 2150.751132] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2150.751145] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2150.751150] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2150.751159] end_request: I/O error, dev sr0, sector 343904 [ 2150.751165] Buffer I/O error on device sr0, logical block 85976 [ 2158.651223] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2158.651238] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2158.651243] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2158.651253] end_request: I/O error, dev sr0, sector 1041424 [ 2158.651258] Buffer I/O error on device sr0, logical block 260356 [ 2158.651269] Buffer I/O error on device sr0, logical block 260357 [ 2158.651276] Buffer I/O error on device sr0, logical block 260358 [ 2158.651279] Buffer I/O error on device sr0, logical block 260359 [ 2158.651283] Buffer I/O error on device sr0, logical block 260360 [ 2158.651286] Buffer I/O error on device sr0, logical block 260361 [ 2158.651290] Buffer I/O error on device sr0, logical block 260362 [ 2158.651293] Buffer I/O error on device sr0, logical block 260363 [ 2167.021202] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2167.021202] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2167.021202] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2167.021202] end_request: I/O error, dev sr0, sector 1041424 [ 2167.021202] Buffer I/O error on device sr0, logical block 260356 [ 2175.241031] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2175.241031] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2175.241031] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2175.241031] end_request: I/O error, dev sr0, sector 1041428 [ 2175.241031] Buffer I/O error on device sr0, logical block 260357 [ 2183.306856] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 2183.306856] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2183.306856] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit [ 2183.306856]
Bug#436260: closed by maximilian attems [EMAIL PROTECTED] (Re: linux-support-2.6.22-1: Support for exernal module packages broken)
reopen 436260 thanks On Sun, Jun 29, 2008 at 03:48:07PM +, Debian Bug Tracking System wrote: closing as this general assumption seems not true quite a bunch of external modules is build. As far as I remember (this was all quite some time ago) the external module packages were all using forked copies of this code; IIRC the patch I have provided largely merged these in. also report against old version. That's because I've not seen any response to this report in the intervening period of time. It's possible that you've provided a suitable interface in the meantime but it's possible that this was resolved - I seem to remember that many of the packages didn't build at the time. I'd at least like to see some sort of response to the patch I've provided and discussion as to how this has been resolved. -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 436260
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 tags 436260 - patch Bug#436260: linux-support-2.6.22-1: Support for exernal module packages broken Tags were: patch Tags removed: patch 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: bug 488566 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10743
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 forwarded 488566 http://bugzilla.kernel.org/show_bug.cgi?id=10743 Bug#488566: linux-image-2.6.25-2-686: Corrupt writes with SATA DVD writer on VIA hardware Forwarded-to-address changed from http://bugzilla.kernel.org/show_bug.cgi?id=10743 to http://bugzilla.kernel.org/show_bug.cgi?id=10743. 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#436260: closed by maximilian attems [EMAIL PROTECTED] (Re: linux-support-2.6.22-1: Support for exernal module packages broken)
On Sun, Jun 29, 2008 at 08:42:11PM +0100, Mark Brown wrote: As far as I remember (this was all quite some time ago) the external module packages were all using forked copies of this code; IIRC the patch I have provided largely merged these in. hmm reopening a but on a wrong fact. i strongly disagree. also report against old version. That's because I've not seen any response to this report in the intervening period of time. It's possible that you've provided a suitable interface in the meantime but it's possible that this was resolved - I seem to remember that many of the packages didn't build at the time. I'd at least like to see some sort of response to the patch I've provided and discussion as to how this has been resolved. there was no patch provided nor any proof of any trouble by your side, so tagging with moreinfo and willl close in 10 days unless something substantial comes up. 2.6.22 is really old and keeping cruft lying around helps noone. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 475319 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10448
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 forwarded 475319 http://bugzilla.kernel.org/show_bug.cgi?id=10448 Bug#475319: linux-2.6: loading video kernel module causes Samsung Q45 to freeze Forwarded-to-address changed from [EMAIL PROTECTED] to http://bugzilla.kernel.org/show_bug.cgi?id=10448. 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: found 462711 in 2.6.25-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.30 found 462711 2.6.25-1 Bug#462711: linux-2.6: ath5k fails to resume from suspend to RAM 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]
Bug#487287: acpi: Negative value is show for temperature, fan constantly on
Am Sonntag, 29. Juni 2008 17:53 schrieb maximilian attems:
On Sun, Jun 29, 2008 at 05:17:07PM +0200, Adolf Winterer wrote:
Am Sonntag, 22. Juni 2008 12:48 schrieb Michael Meskes:
On Sun, Jun 22, 2008 at 10:43:25AM +0200, Adolf Winterer wrote:
The directory /sys/class/thermal does not exist.
Which kernel do you run? Looks like a strange configuration here.
Look at the temperature!
$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature: -73 C
Yes, it reports a negative temperature. But this is reported by the
kernel. acpi only reads this information and displays it. The problem
doesn't seem to be in acpi, but in the kernel itself.
I did some more research regarding ACPI and found out that on both
systems there is a flawed ACPI DSDT.
Using acpidump I stored the DSDT into a file and disassembled it with
iasl. When comiling the file back into a binary file I get one warning
and two errors on both systems which look quite similar.
# iasl -sa dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20061109 [May 15 2007]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt.dsl 378: Method (\_WAK, 1, NotSerialized)
Warning 1079 - ^ Reserved method must return a value
(_WAK)
dsdt.dsl 419: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
dsdt.dsl 424: Store (Local0, Local0)
Error4049 - ^ Method local variable is not
initialized (Local0)
ASL Input: dsdt.dsl - 5129 lines, 163766 bytes, 1797 keywords
Compilation complete. 2 Errors, 1 Warnings, 0 Remarks, 571 Optimizations
I found a suggestion how to fix the warning, but did not find anything
for the errors. The code looks like that:
Scope (\_SI)
{
Method (_MSG, 1, NotSerialized)
{
Store (Local0, Local0)
}
Method (_SST, 1, NotSerialized)
{
Store (Local0, Local0)
}
}
I do not understand a single word from it, so there is not a real chance
to fix it myself.
Some time ago I read about a DSDT fix that has been removed from the
kernel, but I do not know if this is related to the problem we see here.
please report bug upstream in bugzilla.kernel.org one shouldn't need to
fiddle with DSDT tables.
and please let us know the upstream bug number.
For your reference, the bug number is 11010.
http://bugzilla.kernel.org/show_bug.cgi?id=11010
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487176: closed by maximilian attems [EMAIL PROTECTED] (Re: linux-image-2.6.18-6-686: open sleeps)
Debian Bug Tracking System wrote: Version: 2.6.24-1 fixed in newer vfs. not a candidate for backport. use etch + half kernel - http://wiki.debian.org/EtchAndAHalf I had forgotten I filled this report. Every indication seems to be that it is the firewall in the virus scanner we use, F-Secure, that prevents Windows from releasing oplocks properly. After turning off the firewall, the oplocks get released and there is no problem. Possibly related to the timing of wpkg being invoked before system logons too. So probably not a bug as opposed to fixed in newer vfs ;-) Brian May -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
