mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Nehal <nehal@canada.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mount hfs on SCSI cdrom = segfault
Date: Wed, 2 Apr 2003 10:49:22 +0000	[thread overview]
Message-ID: <20030402104922.737d2ae9.rddunlap@osdl.org> (raw)
In-Reply-To: <3E8B28B9.5090400@canada.com>


First post said Linux 2.4.20... that's good info.
That info has been deleted from subsequent postings.

Would it make sense for the BUG() message to include a kernel
version number???  I'm wondering since people do omit that data.

~Randy


On Wed, 02 Apr 2003 10:15:21 -0800 Nehal <nehal@canada.com> wrote:

| > i have a hybrid cd (both HFS, ISO9660) , i have two CD drives,
| > one IDE CD-Rom (actima 32x), and one SCSI CD-burner (yamaha 6416)
| > on an advansys cfg-510 ISA scsi card
| >
| > when i try to mount on IDE using hfs with:
| >
| >    mount -v -r -t hfs /dev/hdc /cdrom
| >
| > it works fine, yet when i try on scsi with:
| >
| >    mount -v -r -t hfs /dev/scd0 /cdrom
| >
| > i get a "Segmentation fault" error, no more output given,
| > it also locks the drive, and sometimes i can use the
| > 'eject' command to eject it, sometimes i cant and i gotta reboot
| >
| > note: when i try to mount the cd using regular iso9660 fs, it
| > works perfectly on both cd drives,
| > also i have tried 2 hybrid cd's, both times i have trouble mounting
| > hfs on the scsi drive only
| >
| > Nehal 
| 
| ok i updated firmware of writer from 1.0c to 1.0d with no help,
| but i found when i do 'dmesg' after mounting i get this error:
| ========
| kernel BUG at buffer.c:2518!
| invalid operand: 0000
| CPU:    0
| EIP:    0010:[<c013c329>]    Not tainted
| EFLAGS: 00013206
| eax: 000007ff   ebx: 00000b00   ecx: 00000800   edx: c11ee640
| esi: 00000b00   edi: 00000200   ebp: 00000b00   esp: c3425db4
| ds: 0018   es: 0018   ss: 0018
| Process mount (pid: 514, stackpage=c3425000)
| Stack: c6d0d760 c3425e48 c0257a59 c7f1c574 00000000 00000b00 00000200 
| 00000000
|        c0139f66 00000b00 00000000 00000200 00000000 00000001 c7568400 
| 00000000
|        c013a1e0 00000b00 00000000 00000200 00000000 c019280a 00000b00 
| 00000000
| Call Trace:    [<c0257a59>] [<c0139f66>] [<c013a1e0>] [<c019280a>] 
| [<c019188a>]
|   [<c01925ff>] [<c0285c30>] [<c013cdca>] [<c013e908>] [<c013d64b>] 
| [<c013cd3c>]
|   [<c013d9a1>] [<c014fcf3>] [<c0150020>] [<c014fe69>] [<c0150441>] 
| [<c01090ff>]
| 
| Code: 0f 0b d6 09 9a 2b 33 c0 8d 87 00 fe ff ff 3d 00 0e 00 00 76
|  
| root@Nehal:~#
| ========
| then when i try it again it doesnt give this message, it locks up my drive
| 
| can someone please help debug this problem,
| thx, Nehal

  reply	other threads:[~2003-04-02 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30 19:37 Nehal
2003-04-02 18:15 ` Nehal
2003-04-02 10:49   ` Randy.Dunlap [this message]
2003-04-02 19:01     ` Oliver Feiler
2003-04-02 19:14       ` Nehal
2003-04-02 20:37         ` Oliver Feiler
2003-04-02 21:12           ` Nehal
2003-04-03  8:06             ` Giuliano Pochini
2003-04-03  9:10               ` Nehal
2003-04-03 16:30                 ` Giuliano Pochini
2003-04-03 18:34                   ` Nehal
2003-04-02 19:05     ` Nehal

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=20030402104922.737d2ae9.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nehal@canada.com \
    /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®