Date: Wed, 16 Oct 2002 19:41:20 -0500 (CDT) From: "Jason A. Young" <jyoung@power.doogles.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: HEADSUP! GEOM as default in 5 days... Message-ID: <Pine.LNX.4.44.0210161924220.1363-100000@power.doogles.com> In-Reply-To: <97316.1033416094@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Attempting to mount my Win2K NTFS partition on my laptop after the
introduction of GEOM results in immediate 100% reproduceable panics. I
built GEOM into my kernel the day after it was introduced into CVS, and
none of the commits made since seem to have fixed it.
I apologize for not posting my panic messages earlier, but the machine
ends up in a state where it can't save a core and I haven't got a
null-modem cable for a serial console handy. I decided to go ahead and
transcribe this by hand, so there will likely be typos.
fstab info:
/dev/ad0s1 /win2k ntfs ro,noauto 0 0
/dev/ad0s2b none swap sw 0 0
Trying "mount /win2k" with kern.sync_on_panic and debug.trace_on_panic =
0, dumpon /dev/ad0s2b:
panic: bundirty: buffer 0xcdbb9a24 still on queue 2
Uptime: 41m37s
Dumping 255MB
ata0: resetting devices ..
[indefinite hang]
---
Trying "mount /win2k" and transcribing ddb trace output:
panic: bundirty: buffer 0xcdb93c24 still on queue 2
Debugger("panic")
Stopped at Debugger0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c02ad0a7,c02fb520,c02b31b3,d36fe3fc,1) at Debugger+0x54
panic(c02b31b3,cdb93c24,2,cdb93c24,d36fe444) at panic+0xab
bundirty(cdb93c24,1,c02b3051,471,0) at bundirty+0x31
brelse(cdb93c24,1,c02b3051,34a,cdb93c24) at brelse+0x77d
bwrite(cdb93c24,12,c02b3051,902,0) at bwrite+0x327
getblk(c8be5940,218fdd,0,400,0) at getblk+0x203
breadn(c8be5940,218fdd,0,400,0) at breadn+0x4a
bread(c8be5940,218fdd,0,400,0) at bread+0x4c
ntfs_readntvattr_plain(c8be7100,c8c48900,c8c47800,1e0,0) at
ntfs_readntvattr_plain+0x330
ntfs_readattr_plain(c8be7100,c8c48900,80,0,1e0) at
ntfs_readattr_plain+0x1fb
ntfs_readattr(c8be7100,c8c48900,80,0,1e0) at ntfs_readattr+0x490
ntfs_mountfs(c8be5940,c8c47200,d36fe8d8,c0f07680,b) at ntfs_mountfs+0x4a5
ntfs_mount(c8c47200,c8be9480,bfbffa88,d36febec,c0f07680) at ntfs_mount+0x1ce
vfs_mount(c0f07680,c8a389f0,c8be9480,1,bfbffa88) at vfs_mount+0x82d
mount(c0f07680,d36fed10,c02c7dfe,42d,4) at mount+0xb8
syscall(2f,2f,2f,bfbffd08,bfbffe29) at syscall+0x32e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (21, FreeBSD ELF32, mount), eip = 0x8049897, esp = 0xbfbff5fc,
ebp = 0xbfbffd20 ---
sysctl kern.geom.confxml:
http://power.doogles.com/~jyoung/confxml
sysctl kern.geom.confdot:
http://power.doogles.com/~jyoung/confdot
dmesg:
http://power.doogles.com/~jyoung/dmesg
Again, this is 100% reproduceable, so I'd be happy to gather any other
information that would help.
--
Jason Young, CCIE #8607, MCSE
Sr. Network Technician, WAN Technologies
(314)817-0131
http://www.wantec.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0210161924220.1363-100000>