From: Marc Lefranc <lefranc.m@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Problem with AHA152X driver in 2.4.19
Date: 03 Aug 2002 19:02:50 +0200 [thread overview]
Message-ID: <p6r65yrlvt1.fsf@free.fr> (raw)
Hi all,
I just built 2.4.19 and checked that the problem that had been
introduced in the aha152x driver between 2.4.19-pre8 and pre10 (bad
initialization due to lost interrupt) had been corrected. However, I
have experienced another problem related to blocking factor.
Using tar without specifying a blocking factor works fine but as soon
as I specify one, tar exits with a segmentation violation immediately
after trying to write to the tape. There is a also a message about a
NULL pointer dereference written to /var/log/messages (see below).
The exact command I used is (taken from a shell script):
tar --create --blocking-factor 96 --file=/dev/st0 --listed-incremental=$JOURNAL --verbose --preserve --one-file-system --atime-preserve $1
The very same script worked flawlessly with 2.4.19-pre8 and before. If
I remove the blocking-factor option, everything is back to normal.
Marc
----------------------------------------------------------------------
Aug 3 17:44:55 socrate kernel: Unable to handle kernel NULL pointer dereference
at virtual address 0000001b
Aug 3 17:44:55 socrate kernel: printing eip:
Aug 3 17:44:55 socrate kernel: c68a21d9
Aug 3 17:44:55 socrate kernel: *pde = 00000000
Aug 3 17:44:55 socrate kernel: Oops: 0000
Aug 3 17:44:55 socrate kernel: CPU: 0
Aug 3 17:44:55 socrate kernel: EIP: 0010:[<c68a21d9>] Not tainted
Aug 3 17:44:55 socrate kernel: EFLAGS: 00010002
Aug 3 17:44:55 socrate kernel: eax: 00000000 ebx: c2575000 ecx: c26e9e30
edx: c1d9a240
Aug 3 17:44:55 socrate kernel: esi: c251c000 edi: 0000000c ebp: c251c000
esp: c2691e4c
Aug 3 17:44:55 socrate kernel: ds: 0018 es: 0018 ss: 0018
Aug 3 17:44:55 socrate kernel: Process tar (pid: 1141, stackpage=c2691000)
Aug 3 17:44:55 socrate kernel: Stack: 00000297 c116fdb4 c2575000 c68a22e3 c2575
000 00000000 00000000 00000000
Aug 3 17:44:55 socrate kernel: c687fab0 c687f517 c2575000 c687fab0 00000
000 c2575000 c116fdb4 c25750b8
Aug 3 17:44:55 socrate kernel: c116fdb4 c688662f c2575000 c2575000 00000
000 c251c000 c5995c00 c116fd60
Aug 3 17:44:55 socrate kernel: Call Trace: [<c68a22e3>] [<c687fab0>] [<c687f
517>] [<c687fab0>] [<c688662f>]
Aug 3 17:44:55 socrate kernel: [<c6885a5f>] [<c6885ab9>] [<c68984cc>] [<c6898
300>] [<c6899ce6>] [<c0132bc8>]
Aug 3 17:44:55 socrate kernel: [<c013266f>] [<c01088b3>]
Aug 3 17:44:55 socrate kernel:
Aug 3 17:44:55 socrate kernel: Code: 0f b6 50 1b 8b 14 95 dc 24 27 c0 2b 82 a0
00 00 00 69 c0 a3
next reply other threads:[~2002-08-03 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-03 17:02 Marc Lefranc [this message]
2002-08-03 22:35 ` Problem with AHA152X driver in 2.4.19 Alan Cox
2002-08-03 23:58 ` Marc Lefranc
2002-08-04 11:33 ` Juergen E. Fischer
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=p6r65yrlvt1.fsf@free.fr \
--to=lefranc.m@free.fr \
--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