Re: Panic in stable/11 (amd64) @r303903: page fault while in kernel mode
On 8/10/16 9:54 AM, David Wolfskill wrote:
> Happened after a few iterations of {"pkill dhclient" followed by
> "dhclient wlan0"}.
>
> Gory details (both "normal" and gzipped, and including the crash
> dump and crashinfo) are in
>
Panic in stable/11 (amd64) @r303903: page fault while in kernel mode
Happened after a few iterations of {"pkill dhclient" followed by
"dhclient wlan0"}.
Gory details (both "normal" and gzipped, and including the crash
dump and crashinfo) are in
Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
On 08/10/16 10:19 AM, Kubilay Kocak wrote:
>> Furthermore, it's a new regression that will go into 11.0-RELEASE, so
>> getting some attention is a good thing. I imagine this is why koobs@
>> CC'd stable@.
>
> It was the original reporter CC'd, I added mfc-stable{10,11} flags in
> case the issue was in those branches.
Oh! My apologies. I misremembered.
(Hmmm...Bugzilla doesn't seem to record changes in the CC list).
> I'm very careful with cc'ing lists for src/base issues unless SNR is
> very high, high impact or it needs eyes now.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
On 08/09/16 06:10 PM, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 > > --- Comment #13 from Ngie Cooper --- > Please don't add -current or -stable to bugs like this; it spams the list > unnecessarily (this issue impacts users of iSCSI + ZFS -- which seems a bit > niche right now) I'm sorry that some people were annoyed, although I wouldn't call it spam. It's a discussion of a bug that affects -STABLE, so stable@ is appropriate. Furthermore, it's a new regression that will go into 11.0-RELEASE, so getting some attention is a good thing. I imagine this is why koobs@ CC'd stable@. I thought it was limited to iSCSI, so I put that in the summary. However, we now know that it is not limited to iSCSI. I just updated the summary accordingly. Cheers, Eric ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
On 11/08/2016 1:14 AM, Eric van Gyzen wrote:
> On 08/09/16 06:10 PM, bugzilla-nore...@freebsd.org wrote:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491
>>
>> --- Comment #13 from Ngie Cooper ---
>> Please don't add -current or -stable to bugs like this; it spams the list
>> unnecessarily (this issue impacts users of iSCSI + ZFS -- which seems a bit
>> niche right now)
>
> I'm sorry that some people were annoyed, although I wouldn't call it
> spam. It's a discussion of a bug that affects -STABLE, so stable@ is
> appropriate.
>
> Furthermore, it's a new regression that will go into 11.0-RELEASE, so
> getting some attention is a good thing. I imagine this is why koobs@
> CC'd stable@.
It was the original reporter CC'd, I added mfc-stable{10,11} flags in
case the issue was in those branches.
I'm very careful with cc'ing lists for src/base issues unless SNR is
very high, high impact or it needs eyes now.
> I thought it was limited to iSCSI, so I put that in the summary.
> However, we now know that it is not limited to iSCSI. I just updated
> the summary accordingly.
>
> Cheers,
>
> Eric
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fsck_ufs dumps core
> On 10 Aug 2016, at 17:55, Konstantin Belousov wrote: > > On Wed, Aug 10, 2016 at 05:29:31PM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> I am running FreeBSD 10.3-STABLE #0 r299261M >> >> After unclean reboot I am unable to fsck my UFS filesystem: >> >> # fsck /dev/mfid0p1 >> ** /dev/mfid0p1 >> ** Last Mounted on /opt >> ** Phase 1 - Check Blocks and Sizes >> fsck: /dev/mfid0p1: Segmentation fault >> >> pid 482 (fsck_ufs), uid 0: exited on signal 11 (core dumped) >> >> # gdb -c fsck_ufs.482 /sbin/fsck_ufs >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you are >> welcome to change it and/or distribute copies of it under certain conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for details. >> This GDB was configured as "amd64-marcel-freebsd"... >> Core was generated by `fsck_ufs'. >> Program terminated with signal 11, Segmentation fault. >> Reading symbols from /lib/libufs.so.6...done. >> Loaded symbols for /lib/libufs.so.6 >> Reading symbols from /lib/libc.so.7...done. >> Loaded symbols for /lib/libc.so.7 >> Reading symbols from /libexec/ld-elf.so.1...done. >> Loaded symbols for /libexec/ld-elf.so.1 >> #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 >> 83 setbmap(i); >> (gdb) bt >> #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 >> #1 0x00409050 in main (argc=, >>argv=) at /place/WRK/src/sbin/fsck_ffs/main.c:447 >> Current language: auto; currently minimal >> (gdb) >> > > Try to use alternative superblock (-b switch). You can get the list of > the possible values for -b by 'newfs -N' invocation, but you have to know > the parameters which were used for formatting. Yes, I tried several different backup superblocks, with the same result. (I created this FS few years ago so I can't be 100% sure about the parameters, but I usually only use larger -i NN for big filesystems, and I can guess the exact value examining df -ik). BTW I just noticed that when I use larger values for backup superblock, it reports an error which looks like overflow: # fsck_ufs -b 7437746112 /dev/mfid0p1 Alternate super block location: -1152188480 ** /dev/mfid0p1 CANNOT SEEK BLK: -1152188480 CONTINUE? [yn] ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fsck_ufs dumps core
On Wed, Aug 10, 2016 at 05:29:31PM +0300, Dmitry Sivachenko wrote: > Hello, > > I am running FreeBSD 10.3-STABLE #0 r299261M > > After unclean reboot I am unable to fsck my UFS filesystem: > > # fsck /dev/mfid0p1 > ** /dev/mfid0p1 > ** Last Mounted on /opt > ** Phase 1 - Check Blocks and Sizes > fsck: /dev/mfid0p1: Segmentation fault > > pid 482 (fsck_ufs), uid 0: exited on signal 11 (core dumped) > > # gdb -c fsck_ufs.482 /sbin/fsck_ufs > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > Core was generated by `fsck_ufs'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /lib/libufs.so.6...done. > Loaded symbols for /lib/libufs.so.6 > Reading symbols from /lib/libc.so.7...done. > Loaded symbols for /lib/libc.so.7 > Reading symbols from /libexec/ld-elf.so.1...done. > Loaded symbols for /libexec/ld-elf.so.1 > #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 > 83 setbmap(i); > (gdb) bt > #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 > #1 0x00409050 in main (argc=, > argv=) at /place/WRK/src/sbin/fsck_ffs/main.c:447 > Current language: auto; currently minimal > (gdb) > Try to use alternative superblock (-b switch). You can get the list of the possible values for -b by 'newfs -N' invocation, but you have to know the parameters which were used for formatting. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
fsck_ufs dumps core
Hello, I am running FreeBSD 10.3-STABLE #0 r299261M After unclean reboot I am unable to fsck my UFS filesystem: # fsck /dev/mfid0p1 ** /dev/mfid0p1 ** Last Mounted on /opt ** Phase 1 - Check Blocks and Sizes fsck: /dev/mfid0p1: Segmentation fault pid 482 (fsck_ufs), uid 0: exited on signal 11 (core dumped) # gdb -c fsck_ufs.482 /sbin/fsck_ufs GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `fsck_ufs'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libufs.so.6...done. Loaded symbols for /lib/libufs.so.6 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 83 setbmap(i); (gdb) bt #0 0x00409a8b in pass1 () at /place/WRK/src/sbin/fsck_ffs/pass1.c:83 #1 0x00409050 in main (argc=, argv=) at /place/WRK/src/sbin/fsck_ffs/main.c:447 Current language: auto; currently minimal (gdb) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with em0 driver after upgrade to r303832
Bit more testing on this, and I think it was a false alarm and my problem was actually hardware related. Moving to a different PCI slot stopped the problem happening. The original ethernet card is now dead however, and the slow has burn marks on it - which makes me think ,it isnt software really ;) Appologies for the noise, it just coincided with an upgrade and I didnt expect the slot to be at fault after trying three cards (though that was the logical next step) -pete. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
