Bug#397616: marked as done ([arm] /proc/cpu/alignment should default to warn and fixup on arm)
Your message dated Sun, 3 Aug 2008 09:04:12 +0300 with message-id [EMAIL PROTECTED] and subject line Re: Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm has caused the Debian Bug report #397616, regarding [arm] /proc/cpu/alignment should default to warn and fixup on arm 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.) -- 397616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397616 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Severity: normal Hi, By default the ARM kernel just ignores unaligned accesses from userspace and can just accesses another address then actually specified. This can cause strange behaviour by userspace programs. While i agree that these programs are somewhat buggy, but doing something undefined and not telling anyone doesn't seem like a good strategy :) Some discussion on #debian-arm indicates that it the current default made some sense in the old days. Where some programs actually relied on the behaviour and the amount of buggy programs was so big that it actually caused a flood of warnings. Times have changed though, no applications in debian should depend on this behaviour and turning on warn+fixup doesn't seem cause a flood anymore. Most problemeatic should have been fixed by now, as on Sparc you'll get a sigbus on unaligned access and iirc Alpha gives a warning about it. For reference, i discovered this issue because powerdns on my arm was giving out weird SOA records. So enabling fixup does solves real problems or at least shows where they are :) (Yes i've already patched pdns and will be sending the patch out after some more testing) Sjoerd -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (101, 'unstable') Architecture: arm (armv5tel) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-iop32x Locale: LANG=C, LC_CTYPE=nl_NL (charmap=ISO-8859-1) ---End Message--- ---BeginMessage--- * Martin Michlmayr [EMAIL PROTECTED] [2008-05-06 17:40]: 2) warnings can cause bad side-effects (imagine a unaligned error in sysklogd..) http://thread.gmane.org/gmane.linux.ports.arm.kernel/34044 I think that's a good argument for not changing the upstream default. So I think we should close this bug report and someone should take this up with upstream (not me). Any volunteers? Someone tried to raise this with upstream recently; here's the reply: http://lists.arm.linux.org.uk/lurker/message/20080801.160843.c7b80fb6.en.html Closing this bug report. -- Martin Michlmayr http://www.cyrius.com/ ---End Message---
Processed: Re: Bug#493415: linux-image-2.6.18: Kernel BUG when mobile phone is connected
Processing commands for [EMAIL PROTECTED]: reassign 493415 linux-2.6 Bug#493415: linux-image-2.6.18: Kernel BUG when mobile phone is connected Warning: Unknown package 'linux-image-2.6.18' Bug reassigned from package `linux-image-2.6.18' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFC] kernel update to 2.6.26
* Otavio Salvador [EMAIL PROTECTED] [2008-08-02 14:17]: - isofs droped (mips) Apparently isofs is built into the kernel on r4k-ip22 and sb1-bcm91250a. I'll change this for 2.6.27, but this is fine for now. - pata modules droped (armel) On the ixp4xx platform, yes. This was intentional. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493415: linux-image-2.6.18: Kernel BUG when mobile phone is connected
Package: linux-image-2.6.18 Version: linux-headers-2.6.18-6-k7 Severity: normal Kernel bug occurs when Nokia 6233 is connected via USB. Didn't happen in 2.6.18-5-k7. System won't boot when phone is plugged in, will hang during boot sequence (i.e. will hang before kernel gets tainted by nvidia module). /var/log/syslog: Aug 2 17:13:21 haktar kernel: [ cut here ] Aug 2 17:13:21 haktar kernel: kernel BUG at mm/slab.c:595! Aug 2 17:13:21 haktar kernel: invalid opcode: [#1] Aug 2 17:13:21 haktar kernel: SMP Aug 2 17:13:21 haktar kernel: Modules linked in: rndis_host cdc_ether usbnet cdc_acm nls_utf8 nls_cp437 vfat fat usb_storage vmnet vmmon nvidia agpgart i2c_core nfs lockd nfs_acl sunrpc ipv6 lp button ac battery sg ppdev loop snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep snd rtc parport_pc parport usblp floppy emu10k1_gp psmouse soundcore pcspkr gameport serio_raw evdev ext3 jbd mbcache sha256 aes dm_crypt dm_mirror dm_snapshot dm_mod ide_generic ide_cd cdrom sd_mod amd74xx ohci_hcd sata_nv libata scsi_mod ehci_hcd 3c59x mii generic ide_core usbcore thermal processor fan Aug 2 17:13:21 haktar kernel: CPU:0 Aug 2 17:13:21 haktar kernel: EIP:0060:[c015733f]Tainted: P VLI Aug 2 17:13:21 haktar kernel: EFLAGS: 00010006 (2.6.18-6-k7 #1) Aug 2 17:13:21 haktar kernel: EIP is at kfree+0x2e/0x65 Aug 2 17:13:21 haktar kernel: eax: 8060 ebx: e6edb300 ecx: d6c0 edx: c14ddac0 Aug 2 17:13:21 haktar kernel: esi: 0286 edi: e6ed62bb ebp: e6edb000 esp: d0b39e14 Aug 2 17:13:21 haktar udevd-event[9510]: run_program: '/sbin/modprobe' abnormal exit Aug 2 17:13:21 haktar kernel: ds: 007b es: 007b ss: 0068 Aug 2 17:13:21 haktar kernel: Process modprobe (pid: 9517, ti=d0b38000 task=cf4e task.ti=d0b38000) Aug 2 17:13:21 haktar kernel: Stack: e6edb300 f8ddb62e e6edb006 f8ddb02d d89fc000 f8c8c6a0 ef911f08 df957c00 Aug 2 17:13:21 haktar kernel:ff92 dfa5d400 0001 0001 0001 0001 Aug 2 17:13:21 haktar kernel:f8c8c660 d89fc000 f8c8d520 f8c8d550 c0213742 f8862ceb d89fc014 d89fc014 Aug 2 17:13:21 haktar kernel: Call Trace: Aug 2 17:13:21 haktar kernel: [f8ddb02d] usbnet_probe+0x4ea/0x4ff [usbnet] Aug 2 17:13:21 haktar kernel: [c0213742] __driver_attach+0x0/0x5d Aug 2 17:13:21 haktar kernel: [f8862ceb] usb_probe_interface+0x58/0x85 [usbcore] Aug 2 17:13:21 haktar kernel: [c021369d] driver_probe_device+0x42/0x91 Aug 2 17:13:21 haktar kernel: [c021377a] __driver_attach+0x38/0x5d Aug 2 17:13:21 haktar kernel: [c02131bc] bus_for_each_dev+0x37/0x59 Aug 2 17:13:21 haktar kernel: [c0213607] driver_attach+0x11/0x13 Aug 2 17:13:21 haktar kernel: [c0213742] __driver_attach+0x0/0x5d Aug 2 17:13:21 haktar kernel: [c0212ecb] bus_add_driver+0x6b/0xfd Aug 2 17:13:21 haktar kernel: [f8862b23] usb_register_driver+0x60/0xbb [usbcore] Aug 2 17:13:21 haktar NetworkManager: debug info^I[1217690001.343841] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_421_491_noserial_if9'). Aug 2 17:13:21 haktar kernel: [c0135ca3] sys_init_module+0x1732/0x18b5 Aug 2 17:13:21 haktar kernel: [c0116755] __wake_up+0x2a/0x3d Aug 2 17:13:21 haktar kernel: [c0102bed] sysenter_past_esp+0x56/0x79 Aug 2 17:13:21 haktar kernel: Code: 89 c7 56 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e2 05 03 15 90 23 37 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 0f 0b 53 02 81 e0 29 c0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10 Aug 2 17:13:21 haktar kernel: EIP: [c015733f] kfree+0x2e/0x65 SS:ESP 0068:d0b39e14 Cheers Jan -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#493518: Kernel freeze due to sky2 network driver
Processing commands for [EMAIL PROTECTED]: forwarded 493518 http://bugzilla.kernel.org/show_bug.cgi?id=11196 Bug#493518: Kernel freeze due to sky2 network driver Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11196. kthxbye 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#493518: Kernel freeze due to sky2 network driver
forwarded 493518 http://bugzilla.kernel.org/show_bug.cgi?id=11196 kthxbye On Sun, Aug 3, 2008 at 1:20 AM, [EMAIL PROTECTED] wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 As suggested in the kernel bugzilla, install 2.6.26 since it was already uploaded in Debian too. This is the version that will probably be released in lenny. You can submit any new info at that bug report and the resolution will be followed in debian BTS. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493540: linux-image-2.6.25-2-686-bigmem: fails to copy files/directories on USB storage media
On Sun, Aug 3, 2008 at 7:34 AM, Stefan Oschkera [EMAIL PROTECTED] wrote: Package: linux-image-2.6.25-2-686-bigmem Version: 2.6.25-7 Severity: critical Justification: causes serious data loss Most probably this bug report is similar to #485692 but this one refers to the linux-image-2.6.25-2-686-bigmem-package: Test if this is also the case with 2.6.26 which was uploaded to unstable. This is the version that will probably be released in lenny. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 493540 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 493540 important Bug#493540: linux-image-2.6.25-2-686-bigmem: fails to copy files/directories on USB storage media Severity set to `important' from `critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493540: linux-image-2.6.25-2-686-bigmem: fails to copy files/directories on USB storage media
Hi Teodor, As suggested, I've installed the 2.6.26 kernel using the linux-image-2.6.26-1-686-bigmem_2.6.26-1_i386.deb package from unstable, unfortunately with identical results. For testing purposes I even switched the video-driver from nvidia to nv to avoid any potential conflicts. Same results. I'm afraid even the latest 2.6.26 kernel does not resolve the problem. Regards, Stefan Test if this is also the case with 2.6.26 which was uploaded to unstable. This is the version that will probably be released in lenny. Thanks -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Severity: normal Hi, When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. When I look in /dev, the /dev/rtc* device is not there. The device was working OK with the 2.6.25 kernel. It seems CONFIG_RTC is no longer set in the 2.6.26 config? It seems is was unset to fix #476970 to allow more specific modules to load. When I loaded the rtc_cmos driver, hwclock worked OK. Should the kernel/udev not load this/the correct module automatically? Regards, Rik -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 18:46:19 UTC 2008 ** Command line: root=/dev/mapper/vg00-root ro vga=791 quiet ** Tainted: P (1) ** Kernel log: [ 14.328154] ACPI: Power Button (CM) [PBTN] [ 14.331011] input: Sleep Button (CM) as /class/input/input5 [ 14.360464] ACPI: PCI Interrupt :00:1f.3[B] - GSI 17 (level, low) - IRQ 17 [ 14.394842] ACPI: Sleep Button (CM) [SBTN] [ 14.736027] ACPI: AC Adapter [AC] (off-line) [ 14.740446] ACPI: WMI: Mapper loaded [ 14.749216] ACPI: device:2f is registered as cooling_device2 [ 14.749941] input: Video Bus as /class/input/input6 [ 14.807051] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 14.868341] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 14.868839] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 14.868839] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 14.868839] PCI: Setting latency timer of device :0c:00.0 to 64 [ 14.868839] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 14.944843] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 14.956259] phy0: Selected rate control algorithm 'iwl-3945-rs' [ 14.970388] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x20 [ 15.007498] input: SynPS/2 Synaptics TouchPad as /class/input/input7 [ 15.096096] ACPI: PCI interrupt for device :0c:00.0 disabled [ 15.348674] ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 [ 15.360525] PCI: Setting latency timer of device :00:1b.0 to 64 [ 15.369837] Error: Driver 'pcspkr' is already registered, aborting... [ 17.355844] EXT3 FS on dm-1, internal journal [ 17.644038] loop: module loaded [ 19.447922] fuse init (API version 7.9) [ 19.536452] kjournald starting. Commit interval 5 seconds [ 19.551061] EXT3 FS on sda5, internal journal [ 19.562835] EXT3-fs: mounted filesystem with ordered data mode. [ 19.611771] kjournald starting. Commit interval 5 seconds [ 19.621836] EXT3 FS on dm-3, internal journal [ 19.633572] EXT3-fs: mounted filesystem with ordered data mode. [ 19.699688] Adding 4194296k swap on /dev/mapper/vg00-swap. Priority:-1 extents:1 across:4194296k [ 21.069599] ip_tables: (C) 2000-2006 Netfilter Core Team [ 21.751955] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 21.763920] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 21.764196] firmware: requesting iwlwifi-3945-1.ucode [ 22.011728] Registered led device: iwl-phy0:radio [ 22.025107] Registered led device: iwl-phy0:assoc [ 22.036883] Registered led device: iwl-phy0:RX [ 22.048419] Registered led device: iwl-phy0:TX [ 22.123235] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 24.589087] NET: Registered protocol family 10 [ 24.589087] lo: Disabled Privacy Extensions [ 24.589087] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 24.589397] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 27.891554] wlan0: Initial auth_alg=0 [ 27.891554] wlan0: authenticate with AP 00:0f:cb:fc:04:ea [ 27.893034] wlan0: RX authentication from 00:0f:cb:fc:04:ea (alg=0 transaction=2 status=0) [ 27.893034] wlan0: authenticated [ 27.893034] wlan0: associate with AP 00:0f:cb:fc:04:ea [ 27.980019] wlan0: RX AssocResp from 00:0f:cb:fc:04:ea (capab=0x431 status=0 aid=1) [ 27.980019] wlan0: associated [ 27.980555] wlan0: switched to short barker preamble (BSSID=00:0f:cb:fc:04:ea) [ 27.980555] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 31.549631] pnp: the driver 'parport_pc' has been registered [ 31.550257] lp: driver loaded but no devices found [ 31.594146] ppdev: user-space parallel port driver [ 37.385590] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 38.829547] wlan0: no IPv6 routers present [ 39.959410] Bluetooth: Core ver 2.11 [ 39.975411] NET: Registered protocol family 31 [ 39.988073] Bluetooth: HCI device and connection manager initialized [ 39.998087] Bluetooth: HCI socket layer initialized [ 40.055994] Bluetooth: L2CAP ver 2.9 [ 40.067295] Bluetooth: L2CAP socket layer initialized
Processed (with 1 errors): Re: Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Processing commands for [EMAIL PROTECTED]: notfixed 476970 2.6.26-1 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug no longer marked as fixed in version 2.6.26-1. reopen 476970 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug reopened, originator not changed. tags 476970 - pending Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Tags were: pending Tags removed: pending found 476970 2.6.26-1 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug marked as found in version 2.6.26-1. severity 493567 important Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Severity set to `important' from `normal' merge 476970 493567 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #476970 has `linux-2.6'; #493567 has `linux-image-2.6.26-1-amd64' tags 493567 + confirmed Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. There were no tags set. Tags added: confirmed kthxbye 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#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
notfixed 476970 2.6.26-1 reopen 476970 tags 476970 - pending found 476970 2.6.26-1 severity 493567 important merge 476970 493567 tags 493567 + confirmed kthxbye On Sun, Aug 3, 2008 at 1:00 PM, Rik Theys [EMAIL PROTECTED] wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. piti:~# hwclock --debug --show hwclock from util-linux-ng 2.13.1.1 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory. No usable clock interface found. Cannot access the Hardware Clock via any known method. It seems CONFIG_RTC is no longer set in the 2.6.26 config? It seems is was unset to fix #476970 to allow more specific modules to load. In 2.6.25 we have CONFIG_RTC=y, but on 2.6.26 this is not even selected as a module. Please select both CONFIG_RTC and CONFIG_GEN_RTC as modules. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Processing commands for [EMAIL PROTECTED]: tags 476970 + confirmed Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. There were no tags set. Tags added: confirmed reassign 493567 linux-2.6 Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Bug reassigned from package `linux-image-2.6.26-1-amd64' to `linux-2.6'. merge 476970 493567 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Merged 476970 493567. kthxbye 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#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
unmerge 476970 fixed 476970 2.6.26-1 tags 476970 pending severity 493567 normal tags 493567 - confirmed thanks On Sun, Aug 03, 2008 at 02:26:56PM +0300, Teodor wrote: notfixed 476970 2.6.26-1 reopen 476970 tags 476970 - pending found 476970 2.6.26-1 severity 493567 important merge 476970 493567 tags 493567 + confirmed kthxbye _STOP_ messing with bugs. The original bug was fixed. You are neither a maintainer of the kernel nor a submitter of any of this bugs. Bastian -- It is a human characteristic to love little animals, especially if they're attractive in some way. -- McCoy, The Trouble with Tribbles, stardate 4525.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Processing commands for [EMAIL PROTECTED]: unmerge 476970 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Disconnected #476970 from all other report(s). fixed 476970 2.6.26-1 Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Bug marked as fixed in version 2.6.26-1. tags 476970 pending Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into kernel, should be compiled as a module. Tags were: confirmed Tags added: pending severity 493567 normal Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Severity set to `normal' from `important' tags 493567 - confirmed Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded. Tags were: confirmed Tags removed: confirmed 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#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: - RTC_CLASS=y - RTC_HCTOSYS=y - RTC_DRV_CMOS=y Bastian -- Conquest is easy. Control is not. -- Kirk, Mirror, Mirror, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 3, 2008 at 3:21 PM, Bastian Blank [EMAIL PROTECTED] wrote: _STOP_ messing with bugs. The original bug was fixed. You are neither a maintainer of the kernel nor a submitter of any of this bugs. Ok, I stand corrected since you know better. I apologize for any trouble created, it wasn't my intention. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i386.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Bastian -- We fight only when there is no other choice. We prefer the ways of peaceful contact. -- Kirk, Spectre of the Gun, stardate 4385.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493479: linux-image-2.6.26-1-amd64: Found boot parameters which allow stock kernel to boot
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Followup-For: Bug #493479 I worked on finding a config for 2.6.26 last night that would allow it to boot, until I got too tired to continue. As mentioned previously, the stock kernel freezes on this system early during the boot process; my own custom kernels, using previously working configurations used with 2.6.25 as a starting basis (with 'make oldconfig'), also freeze early in boot. I found that by removing a great many configuration options, turning off many major subsystems, I was able to build a kernel that would avoid the early freeze. However, because I had turned off Unix Domain Sockets, udev was unable to run and populate /dev. So I wasted a lot of time trying to find the cause of a problem unrelated to the freeze issue I am having with the stock 2.6.26 kernel. Today, I tried adding boot parameters to the kernel line in GRUB 'menu.lst', to see if I could find a particular subsystem to disable which would allow the kernel to boot. My first attempt involved throwing in every possible parameter that might help -- debugging options, as well as options to disable various kernel features. This has allowed the kernel to boot, and I am filing this bug report update from the working kernel. I see that 'reportbug' has added some information from the kernel logs to this message already, but I also attached the full 'dmesg' output in bz2 form. I will try to reduce the number of boot parameters to the minimum that will work now -- I turned a lot of things off, but maybe some of them can be left on. Things turned off include: SMP TSC ACPI APIC AGP HPET HIGH RES TIMERS TICKLESS CLOCKS USB I'm hoping to get it working with just one or 2 of these features disabled, then try to build a custom kernel to verify I can make it work on this system. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 18:46:19 UTC 2008 ** Command line: root=/dev/hda1 ro notsc fbcon=font:8x8 nosmp noacpi noapic printk.time=1 earlyprintk=vga initcall_debug agp=off boot_delay=100 hpet=disable highres=off ignore_loglevel nohz=off nousb print_fatal_signals=1 ** Not tainted ** Kernel log: [4.164699] SB600_PATA: not 100% native mode: will probe irqs later [4.164742] ide0: BM-DMA at 0xf900-0xf907 [4.164782] Probing IDE interface ide0... [4.192356] Driver 'sd' needs updating - please use bus_type methods [4.192483] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [4.192532] sd 0:0:0:0: [sda] Write Protect is off [4.192569] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.192620] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.192701] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [4.192747] sd 0:0:0:0: [sda] Write Protect is off [4.192784] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.192834] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.192877] sda: unknown partition table [4.199516] sd 0:0:0:0: [sda] Attached SCSI disk [4.199608] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) [4.199657] sd 1:0:0:0: [sdb] Write Protect is off [4.199694] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [4.199745] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.199824] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) [4.199870] sd 1:0:0:0: [sdb] Write Protect is off [4.199906] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [4.199957] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.20] sdb: unknown partition table [4.202221] sd 1:0:0:0: [sdb] Attached SCSI disk [4.452603] hda: Maxtor 6H500R0, ATA DISK drive [4.900627] hdb: SAMSUNG DVD-ROM SD-616E, ATAPI CD/DVD-ROM drive [4.956332] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [4.957426] hda: UDMA/100 mode selected [4.958567] hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [4.958700] hdb: UDMA/33 mode selected [4.958880] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [5.029791] hda: max request size: 512KiB [5.031472] hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63 [5.033229] hda: cache flushes supported [5.036093] hda: hda1 hda2 hda3 hda5 hda6 hda7 hda8 hda9 [5.62] hdb: ATAPI 48X DVD-ROM drive, 512kB Cache [5.111320] Uniform CD-ROM driver Revision: 3.20 [5.365673] md: linear personality registered for level -1 [5.370285] md: multipath personality registered for level -4 [5.374454] md: raid0 personality registered for level 0 [5.379595] md: raid1 personality registered for level 1 [5.383743] xor: automatically using best
Bug#493479: linux-image-2.6.26-1-amd64: [SOLVED] Problem was HPET
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Followup-For: Bug #493479 After removing all of the boot parameters for debugging as mentioned in my last message, I then began removing the parameters which disable kernel features one at time. The result was that I could remove all of the options except hpet=disable. There are 5 kernel config options for HPET, and they are identical between my last working custom config for 2.6.25 and the Debian stock 2.6.26-1 kernel: CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_HPET=y # CONFIG_HPET_RTC_IRQ is not set CONFIG_HPET_MMAP=y That is a regression for this machine, with the ECS AMD690GM-M2 motherboard. (As mentioned in my original bug report, I have another machine with a Gigabyte GA-M59SLI-S5 motherboard that is not affected by this regression.) Are there any Debian-specific changes to the HPET source code, or is the problem directly from upstream? -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 18:46:19 UTC 2008 ** Command line: root=/dev/hda1 ro fbcon=scrollback:1024k hpet=disabled ** Not tainted -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (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.26-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-amd64 recommends no packages. Versions of packages linux-image-2.6.26-1-amd64 suggests: ii grub 0.97-44GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493479: linux-image-2.6.26-1-amd64: [SOLVED] Problem was HPET
On Sun, Aug 03, 2008 at 11:42:49AM -0400, Dave Witbrodt wrote: Are there any Debian-specific changes to the HPET source code, or is the problem directly from upstream? No, there are no Debian-specific changes. But 2.6.26 uses the new rtc infrastructure, which may change things. You may check the following: 1. Disable RTC_CLASS, set RTC=y 2. Set RTC_CLASS=y, RTC_DRV_CMOS=y Bastian -- Beam me up, Scotty! signature.asc Description: Digital signature
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Hi, On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Thanks for your quick reply. Do you also have an amd64 image? Don't have any i386 systems running lenny/sid right now. Greetings, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Bastian Hi, Could this be related to #452181? It was fixed in udev 0.124-3, but testing still has 0.114-2. Regards, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Hi, On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 I've installed udev 0.125 from unstable on testing and it seems to fix the issue. The rtc-cmos module is automatically loaded. If udev 0.125 enters testing, it should not be a problem (for me). Regards, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493633: marked as done (linux-source-2.6.25: Suggest libncurses5-dev instead of libncurses-dev)
Your message dated Sun, 03 Aug 2008 20:23:43 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-source-2.6.25: Suggest libncurses5-dev instead of libncurses-dev has caused the Debian Bug report #493633, regarding linux-source-2.6.25: Suggest libncurses5-dev instead of libncurses-dev 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.) -- 493633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493633 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-source-2.6.25 Version: 2.6.25-7 Severity: normal There is no package libncurses-dev any more. Please update suggest list. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.25 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-0.1high-quality block-sorting file co Versions of packages linux-source-2.6.25 recommends: ii gcc 4:4.3.1-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-10 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.25 suggests: ii kernel-package11.001-0.1 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Nope; first of all, libncurses5-dev provides libncurses-dev, second, with the post lenny libncurses5 to libncurses6 transition, people would need to something sensible like libncurses5-dev | libncurses-dev anyway, thus closing this bug. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ ---End Message---
Bug#493633: linux-source-2.6.25: Suggest libncurses5-dev instead of libncurses-dev
Package: linux-source-2.6.25 Version: 2.6.25-7 Severity: normal There is no package libncurses-dev any more. Please update suggest list. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.25 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-0.1high-quality block-sorting file co Versions of packages linux-source-2.6.25 recommends: ii gcc 4:4.3.1-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-10 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.25 suggests: ii kernel-package11.001-0.1 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493639: linux-libc-dev: linux/cdrom.h does not include in any way definition of INT_MAX
Package: linux-libc-dev
Version: 2.6.25-7
Severity: normal
When compiling a program I noticed that linux/cdrom.h uses macro INT_MAX
but does not include a definition of it in any way. I think that the rule of
thumb is that the include files must be self-contained in the sense that they
must #include anything they might need internally.
An obvious workaround for a programmer is to #include limits.h before
linux/cdrom.h.
A trivial code that illustrates the problem is attached.
#include linux/cdrom.h
foo()
{
int bar = CDSL_CURRENT;
}
Bug#485609: closed by Bastian Blank [EMAIL PROTECTED] (Bug#485609: fixed in linux-2.6 2.6.26-1)
Hi Bastian, I snipped the rest of the message body to spare you the huge reply. I have confirmed that today's daily build of the installer seems to resolve the bug. Interestingly, the installer chose 2.6.25-2 for the default kernel. So I suspect the problem was in the installer somehow. I am not sure what change fixes it but it works without problems now. Thanks, Matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338347: Yahoo news
Man arraigned for role in murder plot of IRS agent http://ludmila-skripkina.de/index1.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493479: linux-image-2.6.26-1-amd64: RTC suggestions do not make kernel bootable
Are there any Debian-specific changes to the HPET source code, or is the problem directly from upstream? No, there are no Debian-specific changes. But 2.6.26 uses the new rtc infrastructure, which may change things. OK, I read '/linux-source-2.6.26/Documentation/rtc.txt' and then tried building a kernel for each of your suggestions below. You may check the following: 1. Disable RTC_CLASS, set RTC=y I had RTC_CLASS disabled already, but RTC=m. I changed to RTC=y as suggested. The resulting kernel freezes just like the stock kernel. 2. Set RTC_CLASS=y, RTC_DRV_CMOS=y Setting RTC_CLASS=y causes RTC to disappear in 'make menuconfig', and that equates to RTC=n, as desired. The resulting kernel still froze. Both of these test kernels were configured with HPET=y and HPET_MMAP=y. Experiments last night with HPET=y and HPET_MMAP=n made no difference, though without modifications to RTC* (they all had RTC=m). In short, unless some change is made to the sources, then any d-i CD with 2.6.26 tried on hardware like this machine will freeze during boot. Not even the MAGIC_SYSRQ tricks get a response. Do you have any other suggestions? Should I try building from kernel.org sources? (I don't think it could possibly make a difference... but if I did that, I could then justify submitting the regression report to LKML myself instead of using the Debian Kernel Team as intermediaries.) Thanks, Dave W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493479: linux-image-2.6.26-1-amd64: can't see a quick fix in the sources
I've taken this search for a bugfix about as far as I can,
without outside help. Nothing that I've tried has allowed
me to create a 2.6.26 kernel for my fileserver machine with
the boot parameter hpet=disable. That also includes the
stock 2.6.26-1 kernel. (On my desktop machine, both stock
and custom 2.6.26-1 kernels boot just fine, though I do use
notsc on all of my machines to avoid annoying messages at
boot.)
Hoping that some simple change was made to the HPET sources
between 2.6.25 and 2.6.26 which I could manually revert, I
took a quick look for HPET-related files. For example:
find linux-source-2.6.26 -name '*hpet*' -a \
! -path 'linux-source-2.6.26/debian*'
Most of the files listed had few or no changes between kernel
versions. The most interesting results can be seen (if you
unpack 2.6.25-7 and 2.6.26-1 sources in the same directory)
with this command:
diff -u linux-source-2.6.2[56]/arch/x86/kernel/hpet.c
This is what I saw:
= BEGIN OUTPUT =
--- linux-source-2.6.25/arch/x86/kernel/hpet.c2008-04-16 22:49:44.0
-0400
+++ linux-source-2.6.26/arch/x86/kernel/hpet.c2008-07-13 17:51:29.0
-0400
@@ -137,9 +137,10 @@
hd.hd_irq[0] = HPET_LEGACY_8254;
hd.hd_irq[1] = HPET_LEGACY_RTC;
-for (i = 2; i nrtimers; timer++, i++)
-hd.hd_irq[i] = (timer-hpet_config Tn_INT_ROUTE_CNF_MASK)
+for (i = 2; i nrtimers; timer++, i++) {
+hd.hd_irq[i] = (readl(timer-hpet_config) Tn_INT_ROUTE_CNF_MASK)
Tn_INT_ROUTE_CNF_SHIFT;
+}
hpet_alloc(hd);
@@ -218,7 +219,7 @@
hpet_freq = 1000ULL;
do_div(hpet_freq, hpet_period);
hpet_clockevent.mult = div_sc((unsigned long) hpet_freq,
- NSEC_PER_SEC, 32);
+ NSEC_PER_SEC, hpet_clockevent.shift);
/* Calculate the min / max delta */
hpet_clockevent.max_delta_ns = clockevent_delta2ns(0x7FFF,
hpet_clockevent);
= END OUTPUT =
At first I thought there might be an operator precedence bug with
the first change, at timer-hpet_config. When I thought about
it more, I realized that the kernel works just fine on my desktop
machine.
At any rate, a kernel built with just the first change reverted
froze like the stock kernel; and a kernel built with both changes
reverted also froze.
Unless one of the tiny changes in the other files found with the
'find' command shown above, then the problem is not located in any
source files with hpet in their name. That would mean that other
changes to the kernel are impacting HPET, and I simply don't have
the know-how (yet) to track down such bugs.
Dave W.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
