Bug#681418: #681418 debugfs is a big security hole
Steve Cotton st...@s.cotton.clara.co.uk writes: I'd like to revert the found 681418 3.8.5-1~experimental.1, and close the bug again. sure, please go ahead. Sorry for the confusion. -Timo -- 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/8438qlhmg7@sauna.l.org
Bug#681418: #681418 debugfs is a big security hole
Steve Cotton st...@s.cotton.clara.co.uk writes: For me the mount point changes permission when mounted, and from the hard link count I guess you have it unmounted. tsunami:~# umount /sys/kernel/debug/ tsunami:~# ls -ld /sys/kernel/debug/ drwxr-xr-x 2 root root 0 Jul 30 13:08 /sys/kernel/debug/ tsunami:~# mount -t debugfs none /sys/kernel/debug tsunami:~# ls -ld /sys/kernel/debug/ drwx-- 16 root root 0 Jul 29 08:52 /sys/kernel/debug/ I'm using a local build of 3.10.2. That might indeed be true. I can't reproduce the bug with linux-image-3.10-1-amd64 3.10.3-1 today. -- 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/84d2q0ql3z@sauna.l.org
Bug#681418: #681418 debugfs is a big security hole
package src:linux reopen 681418 found 681418 3.8.5-1~experimental.1 thanks Hi, the issue still exists in experimental lindi3:~$ ls -ld /sys/kernel/debug drwxr-xr-x 2 root root 0 May 5 12:02 /sys/kernel/debug lindi3:~$ cat /proc/version Linux version 3.8-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.5-1~experimental.1 Btw, setting the permissions to 0700 originally broke systemtap: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706817 -- 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/84sj21ye1v@sauna.l.org
Re: [RFC] Putting the date back into utsname::version
Ben Hutchings b...@decadent.org.uk writes: We have a longstanding support problem where there is confusion between the kernel release string (utsname::release, output of uname -r, tail of package names) and the kernel package version. Agreed. Would anyone like to argue in favour of any particular alternative? I don't really care about the format of uname -v but I'd really like to have a stable way to get just the version number part. Now I have: case $DISTRO in Debian) # 2.6.32-39 if uname -v | grep -q Debian; then VERSION=$(uname -v | cut -d -f 4) else VERSION=$(cut -d -f 5 /proc/version | cut -d ) -f 1) fi ;; Ubuntu) # 2.6.32-37.81 VERSION=$(cut -d -f 2 /proc/version_signature | cut -d - -f 1-2) ;; esac -- 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/84620k7zji@sauna.l.org
Bug#691167: #691167 linux-image-3.5-trunk-amd64: please enable CONFIG_UPROBES
Hi, it seems 3.7.3-1~experimental.1 still lacks CONFIG_UPROBES. I'd like to know if there is something I could do to help. Systemtap would greatly benefit. -Timo -- 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/84pq0kl8rt@sauna.l.org
Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found
Package: src:linux Version: 3.7.3-1~experimental.1 Severity: normal With the following configuration the kernel fails to boot as xen domU: pyGRUB version 0.6 ┌┐ │ Debian GNU/Linux, with Linux 3.7-trunk-amd64 │ │ Debian GNU/Linux, with Linux 3.7-trunk-amd64 (recovery mode) │ │ Debian GNU/Linux, with Linux 3.5-trunk-amd64 │ │ Debian GNU/Linux, with Linux 3.5-trunk-amd64 (recovery mode) │ │ Debian GNU/Linux, with Linux 3.2.0-2-amd64 │ │ Debian GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode) │ ││ ││ └┘ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Will boot selected entry in 1 seconds Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') dom0 squeeze amd64 Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 13:49:30 UTC 2012 domU sid amd64 linux-image-3.7-trunk-amd64 3.7.3-1~experimental.1 linux-image-3.5-trunk-amd64 boots successfully. On dom0 I see that xend.log ends with [2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm', ['name', 'lindi3'], ['memory', '1024'], ['on_crash', 'restart'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '4'], ['oos', 1], ['image', ['linux', ['videoram', 4], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'file:/local/xen/lindi3/disk.img'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:01:01:99:2e:5b') [2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:2508) XendDomainInfo.constructDomain [2013-01-30 21:53:28 2182] DEBUG (balloon:220) Balloon: 2102640 KiB free; need 16384; done. [2013-01-30 21:53:28 2182] DEBUG (XendDomain:464) Adding Domain: 15 [2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 15 256 [2013-01-30 21:53:28 1851] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-4.0/bin/pygrub', '--output=/var/run/xend/boot/xenbl.16815', '/local/xen/lindi3/disk.img']. [2013-01-30 21:53:33 2182] DEBUG (XendDomainInfo:2845) _initDomain:shadow_memory=0x0, memory_static_max=0x4000, memory_static_min=0x0. [2013-01-30 21:53:33 2182] INFO (image:182) buildDomain os=linux dom=15 vcpus=4 [2013-01-30 21:53:33 2182] DEBUG (image:721) domid = 15 [2013-01-30 21:53:33 2182] DEBUG (image:722) memsize= 1024 [2013-01-30 21:53:33 2182] DEBUG (image:723) image = /var/run/xend/boot/boot_kernel.33MvmQ [2013-01-30 21:53:33 2182] DEBUG (image:724) store_evtchn = 1 [2013-01-30 21:53:33 2182] DEBUG (image:725) console_evtchn = 2 [2013-01-30 21:53:33 2182] DEBUG (image:726) cmdline= root=UUID=ee66b917-5151-4a4b-944a-99385b7d4d62 ro [2013-01-30 21:53:33 2182] DEBUG (image:727) ramdisk= /var/run/xend/boot/boot_ramdisk.I2OH5Z [2013-01-30 21:53:33 2182] DEBUG (image:728) vcpus = 4 [2013-01-30 21:53:33 2182] DEBUG (image:729) features = [2013-01-30 21:53:33 2182] DEBUG (image:730) flags = 0 [2013-01-30 21:53:33 2182] DEBUG (image:731) superpages = 0 [2013-01-30 21:53:33 2182] ERROR (XendDomainInfo:2909) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File /usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py, line 2880, in _initDomain channel_details = self.image.createImage() File /usr/lib/xen-4.0/lib/python/xen/xend/image.py, line 165, in createImage return self.createDomain() File /usr/lib/xen-4.0/lib/python/xen/xend/image.py, line 184, in createDomain result = self.buildDomain() File /usr/lib/xen-4.0/lib/python/xen/xend/image.py, line 1069, in buildDomain rc = LinuxImageHandler.buildDomain(self) File /usr/lib/xen-4.0/lib/python/xen/xend/image.py, line 745, in buildDomain superpages = self.superpages) Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') [2013-01-30 21:53:33 2182] ERROR (XendDomainInfo:483) VM start failed Traceback (most recent call last): File /usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py, line 469, in start XendTask.log_progress(31, 60, self._initDomain) File /usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py, line 209, in log_progress retval = func(*args, **kwds) File /usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py, line 2912, in _initDomain raise VmError(str(exn)) VmError: (2, 'Invalid kernel',
Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found
Julien Cristau jcris...@debian.org writes: What's your hypervisor? You need one with xz support, see 695056. xen-hypervisor-4.0-amd64 4.0.1-5.5 I guess we could try upgrading the dom0 to testing (wheezy) in a non-production environment but that'll take several weeks at least. -- 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/84txpyl5ik@sauna.l.org
Bug#691167: linux-image-3.5-trunk-amd64: please enable CONFIG_UPROBES
Package: src:linux Version: 3.5.5-1~experimental.1 Severity: wishlist CONFIG_UPROBES lets systemtap place probes on user code just like kprobes lets it to do with kernel code. Support was merged mainline in 3.5. Please consider enabling this option. commit 654443e20dfc0617231f28a07c96a979ee1a0239 Merge: 2c01e7b 9cba26e Author: Linus Torvalds torva...@linux-foundation.org Date: Thu May 24 11:39:34 2012 -0700 Merge branch 'perf-uprobes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull user-space probe instrumentation from Ingo Molnar: The uprobes code originates from SystemTap and has been used for years in Fedora and RHEL kernels. This version is much rewritten, reviews from PeterZ, Oleg and myself shaped the end result. This tree includes uprobes support in 'perf probe' - but SystemTap (and other tools) can take advantage of user probe points as well. Sample usage of uprobes via perf, for example to profile malloc() calls without modifying user-space binaries. First boot a new kernel with CONFIG_UPROBE_EVENT=y enabled. If you don't know which function you want to probe you can pick one from 'perf top' or can get a list all functions that can be probed within libc (binaries can be specified as well): $ perf probe -F -x /lib/libc.so.6 -- Package-specific info: ** Version: Linux version 3.5-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-10) ) #1 SMP Debian 3.5.5-1~experimental.1 ** Command line: root=UUID=ee66b917-5151-4a4b-944a-99385b7d4d62 ro init=/bin/systemd ** Not tainted ** Kernel log: [0.022119] Grant table initialized [0.022119] dummy: [0.022119] NET: Registered protocol family 16 [0.022119] PCI: setting up Xen PCI frontend stub [0.022119] PCI: pci_cache_line_size set to 64 bytes [0.022119] bio: create slab bio-0 at 0 [0.024052] ACPI: Interpreter disabled. [0.024068] xen/balloon: Initialising balloon driver. [0.024068] xen-balloon: Initialising balloon driver. [0.024068] vgaarb: loaded [0.024068] PCI: System does not support PCI [0.024068] PCI: System does not support PCI [0.024147] Switching to clocksource xen [0.025496] pnp: PnP ACPI: disabled [0.028530] NET: Registered protocol family 2 [0.028660] IP route cache hash table entries: 32768 (order: 6, 262144 bytes) [0.029267] TCP established hash table entries: 131072 (order: 9, 2097152 bytes) [0.029903] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [0.030169] TCP: Hash tables configured (established 131072 bind 65536) [0.030178] TCP: reno registered [0.030196] UDP hash table entries: 512 (order: 2, 16384 bytes) [0.030208] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [0.030339] NET: Registered protocol family 1 [0.030353] PCI: CLS 0 bytes, default 64 [0.030386] Unpacking initramfs... [0.061906] Freeing initrd memory: 30480k freed [0.070084] platform rtc_cmos: registered platform RTC device (no PNP device found) [0.070481] audit: initializing netlink socket (disabled) [0.070500] type=2000 audit(1350907337.850:1): initialized [0.080465] HugeTLB registered 2 MB page size, pre-allocated 0 pages [0.080779] VFS: Disk quotas dquot_6.5.2 [0.080806] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.080871] msgmni has been set to 1989 [0.081088] alg: No test for stdrng (krng) [0.081141] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [0.081149] io scheduler noop registered [0.081151] io scheduler deadline registered [0.081176] io scheduler cfq registered (default) [0.081219] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [0.081236] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [0.081240] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.197288] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.197583] Linux agpgart interface v0.103 [0.197659] i8042: PNP: No PS/2 controller found. Probing ports directly. [0.198468] i8042: No controller found [0.198627] mousedev: PS/2 mouse device common for all mice [0.258333] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [0.258461] rtc_cmos: probe of rtc_cmos failed with error -38 [0.258535] drop_monitor: Initializing network drop monitor service [0.258598] TCP: cubic registered [0.258679] NET: Registered protocol family 10 [0.258835] mip6: Mobile IPv6 [0.258840] NET: Registered protocol family 17 [0.258852] Key type dns_resolver registered [0.259007] PM: Hibernation image not present or could not be loaded. [0.259013] registered taskstats version 1 [0.259030] XENBUS: Device with no driver: device/vbd/51712 [0.259033] XENBUS: Device with no driver: device/vif/0 [0.259120]
Bug#602273: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Hi,
I seem to have hit the same bug again with 2.6.32-38 domU (amd64). After
I rebooted dom0 to 2.6.32-41 I see that the jiffies value of the domU
does not increase but cpu_time in xm list -l output does. Value of
last_value seems to increase (now around 1804512135271).
I looked at linux-source-2.6.32 2.6.32-38 and I see that it contains a
call to pvclock_resume in xen_timer_resume so the patch should still be
there. Is this a new bug that just has the same symptoms?
KERNEL: /usr/lib/debug/boot/vmlinux-2.6.32-5-amd64
DUMPFILE: /local/xen/lindi1/core
CPUS: 6
DATE: Mon Mar 5 10:02:26 2012
UPTIME: 54 days, 21:35:49
LOAD AVERAGE: 0.04, 0.01, 0.00
TASKS: 307
NODENAME: lindi1
RELEASE: 2.6.32-5-amd64
VERSION: #1 SMP Mon Oct 3 03:59:20 UTC 2011
MACHINE: x86_64 (3210 Mhz)
MEMORY: 2 GB
PANIC:
PID: 0
COMMAND: swapper
TASK: 814611f0 (1 of 6) [THREAD_INFO: 8142c000]
CPU: 0
STATE: TASK_RUNNING (ACTIVE)
WARNING: panic task not found
crash disassemble xen_timer_resume
Dump of assembler code for function xen_timer_resume:
0x8100de32 xen_timer_resume+0:push %rbx
0x8100de33 xen_timer_resume+1:callq 0x8102cd7e
pvclock_resume
^^
...
crash disassemble pvclock_resume
Dump of assembler code for function pvclock_resume:
0x8102cd7e pvclock_resume+0: movq $0x0,0x5a42cf(%rip)#
0x815d1058
0x8102cd89 pvclock_resume+11: retq
crash x/x 0x815d1058
0x815d1058: 0x01a4254e0867
crash p/x last_value
$17 = {
counter = 0x1a4254e0867
}
crash ps | grep -v IN
PIDPPID CPU TASKST %MEM VSZRSS COMM
0 0 0 814611f0 RU 0.0 0 0 [swapper]
0 0 1 88007ff50e20 RU 0.0 0 0 [swapper]
0 0 2 88007ff51530 RU 0.0 0 0 [swapper]
0 0 3 88007ff51c40 RU 0.0 0 0 [swapper]
0 0 4 88007ff52350 RU 0.0 0 0 [swapper]
0 0 5 88007ff52a60 RU 0.0 0 0 [swapper]
21 2 0 88007ffab170 UN 0.0 0 0 [events/0]
26 2 5 88007ffad4c0 UN 0.0 0 0 [events/5]
32 2 5 88007f418000 UN 0.0 0 0 [xenwatch]
crash bt 0 21 26 32
PID: 0 TASK: 814611f0 CPU: 0 COMMAND: swapper
#0 [8142df70] xen_safe_halt at 8100dcbf
#1 [8142df78] xen_idle at 8100be63
#2 [8142df90] cpu_idle at 8100fe97
PID: 0 TASK: 88007ff50e20 CPU: 1 COMMAND: swapper
#0 [88007ff5de50] schedule at 812fb2a7
#1 [88007ff5de68] xen_force_evtchn_callback at 8100dc41
#2 [88007ff5de70] check_events at 8100e252
#3 [88007ff5dec8] tick_nohz_stop_sched_tick at 81070d4e
#4 [88007ff5df28] cpu_idle at 8100fe97
PID: 0 TASK: 88007ff51530 CPU: 2 COMMAND: swapper
#0 [88007ff5fe50] schedule at 812fb2a7
#1 [88007ff5fe68] xen_force_evtchn_callback at 8100dc41
#2 [88007ff5fe70] check_events at 8100e252
#3 [88007ff5fec8] tick_nohz_stop_sched_tick at 81070d4e
#4 [88007ff5ff28] cpu_idle at 8100fe97
PID: 0 TASK: 88007ff51c40 CPU: 3 COMMAND: swapper
#0 [88007ff69e50] schedule at 812fb2a7
#1 [88007ff69e68] xen_force_evtchn_callback at 8100dc41
#2 [88007ff69e70] check_events at 8100e252
#3 [88007ff69ec8] tick_nohz_stop_sched_tick at 81070d4e
#4 [88007ff69f28] cpu_idle at 8100fe97
PID: 0 TASK: 88007ff52350 CPU: 4 COMMAND: swapper
#0 [88007ff6be50] schedule at 812fb2a7
#1 [88007ff6be68] xen_force_evtchn_callback at 8100dc41
#2 [88007ff6be70] check_events at 8100e252
#3 [88007ff6bec8] tick_nohz_stop_sched_tick at 81070d4e
#4 [88007ff6bf28] cpu_idle at 8100fe97
PID: 0 TASK: 88007ff52a60 CPU: 5 COMMAND: swapper
#0 [88007ff6de50] schedule at 812fb2a7
#1 [88007ff6de68] xen_force_evtchn_callback at 8100dc41
#2 [88007ff6de70] check_events at 8100e252
#3 [88007ff6dec8] tick_nohz_stop_sched_tick at 81070d4e
#4 [88007ff6df28] cpu_idle at 8100fe97
PID: 21 TASK: 88007ffab170 CPU: 0 COMMAND: events/0
#0 [88007ffc3b90] schedule at 812fb2a7
#1 [88007ffc3c68] schedule_timeout at 812fb6dd
#2 [88007ffc3ce8] wait_for_common at 812fb594
#3 [88007ffc3d78] synchronize_sched at 8106307b
#4 [88007ffc3db8] dev_deactivate at 81262d5f
#5 [88007ffc3de8] __linkwatch_run_queue at 8125a8ea
#6 [88007ffc3e28]
Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen (also affects ext3 as of linux-image-3.1.0-1-amd64 et al)
package linux-2.6 notfound 637234 3.0.0-3 found 637234 3.1.0-1~experimental.1 found 637234 3.1.1-1 found 637234 3.1.8-2 found 637234 3.2.4-1 thanks dom0 amd64 squeeze with Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 05:42:31 UTC 2011 config -- name = 'lindi2' vcpus = '4' memory = '1024' disk = [ 'file:/local/xen/lindi2/disk.img,xvda,w' ] vif = [ 'mac=00:01:01:99:80:02' ] on_crash = 'restart' domU amd64 wheezy with Linux version 3.1.0-1-amd64 (Debian 3.1.0-1~experimental.1) (wa...@debian.org) (gcc version 4.6.1 (Debian 4.6.1-16) ) #1 SMP Thu Nov 3 19:35:59 UTC 2011 (also occurs with 3.1.1-1, 3.1.8-2 and 3.2.4-1 but listing the first version where the bug occurs) Using ext3 for rootfs. dmesg has ... blkfront: barrier: empty write xvda op failed blkfront: xvda: barrier or flush: disabled end_request: I/O error, dev xvda, sector 16519664 end_request: I/O error, dev xvda, sector 16519664 ... Full dmesg attached. dmesg_a.3.1.0-1~experimental.1.txt.xz Description: Binary data workaround == Setting barrier=0 for / in fstab seems to help. Thanks Konrad for the tip, now I can continue working :-)
Bug#638316: base: Task blocked for more than 120 seconds
Hi, Roberto Dal Zilio roberto.dalzi...@ilvillage.it writes: [904313.840676] updatedb.mloc D 880001855c40 0 14983 14979 0x [904313.840684] 880001855c40 0282 000800017880 8800032f5810 [904313.840693] f9e0 88002cf2dfd8 [904313.840701] 00015780 00015780 88017880 88017b78 [904313.840708] Call Trace: [904313.840722] [8102cdcc] ? pvclock_clocksource_read +0x3a/0x8b [904313.840731] [810b420d] ? sync_page+0x0/0x46 [904313.840737] [810b420d] ? sync_page+0x0/0x46 [904313.840745] [812fb25a] ? io_schedule+0x73/0xb7 [904313.840750] [810b424e] ? sync_page+0x41/0x46 [904313.840757] [812fc51a] ? _spin_unlock_irqrestore+0xd/0xe [904313.840762] [812fb66a] ? __wait_on_bit_lock+0x3f/0x84 [904313.840767] [810b41da] ? __lock_page+0x5d/0x63 [904313.840773] [81064f48] ? wake_bit_function+0x0/0x23 [904313.840780] [810ca7e0] ? lock_page+0x9/0x1f [904313.840786] [810ccd1e] ? handle_mm_fault+0x563/0x80f [904313.840794] [8100e242] ? check_events+0x12/0x20 [904313.840799] [8100e22f] ? xen_restore_fl_direct_end +0x0/0x1 [904313.840806] [812fe9f6] ? do_page_fault+0x2e0/0x2fc [904313.840811] [812fc895] ? page_fault+0x25/0x30 Something is waiting for something here but unfortunately we can't trust the call trace much since it just contains pointers from stack. I can't perform the above commands because I don't have Xen.org but Citrix XenServer 5.6. That's a same. Doesn't XenServer support any kind of crash dumps? About a year ago I was struggling with a similar tasks get stuck bug and was only able to understand it after I got several crash dumps and could compare them against the working situation. -Timo -- 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/841uwdo3a1@sauna.l.org
Bug#638316: base: Task blocked for more than 120 seconds
Roberto Dal Zilio roberto.dalzi...@ilvillage.it writes: On the xenserver I do not have a crashdump because the VM does not crash Can you delibaretly crash it to obtain such a dump? The stuck processes would still be visible in the dump. (I only get the task hang and the error in dmesg on the VM). Is it helpfull for you if we coredump on the VM itself (I mean enabling the core dump within the VM)? I'm not sure what you mean. A core dump of a userland process won't help here. -- 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/84obzhmhsu@sauna.l.org
Re: Processed: reassign 633535 to systemtap
Hi Frank and Ritesh, The last module unloaded was generated by SystemTap. There is much more information needed from the submitter, regardless. I didn't get your email. Please remember to Cc: 633535-submit...@bugs.debian.org or the emails won't reach the submitter of the bug. - What was that ptrace-related workload being run? (On debian, ptrace has no relations to systemtap.) - What are those itrace / itrace2 dmesg's? It's a toy project of mine that uses ptrace to get a trace of all executed instructions of a process and to correlate this against symbols of loaded libraries. It's not exactly ready yet but it does support i386, amd64, armel and kfreebsd-i386. I was looking at adding thread support last time iirc but it is not done yet. - How long before the kernel error was the last systemtap script completed? - Can the problem be reproduced? Reliably or intermittently? On a freshly booted machine? It's definitely too late now sorry. Let's close the bug now. I'll reopen it if I ever hit the bug again. -Timo -- 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/84r54t1r5q@sauna.l.org
Bug#633535: linux-image-2.6.32-5-amd64: oops in xdr_decode_hyper+0x0/0xe [nfs]
Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal I was playing around with ptrace when I got the following kernel oops. I do not know if this is related to use of ptrace or not. [1131224.792749] alignment check: [#1] SMP [1131224.792761] last sysfs file: /sys/devices/vbd-51712/block/xvda/uevent [1131224.792765] CPU 0 [1131224.792769] Modules linked in: nls_utf8 isofs nls_base iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables binfmt_misc nfs lockd fscache nfs_acl auth_rpcgss sunrpc bridge stp fuse loop evdev pcspkr ext3 jbd mbcache dm_mod xen_netfront xen_blkfront [last unloaded: stap_f729c9d9a15a149b32b8fe942ac255bf_2366] [1131224.792816] Pid: 4233, comm: test2 Not tainted 2.6.32-5-amd64 #1 [1131224.792821] RIP: e030:[a00fe2fc] [a00fe2fc] xdr_decode_hyper+0x0/0xe [nfs] [1131224.792837] RSP: e02b:8800ebe019f0 EFLAGS: 00250282 [1131224.792841] RAX: 01f4 RBX: 8800ebe01b68 RCX: 88005c10e964 [1131224.792846] RDX: 88005c10e97c RSI: 8800ebe01b80 RDI: 88005c10e97c [1131224.792850] RBP: 8800b6224dc0 R08: 8800ebcea600 R09: 812fc392 [1131224.792855] R10: R11: a00fe4b1 R12: [1131224.792860] R13: 8800ed28ae70 R14: a00fe4b1 R15: 8800ebcea600 [1131224.792867] FS: 7fa3ff82a700() GS:880003a05000() knlGS: [1131224.792873] CS: e033 DS: ES: CR0: 8005003b [1131224.792877] CR2: 7f67da03e000 CR3: b6252000 CR4: 0660 [1131224.792882] DR0: DR1: DR2: [1131224.792887] DR3: DR6: 4ff0 DR7: 0400 [1131224.792892] Process test2 (pid: 4233, threadinfo 8800ebe0, task 880057c88000) [1131224.792897] Stack: [1131224.792899] a00fe35c 8800ed28ae70 a00fe4cf 8800ebcea600 [1131224.792907] 0 a0077389 8800ebe01a10 a00769fe 8800ec1f82f0 [1131224.792916] 0 8800b6224dc0 8800b6224e50 [1131224.792926] Call Trace: [1131224.792936] [a00fe35c] ? xdr_decode_fattr+0x52/0xfd [nfs] [1131224.792946] [a00fe4cf] ? nfs3_xdr_attrstat+0x1e/0x23 [nfs] [1131224.792956] [a0077389] ? call_decode+0x5c3/0x647 [sunrpc] [1131224.792964] [a00769fe] ? call_transmit_status+0x3c/0x57 [sunrpc] [1131224.792974] [a007d2f5] ? __rpc_execute+0x73/0x243 [sunrpc] [1131224.792982] [a00774d4] ? rpc_run_task+0x53/0x5b [sunrpc] [1131224.792990] [a00775c3] ? rpc_call_sync+0x3d/0x5a [sunrpc] [1131224.793001] [a00fcf16] ? nfs3_rpc_wrapper+0x28/0x59 [nfs] [1131224.793013] [a00fd68f] ? nfs3_proc_getattr+0x55/0x79 [nfs] [1131224.793023] [a00f05f6] ? __nfs_revalidate_inode+0xb1/0x1b6 [nfs] [1131224.793034] [a00fae5b] ? nfs_sync_mapping_wait+0x16a/0x22a [nfs] [1131224.793044] [a00ef7a7] ? nfs_attribute_timeout+0xe/0x58 [nfs] [1131224.793054] [a00f0862] ? __put_nfs_open_context+0x81/0xb0 [nfs] [1131224.793064] [a00f090a] ? nfs_release+0x79/0x80 [nfs] [1131224.793071] [810efc2d] ? __fput+0x100/0x1af [1131224.793076] [810ed092] ? filp_close+0x5b/0x62 [1131224.793082] [8104fa14] ? put_files_struct+0x64/0xc1 [1131224.793089] [812fc2ca] ? _spin_lock_irq+0x7/0x22 [1131224.793094] [810512d9] ? do_exit+0x236/0x6c6 [1131224.793100] [8100e22f] ? xen_restore_fl_direct_end+0x0/0x1 [1131224.793106] [810e6f25] ? kmem_cache_free+0x72/0xa3 [1131224.793111] [810517df] ? do_group_exit+0x76/0x9d [1131224.793117] [8105e0cb] ? get_signal_to_deliver+0x310/0x339 [1131224.793123] [8101004f] ? do_notify_resume+0x87/0x73f [1131224.793128] [81019ced] ? send_sigtrap+0x66/0x6e [1131224.793134] [812fc94a] ? error_exit+0x2a/0x60 [1131224.793139] [81010e0e] ? int_signal+0x12/0x17 [1131224.793142] Code: e0 f6 05 c3 9e f9 ff 10 74 10 89 de 48 c7 c7 ca 6f 11 a0 31 c0 e8 c3 c2 1f e1 89 d8 5b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 90 90 90 48 8b 07 48 0f c8 48 89 06 48 8d 47 08 c3 53 b8 00 00 00 00 8b [1131224.793208] RIP [a00fe2fc] xdr_decode_hyper+0x0/0xe [nfs] [1131224.793219] RSP 8800ebe019f0 [1131224.793231] ---[ end trace bf8298aa72a71a8e ]--- [1131224.793234] Fixing recursive fault but reboot is needed! -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011 ** Command line: root=/dev/xvda ro console=hvc0 ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 16.449115] svc: failed to register lockdv1 RPC service (errno 97). [ 16.884030] br0: no IPv6 routers present [ 17.148027] eth0: no IPv6 routers present [ 394.499138] kjournald starting.
Bug#629627: linux-2.6: please support kdump (enable CONFIG_CRASH_DUMP=y?)
Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: wishlist kexec, kdump and crash are pretty powerful debugging tools. It would be nice if debian kernels supported kdump fully. If I read /usr/share/doc/kdump-tools/README.Debian correctly this would involve enabling CONFIG_CRASH_DUMP=y. I could not find discussion on why this is not done. Are there any serious drawbacks? If there are, I'm fine with having to build my own kernels but lets document the problems somewhere please :-) -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/84wrgwogt3@sauna.l.org
Bug#615831: [PATCH 1/2] panic(): print name of kernel module before loading it
Hi, maximilian attems m...@stro.at writes: cat: /sys/class/input/input*/device/description: No such file or directory yep that is the case for usb keyboard, so you can check no existence of that. aha, good idea. I'll send new patches against git HEAD. I built these with git-buildpackage and tested them again on the same HP ProLiant MicroServer. -Timo -- 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/8462oq82vg@sauna.l.org
Bug#615831: [PATCH 1/2] panic(): print the name of kernel each module before loading it
Loading a kernel module can crash the system so it is useful that the
user sees which module might be causing trouble.
---
scripts/functions |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/functions b/scripts/functions
index 9b961d2..0a02f04 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -44,8 +44,8 @@ panic()
sleep ${panic}
reboot
fi
- modprobe i8042
- modprobe atkbd
+ modprobe -v i8042
+ modprobe -v atkbd
REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console
21
}
--
1.7.2.5
--
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/1306910912-12748-1-git-send-email-timo.lindf...@iki.fi
Bug#615831: [PATCH 2/2] Load modules for USB keyboard if no keyboard is present at panic
USB modules are not normally loaded at break=top time but since USB keyboards are very common we should take the effort to try to load extra kernel modules at break (=panic) time. This patch closes #615831 and has been adapted from comments mentioned in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 and tested on a HP ProLiant MicroServer that lacks a PS2 port completely. --- scripts/functions |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/scripts/functions b/scripts/functions index 0a02f04..653581d 100644 --- a/scripts/functions +++ b/scripts/functions @@ -46,6 +46,12 @@ panic() fi modprobe -v i8042 modprobe -v atkbd + if ! grep KBD port /sys/class/input/input*/device/description /dev/null 21; then + modprobe -v ehci-hcd + modprobe -v uhci-hcd + modprobe -v ohci-hcd + modprobe -v usbhid + fi REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console 21 } -- 1.7.2.5 -- 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/1306910912-12748-2-git-send-email-timo.lindf...@iki.fi
Bug#615831: [PATCH 2/2] Load modules for USB keyboard if no keyboard is present at panic
maximilian attems m...@stro.at writes: as I didn't want to continue my 1 hour search for an eventual PS/2 mouse, and eventual combinations of the two. I just applied your patch without the check to the branch timo/panic Thanks! -Timo -- 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/84pqmxq4ui@sauna.l.org
Bug#615831: [PATCH 1/2] panic(): print name of kernel module before loading it
maximilian attems m...@stro.at writes: now the only thing that is holding me up to merge your patch is that /proc/bus/input/devices usage, there should be some sysfs file, no? cat /sys/class/input/input*/device/description shows a KBD Unfortunately it does not show a keyboard here: root@metunconf:~# cat /sys/class/input/input*/device/description cat: /sys/class/input/input*/device/description: No such file or directory root@metunconf:~# find /sys/class/input /sys/class/input /sys/class/input/input0 /sys/class/input/mice /sys/class/input/mouse0 /sys/class/input/input1 /sys/class/input/input2 /sys/class/input/mouse1 /sys/class/input/input3 /sys/class/input/input4 /sys/class/input/mouse2 /sys/class/input/input5 /sys/class/input/mouse3 /sys/class/input/input6 /sys/class/input/input7 /sys/class/input/event0 /sys/class/input/event1 /sys/class/input/event2 /sys/class/input/event3 /sys/class/input/event4 /sys/class/input/event5 /sys/class/input/event6 /sys/class/input/event7 /sys/class/input/input8 /sys/class/input/event8 /sys/class/input/js0 root@metunconf:~# lsusb Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0624:0248 Avocent Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub root@metunconf:~# cat /proc/bus/input/devices I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name=Macintosh mouse button emulation P: Phys= S: Sysfs=/devices/virtual/input/input0 U: Uniq= H: Handlers=mouse0 event0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0003 Vendor=04d9 Product=1400 Version=0110 N: Name=HID 04d9:1400 P: Phys=usb-:00:12.0-5/input0 S: Sysfs=/devices/pci:00/:00:12.0/usb1/1-5/1-5:1.0/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=04d9 Product=1400 Version=0110 N: Name=HID 04d9:1400 P: Phys=usb-:00:12.0-5/input1 S: Sysfs=/devices/pci:00/:00:12.0/usb1/1-5/1-5:1.1/input/input2 U: Uniq= H: Handlers=kbd mouse1 event2 B: EV=17 B: KEY=1f 200 39fad941d001 1e 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=0624 Product=0248 Version=0100 N: Name=Avocent USB Composite Device-0 P: Phys=usb-:00:13.2-2/input0 S: Sysfs=/devices/pci:00/:00:13.2/usb4/4-2/4-2:1.0/input/input3 U: Uniq=20090730 H: Handlers=kbd event3 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=0624 Product=0248 Version=0100 N: Name=Avocent USB Composite Device-0 P: Phys=usb-:00:13.2-2/input1 S: Sysfs=/devices/pci:00/:00:13.2/usb4/4-2/4-2:1.1/input/input4 U: Uniq=20090730 H: Handlers=mouse2 event4 js0 B: EV=1f B: KEY=7 0 0 0 0 B: REL=100 B: ABS=3 B: MSC=10 I: Bus=0003 Vendor=0624 Product=0248 Version=0100 N: Name=Avocent USB Composite Device-0 P: Phys=usb-:00:13.2-2/input2 S: Sysfs=/devices/pci:00/:00:13.2/usb4/4-2/4-2:1.2/input/input5 U: Uniq=20090730 H: Handlers=mouse3 event5 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: EV=3 B: KEY=10 0 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input8 U: Uniq= H: Handlers=kbd event8 B: EV=40001 B: SND=6 root@metunconf:~# dmesg | head -n4 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011 [0.00] Command line: root=/dev/nfs initrd=squeeze64unconf/initrd.img nfsroot=10.8.8.8:/tftpboot/squeeze64unconf ip=dhcp BOOT_IMAGE=squeeze64unconf/vmlinuz As a test I did root@metunconf:~# rmmod usbhid root@metunconf:~# rmmod hid and verified that I can no longer type anything to the console. -- 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/84vcwrtk4w@sauna.l.org
Bug#627883: initramfs-tools: uses wrong NIC for DHCP, persistent-net invents eth1-eth0?
Package: initramfs-tools
Version: 0.98.8
Severity: normal
Description
===
On a network booting machine with
oper@watt:~$ zcat /boot/initrd.img-2.6.32-5-amd64 | cpio -i --to-stdout
lib/udev/rules.d/70-persistent-net.rules
# lindi: ethernet port #1 (BIOS boots using this)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:25:90:36:c0:d2, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth0
# PCI device 0x8086:0x10ec (ixgbe)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1b:21:a1:d7:83, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth2
# PCI device 0x8086:0x10ec (ixgbe)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1b:21:a1:d7:82, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth3
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:25:90:36:c0:d3, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth1
53853 blocks
and
$ grep DEVICE= /etc/initramfs-tools/initramfs.conf
DEVICE=eth0
I see that ipconfig gets stuck at bootup trying to send DHCP requests
over a NIC whose MAC is not 00:25:90:36:c0:d2.
Troubleshooting
===
I placed a call to /bin/sh just before configure_networking call in
oper@watt:~$ zcat /boot/initrd.img-2.6.32-5-amd64 | cpio -i --to-stdout
scripts/nfs | head -n15
# NFS filesystem mounting -*- shell-script -*-
# FIXME This needs error checking
retry_nr=0
# parse nfs bootargs and mount nfs
do_nfsmount()
{
configure_networking
# get nfs root from dhcp
if [ x${NFSROOT} = xauto ]; then
# check if server ip is part of dhcp root-path
From this shell I see that the right NIC (i.e. the one with MAC of
00:25:90:36:c0:d2) has the name eth1-eth0 and eth0 is a wrong NIC. I
can see in source code of udev that it sometimes generates such names
but I don't fully understand the logic behind that. I did
rmmod ixgbe
rmmod igb
modprobe igb
modprobe ixgbe
and suddenly 00:25:90:36:c0:d2 was correctly named eth0.
The machine has 36 SATA disks and it takes a while to detect
them. Maybe there's a race condition somewhere?
As a workaround I'm now calling my 00:25:90:36:c0:d2 NIC net0
instead of eth0.
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 9.1M May 23 16:01 /boot/initrd.img-2.6.32-5-amd64
-- /proc/cmdline
root=/dev/nfs initrd=watt/initrd.img nfsroot=10.8.8.8:/tftpboot/watt ip=dhcp
sysrq_always_enabled break=top BOOT_IMAGE=watt/vmlinuz
-- resume
RESUME=UUID=d2e19371-27b1-4826-9d93-dd0f4e1f0ea3
-- /proc/filesystems
-- lsmod
Module Size Used by
loop 11799 0
snd_pcm60503 0
snd_timer 15582 1 snd_pcm
snd46446 2 snd_pcm,snd_timer
soundcore 4598 1 snd
snd_page_alloc 6249 1 snd_pcm
psmouse49937 0
joydev 8459 0
pcspkr 1699 0
serio_raw 3752 0
i2c_i8017830 0
evdev 7352 4
ioatdma34876 32
i2c_core 15819 1 i2c_i801
button 4650 0
processor 29935 16
nfs 241114 1
lockd 57603 1 nfs
fscache29834 1 nfs
nfs_acl 2031 1 nfs
auth_rpcgss33476 1 nfs
sunrpc161541 9 nfs,lockd,nfs_acl,auth_rpcgss
sd_mod 29921 0
crc_t10dif 1276 1 sd_mod
usbhid 33292 0
hid63257 1 usbhid
uhci_hcd 18521 0
ehci_hcd 32081 0
ixgbe 106622 0
usbcore 122386 4 usbhid,uhci_hcd,ehci_hcd
mpt2sas87773 0
scsi_transport_sas 19865 1 mpt2sas
mdio3096 1 ixgbe
scsi_mod 122149 3 sd_mod,mpt2sas,scsi_transport_sas
nls_base6377 1 usbcore
igb77959 0
dca 3761 3 ioatdma,ixgbe,igb
thermal11674 0
thermal_sys11942 2 processor,thermal
-- /etc/initramfs-tools/modules
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=nfs
DEVICE=eth0
NFSROOT=auto
-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no
-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
/usr/share/initramfs-tools/hooks:
busybox
dmsetup
keymap
klibc
mdadm
thermal
udev
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages
Bug#627645: linux-image-2.6.32-5-kirkwood: 'Out of memory and no killable processes...' when trying to run ld.bfd under gdb
Package: linux-2.6
Version: 2.6.32-30
Severity: minor
While trying to debug chromium-browser build failures on my sheevaplug I
attached gdb to a running ld.bfd process. After some time I got a
kernel panic and had to use JTAG to read the dmesg from memory.
The dmesg is attached. I don't expect that you can do much about this
but I thought it might help to let people know about the problem (it is
in fact a local DoS since no root privileges were used). I was building
chromium-browser in an unstable chroot that was mounted via NFS from
another machine.
ommit interval 5 seconds
6[ 12.563032] EXT3-fs: recovery complete.
6[ 12.984956] EXT3-fs: mounted filesystem with ordered data mode.
6[ 13.566602] udev[154]: starting version 164
6[ 14.249662] Adding 714744k swap on /dev/mmcblk0p5. Priority:-1 extents:1
across:714744k SS
6[ 14.415425] EXT3 FS on mmcblk0p2, internal journal
6[ 14.597380] loop: module loaded
6[ 22.119125] eth0: link up, 1000 Mb/s, full duplex, flow control disabled
6[ 23.130689] IPv6: Loaded, but administratively disabled, reboot required
to enable
3[ 128.455065] ata2: exception Emask 0x10 SAct 0x0 SErr 0x401 action 0xe
frozen
3[ 128.462527] ata2: edma_err_cause=0010 pp_flags=, dev connect
3[ 128.469278] ata2: SError: { PHYRdyChg DevExch }
6[ 128.473849] ata2: hard resetting link
4[ 134.426520] ata2: link is slow to respond, please be patient (ready=0)
3[ 138.506523] ata2: SRST failed (errno=-16)
6[ 138.510553] ata2: hard resetting link
6[ 139.836530] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
6[ 139.856772] ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7
6[ 139.862823] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
6[ 139.886813] ata2.00: configured for UDMA/133
6[ 139.891122] ata2: EH complete
5[ 139.894364] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ
1AA0 PQ: 0 ANSI: 5
5[ 139.939151] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00
TB/931 GiB)
5[ 139.947565] sd 1:0:0:0: [sda] Write Protect is off
7[ 139.952387] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
5[ 139.952486] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
6[ 139.962876] sda: unknown partition table
5[ 139.978879] sd 1:0:0:0: [sda] Attached SCSI disk
6[72415.918527] RPC: Registered udp transport module.
6[72415.923258] RPC: Registered tcp transport module.
6[72415.928017] RPC: Registered tcp NFSv4.1 backchannel transport module.
5[72415.992176] Slow work thread pool: Starting up
5[72415.997173] Slow work thread pool: Ready
5[72416.002038] FS-Cache: Loaded
5[72416.114290] FS-Cache: Netfs 'nfs' registered for caching
3[421978.774045] ata2: exception Emask 0x10 SAct 0x0 SErr 0x10 action 0x6
frozen
3[421978.781508] ata2: edma_err_cause=0220 pp_flags=0003,
SError=0010
3[421978.788690] ata2: SError: { Dispar }
6[421978.792386] ata2: hard resetting link
6[421979.296531] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
6[421979.336800] ata2.00: configured for UDMA/133
6[421979.341189] ata2: EH complete
3[520311.272438] ata2: exception Emask 0x10 SAct 0x0 SErr 0x18 action 0x6
frozen
3[520311.279905] ata2: edma_err_cause=0020 pp_flags=,
SError=0018
3[520311.287093] ata2: SError: { 10B8B Dispar }
6[520311.291313] ata2: hard resetting link
6[520311.796532] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
6[520311.836800] ata2.00: configured for UDMA/133
6[520311.841189] ata2: EH complete
3[1130600.900737] ata2: exception Emask 0x10 SAct 0x0 SErr 0x18 action
0x6 frozen
3[1130600.908287] ata2: edma_err_cause=0020 pp_flags=,
SError=0018
3[1130600.915549] ata2: SError: { 10B8B Dispar }
6[1130600.919860] ata2: hard resetting link
6[1130601.266528] ata2: SATA link down (SStatus 0 SControl F300)
6[1130606.266530] ata2: hard resetting link
6[1130606.616525] ata2: SATA link down (SStatus 0 SControl F300)
4[1130606.60] ata2: limiting SATA link speed to 1.5 Gbps
6[1130611.616531] ata2: hard resetting link
6[1130611.966525] ata2: SATA link down (SStatus 0 SControl F310)
4[1130611.972227] ata2.00: disabled
6[1130611.975401] ata2: EH complete
6[1130611.978591] ata2.00: detaching (SCSI 1:0:0:0)
5[1130611.984756] sd 1:0:0:0: [sda] Synchronizing SCSI cache
6[1130611.990794] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
5[1130611.998631] sd 1:0:0:0: [sda] Stopping disk
4[1130612.003765] sd 1:0:0:0: [sda] START_STOP FAILED
6[1130612.008532] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
4[7457076.471788] init invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0
6[7457076.478823] init cpuset=/ mems_allowed=0
4[7457076.482958] [c002df70] (unwind_backtrace+0x0/0xdc) from [c00a2154]
(oom_kill_process+0x5c/0x1d8)
4[7457076.492336] [c00a2154] (oom_kill_process+0x5c/0x1d8) from
[c00a2704] (__out_of_memory+0x148/0x16c)
4[7457076.501887] [c00a2704] (__out_of_memory+0x148/0x16c)
Bug#621072: linux-image-2.6.32-5-amd64: 2.6.32-33 failes to boot as PV domU on Xen
Hi, I can also reproduce the issue with 2.6.32-33: overlord3:~$ sudo xm dmesg (XEN) Xen version 4.0.1 (Debian 4.0.1-2) (wa...@debian.org) (gcc version 4.4.5 (Debian 4.4.5-10) ) Wed Jan 12 14:04:06 UTC 2011 (XEN) Bootloader: GRUB 1.98+20100804-14 (XEN) Command line: placeholder (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) Disc information: (XEN) Found 4 MBR signatures (XEN) Found 4 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ac00 (usable) (XEN) 0009ac00 - 000a (reserved) (XEN) 000e4000 - 0010 (reserved) (XEN) 0010 - dfe9 (usable) (XEN) dfe9 - dfea8000 (ACPI data) (XEN) dfea8000 - dfed (ACPI NVS) (XEN) dfed - dff0 (reserved) (XEN) ffe0 - 0001 (reserved) (XEN) 0001 - 00042000 (usable) (XEN) ACPI: RSDP 000FBED0, 0024 (r2 ACPIAM) (XEN) ACPI: XSDT DFE90100, 005C (r1 082410 XSDT1804 20100824 MSFT 97) (XEN) ACPI: FACP DFE90290, 00F4 (r3 082410 FACP1804 20100824 MSFT 97) (XEN) ACPI: DSDT DFE90460, F42B (r1 A1595 A15950000 INTL 20060113) (XEN) ACPI: FACS DFEA8000, 0040 (XEN) ACPI: APIC DFE90390, 0088 (r1 082410 APIC1804 20100824 MSFT 97) (XEN) ACPI: MCFG DFE90420, 003C (r1 082410 OEMMCFG 20100824 MSFT 97) (XEN) ACPI: OEMB DFEA8040, 0072 (r1 082410 OEMB1804 20100824 MSFT 97) (XEN) ACPI: SRAT DFE9F8B0, 0108 (r1 AMDFAM_F_102 AMD 1) (XEN) ACPI: HPET DFE9F9C0, 0038 (r1 082410 OEMHPET 20100824 MSFT 97) (XEN) ACPI: SSDT DFE9FA00, 0156 (r1 A M I POWERNOW1 AMD 1) (XEN) System RAM: 16382MB (16775336kB) (XEN) Domain heap initialised (XEN) Processor #0 0:10 APIC version 16 (XEN) Processor #1 0:10 APIC version 16 (XEN) Processor #2 0:10 APIC version 16 (XEN) Processor #3 0:10 APIC version 16 (XEN) Processor #4 0:10 APIC version 16 (XEN) Processor #5 0:10 APIC version 16 (XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec0, GSI 0-23 (XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec2, GSI 24-55 (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3210.862 MHz processor. (XEN) Initing memory sharing. (XEN) HVM: ASIDs enabled. (XEN) HVM: SVM enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Total of 6 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) - Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 6 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 - 0x16b8000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00040800-00041000 (4081161 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100-816b8000 (XEN) Init. ramdisk: 816b8000-83104a00 (XEN) Phys-Mach map: 83105000-85068048 (XEN) Start info:85069000-850694b4 (XEN) Page tables: 8506a000-85097000 (XEN) Boot stack:85097000-85098000 (XEN) TOTAL: 8000-8540 (XEN) ENTRY ADDRESS: 81508200 (XEN) Dom0 has maximum 6 VCPUs (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input - DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 176kB init memory. (XEN) traps.c:2308:d0 Domain attempted WRMSR c0010004 from 6412:d4175407 to :. (XEN) traps.c:2308:d0 Domain attempted WRMSR c001 from 0107:6e90187f to :00430076. (XEN) save.c:72:d0 Domain 2 expects freq 3210MHz but host's freq is 3210MHz: trap and emulate rdtsc (XEN) d64:v0: unhandled page fault (ec=) (XEN) Pagetable walk from 8305a000: (XEN) L4[0x1ff] = 00038e68a067 1003 (XEN) L3[0x1fe] = 00038ef4e067 1007 (XEN) L2[0x018] = (XEN) domain_crash_sync called from entry.S (XEN) Domain 64 (vcpu#0) crashed on cpu#4: (XEN) [ Xen-4.0.1 x86_64 debug=n Not tainted ] (XEN) CPU:4 (XEN) RIP:e033:[8100c2af] (XEN) RFLAGS: 0216 EM: 1 CONTEXT: pv guest (XEN) rax: 8305a000 rbx: 8063 rcx: 8163 (XEN) rdx: 2000 rsi: rdi: (XEN) rbp: rsp: 8142db90 r8: 01ff (XEN) r9: 0003 r10:
Re: [PATCH 1/2] panic(): print name of kernel module before loading it
maximilian attems m...@stro.at writes: +try_modprobe() I'd prefer the function to be named modprobe_verbose() Ok. +try_modprobe atkbd why not using -v from modprobe, the only argument against that would count is busybox support. please check? I'm not very familiar with busybox internals but at least on squeeze I don't even have the modprobe applet: $ sudo busybox modprobe modprobe: applet not found $ dpkg-query -W busybox busybox 1:1.17.1-8 and /sbin/modprobe on my initrd generated with BUSYBOX=y is from the module-init-tools package. -- 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/84ei59gom3@sauna.l.org
Bug#619245: linux-image-2.6.32-5-686-bigmem: shmem_fault when using chromium on tmpfs
Package: linux-2.6 Version: 2.6.32-30 Severity: normal I keep hitting this oops maybe once a week when browsing with chromium-browser. I have symlinked ~/.config/chromium and ~/.cache/chromium to /dev/shm/lindi since the internal SSD of my aspire one laptop is so slow. I do not know if this has anything to do with the oops but I thought I'd mention it. 509.077570] BUG: unable to handle kernel paging request at d1a0 509.077595] IP: [c109804e] shmem_getpage+0x540/0x5a9 509.077623] *pdpt = 01447001 *pde = 00180067 *pte = 00aa00aa 509.077645] Oops: 0002 [#1] SMP 509.077657] last sysfs file: /sys/devices/virtual/net/ppp0/uevent 509.077669] Modules linked in: ppp_async crc_ccitt ppp_generic slhc sg sr_mod cdrom option usb_wwan usbserial tun parport_pc ppdev acpi_cpufreq lp cpufreq_conservative cpufreq_stats cpufreq_powersave parport cpufreq_userspace fuse snd_pcm_oss snd_mixer_oss loop snd_hda_codec_realtek joydev arc4 ecb snd_hda_intel snd_hda_codec ath5k snd_hwdep i915 drm_kms_helper snd_pcm mac80211 uvcvideo snd_timer drm ath snd i2c_algo_bit acerhdf videodev i2c_i801 cfg80211 jmb38x_ms soundcore v4l1_compat video pcspkr psmouse evdev serio_raw wmi battery ac i2c_core rng_core rfkill snd_page_alloc button memstick output processor ext3 jbd mbcache usb_storage sd_mod crc_t10dif ata_generic ata_piix libata sdhci_pci sdhci r8169 mmc_core uhci_hcd ehci_hcd scsi_mod mii led_class usbcore thermal nls_base thermal_sys [last unloaded: scsi_wait_scan] 509.077933] 509.077947] Pid: 1792, comm: chromium-browse Not tainted (2.6.32-5-686-bigmem #1) AOA110 509.077961] EIP: 0060:[c109804e] EFLAGS: 00010246 CPU: 1 509.077974] EIP is at shmem_getpage+0x540/0x5a9 509.077984] EAX: EBX: d1a0 ECX: 0400 EDX: 509.077996] ESI: ddc5d008 EDI: d1a0 EBP: c1747000 ESP: dd4a3e58 509.078008] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 509.078023] Process chromium-browse (pid: 1792, ti=dd4a2000 task=dec4ddc0 task.ti=dd4a2000) 509.078032] Stack: 509.078039] 0001 c143eaf8 0165 dd4a3ef0 0109 ddc5d068 ddc5d118 509.078068] 0 000200da ddc5d068 dd4a3ee4 001de108 c1098108 0001 509.078097] 0 dd4a3e9c 0001 c1101b98 c10a0106 509.078127] Call Trace: 509.078144] [c1098108] ? shmem_fault+0x51/0x77 509.078162] [c1101b98] ? shm_fault+0xc/0xd 509.078178] [c10a0106] ? __do_fault+0x53/0x3fb 509.078194] [c10a238b] ? handle_mm_fault+0x4d1/0xa22 509.078214] [c1051528] ? getnstimeofday+0x4d/0xc9 509.078232] [c1280fa0] ? do_page_fault+0x2f1/0x307 509.078247] [c1280caf] ? do_page_fault+0x0/0x307 509.078262] [c127f4db] ? error_code+0x73/0x78 509.078271] Code: ff ff eb 4f 83 4e 04 01 ff 46 08 8b 44 24 18 fe 40 a0 ba 03 00 00 00 89 e8 e8 2d d7 f8 ff 31 d2 b9 00 04 00 00 89 c3 89 c7 89 d0 f3 ab b2 03 89 d8 e8 37 d5 f8 ff f0 80 4d 00 08 83 7c 24 3c 02 509.078423] EIP: [c109804e] shmem_getpage+0x540/0x5a9 SS:ESP 0068:dd4a3e58 509.078442] CR2: d1a0 509.078454] ---[ end trace 97772fea35a2c15e ]--- 509.078469] note: chromium-browse[1792] exited with preempt_count 1 509.104368] BUG: unable to handle kernel paging request at d1a01000 509.104392] IP: [c109804e] shmem_getpage+0x540/0x5a9 509.104419] *pdpt = 01447001 *pde = 00180067 *pte = 00aa00aa 509.104440] Oops: 0002 [#2] SMP 509.104452] last sysfs file: /sys/devices/virtual/net/ppp0/uevent 509.104464] Modules linked in: ppp_async crc_ccitt ppp_generic slhc sg sr_mod cdrom option usb_wwan usbserial tun parport_pc ppdev acpi_cpufreq lp cpufreq_conservative cpufreq_stats cpufreq_powersave parport cpufreq_userspace fuse snd_pcm_oss snd_mixer_oss loop snd_hda_codec_realtek joydev arc4 ecb snd_hda_intel snd_hda_codec ath5k snd_hwdep i915 drm_kms_helper snd_pcm mac80211 uvcvideo snd_timer drm ath snd i2c_algo_bit acerhdf videodev i2c_i801 cfg80211 jmb38x_ms soundcore v4l1_compat video pcspkr psmouse evdev serio_raw wmi battery ac i2c_core rng_core rfkill snd_page_alloc button memstick output processor ext3 jbd mbcache usb_storage sd_mod crc_t10dif ata_generic ata_piix libata sdhci_pci sdhci r8169 mmc_core uhci_hcd ehci_hcd scsi_mod mii led_class usbcore thermal nls_base thermal_sys [last unloaded: scsi_wait_scan] 509.104727] 509.104742] Pid: 1576, comm: chromium-browse Tainted: G D (2.6.32-5-686-bigmem #1) AOA110 509.104756] EIP: 0060:[c109804e] EFLAGS: 00010246 CPU: 1 509.104769] EIP is at shmem_getpage+0x540/0x5a9 509.104780] EAX: EBX: d1a01000 ECX: 0400 EDX: 509.104792] ESI: ddc5d560 EDI: d1a01000 EBP: c1747020 ESP: dd53dbf4 509.104804] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 509.104818] Process chromium-browse (pid: 1576, ti=dd53c000 task=dd530880 task.ti=dd53c000) 509.104828] Stack: 509.104836] d736c8ac c1920e58 c143eaf8 01920e20 dd53dc88 ddc5d5c0 ddc5d670 509.104863] 0 000200da ddc5d5c0 dd53dc7c 8000 c1098108 0001 509.104892] 0
Bug#616581: initramfs-tools: USB keyboard not available with init=/bin/sh
Michal Suchanek hramr...@centrum.cz writes: Can't use an USB keyboard when I boot with init=/bin/sh. This is related to bug #615831. -- 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/84zkp91he5@sauna.l.org
[PATCH 1/2] panic(): print name of kernel module before loading it
Loading a kernel can crash the system so it is useful that the user
sees which module might be causing trouble.
Signed-off-by: Timo Juhani Lindfors timo.lindf...@iki.fi
diff --git a/scripts/functions b/scripts/functions
index 579696a..af49e45 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -31,6 +31,12 @@ log_end_msg()
_log_msg done.\n
}
+try_modprobe()
+{
+ echo Attempting to load kernel module $1
+ modprobe $1
+}
+
panic()
{
if command -v chvt /dev/null 21; then
@@ -44,8 +50,8 @@ panic()
sleep ${panic}
reboot
fi
- modprobe i8042
- modprobe atkbd
+ try_modprobe i8042
+ try_modprobe atkbd
REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console
21
}
--
1.7.2.3
--
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/1299068122-27954-1-git-send-email-timo.lindf...@iki.fi
[PATCH 2/2] Load modules for USB keyboard if no keyboard is present at panic
USB modules are not normally loaded at break=top time but since USB
keyboards are very common we should take the effort to try to load
extra kernel modules at break (=panic) time. This patch closes #615831
and has been adapted from comments mentioned in
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
and tested on a HP ProLiant MicroServer that lacks a PS2 port
completely.
Signed-off-by: Timo Juhani Lindfors timo.lindf...@iki.fi
diff --git a/scripts/functions b/scripts/functions
index af49e45..3c95b55 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -37,6 +37,20 @@ try_modprobe()
modprobe $1
}
+kbd_handler_exists()
+{
+ local line
+
+ while read line; do
+ case $line in
+ H:*kbd*)
+ return 0
+ ;;
+ esac
+ done /proc/bus/input/devices
+ return 1
+}
+
panic()
{
if command -v chvt /dev/null 21; then
@@ -52,6 +66,13 @@ panic()
fi
try_modprobe i8042
try_modprobe atkbd
+ if ! kbd_handler_exists; then
+ try_modprobe ehci-hcd
+ try_modprobe uhci-hcd
+ try_modprobe ohci-hcd
+ try_modprobe usbhid
+ fi
+
REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console
21
}
--
1.7.2.3
--
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/1299068122-27954-2-git-send-email-timo.lindf...@iki.fi
Bug#615831: [PATCH] Load modules for USB keyboard if not keyboard is present at panic
m...@linux.it (Marco d'Itri) writes: My only request is that the loading in panic() of *every* module is preceded by printing on the console an appropriate debug message containing the module name, because loading the module could cause an oops. Ok. I reworked this a bit and resent with git send-email --to=initramfs-to...@packages.debian.org --cc 615...@bugs.debian.org 0001-panic-print-name-of-kernel-module-before-loading-it.patch 0002-Load-modules-for-USB-keyboard-if-no-keyboard-is-pres.patch -- 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/84y64x4szf@sauna.l.org
[PATCH 2/2] Inform the user about reboot on panic=
Currently if a system administrator uses panic=60 break=top boot
options initramfs prints
Spawning shell within the initramfs
but does not actually spawn the shell since panic= disallows
that. This patch explicitely informs the user about the reboot and
hints that by reminving panic= he/she can get break= debugging to
work.
Signed-off-by: Timo Juhani Lindfors timo.lindf...@iki.fi
diff --git a/scripts/functions b/scripts/functions
index 025001f..579696a 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -40,6 +40,7 @@ panic()
echo $@
# Disallow console access
if [ -n ${panic} ]; then
+ echo Rebooting automatically due to panic= option
sleep ${panic}
reboot
fi
--
1.7.2.3
--
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/1298887825-6838-2-git-send-email-timo.lindf...@iki.fi
[PATCH 1/2] Make panic message visible even if panic= is used
The purpose of panic= is to make the system reboot automatically on
panic but also give the interactive user some time to see what went
wrong.
Signed-off-by: Timo Juhani Lindfors timo.lindf...@iki.fi
diff --git a/scripts/functions b/scripts/functions
index 2280ba2..025001f 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -37,6 +37,7 @@ panic()
chvt 1
fi
+ echo $@
# Disallow console access
if [ -n ${panic} ]; then
sleep ${panic}
@@ -44,7 +45,6 @@ panic()
fi
modprobe i8042
modprobe atkbd
- echo $@
REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console
21
}
--
1.7.2.3
--
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/1298887825-6838-1-git-send-email-timo.lindf...@iki.fi
Bug#615831: initramfs-tools: USB keyboards are not available at break=top shell
Package: initramfs-tools Version: 0.98.8 Severity: normal Steps to reproduce: 1) connect usb keyboard 2) boot with break=top Expected results: 2) (initramfs) prompt that responds to user input Actual results: 2) (initramfs) prompt that does not respond to user input More info: 1) This happens of course since USB modules are not loaded at break=top time. 2) A related ubuntu bug is https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-4 GNU cpio -- a program to manage ar ii findutils 4.4.2-1+b1 utilities for finding files--find, ii klibc-utils 1.5.20-1 small utilities built with klibc f ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii udev 164-3 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.17.1-8 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: ii bash-completion 1:1.2-3programmable completion for the ba -- no debconf information -- 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/84d3mco27n@sauna.l.org
[PATCH] Load modules for USB keyboard if not keyboard is present at panic
USB modules are not normally loaded at break=top time but since USB keyboards are very common we should take the effort to try to load extra kernel modules at break (=panic) time. This patch closes #615831 and has been adapted from comments mentioned in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 and tested on on HP ProLiant MicroServer that lacks a PS2 port completely. --- scripts/functions |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/scripts/functions b/scripts/functions index 579696a..778196f 100644 --- a/scripts/functions +++ b/scripts/functions @@ -46,6 +46,13 @@ panic() fi modprobe i8042 modprobe atkbd + if ! grep -q '^H:.*kbd' /proc/bus/input/devices ; then + # no keyboard? Try USB. + modprobe ehci-hcd + modprobe uhci-hcd + modprobe ohci-hcd + modprobe usbhid + fi REASON=$@ PS1='(initramfs) ' /bin/sh -i /dev/console /dev/console 21 } -- 1.7.2.3 -- 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/1298891884-7505-1-git-send-email-timo.lindf...@iki.fi
Bug#614267: firmware-linux-free: please consider documenting that firmware/cis/* is data and not software
Package: firmware-linux-free Version: 2.6.32-30 Severity: wishlist Just out of curiosity went through all the files /lib/firmware/cis/NE2K.cis /lib/firmware/cis/3CCFEM556.cis /lib/firmware/cis/COMpad2.cis /lib/firmware/cis/PE-200.cis /lib/firmware/cis/MT5634ZLX.cis /lib/firmware/cis/RS-COM-2P.cis /lib/firmware/cis/SW_555_SER.cis /lib/firmware/cis/SW_8xx_SER.cis /lib/firmware/cis/tamarack.cis /lib/firmware/cis/DP83903.cis /lib/firmware/cis/LA-PCM.cis /lib/firmware/cis/SW_7xx_SER.cis /lib/firmware/cis/3CXEM556.cis /lib/firmware/cis/PCMLM28.cis /lib/firmware/cis/COMpad4.cis /lib/firmware/dsp56k /lib/firmware/dsp56k/bootstrap.bin /lib/firmware/av7110 /lib/firmware/av7110/bootcode.bin /lib/firmware/keyspan_pda /lib/firmware/keyspan_pda/keyspan_pda.fw /lib/firmware/keyspan_pda/xircom_pgs.fw and checked that debian includes corresponding source code. I could not find source code for cis/* and became worried. After a while I learned that that CIS stands for Card Information Structure and is apparently data, not at all software? Just to clear things up, would it be possible to mention this explanation for the lack of source code somewhere? I had to 1) apt-get source pcmciautils 2) cd pcmciautils-015/debug 3) make to get dump_cis and then use 4) for i in firmware/cis/*; do echo Parsing $i; objcopy -I ihex -O binary $i a; /home/lindi/debian/debian-pcmciautils/pcmciautils-015/dump_cis -f a; done to get a human readable view to the CIS data: Parsing firmware/cis/3CCFEM556.cis.ihex Socket 9 offset 0x02, tuple 0x01, link 0x03 00 00 ff dev_info NULL 0ns, 512b offset 0x07, tuple 0x15, link 0x2d 05 00 33 43 6f 6d 00 4d 65 67 61 68 65 72 74 7a 20 33 43 43 46 45 4d 35 35 36 00 4c 41 4e 20 2b 20 35 36 6b 20 4d 6f 64 65 6d 00 00 ff vers_1 5.0, 3Com, Megahertz 3CCFEM556, LAN + 56k Modem, offset 0x36, tuple 0x20, link 0x04 01 01 56 05 manfid 0x0101, 0x0556 offset 0x3c, tuple 0x21, link 0x02 00 00 funcid multi_function offset 0x40, tuple 0x06, link 0x0b 02 00 4d 00 00 00 00 6b 00 00 00 mfc_long_link function 0: attr 0x004d function 1: attr 0x006b offset 0x4f, tuple 0x13, link 0x03 43 49 53 link_target offset 0x54, tuple 0x21, link 0x02 06 00 funcid network_adapter offset 0x58, tuple 0x1a, link 0x06 05 07 00 10 67 02 config base 0x1000 mask 0x0267 last_index 0x07 offset 0x60, tuple 0x1b, link 0x09 87 01 19 01 55 64 30 ff ff cftable_entry 0x07 Vcc Vnom 5V io 0x-0x000f [lines=4] [8bit] [16bit] irq mask 0x [level] offset 0x6d, tuple 0x13, link 0x03 43 49 53 link_target offset 0x72, tuple 0x21, link 0x02 02 00 funcid serial_port offset 0x76, tuple 0x1a, link 0x06 05 27 00 11 77 02 config base 0x1100 mask 0x0277 last_index 0x27 offset 0x7e, tuple 0x1b, link 0x09 a7 01 19 01 55 23 30 ff ff cftable_entry 0x27 Vcc Vnom 5V io 0x-0x0007 [lines=3] [8bit] irq mask 0x [level] Parsing firmware/cis/3CXEM556.cis.ihex Socket 9 offset 0x02, tuple 0x01, link 0x03 00 00 ff dev_info NULL 0ns, 512b offset 0x07, tuple 0x15, link 0x2c 05 00 33 43 6f 6d 00 4d 65 67 61 68 65 72 74 7a 20 33 43 58 45 4d 35 35 36 00 4c 41 4e 20 2b 20 35 36 6b 20 4d 6f 64 65 6d 00 00 ff vers_1 5.0, 3Com, Megahertz 3CXEM556, LAN + 56k Modem, offset 0x35, tuple 0x20, link 0x04 01 01 35 00 manfid 0x0101, 0x0035 offset 0x3b, tuple 0x21, link 0x02 00 00 funcid multi_function offset 0x3f, tuple 0x06, link 0x0b 02 00 4c 00 00 00 00 69 00 00 00 mfc_long_link function 0: attr 0x004c function 1: attr 0x0069 offset 0x4e, tuple 0x13, link 0x03 43 49 53 link_target offset 0x53, tuple 0x21, link 0x02 06 00 funcid network_adapter offset 0x57, tuple 0x1a, link 0x05 01 07 00 08 63 config base 0x0800 mask 0x0063 last_index 0x07 offset 0x5e, tuple 0x1b, link 0x09 87 01 19 01 55 64 30 ff ff cftable_entry 0x07 Vcc Vnom 5V io 0x-0x000f [lines=4] [8bit] [16bit] irq mask 0x [level] offset 0x6b, tuple 0x13, link 0x03 43 49 53 link_target offset 0x70, tuple 0x21, link 0x02 02 00 funcid serial_port offset 0x74, tuple 0x1a, link 0x05 01 27 00 09 63 config base 0x0900 mask 0x0063 last_index 0x27 offset 0x7b, tuple 0x1b, link 0x09 a7 01 19 01 55 23 30 ff ff cftable_entry 0x27 Vcc Vnom 5V io 0x-0x0007 [lines=3] [8bit] irq mask 0x [level] Parsing firmware/cis/COMpad2.cis.ihex Socket 9 offset 0x02, tuple 0x01, link 0x03 00 00 ff dev_info NULL 0ns, 512b offset 0x07, tuple 0x15, link 0x1f 04 01 41 44 56 41 4e 54 45 43 48 00 43 4f 4d 70 61 64 2d 33 32 2f 38 35 00 31 2e 30 00 00 ff vers_1 4.1, ADVANTECH, COMpad-32/85, 1.0, offset 0x28, tuple 0x21, link 0x02 02 01 funcid serial_port [post] offset 0x2c, tuple 0x1a, link 0x05 01 05 00 01 03 config base 0x0100 mask 0x0003 last_index 0x05 offset 0x33, tuple 0x1b, link 0x0e c1 81 18 aa 61 e8 02 07 e8 03 07 30 b8 9e cftable_entry 0x01 [default] [mwait] io 0x02e8-0x02ef, 0x03e8-0x03ef [lines=10] [8bit] [range] irq mask 0x9eb8
Bug#614267: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#614267: firmware-linux-free: please consider documenting that firmware/cis/* is data and not software)
ow...@bugs.debian.org (Debian Bug Tracking System) writes: The source is added by debian/patches/bugfix/all/firmware-pcmcia-cs-CIS-source-and-copyright.patch whoa! Thanks. I don't understand why I missed that. -Timo -- 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/84bp26v620@sauna.l.org
Bug#611832: linux-image-2.6.32-5-amd64: general protection fault at reboot under qemu: native_stop_other_cpus+0x86/0x90
Ben Hutchings b...@decadent.org.uk writes:
It's a kernel feature to be more efficient when running in a recognised
virtual machine implementation (PV = paravirtualisation).
thanks. I think it is the following code from vmi_32.c:
/*
* Apply patch if appropriate, return length of new instruction
* sequence. The callee does nop padding for us.
*/
static unsigned vmi_patch(u8 type, u16 clobbers, void *insns,
unsigned long ip, unsigned len)
{
switch (type) {
case PARAVIRT_PATCH(pv_irq_ops.irq_disable):
return patch_internal(VMI_CALL_DisableInterrupts, len,
insns, ip);
case PARAVIRT_PATCH(pv_irq_ops.irq_enable):
return patch_internal(VMI_CALL_EnableInterrupts, len,
insns, ip);
case PARAVIRT_PATCH(pv_irq_ops.restore_fl):
return patch_internal(VMI_CALL_SetInterruptMask, len,
insns, ip);
case PARAVIRT_PATCH(pv_irq_ops.save_fl):
return patch_internal(VMI_CALL_GetInterruptMask, len,
insns, ip);
case PARAVIRT_PATCH(pv_cpu_ops.iret):
return patch_internal(VMI_CALL_IRET, len, insns, ip);
case PARAVIRT_PATCH(pv_cpu_ops.irq_enable_sysexit):
return patch_internal(VMI_CALL_SYSEXIT, len, insns, ip);
default:
break;
}
return len;
}
I don't understand how the first xchg instruction in
0x00600889 f+41: 57 push %rdi
0x0060088a f+42: 9d popfq
0x0060088b f+43: 66 66 90 xchg %ax,%ax
0x0060088e f+46: 66 90 xchg %ax,%ax
can generate a general protection fault. I googled around and found
yes - it smells like it tries to deliver vector 0, after the panic
code has deinitialized the lapic / ioapic
which suggests a qemu bug from
http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-09/msg09652.html
Shall I reassign the bug or do you know how to investigate this more?
--
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/84oc6d5jga@sauna.l.org
Re: Debug infos for remaining packages
Bastian Blank wa...@debian.org writes: Maybe this could be used to enable the possibility to do limited debugging on all images without emiting too much preasure on the buildd/archive. Probably not a bad idea. However, such partially debuggable kernels should be marked clearly. It is not nice to spend weeks trying to reproduce a bug and then to notice that the debug information for that version to be minimal. How about using -partial-dbg instead of -dbg for those? ;-) -- 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/84pqqu949v@sauna.l.org
Re: Uploading linux-2.6 2.6.37-1 to unstable
Ben Hutchings b...@decadent.org.uk writes: Note that the OpenVZ, VServer and Xen flavours have been dropped and will not come back. Does this mean that it would be a good day to start testing the dom0 support of plain 2.6.37 to make sure regressions will be minimal? (I am assuming 2.6.37 does support dom0 now). -- 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/84aai6xx21@sauna.l.org
Re: Uploading linux-2.6 2.6.37-1 to unstable
Ben Hutchings b...@decadent.org.uk writes: The backend drivers have not yet been merged, so it's not yet very useful as dom0. ok. Is there still hope that they will get merged before wheezy is released or would now be a good time to start looking at KVM migration plans? -- 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/8462suxspr@sauna.l.org
Bug#611832: linux-image-2.6.32-5-amd64: general protection fault at reboot under qemu: native_stop_other_cpus+0x86/0x90
Package: linux-2.6 Version: 2.6.32-30 Severity: normal Sometimes when I use shutdown -r now under qemu I get a general protection fault: 6[ 103.542142] e1000 :00:03.0: PCI INT A disabled 0[ 103.543710] Restarting system. 4[ 103.543772] machine restart 0[ 103.544118] general protection fault: fff2 [#1] SMP 0[ 103.544118] last sysfs file: /sys/devices/pci:00/:00:01.1/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0/manage_start_stop 4[ 103.544118] CPU 0 4[ 103.544118] Modules linked in: parport_pc psmouse mtdchar parport i2c_piix4 processor button pcspkr evdev serio_raw i2c_core ext2 mbcache softdog jffs2 zlib_deflat e lzo_decompress lzo_compress mtdblock mtd_blkdevs mtdram mtd sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix thermal libata floppy thermal_sys scsi_mod e1000 [la st unloaded: scsi_wait_scan] 6[ 103.544118] Pid: 1020, comm: reboot Not tainted 2.6.32-5-amd64 #1 Bochs 6[ 103.544118] RIP: 0010:[810239db] [810239db] native_stop_other_cpus+0x86/0x90 6[ 103.544118] RSP: 0018:88001f2b3e08 EFLAGS: 0246 6[ 103.544118] RAX: 0001 RBX: 0246 RCX: 0001 6[ 103.544118] RDX: 0101010101010101 RSI: 00ff RDI: 0246 6[ 103.544118] RBP: 0001 R08: R09: 0008 6[ 103.544118] R10: R11: 81027dfc R12: 814d6740 6[ 103.544118] R13: R14: R15: 0001 6[ 103.544118] FS: 7ff3e26fe700() GS:88000180() knlGS: 6[ 103.544118] CS: 0010 DS: ES: CR0: 8005003b 6[ 103.544118] CR2: 7ff3e2701000 CR3: 1ddda000 CR4: 06f0 6[ 103.544118] DR0: DR1: DR2: 6[ 103.544118] DR3: DR6: DR7: 4[ 103.544118] Process reboot (pid: 1020, threadinfo 88001f2b2000, task 88001e89e350) 0[ 103.544118] Stack: 4[ 103.544118] 01234567 28121969 fee1dead 8102388b 4[ 103.544118] 0 810235f4 01234567 8105f961 4[ 103.544118] 0 02359000 7ff3e2186000 0[ 103.544118] Call Trace: 4[ 103.544118] [8102388b] ? native_machine_shutdown+0x56/0x6f 4[ 103.544118] [810235f4] ? native_machine_restart+0x21/0x37 4[ 103.544118] [8105f961] ? sys_reboot+0x146/0x190 4[ 103.544118] [810cea3e] ? free_pgtables+0x9c/0xbe 4[ 103.544118] [810fea38] ? dput+0x2c/0x15e 4[ 103.544118] [81103295] ? mntput_no_expire+0x23/0xee 4[ 103.544118] [810ecd86] ? filp_close+0x5b/0x62 4[ 103.544118] [81010b42] ? system_call_fastpath+0x16/0x1b 0[ 103.544118] Code: 76 0e 85 ed 75 e0 48 85 db 74 05 48 ff cb eb d6 9c 58 66 66 90 66 90 48 89 c3 fa 66 66 90 66 66 90 e8 1e 0b 00 00 48 89 df 57 9d 66 66 90 66 90 5b 5d 41 5c c3 48 83 ec 08 48 8b 05 b0 27 4b 00 1[ 103.544118] RIP [810239db] native_stop_other_cpus+0x86/0x90 4[ 103.544118] RSP 88001f2b3e08 4[ 103.544118] ---[ end trace c7434bd0d5312ada ]--- More info: 1) I disassembled the Code: part with gdb: Dump of assembler code for function f: 0x00600860 f+0:76 0e jbe0x600870 f+16 0x00600862 f+2:85 ed test %ebp,%ebp 0x00600864 f+4:75 e0 jne0x600846 data_start+6 0x00600866 f+6:48 85 db test %rbx,%rbx 0x00600869 f+9:74 05 je 0x600870 f+16 0x0060086b f+11: 48 ff cb dec%rbx 0x0060086e f+14: eb d6 jmp0x600846 data_start+6 0x00600870 f+16: 9c pushfq 0x00600871 f+17: 58 pop%rax 0x00600872 f+18: 66 66 90 xchg %ax,%ax 0x00600875 f+21: 66 90 xchg %ax,%ax 0x00600877 f+23: 48 89 c3 mov%rax,%rbx 0x0060087a f+26: fa cli 0x0060087b f+27: 66 66 90 xchg %ax,%ax 0x0060087e f+30: 66 66 90 xchg %ax,%ax 0x00600881 f+33: e8 1e 0b 00 00 callq 0x6013a4 0x00600886 f+38: 48 89 df mov%rbx,%rdi 0x00600889 f+41: 57 push %rdi 0x0060088a f+42: 9d popfq 0x0060088b f+43: 66 66 90 xchg %ax,%ax 0x0060088e f+46: 66 90 xchg %ax,%ax 0x00600890 f+48: 5b pop%rbx 0x00600891 f+49: 5d pop%rbp 0x00600892 f+50: 41 5c pop%r12 0x00600894 f+52: c3 retq 0x00600895 f+53: 48 83 ec 08sub$0x8,%rsp 0x00600899 f+57: 48 8b 05 b0 27 4b 00 mov 0x4b27b0(%rip),%rax# 0xab3050 0x006008a0 f+64: 00 00 add%al,(%rax) 2) I then run objdump -axdt /usr/lib/debug/boot/vmlinux-2.6.32-5-amd64 to see the
Bug#611832: linux-image-2.6.32-5-amd64: general protection fault at reboot under qemu: native_stop_other_cpus+0x86/0x90
Ben Hutchings b...@decadent.org.uk writes: Which version of qemu are you using in the host? If you are using kvm-qemu, which kernel version are you using in the host? The host is a xen domU: lindi1:~$ qemu-system-x86_64 --version QEMU PC emulator version 0.12.5 (Debian 0.12.5+dfsg-3), Copyright (c) 2003-2008 Fabrice Bellard lindi1:~$ dpkg-query -W qemu qemu0.12.5+dfsg-3 lindi1:~$ dmesg|head -n3 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011 0x00600889 f+41: 57 push %rdi 0x0060088a f+42: 9d popfq 0x0060088b f+43: 66 66 90 xchg %ax,%ax 0x0060088e f+46: 66 90 xchg %ax,%ax This looks like deliberate patching by the PV-alternatives mechanism. Is this PV-alternatives a linux or qemu feature or are they both cooperating? I tried to look around but couldn't find the code yet. -- 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/84lj1y126i@sauna.l.org
Bug#607879: System hangs up with mmap.c:873!
Ronny Standtke ronny.stand...@gmx.net writes: Just boot the DVD in your home machine, the installer starts up automatically and makes producing a Debian Live USB flash drive a breeze. Then you can test on any machine that can boot from USB. Well I don't have any DVDs and the cdrom drive is not easily accessible. I tried booting http://www.imedias.ch/dateien/lernstick-testversion/lernstick_debian5_2010-11-09.iso with xen configuration name = 'lernstick' vcpus = '1' memory = '1024' kernel = '/usr/lib/xen/boot/hvmloader' builder = 'hvm' device_model='/usr/lib/xen/bin/qemu-dm' disk = [ 'file:/local/xen/lernstick/lernstick_debian5_2010-11-09.iso,hdc:cdrom,r', 'file:/local/xen/lernstick/usb.img,hda,w' ] vif = [ 'bridge=eth0,mac=52:54:00:12:35:11' ] vnc=1 vnclisten='0.0.0.0' vncdisplay=22 vncpasswd='secret' keymap='sv' usbdevice='tablet' localtime=1 boot = 'd' but it gives me an error message in german and does not let me copypaste it :-) It seems to not recognize my empty usb.img as an usb stick. I tried creating partition with fdisk and filesystem with mkfs.vfat but it still can't recognize it as an usb stick. -- 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/84tyhb9lpp@sauna.l.org
Bug#607141: xm block-attach failed on domU
Peter Viskup skupko...@gmail.com writes:
'xm block-attach domain phy:data/disk /dev/xvda6 w'
I can attach a block device
$ sudo xm block-attach 27 file:/local/xen/lindi-exp1/disk.img /dev/xvda w
$ sudo xm block-list 27
Vdev BE handle state evt-ch ring-ref BE-path
51712 00 4 9 770 /local/domain/0/backend/vbd/27/51712
[ 81.988522] blkfront: xvda: barriers enabled
[ 81.988852] xvda: xvda1
[ 81.988969] xvda: p1 size 979902 exceeds device capacity, limited to end of
disk
and also detach it:
$ sudo xm block-detach 27 51712
This particular domU was started with
name = 'lindi-exp1'
vcpus = '1'
memory = '256'
kernel = '/local/xen/lindi-exp1/vmlinuz-2.6.32-5-amd64'
ramdisk = '/local/xen/lindi-exp1/initrd.img-2.6.32-5-amd64'
nfs_server = '10.7.2.17'
nfs_root = '/tftpboot/lindi-exp1'
extra = 'root=/dev/nfs ip=dhcp'
vif = [ 'mac=52:54:00:12:35:09' ]
cpuid = [ '0:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
'1:eax=0x0f61,ecx=0xx00x0x,edx=xxx0',
'0x8000:eax=0x8004,ebx=0x0,ecx=0x0,edx=0x0',
'0x8001:eax=0x0f61,ecx=xx0x,edx=00xx000xx0xxx0xx'
]
# up to leaf _0003/8000_0004
# family 15 model 6 stepping 1 (Intel P4 Prescott, AMD K8)
# disable POPCNT, SSE4.[12], SSSE3
# disable HTT
# disable CMPLEGACY, SVM, EXTAPIC, ALTMOVCR8, ABM, SSE4a, MisAlignSSE,
# 3DNOWPrefetch, OSVW, IBS, SSE5, SKINIT, WDT
# disable 3DNOW, 3DNOWEXT, RDTSCP, Page1GB, FFXSR, MMXExt, MP
#
# Source: Cross-Vendor Migration
# AMD Operating Systems Research Center
# Uwe Dannowski Andre Przywara
# {firstname.lastna...@amd.com
# 2010 Advanced Micro Devices, Inc. All rights reserved.
--
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/84y66tcglr@sauna.l.org
Bug#607495: linux-image-2.6.32-5-amd64: kernel freeze
Philip Ashmore cont...@philipashmore.com writes: What I really meant was your hardware device info. $ lspci 00:00.0 Host bridge: ATI Technologies Inc RD890 Northbridge only single slot PCI-e GFX Hydra part (rev 02) 00:04.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port D) 00:06.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port F) 00:07.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port G) 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40) 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 41) 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller (rev 40) 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller 00:16.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller 00:16.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control 01:05.0 VGA compatible controller: S3 Inc. 86c325 [ViRGE] (rev 06) 02:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8059 PCI-E Gigabit Ethernet Controller (rev 11) 04:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 04:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) -- 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/84tyhhcfqf@sauna.l.org
Bug#609448: linux-source-2.6.37: source code not included for drivers/staging/ft1000/ft1000-pcmcia/boot.h?
Package: linux-source-2.6.37
Version: 2.6.37-1~experimental.1
Severity: serious
drivers/staging/ft1000/ft1000-pcmcia/boot.h seems to contain firmware
in binary form. Is the source code available somewhere?
(This is the only blob I could find with
http://www.linux-libre.fsfla.org/pub/linux-libre/releases/2.6.37-libre/deblob-2.6.37)
$ head -n50 linux-source-2.6.37/drivers/staging/ft1000/ft1000-pcmcia/boot.h
//---
// FT1000 driver for Flarion Flash OFDM NIC Device
//
// Copyright (C) 2002 Flarion Technologies, All rights reserved.
//
// This program is free software; you can redistribute it and/or modify it
// under the terms of the GNU General Public License as published by the Free
// Software Foundation; either version 2 of the License, or (at your option) any
// later version. This program is distributed in the hope that it will be
useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY
// or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
// more details. You should have received a copy of the GNU General Public
// License along with this program; if not, write to the
// Free Software Foundation, Inc., 59 Temple Place -
// Suite 330, Boston, MA 02111-1307, USA.
//---
//
// File: boot.h
//
// Description:boatloader
//
// History:
// 1/11/05WhcPorted to Linux.
//
//---
#ifndef _BOOTH_
#define _BOOTH_
// Official bootloader
unsigned char bootimage [] = {
0x00,0x00,0x01,0x5E,0x00,0x00
,0x00,0x00,0x00,0x00,0x02,0xD7
,0x00,0x00,0x01,0x5E,0x46,0xB3
,0xE6,0x02,0x00,0x98,0xE6,0x8C
,0x00,0x98,0xFB,0x92,0xFF,0xFF
,0x98,0xFB,0x94,0xFF,0xFF,0x98
,0xFB,0x06,0x08,0x00,0x98,0xFB
,0x96,0x84,0x00,0x98,0xFB,0x08
,0x1C,0x00,0x98,0xFB,0x51,0x25
,0x10,0x1C,0x00,0xE6,0x51,0x01
,0x07,0xFD,0x4C,0xFF,0x20,0xF5
,0x51,0x02,0x20,0x08,0x00,0x4C
,0xFF,0x20,0x3C,0x00,0xC0,0x64
,0x98,0xC0,0x66,0x98,0xC0,0x68
,0x98,0xC0,0x6A,0x98,0xC0,0x6C
,0x98,0x90,0x08,0x90,0x09,0x90
,0x0A,0x90,0x0B,0x90,0x0C,0x90
,0x0D,0x90,0x0E,0x90,0x0F,0x90
,0x04,0x90,0x06,0xFB,0x51,0x22
,0x16,0x08,0x03,0xFB,0x51,0x52
...
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
--
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/84ei8mdro6@sauna.l.org
Bug#609448: linux-source-2.6.37: source code not included for drivers/staging/ft1000/ft1000-pcmcia/boot.h?
Ben Hutchings b...@decadent.org.uk writes: I do check for blobs in each new upstream version but apparently I missed this one. Thanks a lot for your work. Are you using the same deblob script or is there some heuristics used for new versions? -- 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/84aajadofl@sauna.l.org
Bug#609149: nfs-kernel-server: after some time, the server nfs is not working, and no client can mount share
yellow yellowprot...@gmail.com writes: Package: nfs-kernel-server Version: 1:1.2.2-4 Severity: normal For the clients to mount their /home, I need to do : Jikes, that sounds scary. How often do you need to restart it? Can you make it happen more often if you mount/remount in a loop? -- 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/841v4phjt7@sauna.l.org
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- 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/8462u5jfpm@sauna.l.org
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks [resending via smtp.academica.fi since smtp.netsonic.fi does not seem to be delivering my emails any time soon...] Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- 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/8462u4ibfp@sauna.l.org
Bug#608250: acpi-cpufreq: Error inserting acpi_cpufreq module: No such device
Hi, thanks for your report. I get the same behavior: overlord3:~$ sudo modprobe acpi-cpufreq FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.32-5-xen-amd64/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device overlord3:~$ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-29 Does this work if you boot the same machine without xen? -Timo -- 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/84r5d1q7rg@sauna.l.org
Bug#607879: System hangs up with mmap.c:873!
Ronny Standtke ronny.stand...@gmx.net writes: I just tested it. Booting the DVD ISO in qemu took more than 20 minutes to get How much RAM did you assign to the virtualized machine? I think the default is 128MB. I did not experience the system hang in this one single qemu test run (I also do not run into the system hangup on real hardware all the time) but I fail to see the value in retrying with quemu as it is slow beyond repair. We better test with real hardware and real scenarios. Sure, I was just asking if there would be something I could easily test here. I don't have a machine with cdrom drive easily accessible (my work machine is a geode, my laptop does not have cdrom and my home machine is in a closet to make it more quiet...) -Timo -- 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/84ipycqwo5@sauna.l.org
Bug#607879: System hangs up with mmap.c:873!
Ronny Standtke ronny.stand...@gmx.net writes: I can confirm this bug. I created a Debian Live system based on Squeeze and on many machines the system just hangs when shutting down. My latest test was on a Dell Optiplex SX280. I will attach the entries in kern.log and the output of lspci on this system. ok, does it happen if you boot the livecd under qemu? -- 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/84r5d2rvha@sauna.l.org
Bug#607879: System hangs up with mmap.c:873!
Grzegorz Wyrobek w.gri...@gmail.com writes: So I'm looking forward to fix this bug. We are going to make test ISO tomorrow for you. If the ISO includes non-free nvidia drivers then I don't think I want to test it either. Are you creating them with live-helper? -- 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/841v53uxv9@sauna.l.org
Bug#607709: XEN kernel crash on DNS process
Giuseppe Sacco giuse...@eppesuigoccas.homedns.org writes: Package: linux-image-2.6.32-5-xen-686 Version: 2.6.32-27 Severity: important Are you running this as a dom0 or domU? You don't need to use a -xen- kernel as a domU. -- 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/84tyi0won3@sauna.l.org
Bug#607141: xm block-attach failed on domU
Peter Viskup skupko...@gmail.com writes: Execution of xm block-attach to PV domU failed and I have got Ooops kernel messages in attachment. Can you tell me the exact block-attach command so that I can at least test that it works with squeeze? (I doubt it can be fixed for lenny.) -- 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/84y67cwpcr@sauna.l.org
Bug#607879: System hangs up with mmap.c:873!
gring...@poczta.onet.pl writes: Dec 7 12:16:26 wokanda1 kernel: [ 24.817488] [f08bda3f] ? aufs_fault+0xf1/0xfb [aufs] Hmm, how are you using aufs? (I have never used it so I don't even know how to set it up to test anything...) -- 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/84lj3cwo3x@sauna.l.org
Bug#607709: XEN kernel crash on DNS process
Giuseppe Sacco giuse...@eppesuigoccas.homedns.org writes: This is dom0 hosting a windows machine. Ok, then I'm afraid I can't help much. I know only about debugging domU'ss and not dom0's. -- 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/8462ugw5b6@sauna.l.org
Bug#607495: linux-image-2.6.32-5-amd64: kernel freeze
Philip Ashmore cont...@philipashmore.com writes: I'd recommend also attaching your hardware information, or trying it Not sure how much this matters under xen really but the cpuinfo in dom0 has processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 10 model name : AMD Phenom(tm) II X6 1090T Processor stepping: 0 cpu MHz : 902692.661 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch bogomips: 6421.72 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate [9] and 5 other cores. on a non-Xen kernel - something is different. Sorry but I was only trying this out since if I had managed to reproduce it under xen I could do something about it :-) Also, I'm not familiar with the output in your report - just out of interest, what's the source? xm console DOMAIN but dmesg really should show the same info. -- 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/841v54w40r@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
Richard Mittendorfer del...@gmx.net writes: Did you try with an updated dom0 kernel as well? 64bit dom0 seems to shutdown and reboot properly. -- 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/84k4jc7l69@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
Ian Campbell i...@hellion.org.uk writes: Just to clarify, since the recent messages are not completely clear on the details, we think that with the 2.6.32-29 package reboot works fine for both 32 and 64 bit domU and dom0? Yes. It seems the failed reboot of 32-bit domUs was due to [2010-12-14 13:01:45 2071] ERROR (XendDomainInfo:2205) VM squeeze32 restarting too fast (Elapsed time: 24.226863 seconds). Refusing to restart to avoid loops. (The limit seems to be hardcoded to 60 seconds) -- 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/84bp4o7gov@sauna.l.org
Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'
Peter Viskup skupko...@gmail.com writes: Package: linux-image-2.6-xen-amd64 Version: 2.6.26+17+lenny1 Can you try linux-image-2.6.32-5-xen-amd64 2.6.32-29 from debian squeeze? You probably should be able to install it to a lenny system without upgrading the system otherwise. -- 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/8462uw83or@sauna.l.org
Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'
Peter Viskup skupko...@gmail.com writes: I want to run official Debian stable versions. I understand that perfectly. However, it is not likely that this can be fixed for 2.6.26 -- the best thing you can do about this problem is to ensure that it gets fixed before squeeze is released. Just find there is backports version linux-image-2.6.32-bpo.5-xen-amd64 available. I need to know what the bug is if the move to this backports kernel will help - just before I will install it. I am running production servers and cannot just test that. Difficult situation indeed. In that case you probably only can hope that somebody else is able to reproduce the bug on their system. I have experince only on debugging domUs, I don't even know how to dump the state of a dom0 to disk. -- 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/841v5k81im@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
Richard Mittendorfer del...@gmx.net writes: Did you try with an updated dom0 kernel as well? Don't have 32bit guests here, neither gave debian 2.6.32-29 a try yet. Reboot seems to work with a 64bit guest: squeeze64:~# dmesg|head -n4 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 15:35:08 UTC 2010 [0.00] Command line: root=/dev/xvda ro console=hvc0 squeeze64:~# shutdown -r now Broadcast message from r...@squeeze64 (hvc0) (Sun Dec 12 12:45:59 2010): The system is going down for reboot NOW! INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signal Using makefile-style concurrent boot in runlevel 6. Stopping internet superserver: inetd. Stopping NTP server: ntpd. Stopping deferred execution scheduler: atd. Stopping MTA: exim4_listener. Stopping kernel log daemon Stopping system log daemon acpid: exiting Asking all remaining processes to terminate...done. All processes ended within 1 secondsdone. Stopping portmap daemon Stopping NFS common utilities: statd. Saving the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Deconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:01:01:99:7e:eb Sending on LPF/eth0/00:01:01:99:7e:eb Sending on Socket/fallback DHCPRELEASE on eth0 to 10.7.2.14 port 67 invoke-rc.d: - invoke-rc.d: WARNING: 'invoke-rc.d ntp try-restart' called invoke-rc.d: during shutdown sequence. invoke-rc.d: enabling safe mode: initscript policy layer disabled invoke-rc.d: - done. Cleaning up ifupdown Deactivating swap...done. Will now restart. [ 105.523291] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 105.832221] Restarting system. overlord2:~$ sudo xm console squeeze64 [0.00] Initializing cgroup subsys cpuset ... squeeze64 login: -- 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/841v5n9si0@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
Hi, at least on a 32-bit domU, 2.6.32-29 seems to break reboot completely. The guest just disappears as if it had called halt instead: overlord2:~$ cat /local/xen/squeeze32/config name = 'squeeze32' bootloader = '/usr/bin/pygrub' vcpus = '4' memory = '512' disk = [ 'file:/local/xen/squeeze32/disk.img,xvda,w' ] vif = [ 'mac=00:01:01:99:7e:ec' ] overlord2:~$ sudo xm create -c /local/xen/squeeze32/config ... squeeze32:~# dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-686-bigmem 2.6.32-29 squeeze32:~# reboot Broadcast message from r...@squeeze32 (hvc0) (Sat Dec 11 19:03:00 2010): The system is going down for reboot NOW! INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signal Using makefile-style concurrent boot in runlevel 6. Stopping internet superserver: inetd. Stopping NTP server: ntpd. Stopping deferred execution scheduler: atd. Stopping MTA: exim4_listener. Asking all remaining processes to terminate...done. All processes ended within 1 secondsdone. Stopping enhanced syslogd: rsyslogd. Stopping portmap daemon Stopping NFS common utilities: statd. Saving the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Deconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:01:01:99:7e:ec Sending on LPF/eth0/00:01:01:99:7e:ec Sending on Socket/fallback DHCPRELEASE on eth0 to 10.7.2.14 port 67 invoke-rc.d: - invoke-rc.d: WARNING: 'invoke-rc.d ntp try-restart' called invoke-rc.d: during shutdown sequence. invoke-rc.d: enabling safe mode: initscript policy layer disabled invoke-rc.d: - done. Cleaning up ifupdown Deactivating swap...done. Will now restart. [ 37.194669] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 37.502669] Restarting system. overlord2:~$ sudo xm info host : overlord2 release: 2.6.32-5-xen-amd64 version: #1 SMP Sat Oct 30 17:04:10 UTC 2010 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2394 hw_caps: bfebfbff:20100800::0940:e3bd::0001: virt_caps : hvm hvm_directio total_memory : 8189 free_memory: 1028 node_to_cpu: node0:0-3 node_to_memory : node0:1028 node_to_dma32_mem : node0:28 max_node_id: 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: cc_compiler: gcc version 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Fri Sep 3 15:38:12 UTC 2010 xend_config_format : 4 overlord2:~$ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-28 overlord2:~$ sudo xm list NameID Mem VCPUs State Time(s) Domain-0 0 2357 4 r- 62876.9 lindi1 24 1024 4 -b 9442.2 -- 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/84y67w9qya@sauna.l.org
Bug#606520: linux-tools-2.6.36: /usr/bin/perf_2.6.36 links against openssl but copyright lists only GPLv2 without exceptions
Package: linux-tools-2.6.36 Version: 2.6.36-1~experimental.1 Severity: serious /usr/share/doc/linux-tools-2.6.36/copyright gives me the impression that we have a license to distribute /usr/bin/perf_2.6.36 only under the terms of the GPLv2. Is this correct? It seems that perf_2.6.36 uses openssl: $ ldd /usr/bin/perf_2.6.36|grep ssl libssl.so.0.9.8 = /usr/lib/libssl.so.0.9.8 (0x7f20fad1f000) Has perf upstream given an exception to GPLv2 to allow us to do this or is this indeed a real problem? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages linux-tools-2.6.36 depends on: ii binutils2.20.1-15The GNU assembler, linker and bina ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libelf1 0.148-1 library to read and write ELF file ii libperl5.10 5.10.1-16shared Perl library ii libpython2.62.6.6-6 Shared Python runtime library (ver ii perl5.10.1-16Larry Wall's Practical Extraction ii python 2.6.6-3+squeeze1 interactive high-level object-orie ii python-support 1.0.10 automated rebuilding support for P Versions of packages linux-tools-2.6.36 recommends: ii linux-base 2.6.36-1~experimental.1 Linux image base package Versions of packages linux-tools-2.6.36 suggests: pn linux-doc-2.6.36 none (no description available) -- no debconf information -- 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/84hbembpcu@sauna.l.org
Bug#606520: linux-tools-2.6.36: /usr/bin/perf_2.6.36 links against openssl but copyright lists only GPLv2 without exceptions
Ben Hutchings b...@decadent.org.uk writes: I have no idea what the upstream developers intended, they seem a bit clueless about distribution. I only just realised that they try to use libbfd (GPLv3, incompatible) even though perf can get the same functionality from libiberty (GPLv2)! Hmm, are you planning to file a separate bug report about that? -- 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/84d3paayva@sauna.l.org
Bug#606520: linux-tools-2.6.36: /usr/bin/perf_2.6.36 links against openssl but copyright lists only GPLv2 without exceptions
Ben Hutchings b...@decadent.org.uk writes: Since perf doesn't use any of the functionality in libssl via Python, I'm not convinced there's a problem here. Good. Would it be appropriate to describe this in copyright file though? -- 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/848vzyaytz@sauna.l.org
Bug#602273: [PATCH] Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Ian Campbell i...@hellion.org.uk writes: On Wed, 2010-11-03 at 13:23 +0200, Timo Juhani Lindfors wrote: http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html Thanks, I've pinged upstream to see if this patch will be applied and also requested that it gets tagged to go into stable. Any news on this? Did you ping them on the xen-devel mailing list? (I tried to look but there are so many messages that I didn't spot your ping). -- 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/8439q9dh40@sauna.l.org
Bug#602273: [PATCH] Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Ian Campbell i...@hellion.org.uk writes: My ping at http://marc.info/?l=linux-kernelm=128879080525214w=2 went unanswered but Jeremy picked it up again at http://marc.info/?l=linux-kernelm=129045702011984w=2 and it seems to have gone into the tip.git tree (in x86/urgent) but not to Linus yet. Ok thanks. I hope you are still planning to add this to squeeze when it reaches Linus. -- 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/84y681bxky@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
I can reproduce the problem. The guest never really quits: squeeze64:~# dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-amd64 2.6.32-28 squeeze64:~# halt Broadcast message from r...@squeeze64 (hvc0) (Tue Nov 30 13:02:53 2010): The system is going down for system halt NOW! INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal Using makefile-style concurrent boot in runlevel 0. Stopping deferred execution scheduler: atd. Stopping MTA: exim4_listener. Stopping internet superserver: inetd. Stopping NTP server: ntpd. Stopping kernel log daemon Stopping system log daemon Asking all remaining processes to terminate...acpid: exiting done. All processes ended within 1 secondsdone. Stopping NFS common utilities: statd. Stopping portmap daemon Saving the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Deconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:01:01:99:7e:eb Sending on LPF/eth0/00:01:01:99:7e:eb Sending on Socket/fallback DHCPRELEASE on eth0 to 10.7.2.14 port 67 invoke-rc.d: - invoke-rc.d: WARNING: 'invoke-rc.d ntp try-restart' called invoke-rc.d: during shutdown sequence. invoke-rc.d: enabling safe mode: initscript policy layer disabled invoke-rc.d: - done. Cleaning up ifupdown Deactivating swap...done. Will now halt. [ 3467.394863] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 3467.701267] System halted. Before I was seeing squeeze64:~# halt Broadcast message from r...@squeeze64 (hvc0) (Tue Nov 30 12:04:38 2010): The system is going down for system halt NOW! INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal squeeze64:~# Using makefile-style concurrent boot in runlevel 0. Stopping deferred execution scheduler: atd. Stopping internet superserver: inetd. Stopping MTA: exim4_listener. Stopping NTP server: ntpd. Stopping kernel log daemon Stopping system log daemon Asking all remaining processes to terminate...acpid: exiting done. All processes ended within 1 secondsdone. Stopping NFS common utilities: statd. Stopping portmap daemon Saving the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Deconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:01:01:99:7e:eb Sending on LPF/eth0/00:01:01:99:7e:eb Sending on Socket/fallback DHCPRELEASE on eth0 to 10.7.2.14 port 67 invoke-rc.d: - invoke-rc.d: WARNING: 'invoke-rc.d ntp try-restart' called invoke-rc.d: during shutdown sequence. invoke-rc.d: enabling safe mode: initscript policy layer disabled invoke-rc.d: - done. Cleaning up ifupdown Deactivating swap...done. Will now halt. [ 60.457148] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping [ 61.089264] System halted. overlord2:~$ -- 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/84tyizhxym.fsf...@sauna.l.org
Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
Richard Mittendorfer del...@gmx.net writes: Version: 2.6.32-28 likely https://lkml.org/lkml/2010/11/26/197 Does this mean that you tested 2.6.32-27 and that works? -- 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/8439qjjsr0@sauna.l.org
Bug#575833: problem still exists and should be fixed for embedded systems like the ALIX
Marcel Langner marcel.lang...@gmx.net writes: Bug seems to exist for a long time now. Should be fixed before Squeeze gets out officially! 1) Are the scheduling while atomic and transmit timed out different bugs? 2) Have you tried if this occurs with mainline kernel from kernel.org? I have a geode box with $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 498.106 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips: 996.21 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: and via-rhine $ dpkg-query -W linux-image-2.6.32-5-486 linux-image-2.6.32-5-4862.6.32-27 that sometimes goes to an odd state. Under lenny: fomalhaut:~$ ping -i 0.2 garfield 64 bytes from garfield.lan (10.7.3.37): icmp_seq=15 ttl=64 time=0.366 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=1 ttl=64 time=2914 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=2 ttl=64 time=2705 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=3 ttl=64 time=2497 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=4 ttl=64 time=2289 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=5 ttl=64 time=2081 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=6 ttl=64 time=1874 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=7 ttl=64 time=1666 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=8 ttl=64 time=1458 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=9 ttl=64 time=1250 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=10 ttl=64 time=1042 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=11 ttl=64 time=834 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=12 ttl=64 time=626 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=13 ttl=64 time=418 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=14 ttl=64 time=210 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=16 ttl=64 time=9344 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=17 ttl=64 time=9137 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=18 ttl=64 time=8929 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=19 ttl=64 time=8721 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=20 ttl=64 time=8513 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=21 ttl=64 time=8305 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=22 ttl=64 time=8098 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=23 ttl=64 time=7890 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=24 ttl=64 time=7681 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=25 ttl=64 time=7474 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=26 ttl=64 time=7266 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=27 ttl=64 time=7058 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=28 ttl=64 time=6850 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=29 ttl=64 time=6642 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=30 ttl=64 time=6434 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=31 ttl=64 time=6226 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=32 ttl=64 time=6018 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=33 ttl=64 time=5811 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=34 ttl=64 time=5603 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=35 ttl=64 time=5395 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=36 ttl=64 time=5186 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=37 ttl=64 time=4979 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=38 ttl=64 time=4771 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=39 ttl=64 time=4563 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=40 ttl=64 time=4355 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=41 ttl=64 time=4147 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=42 ttl=64 time=3939 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=43 ttl=64 time=3732 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=44 ttl=64 time=3524 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=45 ttl=64 time=3316 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=46 ttl=64 time=3108 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=47 ttl=64 time=2900 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=48 ttl=64 time=2692 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=49 ttl=64 time=2484 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=50 ttl=64 time=2276 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=51 ttl=64 time=2068 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=52 ttl=64 time=1860 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=53 ttl=64 time=1652 ms 64 bytes from garfield.lan (10.7.3.37): icmp_seq=54
Bug#575833: problem still exists and should be fixed for embedded systems like the ALIX
Marcel Langner marcel.lang...@gmx.net writes: Does a report exists for this transmit timeout problem already? I don't know. I have hit the issue only twice and it is difficult to debug so I did not report it yet. No I have not. Do you think it makes sense to try it? It's a long time since I compiled my own kernel. I think that is needed. If it works with mainline kernel then we can start looking for the patch that fixed it. If it doesn't work then you can report the bug upstream. btw, always keep 575...@bugs.debian.org in Cc so that the bug discussion is not lost. -- 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/847hfyn49g@sauna.l.org
Bug#593245: linux-image-2.6.32-5-xen-amd64_2.6.32-20_amd64.deb can't start VM's due to udev rule mismatch
Ian Campbell i...@hellion.org.uk writes: The version of xen-utils-common may also have some bearing on this since it is the package which provides /lib/udev/rules.d/xend.rules Here in working case I have $ dpkg-query -W xen* xen-hypervisor-amd64 xen-linux-system-2.6.32-5+bug580889.1-xen-amd64 xen-tools xen-utils-common4.0.0-1 xenstore-utils 4.0.1-1 It's also worth checking for stale entries in /etc/udev/rules.d (or whatever the previous path was) which might be interfering. $ md5sum /lib/udev/rules.d/*xen* cea42daba332764f255dadec112f64c5 /lib/udev/rules.d/xen-backend.rules 5a306f5dba657c3c962c158782e848fb /lib/udev/rules.d/xend.rules -- 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/84aal0fmlw@sauna.l.org
Bug#603432: linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
Christoph Anton Mitterer cales...@scientia.net writes: Unfortunately it turned out, that my ISP had to but that respective cluster into production now, and was therefore not longer able to play around very much. That's unfortunate. Do they advertise support for hosting debian in a xen publicly? -- 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/8462vofmjo@sauna.l.org
Bug#604442: linux-image-2.6-686: Kernel Oops after return from hibernation
George B. i93.b...@gmail.com writes: Nov 22 10:03:19 deli kernel: [12673.102822] [c11be566] ? mousedev_destroy+0xe/0x2c Just to narrow things down. Does this occur if you 1) login using ssh from another computer 2) stop Xorg 3) sudo rmmod psmouse usbhid hid ? If yes, is just loading one of these modules enough to make it crash or do you need to be running Xorg too? Finally, what laptop is this? And, how do you exactly hibernate? -- 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/844ob9hbqn@sauna.l.org
Bug#599823: linux-2.6: XEN and NFS causes duplicate filenames with large directories
Jason Kendall jakend...@gmail.com writes: 1. All the scripts/commands should be run on the client. 2. As far as I can tell, you can't just move the directory, you have to move each file, but again, I was able to trigger it with just the process of making the files. 3. Most of the time there is no difference seen on any other client, meaning the one with the bug only shows the duplicate files. I have never seen duplicate files on the server. I still get no duplicate files: $ for i in $(seq 1 1); do touch tmp/$i; done $ ls tmp | sort | uniq -d $ for i in $(seq 1 1); do mv tmp/$i tmp/$i.a; done $ ls tmp | sort | uniq -d $ ls tmp | wc -l 1 What exact commands did you use? -- 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/847hg8l3yy@sauna.l.org
Bug#599823: linux-2.6: XEN and NFS causes duplicate filenames with large directories
Jason Kendall jakend...@gmail.com writes: Which kernel do you have on this client - what are your NFS mount options for this directory? linux-image-2.6.32-5-amd64 2.6.32-27 nfs:/home /home nfs rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.7.2.3,mountvers=3,mountport=56804,mountproto=udp,addr=10.7.2.3 0 0 -- 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/8439qwkpy3@sauna.l.org
Re: [PATCH] remove build directories on clean
Ben Hutchings b...@decadent.org.uk writes: On Mon, 2010-11-15 at 12:55 +0200, Timo Juhani Lindfors wrote: Ben Hutchings b...@decadent.org.uk writes: However, the same applies to several other package names that change with the upstream version number: linux-source-version, linux-doc-version, linux-manual-version and linux-patch-debian-version. I think perhaps we should remove those with wildcards as well. Here's a new patch that removes more than just linux-support-*: Index: linux-2.6/debian/rules === --- linux-2.6/debian/rules (revision 16542) +++ linux-2.6/debian/rules (working copy) @@ -56,7 +56,7 @@ clean: debian/control dh_testdir - rm -rf $(BUILD_DIR) $(STAMPS_DIR) debian/lib/python/debian_linux/*.pyc debian/linux-headers-* debian/linux-image-* debian/linux-tools-* + rm -rf $(BUILD_DIR) $(STAMPS_DIR) debian/lib/python/debian_linux/*.pyc debian/linux-headers-* debian/linux-image-* debian/linux-tools-* debian/linux-support-* debian/linux-source-* debian/linux-doc-* debian/linux-manual-* debian/linux-patch-debian-* dh_clean binary-indep: $(STAMPS_DIR)/source-base
Bug#604013: base: ls -al on armel inside loopback mounted ISO image failes with -1 ENOMEM
Holger Levsen hol...@layer-acht.org writes: This is a test on the Kirkwood machine: r...@dockstar:/srv/tftp# md5sum systemrescuecd-x86-1.6.2.iso b7662eb44b530d62c487dd367f2036ed systemrescuecd-x86-1.6.2.iso r...@dockstar:/srv/tftp# uname -a Linux dockstar.lab.elconas.de 2.6.32-5-kirkwood #1 Sat Sep 18 15:20:08 UTC 2010 armv5tel GNU/Linux r...@dockstar:/srv/tftp# mount -o loop systemrescuecd-x86-1.6.2.iso sysrescuecd r...@dockstar:/srv/tftp# ls -al sysrescuecd ls: cannot access sysrescuecd/bootdisk: Cannot allocate memory Works for me: # mount systemrescuecd-x86-1.6.3.iso /mnt -oloop # ls -la /mnt total 228070 dr-xr-xr-x 1 root root 2048 Oct 30 17:53 . drwxr-xr-x 22 root root 4096 Jul 18 18:05 .. dr-xr-xr-x 1 root root 2048 Jun 11 20:15 bootdisk dr-xr-xr-x 1 root root 2048 May 26 08:07 bootprog dr-xr-xr-x 1 root root 2048 Oct 30 17:54 isolinux dr-xr-xr-x 1 root root 2048 Mar 2 2010 ntpasswd -r-xr-xr-x 1 root root 233508864 Oct 30 17:53 sysrcd.dat -r-xr-xr-x 1 root root45 Oct 30 17:53 sysrcd.md5 dr-xr-xr-x 1 root root 2048 Oct 23 10:24 usb_inst -r-xr-xr-x 1 root root 15672 Sep 25 22:20 usb_inst.sh -r-xr-xr-x 1 root root 877 Sep 25 22:20 usbstick.htm -r-xr-xr-x 1 root root 6 Oct 30 17:53 version # dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-versatile 2.6.32-27 # md5sum systemrescuecd-x86-1.6.3.iso 1a20150368442063a3fbc7b5faa127e2 systemrescuecd-x86-1.6.3.iso (md5sum differs since I accidentally downloaded newer version of systemrescuecd...) -- 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/84bp5lkofx@sauna.l.org
Bug#583895: linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important
Kind of hard to debug without console output indeed. Does the kernel boot without xen? Have you tried 2.6.32-27? -- 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/84sjyzm589@sauna.l.org
Bug#593245: linux-image-2.6.32-5-xen-amd64_2.6.32-20_amd64.deb can't start VM's due to udev rule mismatch
With $ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-27 I see $ find /dev|grep evt /dev/.udev/db/misc:xen/evtchn /dev/xen/evtchn Does everything work if you create evtchn manually with mknod /dev/xen/evtchn c 10 57? -- 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/84oc9nm4zi@sauna.l.org
Bug#603811: linux-image-2.6.26-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
You meantion SCHED_IDLE only in the subject but don't elaborate it in the bug report itself. What do you mean by it exactly? -- 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/84r5eilskc@sauna.l.org
Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Artur Linhart al.li...@bcpraha.com writes: If the kernel is used for paravirtual DomU, then the DomU is normally started orshutdown. Ifthe xm save and xm restore is invoked explicitely,then the DomU also restores normally. Only in the case the DomU is restored automatically via xendomains script facility on Dom0 start it is restored, so visible in the list This is most likely a duplicate of my bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273 Can you please test the patch that is included in that bug report? -- 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/84lj4sp01s@sauna.l.org
Bug#603811: linux-image-2.6.26-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
masterdead masterd...@gmail.com writes: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-25 Severity: important What hardware do you have? Especially disks, raid/lvm/crypto configuration would be important. Is there any kind of virtualization involved? -- 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/84eiakoup0@sauna.l.org
Bug#599823: linux-2.6: XEN and NFS causes duplicate filenames with large directories
Works for me. In the following ceasar and lindi1 are nfs clients, lindi1 is a domU with 2.6.32-27 and nova is an nfs server with 2.6.26+17+lenny1: nova:~$ ssh caesar bash -c 'for i in \$(seq 1 1); do touch tmp/\$i; done' nova:~$ ssh lindi1 ls tmp | sort | uniq -d nova:~$ ssh caesar mv tmp/1 tmp/1.new nova:~$ ssh lindi1 ls tmp | sort | uniq -d -- 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/84aal7nkyj@sauna.l.org
Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
Hmm. So you are running an X server in the dom0 or in a domU? -- 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/8462vvnkp0@sauna.l.org
Bug#582021: linux-image-2.6.32-bpo.4-xen-amd64 misses networking booting domUs installed via xen-tools
Hi, it would be useful to know sudo brctl show sudo xm info sudo xm list lsmod dpkg-query -W linux-image-$(uname -r) on dom0 when you have no networking and sudo ip link lsmod dpkg-query -W linux-image-$(uname -r) on domU when you have no networking. With squeeze dom0 and domU on amd64 at least cat config EOF name = 'squeeze64' bootloader = '/usr/bin/pygrub' vcpus = '4' memory = '512' disk = [ 'file:/local/xen/squeeze64/disk.img,xvda,w' ] vif = [ 'mac=00:01:01:99:7e:eb' ] EOF sudo xm create -c config has networking. -- 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/84wrobm5f2@sauna.l.org
Re: [PATCH] remove debian/linux-support-* on clean
Ben Hutchings b...@decadent.org.uk writes: However, the same applies to several other package names that change with the upstream version number: linux-source-version, linux-doc-version, linux-manual-version and linux-patch-debian-version. I think perhaps we should remove those with wildcards as well. Sure, should I send a new patch or is it easier for you to just edit the file and commit? (I didn't notice those other cases since I only build -image, -headers and -dbg). -- 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/847hgeam9w@sauna.l.org
Bug#603432: linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
Christoph Anton Mitterer cales...@scientia.net writes: If you need any further help or so, please ask. My great ISP (Star-Hosting) is very cooperative and they'll probably give me a test system for some time, if we need it. Thanks for reporting this bug. Can you please save the save the state of the hung domU by executing xm dump-core $DOMAIN $DOMAIN.dump on dom0 (you probably need your ISP to run it for you) and then apt-get install linux-image-2.6.32-5-amd64-dbg crash on some squeeze machine (even your domU booted with another kernel is ok) so that you can say crash -e emacs /usr/lib/debug/boot/vmlinux-2.6.32-5-amd64 $DOMAIN.dump and then invoke at least the following commands in the crash prompt: sys ps foreach bt -f foreach bt -F -- 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/84fwv4cd94@sauna.l.org
Bug#603432: linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
Christoph Anton Mitterer cales...@scientia.net writes: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-27 Severity: important Can you also attach the output of xm info from the dom0 to the bug report? 2.6.32-27 boots here as a domU just fine when I also use 2.6.32-27 as a dom0 :-) -- 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/847hggc7zh@sauna.l.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Angelo Pantano a.pant...@siodata.it writes: since I cannot dump a core if the machine has already crashed I dumped it right after launching the migration command I'm afraid that dump is not going to be very useful. There must be a way to trigger dumping on crash? -- 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/8439r4c4jh@sauna.l.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Hi, Google finds the same crash at http://www.chiark.greenend.org.uk/~xensrcts/logs/2449/test-amd64-amd64-pair/guest-debian.guest.osstest-console which is apparently some sort of testsuite log. It says that the version was 28a160746815. Then in the same directory hierarchy I found that the first non-failing version is http://www.chiark.greenend.org.uk/~xensrcts/logs/2473/test-amd64-amd64-pair/guest-debian.guest.osstest-console which says this 6c72eadd151f6f1b904989532a83988af0ea661a, baseline d0054d672ff0ebf6116cee27bae3fc2591c726af -- I have no idea if the bug was fixed or the test was changed. Ian, I noticed you were hosting the testsuite results so I hope it's ok to Cc you about this bug. Can you enlighten us on whether the failing test has already been fixed? For reference here's the beginning of the failing flight 2449: [ 37.107944] BUG: unable to handle kernel paging request at 7f7f850b0098 [ 37.107944] IP: [8105eb42] fill_pmd+0x13/0xec [ 37.107944] PGD 0 [ 37.107944] Oops: [#1] SMP [ 37.107944] last sysfs file: /sys/kernel/uevent_seqnum [ 37.107944] CPU 0 [ 37.107944] Modules linked in: [last unloaded: scsi_wait_scan] [ 37.107944] Pid: 1509, comm: kstop/0 Not tainted 2.6.32.24 #1 [ 37.107944] RIP: e030:[8105eb42] [8105eb42] fill_pmd+0x13/0xec [ 37.107944] RSP: e02b:88001fd1fd20 EFLAGS: 00010082 [ 37.107944] RAX: 0ff8 RBX: c7f8 RCX: ff57a000 [ 37.107944] RDX: 8000cf4d2063 RSI: ff57a000 RDI: c7f8 [ 37.107944] RBP: 88001fd1fd40 R08: R09: 88001fc64008 [ 37.107944] R10: 0396 R11: 8103bb01 R12: 8000cf4d2063 [ 37.107944] R13: ff57a000 R14: e8fe96c8 R15: 88001fcda5d0 [ 37.107944] FS: 7fb35eb96790() GS:8800026b2000() knlGS: [ 37.107944] CS: e033 DS: ES: CR0: 8005003b [ 37.107944] CR2: 7f7f850b0098 CR3: 204a7000 CR4: 2660 [ 37.107944] DR0: DR1: DR2: [ 37.107944] DR3: DR6: 0ff0 DR7: 0400 [ 37.107944] Process kstop/0 (pid: 1509, threadinfo 88001fd1e000, task 88001fcda5d0) [ 37.107944] Stack: [ 37.107944] 88001fd1fd70 ff57a000 8000cf4d2063 e8fe96c0 [ 37.107944] 0 88001fd1fd70 8105ec40 00012ed2d067 8000cf4d2063 -- 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/84fwv9h31l@sauna.l.org
rebuild official kernel with only the modules you need / mapping module names back to CONFIG options
Hi,
while struggling with various kernel bugs[1] this year I had to do a
lot of rebuilds to test patches. I wanted proper source packages that
I can share from my private debian repository and also wanted
-headers, -dbg and -source binary packages. Most importantly I wanted
proper changelog entries. I could not figure out how to do this with
make-kpkg so I thought I'd dig into the real thing, linux-2.6.
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage has a
fairly good guide on how to rebuild kernels. However, it requires one
to either recompile all flavors or to live without -headers [2]. I
don't really understand the build system fully but with a patch[3]
simply running debuild --no-lintian -e DEB_BUILD_OPTIONS=parallel=4
created only
linux-tools-2.6.32_2.6.32-27+lindi.5_amd64.deb
linux-libc-dev_2.6.32-27+lindi.5_amd64.deb
linux-headers-2.6.32-5+lindi.5-all-amd64_2.6.32-27+lindi.5_amd64.deb
linux-headers-2.6.32-5+lindi.5-all_2.6.32-27+lindi.5_amd64.deb
linux-headers-2.6.32-5+lindi.5-common_2.6.32-27+lindi.5_amd64.deb
linux-headers-2.6.32-5+lindi.5-amd64_2.6.32-27+lindi.5_amd64.deb
linux-image-2.6.32-5+lindi.5-amd64-dbg_2.6.32-27+lindi.5_amd64.deb
linux-image-2.6.32-5+lindi.5-amd64_2.6.32-27+lindi.5_amd64.deb
linux-base_2.6.32-27+lindi.5_all.deb
linux-support-2.6.32-5+lindi.5_2.6.32-27+lindi.5_all.deb
which is everything I need but without too much extra. Should I put
this to the wiki and replace the old make -f debian/rules.gen
binary-arch_i386_none_686 binary-indep tricks?
Next problem: The unpacked -dbg package takes almost 1.5 GB of disk
space. The thought of having to run make menuconfig to manually
disable modules that I don't need was scary so I automated the
process. This is somewhat hacky but I thought it might be useful to
someone:
1) http://iki.fi/lindi/linux/find-config-option-for-module-file takes
a path to a kernel module as an argument and prints the CONFIG option
that enables it. It needs to be run directory that contains unpacked
/usr/src/linux-source-2.6.32.tar.bz2:
$ ./find-config-option-for-module-file
/lib/modules/2.6.32-5-amd64/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko
CONFIG_SCSI_DH_RDAC
$ ./find-config-option-for-module-file
/lib/modules/2.6.32-5-amd64/kernel/drivers/memstick/core/mspro_block.ko
CONFIG_MSPRO_BLOCK
2) for i in $(find /lib/modules/2.6.32-5-amd64 -name *.ko); do echo $i
$(./find-config-option-for-module-file $i); done ../module-to-config.map
runs this for all kernel modules and creates mapping from module names
to CONFIG options:
/lib/modules/2.6.32-5-amd64/kernel/drivers/idle/i7300_idle.ko CONFIG_I7300_IDLE
/lib/modules/2.6.32-5-amd64/kernel/drivers/regulator/pcf50633-regulator.ko
CONFIG_REGULATOR_PCF50633
/lib/modules/2.6.32-5-amd64/kernel/drivers/regulator/wm831x-ldo.ko
CONFIG_REGULATOR_WM831X
/lib/modules/2.6.32-5-amd64/kernel/drivers/regulator/wm831x-isink.ko
CONFIG_REGULATOR_WM831X
/lib/modules/2.6.32-5-amd64/kernel/drivers/regulator/mc13783.ko
CONFIG_REGULATOR_MC13783
...
3) cat module-to-config.map | while read file option; do module=$(basename
$file|sed 's/\.ko$//;s/-/_/g'); if [ $(lsmod|awk '{print $1}'|grep
^$module$) = ]; then echo $option; fi; done unnecessary-options.lst
lists all CONFIG options that are not associated with a module that is
currently loaded according to lsmod.
4) for i in $(cat unnecessary-options.lst); do sed -i s/$i=m/# $i is not set/
$(find debian/config -type f); done
edits all the debian/config/** files so that all unnecessary options
are disabled.
= With all this in place I get nice almost like official kernels
that have everything I need but take almost no time to build and
almost no time to copy over network:
38M Nov 9 12:55
linux-image-2.6.32-5+lindi.5-amd64-dbg_2.6.32-27+lindi.5_amd64.deb
3.8M Nov 9 12:55
linux-headers-2.6.32-5+lindi.5-common_2.6.32-27+lindi.5_amd64.deb
3.4M Nov 9 12:55
linux-image-2.6.32-5+lindi.5-amd64_2.6.32-27+lindi.5_amd64.deb
816K Nov 9 12:56 linux-libc-dev_2.6.32-27+lindi.5_amd64.deb
289K Nov 9 12:55
linux-headers-2.6.32-5+lindi.5-amd64_2.6.32-27+lindi.5_amd64.deb
287K Nov 9 12:56 linux-tools-2.6.32_2.6.32-27+lindi.5_amd64.deb
202K Nov 9 12:56 linux-2.6_2.6.32-27+lindi.5_amd64.build
158K Nov 9 12:55 linux-base_2.6.32-27+lindi.5_all.deb
150K Nov 9 12:55 linux-support-2.6.32-5+lindi.5_2.6.32-27+lindi.5_all.deb
134K Nov 9 12:56
linux-headers-2.6.32-5+lindi.5-all-amd64_2.6.32-27+lindi.5_amd64.deb
134K Nov 9 12:56
linux-headers-2.6.32-5+lindi.5-all_2.6.32-27+lindi.5_amd64.deb
17K Nov 9 12:56 linux-2.6_2.6.32-27+lindi.5_amd64.changes
$ debc linux-2.6_2.6.32-27+lindi.5_amd64.changes
linux-image-2.6.32-5+lindi.5-amd64|grep ko$
-rw-r--r-- root/root 84136 2010-11-09 12:55
./lib/modules/2.6.32-5+lindi.5-amd64/kernel/net/bridge/bridge.ko
-rw-r--r-- root/root 6144 2010-11-09 12:55
./lib/modules/2.6.32-5+lindi.5-amd64/kernel/net/802/stp.ko
-rw-r--r-- root/root313968 2010-11-09 12:55
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Angelo Pantano tecn...@advert.it writes: if there is anything else we can provide let us know regards Just in case the problem becomes hard to reproduce you probably want to save the state of the crashed child with xm dump-core DOMAIN FILE If you have lots of private data you obviously can not share that dump but we might be able to guide you to extract the information that is needed. -- 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/841v6uiiwx@sauna.l.org
[PATCH] remove debian/linux-support-* on clean
Hi, it seems that if I debuild the linux-2.6 package multiple times in a row and increment the version number it does not remove the old debian/linux-support-* directories. Is there some reason why it is not removed on clean? If not, would the attached patch be ok? Index: linux-2.6/debian/rules === --- linux-2.6/debian/rules (revision 16542) +++ linux-2.6/debian/rules (working copy) @@ -56,7 +56,7 @@ clean: debian/control dh_testdir - rm -rf $(BUILD_DIR) $(STAMPS_DIR) debian/lib/python/debian_linux/*.pyc debian/linux-headers-* debian/linux-image-* debian/linux-tools-* + rm -rf $(BUILD_DIR) $(STAMPS_DIR) debian/lib/python/debian_linux/*.pyc debian/linux-headers-* debian/linux-image-* debian/linux-tools-* debian/linux-support-* dh_clean binary-indep: $(STAMPS_DIR)/source-base
Bug#602273: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Package: linux-image-2.6.32-5-686-bigmem Version: 2.6.32-26 Severity: normal Steps to reproduce: 1) use 64-bit squeeze as dom0 2) use 32-bit squeeze as domU 3) reboot dom0 Expected results: 3) domU's state is saved to disk and then restored Actual results: 2) domU's state is saved to disk but it hangs after restore More info: 1) Saving and restoring the domU with xm save and xm restore worked at least twice. The problem occurs only if dom0 is rebooted. = Is some clock perhaps visible to the domU and which then gets confused when it is reset and thus goes backwards in time? 2) hypervisor and dom0 information: overlord2:~$ dpkg-query -W xen-hypervisor-4.0-amd64 linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-27 xen-hypervisor-4.0-amd644.0.1-1 overlord2:~$ sudo xm info host : overlord2 release: 2.6.32-5-xen-amd64 version: #1 SMP Wed Oct 20 02:22:18 UTC 2010 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2394 hw_caps: bfebfbff:20100800::0940:e3bd::0001: virt_caps : hvm hvm_directio total_memory : 8189 free_memory: 3 node_to_cpu: node0:0-3 node_to_memory : node0:3 node_to_dma32_mem : node0:3 max_node_id: 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: cc_compiler: gcc version 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Fri Sep 3 15:38:12 UTC 2010 xend_config_format : 4 overlord2:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: 3) domU information: $ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-686-bigmem 2.6.32-26 4) We used sudo xm dump-core squeeze32 squeeze32.dump to save the memory of the stuck domU to disk. 5) We used crash -s --no_panic -e emacs vmlinux-2.6.32-5-686-bigmem squeeze32.dump to analyze the
Bug#602273: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
package linux-image-2.6.32-5-686-bigmem found 602273 2.6.32-27 thanks This issue looks a lot like [Xen-devel] DomU clock jumps forward then freezes after Dom0 reboot http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00498.html and [Xen-devel] Migrated domUs hangs http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00057.html We are going to test the patch from http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html -- 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/84wrou6avn.fsf...@sauna.l.org
Bug#602273: [PATCH] Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
package linux-image-2.6.32-5-686-bigmem
tags 602273 patch
thanks
The patch from
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
seems to help! Please consider applying this to debian.
For completeness, here's the patch from the email archive (probably
messes up whitespace though):
From: Jeremy Fitzhardinge jeremy.fitzhardi...@xx
Date: Mon, 25 Oct 2010 16:53:46 -0700
Subject: [PATCH] x86/pvclock: zero last_value on resume
If the guest domain has been suspend/resumed or migrated, then the
system clock backing the pvclock clocksource may revert to a smaller
value (ie, can be non-monotonic across the migration/save-restore).
Make sure we zero last_value in that case so that the domain
continues to see clock updates.
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@xx
diff --git a/arch/x86/include/asm/pvclock.h b/arch/x86/include/asm/pvclock.h
index cd02f32..6226870 100644
--- a/arch/x86/include/asm/pvclock.h
+++ b/arch/x86/include/asm/pvclock.h
@@ -11,5 +11,6 @@ unsigned long pvclock_tsc_khz(struct pvclock_vcpu_time_info
*src);
void pvclock_read_wallclock(struct pvclock_wall_clock *wall,
struct pvclock_vcpu_time_info *vcpu,
struct timespec *ts);
+void pvclock_resume(void);
#endif /* _ASM_X86_PVCLOCK_H */
diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
index 239427c..a4f07c1 100644
--- a/arch/x86/kernel/pvclock.c
+++ b/arch/x86/kernel/pvclock.c
@@ -120,6 +120,11 @@ unsigned long pvclock_tsc_khz(struct
pvclock_vcpu_time_info *src)
static atomic64_t last_value = ATOMIC64_INIT(0);
+void pvclock_resume(void)
+{
+ atomic64_set(last_value, 0);
+}
+
cycle_t pvclock_clocksource_read(struct pvclock_vcpu_time_info *src)
{
struct pvclock_shadow_time shadow;
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index b2bb5aa..5da5e53 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -426,6 +426,8 @@ void xen_timer_resume(void)
{
int cpu;
+ pvclock_resume();
+
if (xen_clockevent != xen_vcpuop_clockevent)
return;
--
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/84mxpq6480@sauna.l.org
Bug#580889: linux-image-2.6.32-3-amd64: tasks get stuck at pvclock_clocksource_read under xen
Hi,
here's even more info on the issue. This time I discovered a
workaround but don't still know the real root cause of the problem.
I looked at the blkfront_info structure at 0x8800029e8000. In
particular
info-ring.rsp_cons = 96031
info-ring.sring-rsp_prod = 96047
= The ringbuffer contains 16 entries that are done but have not been
handled by the frontend.
If I let i range from 96031 to 96047 and then look at
ring.sring-ring[ i 31].rsp.id
I see the shadow[] indexes of these entries:
14 2 15 3 13 9 1 11 5 16 4 10 12 0 6 7
If I then let j range over these indexes and look at
((struct request*)(((struct
blkfront_info*)0x8800029e8000)-shadow[j].request))-__sector
((struct request*)(((struct
blkfront_info*)0x8800029e8000)-shadow[j].request))-buffer
I get sector numbers and data buffer contents. If I then use
sudo dd if=/dev/xendisk/orbit_root bs=512 skip=$sector count=1 2 /dev/null
|less
for each sector listed above I see that all the data in the buffers
matches what is already in disk.
= All the data has been already written to the disk.
So, where's the interrupt to notify the frontend about this?
The following kernel module calls the interrupt handler directly. It
lets me recover from the stuck state.
#include linux/module.h
#include linux/kernel.h
#include linux/irqreturn.h
static irqreturn_t (*blkif_interrupt_copy)(int irq, void *dev_id) =
(void*)0xa7ba;
static int __init init_crash(void) {
printk(KERN_EMERG crash: calling blkif_interrupt\n);
blkif_interrupt_copy(22, (void*)0x8800029e8000 /* struct blkfront_info*
*/);
printk(KERN_EMERG crash: blkif_interrupt returned\n);
return 0;
}
static void __exit cleanup_crash(void) {
}
MODULE_LICENSE(GPL);
MODULE_DESCRIPTION(crash the system);
MODULE_AUTHOR(Timo Juhani Lindfors timo.lindf...@iki.fi);
module_init(init_crash);
module_exit(cleanup_crash);
--
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/8439sghk1c.fsf...@sauna.l.org
