[parisc-linux] Yet another tar-triggered problem?
Nahkola Mikko
mnahkola@trinms01.ntc.nokia.com
Tue, 4 Feb 2003 10:55:02 +0200
On Mon, Feb 03, 2003 at 10:30:57AM -0700, ext Grant Grundler wrote:
> On Mon, Feb 03, 2003 at 05:44:50PM +0200, Nahkola Mikko wrote:
> > ... the 70096's scrollback was full of something that looks like
> > a hex dump, and then a HPMC at the end.
> Likely a problem with st or scsi driver.
> Not many people are using tape drives so we don't get much
> feedback on that.
Well, duh ... tapes are fun. Wonder why no one seems interested in them
nowadays.
> > Is anyone interested in the hex dump?
> Well, TBH, I'd be more interested in one from a 2.4.20 kernel.
> Too much code has changed since 2.4.18.
OK, I'll see if I can reproduce this on 2.4.20.
It would be nice to get a newer kernel to work in real use too... funny
that KDE should lock up though, that's not a symptom that I'd expect to
see.
> > r00-03 00000000 10300010 1010d4e8 ffffffff
> ...
> > IASQ: 00000000 00000000 IAOQ: 1024a2d0 1024a2d4
>
> Can you look up (IOAQ) 1024a2d0 and (GR02) 1010d4e8
> in the matching System.map?
> I'm curious where it died.
Well, 1010d4e8 seems to be in the middle of something...
1010d1c0 t pcxl_proc_info
1010d30c t .L1066
1010d36c T inb
............. lots of other "t .L???"s and an occasional "T inw"
1010d480 t .L708
1010d484 T inl
1010d4ec t .L712
1024a2d0 seems much more readable here... but then again the stuff is
much further apart.
1024a2ac t dino_in32
1024a2e4 t dino_out8
1024a320 t dino_out16
> Though with HPMCs, it's likely to be a bug in some other code path.
Indeed, and on HP-UX I've seen occasional HPMCs with slightly-broken
disks, for example...
--
Mikko Nahkola <mikko.nahkola@nokia.com>
Tre-IN sysadmin <mnahkola@trein.ntc.nokia.com>