Re: EXT4-fs error, kernel BUG

also sprach martin f krafft [2014-08-05 16:15 +0300]: > > It's possible that this was caused by a memory corruption, but it > > wouldn't have been high on my suspect list. Still, if this is > > a new machine, it might not be a bad idea to run memtest86+ for > &g

Re: EXT4-fs error, kernel BUG

also sprach Theodore Ts'o [2014-08-05 14:51 +0200]: > One likely cause of this issue is that the hardware hiccuped on > a read, and returned garbage, which is what triggered the "EXT4-fs > error" message (which is really a report of a detect file system > inconsistency). A common cause of this is

Re: Disabling physical RAM regions for testing

also sprach Austin S Hemmelgarn [2014-08-05 14:26 +0200]: > The e820 is probably not what you want to be looking at. I would > suggest looking into memory hot-plug/hot-remove support, IIRC the > hot-remove support allows you to bring a bank offline. Oh, good pointer, yeah, that would do and allo

Disabling physical RAM regions for testing

Hello, A NAS seems to be having RAM problems, leading me to want to swap out DIMMs until I found the offender; I'd rather not go to the rack every time I need to make a change. Is there a way to declare a DIMM unavailable to Linux with a boot parameter? There is mem= and memmap= but i cannot figu

EXT4-fs error, kernel BUG

Dear kernel people, Yesterday, I encountered something weird on one of our NAS machines: Aug 4 20:09:40 julia kernel: [342873.007709] EXT4-fs error (device dm-6): ext4_ext_check_inode:481: inode #30414321: comm du: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max

Re: Monthly md check == hung machine; how do I debug?

also sprach Robin Lee Powell <[EMAIL PROTECTED]> [2008.02.04.1021 +1300]: > /usr/share/mdadm/checkarray --cron --all --quiet FYI: http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=blob;f=debian/checkarray It basically does echo check > /sys/block/$array/md/sync_action for all arrays. -- ma

Re: what does this mean: "kernel: 7.0.0.1:53 L=79 S=0x00 I=39869 F=0x4000 T=64"

also sprach Alexander E. Patrakov <[EMAIL PROTECTED]> [2007.08.23.1847 +0200]: > However, the style does look similar to a message in ipw2100.c: > > IPW_DEBUG_TX("TX%d V=%p P=%04X T=%04X L=%d\n", i, > &txq->drv[i], > (u32) (txq->nic + i * sizeof(struct ipw2100_bd)), >

Re: what does this mean: "kernel: 7.0.0.1:53 L=79 S=0x00 I=39869 F=0x4000 T=64"

also sprach Alexander E. Patrakov <[EMAIL PROTECTED]> [2007.08.23.1730 +0200]: >> I am staring at this log message: >> kernel: 7.0.0.1:53 L=79 S=0x00 I=39869 F=0x4000 T=64 >> and I cannot figure out what it's trying to tell me. Could someone >> please enlighten me? > > Looks like some DNS packet

what does this mean: "kernel: 7.0.0.1:53 L=79 S=0x00 I=39869 F=0x4000 T=64"

I am staring at this log message: kernel: 7.0.0.1:53 L=79 S=0x00 I=39869 F=0x4000 T=64 and I cannot figure out what it's trying to tell me. Could someone please enlighten me? -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL

Re: swsusp logic error?

also sprach Pavel Machek > > > Could you, please, verify that you don't need to load any > > > modules from initrd for your swap partition to work? It won't > > > work if you do. > > > > this makes perfect sense to me when you talk about resuming. > > does it also apply to suspending? > > As ke

Re: swsusp logic error?

also sprach Rafael J. Wysocki <[EMAIL PROTECTED]> [2005.02.28.1533 +0100]: > Could you, please, verify that you don't need to load any modules > from initrd for your swap partition to work? It won't work if you do. this makes perfect sense to me when you talk about resuming. does it also apply to

Re: swsusp logic error?

also sprach martin f krafft <[EMAIL PROTECTED]> [2005.02.27.1843 +0100]: > Please check my first post, if you have the time: > > http://marc.theaimsgroup.com/?l=linux-kernel&m=110789536921510&w=2 There is also http://thread.gmane.org/gmane.linux.acpi.devel/12540 w

Re: swsusp logic error?

also sprach Pavel Machek <[EMAIL PROTECTED]> [2005.02.27.1804 +0100]: > Ugh, too late, I already forgot what went wrong for you. Anyway > try reading Documentation/power/swsusp.txt and/or going to > 2.6.11-rc4. If that does not help, debug with printk :-). I already did the first two. I will try 2

Re: swsusp logic error?

Sorry for the late reply, I've been strung up with work. I tried your suggestion on another machine, with a vanilla 2.6.10 kernel and a single swap device, twice the size of the physical RAM; I get exactly the same result. The swap device cannot be found. What to try next? -- martin;

swsusp logic error?

I am trying to get swsusp working on a 2.6.10 Debian kernel (2.6.10-1-686, custom compile, enabling only CONFIG_SOFTWARE_SUSPEND and leaving CONFIG_PM_STD_PARTITION empty) on this Sony Vaio Z1RSP Centrino 1.7 Pentium M laptop... without much success. Whenever I enter swsusp mode, the kernel reports