From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Annoying kernel behaviour
Date: Fri, 22 Jun 2001 19:24:16 -0600 [thread overview]
Message-ID: <3B33EFC0.D9C930D5@bigfoot.com> (raw)
I upgraded a fileserver to 2.4.5 because of the RAID support (the 0.90
patch I grabbed did not apply cleanly to 2.2.19, despite it being a fresh
copy). Besides a nice speed increase (the EEPro now pumps 10 megs a second,
instead of 2 or 3), there is a problem with the video4linux in it. The box
has a bttv card hooked up to a camera. Under 2.2.19, Apache had mod_video
installed, which would produce a jpeg of the composite in on the card (a
cheapy CCD camera is hooked up). Upon insmoding:
Module Size Used by
bttv 55184 0 (unused)
videodev 4864 2 [bttv]
i2c-algo-bit 7712 1 [bttv]
i2c-dev 3904 0 (unused)
i2c-core 12656 0 [bttv i2c-algo-bit i2c-dev]
and accesing mod_video, the box locked up hard (not even sysrq worked). And
when I rebooted, I found that some files is /etc were eaten -- even though
that partition is mounted with the sync option, and even though it'd had a
good 2-5 seconds the write the ~10k data file.
So why does bttv lock the box, and why does sync not sync? I don't feel
like converting ~80gb to some other FS than ext2 just yet.
PS: I can't give an Oops because the DPMS mode on the console was on, and it
won't return when it locks up (perhaps turn on monitor as part of Oops
handling?). Assuming there even was an oops.
PPS: Please CC me since I'm not on the list.
--
www.kuro5hin.org -- technology and culture, from the trenches.
next reply other threads:[~2001-06-23 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 1:24 Dylan Griffiths [this message]
[not found] ` <9h0r6s$fe7$1@ns1.clouddancer.com>
2001-06-23 9:05 ` Annoying kernel behaviour Colonel
2001-06-24 10:37 ` Dylan Griffiths
[not found] ` <9h4ft5$1ku$1@ns1.clouddancer.com>
2001-06-24 11:46 ` Colonel
2001-06-24 19:46 ` Dylan Griffiths
[not found] ` <9h5gbc$3mb$1@ns1.clouddancer.com>
2001-06-25 3:22 ` Colonel
2001-06-25 7:41 ` Gerd Knorr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B33EFC0.D9C930D5@bigfoot.com \
--to=dylan_g@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox