From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <david+cert@blue-labs.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: nit picking UDF
Date: Wed, 26 Mar 2003 21:40:12 -0800 (PST) [thread overview]
Message-ID: <32826.4.64.238.61.1048743612.squirrel@webmail.osdl.org> (raw)
In-Reply-To: <3E82866A.1000704@blue-labs.org>
> ACPI: (supports S0 S1 S4 S4bios S5)
> You didn't specify the type of your ufs filesystem
>
> mount -t ufs -o
> ufstype=sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
> ufstype=old
> ufs_read_super: bad magic number
> UDF-fs DEBUG fs/udf/lowlevel.c:65:udf_get_last_session:
> CDROMMULTISESSION not supported: rc=-25
> UDF-fs DEBUG fs/udf/super.c:1472:udf_fill_super: Multi-session=0
> UDF-fs DEBUG fs/udf/super.c:460:udf_vrs: Starting at sector 16 (2048 byte
> sectors)
> UDF-fs DEBUG fs/udf/super.c:1208:udf_check_valid: Failed to read byte
> 32768. Assuming open disc. Skipping validity check
> UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block
> 256, tag 18 != 256
> UDF-fs DEBUG fs/udf/super.c:1262:udf_load_partition: No Anchor block found
> UDF-fs: No partition found (1)
> found reiserfs format "3.6" with standard journal
>
> Is all this blurbage necessary? I don't even have a disc in the 'rom drive
> because it causes the kernel to lock up hard on bootup if I do. Right at
> the moment, the 'rom isn't even plugged in.
Is this with 2.5.66?
I also get an oops during boot on 2.5.66 if I have
hdc=ide-scsi
on the kernel boot command line. I have to remove it to boot 2.5.66.
I don't mind editing lilo.conf, but the oops shouldn't be what makes
me edit it.
~Randy
prev parent reply other threads:[~2003-03-27 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 5:04 David Ford
2003-03-27 5:40 ` Randy.Dunlap [this message]
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=32826.4.64.238.61.1048743612.squirrel@webmail.osdl.org \
--to=rddunlap@osdl.org \
--cc=david+cert@blue-labs.org \
--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
all inboxes | Powered by JetHome®