Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
Hello, On Wed, Oct 24, 2012 at 10:52:48PM +0100, Julian Gilbey wrote: Oh, it just finished this time! I now understand why it took so long - the -dbg package is *huge*! It would be nice to get support for DEBIAN_KERNEL_USE_CCACHE and DEBIAN_KERNEL_DISABLE_DEBUG info test-patches. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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/20121026082600.go...@pengutronix.de
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Hi Jonathan, Le jeudi, 25 octobre 2012 22.25:03, Jonathan Nieder a écrit : Didier Raboud wrote: Tags: upstream What upstream version did you test? Well we only tried packaged kernels, all wheezy, unstable and experimental exhibit this behaviour. We started to compile an upstream kernel but didn't try yet. I tagged this bug as upstream, considering it's probably not a bug of the packaging. 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. I'll let Dorian send that to the bug, we'll see what that gives. Cheers, OdyX -- 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/201210261344.35883.o...@debian.org
Bug#690814: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000
--- On Thu, 10/25/12, Jonathan Nieder jrnie...@gmail.com wrote: From: Jonathan Nieder jrnie...@gmail.com Subject: Re: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000 To: Frank Lenaerts frank.lenae...@yahoo.com Cc: 690...@bugs.debian.org Date: Thursday, October 25, 2012, 10:41 PM 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. I just used uname -r and left out '-486' (because that's always the same on this box).
Re: autobuilding src:nvidia-* [non-free]
On Mon, Aug 06, 2012 at 04:02:30PM +0200, Philipp Kern wrote: am Mon, Aug 06, 2012 at 11:47:21AM +0200 hast du folgendes geschrieben: nvidia-cg-toolkit nvidia-cuda-toolkit nvidia-graphics-drivers nvidia-graphics-drivers-legacy-173xx nvidia-graphics-drivers-legacy-96xx nvidia-graphics-drivers-legacy-71xx nvidia-graphics-modules Done for all of them. nvidia-graphics-modules, if it stays in testing, needs to be updated for every new kernel ABI and be unblocked when linux is unblocked. Otherwise it becomes useless. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#599161: #599161: Xen debug patch for the clock shifts by 50 minutes bug.
Hi all,
I've BCC'd a number of people who have reported seeing this bug at
various times in the past.
If you can still repro I'd appreciate it if you could give the patch in
http://marc.info/?l=xen-develm=135049062216685w=2 (also attached) a go
and report back success/failure and the output of the debugging messages
produced.
Thanks,
Ian.
--
Ian Campbell
Current Noise: Death - Evil Dead
Executive ability is prominent in your make-up.
diff -r c1c549c4fe9e xen/arch/x86/time.c
--- a/xen/arch/x86/time.c Mon Oct 15 16:51:44 2012 +0100
+++ b/xen/arch/x86/time.c Wed Oct 17 17:13:22 2012 +0100
@@ -523,11 +523,12 @@ static s_time_t __read_platform_stime(u6
static void plt_overflow(void *unused)
{
int i;
-u64 count;
+u64 count, old_stamp, tsc;
s_time_t now, plt_now, plt_wrap;
spin_lock_irq(platform_timer_lock);
+old_stamp = plt_stamp;
count = plt_src.read_counter();
plt_stamp64 += (count - plt_stamp) plt_mask;
plt_stamp = count;
@@ -540,6 +541,14 @@ static void plt_overflow(void *unused)
plt_wrap = __read_platform_stime(plt_stamp64 + plt_mask + 1);
if ( ABS(plt_wrap - now) ABS(plt_now - now) )
break;
+rdtscll(tsc);
+printk(XXX plt_overflow: plt_now=%PRIx64 plt_wrap=%PRIx64
+now=%PRIx64 old_stamp=%PRIx64 new_stamp=%PRIx64
+plt_stamp64=%PRIx64 plt_mask=%PRIx64
+tsc=%PRIx64 tsc_stamp=%PRIx64\n,
+ plt_now, plt_wrap, now, old_stamp, plt_stamp, plt_stamp64,
+ plt_mask, tsc, this_cpu(cpu_time).local_tsc_stamp);
+break;
plt_stamp64 += plt_mask + 1;
}
if ( i != 0 )
Bug#599161: #599161: Xen debug patch for the clock shifts by 50 minutes bug.
On 26 October 2012 14:59, Ian Campbell i...@hellion.org.uk wrote: Hi all, I've BCC'd a number of people who have reported seeing this bug at various times in the past. If you can still repro I'd appreciate it if you could give the patch in http://marc.info/?l=xen-develm=135049062216685w=2 (also attached) a go and report back success/failure and the output of the debugging messages produced. Is that patch for amd64 architectures? -- 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/CAE17a0WfpKHxN=3if6f+p0nt4ubyf9lbpm8r5+jjequqomu...@mail.gmail.com
Bug#599161: [Xen-devel] #599161: Xen debug patch for the clock shifts by 50 minutes bug.
On Fri, 2012-10-26 at 19:25 +0100, Mauro wrote: On 26 October 2012 14:59, Ian Campbell i...@hellion.org.uk wrote: Hi all, I've BCC'd a number of people who have reported seeing this bug at various times in the past. If you can still repro I'd appreciate it if you could give the patch in http://marc.info/?l=xen-develm=135049062216685w=2 (also attached) a go and report back success/failure and the output of the debugging messages produced. Is that patch for amd64 architectures? It is for 32 and 64 bit x86, so yes. BTW, you were the original recipient of this patch in the thread linked above. Ian. -- Ian Campbell I'd love to go out with you, but I'm having all my plants neutered. -- 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/1351276803.12176.4.ca...@dagon.hellion.org.uk
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Just a little bit of info I found reading the last changes to the X intel driver: Release 2.20.9 (2012-09-29) === And so it came to pass that a critical bug was uncovered in UXA. The kernel does not like to pageflip when the pipe is off, yet due to the delayed nature of a pageflip and the relaxed checking performed by UXA, we could request a pageflip after turning off the display (DPMS). The kernel rejected that pageflip and the error handling path failed to restore sanity, and when the screen came back it was stuck on the image seen before it went to sleep. (Note that there are also some related kernel bugs, but this update should prevent the most conspicious of the freezes.) Many thanks to Timo Aaltonen for his efforts in tracking down the issue. [...] This is not the kernel bug, but the graphics bug. However, maybe is not a bad idea to upgrade the X driver and see what happen with 3.2.x. -- Saludos de Javier jcant...@escomposlinux.org signature.asc Description: Digital signature
Bug#666108: (no subject)
Any update on this? Just pulled down squeeze 6.0.6 and it still cannot find the PERC H710P on a Dell 720. -- 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/508ae434.7030...@gmail.com
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM,
Hi, kernel is 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux, test with: SSD + 8gB. nothing crashed for 28 hours. I also managed to copy 3 files (5-8 gB per file) to another pc via ethernet and the md5sums were ok. I also did the opposite (the other pc already had the known good files before these tests) copying the files from that pc to the notebook, md5sum comparison was ok. So, i thought Test will pass and the uptime will reach 5 or more days .. no :( at uptime == ~27 hours i decided to unmount the 1gB ramdisk , to mount a 4gB ramdisk. i then started using it and xfce4-terminal crashed, on the screen this log appeared: Oct 26 20:57:50 --- kernel: [102454.988228] general protection fault: [#1] SMP Oct 26 20:57:50 --- kernel: [102454.988291] CPU 0 Oct 26 20:57:50 --- kernel: [102454.988315] Modules linked in: nfnetlink usb_storage uas cpufreq_conservative cpufreq_powersave cpufreq_stats bbswitch (O) cpufreq_userspace uinput ext4 crc16 jbd2 loop snd_hda_codec_hdmi snd_hda_codec_conexant joydev arc4 ath9k ath9k_co mmon ath9k_hw ath uvcvideo mac80211 videodev jmb38x_ms v4l2_compat_ioctl32 mxm_wmi media coretemp crc32c_intel pcspkr psmouse evdev serio_raw intel_ips memstick cfg80211 battery snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq snd_seq_device snd_tim er iTCO_wdt ac i915 power_supply iTCO_vendor_support video snd drm_kms_helper drm wmi asus_laptop i2c_algo_bit sparse_keymap i2c_core rfkill acpi_cpufreq input_polldev soundcore mperf button processor ext3 mbcache jbd sg sr_mod sd_mod cdrom crc_t10dif jme mii ahci liba hci libata scsi_mod sdhci_pci sdhci mmc_core ehci_hcd usbcore usb_common thermal thermal_sys [last unloaded: nvidia] Oct 26 20:57:50 --- kernel: [102454.989347] Oct 26 20:57:50 --- kernel: [102454.989366] Pid: 2684, comm: xfce4-terminal Tainted: P O 3.2.0-3-amd64 #1 ASUSTeK Computer Inc. K52Jc/K52Jc Oct 26 20:57:50 --- kernel: [102454.989483] RIP: 0010:[81107e76] [81107e76] do_sys_poll+0x1af/0x347 Oct 26 20:57:50 --- kernel: [102454.989569] RSP: 0018:8802403e9b68 EFLAGS: 00010286 Oct 26 20:57:50 --- kernel: [102454.989621] RAX: 0145 RBX: RCX: efff817f6fa0 Oct 26 20:57:50 --- kernel: [102454.989690] RDX: 880036d09480 RSI: 880037080098 RDI: 880036d094b0 Oct 26 20:57:50 --- kernel: [102454.989758] RBP: 7f51a009d160 R08: R09: 88003708 Oct 26 20:57:50 --- kernel: [102454.989826] R10: 88023ebe7510 R11: 88023ebe7510 R12: Oct 26 20:57:50 --- kernel: [102454.989934] R13: 8802403e9e4c R14: 0001 R15: 8802403e9e08 Oct 26 20:57:50 --- kernel: [102454.990041] FS: 7f519da01960() GS: 88024bc0() knlGS: Oct 26 20:57:50 --- kernel: [102454.990162] CS: 0010 DS: ES: CR0: 80050033 Oct 26 20:57:50 --- kernel: [102454.990248] CR2: 7f3c7a990181 CR3: 00023ffcc000 CR4: 06f0 Oct 26 20:57:50 --- kernel: [102454.990355] DR0: DR1: DR2: Oct 26 20:57:50 --- kernel: [102454.990461] DR3: DR6: 0ff0 DR7: 0400 Oct 26 20:57:50 --- kernel: [102454.990567] Process xfce4-terminal (pid: 2684, threadinfo 8802403e8000, task 88023ebe7510) Oct 26 20:57:50 --- kernel: [102454.990696] Stack: Oct 26 20:57:50 --- kernel: [102454.990730] 8802 0282 8802403e9e74 Oct 26 20:57:50 --- kernel: [102454.990856] 88023ebe7510 8110717b 0019 Oct 26 20:57:50 --- kernel: [102454.990982] 8802413fa000 88023ebe7510 88020009 Oct 26 20:57:50 --- kernel: [102454.991107] Call Trace: Oct 26 20:57:50 --- kernel: [102454.991153] [8110717b] ? poll_freewait+0x97/0x97 Oct 26 20:57:50 --- kernel: [102454.991240] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991322] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991404] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991487] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991570] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991652] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991734] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991817] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991899] [81107249] ? __pollwait+0xce/0xce Oct 26 20:57:50 --- kernel: [102454.991984] [81108099] ? sys_poll+0x43/0xab Oct 26 20:57:50 --- kernel: [102454.992066] [8134fc92] ? system_call_fastpath+0x16/0x1b Oct 26 20:57:50 --- kernel: [102454.992157] Code: ff 78 7e 48 8d b4 24 ac 03 00 00 e8 f5 28 ff
