Bug#673290: nfs-common: rpc.idmapd drashes when given -d
Control: retitle 673290 nfs-common: rpc.idmapd crashes when given -d Control: merge 673290 624843 This has been fixed upstream a while ago: http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=df0f8ab7de8d4664ca3d97d71ff2ef80fae24cb4 rpc.idmapd: Remove no longer supported flags from man page.
Bug#588675: / left as /dev/root with non-initrd kernel
On 12/02/2015 04:30 PM, Elliott Mitchell wrote:
> You're thinking of the wrong bug. #588675 is the bug # for /proc/mounts
> having "/dev/root" listed as the device for the root filesystem. Your
Indeed, I think I confused this with #656333 ("Please ignore rootfs in
df output"), which may be related to this one.
> previous mention indicated you would expect "/dev/sda6" to be there. I'm
> guessing prior to wheezy, when you were using BLK_DEV_IDE_PMAC, you would
> have been seeing "/dev/hda6" listed as the root device?
Again, I'm afraid I don't remember what I've seen prior to wheezy. The
system is running 24x7 but I'll try to boot a pre-wheezy image (or
something with BLK_DEV_IDE_PMAC enabled) the next time this machine is
rebooted and see if the actual disk or /dev/rootfs is displayed.
Christian.
Bug#588675: / left as /dev/root with non-initrd kernel
On 12/02/2015 01:23 PM, Elliott Mitchell wrote: > Could you confirm a few things about what you've seen of bug 588675? > > Did you observe the behavior prior to Debian wheezy/Linux kernel 3.2? > > What type of disk/controller/disk subsystem is on your powerpc system? > > From your mention of /dev/sda6 in bug #588675 it is clear as of Debian > wheezy/Linux kernel 3.2 that the disk/controller plugs into the SCSI > subsystem. I'm pretty sure this is a SCSI subsystem bug, since you've > also seen the behavior I'd like to confirm this has followed the SCSI > subsystem for you as well. Wow, that's an old bug :-) I had to reinstall the PowerBook with Wheezy due to a disk failure and after that I've upgraded from Wheezy to Jessie and the problem is gone now. I can't tell if I've seen this prior to Linux 3.2 kernels. If it helps I could try to boot an older Debian/wheezy live-cd and see if the rootfs comes up twice. The disk controller of this PowerBook G4 is: 0002:20:0d.0 Unassigned class [ff00]: Apple Inc. UniNorth/Intrepid ATA/100 I've used BLK_DEV_IDE_PMAC ages ago, but have switched to PATA_MACIO for a while now. But again, I can't tell when the double "/" entry occured first, I noticed it only at the time of my bug entry (wheezy 7.3). I'm still using a self-compiled kernel but the issue is gone now, at least on this system: $ uname -r; grep root /proc/mounts 4.3.0-11626-g5d50ac7 /dev/root / jfs rw,nodev,relatime 0 0 HTH, Christian.
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
On Wed, 14 Aug 2013 at 21:29, Christian Kujau wrote:
On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote:
It looks like the problem is that jfs was using a cookie value of 2 for
a real directory entry, where NFSv4 expect 2 to represent ... This
patch has so far only been lightly tested.
Hm, a first compile of 3.11-rc5 errors out with:
CC [M] fs/jfs/jfs_dtree.o
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’:
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage
class for function ‘free_index’
[...]
I'll run mrproper and try again...
This did not help, but adding a closing bracket did, in fs/jfs/jfs_dtree.c:354
if (jfs_ip-next_index 3) {
jfs_ip-next_index = 3;
}
-^
This compiled and booted and now I can run find(1) over that whole NFS
share, without any readdir loop messages and with unique inode numbers,
yay!
Tested-by: Christian Kujau li...@nerdbynature.de
Thanks!
Christian.
--
BOFH excuse #36:
dynamic software linking table corrupted
--
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/alpine.deb.2.10.1308150001530.7...@trent.utfs.org
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote: This patch replaces the one I posted yesterday. I like this better since it doesn't require fixing existing on-disk cookies or skipping a position in the in-inode index table. Thanks. Applied to 3.11-rc5 and tested, no more readdir loop messages and with unique inode numbers, great! Tested-by: Christian Kujau li...@nerdbynature.de Thanks for the fix! Christian. -- BOFH excuse #442: Trojan horse ran out of hay -- 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/alpine.deb.2.10.1308151420140.7...@trent.utfs.org
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote: It looks like the problem is that jfs was using a cookie value of 2 for a real directory entry, where NFSv4 expect 2 to represent ... This patch has so far only been lightly tested. Hm, a first compile of 3.11-rc5 errors out with: CC [M] fs/jfs/jfs_dtree.o /usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’: /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage class for function ‘free_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:521:13: error: invalid storage class for function ‘modify_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:546:12: error: invalid storage class for function ‘read_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:927:12: error: invalid storage class for function ‘dtSplitUp’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1327:12: error: invalid storage class for function ‘dtSplitPage’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1639:12: error: invalid storage class for function ‘dtExtendPage’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1872:12: error: invalid storage class for function ‘dtSplitRoot’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2234:12: error: invalid storage class for function ‘dtDeleteUp’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2744:12: error: invalid storage class for function ‘dtRelink’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2915:13: error: invalid storage class for function ‘add_missing_indices’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2982:34: error: invalid storage class for function ‘next_jfs_dirent’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c::12: error: invalid storage class for function ‘dtReadFirst’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3405:12: error: invalid storage class for function ‘dtReadNext’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3581:12: error: invalid storage class for function ‘dtCompare’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3657:12: error: invalid storage class for function ‘ciCompare’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3765:12: error: invalid storage class for function ‘ciGetLeafPrefixKey’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3832:13: error: invalid storage class for function ‘dtGetKey’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3896:13: error: invalid storage class for function ‘dtInsertEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4054:13: error: invalid storage class for function ‘dtMoveEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4255:13: error: invalid storage class for function ‘dtDeleteEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4350:13: error: invalid storage class for function ‘dtTruncateEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4430:13: error: invalid storage class for function ‘dtLinelockFreelist’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4565:1: error: expected declaration or statement at end of input /usr/local/src/linux-git/fs/jfs/jfs_dtree.c: At top level: /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:152:12: warning: ‘dtSplitUp’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:155:12: warning: ‘dtSplitPage’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:158:12: warning: ‘dtExtendPage’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:161:12: warning: ‘dtSplitRoot’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:164:12: warning: ‘dtDeleteUp’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:167:12: warning: ‘dtRelink’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:169:12: warning: ‘dtReadFirst’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:171:12: warning: ‘dtReadNext’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:174:12: warning: ‘dtCompare’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:176:12: warning: ‘ciCompare’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:179:13: warning: ‘dtGetKey’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:182:12: warning: ‘ciGetLeafPrefixKey’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:185:13: warning: ‘dtInsertEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:188:13: warning: ‘dtMoveEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:192:13: warning: ‘dtDeleteEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:194:13: warning:
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
FWIW, this still happens when both client server are running Linux 3.11.0-rc5 (vanilla). $ dpkg -l | grep nfs | cut -c-70 ii libnfsidmap2:amd64 0.25-4amd64 ii nfs-common 1:1.2.6-4 amd64 ii nfs-kernel-server 1:1.2.6-4 amd64 -- 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/alpine.deb.2.10.1308120113360.7...@trent.utfs.org
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
Sorry for the noise, here's another oddity, same setup (client server running 3.11-rc5): $ find /mnt/nfs/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk It's the same file, but gets reported 10 times! Hence the error when trying to tar(1) the directory: $ tar -cf - /mnt/nfs/usr/share/awk/ /dev/null tar: Removing leading `/' from member names tar: /mnt/nfs/usr/share/awk/: Cannot savedir: Too many levels of symbolic links tar: Exiting with failure status due to previous errors On the server: $ find /mnt/disk/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/disk/usr/share/awk/getopt.awk So, is JFS NFS really br0ken and nobody noticed? -- 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/alpine.deb.2.10.1308120122500.7...@trent.utfs.org
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
On Mon, 12 Aug 2013 at 12:29, J. Bruce Fields wrote: It might be interesting to get a network trace (something like tcpdump -s0 -wtmp.pcap; then wireshark tmp.pcap and look at the cookie fields in the readdir calls and replies. I've created #60737[0] to track this issue upstream and attached a pcap to the bug, obtained while running find dir -ls on the client. But I fail to look at the right details in tcpdump/wireshare, I don't see any cookie information... You could also just run strace -egetdents64 -v ls on the server on the exported filesystem, in a problem directory, and see if the offsets are unique. strace returned nothing for getdents64, only getdents. My test filesystems are 256 MB in size, maybe this is too small for getdents64 to be used? All the calls to getdents however return unique offsets, if I did this right: $ strace -egetdents -v ls /mnt/disk_jfs/usr/share/terminfo/q 21 | egrep -o d_off=[0-9]* | sort When running ls (even w/o -l) on the client on that NFS share, this readdir loop message is printed. HTH, Christian. [0] https://bugzilla.kernel.org/show_bug.cgi?id=60737 -- 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/alpine.deb.2.10.1308121257020.7...@trent.utfs.org
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
Interesting stuff. Out of curiosity I just tried this myself, both client server are virtual machines running Debian/stable (3.2.0-4-amd64) and I was able to reproduce this. A test case would be: ## server: $ apt-get install nfs-kernel-server jfsutils $ dd if=/dev/zero bs=1M count=256 /var/test.img $ losetup -f /var/test.img $ mkfs.jfs /dev/loop0 $ mount -t jfs /dev/loop0 /mnt/disk $ tar -C / -cf - usr/share | tar -C /mnt/disk/ -xf - $ tail -1 /etc/exports /mnt/disk 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check) $ service nfs-kernel-server restart ## client $ apt-get install nfs-common $ showmount -e server | tail -1 /mnt/disk 192.168.0.0/24 $ tail -1 /etc/fstab server:/mnt/disk /mnt/nfs nfs rsize=8192,wsize=8192,intr 0 0 $ mount /mnt/nfs $ mount | tail -1 server:/mnt/disk on /mnt/nfs type nfs4 (rw,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.137,minorversion=0,local_lock=none,addr=192.168.0.138) $ tar -cf - /mnt/nfs/ /dev/null tar: Removing leading `/' from member names tar: Removing leading `/' from hard link targets tar: /mnt/nfs/usr/share/perl/5.14.2/Pod/: Cannot savedir: Too many levels of symbolic links tar: Exiting with failure status due to previous errors $ dmesg | tail [ 63.912327] RPC: Registered named UNIX socket transport module. [ 63.913801] RPC: Registered udp transport module. [ 63.914713] RPC: Registered tcp transport module. [ 63.915644] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 63.949485] FS-Cache: Loaded [ 63.972688] FS-Cache: Netfs 'nfs' registered for caching [ 63.993300] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 284.733629] loop: module loaded [ 840.372846] NFS: directory 5.14.2/Pod contains a readdir loop.Please contact your server vendor. The file: Simple has duplicate cookie 18 [ 840.375842] NFS: directory 5.14.2/Pod contains a readdir loop.Please contact your server vendor. The file: Simple has duplicate cookie 18 There are no messages on the server when this happens. The message on the client repeats on every attempt, this Cannot savedir above may be triggering it. -- 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/alpine.deb.2.10.1308092352550.7...@trent.utfs.org
Bug#706660: WARNING: at drivers/cpuidle/driver.c:87 cpuidle_unregister_driver+0x1a/0x3c()
FWIW, this happens on a different machine too: Debian/wheezy, just upgraded from sqeeze, but this time in a VMware virtual machine: [ cut here ] WARNING: at /build/buildd-linux_3.2.41-2+deb7u2-i386-G4jjsr/linux-3.2.41/drivers/cpuidle/driver.c:87 cpuidle_unregister_driver+0x1a/0x3c() Hardware name: VMware Virtual Platform invalid cpuidle_unregister_driver(acpi_idle) Modules linked in: cachefiles dlm configfs nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop ecryptfs sg vmwgfx snd_timer snd ttm soundcore vmw_balloon drm mperf libata i2c_core processor(-) power_supply thermal_sys ext4 jbd2 mbcache crc16 btrfs crc32c libcrc32c zlib_deflate sd_mod crc_t10dif evdev mptsas scsi_transport_sas mptscsih e1000 scsi_mod mptbase [last unloaded: psmouse] Pid: 2884, comm: rmmod Not tainted 3.2.0-4-686-pae #1 Debian 3.2.41-2+deb7u2 Call Trace: [c10383c4] ? warn_slowpath_common+0x68/0x79 [c120c20a] ? cpuidle_unregister_driver+0x1a/0x3c [c103843d] ? warn_slowpath_fmt+0x29/0x2d [c120c20a] ? cpuidle_unregister_driver+0x1a/0x3c [f841357a] ? acpi_processor_exit+0x57/0xadd [processor] [f84102e7] ? acpi_processor_hotplug_notify+0x9a/0x9a [processor] [c105fe2d] ? sys_delete_module+0x19f/0x217 [c10d0072] ? cn_printf+0x31/0x7f [c10cd846] ? fput+0x148/0x160 [c10df33b] ? mntput_no_expire+0x1b/0xb0 [c10cb5e8] ? filp_close+0x52/0x58 [c12c6e1f] ? sysenter_do_call+0x12/0x28 ---[ end trace 81248210d0937111 ]--- -- 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/alpine.deb.2.10.1305170158370.13...@trent.utfs.org
Bug#706660: WARNING: at drivers/cpuidle/driver.c:87 cpuidle_unregister_driver+0x1a/0x3c()
Package: src:linux Version: 3.2.41-2 Severity: normal Dear Maintainer, after upgrading from squeeze to wheezy in this VirtualBox VM, the following is printed during every bootup: [ cut here ] WARNING: at /build/buildd-linux_3.2.41-2-i386-BfAj4s/linux-3.2.41/drivers/cpuidle/driver.c:87 cpuidle_unregister_driver+0x1a/0x3c() Hardware name: VirtualBox invalid cpuidle_unregister_driver(acpi_idle) Modules linked in: nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc jfs xfs sr_mod power_supply cdrom psmouse evdev pcspkr processor(-) thermal_sys button iTCO_wdt iTCO_vendor_support vboxguest(O) i2c_piix4 i2c_core rng_core virtio_net ext4 crc16 jbd2 mbcache sd_mod crc_t10dif ahci libahci libata scsi_mod virtio_pci virtio_ring virtio [last unloaded: serio_raw] Pid: 3475, comm: rmmod Tainted: G O 3.2.0-4-686-pae #1 Debian 3.2.41-2 Call Trace: [c10383c4] ? warn_slowpath_common+0x68/0x79 [c120c1e2] ? cpuidle_unregister_driver+0x1a/0x3c [c103843d] ? warn_slowpath_fmt+0x29/0x2d [c120c1e2] ? cpuidle_unregister_driver+0x1a/0x3c [e089e57a] ? acpi_processor_exit+0x57/0xadd [processor] [e089b2e7] ? acpi_processor_hotplug_notify+0x9a/0x9a [processor] [c105fe29] ? sys_delete_module+0x19f/0x217 [c10d0072] ? cn_printf+0x51/0x7f [c10cd826] ? fput+0x148/0x160 [c10df31b] ? mntput_no_expire+0x1b/0xb0 [c10cb5c8] ? filp_close+0x52/0x58 [c12c6d9f] ? sysenter_do_call+0x12/0x28 ---[ end trace 2e4c1b1b2be01e81 ]--- This is proably triggered by the Virtualbox modules (package virtualbox-guest-dkms and virtualbox-guest-utils (version: 4.1.18-dfsg-2+deb7u1). A similar (same?) error was reported on the xen-devl mailing-list back in 2011: http://lists.xen.org/archives/html/xen-devel/2011-08/msg01275.html Although Debian's 3.2.0-4-686-pae kernel is XEN enabled, I'm not using Xen. This installation is a VirtualBox guest, though. -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=9e4ac2d3-4f1b-496b-b5be-527de71c7217 ro fb=false ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [3.298948] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.302460] sd 3:0:0:0: [sdc] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [3.304626] sd 3:0:0:0: [sdc] Write Protect is off [3.305711] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [3.305735] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.306137] sdb: sdb1 sdb2 [3.309456] sd 1:0:0:0: [sdb] Attached SCSI disk [3.312757] sdc: unknown partition table [3.314306] sd 3:0:0:0: [sdc] Attached SCSI disk [3.321716] sda: sda1 sda2 [3.323103] sd 0:0:0:0: [sda] Attached SCSI disk [3.727938] PM: Starting manual resume from disk [3.729432] PM: Hibernation image partition 8:2 present [3.729434] PM: Looking for hibernation image. [3.729637] PM: Image not found (code -22) [3.729639] PM: Hibernation image not present or could not be loaded. [3.783630] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [5.131260] udevd[298]: starting version 175 [5.513926] intel_rng: FWH not detected [5.516499] piix4_smbus :00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [5.545442] iTCO_vendor_support: vendor-support=0 [5.24] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.575407] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x8060) [5.577594] iTCO_wdt: timeout value out of range, using 30 [5.590554] input: Unspecified device as /devices/virtual/input/input1 [5.600891] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [5.608094] ACPI: Power Button [PWRF] [5.610417] vboxguest: major 0, IRQ 20, I/O port d020, MMIO at f000 (size 0x40) [5.620527] vboxguest: Successfully loaded version 4.1.18_Debian (interface 0x00010004) [5.625830] input: PC Speaker as /devices/platform/pcspkr/input/input3 [5.637424] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [5.654012] input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input4 [5.694389] leds_ss4200: no LED devices found [5.723203] ACPI: Sleep Button [SLPF] [5.749446] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input5 [5.789780] sr0: scsi3-mmc drive: 32x/32x xa/form2 tray [5.791168] cdrom: Uniform CD-ROM driver Revision: 3.20 [5.807517] sr 2:0:0:0: Attached scsi CD-ROM sr0 [5.866510] ACPI: AC Adapter [AC] (on-line) [5.887126] parport_pc 00:04: reported by Plug and Play ACPI [5.920904] sd 0:0:0:0: Attached scsi generic sg0 type 0 [5.924664] sd 1:0:0:0: Attached scsi generic
Bug#540486: linux-image-powerpc: please enable CONFIG_EFI_PARTITION
Package: linux-image-powerpc Version: 2.6.26+17+lenny1 Severity: important Please enable CONFIG_EFI_PARTITION in the kernel config. This has been discussed and fixed for i386 and amd64 in #281905 (for 2.6.8, 2.6.10) but linux-image-powerpc still ships with CONFIG_EFI_PARTITION unset: $ grep EFI_PARTITION /boot/config-2.6.26-2-powerpc # CONFIG_EFI_PARTITION is not set With harddisks getting bigger and bigger, CONFIG_EFI_PARTITION gets more and more important. Please consider enabling it. Thanks, Christian. -- BOFH excuse #150: Arcserve crashed the server again. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
Just for the record: gcc-4.3 still fails on a current vanilla kernel with the same message: http://nerdbynature.de/bits/2.6.25-git/ (gcc 4.3-20080227-1 with today's 2.6.25-git) Adding -fno-tree-scev-cprop to KBUILD_CFLAGS did not succeed, the build fails instantly, please see make_fno-tree-scev-cprop.log. There are reports on the net to set CONFIG_GCC_4003_SUPPORT, however this option is not mainline (nor did I find any patches adding this option). Thanks, Christian. -- BOFH excuse #269: Melting hard drives -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299875: ppp: out-of-memory 30min after LCP terminated by peer
hi again, sorry for the delay, but the bug triggers only when the remote peer disconnects me - and it does it only once a day. Marco d'Itri wrote: reassign 299875 kernel retitle 299875 CAN-2005-0384: Remote Linux DoS on ppp servers tag 299875 patch security yes, it really looks like a pppd DoS, but as i suspected, things are a bit different here: - pppoe receives PADT from peer - pppd in turn gets LCP terminated by peer - pppd tries to re-establish the connection, says Starting link in the logfile [1] and then just hangs. i have to re-adjust the subject line, because OOM was triggered by something else, *because* pppd did not succeed to re-establish the connection. but oom is totally unrelated here (and fixed on my system). but still: pppd hangs and is only killable via kill -9. but it is *NOT* a cpu hog as stated by Paul Mackerras. i've strace'd the hanging pppd: http://nerdbynature.de/bits/sheep/2.6.11/oom/pppd_2.6.11.4.log (the very first line is the only one i get from just doing strace -p `pidof pppd`, then i did killall pppd, then with -9) to summarise: i've noticed the pppd behaviour first with 2.6.11, then with 2.6.11-rc5-bk2, now with 2.6.11.3 and 2.6.11.4. downgrading to ppp_2.4.2+20040428-6_i386 solves it. thank you for your time, Christian. PS: i'll close the issue i reported on lkml: http://www.ussg.iu.edu/hypermail/linux/kernel/0503.2/0316.html [1] http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt -- BOFH excuse #139: UBNC (user brain not connected) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299875: ppp: out-of-memory 30min after LCP terminated by peer
Justin Pryzby wrote: I assume that you have seen this: http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11.4 yes i have*now*. obviously this was a security issue (CAN-2005-0384) and i *guess* that's why the issue was not discussed in public. what pity and what a waste of time in tracking this down when the security guys are already on it and release a fix out-of-the-box. If not .. tag patch:) In less than 100 lines, even! yes, 2.6.11.4 is out including this fix. Marco d'Itri commented: Paul Mackerras says that this bug affects all kernels (2.4 and 2.6) and can be easily triggered remotely, but is only a CPU DoS. --^ actually my problem was *not* about a CPU DoS but a (out-of)memory DoS. cpu was spinning normally. and i was not able to tell the exact kernel version when the problem started - instead my research led to the assumption that the new ppp package was to blame. well, i'm already compiling 2.6.11.4, i'll see what it gives. thank you for your concern, Christian. -- BOFH excuse #188: ..disk or the processor is on fire. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
oops with 2.6.8-rc4 (ipv6 / nfs / 3c59x related?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi list, yesterday i encounterd several oopses with my server. the subject of this mail is just plain saying that it is all 2.6.8-rc4's fault. the reality however turned out to be much more complex and confusing so i try to recapitulate in a chronologically way: - - the box (debian/unstable, i368 [PentiumIII] ) was running for 28 days with 2.6.7-ck5 (no other patches but the -ck5 [1] ) - - ipv6 transition interface was down again, i had to start the freenet6 client again, to setup sit1. then i tried from a nfs-client to use this interface by issuing tracepath6 comamnds when i noticed my nfs-server (the pIII-box) was dead. i could not catch the oops, had no digicam at hand / was too lazy to write, i'll tell later on that. - - rebooted same kernel, tried again locally (setup sit1, tracepath6 to some ipv6 host) - the box oopsed and locked up. (SYSRQ-s|u did not succeed, only SYSRQ-b...rebooting) - - ok, 2.6.8-rc4 is out anyway, time to update. compiled, booted, setup sit1, tracepath6- the box oopsed and locked up. - - am i too dumb to boot my self-built kernels? perhaps, so i used kernel-image-2.6.7-1-686 from debian. again: i set up sit1, tracepath6 to some host - ha! it did not lock up instantly, but tracepath6 gave not results, so i CTRL-C'ed it and received a message: KERNEL: assertion (!atomic_read(sk-sk_wmem_alloc)) failed at net/ipv4/af_inet.c (155) everytime i CTRL-C'ed i received this message. and 2.6.7-1-686 was still alivefor a few minutes. when i used my nfs-client to issue tracepath6 commands, the box oopsed but this time the oops mad it to the disk [2]. then it locked up, and the screen filled with traces. - - today i got a camera so i was able to catch the oops [3] + [4]. now the confusing part: i rememberd the oopses from the 2.6.8-rc4: they were the same as [3] is showing, so it seemed to be related to the 3c59x module. i even suspected (sudden) harware problems so i changed the NIC to another 3c59x card. hm, the 3c59x oopses were gone indeed (somehow i still doubt the card is damaged), but the nfs related oopses occured with 2.6.7-1-i686 *and* 2.6.8-rc4 [4] + [5]. - - so, the nfs-related oopses were 100% reproducable when i used the nfs-shares on the client (both 2.6.7-1-686 and 2.6.8-rc4) - - somehow ipv6 was always involved, i could not trigger the oops when ipv6 was not loaded/sit1 was not setup. - - vanilla 2.6.7 seems not affected, 2.6.8-rc[1..3] are also ok (2.6.8-rc3 is running atm). i hope i did not mix something up here. yes, maybe this report has to split up into one ipv6 and one nfs report. i hope [3], [4], [5] are helpful to find out what the oops was all about. (the Tainted flags in the 2.6.7-1-686 kernels came from loop-aes modules: loop: no version for struct_module found: kernel tainted.) sorry for the crossposting (please delete rcpts if not applicable) Thank you for your commments. Christian. [1] http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/patch-2.6.7-ck5.bz2 [2] http://nerdbynature.de/bits/sheep/2.6.8/2.6.7-1-686.oops [3] http://nerdbynature.de/bits/sheep/2.6.8/2.6.7-1-686.oops_3c59x.jpg [4] http://nerdbynature.de/bits/sheep/2.6.8/2.6.7-1-686.oops_nfs.jpg [5] http://nerdbynature.de/bits/sheep/2.6.8/2.6.8-rc4.oops_nfs.jpg everything: http://nerdbynature.de/bits/sheep/2.6.8/ - -- BOFH excuse #78: Yes, yes, its called a design limitation -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBGnOd+A7rjkF8z0wRAqK2AJ96DxaNdgXBRbDJvhZUNChmh9kDugCdFyIa n5wJaT5zXePq7xakS2SuPsA= =SkFV -END PGP SIGNATURE-
