Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
On Wed, Oct 24, 2012 at 11:27:51PM +0100, Julian Gilbey wrote: The only interesting recent sky2 patch I can find upstream is v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How does a kernel with that patch applied behave? A 3.6.y kernel should be hitting experimental this weekend, or if you'd like to try the patch before then, see [1]. That seems to work on my home network - I'll try it at work tomorrow, all being well, and let you know how that goes. Here's hoping Yes, that seems to have fixed the problem! Cool! Julian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025094617.gd4...@d-and-j.net
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Am 24.10.2012 02:39, schrieb Jonathan Nieder: Hi Per, Per Foreby wrote: Just to clear some confusion: In a previous comment you suggested trying 3.2.30-1 first (which seems to have been replaced by 3.2.32-1 a few days ago). So what should I try, and in what order? I have downloaded the following packages: What I just found in the german Debian Forum https://debianforum.de/forum/viewtopic.php?f=26t=137332 is the same observed on a ThinkPad T430 with a i5-3320M 2.60 GHz, HD4000 graphics and Wheezy (reported 2012-07-26) - translated into English: ... to avoid *priodic freezes* I updated the kernel to 3.4.4-1 from experimental ... Meanwhile the author has updated to kernel 3.5.5-1-amd64 and all appears still fine. Just my 2 cents, Ingo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5089184c.3040...@gmx.net
Bug#690814: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000
--- On Wed, 10/17/12, Jonathan Nieder jrnie...@gmail.com wrote: From: Jonathan Nieder jrnie...@gmail.com Subject: Re: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000 To: Frank Lenaerts frank.lenae...@yahoo.com Cc: 690...@bugs.debian.org Date: Wednesday, October 17, 2012, 11:19 PM # regression severity 690814 important quit Hi Frank, Frank Lenaerts wrote: I had to use the power button to restart the machine. The first time I rebooted, the system got stuck when trying to mount one of the filesystems. Rebooted again and got the login prompt. Did some more reboots and found out that the system hangs during more or less 50% of the reboots. Since the disk activity LED was always on, I tried to provoke some disk activity e.g. by installing some packages. This effectively locked up the system. I only once got the system in a locked up state without having the disk activity LED turned on. [...] Since this machine had been running Lenny just fine, and Squeeze also worked fine, I decided to install a 2.6 kernel. [...] Note that it took several reboots to get the deb file on the system and to install it. With this kernel, the box runs just fine. Thanks for reporting it. A few suggestions for moving forward: [...snipped...] * if you have time to run a bisection search through the pre-compiled kernels at http://snapshot.debian.org/package/linux-2.6/ to find the first broken one, that could help narrow down things quite a bit. Tested some of the linux images: - 2.6.39 seems ok - 3.0.0-1 seems ok - 3.1.0-1 seems ok - 3.2.0-1 does not seem to be ok: - first boot: system hung at Loading, please wait...; note that the LED indicating disk activity was not burning - second boot: ok - third boot: ok Had it running and used it for a few days. Then decided to give 3.2.0-3 a try again. - 3.2.0-3 is not ok: - first boot: crash during the boot process i.e. detected the external USB disk (which I had connected again while working with 3.2.0-1), makefile style concurrent boot, hotplug, udev... stacktrace (not sure if it was after or before the hotplug stuff; unfortunately didn't have logging turned on and keyboard was stuck)... boot process continued a bit and then hung; note that the LED was not on; since I've now seen quite some lockups without this LED being on, I think it does not necessarily have anything to do with disk activity - seond boot: stuck in Configuring network interfaces; note that I've seen this more than once already So, it looks like we'll have to investigate the differences between -1 and -3. Question: 3.2.0-3 was the one installed during the installation. 3.2.0-1 was installed by me for testing purposes and came from 3.2.1-1. I see that the snapshot directory contains other 3.2.0-1 e.g. under 3.2.2-1. Why is it like that? I see that the 3.2.19-1 directory contains 3.2.0-2 for instance and it seems that 3.2.0-3 is not in the snapshot directory...Hope that helps, and sorry I have no better ideas, Jonathan [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Source: linux Version: 3.2.32-1 Severity: important Tags: upstream Hi dear linux maintainers, I have setup a Debian Wheezy on a brand new Lenovo Thinkpad T430s with a SSDSC2BW180A3L SSD drive. After the install, the user installed his usual softwares (solr, apache, nodejs, …) and started work. Under some load (importing thousands of records in MySQL via a hand-called PHP script), the system reliably stops working fine enough because of journal commit I/O error leading to a readonly filesystem. Then Gnome becomes (obviously) unuseable and the only way out is a hard-reboot. The disk looks fine (and is brand new), according to the BIOS disk report and SMART tests, so the usual suspiscion that it might be broken is improbable. We have reproduced this bug under 3.2.0-4 (3.2.23-1), 3.2.0-5 (3.2.32-1) and 3.5-trunk (3.5.5-1~experimental.1). The setup is an ext4 / (and /home) on LVM, on the mentionned SSD. What are the things we could do to help resolve this bug? Are there logs that you might want to get? Please advise! Cheers, OdyX, on behalf of Dorian Villet, owner of the (unuseable) T430s. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025145608.8828.41282.reportbug@gyllingar
Processed: owner 691427
Processing commands for cont...@bugs.debian.org: owner 691427 Dorian Villet dorian.vil...@liip.ch Bug #691427 [src:linux] journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD Owner recorded as Dorian Villet dorian.vil...@liip.ch. thanks Stopping processing here. Please contact me if you need assistance. -- 691427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135117765027669.transcr...@bugs.debian.org
Processed: bug 691427 has no owner, submitter 691427
Processing commands for cont...@bugs.debian.org: noowner 691427 Bug #691427 [src:linux] journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD Removed annotation that Bug was owned by Dorian Villet dorian.vil...@liip.ch. # Whoops. submitter 691427 Dorian Villet dorian.vil...@liip.ch Bug #691427 [src:linux] journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD Changed Bug submitter to 'Dorian Villet dorian.vil...@liip.ch' from 'Didier Raboud o...@debian.org' thanks Stopping processing here. Please contact me if you need assistance. -- 691427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135117830532352.transcr...@bugs.debian.org
Processed: [bts-link] source package src:linux
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #686284 (http://bugs.debian.org/686284) # Bug title: linux-image-3.2.0-3-686-pae: i915 locks up my Thinkpad X30 (using a GMA 82830) # * https://bugs.freedesktop.org/show_bug.cgi?id=54615 # * remote status changed: NEEDINFO - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 686284 + fixed-upstream Bug #686284 [src:linux] linux-image-3.2.0-3-686-pae: i915 locks up my Thinkpad X30 (using a GMA 82830) Added tag(s) fixed-upstream. usertags 686284 - status-NEEDINFO Usertags were: status-NEEDINFO. Usertags are now: . usertags 686284 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 686284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13511837184927.transcr...@bugs.debian.org
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #686284 (http://bugs.debian.org/686284) # Bug title: linux-image-3.2.0-3-686-pae: i915 locks up my Thinkpad X30 (using a GMA 82830) # * https://bugs.freedesktop.org/show_bug.cgi?id=54615 # * remote status changed: NEEDINFO - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 686284 + fixed-upstream usertags 686284 - status-NEEDINFO usertags 686284 + status-RESOLVED resolution-FIXED thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025163344.25804.57813.btsl...@sonntag.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags #665493 upstream fixed-upstream Bug #665493 [linux-2.6] linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:) Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 665493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13511929675142.transcr...@bugs.debian.org
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
found 691427 linux/3.2.23-1 , linux/3.5.5-1~experimental.1 quit Hi, Didier Raboud wrote: Tags: upstream What upstream version did you test? [...] Under some load (importing thousands of records in MySQL via a hand-called PHP script), the system reliably stops working fine enough because of journal commit I/O error leading to a readonly filesystem. Then Gnome becomes (obviously) unuseable and the only way out is a hard-reboot. Can you get full dmesg output when in this state? A serial console[1] or netconsole[2] might be helpful in obtaining that, or if that's not possible, a photograph of messages on the screen will do in a pinch. Thanks for reporting, and hope that helps, Jonathan [1] if you are lucky enough to have a docking station with serial port: http://www.kernel.org/doc/Documentation/serial-console.txt [2] http://www.kernel.org/doc/Documentation/networking/netconsole.txt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025202503.GE30334@elie.Belkin
Processed: Re: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Processing commands for cont...@bugs.debian.org: found 691427 linux/3.2.23-1 , linux/3.5.5-1~experimental.1 Bug #691427 [src:linux] journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD Marked as found in versions linux/3.5.5-1~experimental.1 and linux/3.2.23-1. quit Stopping processing here. Please contact me if you need assistance. -- 691427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135119671428720.transcr...@bugs.debian.org
Bug#690814: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000
Frank Lenaerts wrote: Tested some of the linux images: - 2.6.39 seems ok - 3.0.0-1 seems ok - 3.1.0-1 seems ok - 3.2.0-1 does not seem to be ok: - first boot: system hung at Loading, please wait...; note that the LED indicating disk activity was not burning - second boot: ok - third boot: ok Had it running and used it for a few days. Then decided to give 3.2.0-3 a try again. - 3.2.0-3 is not ok: Thanks much for this. [...] - first boot: crash during the boot process i.e. detected the external USB disk (which I had connected again while working with 3.2.0-1), makefile style concurrent boot, hotplug, udev... stacktrace (not sure if it was after or before the hotplug stuff; unfortunately didn't have logging turned on and keyboard was stuck)... For the future, photographs work fine if you can catch the machine at the right moment. [...] Question: 3.2.0-3 was the one installed during the installation. 3.2.0-1 was installed by me for testing purposes and came from 3.2.1-1. I see that the snapshot directory contains other 3.2.0-1 e.g. under 3.2.2-1. Why is it like that? Package names like linux-image-3.2.0-1-486 describe the kernel's ABI, not the package version. The package version is something like 3.2.1-1. See http://kernel-handbook.alioth.debian.org/ch-versions.html for more details. You can get the version of the currently running kernel by running cat /proc/version (it will be in parentheses). The currently installed kernel's version number can be retrieved with dpkg-query -W linux-image-$(uname -r). Which versions were the 3.2.0-1, 3.2.0-2, and 3.2.0-3 kernels you mentioned testing above? Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025203420.GF30334@elie.Belkin
Bug#690814: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000
Jonathan Nieder wrote: Package names like linux-image-3.2.0-1-486 describe the kernel's ABI, not the package version. The package version is something like 3.2.1-1. See http://kernel-handbook.alioth.debian.org/ch-versions.html for more details. You can get the version of the currently running kernel by running cat /proc/version (it will be in parentheses). The currently installed kernel's version number can be retrieved with dpkg-query -W linux-image-$(uname -r). Which versions were the 3.2.0-1, 3.2.0-2, and 3.2.0-3 kernels you mentioned testing above? I mean 3.1.0-1, 3.2.0-1, 3.2.0-3 here. Sorry for the lack of clarity. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025204154.GG30334@elie.Belkin
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
I am back and join the injured. today I again had the known freeze after 3 weeks of freedom with 256MB GPU-RAM BIOS setting. So my remedy did not cure the root cause. I now installed kernel 3.5.5-1 from experimental - let's see. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5089aab3.8060...@gmx.net
Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
tags 681280 + upstream patch forwarded 681280 http://thread.gmane.org/gmane.linux.network/235795/focus=247154 quit Julian Gilbey wrote: Jonathan Nieder wrote: A 3.6.y kernel should be hitting experimental this weekend, or if you'd like to try the patch before then, see [1]. [...] Yes, that seems to have fixed the problem! Cool! Nice to hear. Passed upstream, so hopefully this will be part of the stable trees on kernel.org soon. Of course that's no reason for the Debian kernel maintainers not to pick it up first (hint, hint). Regards, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025224433.GH30334@elie.Belkin
Processed: Re: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
Processing commands for cont...@bugs.debian.org: tags 681280 + upstream patch Bug #681280 [src:linux] kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out Bug #687791 [src:linux] sky2: TX watchdog timeout on Yukon-2 FE+ Added tag(s) upstream and patch. Added tag(s) upstream and patch. forwarded 681280 http://thread.gmane.org/gmane.linux.network/235795/focus=247154 Bug #681280 [src:linux] kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out Bug #687791 [src:linux] sky2: TX watchdog timeout on Yukon-2 FE+ Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.network/235795/focus=247154'. Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.network/235795/focus=247154'. quit Stopping processing here. Please contact me if you need assistance. -- 681280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681280 687791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120508523087.transcr...@bugs.debian.org
Processed: Re: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages
Processing commands for cont...@bugs.debian.org: # Brian Kroth wrote: # # Got another panic using this kernel/set of patches. The dump is attached. tags 682007 - patch moreinfo Bug #682007 [src:linux] linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference in __fscache_read_or_alloc_pages Bug #682116 [src:linux] linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference related to nfs/cachefilesd Removed tag(s) moreinfo and patch. Removed tag(s) moreinfo and patch. End of message, stopping processing here. Please contact me if you need assistance. -- 682007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682007 682116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120521924177.transcr...@bugs.debian.org
Processed: Re: [experimental] linux: please update to 3.6-rc series
Processing commands for cont...@bugs.debian.org: tags 688834 + pending Bug #688834 [src:linux] [experimental] linux: please update to 3.6-rc series Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 688834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120566127334.transcr...@bugs.debian.org
Bug#686711: [experimental] acpi error with ASUS P8P67 LE
tags 686711 - moreinfo found 686711 linux/3.5.5-1~experimental.1 severity 686711 minor quit Hi again, gpe wrote: gpe92 wrote: I'm using an ASUS P867 LE moterboard with the last BIOS 3602 and in messages I've : [...] I've tested with the kernel 3.5.5 from experimental and the problem remains present. Thanks for checking, and sorry for the slow reply. Please attach full dmesg and acpidump output. Am I correct in understanding that except for the messages this kernel works ok so far? Yours, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025225829.GI30334@elie.Belkin
Processed: Re: [experimental] acpi error with ASUS P8P67 LE
Processing commands for cont...@bugs.debian.org: tags 686711 - moreinfo Bug #686711 [src:linux] linux-image-3.4-trunk-686-pae: acpi error with ASUS P8P67 LE Removed tag(s) moreinfo. found 686711 linux/3.5.5-1~experimental.1 Bug #686711 [src:linux] linux-image-3.4-trunk-686-pae: acpi error with ASUS P8P67 LE Marked as found in versions linux/3.5.5-1~experimental.1. severity 686711 minor Bug #686711 [src:linux] linux-image-3.4-trunk-686-pae: acpi error with ASUS P8P67 LE Severity set to 'minor' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 686711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120591928847.transcr...@bugs.debian.org
Processed: Re: suspending a Lenovo Thinkpad X131e AMD crashes on resume
Processing commands for cont...@bugs.debian.org: # Phil Reynolds wrote: # On 03/10/12 16:02, Ben Hutchings wrote: # # Please remove the broadcom-sta driver (rmmod wl) and re-test. # # Well, it worked, for a while, when I tried this, but is now failing # again in exactly the same way, even though I've added config to deal # with the wl module. # # I can hibernate OK (apart from the fact it needs to be triggered from a # root command prompt), but suspend is still troublesome. tags 689516 - moreinfo Bug #689516 [src:linux] linux-image-3.2.0-3-amd64: suspending a Lenovo Thinkpad X131e AMD crashes on resume Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 689516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120645132239.transcr...@bugs.debian.org
Processed: Re: user space serial console messages held back on HS20 blade until qla2xxx is loaded
Processing commands for cont...@bugs.debian.org: # Ferenc Wagner wrote: # Ben Hutchings b...@decadent.org.uk writes: # # Please test Linux 3.5 (as packaged in experimental) or 3.6. # # Forgot to say that I've already partially tested 3.6 (minimal config, no # modules, no qla2xxx driver): no user space console at all. I couldn't # test whether loading the module eventually activates it, but the problem # definitely seems to be there. I'll fully test the packaged 3.5 shortly. # [...] # I tried the same in another IBM Bladecenter with slightly different # parts and firmware versions. There loading qla2xxx does not fix the # user space console output. Even worse (on a virtual console): # [etc] tags 690727 - moreinfo Bug #690727 [src:linux] linux-image-3.2.0-3-686-pae: user space serial console messages held back on HS20 blade until qla2xxx is loaded Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 690727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135120656932730.transcr...@bugs.debian.org
Bug#684926: marked as done (linux: disable CONFIG_CC_OPTIMIZE_FOR_SIZE)
Your message dated Thu, 25 Oct 2012 16:12:26 -0700 with message-id 20121025231226.GA1758@elie.Belkin and subject line Re: linux: disable CONFIG_CC_OPTIMIZE_FOR_SIZE has caused the Debian Bug report #684926, regarding linux: disable CONFIG_CC_OPTIMIZE_FOR_SIZE 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.) -- 684926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux Severity: wishlist Hi. Is there any reasons why you've enabled CONFIG_CC_OPTIMIZE_FOR_SIZE? From the help: Enabling this option will pass -Os instead of -O2 to gcc resulting in a smaller kernel. From gcc: Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size. -Os disables the following optimization flags: -falign-functions -falign-jumps -falign-loops -falign-labels -freorder-blocks -freorder-blocks-and-partition -fprefetch-loop-arrays -ftree-vect-loop-version So we loose all kinds of optimisations just for storage, which really doesn't count on all but embedded systems. Cheers, Chris. ---End Message--- ---BeginMessage--- Hi, Christoph Anton Mitterer wrote: On Tue, 2012-08-14 at 21:57 +0100, Ben Hutchings wrote: Is there any reasons why you've enabled CONFIG_CC_OPTIMIZE_FOR_SIZE? [...] Larger code results in more I-cache misses, so it can be slower after all. Let's see your benchmark results. Well.. I guess making usable benchmarks there is really difficult,.. Not really. :) All it would take is one important use case that gets faster to get the conversation started. Until then, I can't see much reason to pursue this, so closing. Thanks, Jonathan---End Message---
Debian kernel hangs during boot under KVM with more than 4 vcpus
Hi guys, Since this issue seems to be Debian related, I'm posting it here, too. I have a problem with KVM. I try to describe the problem as much detailed as possible so please bear with me. I have CentOS 6.3 installed on a server with dual Xeon CPU's. CentOS was installed a week ago fresh, no unofficial packages are installed. CentOS is up-to-date. Kernel is the stock kernel: 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Motherboard info: http://www.supermicro.com/products/m...0/X9DRT-HF.cfm CPU info (we have two of these): Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz http://ark.intel.com/products/64594/...-GTs-Intel-QPI Generally kvm-qemu works. But my Debian guest OS (Debian squeeze with 2.6.32 or 3.2.x.x kernel) won't boot up if I assign more than 4 vcpus to the guest. What happens is the kernel starts to load then it freezes right where it should load the Linux agpgart module. It just hangs there. I can hit enter in the console and the cursor moves down but that's all what I can do besides force-shutoff the guest vm. If I change the VM's config to have just 4 vcpus then it boots up most of the time. Sometimes it hangs with just 4 vcpus, too. When it hangs, it always hangs at the same point, so it is consistent. Changing the amount of RAM of the VM also have an effect: with 6GB or less RAM assigned to the VM it most likely boots up fine. With 8GB RAM, however, it will boot up about 50% of the time and it hangs the other 50% of the time. My Debian guest VM *never* booted up with 6 or more vcpus. Again, with 4 vcpus it may or may not boot up but if I add a total of 8GB RAM it will more likely hang at bootup. I don't change anything else between these tries just the number of vcpus or the amount of RAM. I have tried to use a newer Debian kernel installed from Debian backports (3.2.x.x Linux kernel), but it did not help. What happens is exactly the same thing. I also have other Debian VM images (some of them are raw image file based some of them are LVM block device based) and I can reproduce the problem with all of these Debian VMs. My problem somewhat resembles this one: http://forum.parallels.com/showthread.php?t=4882 except that I'm not using parallels at all, I am trying to use kvm-qemu under CentOS 6.3 But this part seems to apply: I did experience some relief ... by changing the amount of available RAM, but that has no longer prevented the intel-agp kernel panic recently. I've tried to blacklist the agpgart module inside my guest OS to no avail. Here is what I've added to the end of /etc/modprobe.d/blacklist.conf : blacklist agpgart blacklist intel-agp However, when the VM happens to boot up then I still see a reference to agpgart in dmesg (snippet): Oct 25 23:27:01 infoglobal kernel: [ 0.864798] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Oct 25 23:27:01 infoglobal kernel: [ 0.865650] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 Oct 25 23:27:01 infoglobal kernel: [ 0.866538] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Oct 25 23:27:01 infoglobal kernel: [ 0.867484] acpiphp: Slot [1] registered Oct 25 23:27:01 infoglobal kernel: [ 0.868250] acpiphp: Slot [2] registered Oct 25 23:27:01 infoglobal kernel: [ 0.868995] acpiphp: Slot [3] registered Oct 25 23:27:01 infoglobal kernel: [ 0.869750] acpiphp: Slot [4] registered Oct 25 23:27:01 infoglobal kernel: [ 0.870489] acpiphp: Slot [5] registered Oct 25 23:27:01 infoglobal kernel: [ 0.871233] acpiphp: Slot [6] registered Oct 25 23:27:01 infoglobal kernel: [ 0.871959] acpiphp: Slot [7] registered Oct 25 23:27:01 infoglobal kernel: [ 0.872735] acpiphp: Slot [8] registered Oct 25 23:27:01 infoglobal kernel: [ 0.873472] acpiphp: Slot [9] registered Oct 25 23:27:01 infoglobal kernel: [ 0.874222] acpiphp: Slot [10] registered Oct 25 23:27:01 infoglobal kernel: [ 0.874958] acpiphp: Slot [11] registered Oct 25 23:27:01 infoglobal kernel: [ 0.875705] acpiphp: Slot [12] registered Oct 25 23:27:01 infoglobal kernel: [ 0.876494] acpiphp: Slot [13] registered Oct 25 23:27:01 infoglobal kernel: [ 0.877237] acpiphp: Slot [14] registered Oct 25 23:27:01 infoglobal kernel: [ 0.877987] acpiphp: Slot [15] registered Oct 25 23:27:01 infoglobal kernel: [ 0.878749] acpiphp: Slot [16] registered Oct 25 23:27:01 infoglobal kernel: [ 0.879517] acpiphp: Slot [17] registered Oct 25 23:27:01 infoglobal kernel: [ 0.880299] acpiphp: Slot [18] registered Oct 25 23:27:01 infoglobal kernel: [ 0.881042] acpiphp: Slot [19] registered Oct 25 23:27:01 infoglobal kernel: [ 0.881791] acpiphp: Slot [20] registered Oct 25 23:27:01 infoglobal kernel: [ 0.882546] acpiphp: Slot [21] registered Oct 25 23:27:01 infoglobal kernel: [ 0.883292] acpiphp: Slot [22] registered Oct 25 23:27:01 infoglobal kernel: [ 0.884045] acpiphp: Slot [23] registered Oct 25 23:27:01 infoglobal kernel: [ 0.884796] acpiphp: Slot [24] registered Oct 25 23:27:01 infoglobal kernel: [ 0.885545]
