Displaying 20 results from an estimated 100000 matches similar to: "[BUG 2.6.15-rc5] EXT3-fs error and soft lockup detected"
2008 Aug 31
0
crash at shutdown
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:
2007 Jul 17
1
large ext3 filesystem consistantly locking itself read-only
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
2007 Apr 23
1
Compact Flash, EXT3, and IDE - a bad idea?
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:
2007 Feb 08
3
Kernel Panic-not syncing VFS: Unable to mount root fs on unknown-block(8, 1)
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
2006 Aug 29
2
Ext3 emergency recovery
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
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
2003 Mar 22
0
ext3 oops with 2.4.20
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
2005 Feb 16
0
mke2fs options for very large filesystems (and corruption!)
[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
2008 Feb 27
3
domU on v3.2 is not booting
hi all,
I installed v3.2 from source and now dom0 is booting well. But when I
tried to start domU it shows the following error message and seems
hanging.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT3 FS on hda1, internal journal
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
2005 Jan 15
1
Guide to stripping Centos 3
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
2008 Nov 25
3
IRQ Problems with kernel 2.6.18.8 when PCI passthrough to PVM''s
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
2008 Nov 25
3
IRQ Problems with kernel 2.6.18.8 when PCI passthrough to PVM''s
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
2006 May 26
1
[PATCH - 2.6.17-rc5] ext3: Fix missed mutex unlock - unroll
Hi,
I believe the following patch in the GIT - 2.6.17-rc5 is not correct:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c
It is the second of the two patches contributed by Leonid Ananiev. This
one incorrectly adds the super block unlocking in the error path, though.
As we can see in the function ext3_group_add() the
2001 Oct 11
4
ext3 on 2.4.10-ac11 w/ext3-2.4-0.9.12-2410ac11
I am trying to compile 2.4.10-ac11 w/ the ext3-2.4-0.9.12-2410ac11
patch. I'm getting unresolved symbols w/ ext3 module:
cd /lib/modules/2.4.10-ac11; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.10-ac11;
fi
depmod: *** Unresolved symbols in
2008 Apr 30
1
btrfs v0.14: kernel BUG at /home/trey/btrfs-0.14/volumes.c:1453
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 *
2006 Dec 14
1
xen-3.0.4-rc1: undefined reference to `remove_siblinginfo''
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.