panic: ext2fs_dirbadentry

2013-07-17 Thread Sergey Bronnikov
Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. panic: ext2fs_dirbadentry Stopped at Debugger+0x5: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHO

panic: vrele: ref cnt

2013-07-17 Thread Sergey Bronnikov
Bug was catched by fsfuzzer pointed to ext2 fs. panic() at panic+0xe4 vrele() at vrele+0xcf ext2fs_reclaim() at ext2fs_reclaim+0x47 VOP_RECLAIM() at VOP_RECLAIM+0x2b vclean() at vclean+0x90 vgonel() at vgonel+0x40 vrecycle() at vrecycle+0x16 ext2fs_inactive() at ext2fs_inactive+0x7a VOP_INACTIVE()

Re: Intel GM45 hangs

2013-07-17 Thread Jonathan Gray
On Tue, Jul 16, 2013 at 09:14:49PM +0300, ja...@cieti.lv wrote: > >Can you try move the relevant mesa driver to a different > >directory so we can see if it is the x driver or the mesa driver > >that is triggering it? > > > >In other words move /usr/X11R6/lib/modules/dri/i965_dri.so to > >a differe

Re: panic: ext2fs_dirbadentry

2013-07-17 Thread Kenneth R Westerback
On Wed, Jul 17, 2013 at 12:11:34PM +0400, Sergey Bronnikov wrote: > Bug was catched by fsfuzzer. Probably that bug cannot be > found in real life with real usecase, but anyway it is a bug. Why? A failed consistency check means a bad fs, not necessarily a bug. "inode out of range" seems clear. A to

Re: panic: ext2fs_dirbadentry

2013-07-17 Thread Philip Guenther
On Wed, 17 Jul 2013, Sergey Bronnikov wrote: > Bug was catched by fsfuzzer. Probably that bug cannot be > found in real life with real usecase, but anyway it is a bug. Is e2fsck being run (forced?) after fuzzing and before trying to mount it? Philip

Re: panic: ext2fs_dirbadentry

2013-07-17 Thread Sergey Bronnikov
On 09:50 Wed 17 Jul , Philip Guenther wrote: > On Wed, 17 Jul 2013, Sergey Bronnikov wrote: > > Bug was catched by fsfuzzer. Probably that bug cannot be > > found in real life with real usecase, but anyway it is a bug. > > Is e2fsck being run (forced?) after fuzzing and before trying to mount it?

umount -tnfs -a does not unmount all NFS filesystems

2013-07-17 Thread Christian Weisgerber
"umount -tnfs -a" does not unmount all NFS filesystems. # mount /dev/sd0a on / type ffs (local) /dev/sd0d on /tmp type ffs (local, nodev, nosuid, softdep) /dev/sd0e on /var type ffs (local, nodev, nosuid, softdep) /dev/sd0f on /usr type ffs (local, nodev, softdep) /dev/sd0g on /usr/local type ffs

Re: umount -tnfs -a does not unmount all NFS filesystems

2013-07-17 Thread Miod Vallat
> "umount -tnfs -a" does not unmount all NFS filesystems. Likely related to the recent sysctl bug.

panic: ehci_device_clear_toggle: queue active

2013-07-17 Thread Sergey Bronnikov
Panic on attempt to write to USB 2.0 mass storage device. Step to reproduce: - attach USB flash - mount it - start copying files to mass storage - try to get a list of files on flash via ls(1) several times Unfortunately reproduction is not 100% OpenBSD 5.4-beta (GENERIC) #0: Mon Jul 15 23:06:59

Re: panic: ehci_device_clear_toggle: queue active

2013-07-17 Thread Alexey E. Suslikov
Sergey Bronnikov gmail.com> writes: > panic: ehci_device_clear_toggle: queue active Seems to be similar case as in another bug report. http://article.gmane.org/gmane.os.openbsd.bugs/19812/