Hi,

I have a somewhat weird hang problem when booting all recent kernel
versions including 2.6.28: When I boot my system and let grub start the
kernel after a 5 second timeout, the system will hang after registering
the io schedulers (see below). However, when I choose the default grub
entry manually by pressing ENTER in the menu, the kernel does not hang
and continues the normal booting process.

Below, you can find the place of the hang and an excerpt of the messages
that follow on a normal boot as well as some system information.

Thanks for your time on this problem.

Best regards
Kai

# dmesg
...
[ 0.309379] io scheduler noop registered
[ 0.309473] io scheduler anticipatory registered
[ 0.309569] io scheduler deadline registered
[ 0.309679] io scheduler cfq registered (default)

Hang happens here.

Hi!

Hi,

Is there a way to see q->qstats.requeues statistics
(dev_requeue_skb()) ? I tried tc tool but it does not
show it...

Don.

I get the following error message at bootup.
[ 1.839948] ebt_ulog: out of memory trying to call netlink_kernel_create

The system certainly is not out of memory, because it works fine, otherwise.

The kernel is a 2.6.28-rc9 on an x86_64 architecture.

--
Greetings, Michael.

All,

On the mdraid list, there was a recent thread about using raid
functionality to detect / repair silent corruption.

The issues brought up were that a lot of silent data corruption occurs
when cables, controllers, power supplies, ram, cache, etc. goes bad.

It made me think about another option for detecting silent corruption
I have not seen discussed, but maybe I missed it.

Aiui, the ATA spec allows for the reading of a long sector as well as
the normal 512 byte sector. When you get a long sector you also get
the CRC (or whatever checksum data there is on the disk that allows
the drive itself to detect media errors).

I don't have any idea how easy or hard it would be to do, but I would
like to see the entire block subsystem enhanced to optionally allow
long sector reads to be used in a "paranoid" fashion.

Effectively it would be:

1) Read long sector from drive: verify CRC in kernel. This tests
most everything on the i/o path.

Hi!

in-tree documentation says that default for ext3 is errors=remount-ro,
and that's sensible, but I see errors=continue on my disks, due to
superblock settings. (Maybe documentation should mention that?)

I don't know where errors=continue came from (and I think its
dangerous); mkfs does not seem to have such option, nor can I see
anything in /etc/mke2fs.conf...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Feiern Sie ein Winterfest und machen Sie Ihr Geld winterfest - meine Freundin zeigt Ihnen, wie:

http://www.Geld-Winterfest.com/

what about some "make modules_install_compressed" instead ?

as i have run out of diskspace quite often when installing test kernels, i
think we really need a feature like this.

i`d also favour the makefile approach.
why another kconfig option?

jan`s patch looks clean and simple, but i think it`s a little bit
intrusive...

regards
roland

ps:
i`d use gzip without "-9" as this gives very little space savings. it mostly
burns cpu and slows things down too much.
( see
http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/080/8051/8051f1... )

On Friday 2008-12-26 20:48, Sam Ravnborg wrote: