Processed: Re: Bug#542772: hal: HAL deamon locks computer on boot, needs powercycling to recover
Processing commands for cont...@bugs.debian.org: > severity 542772 important Bug #542772 [hal] hal: HAL deamon locks computer on boot, needs powercycling to recover Severity set to 'important' from 'grave' > reassign 542772 linux-image-2.6.30-1-686 Bug #542772 [hal] hal: HAL deamon locks computer on boot, needs powercycling to recover Bug reassigned from package 'hal' to 'linux-image-2.6.30-1-686'. Bug No longer marked as found in versions hal/0.5.12~git20090406.46dc48-2. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#488022: Official Prize Notification
Your e-mail address has won the British Tobacco Promotion.Therefore you have been approve to claim the sum of 1,000,000.00 GBP. Send Names: Address: Country: Phone No: Occupation: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Debian-installer use of initrd (was Re: CONFIG_BLK_DEV_RAM=y)
On Sun, 2009-09-06 at 19:03 +0100, Ben Hutchings wrote: > Marco d'Itri wrote: > > Why? The /dev/ram* devices are not needed anymore for the early boot > > with 2.6 kernels, unless there is something fundamental I am missing > > this driver should become modular. > > Apparently it used to be needed by debian-installer, but that doesn't > seem to be the case any more. If it's not, I'll change it to a module. Given the lack of response, I'm assuming this is OK to change. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp signature.asc Description: This is a digitally signed message part
Bug#545920: 'W: Possible missing firmware ... for module e100' even though e100 isn't loaded
Package: initramfs-tools
Version: 0.92o
Severity: normal
# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-2.6.31-grml64
W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100
update-initramfs: Generating /boot/initrd.img-2.6.26-2-amd64
update-initramfs -u -k all 8.01s user 3.54s system 106% cpu 10.804 total
# lsmod | grep e100
e1000e138944 0
#
My guess is that the check inside initramfs-tools isn't precise
enough when matching the module name ('e100' being part of
'e1000e').
regards,
-mika-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Driver for HP arry P410I ZM SAS array controller
On Wed, Sep 09, 2009 at 12:14:20PM +0200, Olivier JUDITH wrote: > Sorry , i made i big mistake . > I'm very confuse. > > The problem not coming from the P410i card but from a P212 SAS PCI > controller which is directly attached to the HP MSL Tape library. > same driver module is used for both card. I wonder if we need this change.. commit 935dc8d7575e6c1292b057e39045a40f1fbe26e7 Author: Mike Miller Date: Mon Aug 4 11:54:54 2008 +0200 cciss: add support for multi lun tape devices This patch adds support for multi-lun devices in a SAS environment. It's required for the support of media changers. Signed-off-by: Stephen M. Cameron Signed-off-by: Mike Miller Signed-off-by: Jens Axboe -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Driver for HP arry P410I ZM SAS array controller
On Wed, Sep 09, 2009 at 12:14:20PM +0200, Olivier JUDITH wrote: > Sorry , i made i big mistake . > I'm very confuse. > > The problem not coming from the P410i card but from a P212 SAS PCI > controller which is directly attached to the HP MSL Tape library. > same driver module is used for both card. > I have no information and device for P212 card and can not see the tape > library on debian. > > /proc/scsi/scsi on debian > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: TEAC Model: DV-28S-V Rev: C.0F > Type: CD-ROM ANSI SCSI revision: 05 > > > /proc/scsi/scsi on Redhat > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: TEAC Model: DV-28S-V Rev: C.0F > Type: CD-ROM ANSI SCSI revision: 05 > Host: scsi2 Channel: 00 Id: 00 Lun: 00 > Vendor: HP Model: Ultrium 3-SCSI Rev: C25W > Type: Sequential-AccessANSI SCSI revision: 05 > Host: scsi2 Channel: 00 Id: 01 Lun: 00 > Vendor: HP Model: MSL G3 SeriesRev: 4.60 > Type: Medium Changer ANSI SCSI revision: 05 > > > Sorry bad informations in my previous email Can you provide the 'dmesg' output from the Red Hat system? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#540923: after suspend to ram wicd cannot find any networks anymore
On Mo, 07 Sep 2009, Ben Hutchings wrote: > > After suspend to ram and wake up, which works fine, the wireless card > > does not work at all. I thought it is hal/dbus so I restarted the > > dbus service (which in turn restarted hal, wicd, and several others), > > but to no effect. The wireless is gone, no network found. > Which driver are you using? kernel included iwl3945 Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- BRECON That part of the toenail which is designed to snag on nylon sheets. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 545879 is important
Processing commands for cont...@bugs.debian.org: > severity 545879 important Bug #545879 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: soft lockup CPU stuck on heavy load 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 debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498702: closed by Moritz Muehlenhoff (Re: additional comment: PATA HD not detected)
> > This should be fixed in 2.6.26-12. Can you confirm? > > No further feedback, closing. Please reopen if the bug persists in latest > Lenny or unstable. My sincere apologies, I had not seen your question. Yes, this is now fixed. Many thanks! Edsko -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#404951: sb1-bcm91250a kernel does not boot
On Wed, Oct 29, 2008 at 07:40:22AM +0100, Martin Michlmayr wrote: > * Thiemo Seufer [2008-09-15 14:11]: > > I am promised to have internet access again at home next weekend, > > working on the SWARM kernels is the highest Debian-related priority > > I have at that point. > > Thiemo, what's the status of this? What's the status? Is is still broken? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522773: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro
On Wed, Sep 09, 2009 at 10:36:45AM +, Thorsten Glaser wrote: > Moritz Muehlenhoff dixit: > > >You need to get this changed upstream, we won't deviate from > >upstream for this. > > You probably have better contact to upstream, would you be > so kind as to bring this forward with them? We don't have time for this. You should contact linux-kernel or file a bug at http://bugzilla.kernel.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
On Sun, Sep 21, 2008 at 04:34:15PM +0200, Sandro Tosi wrote: > Hello Maximilian, > I'm not quite happy with your downgrade of #499198 to important since > this (together with #499046 and #498328) is a clear regretion from > 2.6.25 and caused my data loss (hence it qualifies for severity > grave). > > I'm on > > $ uname -a > Linux zion 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 GNU/Linux > > since more than 4 days, and none of the above problem ever happened: > > - the system runs fine, without any "mtrr: type mismatch", partial > freeze (#499046) or complete freeze (#499198) > - when typing, there are not char repetition or strange behavior (#498328) > - I'm running since 1day the long-running task mentioned in (#498328) > and it's using 100% of all 4 cores, without me even noticing it. > > At last: those are all important bug and I believe #499198 to be RC. > > I renew my willing to help you, just tell me how; but if the only > interaction you want to have with my bugs is via control server to > downgrade their severity, then I'll find other way to let my concerns > be known. What is the status? Does this still affect the final Lenny kernel? Did you try a more recent kernel from backports.org? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521943: [linux-image-2.6.29-1-686] system becomes unresponsive due to "soft lockup - CPU#0 stuck for 61s!"
On Tue, Mar 31, 2009 at 12:21:15AM +0200, Giovanni Mascellani wrote: > Package: linux-image-2.6.29-1-686 > Version: 2.6.29-1 > Severity: important > > --- Please enter the report below this line. --- > After a few hours my laptop is on, the system suddenly becomes near > totally unresponsive: the keyboard doesn't work (in particular, I can't > switch to tty1 or kill X with Ctrl-Alt-Backspace), the mouse moves, but > the clicks are processed with considerable delay (magnitude of minutes). > The GNOME interface (panels, applets) are working, so I can see that the > CPU usage is constantly to 50% (I'm on a two cores machine, so one core > totally used and the other not). > > I've tried to let the computer alone and without inputs for a couple of > hours, but nothing changed when I started again trying to bring it again > to normal work. > > After reboot with Alt-SysRq-B, the syslog contains lots of messages like > this: > > > Mar 30 23:58:26 sieff kernel: [14450.420008] BUG: soft lockup - CPU#0 stuck > > for 61s! [cp:9819] > > Mar 30 23:58:26 sieff kernel: [14450.420008] Modules linked in: nls_utf8 > > nls_cp437 vfat fat nls_base usb_storage i915 drm i2c_algo_bit ppdev > > parport_pc lp parport binfmt_misc cpufreq_stats cpufreq_userspa > > ce cpufreq_powersave cpufreq_conservative tun fuse ipv6 acpi_cpufreq > > coretemp eeprom loop dm_crypt dm_mod snd_hda_codec_realtek joydev > > snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_p > > cm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event > > snd_seq snd_timer snd_seq_device snd soundcore i2c_i801 yenta_socket > > acer_wmi rfkill intel_agp pcspkr i2c_core serio_raw psmouse rs > > rc_nonstatic snd_page_alloc evdev rng_core wmi battery container agpgart ac > > video output button ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod > > crc_t10dif ide_pci_generic ide_core ata_generic ata_piix > > libata b44 ssb scsi_mod sdhci_pci sdhci uhci_hcd mmc_core pcmcia > > pcmcia_core mii ehci_hcd led_class usbcore thermal processor fan > > thermal_sys [last unloaded: v4l1_compat] > > Mar 30 23:58:26 sieff kernel: [14450.420008] > > Mar 30 23:58:26 sieff kernel: [14450.420008] Pid: 9819, comm: cp Not > > tainted (2.6.29-1-686 #1) Aspire 5610Z > > Mar 30 23:58:26 sieff kernel: [14450.420008] EIP: 0060:[] EFLAGS: > > 00010246 CPU: 0 > > Mar 30 23:58:26 sieff kernel: [14450.420008] EIP is at > > __copy_from_user_ll_nocache_nozero+0x21/0x2c > > Mar 30 23:58:26 sieff kernel: [14450.420008] EAX: f76ff000 EBX: 1000 > > ECX: 0400 EDX: > > Mar 30 23:58:26 sieff kernel: [14450.420008] ESI: 09a7b000 EDI: f76ff000 > > EBP: ESP: e865ddbc > > Mar 30 23:58:26 sieff kernel: [14450.420008] DS: 007b ES: 007b FS: 00d8 > > GS: 0033 SS: 0068 > > Mar 30 23:58:26 sieff kernel: [14450.420008] CR0: 8005003b CR2: f76ff000 > > CR3: 2bafd000 CR4: 06d0 > > Mar 30 23:58:26 sieff kernel: [14450.420008] DR0: DR1: > > DR2: DR3: > > Mar 30 23:58:26 sieff kernel: [14450.420008] DR6: 0ff0 DR7: 0400 > > Mar 30 23:58:26 sieff kernel: [14450.420008] Call Trace: > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > iov_iter_copy_from_user_atomic+0x4d/0xa5 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > generic_file_buffered_write+0xe1/0x270 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > generic_file_buffered_write+0x10a/0x270 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > __generic_file_aio_write_nolock+0x265/0x28d > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > _spin_lock+0x5/0x7 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > _spin_lock+0x5/0x7 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > generic_file_aio_write+0x5d/0xb4 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > do_sync_write+0xc0/0x107 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > sched_clock_cpu+0x136/0x147 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > pick_next_task_fair+0x80/0x87 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > autoremove_wake_function+0x0/0x2d > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > schedule+0x6dd/0x754 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > security_file_permission+0xc/0xd > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > do_sync_write+0x0/0x107 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > vfs_write+0x7e/0xd6 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > sys_write+0x3c/0x63 > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > sysenter_do_call+0x12/0x2f > > Mar 30 23:58:26 sieff kernel: [14450.420008] [] > > pci_fixup_video+0x0/0x93 > > I'm not able to understand what they mean. They seem to be sent out on > an average of once every one or two minutes, for the entire interval > during which the system is unresponsive. > > I hope this annoying but to be fixed as soon as possible! > > Thank you for your work
Bug#500158: Comments.
On Thu, Jan 22, 2009 at 06:28:34PM +0100, Raúl Sánchez Siles wrote: > Hello: > > I think this bug is closely related to [0] but I'm not sure. > > Bets are, that again in this case, you're facing an unsupported assembler > instruction which is not supported by your CPU. The first panic message > retrieved from kernel was useful in those days to diagnose the cause of the > panic, but unfortunately I've been unable to find that linux-image package > version and I couldn't check in the System.map file which function contains > the > crash. > > Maybe you can still reproduce it and provide with a fresh panic message and > either check yourself which function breaks or providing both the crash info > and the running kernel System.map. > > Anyway, I'd suggest reading my latter comment on [0] and taking conclusions > from there. But I have the impression this time again, it's virtualization > that's breaking down. I think report should arrive upstream somehow. Before reporting this upstream, we should test whether it might already been fixed in the mean time. Can you test, whether a 2.6.30 kernel from backports.org exhibits the same behaviour? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 520049 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 520049 wishlist Bug #520049 [linux-2.6] linux-image-2.6.28-1-686: please set CONFIG_IWLWIFI_DEBUG Severity set to 'wishlist' from 'important' > 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 debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 520049
Processing commands for cont...@bugs.debian.org: > tags 520049 wontfix Bug #520049 [linux-2.6] linux-image-2.6.28-1-686: please set CONFIG_IWLWIFI_DEBUG Added tag(s) wontfix. > 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 debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#545879: kernel log at the time of cmplete lock
Aug 16 13:37:51 server2 kernel: [1160195.626233] rpcbind: server 192.168.1.1 not responding, timed out Aug 17 06:25:05 server2 kernel: [1237254.638802] apt-cacher[16649]: segfault at a80 ip 7f31e416ebd3 sp 7fffec663c50 error 4 in libperl.so.5.10.0[7f31e40de000+162000] Aug 19 07:04:51 server2 kernel: [1422975.972778] Clocksource tsc unstable (delta = 3701009377670 ns) Aug 19 07:04:51 server2 kernel: [1422975.972778] BUG: soft lockup - CPU#1 stuck for 7781s! [wrf.exe:25309] Aug 19 07:04:51 server2 kernel: [1422975.972778] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables cpufreq_ondemand cpufreq_userspace cpufreq_powersave cpufreq_stats freq_table cpufreq_conservative ipv6 fuse dm_snapshot dm_mirror dm_log dm_mod loop snd_pcsp snd_pcm rng_core shpchp i5000_edac edac_core psmouse snd_timer pci_hotplug snd soundcore snd_page_alloc serio_raw evdev button dcdbas usbhid hid ff_memless ext3 jbd mbcache sg sr_mod cdrom ata_generic ide_pci_generic ide_core sd_mod ata_piix uhci_hcd bnx2 libata dock ehci_hcd mptsas mptscsih mptbase scsi_transport_sas scsi_mod firmware_class thermal processor fan thermal_sys Aug 19 07:04:51 server2 kernel: [1422975.972778] CPU 1: Aug 19 07:04:51 server2 kernel: [1422975.972778] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables cpufreq_ondemand cpufreq_userspace cpufreq_powersave cpufreq_stats freq_table cpufreq_conservative ipv6 fuse dm_snapshot dm_mirror dm_log dm_mod loop snd_pcsp snd_pcm rng_core shpchp i5000_edac edac_core psmouse snd_timer pci_hotplug snd soundcore snd_page_alloc serio_raw evdev button dcdbas usbhid hid ff_memless ext3 jbd mbcache sg sr_mod cdrom ata_generic ide_pci_generic ide_core sd_mod ata_piix uhci_hcd bnx2 libata dock ehci_hcd mptsas mptscsih mptbase scsi_transport_sas scsi_mod firmware_class thermal processor fan thermal_sys Aug 19 07:04:51 server2 kernel: [1422975.972778] Pid: 25309, comm: wrf.exe Not tainted 2.6.26-2-amd64 #1 Aug 19 07:04:51 server2 kernel: [1422975.972778] RIP: 0010:[] [] system_call_after_swapgs+0x2b/0x8f Aug 19 07:04:51 server2 kernel: [1422975.972778] RSP: 0018:810215ebdf88 EFLAGS: 0286 Aug 19 07:04:51 server2 kernel: [1422975.972778] RAX: 0018 RBX: RCX: 2ac4a1f6c657 Aug 19 07:04:51 server2 kernel: [1422975.972778] RDX: 2ac4a168da68 RSI: RDI: 0001 Aug 19 07:04:51 server2 kernel: [1422975.972778] RBP: 81022d54eda0 R08: 02bc5fd8 R09: 084b31b8 Aug 19 07:04:51 server2 kernel: [1422975.972778] R10: 2ac4a26590c0 R11: 0246 R12: 81022d54eb10 Aug 19 07:04:51 server2 kernel: [1422975.972778] R13: 81022d54eb10 R14: 810142afb560 R15: 8101fd9958e0 Aug 19 07:04:51 server2 kernel: [1422975.972778] FS: 2ac4a2627b10() GS:81022f0928c0() knlGS: Aug 19 07:04:51 server2 kernel: [1422975.972778] CS: 0010 DS: ES: CR0: 80050033 Aug 19 07:04:51 server2 kernel: [1422975.972778] CR2: 02ac1528 CR3: 00021507a000 CR4: 06e0 Aug 19 07:04:51 server2 kernel: [1422975.972778] DR0: DR1: DR2: Aug 19 07:04:51 server2 kernel: [1422975.972778] DR3: DR6: 0ff0 DR7: 0400 Aug 19 07:04:51 server2 kernel: [1422975.972778] Aug 19 07:04:51 server2 kernel: [1422975.972778] Call Trace: Aug 19 07:04:51 server2 kernel: [1422975.972778] [] ? system_call_after_swapgs+0x8a/0x8f Aug 19 07:04:51 server2 kernel: [1422975.972778] Aug 19 07:04:51 server2 kernel: [1422975.972778] BUG: soft lockup - CPU#2 stuck for 7780s! [wrf.exe:25592] Aug 19 07:04:51 server2 kernel: [1422975.972778] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables cpufreq_ondemand cpufreq_userspace cpufreq_powersave cpufreq_stats freq_table cpufreq_conservative ipv6 fuse dm_snapshot dm_mirror dm_log dm_mod loop snd_pcsp snd_pcm rng_core shpchp i5000_edac edac_core psmouse snd_timer pci_hotplug snd soundcore snd_page_alloc serio_raw evdev button dcdbas usbhid hid ff_memless ext3 jbd mbcache sg sr_mod cdrom ata_generic ide_pci_generic ide_core sd_mod ata_piix uhci_hcd bnx2 libata dock ehci_hcd mptsas mptscsih mptbase scsi_transport_sas scsi_mod firmware_class thermal processor fan thermal_sys Aug 19 07:04:51 server2 kernel: [1422975.972778] CPU 2: Aug 19 07:04:51 server2 kernel: [1422975.972778] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables cpufreq_ondemand cpufreq_userspace cpufreq_powersave cpufreq_stats f
Bug#497870: marked as done (linux-image-2.6.26-1-amd64: freeze with flashing caps lock on lenovo thinkpad t61)
Your message dated Wed, 9 Sep 2009 21:01:35 +0200 with message-id <20090909190135.gj22...@inutil.org> and subject line Re: Another update has caused the Debian Bug report #497870, regarding linux-image-2.6.26-1-amd64: freeze with flashing caps lock on lenovo thinkpad t61 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 ow...@bugs.debian.org immediately.) -- 497870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-3 Severity: important 2.6.25 also exhibited this behaviour (2.6.24 never has). the machine would just freeze. it usually happened with the lid closed, so the screen was black, but once it happened with the lid open, with an x server running, and i can't find any logs with a kernel panic or anything. only feedback i get is that the caps lock light flashes on my thinkpad. how can i find logs to help track down this problem? thanks, jayen -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-3) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Aug 20 12:09:32 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=ab5d8c7a-80a8-4241-a80b-28496df577d4 ro ** Tainted: P (1) ** Kernel log: [38195.259446] update_stats: bogus ndx1 -1, max 12, mode 1 [40101.357716] update_stats: bogus ndx2 -1, max 12, mode 1 [40101.357732] update_stats: bogus ndx1 -1, max 12, mode 1 [41161.476830] update_stats: bogus ndx2 -1, max 12, mode 1 [41161.476830] update_stats: bogus ndx1 -1, max 12, mode 1 [41312.782504] update_stats: bogus ndx2 -1, max 12, mode 1 [41312.782519] update_stats: bogus ndx1 -1, max 12, mode 1 [41615.424005] update_stats: bogus ndx1 -1, max 12, mode 1 [44491.552962] update_stats: bogus ndx2 -1, max 12, mode 1 [44491.552962] update_stats: bogus ndx1 -1, max 12, mode 1 [45097.748240] update_stats: bogus ndx2 -1, max 12, mode 1 [45097.748253] update_stats: bogus ndx1 -1, max 12, mode 1 [45326.150436] update_stats: bogus ndx2 -1, max 12, mode 1 [45326.150449] update_stats: bogus ndx1 -1, max 12, mode 1 [45402.786172] update_stats: bogus ndx2 -1, max 12, mode 1 [45402.786184] update_stats: bogus ndx1 -1, max 12, mode 1 [45704.776453] update_stats: bogus ndx2 -1, max 12, mode 1 [45704.776453] update_stats: bogus ndx1 -1, max 12, mode 1 [45705.790168] update_stats: bogus ndx2 -1, max 12, mode 1 [45705.790182] update_stats: bogus ndx1 -1, max 12, mode 1 [46160.459370] rix 10 (0) bad ratekbps 0 mode 1 [46160.459381] update_stats: bogus ndx2 -1, max 12, mode 1 [46243.886175] update_stats: bogus ndx2 -1, max 12, mode 1 [46243.886187] update_stats: bogus ndx1 -1, max 12, mode 1 [46463.746850] update_stats: bogus ndx2 -1, max 12, mode 1 [46463.746850] update_stats: bogus ndx1 -1, max 12, mode 1 [47703.348332] update_stats: bogus ndx2 -1, max 12, mode 1 [47703.348345] update_stats: bogus ndx1 -1, max 12, mode 1 [48309.308227] update_stats: bogus ndx2 -1, max 12, mode 1 [48309.308227] update_stats: bogus ndx1 -1, max 12, mode 1 [48918.319386] update_stats: bogus ndx2 -1, max 12, mode 1 [48918.319399] update_stats: bogus ndx1 -1, max 12, mode 1 [49217.242474] update_stats: bogus ndx2 -1, max 12, mode 1 [49217.242474] update_stats: bogus ndx1 -1, max 12, mode 1 [49520.531370] update_stats: bogus ndx2 -1, max 12, mode 1 [49520.531381] update_stats: bogus ndx1 -1, max 12, mode 1 [50369.232137] update_stats: bogus ndx2 -1, max 12, mode 1 [50369.234026] update_stats: bogus ndx1 -1, max 12, mode 1 [52912.884080] update_stats: bogus ndx2 -1, max 12, mode 1 [52912.884080] update_stats: bogus ndx1 -1, max 12, mode 1 [52913.888550] update_stats: bogus ndx2 -1, max 12, mode 1 [52913.888562] update_stats: bogus ndx1 -1, max 12, mode 1 [53142.022703] update_stats: bogus ndx2 -1, max 12, mode 1 [53142.022715] update_stats: bogus ndx1 -1, max 12, mode 1 [53671.911420] update_stats: bogus ndx2 -1, max 12, mode 1 [53671.911432] update_stats: bogus ndx1 -1, max 12, mode 1 [53821.416766] update_stats: bogus ndx2 -1, max 12, mode 1 [53821.416766] update_stats: bogus ndx1 -1, max 12, mode 1 [53974.959220] update_stats: bogus ndx2 -1, max 12, mode 1 [53974.959232] update_stats: bogus ndx1 -1, max 12, mode 1 [54124.164295] update_stats: bogus ndx2 -1, max 12, mode 1 [54124.164295] update_stats: bogus ndx1 -1, max 12, mode 1 [54973.066193] update_stats: bogus ndx2 -1, max 12, mode 1 [54973.066205] update_stats: bogus ndx1 -1, max 12, mode 1 [56639.364288] update_stats: bogus ndx2 -1, max 12, mode 1 [56639.364288] update_stats: bogus ndx1 -1, max 12, m
Bug#519939: marked as done (linux-image-2.6.28-1-686: snd-opl3sa2 loaded along with snd_hda_intel hangs s2disk on d630)
Your message dated Wed, 9 Sep 2009 21:01:12 +0200 with message-id <20090909190112.gh22...@inutil.org> and subject line Re: linux-image-2.6.28-1-686: snd-opl3sa2 loaded along with snd_hda_intel hangs s2disk on d630 has caused the Debian Bug report #519939, regarding linux-image-2.6.28-1-686: snd-opl3sa2 loaded along with snd_hda_intel hangs s2disk on d630 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 ow...@bugs.debian.org immediately.) -- 519939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.28-1-686 Version: 2.6.28-1 Severity: important s2disk causes Opps like http://www.kerneloops.org/raw.php?rawid=80591&msgid= when snd-opl3sa2 is loaded. Plese note that this module is useless because sound works without snd-opl3sa2 on my Dell Latitude D630. The module snd_hda_intel seems enough. (I have added snd-opl3sa2 to modprobe blacklist.) -- Package-specific info: ** Version: Linux version 2.6.28-1-686 (Debian 2.6.28-1) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-4) ) #1 SMP Mon Feb 23 03:13:24 UTC 2009 ** Command line: root=/dev/sda6 ro usbcore.autosuspend=1 no_console_suspend ** Not tainted ** Kernel log: [ 13.597063] agpgart-intel :00:00.0: Intel 965GM Chipset [ 13.598110] agpgart-intel :00:00.0: detected 7676K stolen memory [ 13.600913] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xe000 [ 13.602171] ACPI: AC Adapter [AC] (on-line) [ 13.687364] ACPI: Battery Slot [BAT0] (battery present) [ 13.687489] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4 [ 13.693671] ACPI: Lid Switch [LID] [ 13.693779] ACPI: Battery Slot [BAT1] (battery absent) [ 13.693896] input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5 [ 13.708022] ACPI: Power Button (CM) [PBTN] [ 13.708139] input: Sleep Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input6 [ 13.724016] ACPI: Sleep Button (CM) [SBTN] [ 13.785219] ACPI: WMI: Mapper loaded [ 14.112764] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:37/input/input7 [ 14.132014] ACPI: Video Device [VID1] (multi-head: yes rom: no post: no) [ 14.132127] ACPI Warning (nspredef-0357): \_SB_.PCI0.VID2._DOD: Return Package has no elements (empty) [20080926] [ 14.132365] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:3c/input/input8 [ 14.147200] ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) [ 14.252044] cfg80211: Using static regulatory domain info [ 14.252109] cfg80211: Regulatory domain: US [ 14.252167] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 14.252240] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 14.252303] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.252367] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.252430] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.252493] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 14.252557] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 14.252622] cfg80211: Calling CRDA for country: US [ 14.422993] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 14.423073] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 14.423230] iwl3945 :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 14.423306] iwl3945 :0c:00.0: setting latency timer to 64 [ 14.423367] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 14.500146] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 14.501161] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.04 [ 14.501294] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060) [ 14.501573] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 14.516192] phy0: Selected rate control algorithm 'iwl-3945-rs' [ 15.082490] i801_smbus :00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 15.093832] input: PC Speaker as /devices/platform/pcspkr/input/input9 [ 15.413784] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [ 15.488582] iwl3945 :0c:00.0: PCI INT A disabled [ 15.494602] udev: renamed network interface wlan0 to wlan1 [ 15.644365] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input10 [ 15.699781] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input11 [ 15.794266] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 15.794431] HDA I
Bug#508820: marked as done (linux-image-2.6.26-1-mckinley: MCA and panic after bringing up loopback interface on ia64)
Your message dated Wed, 9 Sep 2009 21:00:01 +0200 with message-id <20090909190001.gd22...@inutil.org> and subject line Re: Bug#508820: linux-image-2.6.26-1-mckinley: MCA and panic after bringing up loopback interface on ia64 has caused the Debian Bug report #508820, regarding linux-image-2.6.26-1-mckinley: MCA and panic after bringing up loopback interface on ia64 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 ow...@bugs.debian.org immediately.) -- 508820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-mckinley Version: 2.6.26-11 Severity: grave Justification: renders package unusable Attempting to boot linux-image-2.6.26-1-mckinley (2.6.26-11) as an HP Integrity Virtual Machines guest OS results in a panic during network startup. Console messages leading up to this: [...] [16578579.202741] EXT3 FS on dm-1, internal journal [16578579.204938] EXT3-fs: mounted filesystem with ordered data mode. done. Activating swapfile swap...[16578579.463160] Adding 4194272k swap on /dev/mapper/vg00-swap. Priority:-1 extents:1 across:4194272k done. Setting up networking Configuring network interfaces...[16578581.213754] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [16578582.433694] NET: Registered protocol family 10 [16578582.437702] lo: Disabled Privacy Extensions [16578582.580016] Entered OS MCA handler. PSP=fff2e12c cpu=1 monarch=1 [16578582.580019] All OS MCA slaves have reached rendezvous [16578582.607085] mlogbuf_finish: printing switched to urgent mode, MCA/INIT might be dodgy or fail. [16578582.611888] Delaying for 5 seconds... Dumping Guest Image Done with dump (9612Kbytes) *** VM restarting *** [end of console logs] Hardware information: The physical system in an HP Integrity rx3600 running HP-UX 11.23 0609 and Integrity VM version A.03.00. The VM has two CPUs, 3Gbytes of RAM, a single SCSI DVD drive, two SCSI hard drives, and two "Intel Corporation 82540EM Gigabit Ethernet Controller" NICs. lspci output: 00:00.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 00:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 00:03.0 ISA bridge: Intel Corporation 82372FB PIIX5 ISA (rev 01) 07:00.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller 07:01.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller Integrity VM saved a core dump file which is available if desired. Physical access to this machine may be available for developers in the nothern Colorado area (dannf, want to come and lay hands on?) linux-image-2.6.26-1-mckinley(2.6.26-8) worked fine. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (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-mckinley depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-mckinley recommends no packages. Versions of packages linux-image-2.6.26-1-mckinley suggests: ii elilo 3.8-1 Bootloader for systems using EFI-b pn fdutils(no description available) pn linux-doc-2.6.26 (no description available) -- debconf information: linux-image-2.6.26-1-mckinley/preinst/elilo-initrd-2.6.26-1-mckinley: true linux-image-2.6.26-1-mckinley/postinst/depmod-error-2.6.26-1-mckinley: false linux-image-2.6.26-1-mckinley/postinst/bootloader-test-error-2.6.26-1-mckinley: * shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-mckinley/postinst/bootloader-error-2.6.26-1-mckinley: linux-image-2.6.26-1-mckinley/preinst/abort-overwrite-2.6.26-1-mckinley: linux-image-2.6.26-1-mckinley/postinst/create-kimage-link-2.6.26-1-mckinley: true linux-image-2.6.26-1-mckinley/postinst/kimage-is-a-directory: linux-image-2.6.26-1-mckinley/preinst/lilo-initrd-2.6.26-1-mckinley: true * linux-image-2.6.26-1-mckinley/preinst/already-running-this-2.6.26-1-mckinley: linux-image-2.6.26-1-mckinley/postinst/o
Bug#520891: marked as done (general: Data coruption on my /dev/sda - /dev/sdd sata_siil siil 3114 chip)
Your message dated Wed, 9 Sep 2009 20:59:44 +0200 with message-id <20090909185944.gc22...@inutil.org> and subject line Re: general: Data coruption on my /dev/sda - /dev/sdd sata_siil siil 3114 chip has caused the Debian Bug report #520891, regarding general: Data coruption on my /dev/sda - /dev/sdd sata_siil siil 3114 chip 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 ow...@bugs.debian.org immediately.) -- 520891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Files on theese /dev/sda-/dev/sdd drivers are going courrupt :( They are all samsung spinpoint 500GB I have before tryed to run soft RAID5 on them, not good :-( Bengt / --- End Message --- --- Begin Message --- Version: 2.6.28-1 On Fri, Aug 21, 2009 at 04:36:29PM +0200, wy...@volny.cz wrote: > Hi, > > based on my deep testing during chasing other kernel bug > (http://bugzilla.kernel.org/show_bug.cgi?id=13933), > i can tell, that i had no such problem at all with sata_sil. Tested > several days + checksuming. > > I had no sata_sil problem with following kernels: > > * 2.6.26.8 > * 2.6.27.29 > * 2.6.28.10 > * 2.6.29.6 > * 2.6.30.4 > * 2.6.30.5 > * 2.6.31-rc6 Thanks for the feedback, marking as closed, then. Cheers, Moritz --- End Message ---
Bug#500894: marked as done (linux-image-2.6.26-1-amd64: Broadcom (b43) wireless driver broken)
Your message dated Wed, 9 Sep 2009 21:00:55 +0200 with message-id <20090909190055.gg22...@inutil.org> and subject line Re: linux-image-2.6.26-1-amd64: Broadcom (b43) wireless driver broken has caused the Debian Bug report #500894, regarding linux-image-2.6.26-1-amd64: Broadcom (b43) wireless driver 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 ow...@bugs.debian.org immediately.) -- 500894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-amd64 Severity: important HP6720 laptop, amd64. % lspci -vvn|grep 43 -A7 10:00.0 0280: 14e4:4311 (rev 02) Subsystem: 103c:1375 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: b43-pci-bridge Kernel modules: ssb % dmesg [ 239.793947] wlan1: Configured IBSS beacon template [ 239.793947] phy0: Adding new IBSS station 00:0e:2e:5c:c7:75 (dev=wlan1) [ 239.894593] __ratelimit: 48 messages suppressed [ 239.901010] wlan1: beacon TSF higher than local TSF - IBSS merge with BSSID 06:b7:18:13:2a:72 [ 239.901101] wlan1: Configured IBSS beacon template [ 239.901117] phy0: Adding new IBSS station 00:0e:2e:5c:c7:75 (dev=wlan1) [ 269.919612] wlan1: expiring inactive STA 00:0e:2e:5c:c7:75 [ 269.928563] wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) [ 300.855343] wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) As you can see I get an enormous amount of messages (50/s) and after a minute or two connection (ad-hoc, WEP) dies. It works fine with 2.6.25. Regards, Vedran -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=hr_HR.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.23 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-amd64 recommends no packages. Versions of packages linux-image-2.6.26-1-amd64 suggests: ii lilo 1:22.8-6 LInux LOader - The Classic OS load ii linux-doc-2.6.26 2.6.26-6 Linux kernel specific documentatio --- End Message --- --- Begin Message --- On Sun, Mar 29, 2009 at 07:31:39PM +0200, maximilian attems wrote: > > As you can see I get an enormous amount of messages (50/s) and after a > > minute or two connection (ad-hoc, WEP) dies. It works fine with 2.6.25. > > can you give an update on newer kernel aka 2.6.29 linux images? > > thanks for the feedback. No further feedback, closing the bug. Please reopen if the error persists with 2.6.30. Cheers, Moritz --- End Message ---
Bug#498702: marked as done (linux-image-2.6.26-1-686: SATA DVD drive recognized in 2.6.25-2 but not in 2.6.26-1)
Your message dated Wed, 9 Sep 2009 21:01:22 +0200 with message-id <20090909190122.gi22...@inutil.org> and subject line Re: additional comment: PATA HD not detected has caused the Debian Bug report #498702, regarding linux-image-2.6.26-1-686: SATA DVD drive recognized in 2.6.25-2 but not in 2.6.26-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 ow...@bugs.debian.org immediately.) -- 498702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: important My Sony CD-RW/DVD-ROM CRX310S was working file until apt-get upgraded the kernel from 2.6.25-2 to 2.6.26-1 (Debian testing). The mount-point /dev/scd0 I was using has completely disappeared; this excerpt from dmesg seems highly relevant: # grep ata2 2.6.25-2.dmesg [2.193463] ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xe008 irq 21 [3.302216] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [3.492641] ata2.00: ATAPI: SONY CD-RW/DVD-ROM CRX310S, VDK2, max UDMA/100 [3.695990] ata2.00: configured for UDMA/100 # grep ata2 2.6.26-1.dmesg [2.246140] ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xe008 irq 21 [3.424045] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [3.448038] ata2.00: NODEV after polling detection The following modules get loaded when using 2.6.25-2 but not with 2.6.26-1: # diff 2.6.25-2.lsmod-modules 2.6.26-1.lsmod-modules | grep '<' < cdrom < isofs < nls_base < rtc_cmos < rtc_core < rtc_lib < sg < sr_mod < udf < zlib_inflate And these modules get loaded in 2.6.26-1 but not in 2.6.25-2: # diff 2.6.25-2.lsmod-modules 2.6.26-1.lsmod-modules | grep '>' > dm_log > ndiswrapper > thermal_sys However, that appears to be a symptom rather than the cause of the problem because when I manually modprobe the missing modules, nothing happens. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-4) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 2008 ** Command line: root=/dev/sda2 ro ** Tainted: P (1) ** Kernel log: [5.308284] usb 1-6: Product: USB Optical Mouse [5.508336] usb 2-4.3: new high speed USB device using ehci_hcd and address 6 [5.601391] usb 2-4.3: configuration #1 chosen from 1 choice [5.601731] hub 2-4.3:1.0: USB hub found [5.602081] hub 2-4.3:1.0: 4 ports detected [5.704137] usb 2-4.3: New USB device found, idVendor=05e3, idProduct=0608 [5.704196] usb 2-4.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [5.704258] usb 2-4.3: Product: USB2.0 Hub [5.904336] usb 2-4.3.1: new high speed USB device using ehci_hcd and address 7 [5.998510] usb 2-4.3.1: configuration #1 chosen from 1 choice [5.998952] usb 2-4.3.1: New USB device found, idVendor=058f, idProduct=6362 [5.999007] usb 2-4.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [5.999069] usb 2-4.3.1: Product: Mass Storage Device [5.999119] usb 2-4.3.1: Manufacturer: Generic [5.999168] usb 2-4.3.1: SerialNumber: 058F312D81B [6.001099] usbcore: registered new interface driver hiddev [6.007425] input: DELL DELL USB Keyboard as /class/input/input0 [6.016093] input,hidraw0: USB HID v1.10 Keyboard [DELL DELL USB Keyboard] on usb-:00:0b.0-3 [6.022336] input: USB Optical Mouse as /class/input/input1 [6.032309] input,hidraw1: USB HID v1.11 Mouse [USB Optical Mouse] on usb-:00:0b.0-6 [6.032539] usbcore: registered new interface driver usbhid [6.032591] usbhid: v2.6:USB HID core driver [6.034294] Initializing USB Mass Storage driver... [6.034998] scsi4 : SCSI emulation for USB Mass Storage devices [6.035138] usbcore: registered new interface driver usb-storage [6.035192] USB Mass Storage support registered. [6.035247] usb-storage: device found at 7 [6.035249] usb-storage: waiting for device to settle before scanning [6.170623] PM: Starting manual resume from disk [6.196014] kjournald starting. Commit interval 5 seconds [6.196014] EXT3-fs: mounted filesystem with ordered data mode. [8.475046] udevd version 125 started [9.166653] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [9.750564] input: Power Button (FF) as /class/input/input2 [9.779585] ACPI: Power Button (FF) [PWRF] [9.779717] input: Power Button (CM) as /class/input/input3 [9.808079] ACPI: Power Button (CM) [PWRB] [ 10.735949] i2c-adapter i2c-
Bug#519908: marked as done (kernel panic not syncing: Out of low memory (IBM System x 3590 M2))
Your message dated Wed, 9 Sep 2009 20:58:37 +0200 with message-id <20090909185837.ga22...@inutil.org> and subject line Re: kernel panic not syncing: Out of low memory (IBM System x 3590 M2) has caused the Debian Bug report #519908, regarding kernel panic not syncing: Out of low memory (IBM System x 3590 M2) 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 ow...@bugs.debian.org immediately.) -- 519908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel-package Version: 11.015 Severity: important Machine: IBM System x 3590 M2 (7141-WJS) Processor:QuadCore Xeon X7350 2.93GHz 8MB L2 x 16cpus Memory:64GB (8GBx8) System can not boot kernel(2.6.26-1-amd64) with kernel panic, after upgraded to lenny(debian 5.0.0) from Etch(4.0.r7). Boot Message Loading /install.amd/vmlinuz... Loading /install.amd/initrd.gz.. ...ready. Decompressing Linux... Booting the kernel. Kernel alive [ 0.004000 ] low bootmem alloc of 8388608 bytes failed ! [ 0.004000 ] kernel panic - not syncing: Out of low memory --- End Message --- --- Begin Message --- On Wed, Jul 29, 2009 at 09:33:55PM +0200, Moritz Muehlenhoff wrote: > On Mon, Mar 16, 2009 at 01:17:49PM +0900, t.nakao wrote: > > Package: kernel-package > > Version: 11.015 > > Severity: important > > > > Machine: IBM System x 3590 M2 (7141-WJS) > > Processor:QuadCore Xeon X7350 2.93GHz 8MB L2 x 16cpus > > Memory:64GB (8GBx8) > > > > System can not boot kernel(2.6.26-1-amd64) with kernel panic, > > after upgraded to lenny(debian 5.0.0) from Etch(4.0.r7). > > > > Boot Message > > > > Loading /install.amd/vmlinuz... > > Loading /install.amd/initrd.gz.. > > ...ready. > > > > Decompressing Linux... > > Booting the kernel. > > > > Kernel alive > > [ 0.004000 ] low bootmem alloc of > > 8388608 bytes failed ! > > [ 0.004000 ] kernel panic - > > not syncing: Out of low memory > > Please explain in more detail what you did. Did you build your own > package with kernel-package? Do the standard Debian kernels work? No further feedback, closing the bug. Cheers, Moritz --- End Message ---
Bug#501789: linux-image-2.6.26-1-amd64: ACPI Error for AC adapter
In data martedì 1 settembre 2009 19:24:43, Moritz Muehlenhoff ha scritto: : > On Fri, Oct 10, 2008 at 02:57:03PM +0200, Angelo Puglisi wrote: > > Package: linux-image-2.6.26-1-amd64 > > Version: 2.6.26-5 > > Severity: important > > > > The system do not detect AC on and AC off ACPI events. > > For a laptop this is really annoying. > > In the kernel log there is an AC off and AC on in sequence. > > I remember that in the etch kernel (2.6.18 one) it worked. > > Moreover I experience ACPI slowness (with the events that work) > > Does this error still occur with more recent kernel versions > like 2.6.30 from testing/unstable? > > Cheers, > Moritz Yes it does. But I do not experience ACPI slowness, I don't remember since which version. $ dpkg -l "linux-image-`uname -r`" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Nome Versione Descrizione +++-=-=- == ii linux-image-2.6.30-1-amd642.6.30-6 Linux 2.6.30 image on AMD64 -- Angelo Puglisi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, 2009-09-09 at 18:05 +0200, Bastian Blank wrote: > [ Remove -release, this is technical stuff. ] > > On Wed, Sep 09, 2009 at 01:31:36PM +0200, Julien Cristau wrote: > > On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: > > > Is KMS backward compatible with older versions of the intel driver? > > No :/ > > What happens when a old driver runs on a KMS enabled system? > > I don't think it have an automatic fallback to the fb device. Both try to access the registers for modesetting. Everything can happen afterwards (nothing, crash, lock, corruption ..) Xav -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
[ Remove -release, this is technical stuff. ] On Wed, Sep 09, 2009 at 01:31:36PM +0200, Julien Cristau wrote: > On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: > > Is KMS backward compatible with older versions of the intel driver? > No :/ What happens when a old driver runs on a KMS enabled system? I don't think it have an automatic fallback to the fb device. Bastian -- Oblivion together does not frighten me, beloved. -- Thalassa (in Anne Mulhall's body), "Return to Tomorrow", stardate 4770.3. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
Le mercredi 09 septembre 2009 à 14:04 +0200, Andreas Barth a écrit : > If not at X side, is it a possibility to either (a) add the new memory > manager to lenny (I assume not), or (b) tell the users "you need to > upgrade your kernel first" (and make the new X pre-depending somehow > on the kernel). This sounds like the udev case for the sarge → etch upgrade. This was solved with a big hack in the preinst, that surprisingly turned out to work. If there is no other way, this is an option. > Of course, this sounds to me like "people need to do > updates in console mode", which ... isn't the best either. Not necessarily. The only thing is that people must not restart X before rebooting. This will, of course, cause trouble with (at least) GDM, which will restart itself and re-launch X when you log out after an upgrade. Having the driver fall back to vesa when no kernel support is found, as Julien proposed, sounds like a more reliable solution. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: X.org plans for the squeeze cycle
On Wed, 2009-09-09 at 13:31 +0200, Julien Cristau wrote: > On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: > > > On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: > > > One more thing. Intel plans to deprecate userspace mode setting with > > > their Q4 2009 release (meaning December this year, so probably something > > > we'll want for squeeze, depending on the freeze date you pick). > > > > Oh, no. Not again. It does not yet properly work without the new memory > > manager (#538442). And KMS is completely unusable currently on this > > kernels. > > > > > This might also mean that we'll want to > > > turn kms on by default in the debian kernel, > > > > Is KMS backward compatible with older versions of the intel driver? > > > No :/ Running the kernel with intel.modeset=0 doesn't help ? Xav -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, Sep 9, 2009 at 14:42:52 +0200, Xavier Bestel wrote: > On Wed, 2009-09-09 at 13:31 +0200, Julien Cristau wrote: > > On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: > > > > > On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: > > > > This might also mean that we'll want to > > > > turn kms on by default in the debian kernel, > > > > > > Is KMS backward compatible with older versions of the intel driver? > > > > > No :/ > > Running the kernel with intel.modeset=0 doesn't help ? > Yeah that works (with s/intel/i915/), but it's not quite user friendly to crash unless that's manually added to the kernel command line. So it's probably better to default kms off in the kernel, and have the new userspace turn it on via /etc/modprobe.d/. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
* Bastian Blank (wa...@debian.org) [090909 12:37]: > On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: > > One more thing. Intel plans to deprecate userspace mode setting with > > their Q4 2009 release (meaning December this year, so probably something > > we'll want for squeeze, depending on the freeze date you pick). > > Oh, no. Not again. It does not yet properly work without the new memory > manager (#538442). And KMS is completely unusable currently on this > kernels. If not at X side, is it a possibility to either (a) add the new memory manager to lenny (I assume not), or (b) tell the users "you need to upgrade your kernel first" (and make the new X pre-depending somehow on the kernel). Of course, this sounds to me like "people need to do updates in console mode", which ... isn't the best either. Cheers, Andi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: > On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: > > One more thing. Intel plans to deprecate userspace mode setting with > > their Q4 2009 release (meaning December this year, so probably something > > we'll want for squeeze, depending on the freeze date you pick). > > Oh, no. Not again. It does not yet properly work without the new memory > manager (#538442). And KMS is completely unusable currently on this > kernels. > > > This might also mean that we'll want to > > turn kms on by default in the debian kernel, > > Is KMS backward compatible with older versions of the intel driver? > No :/ I guess we could also decide to freeze on the intel Q3 bits, but then we're likely to be on our own for new hardware support and stuff like that. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522773: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro
Moritz Muehlenhoff dixit: >You need to get this changed upstream, we won't deviate from >upstream for this. You probably have better contact to upstream, would you be so kind as to bring this forward with them? Thanks in advance. Sincerely, //mirabilos -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: > One more thing. Intel plans to deprecate userspace mode setting with > their Q4 2009 release (meaning December this year, so probably something > we'll want for squeeze, depending on the freeze date you pick). Oh, no. Not again. It does not yet properly work without the new memory manager (#538442). And KMS is completely unusable currently on this kernels. > This might also mean that we'll want to > turn kms on by default in the debian kernel, Is KMS backward compatible with older versions of the intel driver? Does not looks like: | bool "Enable modesetting on intel by default" | depends on DRM_I915 | help | Choose this option if you want kernel modesetting enabled by default, | and you have a new enough userspace to support this. Running old | userspaces with this enabled will cause pain. Note that this causes | the driver to bind to PCI devices, which precludes loading things | like intelfb. Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Driver for HP arry P410I ZM SAS array controller
Sorry , i made i big mistake . I'm very confuse. The problem not coming from the P410i card but from a P212 SAS PCI controller which is directly attached to the HP MSL Tape library. same driver module is used for both card. I have no information and device for P212 card and can not see the tape library on debian. /proc/scsi/scsi on debian Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: TEAC Model: DV-28S-V Rev: C.0F Type: CD-ROM ANSI SCSI revision: 05 /proc/scsi/scsi on Redhat Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: TEAC Model: DV-28S-V Rev: C.0F Type: CD-ROM ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: HP Model: Ultrium 3-SCSI Rev: C25W Type: Sequential-AccessANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: HP Model: MSL G3 SeriesRev: 4.60 Type: Medium Changer ANSI SCSI revision: 05 Sorry bad informations in my previous email On Wed, September 9, 2009 12:40 am, Ben Hutchings wrote: > On Tue, 2009-09-08 at 23:24 +0200, Olivier JUDITH wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> >> Hi, >> >> I recently received 2 HP DL360 G6 with additional SAS controller HP >> P410i ZM (Zero memory) to interface with a HPLTO3 Library . >> I started Debian lenny 5.02 (2.6.26-2) but SAS controller is not >> detected . > > Linux 2.6.26 includes support for P410i and the ZM configuration. I > think the problem may lie elsewhere. > > When you say you 'started Debian', do you mean you started to install > it, or that you installed it but it did not boot afterwards? > > Can you send a kernel log from the Debian kernel? If you cannot save it > to a file, please take a photograph. > > Ben. > > -- > Ben Hutchings > Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Sun, Aug 16, 2009 at 14:41:24 +0200, Marc Brockschmidt wrote: > * How many "big" transitions will the upcoming changes cause? When > should those happen? Can we do something to make them easier? > One more thing. Intel plans to deprecate userspace mode setting with their Q4 2009 release (meaning December this year, so probably something we'll want for squeeze, depending on the freeze date you pick). This means the intel X driver won't work with lenny's kernel, so we might have to figure out an upgrade path somehow (which might be to make the driver fall back to the vesa driver if it doesn't find a modesetting-capable kernel). This might also mean that we'll want to turn kms on by default in the debian kernel, or have xserver-xorg-video-intel install a file in /etc/modprobe.d/ to set i915.modeset. cc:ing debian-kernel as a heads-up. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#415068: I can reproduce #415068 on a UltraSparc 5 over USB serial adapter
Hi Moritz, On Tue, Sep 08, 2009 at 10:02:32PM +0200, Moritz Muehlenhoff wrote: > On Sat, Jul 18, 2009 at 12:32:00AM +0200, Moritz Muehlenhoff wrote: > > On Wed, Dec 12, 2007 at 09:58:43PM +0100, Axel Beckert wrote: > > Does this error still occur with the Lenny kernel? sorry that I didn't answer in time -- you guessed the problem partially: > Do you still own such a system? Yes, and it's also running Lenny -- the remote dist-upgrade went fine. But I don't have it on serial console anymore and it's in production at an offsite location, so difficult to reach and use for debugging kernel crashes. :-/ I noticed the error when I had the box here to replace the harddisk and used serial console because I didn't have a 13W3 capable monitor. At home, I have an UltraSparc 10 (should be the same as UltraSparc 5, except that it has a VGA graphics card and it's a tower case instead of a pizza box) running Sid. I could install Lenny kernels and test with them. I'm though not sure how much influence the graphics card and using grub instead of silo will have. At least on kfreebsd, using grub instead of the freebsd loader caused some differences (until grub had been fixed). Do you think it's worth a try anyway? Would Etch kernels still run with Sid, so that I can cross check? Regards, Axel Beckert -- Axel Beckertsupport: +41 44 633 26 68 IT Services Group, HPT D 17 voice: +41 44 633 41 89 Departement of Physics, ETH Zurich CH-8093 Zurich, Switzerlandhttp://nic.phys.ethz.ch/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#535008: News on BOOTIF variable support for pxelinux?
Hi Is there any change for that to be integrated? We also experience the issues mentioned by Vagrant Cascadian. Bests Salvatore signature.asc Description: Digital signature
Re: Bug#465278: Appletouch failure upon resume after suspend2ram
> > Does this error still occur with more recent kernel versions, such > > as the 2.6.30 kernel from unstable? Yes it does. -- Raf http://www.catb.org/~esr/faqs/smart-questions.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
