Re: cvs commit: src/sys/compat/linux linux_stats.c
At Wed, 1 Nov 2000 22:08:26 -0800 (PST), Marcel Moolenaar wrote: marcel 2000/11/01 22:08:26 PST Modified files: sys/compat/linux linux_stats.c Log: Fix linux_ustat syscall. We only have cdevs now, so looking for a block device isn't that useful anymore. Reported by: Wesley Morgan [EMAIL PROTECTED] Submitted by: gallatin Acknowledged by: phk After this change, it panics when you perform stat against a linux block device node. Actually, emulators/vmware2 port creates some block device nodes in /compat/linux/dev, so all the vmware2 users still have ones installed. And when they hit `ls /compat/linux/dev' or `pkg_delete vmware-2.0.x.yyy', they will see their boxen panic. ;) I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). Please fix it! ; -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
Akinori MUSHA writes: At Wed, 1 Nov 2000 22:08:26 -0800 (PST), Marcel Moolenaar wrote: marcel 2000/11/01 22:08:26 PST Modified files: sys/compat/linux linux_stats.c Log: Fix linux_ustat syscall. We only have cdevs now, so looking for a block device isn't that useful anymore. Reported by: Wesley Morgan [EMAIL PROTECTED] Submitted by: gallatin Acknowledged by: phk After this change, it panics when you perform stat against a linux block device node. Actually, emulators/vmware2 port creates some block device nodes in /compat/linux/dev, so all the vmware2 users still have ones installed. And when they hit `ls /compat/linux/dev' or `pkg_delete vmware-2.0.x.yyy', they will see their boxen panic. ;) I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). Hmm.. I seem to remember seeing something similar yesterday when my alpha was booting a brand new kernel with a 2 day-old userland. It was crashing in vfinddev called out of savecore and dev_mkdb. Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
At Fri, 03 Nov 2000 02:02:50 +0900, I wrote: I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). D'uh, I lied! Actually `ls /compat/linux/dev' panics at: vfinddev() -- addaliasu() -- ufs_vinit(). Seems I was 100% confused looking alternatively at source and ddb console. Sorry for the false report, but I'm repoting the truth this time. ;) Anyway, I think you can reproduce the panic by installing vmware2 port and doing `ls /compat/linux/dev'. Regards, -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
Akinori MUSHA writes: At Fri, 03 Nov 2000 02:02:50 +0900, I wrote: I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). D'uh, I lied! Actually `ls /compat/linux/dev' panics at: vfinddev() -- addaliasu() -- ufs_vinit(). Seems I was 100% confused looking alternatively at source and ddb console. Sorry for the false report, but I'm repoting the truth this time. ;) Anyway, I think you can reproduce the panic by installing vmware2 port and doing `ls /compat/linux/dev'. To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? I don't suppose you could throw an older kernel on and show the output of /bin/ls /compat/linux/dev ? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
At Thu, 2 Nov 2000 14:11:44 -0500 (EST), Andrew Gallatin wrote: To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? Yes. I don't suppose you could throw an older kernel on and show the output of /bin/ls /compat/linux/dev ? Here is the output from the native /bin/ls on 5.0-CURRENT as of two days ago. This operation causes panic on the latest CURRENT: knu@archon[2]% uname -a FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Tue Oct 31 15:11:38 JST 2000 [EMAIL PROTECTED]:/usr/local/src/sys/compile/ARCHON i386 knu@archon[2]% ls -l /compat/linux/dev total 0 brw-r--r-- 1 root wheel - 0, 0x00010002 Nov 2 20:28 hda brw-r--r-- 1 root wheel - 0, 0x0001000a Nov 2 20:28 hdb crw-rw-rw- 1 root wheel - 2, 2 Nov 2 20:28 null crw-r--r-- 1 root wheel - 202, 0 Nov 2 20:17 rtc lrwxr-xr-x 1 root wheel - 22 Nov 2 20:28 tty0@ - /compat/linux/dev/tty1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty1@ - /dev/ttyv0 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty10@ - /dev/ttyv9 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty11@ - /dev/ttyva lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty12@ - /dev/ttyvb lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty2@ - /dev/ttyv1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty3@ - /dev/ttyv2 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty4@ - /dev/ttyv3 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty5@ - /dev/ttyv4 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty6@ - /dev/ttyv5 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty7@ - /dev/ttyv6 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty8@ - /dev/ttyv7 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty9@ - /dev/ttyv8 crw-r--r-- 1 root wheel - 200, 0 Nov 2 20:28 vmmon crw-r--r-- 1 root wheel - 149, 0x00010001 Nov 2 20:35 vmnet1 As you see, hda and hdb are block devices that might cause the panic.. -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
In message [EMAIL PROTECTED], "Akinori MUSHA" writes: At Fri, 03 Nov 2000 02:02:50 +0900, I wrote: I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). D'uh, I lied! Actually `ls /compat/linux/dev' panics at: vfinddev() -- addaliasu() -- ufs_vinit(). Seems I was 100% confused looking alternatively at source and ddb console. Yes, this is my bad. I'm looking at it right now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
Akinori MUSHA wrote: At Thu, 2 Nov 2000 14:11:44 -0500 (EST), Andrew Gallatin wrote: To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? Yes. How is linux_ustat involved if the panic is caused by a native binary? -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
At Thu, 02 Nov 2000 15:26:29 -0500, Marcel Moolenaar wrote: Akinori MUSHA wrote: At Thu, 2 Nov 2000 14:11:44 -0500 (EST), Andrew Gallatin wrote: To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? Yes. How is linux_ustat involved if the panic is caused by a native binary? Not at all. Sorry, that was my mistaken assumption, after all. :( I confirmed linux ls didn't cause panic, so the culprit should belong somewhere else. Hopefully phk will catch it for us. :) -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
In message [EMAIL PROTECTED], "Akinori MUSHA" writes: At Thu, 02 Nov 2000 15:26:29 -0500, Marcel Moolenaar wrote: Akinori MUSHA wrote: At Thu, 2 Nov 2000 14:11:44 -0500 (EST), Andrew Gallatin wrote: To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? Yes. How is linux_ustat involved if the panic is caused by a native binary? Not at all. Sorry, that was my mistaken assumption, after all. :( I confirmed linux ls didn't cause panic, so the culprit should belong somewhere else. Hopefully phk will catch it for us. :) I hope I just did. Please report back if this has or hasn't solve the problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
At Thu, 02 Nov 2000 22:15:45 +0100, Poul-Henning Kamp wrote: I confirmed linux ls didn't cause panic, so the culprit should belong somewhere else. Hopefully phk will catch it for us. :) I hope I just did. Please report back if this has or hasn't solve the problem. Just confirmed that your fix solved the problem! Thanks! knu@archon[3]% uname -a FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #25: Fri Nov 3 06:28:04 JST 2000 [EMAIL PROTECTED]:/usr/local/src/sys/compile/ARCHON i386 knu@archon[3]% ls -l /compat/linux/dev total 0 brw-r--r-- 1 root wheel - 0, 0x00010002 Nov 2 20:28 hda brw-r--r-- 1 root wheel - 0, 0x0001000a Nov 2 20:28 hdb crw-rw-rw- 1 root wheel - 2, 2 Nov 2 20:28 null crw-r--r-- 1 root wheel - 202, 0 Nov 2 20:17 rtc lrwxr-xr-x 1 root wheel - 22 Nov 2 20:28 tty0@ - /compat/linux/dev/tty1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty1@ - /dev/ttyv0 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty10@ - /dev/ttyv9 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty11@ - /dev/ttyva lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty12@ - /dev/ttyvb lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty2@ - /dev/ttyv1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty3@ - /dev/ttyv2 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty4@ - /dev/ttyv3 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty5@ - /dev/ttyv4 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty6@ - /dev/ttyv5 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty7@ - /dev/ttyv6 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty8@ - /dev/ttyv7 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty9@ - /dev/ttyv8 crw-r--r-- 1 root wheel - 200, 0 Nov 2 20:28 vmmon crw-r--r-- 1 root wheel - 149, 0x00010001 Nov 2 20:35 vmnet1 knu@archon[3]% -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
