similar to: [BUG 2.6.15-rc5] EXT3-fs error and soft lockup detected

My kernel crashes every time I shut down dom0 This crash was not happening before I installed the Xen hypervisor Any ideas? (XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi at debian.org) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=9600,8n1 console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods:

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

Hi I just tried to install Xen (3.0.4) from source. The Installation process finished without any errors. Then after booting the XEN-Image (without initrd) I got a Kernel Panic. My machine said it was unuable to mount root fs from Sda1 or unknown-block(0,0) After some research on google, I built the SCSI and SATA drivers in the XEN-kernel and now this kernel Panic occurs: Kernel Panic-not

[sorry if this isn't threaded right... I just subscribed] Theodore Ts'o wrote: > > There are two reasons for the reserve. One is to reserve space on the > partition containing /var and /etc for log files, etc. The other is > to avoid the performance degredation when the last 5-10% of the disk > space is used. (BSD actually reserves 10% by default.) Given that > the

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

Hi All, I'm currently running an embedded linux system (arm) with a CF card mounted as EXT3. I'll copy some system details below... Anyway, I'm getting some drive errors and I'm wondering if they're due to bad/old drivers, something with EXT3 and CF latency, or something else entirely. These are the errors: hda: write_intr error1: nr_sectors=1, stat=0x51 hda:

Hi, Kernel crash when i tried to mount btrfs: -- Machine: HP Proliant DL 380 G4 -- Ubuntu 8.04 Hardy Server root at btrfs:/home/trey# uname -a Linux btrfs 2.6.24-16-server #1 SMP Thu Apr 10 13:15:38 UTC 2008 x86_64 GNU/Linux -- root at btrfs:/home/trey# fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 *

Hello, On my x86_64 box, when compiling the xen-3.0.4-rc1, if CONFIG_HOTPLUG_CPU is not set it produces an undefined reference to ''remove_siblinginfo'' that is used in arch/x86_64/kernel/smpboot.c drivers/built-in.o: In function `__cpu_up'': (.text+0x54c10): undefined reference to `remove_siblinginfo'' If CONFIG_HOTPLUG_CPU is set the compilation works fine.

I have a damaged Ext3 filesystem which fsck has not been able to recover. If I try to mount it, I get a message like this in dmesg: EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already cleared for block 2370866 If I try fsck on it, I get a series of messages like this: Inode bitmap for group 0 is not in group. (block 0) Relocate<y>? Up to group 95. Some say

Wanted to pass this error by you and get your feedback ... I tried building a debug kernel with spinlock related debug info. The tree was pulled when the Xen-305 first rc was announced (and has not been updated since) make -C /root/src/mercurial/xen-3.0.5-testing.hg/linux-2.6.18-xen O=/root/src/mercurial/xen-3.0.5-testing.hg/build-linux-2.6.18-xen_x86_64 vmlinuz Using

Hi... I have a Dell Latitute with an ATA/ATAPI-5 T13 1321D and it would seem that my disk access is extremely slow. I have the latest updated kernel from RedHat 8.0 kernel 2.4.18-27.8.0. Somehow I think it is related to the UDMA stuff (shows my level of understanding). I have run hdparm and although I think I should at least udma level 5, I have at most udma2 listed. Is this a kernel

Hi folks, Backing up a host as noted below im getting over and over again the same issue on actual kernel, details: - Backup host has a pci/usb2.0 card, with a 250gb usb 2.0 disk attached, - Celeron 900 family - Remote host, local console from boot linux rescue: # dd if=/dev/hda conv=sync,noerror | ssh -c blowfish root at 192.168.0.6 "dd of=/media/backup/vol-hda.raw.img" - Backup

I responded to a post in the Dell poweredge mailing list earlier today. My answer was off the top of my head, with a bit of experimentation. The content may be useful in the Cenyos context as well to admin's looking to strip the size of an install to the bare bones. Comment welcomed. Can anyone see any packages which I have missed? -- Russ Herrold ---------- Forwarded message