* bug ?
@ 2003-03-17 14:06 Andreas Westin
0 siblings, 0 replies; 42+ messages in thread
From: Andreas Westin @ 2003-03-17 14:06 UTC (permalink / raw)
To: netdev
Hello,
I've gotten this "crash" now several times with >=2.4.20. It usually happens
within 1-2 days after bootup while downloading a larger amount of data at
around 500k/s.
Using gentoo linux on a dual 400mhz (celeron) abit bp6, i know this could be
due to hardware problems but i thought that I might aswell report it if its
a real bug. I hope that the info below is all that you need.
/Andreas
Network driver:
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 Fast Ethernet at 0xd8800000, 00:d0:70:01:0f:2f, IRQ 18
eth0: Identified 8139 chip type 'RTL-8139C'
Unable to handle kernel paging request at virtual address e9272d39
c026c49f
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c026c49f>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00210246
eax: 00008000 ebx: e9272d0d ecx: d561e3a0 edx: 00000000
esi: cad75f6c edi: cc47bec0 ebp: cad75f6c esp: cad75ee4
ds: 0018 es: 0018 ss: 0018
Process ncftp (pid: 31976, stackpage=cad75000)
Stack: d561e3a0 cad75f6c 00008000 00000000 00000000 cad75efc 00000000
00008000
cad75f20 c022c008 cc47bec0 cad75f6c 00008000 00000000 cad75f20
00000000
00000000 00000000 00000000 00000000 00000049 cad74000 00000064
d65bb520
Call Trace: [<c022c008>] [<c022c147>] [<c013ce97>] [<c010773f>]
Code: ff 53 2c 85 c0 89 c2 78 07 8b 44 24 18 89 46 04 8b 5c 24 1c
>>EIP; c026c49f <inet_recvmsg+4f/70> <=====
Trace; c022c008 <sock_recvmsg+58/f0>
Trace; c022c147 <sock_read+a7/b0>
Trace; c013ce97 <sys_read+97/140>
Trace; c010773f <system_call+33/38>
Code; c026c49f <inet_recvmsg+4f/70>
00000000 <_EIP>:
Code; c026c49f <inet_recvmsg+4f/70> <=====
0: ff 53 2c call *0x2c(%ebx) <=====
Code; c026c4a2 <inet_recvmsg+52/70>
3: 85 c0 test %eax,%eax
Code; c026c4a4 <inet_recvmsg+54/70>
5: 89 c2 mov %eax,%edx
Code; c026c4a6 <inet_recvmsg+56/70>
7: 78 07 js 10 <_EIP+0x10>
Code; c026c4a8 <inet_recvmsg+58/70>
9: 8b 44 24 18 mov 0x18(%esp,1),%eax
Code; c026c4ac <inet_recvmsg+5c/70>
d: 89 46 04 mov %eax,0x4(%esi)
Code; c026c4af <inet_recvmsg+5f/70>
10: 8b 5c 24 1c mov 0x1c(%esp,1),%ebx
Linux hostname 2.4.21-pre5 #2 SMP Fri Feb 28 00:03:43 CET 2003 i686 Celeron
(Mendocino) GenuineIntel GNU/Linux
Gnu C 3.2.2
Gnu make 3.80
util-linux 2.11z
mount 2.11z
modutils 2.4.23
e2fsprogs 1.32
reiserfsprogs 3.6.3
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.1.6
Net-tools 1.60
Kbd 1.06
Sh-utils 2.0.15
^ permalink raw reply [flat|nested] 42+ messages in thread
* BUG,
@ 2019-08-05 2:42 Su Yanjun
0 siblings, 0 replies; 42+ messages in thread
From: Su Yanjun @ 2019-08-05 2:42 UTC (permalink / raw)
To: linux-nfs; +Cc: cuiyue-fnst
Hi,
When I tested xfstests generic/465 with NFS, there was something unexpected.
When memory of NFS server was 10G, test passed.
But when memory of NFS server was 4G, test failed.
Fail message was as below.
non-aio dio test
encounter an error: block 4 offset 0, content 62
aio-dio test
encounter an error: block 1 offset 0, content 62
All of the NFS versions(v3 v4.0 v4.1 v4.2) have this problem.
Maybe something is wrong about NFS's I/O operation.
Thanks in advance.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug: "git log --format='format:%+s%+b'" doesn't insert newline before body
@ 2016-07-24 13:46 Ilya Tumaykin
2016-07-25 6:55 ` Bug: Beat Bolli
0 siblings, 1 reply; 42+ messages in thread
From: Ilya Tumaykin @ 2016-07-24 13:46 UTC (permalink / raw)
To: git
Hello.
Steps to reproduce:
$ git init
$ >123
$ git add 123
$ git commit -v -m 'This is subject' -m 'And this is body'
$ git --no-pager log -1 --format='format:%+s%+b'
Actual results:
```
This is subject
And this is body
```
Expected results:
```
This is subject
And this is body
```
$ git --version
git version 2.9.2
Please fix.
--
Best regards.
Ilya Tumaykin.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2015-04-10 18:27 Barclay Jameson
0 siblings, 0 replies; 42+ messages in thread
From: Barclay Jameson @ 2015-04-10 18:27 UTC (permalink / raw)
To: ceph-devel
Watching osd pool stats (watch --interval=.5 -d 'ceph osd pool stats')
while restarting 1/3 of my OSDs give some odd numbers:
pool cephfs_data id 1
-768/9 objects degraded (-8533.333%)
recovery io 18846 B/s, 1 objects/s
client io 15356 B/s wr, 2 op/s
pool cephfs_metadata id 2
-1/0 objects degraded (-inf%)
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes
@ 2014-04-21 16:16 Andreas Reis
2014-04-21 19:13 ` Andreas Reis
0 siblings, 1 reply; 42+ messages in thread
From: Andreas Reis @ 2014-04-21 16:16 UTC (permalink / raw)
To: linux-btrfs
Kernel 3.15.0-rc2, btrfs-progs 3.14.1
While doing some minor package updates my btrfs root partition [*]
decided to corrupt itself. There was no system crash, although I had
plenty of these (due to an USB-related regression) in recent weeks that
resulted in no trouble.
First only one of a package's folders was corrupted, any access to files
within (incl. attempts to delete) printed
btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
to dmesg (I'm actually not sure about the numbers, but that was indeed
the error message). After moving the folder out of the way the partition
continued to appear working as normal, one reboot also worked fine.
Now I can't boot at all (beyond loading the kernel image located on
another partition), neither with 3,15-rc2 nor 3.14.1. Attempting to
mount the __current/ROOT subvolume on ArchLinux's current Live-CD
(kernel 3.13.7) prints
btrfs: device label Linux devid 1 transid 55586 /dev/sdc5
btrfs: use ssd allocation scheme
btrfs: disk space caching is enabled
btrfs: checking UUID tree
btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
BTRFS error (device sdc5): Error removing orphan entry, stopping orphan
cleanup
BTRFS critical (device sdc5): could not do orphan cleanup -22
Doing "btrfs check /dev/sdc5" merely first prints ten
free space inode generation (0) did not match free space cache
generation ([different transids between 40010 and 55578])
to then abort with
checking fs roots
btrfs: cmds-check.c:1151: procecss_file_extent: Assertion `!(rec->ino !=
key->objectid || rec->refs > 1)' failed.
I'm reluctant to try any of "btrfs check" options (or mount with -o
recovery) since the last three times I did this (with other partitions)
it resulted in the partition becoming entirely trashed, while before at
least "btrfs restore" still managed to extract some data each time.
The affected folder was one within /usr/include/qt4 (which I then moved
to /usr/BROKEN, to successfully reinstall the package), ie. on the
__current/ROOT subvolume.
Which seems the only subvolume affected (yet). Mounting & accessing the
other three (__current/{var,home,opt}) still works.
[*] Organised following
http://blog.fabio.mancinelli.me/2012/12/28/Arch_Linux_on_BTRFS.html
(Also posted on https://bugzilla.kernel.org/show_bug.cgi?id=74611 )
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes
2014-04-21 16:16 Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes Andreas Reis
@ 2014-04-21 19:13 ` Andreas Reis
2014-04-22 18:16 ` Andreas Reis
0 siblings, 1 reply; 42+ messages in thread
From: Andreas Reis @ 2014-04-21 19:13 UTC (permalink / raw)
To: linux-btrfs
Alright, turns out the partition does actually mount on 3.15-rc2 (error
messages remain, of course).
But systemd will fail to continue booting as /bin/mount returns "exit
status 32" and / thus ends as ro, yet can be manually remounted as rw.
Another error message I've spotted with 3.15 is
BTRFS error (device sdc5): error loading props for ino 1810424 (root
257): -5
I've now tried to mount with -o recovery and clear_cache, no effect.
On 21.04.2014 18:16, Andreas Reis wrote:
> Kernel 3.15.0-rc2, btrfs-progs 3.14.1
>
> While doing some minor package updates my btrfs root partition [*]
> decided to corrupt itself. There was no system crash, although I had
> plenty of these (due to an USB-related regression) in recent weeks that
> resulted in no trouble.
>
> First only one of a package's folders was corrupted, any access to files
> within (incl. attempts to delete) printed
>
> btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
>
> to dmesg (I'm actually not sure about the numbers, but that was indeed
> the error message). After moving the folder out of the way the partition
> continued to appear working as normal, one reboot also worked fine.
>
> Now I can't boot at all (beyond loading the kernel image located on
> another partition), neither with 3,15-rc2 nor 3.14.1. Attempting to
> mount the __current/ROOT subvolume on ArchLinux's current Live-CD
> (kernel 3.13.7) prints
>
> btrfs: device label Linux devid 1 transid 55586 /dev/sdc5
> btrfs: use ssd allocation scheme
> btrfs: disk space caching is enabled
> btrfs: checking UUID tree
> btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
> btrfs: corrupt leaf, slot offset bad: block=842924032,root=1, slot=88
> BTRFS error (device sdc5): Error removing orphan entry, stopping orphan
> cleanup
> BTRFS critical (device sdc5): could not do orphan cleanup -22
>
> Doing "btrfs check /dev/sdc5" merely first prints ten
>
> free space inode generation (0) did not match free space cache
> generation ([different transids between 40010 and 55578])
>
> to then abort with
>
> checking fs roots
> btrfs: cmds-check.c:1151: procecss_file_extent: Assertion `!(rec->ino !=
> key->objectid || rec->refs > 1)' failed.
>
> I'm reluctant to try any of "btrfs check" options (or mount with -o
> recovery) since the last three times I did this (with other partitions)
> it resulted in the partition becoming entirely trashed, while before at
> least "btrfs restore" still managed to extract some data each time.
>
> The affected folder was one within /usr/include/qt4 (which I then moved
> to /usr/BROKEN, to successfully reinstall the package), ie. on the
> __current/ROOT subvolume.
>
> Which seems the only subvolume affected (yet). Mounting & accessing the
> other three (__current/{var,home,opt}) still works.
>
> [*] Organised following
> http://blog.fabio.mancinelli.me/2012/12/28/Arch_Linux_on_BTRFS.html
>
> (Also posted on https://bugzilla.kernel.org/show_bug.cgi?id=74611 )
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes
2014-04-21 19:13 ` Andreas Reis
@ 2014-04-22 18:16 ` Andreas Reis
2014-04-23 2:55 ` Duncan
0 siblings, 1 reply; 42+ messages in thread
From: Andreas Reis @ 2014-04-22 18:16 UTC (permalink / raw)
To: linux-btrfs
Same failure with btrfs-progs from integration-20140421 (apart from the
line number 1156).
Can I get a bit of input on this? Is it safe to just ignore the error
for now (as I'm doing atm), ie. remount as rw to skip the orphan cleanup?
Might it even be safe to call btrfs check --repair on the partition? I'm
not keen on that failing mid-process at the same assertion and thus
breaking it over a bunch of minor files, just like it happened with my
previous btrfs partitions.
On 21.04.2014 21:13, Andreas Reis wrote:
> Alright, turns out the partition does actually mount on 3.15-rc2 (error
> messages remain, of course).
>
> But systemd will fail to continue booting as /bin/mount returns "exit
> status 32" and / thus ends as ro, yet can be manually remounted as rw.
>
> Another error message I've spotted with 3.15 is
>
> BTRFS error (device sdc5): error loading props for ino 1810424 (root
> 257): -5
>
> I've now tried to mount with -o recovery and clear_cache, no effect.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes
2014-04-22 18:16 ` Andreas Reis
@ 2014-04-23 2:55 ` Duncan
2014-04-25 2:04 ` Bug: Andreas Reis
0 siblings, 1 reply; 42+ messages in thread
From: Duncan @ 2014-04-23 2:55 UTC (permalink / raw)
To: linux-btrfs
Andreas Reis posted on Tue, 22 Apr 2014 20:16:13 +0200 as excerpted:
> Same failure with btrfs-progs from integration-20140421 (apart from the
> line number 1156).
>
> Can I get a bit of input on this? Is it safe to just ignore the error
> for now (as I'm doing atm), ie. remount as rw to skip the orphan
> cleanup?
I explained orphans in my other reply. Since they're simply not yet
completed file deletions, it should be /relatively/ safe to continue
ignoring and doing the manual remount rw, since that continues to work.
"Relatively" as in that's what I'd do in the shorter term here were I
seeing the problem, tho I'd ensure my backups were current and tested, as
should be the case on btrfs anyway since it's not entirely stable yet,
and just because I don't like nagging half-dealt-with-problems left
laying around and the error would eat at me until I'd cleared it, at some
point likely rather sooner than later, I'd very likely mkfs and restore
from those backups. But I'd certainly be willing to continue running
from the partition short term, for a week or so until I had a chance to
do the mkfs.btrfs and restore from backup, as long as that remained the
only issue I was seeing.
> Might it even be safe to call btrfs check --repair on the partition? I'm
> not keen on that failing mid-process at the same assertion and thus
> breaking it over a bunch of minor files, just like it happened with my
> previous btrfs partitions.
That I can't say. Based on reports and the common knowledge of the list,
I've become rather leery of btrfs check --repair myself, and tend to rely
on scrub and balance to fix issues if they can, and beyond that,
mkfs.btrfs and restore from backup. In fact, while btrfs check without
the --repair is safe as it's read-only, I don't run it regularly either,
because I know should it report problems I'd then be worried about things
I might have no reasonable way to fix, that obviously aren't causing me
problems anyway. Basically, if mounting and regular use of the
filesystem isn't giving me anything unusual in dmesg, I consider it good,
and I for the most part I tend to route around btrfs check entirely, as
if it weren't even there, tho I've run it in default read-only mode a few
times, to compare my output with a post from the list or something,
always with a clean bill of health from btrfs check when I have run it.
That said, if you have backups tested and ready anyway, and would
otherwise be doing a mkfs.btrfs in short order in ordered to get rid of
those bad orphan warnings anyway, I don't see the harm in running it,
since at that point it's zero risk anyway. If you lose the filesystem as
a result, big deal, as you were going to mkfs.btrfs and restore from
backup anyway, and if it fixes the problem, well, you saved yourself the
hassle.
Plus, either way you can report back the results and then we'll know
whether it's safe to recommend btrfs check for the next report, or not.
=:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug:
2014-04-23 2:55 ` Duncan
@ 2014-04-25 2:04 ` Andreas Reis
0 siblings, 0 replies; 42+ messages in thread
From: Andreas Reis @ 2014-04-25 2:04 UTC (permalink / raw)
To: linux-btrfs
Duncan <1i5t5.duncan <at> cox.net> writes:
> Plus, either way you can report back the results and then we'll
know
> whether it's safe to recommend btrfs check for the next report,
or not.
> =:^)
Well this is just bloody brilliant.
I did btrfs check --repair with from integration and a bunch of
fixes on this list applied. Failed at the same assert, but
otherwise left the partition unchanged, ie. mountable.
So as planned, thinking I have a relatively fresh backup of the
whole partition (via partclone.btrfs), I go on restoring it to
get rid of the errors.
partclone does its thing, the restored partition mounts, text
files are properly readable (!) and btrfs check reports no
errors.
Then on reboot, the kernel (residing on another partition)
instantly crashes: "Input/Output error".
Turns out that when I try to run any binary from the restored
partition (via LiveCD), *every* *single* *one* fails with this
remarkably expressive error. If I manually replace one with a
fresh download, I get a SIGBUS crash instead.
Oh, and upon accessing any of said binaries, dmesg prints a BTRFS
info that csum failed. But only for binaries.
Yay. No idea how to proceed from here, but I guess this might not
necessarily be related to btrfs. Certainly doesn't make me want
to recommend it in the foreseeable future, though.
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug?
@ 2014-02-17 10:28 Dirk Winning, junidas GmbH
2014-02-17 14:51 ` bug? Pasi Kärkkäinen
0 siblings, 1 reply; 42+ messages in thread
From: Dirk Winning, junidas GmbH @ 2014-02-17 10:28 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1.1: Type: text/plain, Size: 2358 bytes --]
Hi,
we have XEN 4.0.1 on debian 6.0.6
and I tried to activate a USB-Modem for a DOMU running OSX; the modem is already recognized and looks right; but it will not dial out or take a call.
Tried a memory-Stick and the same here: it appears in USB but will not mount.
Obviously it may not be clear where the problem exactly is, but one question arises:
is it neccessary to do all steps listed further down and what about the error message?
Since, the USB-devices already do appear correctly, but are unusable in the end.
Thanks for any hints
greets
Started domain fax (id=89)
root@graff:~# xm usb-list 89
root@graff:~# xm usb-hc-create fax 89 1
root@graff:~# xm usb-list 89
Idx BE state usb-ver BE-path
0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
port 1:
root@graff:~# xm usb-add 89 host:05ac:1401
root@graff:~# xm usb-list 89
Idx BE state usb-ver BE-path
0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
port 1:
root@graff:~# xm usb-attach 89 0 1 2-1
Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>
main.main(sys.argv)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main
_, rc = _run_cmd(cmd, cmd_name, args)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _run_cmd
return True, cmd(args)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 2868, in xm_usb_attach
if vusb_util.bus_is_assigned(bus):
File "/usr/lib/xen-4.0/lib/python/xen/util/vusb_util.py", line 275, in bus_is_assigned
raise UsbDeviceParseError("Can't get assignment status: (%s)." % bus)
xen.util.vusb_util.UsbDeviceParseError: vusb: Error parsing USB device info: Can't get assignment status: (2-1).
root@graff:~# xm usb-list-assignable-devices
1-6 : ID 14dd:0002 Peppercon AG Multidevice
2-1 : ID 05ac:1401 Motorola, Inc. Apple USB Modem
2-2 : ID 06da:0003 OMRON USB UPS
Dipl. Ing. Dirk Winning, Systemberater
dirk.winning@junidas.de
junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart
Tel. +49 (711) 4599799-12
Geschäftsführer: Dr. Markus Stoll, Matthias Zepf
Amtsgericht Stuttgart, HRB 21939
[-- Attachment #1.1.2: Type: text/html, Size: 7124 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3646 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug?
2014-02-17 10:28 bug? Dirk Winning, junidas GmbH
@ 2014-02-17 14:51 ` Pasi Kärkkäinen
0 siblings, 0 replies; 42+ messages in thread
From: Pasi Kärkkäinen @ 2014-02-17 14:51 UTC (permalink / raw)
To: Dirk Winning, junidas GmbH; +Cc: xen-devel
On Mon, Feb 17, 2014 at 11:28:55AM +0100, Dirk Winning, junidas GmbH wrote:
> Hi,
Hi,
> we have XEN 4.0.1 on debian 6.0.6
First of all you should upgrade Xen..
Xen 4.0.1 is very old already, and it's not supported anymore by upstream.
> and I tried to activate a USB-Modem for a DOMU running OSX; the modem is
> already recognized and looks right; but it will not dial out or take a
> call.
> Tried a memory-Stick and the same here: it appears in USB but will not
> mount.
> Obviously it may not be clear where the problem exactly is, but one
> question arises:
> is it neccessary to do all steps listed further down and what about the
> error message?
> Since, the USB-devices already do appear correctly, but are unusable in
> the end.
> Thanks for any hints
> greets
> Started domain fax (id=89)
> root@graff:~# xm usb-list 89
> root@graff:~# xm usb-hc-create fax 89 1
> root@graff:~# xm usb-list 89
> Idx BE state usb-ver BE-path
> 0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
> port 1:
> root@graff:~# xm usb-add 89 host:05ac:1401
> root@graff:~# xm usb-list 89
> Idx BE state usb-ver BE-path
> 0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
> port 1:
> root@graff:~# xm usb-attach 89 0 1 2-1
>
Hmm.. "usb-attach" is a command for Xen PVUSB.
Do you really have a Xen PVUSB backend driver (usbback) in dom0 kernel,
and especially PVUSB frontend driver loaded in the *OSX* VM?
-- Pasi
> Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
> Please report to [1]xen-devel@lists.xensource.com
> Traceback (most recent call last):
> File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>
> main.main(sys.argv)
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main
> _, rc = _run_cmd(cmd, cmd_name, args)
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in
> _run_cmd
> return True, cmd(args)
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 2868, in
> xm_usb_attach
> if vusb_util.bus_is_assigned(bus):
> File "/usr/lib/xen-4.0/lib/python/xen/util/vusb_util.py", line 275, in
> bus_is_assigned
> raise UsbDeviceParseError("Can't get assignment status: (%s)." % bus)
> xen.util.vusb_util.UsbDeviceParseError: vusb: Error parsing USB device
> info: Can't get assignment status: (2-1).
> root@graff:~# xm usb-list-assignable-devices
> 1-6 : ID 14dd:0002 Peppercon AG Multidevice
> 2-1 : ID 05ac:1401 Motorola, Inc. Apple USB Modem
> 2-2 : ID 06da:0003 OMRON USB UPS
> Dipl. Ing. Dirk Winning, Systemberater
> [2]dirk.winning@junidas.de
>
> junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart
> Tel. +49 (711) 4599799-12
> Geschäftsführer: Dr. Markus Stoll, Matthias Zepf
> Amtsgericht Stuttgart, HRB 21939
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* BUG??
@ 2013-11-20 22:18 Bruno Bruzzano
2013-11-21 12:02 ` BUG?? Luiz Augusto von Dentz
0 siblings, 1 reply; 42+ messages in thread
From: Bruno Bruzzano @ 2013-11-20 22:18 UTC (permalink / raw)
To: linux-bluetooth
Hi all,
Maybe I encountered a bug. I'm using git version of Bluez5 on Fedora
20 beta and all crash when I try to connect to a generic profile. In
particular, the steps to reproduce it are the following:
- start bluetooth daemon (with -ndE args)
- using bluetoothctl (in client folder):
-- agent on
-- scan on
-- wait to discovery my android device
-- scan off
-- pair maddr -> pair complete!
After that I try to connect using AVRCP profile. It works.
The problem appears when a tap on my smartphone's player. Bluetoothd crashes!!
Here, you can find some pastebins.
bluetoothd -> http://pastebin.com/ZSER2Df6
bluetoothctl -> http://pastebin.com/rexVrruB
I hope someone can give me a feedback or a
tip!
Thanks in advance
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG??
2013-11-20 22:18 BUG?? Bruno Bruzzano
@ 2013-11-21 12:02 ` Luiz Augusto von Dentz
2013-11-21 14:07 ` BUG?? Bruno Bruzzano
0 siblings, 1 reply; 42+ messages in thread
From: Luiz Augusto von Dentz @ 2013-11-21 12:02 UTC (permalink / raw)
To: Bruno Bruzzano; +Cc: linux-bluetooth
Hi Bruno,
On Thu, Nov 21, 2013 at 12:18 AM, Bruno Bruzzano <brunano21@gmail.com> wrote:
> Hi all,
>
> Maybe I encountered a bug. I'm using git version of Bluez5 on Fedora
> 20 beta and all crash when I try to connect to a generic profile. In
> particular, the steps to reproduce it are the following:
> - start bluetooth daemon (with -ndE args)
> - using bluetoothctl (in client folder):
> -- agent on
> -- scan on
> -- wait to discovery my android device
> -- scan off
> -- pair maddr -> pair complete!
>
> After that I try to connect using AVRCP profile. It works.
> The problem appears when a tap on my smartphone's player. Bluetoothd crashes!!
>
> Here, you can find some pastebins.
> bluetoothd -> http://pastebin.com/ZSER2Df6
> bluetoothctl -> http://pastebin.com/rexVrruB
>
> I hope someone can give me a feedback or a
> tip!
Give the following message I believe there is something wrong with the
D-Bus conf file:
bluetoothd[2009]: src/agent.c:simple_agent_reply() agent error reply:
org.freedesktop.DBus.Error.NoReply, Message did not receive a reply
(timeout by message bus)
bluetoothd[2009]: Access denied: Message did not receive a reply
(timeout by message bus)
Also it is quite possible that bluetoothd is being disconnected from
D-Bus due to SELinux policy, you can try disabling it and see if that
works, if it does then we need to let the fedora folks know so they
add a proper rule for it.
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG??
2013-11-21 12:02 ` BUG?? Luiz Augusto von Dentz
@ 2013-11-21 14:07 ` Bruno Bruzzano
2013-11-21 14:17 ` BUG?? Bruno Bruzzano
0 siblings, 1 reply; 42+ messages in thread
From: Bruno Bruzzano @ 2013-11-21 14:07 UTC (permalink / raw)
To: Luiz Augusto von Dentz; +Cc: linux-bluetooth
Hi Luiz,
I did as you suggested, disabling temporarily the SELinux.
Unfortunally the result is the same. Here I made a pastebin which
shows the last part of the connection and the fail.
Let me know. Thanks!.
Best Regards,
Bruno Bruzzano
On Thu, Nov 21, 2013 at 7:02 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Hi Bruno,
>
> On Thu, Nov 21, 2013 at 12:18 AM, Bruno Bruzzano <brunano21@gmail.com> wrote:
>> Hi all,
>>
>> Maybe I encountered a bug. I'm using git version of Bluez5 on Fedora
>> 20 beta and all crash when I try to connect to a generic profile. In
>> particular, the steps to reproduce it are the following:
>> - start bluetooth daemon (with -ndE args)
>> - using bluetoothctl (in client folder):
>> -- agent on
>> -- scan on
>> -- wait to discovery my android device
>> -- scan off
>> -- pair maddr -> pair complete!
>>
>> After that I try to connect using AVRCP profile. It works.
>> The problem appears when a tap on my smartphone's player. Bluetoothd crashes!!
>>
>> Here, you can find some pastebins.
>> bluetoothd -> http://pastebin.com/ZSER2Df6
>> bluetoothctl -> http://pastebin.com/rexVrruB
>>
>> I hope someone can give me a feedback or a
>> tip!
>
> Give the following message I believe there is something wrong with the
> D-Bus conf file:
>
> bluetoothd[2009]: src/agent.c:simple_agent_reply() agent error reply:
> org.freedesktop.DBus.Error.NoReply, Message did not receive a reply
> (timeout by message bus)
> bluetoothd[2009]: Access denied: Message did not receive a reply
> (timeout by message bus)
>
> Also it is quite possible that bluetoothd is being disconnected from
> D-Bus due to SELinux policy, you can try disabling it and see if that
> works, if it does then we need to let the fedora folks know so they
> add a proper rule for it.
>
>
> --
> Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG??
2013-11-21 14:07 ` BUG?? Bruno Bruzzano
@ 2013-11-21 14:17 ` Bruno Bruzzano
0 siblings, 0 replies; 42+ messages in thread
From: Bruno Bruzzano @ 2013-11-21 14:17 UTC (permalink / raw)
To: Luiz Augusto von Dentz; +Cc: linux-bluetooth
Hi Luiz,
I did as you suggested, disabling temporarily the SELinux.
Unfortunally the result is the same. Here I made a pastebin which
shows the last part of the connection and the fail.
http://pastebin.com/K4QKCHgN
Let me know. Thanks!.
Best Regards,
Bruno Bruzzano
On Thu, Nov 21, 2013 at 9:07 AM, Bruno Bruzzano <brunano21@gmail.com> wrote:
> Hi Luiz,
>
> I did as you suggested, disabling temporarily the SELinux.
> Unfortunally the result is the same. Here I made a pastebin which
> shows the last part of the connection and the fail.
>
> Let me know. Thanks!.
> Best Regards,
> Bruno Bruzzano
>
> On Thu, Nov 21, 2013 at 7:02 AM, Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
>> Hi Bruno,
>>
>> On Thu, Nov 21, 2013 at 12:18 AM, Bruno Bruzzano <brunano21@gmail.com> wrote:
>>> Hi all,
>>>
>>> Maybe I encountered a bug. I'm using git version of Bluez5 on Fedora
>>> 20 beta and all crash when I try to connect to a generic profile. In
>>> particular, the steps to reproduce it are the following:
>>> - start bluetooth daemon (with -ndE args)
>>> - using bluetoothctl (in client folder):
>>> -- agent on
>>> -- scan on
>>> -- wait to discovery my android device
>>> -- scan off
>>> -- pair maddr -> pair complete!
>>>
>>> After that I try to connect using AVRCP profile. It works.
>>> The problem appears when a tap on my smartphone's player. Bluetoothd crashes!!
>>>
>>> Here, you can find some pastebins.
>>> bluetoothd -> http://pastebin.com/ZSER2Df6
>>> bluetoothctl -> http://pastebin.com/rexVrruB
>>>
>>> I hope someone can give me a feedback or a
>>> tip!
>>
>> Give the following message I believe there is something wrong with the
>> D-Bus conf file:
>>
>> bluetoothd[2009]: src/agent.c:simple_agent_reply() agent error reply:
>> org.freedesktop.DBus.Error.NoReply, Message did not receive a reply
>> (timeout by message bus)
>> bluetoothd[2009]: Access denied: Message did not receive a reply
>> (timeout by message bus)
>>
>> Also it is quite possible that bluetoothd is being disconnected from
>> D-Bus due to SELinux policy, you can try disabling it and see if that
>> works, if it does then we need to let the fedora folks know so they
>> add a proper rule for it.
>>
>>
>> --
>> Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 42+ messages in thread
[parent not found: <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>]
* Re: bug?
[not found] <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>
@ 2013-01-28 16:37 ` Mathieu Desnoyers
0 siblings, 0 replies; 42+ messages in thread
From: Mathieu Desnoyers @ 2013-01-28 16:37 UTC (permalink / raw)
To: Yang Wang; +Cc: Kenneth Kent, lttng-dev, ,
* Yang Wang (yangw.wang5@unb.ca) wrote:
> Hello,
>
> I am Yang Wang, I am currently using lttng to trace my JVM.
>
> During my using lttng in tracing JVM, I found three problems,
>
> 1) in lttng-ust-2.1.0/include/lttng/ust-tracepoint-event.h
>
> why using an assertion "assert(!ret);" (Line676)?
> not allowing double registering and init?
> if double registering or initialization (provider), why not allowed just returning silently instead
> of aborting"? How about comments assert(!ret); ==>//assert(!ret); what is the side-effects
> of doing this?
This would be caused by having two different versions of .so with
conflicting provider name. This is usually a linking issue, and/or due
to the fact that your system has old/deprecated provider .so still
reachable.
If your system has only one version of the provider available, you would
not trigger double registering.
So I don't see how silently allowing multiple non-matching providers
(and using just the first one that happened to be loaded) would help
diagnosing bogus setups.
>
> 2) The other problem is in ./userspace-rcu-0.7.5/urcu/list.h Line85
>
> I have to add a guard "if" statement as the assertion in my program fails otherwise
>
> static inline void
> __cds_list_del (struct cds_list_head *prev, struct cds_list_head *next)
> {
> if (prev != NULL && next != NULL) {
> //assert(prev != NULL && next != NULL);
> next->prev = prev;
> prev->next = next;
> }
It might be caused by e.g. double registration issues I'm talking about,
now that you removed the assert in __lttng_events_init__.
You should verify which provider .so are reachable, and make sure you
don't try to load two different providers with the same name.
>
> 3) Now my instrumented prog is ready to run. Here is my commands:
> lttng create
> lttng enable-event -u -a
> lttng start
> ./prog
>
> The (lttng) instrumented prog is stuck there without any outputs
> related to lttng tracing, how can I know what happen inside.
> In other words, does lttng have any mechanism to trace itself?
Start with LTTNG_UST_DEBUG=1 env. var. set (see man 3 lttng-ust)
gdb is usually pretty good at letting us know the culprit of such a
hang. Recommendation: compile your program with CFLAGS="-O0 -g", and use
"thread apply all bt full" to see the stack of each thread.
Best regards,
Mathieu
>
> Thanks
>
> Yang
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug?
@ 2013-01-23 20:09 Yang Wang
0 siblings, 0 replies; 42+ messages in thread
From: Yang Wang @ 2013-01-23 20:09 UTC (permalink / raw)
To: lttng-dev; +Cc: Kenneth Kent, ,
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
Hello,
I am Yang Wang, I am currently using lttng to trace my JVM.
During my using lttng in tracing JVM, I found three problems,
1) in lttng-ust-2.1.0/include/lttng/ust-tracepoint-event.h
why using an assertion "assert(!ret);" (Line676)?
not allowing double registering and init?
if double registering or initialization (provider), why not allowed just returning silently instead
of aborting"? How about comments assert(!ret); ==>//assert(!ret); what is the side-effects
of doing this?
2) The other problem is in ./userspace-rcu-0.7.5/urcu/list.h Line85
I have to add a guard "if" statement as the assertion in my program fails otherwise
static inline void
__cds_list_del (struct cds_list_head *prev, struct cds_list_head *next)
{
if (prev != NULL && next != NULL) {
//assert(prev != NULL && next != NULL);
next->prev = prev;
prev->next = next;
}
3) Now my instrumented prog is ready to run. Here is my commands:
lttng create
lttng enable-event -u -a
lttng start
./prog
The (lttng) instrumented prog is stuck there without any outputs related to lttng tracing, how can I know what happen inside.
In other words, does lttng have any mechanism to trace itself?
Thanks
Yang
[-- Attachment #1.2: Type: text/html, Size: 2558 bytes --]
[-- Attachment #2: Type: text/plain, Size: 155 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2012-11-23 10:32 Dirk Winning
2012-11-23 16:46 ` Bug? George Dunlap
0 siblings, 1 reply; 42+ messages in thread
From: Dirk Winning @ 2012-11-23 10:32 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1600 bytes --]
root@graff:~# xm usb-list-assignable-devices
1-6 : ID 14dd:0002 Peppercon AG Multidevice
2-2 : ID 051d:0002 American Power Conversion Smart-UPS 3000 RM XL FW:691.16.I USB FW:7.3
root@graff:~# xm usb-hc-create bosch-w2k3-pv 1 1
root@graff:~# xm usb-list bosch-w2k3-pv
Idx BE state usb-ver BE-path
0 0 1 USB1.1 /local/domain/0/backend/vusb/55/0
port 1:
root@graff:~# xm usb-attach bosch-w2k3-pv 0 1 2-2
Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>
main.main(sys.argv)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main
_, rc = _run_cmd(cmd, cmd_name, args)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _run_cmd
return True, cmd(args)
File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 2868, in xm_usb_attach
if vusb_util.bus_is_assigned(bus):
File "/usr/lib/xen-4.0/lib/python/xen/util/vusb_util.py", line 275, in bus_is_assigned
raise UsbDeviceParseError("Can't get assignment status: (%s)." % bus)
xen.util.vusb_util.UsbDeviceParseError: vusb: Error parsing USB device info: Can't get assignment status: (2-2).
regards
Dipl. Ing. Dirk Winning, Systemberater
dirk.winning@junidas.de
junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart
Tel. +49 (711) 4599799-12, Fax +49 (711) 4599799-10
Geschäftsführer: Dr. Markus Stoll, Matthias Zepf
Amtsgericht Stuttgart, HRB 21939
[-- Attachment #1.2: Type: text/html, Size: 6999 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug?
2012-11-23 10:32 Bug? Dirk Winning
@ 2012-11-23 16:46 ` George Dunlap
0 siblings, 0 replies; 42+ messages in thread
From: George Dunlap @ 2012-11-23 16:46 UTC (permalink / raw)
To: Dirk Winning; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1960 bytes --]
On Fri, Nov 23, 2012 at 10:32 AM, Dirk Winning <dirk.winning@junidas.de>wrote:
> root@graff:~# xm usb-list-assignable-devices
> 1-6 : ID 14dd:0002 Peppercon AG Multidevice
> 2-2 : ID 051d:0002 American Power Conversion Smart-UPS 3000 RM XL
> FW:691.16.I USB FW:7.3
>
> root@graff:~# xm usb-hc-create bosch-w2k3-pv 1 1
>
> root@graff:~# xm usb-list bosch-w2k3-pv
> Idx BE state usb-ver BE-path
> 0 0 1 USB1.1 /local/domain/0/backend/vusb/55/0
> port 1:
>
> root@graff:~# xm usb-attach bosch-w2k3-pv 0 1 2-2
> Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
>
> Please report to xen-devel@lists.xensource.com
> Traceback (most recent call last):
> File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>
> main.main(sys.argv)
>
It looks like you're using Xen 4.0 -- have you tried 4.1 or 4.2?
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main
> _, rc = _run_cmd(cmd, cmd_name, args)
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _run_cmd
> return True, cmd(args)
> File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 2868, in
> xm_usb_attach
> if vusb_util.bus_is_assigned(bus):
> File "/usr/lib/xen-4.0/lib/python/xen/util/vusb_util.py", line 275, in
> bus_is_assigned
> raise UsbDeviceParseError("Can't get assignment status: (%s)." % bus)
> xen.util.vusb_util.UsbDeviceParseError: vusb: Error parsing USB device
> info: Can't get assignment status: (2-2).
>
>
>
> regards
>
> Dipl. Ing. Dirk Winning, Systemberater
> dirk.winning@junidas.de
>
> junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart
> Tel. +49 (711) 4599799-12, Fax +49 (711) 4599799-10
> Geschäftsführer: Dr. Markus Stoll, Matthias Zepf
> Amtsgericht Stuttgart, HRB 21939
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 5524 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug?
@ 2012-04-21 12:53 Thomas Weber
2012-04-24 15:26 ` bug? Josef Bacik
0 siblings, 1 reply; 42+ messages in thread
From: Thomas Weber @ 2012-04-21 12:53 UTC (permalink / raw)
To: linux-btrfs
Hello,
today my laptop crashed with the following output. Installed is
Archlinux with btrfs on a SSD.
Is it btrfs related?
Thanks,
Thomas
Apr 21 13:01:01 localhost anacron[3307]: Anacron started on 2012-04-21
Apr 21 13:01:01 localhost anacron[3307]: Will run job `cron.daily' in 48
min.
Apr 21 13:01:01 localhost anacron[3307]: Jobs will be executed sequentially
Apr 21 13:21:01 localhost -- MARK --
Apr 21 13:41:01 localhost -- MARK --
Apr 21 13:49:01 localhost anacron[3307]: Job `cron.daily' started
Apr 21 13:49:14 localhost kernel: [23420.297861] general protection
fault: 0000 [#1] PREEMPT SMP
Apr 21 13:49:14 localhost kernel: [23420.297976] CPU 1
Apr 21 13:49:14 localhost kernel: [23420.298007] Modules linked in:
nls_cp437 vfat fat usb_storage uas aes_x86_64 cryptd aes_generic fuse
ext4 jbd2 mbcache crc16 joydev arc4 dell_wmi sparse_keymap i915
snd_hda_codec_idt iwl3945 dell_laptop dcdbas iwl_legacy mac80211
snd_hda_intel i2c_algo_bit snd_hda_codec drm_kms_helper evdev snd_hwdep
snd_pcm drm serio_raw psmouse pcspkr tg3 snd_page_alloc cfg80211
snd_timer i2c_i801 iTCO_wdt iTCO_vendor_support snd i2c_core libphy
rfkill soundcore intel_agp intel_gtt wmi thermal button battery video
processor ac btrfs crc32c libcrc32c zlib_deflate sr_mod cdrom sd_mod
pata_acpi ata_generic ata_piix libata scsi_mod ehci_hcd uhci_hcd usbcore
usb_common
Apr 21 13:49:14 localhost kernel: [23420.299233]
Apr 21 13:49:14 localhost kernel: [23420.299262] Pid: 11172, comm:
updatedb Not tainted 3.2.11-1-ARCH #1 Dell Inc. Latitude
D530 /0HP728
Apr 21 13:49:14 localhost kernel: [23420.299410] RIP:
0010:[<ffffffffa0180ddd>] [<ffffffffa0180ddd>] btrfs_getattr+0x3d/0x90
[btrfs]
Apr 21 13:49:14 localhost kernel: [23420.299560] RSP:
0018:ffff880077765e38 EFLAGS: 00010206
Apr 21 13:49:14 localhost kernel: [23420.299630] RAX: 41d700000000fffe
RBX: ffff8800bf6c1550 RCX: 000000000000000c
Apr 21 13:49:14 localhost kernel: [23420.299717] RDX: ffff880077765f00
RSI: ffff880077765f00 RDI: ffff8800bf6c1550
Apr 21 13:49:14 localhost kernel: [23420.299804] RBP: ffff880077765e58
R08: ffffffff81173373 R09: ffff8800ba43bcf8
Apr 21 13:49:14 localhost kernel: [23420.299891] R10: ffff8800ba43bcc0
R11: 0000000000000005 R12: ffff880077765f00
Apr 21 13:49:14 localhost kernel: [23420.299978] R13: 0000000000001000
R14: ffff880077765f00 R15: 0000000001e54c50
Apr 21 13:49:14 localhost kernel: [23420.300067] FS:
00007f3e42b8f700(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
Apr 21 13:49:14 localhost kernel: [23420.300168] CS: 0010 DS: 0000 ES:
0000 CR0: 0000000080050033
Apr 21 13:49:14 localhost kernel: [23420.300240] CR2: 0000000001e71ffc
CR3: 0000000058685000 CR4: 00000000000006e0
Apr 21 13:49:14 localhost kernel: [23420.300327] DR0: 0000000000000000
DR1: 0000000000000000 DR2: 0000000000000000
Apr 21 13:49:14 localhost kernel: [23420.300414] DR3: 0000000000000000
DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 21 13:49:14 localhost kernel: [23420.300502] Process updatedb (pid:
11172, threadinfo ffff880077764000, task ffff88008a8023a0)
Apr 21 13:49:14 localhost kernel: [23420.300603] Stack:
Apr 21 13:49:14 localhost kernel: [23420.300635] ffff880077765f68
ffff8800ba43bcc0 ffff88011707bd00 ffff8800bf6c1550
Apr 21 13:49:14 localhost kernel: [23420.300753] ffff880077765e98
ffffffff8116c51e ffff880077765f00 0000000001e38319
Apr 21 13:49:14 localhost kernel: [23420.300869] ffff880077765f00
0000000001e38319 00007fffd821ca18 0000000000000000
Apr 21 13:49:14 localhost kernel: [23420.300985] Call Trace:
Apr 21 13:49:14 localhost kernel: [23420.301001] [<ffffffff8116c51e>]
vfs_getattr+0x4e/0x80
Apr 21 13:49:14 localhost kernel: [23420.301001] [<ffffffff8116c59e>]
vfs_fstatat+0x4e/0x70
Apr 21 13:49:14 localhost kernel: [23420.301001] [<ffffffff8116c5de>]
vfs_lstat+0x1e/0x20
Apr 21 13:49:14 localhost kernel: [23420.301001] [<ffffffff8116c77a>]
sys_newlstat+0x1a/0x40
Apr 21 13:49:14 localhost kernel: [23420.301001] [<ffffffff8145ddc2>]
system_call_fastpath+0x16/0x1b
Apr 21 13:49:14 localhost kernel: [23420.301001] Code: 6d f8 66 66 66 66
90 48 8b 5e 30 48 89 d6 49 89 d4 48 8b 43 28 48 89 df 44 8b 68 18 e8 5d
b2 fe e0 48 8b 83 60 fe ff ff 48 89 df <8b> 80 00 04 00 00 49 c7 44 24
58 00 10 00 00 41 89 44 24 08 e8
Apr 21 13:49:14 localhost kernel: [23420.301001] RIP
[<ffffffffa0180ddd>] btrfs_getattr+0x3d/0x90 [btrfs]
Apr 21 13:49:14 localhost kernel: [23420.301001] RSP <ffff880077765e38>
Apr 21 13:49:14 localhost anacron[3307]: Job `cron.daily' terminated
(exit status: 1) (mailing output)
Apr 21 13:49:14 localhost anacron[3307]: Can't find sendmail at
/usr/sbin/sendmail, not mailing output
Apr 21 13:49:14 localhost anacron[3307]: Normal exit (1 job run)
Apr 21 13:49:14 localhost kernel: [23420.365362] ---[ end trace
27dae2a049083cf1 ]---
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug?
2012-04-21 12:53 bug? Thomas Weber
@ 2012-04-24 15:26 ` Josef Bacik
2012-04-24 15:47 ` bug? Thomas Weber
0 siblings, 1 reply; 42+ messages in thread
From: Josef Bacik @ 2012-04-24 15:26 UTC (permalink / raw)
To: Thomas Weber; +Cc: linux-btrfs
On Sat, Apr 21, 2012 at 02:53:55PM +0200, Thomas Weber wrote:
> Hello,
>
> today my laptop crashed with the following output. Installed is
> Archlinux with btrfs on a SSD.
> Is it btrfs related?
Sort of an old kernel, can you try on something recent? It doesn't look
familiar but who knows. Thanks,
Josef
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug?
2012-04-24 15:26 ` bug? Josef Bacik
@ 2012-04-24 15:47 ` Thomas Weber
0 siblings, 0 replies; 42+ messages in thread
From: Thomas Weber @ 2012-04-24 15:47 UTC (permalink / raw)
To: Josef Bacik; +Cc: Thomas Weber, linux-btrfs
Hello Josef,
On 04/24/2012 05:26 PM, Josef Bacik wrote:
> On Sat, Apr 21, 2012 at 02:53:55PM +0200, Thomas Weber wrote:
>> Hello,
>>
>> today my laptop crashed with the following output. Installed is
>> Archlinux with btrfs on a SSD.
>> Is it btrfs related?
> Sort of an old kernel, can you try on something recent? It doesn't look
> familiar but who knows. Thanks,
>
> Josef
I was on the 3.2 kernel because of the enospc problem. Today I updated
to 3.3.3 kernel.
Thomas
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2011-11-23 9:18 Kormos 'Morc' Gábor
2012-03-22 11:07 ` Bug? Kormos 'Morc' Gábor
0 siblings, 1 reply; 42+ messages in thread
From: Kormos 'Morc' Gábor @ 2011-11-23 9:18 UTC (permalink / raw)
To: linux-crypto
Hi Guys,
Sorry if I post this on the wrong list, but don't know who this
belongs to and first time trying to post a kernel bug. Please direct me
to the list it's appropriate on if it's not this or let me know if this
may be an OpenSWAN bug and not a kernel.
So I run a few virtual machines on Windows 7 x64 on Intel Core
i5-2500 CPU, now running with kernel 3.2.0-rc2 based on the Ubuntu 11.10
x86 kernel config file. I use OpenSWAN 2.6.28+dfsg-5ubuntu2 to build a
VPN link between two nodes and those two nodes only, no subnets on
either side and the moment I try to ping or connection from one server
to the other kernel panics and CapsLock and ScrollLock LEDs on keyboard
start flashing and get the kernel trace below. I tried with the PCNet32
equivalent VMWare network card as well, without any difference. I'm
running VMWare Workstation 8.0.1 build 528992. If you need more info let
me know.
Please advise,
Gabor 'Morc' Kormos.
[ 35.219366] general protection fault: 0000 [#1] SMP
[ 35.221892] Modules linked in: authenc deflate zlib_deflate ctr
camellia cast5 rmd160 crypto_null ccm serpent blowfish_generic
blowfish_common twofish_generic twofish_i586 twofish_common xcbc
sha512_generic des_generic aesni_intel cryptd aes_i586 xfrm_user ah6 ah4
esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel
xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro xfrm6_mode_beet
xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp xfrm6_tunnel tunnel6 af_key
xt_tcpudp xt_policy iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
nf_defrag_ipv4 iptable_filter ip_tables x_tables ppdev vmw_balloon
psmouse serio_raw parport_pc i2c_piix4 shpchp lp parport floppy e1000
mptspi mptscsih mptbase
[ 35.254720]
[ 35.255400] Pid: 0, comm: swapper Not tainted 3.2.0-rc2 #1 VMware,
Inc. VMware Virtual Platform/440BX Desktop Reference Platform
[ 35.260348] EIP: 0060:[<e0a238c0>] EFLAGS: 00010293 CPU: 0
[ 35.262785] EIP is at aesni_cbc_dec+0x5c/0xbc [aesni_intel]
[ 35.264201] EAX: c77a3a7a EBX: 00000010 ECX: d0621950 EDX: c77a3a7a
[ 35.265612] ESI: 00000060 EDI: d0621920 EBP: c77a3a6a ESP: d840dc3c
[ 35.267010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 35.268215] Process swapper (pid: 0, ti=d840c000 task=c08b1020
task.ti=c08aa000)
[ 35.269849] Stack:
[ 35.270330] d840dcbc 00000060 00000000 d840dcb0 e0a24161 d0621830
c77a3a7a c77a3a7a
[ 35.272475] 00000060 c77a3a6a d0621830 dfbcf460 c77a3a7a dfbcf460
c77a3a7a d06211fc
[ 35.274645] 00000a7a 00000060 d06211fc 00000a7a 00000060 00000000
00000000 c77a3a6a
[ 35.276811] Call Trace:
[ 35.277454] [<e0a24161>] ? cbc_decrypt+0xe1/0x130 [aesni_intel]
[ 35.278834] [<c0380c60>] ? scatterwalk_done+0x40/0x50
[ 35.280381] [<e0a23d44>] ? ablk_decrypt+0xc4/0xd0 [aesni_intel]
[ 35.281750] [<e0aaae65>] ? crypto_authenc_decrypt+0x145/0x2fc [authenc]
[ 35.283292] [<e09dd917>] ? esp_input+0x167/0x2d0 [esp4]
[ 35.284501] [<c05ff445>] ? xfrm_input+0x3e5/0x430
[ 35.285599] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
[ 35.286752] [<c05f6255>] ? xfrm4_rcv_encap+0x25/0x30
[ 35.287905] [<c05f6283>] ? xfrm4_rcv+0x23/0x30
[ 35.288947] [<c05b0677>] ? ip_local_deliver_finish+0xa7/0x290
[ 35.290270] [<c05b09ef>] ? ip_local_deliver+0x7f/0x90
[ 35.291443] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
[ 35.292593] [<c05b0363>] ? ip_rcv_finish+0x113/0x380
[ 35.294538] [<c05b0c43>] ? ip_rcv+0x243/0x310
[ 35.296568] [<c05b0250>] ? inet_del_protocol+0x30/0x30
[ 35.298762] [<c05841aa>] ? __netif_receive_skb+0x45a/0x500
[ 35.301071] [<c0584baf>] ? netif_receive_skb+0x6f/0x80
[ 35.303252] [<c0584f03>] ? dev_gro_receive+0x163/0x240
[ 35.305442] [<c0584cd7>] ? napi_skb_finish+0x37/0x50
[ 35.307668] [<c0585141>] ? napi_gro_receive+0xa1/0xb0
[ 35.310577] [<e085b75c>] ? e1000_clean_rx_irq+0x20c/0x3b0 [e1000]
[ 35.313119] [<c0141898>] ? ttwu_do_wakeup+0x28/0x130
[ 35.315223] [<e085cd84>] ? e1000_clean+0x184/0x490 [e1000]
[ 35.317596] [<c016f9ec>] ? __queue_work+0xcc/0x390
[ 35.319625] [<c058530d>] ? net_rx_action+0x10d/0x220
[ 35.321912] [<c016fcb0>] ? __queue_work+0x390/0x390
[ 35.324149] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.325384] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.326587] [<c015e171>] ? __do_softirq+0x81/0x1a0
[ 35.327697] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.328905] <IRQ>
[ 35.329477] [<c015e4b6>] ? irq_exit+0x76/0xa0
[ 35.330495] [<c0677fdb>] ? do_IRQ+0x4b/0xc0
[ 35.331475] [<c015e4a0>] ? irq_exit+0x60/0xa0
[ 35.332490] [<c06780a9>] ? smp_apic_timer_interrupt+0x59/0x88
[ 35.333803] [<c0677e30>] ? common_interrupt+0x30/0x38
[ 35.334974] [<c013439a>] ? native_safe_halt+0xa/0x10
[ 35.336198] [<c011802e>] ? default_idle+0x5e/0x110
[ 35.337336] [<c0110358>] ? cpu_idle+0xa8/0xe0
[ 35.338396] [<c064aa45>] ? rest_init+0x5d/0x68
[ 35.339448] [<c091979d>] ? start_kernel+0x357/0x35d
[ 35.340581] [<c09191d7>] ? loglevel+0x2b/0x2b
[ 35.341606] [<c09190ba>] ? i386_start_kernel+0xa9/0xaf
[ 35.342789] Code: 83 fe 40 72 5a 66 90 0f 10 0a 0f 28 c1 0f 10 7a 10
0f 28 e7 0f 10 4a 20 0f 28 e9 0f 10 7a 30 0f 28 f7 e8 d8 fc ff ff 66 0f
ef c3
[ 35.347966] 0f ef 22 66 0f ef 6a 10 66 0f ef f1 0f 28 df 0f 11 00 0f 11
[ 35.350719] EIP: [<e0a238c0>] aesni_cbc_dec+0x5c/0xbc [aesni_intel]
SS:ESP 0068:d840dc3c
[ 35.353175] ---[ end trace 5b7cd1586950280a ]---
[ 35.354312] Kernel panic - not syncing: Fatal exception in interrupt
[ 35.355852] Pid: 0, comm: swapper Tainted: G D 3.2.0-rc2 #1
[ 35.357403] Call Trace:
[ 35.358043] [<c0668079>] ? printk+0x2d/0x2f
[ 35.359099] [<c0667f4e>] panic+0x5c/0x15a
[ 35.360117] [<c0671c6d>] oops_end+0xcd/0xd0
[ 35.361188] [<c0113e14>] die+0x54/0x80
[ 35.362147] [<c0671832>] do_general_protection+0x102/0x180
[ 35.363504] [<c03837bd>] ? blkcipher_walk_next+0x1ad/0x3c0
[ 35.364858] [<c0671730>] ? do_trap+0xd0/0xd0
[ 35.366014] [<c0671487>] error_code+0x67/0x6c
[ 35.367117] [<c038007b>] ? crypto_attr_alg2+0x2b/0x40
[ 35.368370] [<e0a238c0>] ? aesni_cbc_dec+0x5c/0xbc [aesni_intel]
[ 35.369836] [<e0a24161>] ? cbc_decrypt+0xe1/0x130 [aesni_intel]
[ 35.371291] [<c0380c60>] ? scatterwalk_done+0x40/0x50
[ 35.372540] [<e0a23d44>] ? ablk_decrypt+0xc4/0xd0 [aesni_intel]
[ 35.374004] [<e0aaae65>] ? crypto_authenc_decrypt+0x145/0x2fc [authenc]
[ 35.375652] [<e09dd917>] ? esp_input+0x167/0x2d0 [esp4]
[ 35.376954] [<c05ff445>] ? xfrm_input+0x3e5/0x430
[ 35.378173] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
[ 35.379406] [<c05f6255>] ? xfrm4_rcv_encap+0x25/0x30
[ 35.380657] [<c05f6283>] ? xfrm4_rcv+0x23/0x30
[ 35.381776] [<c05b0677>] ? ip_local_deliver_finish+0xa7/0x290
[ 35.383205] [<c05b09ef>] ? ip_local_deliver+0x7f/0x90
[ 35.384455] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
[ 35.385722] [<c05b0363>] ? ip_rcv_finish+0x113/0x380
[ 35.386967] [<c05b0c43>] ? ip_rcv+0x243/0x310
[ 35.388108] [<c05b0250>] ? inet_del_protocol+0x30/0x30
[ 35.389387] [<c05841aa>] ? __netif_receive_skb+0x45a/0x500
[ 35.390751] [<c0584baf>] ? netif_receive_skb+0x6f/0x80
[ 35.392033] [<c0584f03>] ? dev_gro_receive+0x163/0x240
[ 35.393305] [<c0584cd7>] ? napi_skb_finish+0x37/0x50
[ 35.394560] [<c0585141>] ? napi_gro_receive+0xa1/0xb0
[ 35.395907] [<e085b75c>] ? e1000_clean_rx_irq+0x20c/0x3b0 [e1000]
[ 35.397441] [<c0141898>] ? ttwu_do_wakeup+0x28/0x130
[ 35.398679] [<e085cd84>] ? e1000_clean+0x184/0x490 [e1000]
[ 35.400030] [<c016f9ec>] ? __queue_work+0xcc/0x390
[ 35.401222] [<c058530d>] ? net_rx_action+0x10d/0x220
[ 35.402464] [<c016fcb0>] ? __queue_work+0x390/0x390
[ 35.403682] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.404986] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.406324] [<c015e171>] ? __do_softirq+0x81/0x1a0
[ 35.407608] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
[ 35.408933] <IRQ> [<c015e4b6>] ? irq_exit+0x76/0xa0
[ 35.410250] [<c0677fdb>] ? do_IRQ+0x4b/0xc0
[ 35.411305] [<c015e4a0>] ? irq_exit+0x60/0xa0
[ 35.412400] [<c06780a9>] ? smp_apic_timer_interrupt+0x59/0x88
[ 35.413788] [<c0677e30>] ? common_interrupt+0x30/0x38
[ 35.414955] [<c013439a>] ? native_safe_halt+0xa/0x10
[ 35.416111] [<c011802e>] ? default_idle+0x5e/0x110
[ 35.417228] [<c0110358>] ? cpu_idle+0xa8/0xe0
[ 35.418251] [<c064aa45>] ? rest_init+0x5d/0x68
[ 35.419559] [<c091979d>] ? start_kernel+0x357/0x35d
[ 35.420696] [<c09191d7>] ? loglevel+0x2b/0x2b
[ 35.421721] [<c09190ba>] ? i386_start_kernel+0xa9/0xaf
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug?
2011-11-23 9:18 Bug? Kormos 'Morc' Gábor
@ 2012-03-22 11:07 ` Kormos 'Morc' Gábor
0 siblings, 0 replies; 42+ messages in thread
From: Kormos 'Morc' Gábor @ 2012-03-22 11:07 UTC (permalink / raw)
To: linux-crypto
Anyone cares to give me some feedback on this?
Thanks,
Morc.
Kormos 'Morc' Gábor wrote:
> Hi Guys,
>
> Sorry if I post this on the wrong list, but don't know who this
> belongs to and first time trying to post a kernel bug. Please direct
> me to the list it's appropriate on if it's not this or let me know if
> this may be an OpenSWAN bug and not a kernel.
>
> So I run a few virtual machines on Windows 7 x64 on Intel Core
> i5-2500 CPU, now running with kernel 3.2.0-rc2 based on the Ubuntu
> 11.10 x86 kernel config file. I use OpenSWAN 2.6.28+dfsg-5ubuntu2 to
> build a VPN link between two nodes and those two nodes only, no
> subnets on either side and the moment I try to ping or connection from
> one server to the other kernel panics and CapsLock and ScrollLock LEDs
> on keyboard start flashing and get the kernel trace below. I tried
> with the PCNet32 equivalent VMWare network card as well, without any
> difference. I'm running VMWare Workstation 8.0.1 build 528992. If you
> need more info let me know.
>
> Please advise,
>
> Gabor 'Morc' Kormos.
>
> [ 35.219366] general protection fault: 0000 [#1] SMP
> [ 35.221892] Modules linked in: authenc deflate zlib_deflate ctr
> camellia cast5 rmd160 crypto_null ccm serpent blowfish_generic
> blowfish_common twofish_generic twofish_i586 twofish_common xcbc
> sha512_generic des_generic aesni_intel cryptd aes_i586 xfrm_user ah6
> ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel
> xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro
> xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp
> xfrm6_tunnel tunnel6 af_key xt_tcpudp xt_policy iptable_nat nf_nat
> nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables
> x_tables ppdev vmw_balloon psmouse serio_raw parport_pc i2c_piix4
> shpchp lp parport floppy e1000 mptspi mptscsih mptbase
> [ 35.254720]
> [ 35.255400] Pid: 0, comm: swapper Not tainted 3.2.0-rc2 #1 VMware,
> Inc. VMware Virtual Platform/440BX Desktop Reference Platform
> [ 35.260348] EIP: 0060:[<e0a238c0>] EFLAGS: 00010293 CPU: 0
> [ 35.262785] EIP is at aesni_cbc_dec+0x5c/0xbc [aesni_intel]
> [ 35.264201] EAX: c77a3a7a EBX: 00000010 ECX: d0621950 EDX: c77a3a7a
> [ 35.265612] ESI: 00000060 EDI: d0621920 EBP: c77a3a6a ESP: d840dc3c
> [ 35.267010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> [ 35.268215] Process swapper (pid: 0, ti=d840c000 task=c08b1020
> task.ti=c08aa000)
> [ 35.269849] Stack:
> [ 35.270330] d840dcbc 00000060 00000000 d840dcb0 e0a24161 d0621830
> c77a3a7a c77a3a7a
> [ 35.272475] 00000060 c77a3a6a d0621830 dfbcf460 c77a3a7a dfbcf460
> c77a3a7a d06211fc
> [ 35.274645] 00000a7a 00000060 d06211fc 00000a7a 00000060 00000000
> 00000000 c77a3a6a
> [ 35.276811] Call Trace:
> [ 35.277454] [<e0a24161>] ? cbc_decrypt+0xe1/0x130 [aesni_intel]
> [ 35.278834] [<c0380c60>] ? scatterwalk_done+0x40/0x50
> [ 35.280381] [<e0a23d44>] ? ablk_decrypt+0xc4/0xd0 [aesni_intel]
> [ 35.281750] [<e0aaae65>] ? crypto_authenc_decrypt+0x145/0x2fc
> [authenc]
> [ 35.283292] [<e09dd917>] ? esp_input+0x167/0x2d0 [esp4]
> [ 35.284501] [<c05ff445>] ? xfrm_input+0x3e5/0x430
> [ 35.285599] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
> [ 35.286752] [<c05f6255>] ? xfrm4_rcv_encap+0x25/0x30
> [ 35.287905] [<c05f6283>] ? xfrm4_rcv+0x23/0x30
> [ 35.288947] [<c05b0677>] ? ip_local_deliver_finish+0xa7/0x290
> [ 35.290270] [<c05b09ef>] ? ip_local_deliver+0x7f/0x90
> [ 35.291443] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
> [ 35.292593] [<c05b0363>] ? ip_rcv_finish+0x113/0x380
> [ 35.294538] [<c05b0c43>] ? ip_rcv+0x243/0x310
> [ 35.296568] [<c05b0250>] ? inet_del_protocol+0x30/0x30
> [ 35.298762] [<c05841aa>] ? __netif_receive_skb+0x45a/0x500
> [ 35.301071] [<c0584baf>] ? netif_receive_skb+0x6f/0x80
> [ 35.303252] [<c0584f03>] ? dev_gro_receive+0x163/0x240
> [ 35.305442] [<c0584cd7>] ? napi_skb_finish+0x37/0x50
> [ 35.307668] [<c0585141>] ? napi_gro_receive+0xa1/0xb0
> [ 35.310577] [<e085b75c>] ? e1000_clean_rx_irq+0x20c/0x3b0 [e1000]
> [ 35.313119] [<c0141898>] ? ttwu_do_wakeup+0x28/0x130
> [ 35.315223] [<e085cd84>] ? e1000_clean+0x184/0x490 [e1000]
> [ 35.317596] [<c016f9ec>] ? __queue_work+0xcc/0x390
> [ 35.319625] [<c058530d>] ? net_rx_action+0x10d/0x220
> [ 35.321912] [<c016fcb0>] ? __queue_work+0x390/0x390
> [ 35.324149] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.325384] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.326587] [<c015e171>] ? __do_softirq+0x81/0x1a0
> [ 35.327697] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.328905] <IRQ>
> [ 35.329477] [<c015e4b6>] ? irq_exit+0x76/0xa0
> [ 35.330495] [<c0677fdb>] ? do_IRQ+0x4b/0xc0
> [ 35.331475] [<c015e4a0>] ? irq_exit+0x60/0xa0
> [ 35.332490] [<c06780a9>] ? smp_apic_timer_interrupt+0x59/0x88
> [ 35.333803] [<c0677e30>] ? common_interrupt+0x30/0x38
> [ 35.334974] [<c013439a>] ? native_safe_halt+0xa/0x10
> [ 35.336198] [<c011802e>] ? default_idle+0x5e/0x110
> [ 35.337336] [<c0110358>] ? cpu_idle+0xa8/0xe0
> [ 35.338396] [<c064aa45>] ? rest_init+0x5d/0x68
> [ 35.339448] [<c091979d>] ? start_kernel+0x357/0x35d
> [ 35.340581] [<c09191d7>] ? loglevel+0x2b/0x2b
> [ 35.341606] [<c09190ba>] ? i386_start_kernel+0xa9/0xaf
> [ 35.342789] Code: 83 fe 40 72 5a 66 90 0f 10 0a 0f 28 c1 0f 10 7a
> 10 0f 28 e7 0f 10 4a 20 0f 28 e9 0f 10 7a 30 0f 28 f7 e8 d8 fc ff ff
> 66 0f ef c3
> [ 35.347966] 0f ef 22 66 0f ef 6a 10 66 0f ef f1 0f 28 df 0f 11 00
> 0f 11
> [ 35.350719] EIP: [<e0a238c0>] aesni_cbc_dec+0x5c/0xbc [aesni_intel]
> SS:ESP 0068:d840dc3c
> [ 35.353175] ---[ end trace 5b7cd1586950280a ]---
> [ 35.354312] Kernel panic - not syncing: Fatal exception in interrupt
> [ 35.355852] Pid: 0, comm: swapper Tainted: G D 3.2.0-rc2 #1
> [ 35.357403] Call Trace:
> [ 35.358043] [<c0668079>] ? printk+0x2d/0x2f
> [ 35.359099] [<c0667f4e>] panic+0x5c/0x15a
> [ 35.360117] [<c0671c6d>] oops_end+0xcd/0xd0
> [ 35.361188] [<c0113e14>] die+0x54/0x80
> [ 35.362147] [<c0671832>] do_general_protection+0x102/0x180
> [ 35.363504] [<c03837bd>] ? blkcipher_walk_next+0x1ad/0x3c0
> [ 35.364858] [<c0671730>] ? do_trap+0xd0/0xd0
> [ 35.366014] [<c0671487>] error_code+0x67/0x6c
> [ 35.367117] [<c038007b>] ? crypto_attr_alg2+0x2b/0x40
> [ 35.368370] [<e0a238c0>] ? aesni_cbc_dec+0x5c/0xbc [aesni_intel]
> [ 35.369836] [<e0a24161>] ? cbc_decrypt+0xe1/0x130 [aesni_intel]
> [ 35.371291] [<c0380c60>] ? scatterwalk_done+0x40/0x50
> [ 35.372540] [<e0a23d44>] ? ablk_decrypt+0xc4/0xd0 [aesni_intel]
> [ 35.374004] [<e0aaae65>] ? crypto_authenc_decrypt+0x145/0x2fc
> [authenc]
> [ 35.375652] [<e09dd917>] ? esp_input+0x167/0x2d0 [esp4]
> [ 35.376954] [<c05ff445>] ? xfrm_input+0x3e5/0x430
> [ 35.378173] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
> [ 35.379406] [<c05f6255>] ? xfrm4_rcv_encap+0x25/0x30
> [ 35.380657] [<c05f6283>] ? xfrm4_rcv+0x23/0x30
> [ 35.381776] [<c05b0677>] ? ip_local_deliver_finish+0xa7/0x290
> [ 35.383205] [<c05b09ef>] ? ip_local_deliver+0x7f/0x90
> [ 35.384455] [<c05b05d0>] ? ip_rcv_finish+0x380/0x380
> [ 35.385722] [<c05b0363>] ? ip_rcv_finish+0x113/0x380
> [ 35.386967] [<c05b0c43>] ? ip_rcv+0x243/0x310
> [ 35.388108] [<c05b0250>] ? inet_del_protocol+0x30/0x30
> [ 35.389387] [<c05841aa>] ? __netif_receive_skb+0x45a/0x500
> [ 35.390751] [<c0584baf>] ? netif_receive_skb+0x6f/0x80
> [ 35.392033] [<c0584f03>] ? dev_gro_receive+0x163/0x240
> [ 35.393305] [<c0584cd7>] ? napi_skb_finish+0x37/0x50
> [ 35.394560] [<c0585141>] ? napi_gro_receive+0xa1/0xb0
> [ 35.395907] [<e085b75c>] ? e1000_clean_rx_irq+0x20c/0x3b0 [e1000]
> [ 35.397441] [<c0141898>] ? ttwu_do_wakeup+0x28/0x130
> [ 35.398679] [<e085cd84>] ? e1000_clean+0x184/0x490 [e1000]
> [ 35.400030] [<c016f9ec>] ? __queue_work+0xcc/0x390
> [ 35.401222] [<c058530d>] ? net_rx_action+0x10d/0x220
> [ 35.402464] [<c016fcb0>] ? __queue_work+0x390/0x390
> [ 35.403682] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.404986] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.406324] [<c015e171>] ? __do_softirq+0x81/0x1a0
> [ 35.407608] [<c015e0f0>] ? local_bh_enable_ip+0x90/0x90
> [ 35.408933] <IRQ> [<c015e4b6>] ? irq_exit+0x76/0xa0
> [ 35.410250] [<c0677fdb>] ? do_IRQ+0x4b/0xc0
> [ 35.411305] [<c015e4a0>] ? irq_exit+0x60/0xa0
> [ 35.412400] [<c06780a9>] ? smp_apic_timer_interrupt+0x59/0x88
> [ 35.413788] [<c0677e30>] ? common_interrupt+0x30/0x38
> [ 35.414955] [<c013439a>] ? native_safe_halt+0xa/0x10
> [ 35.416111] [<c011802e>] ? default_idle+0x5e/0x110
> [ 35.417228] [<c0110358>] ? cpu_idle+0xa8/0xe0
> [ 35.418251] [<c064aa45>] ? rest_init+0x5d/0x68
> [ 35.419559] [<c091979d>] ? start_kernel+0x357/0x35d
> [ 35.420696] [<c09191d7>] ? loglevel+0x2b/0x2b
> [ 35.421721] [<c09190ba>] ? i386_start_kernel+0xa9/0xaf
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug ;(
@ 2010-02-26 11:15 Ян Программист
0 siblings, 0 replies; 42+ messages in thread
From: Ян Программист @ 2010-02-26 11:15 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 3186 bytes --]
Hi people. Having a bug. Please anyone help me to resolve it. When trying to
activate xend debug following errors appeared:
mkdir: cannot create directory `/dev/shm/sysconfig/xenbridges': No such
file or directory
[xend] WARNING (XendAPI:701) API call: VBD.set_device not found
[xend] WARNING (XendAPI:701) API call: VBD.set_type not found
[xend] WARNING (XendAPI:701) API call: session.get_all_records not found
[xend] WARNING (XendAPI:701) API call: event.get_record not found
[xend] WARNING (XendAPI:701) API call: event.get_all not found
[xend] WARNING (XendAPI:701) API call: VIF.get_network not found
[xend] WARNING (XendAPI:701) API call: VIF.set_device not found
[xend] WARNING (XendAPI:701) API call: VIF.set_MAC not found
[xend] WARNING (XendAPI:701) API call: VIF.set_MTU not found
[xend] WARNING (XendAPI:701) API call: debug.get_all not found
No configuration found for eth0
Nevertheless the interface will be shut down.
Exception in thread UnixHttpServer:
Traceback (most recent call last):
File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner
self.run()
File "/usr/lib64/python2.6/threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib64/python2.6/site-packages/xen/web/httpserver.py", line 312,
in run
(sock, addr) = self.accept()
File "/usr/lib64/python2.6/site-packages/xen/web/httpserver.py", line 331,
in accept
return self.socket.accept()
File "/usr/lib64/python2.6/socket.py", line 195, in accept
sock, addr = self._sock.accept()
error: [Errno 22] Invalid argument
[2010-02-25 10:17:37 3105] DEBUG (XendDomain:453) Adding Domain: 0
[2010-02-25 10:17:37 3105] DEBUG (XendDomainInfo:1733)
XendDomainInfo.handleShutdownWatch
[2010-02-25 10:17:37 3105] DEBUG (XendDomain:387) number of vcpus to use is
0
[2010-02-25 10:17:37 3105] INFO (SrvServer:178) unix
path=/var/lib/xend/xend-socket
[2010-02-25 10:17:37 3105] ERROR (SrvDaemon:341) Exception starting xend ()
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line
341, in run
servers = SrvServer.create()
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py", line
256, in create
_loadConfig(servers, root, False)
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py", line
225, in _loadConfig
hosts_allowed = hosts_allowed))
File "/usr/lib64/python2.6/site-packages/xen/xend/server/XMLRPCServer.py",
line 119, in __init__
self.xenapi = use_xenapi and XendAPI.XendAPI(auth) or None
File "/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py", line 541, in
__new__
cls._decorate()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py", line 743, in
_decorate
dtor_event_wrapper(api_cls)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py", line 671, in
dtor_event_wrapper
wrap_method(
File "/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py", line 671, in
dtor_event_wrapper
wrap_method(
File "/usr/lib64/python2.6/bdb.py", line 46, in trace_dispatch
return self.dispatch_line(frame)
File "/usr/lib64/python2.6/bdb.py", line 65, in dispatch_line
if self.quitting: raise BdbQuit
BdbQuit
[-- Attachment #1.2: Type: text/html, Size: 10287 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug:
@ 2009-08-12 22:07 Dennis Gilmore
0 siblings, 0 replies; 42+ messages in thread
From: Dennis Gilmore @ 2009-08-12 22:07 UTC (permalink / raw)
To: sparclinux
[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]
On one of my netra X1's that i just updated to the F-12 rawhide tree i got the
following
uname -a
Linux thor.ausil.us 2.6.31-0.149.rc5.git3.fc12.sparc64 #1 SMP Wed Aug 12
03:02:38 UTC 2009 sparc64 sparc64 sparc64 GNU/Linux
We disabled the -smp kernel and are now only building a smp kernel. the netra
has only a single cpu
BUG: spinlock bad magic on CPU#0, swapper/1 (Not tainted)
lock: fffff8006f2ce528, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
Call Trace:
[0000000000650f58] spin_bug+0x8c/0x9c
[0000000000651030] _raw_spin_lock+0x24/0x150
[000000000084a30c] _spin_lock_bh+0x14/0x24
[0000000000794d28] alloc_netdev_mq+0xf0/0x288
[00000000006f49b4] loopback_net_init+0x20/0x84
[000000000078d064] register_pernet_operations+0x38/0xe0
[000000000078d128] register_pernet_device+0x1c/0x5c
[0000000000aaef04] net_dev_init+0x174/0x1f4
[0000000000426d30] do_one_initcall+0x5c/0x188
[0000000000a8e3a4] kernel_init+0x238/0x29c
[000000000042b550] kernel_thread+0x38/0x50
[0000000000832c1c] rest_init+0x18/0x80
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 42+ messages in thread
* BUG?
@ 2008-08-23 16:17 Mateyko
2008-08-25 21:35 ` BUG? Luis R. Rodriguez
0 siblings, 1 reply; 42+ messages in thread
From: Mateyko @ 2008-08-23 16:17 UTC (permalink / raw)
To: linux-wireless
Here is output from console after typing "make"
mateyko@********:~/Pulpit/compat-wireless-2008-08-06$ make
/home/mateyko/Pulpit/compat-wireless-2008-08-06/config.mk:30: *** "ERROR: There is a bug with compat-wireless on 2.6.22. Remove me if you want to fix me". Stop.
mateyko@********:~/Pulpit/compat-wireless-2008-08-06$ make install
/home/mateyko/Pulpit/compat-wireless-2008-08-06/config.mk:30: *** "ERROR: There is a bug with compat-wireless on 2.6.22. Remove me if you want to fix me". Stop.
mateyko@********:~/Pulpit/compat-wireless-2008-08-06$
Btw i don't know how to use mailing list so any reply send to: mateyko5(at)o2.pl or mateyko(at)mateyko.net
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG?
2008-08-23 16:17 BUG? Mateyko
@ 2008-08-25 21:35 ` Luis R. Rodriguez
0 siblings, 0 replies; 42+ messages in thread
From: Luis R. Rodriguez @ 2008-08-25 21:35 UTC (permalink / raw)
To: Mateyko; +Cc: linux-wireless
On Sat, Aug 23, 2008 at 09:17:46AM -0700, Mateyko wrote:
> Here is output from console after typing "make"
>
>
> mateyko@********:~/Pulpit/compat-wireless-2008-08-06$ make
> /home/mateyko/Pulpit/compat-wireless-2008-08-06/config.mk:30: *** "ERROR: There is a bug with compat-wireless on 2.6.22. Remove me if you want to fix me". Stop.
> mateyko@********:~/Pulpit/compat-wireless-2008-08-06$ make install
> /home/mateyko/Pulpit/compat-wireless-2008-08-06/config.mk:30: *** "ERROR: There is a bug with compat-wireless on 2.6.22. Remove me if you want to fix me". Stop.
> mateyko@********:~/Pulpit/compat-wireless-2008-08-06$
>
>
> Btw i don't know how to use mailing list so any reply send to: mateyko5(at)o2.pl or mateyko(at)mateyko.net
The error indicates there is an oops (crash) you will get with
compat-wireless right now if you try to use it on 2.6.22. If someone
wants to fix it the bug then they can enable 2.6.22 support in
compat-wireless. I just haven't had time for this.
Luis
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2007-04-01 13:39 Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
0 siblings, 1 reply; 42+ messages in thread
From: Sascha Curth @ 2007-04-01 13:39 UTC (permalink / raw)
To: linux-kernel
Hi,
i hav essen this in my logfiles. The server wasn't rechable any more and
a hard reset was needed....
Kernel: 2.6.18
Logfile:
Mar 29 22:18:07 seven ------------[ cut here ]------------
Mar 29 22:18:07 seven kernel BUG at mm/rmap.c:522!
Mar 29 22:18:07 seven invalid opcode: 0000 [#1]
Mar 29 22:18:07 seven SMP
Mar 29 22:18:07 seven Modules linked in: capi capifs st fcdsl
Mar 29 22:18:07 seven CPU: 0
Mar 29 22:18:07 seven EIP: 0060:[<c0151a46>] Tainted: P S VLI
Mar 29 22:18:07 seven EFLAGS: 00210286 (2.6.18-gentoo-r3 #1)
Mar 29 22:18:07 seven EIP is at page_remove_rmap+0x26/0x30
Mar 29 22:18:07 seven eax: ffffffff ebx: d54dda88 ecx: c1ffaa40
edx: 00000000
Mar 29 22:18:07 seven esi: c1ffaa40 edi: b7ea2000 ebp: b7ea4000
esp: ca969edc
Mar 29 22:18:07 seven ds: 007b es: 007b ss: 0068
Mar 29 22:18:07 seven Process exim (pid: 14060, ti=ca968000
task=f6565580 task.ti=ca968000)
Mar 29 22:18:07 seven Stack: c014bb06 00000000 f639af98 ca969f48
00000000 00000001 d6f50b7c f7c1a900
Mar 29 22:18:07 seven c200be20 00000000 fffffffc c12a9bac d6f50b7c
7fd52025 b7ea3fff 00294bfc
Mar 29 22:18:07 seven b7ea4000 00000000 ca969f48 dd471128 f7c1a900
ca968000 c014e989 ffffffff
Mar 29 22:18:07 seven Call Trace:
Mar 29 22:18:07 seven [<c014bb06>] unmap_vmas+0x286/0x520
Mar 29 22:18:07 seven [<c014e989>] exit_mmap+0x79/0x100
Mar 29 22:18:07 seven [<c011b9c3>] mmput+0x33/0xa0
Mar 29 22:18:07 seven [<c0120c23>] do_exit+0xf3/0x8b0
Mar 29 22:18:07 seven [<c01126b7>] do_page_fault+0xe7/0x5ab
Mar 29 22:18:07 seven [<c0121413>] do_group_exit+0x33/0x90
Mar 29 22:18:07 seven [<c0102e2d>] sysenter_past_esp+0x56/0x79
Mar 29 22:18:07 seven Code: bf 00 00 00 00 89 c1 90 83 40 08 ff 0f 98 c0
84 c0 75 02 f3 c3 8b 41 08 40 78 10 8b 51 10 89 c8 83 f2 01 83 e2 01 e9
ba 81 ff f
f <0f> 0b 0a 02 88 90 51 c0 eb e6 83 ec 20 89 74 24 14 89 d6 89 5c
Mar 29 22:18:07 seven EIP: [<c0151a46>] page_remove_rmap+0x26/0x30
SS:ESP 0068:ca969edc
Mar 29 22:18:07 seven <1>Fixing recursive fault but reboot is needed!
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug?
2007-04-01 13:39 Bug? Sascha Curth
@ 2007-04-01 13:54 ` Michal Piotrowski
0 siblings, 0 replies; 42+ messages in thread
From: Michal Piotrowski @ 2007-04-01 13:54 UTC (permalink / raw)
To: info; +Cc: linux-kernel
Hi,
On 01/04/07, Sascha Curth <info@sascha-curth.de> wrote:
> Hi,
>
> i hav essen this in my logfiles. The server wasn't rechable any more and
> a hard reset was needed....
Yes, that's a bug.
>
>
>
> Kernel: 2.6.18
> Logfile:
>
> Mar 29 22:18:07 seven ------------[ cut here ]------------
> Mar 29 22:18:07 seven kernel BUG at mm/rmap.c:522!
> Mar 29 22:18:07 seven invalid opcode: 0000 [#1]
> Mar 29 22:18:07 seven SMP
> Mar 29 22:18:07 seven Modules linked in: capi capifs st fcdsl
> Mar 29 22:18:07 seven CPU: 0
> Mar 29 22:18:07 seven EIP: 0060:[<c0151a46>] Tainted: P S VLI
You are using proprietary module. Please reproduce with an untainted kernel.
Regards,
Michal
--
Michal K. K. Piotrowski
Hurd Testers Group
(http://www.hurdtestersgroup.org/)
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug?
@ 2005-05-19 6:25 Holub Zoltan
2005-05-19 6:25 ` bug? Rudolf Marek
0 siblings, 1 reply; 42+ messages in thread
From: Holub Zoltan @ 2005-05-19 6:25 UTC (permalink / raw)
To: lm-sensors
Hi!!
I have two asus p5a-b motherboard.
The first one is Rev 1.03, the second one is Rev 1.04
In the bios i see the cpu and mobo temperature, it works fine.
I using kernel 2.6
This mobo needs ALI15X3 hw bus, and Winbond W83781D sensor chip driver.
With these drivers i see the sensors on sysfs.
The only difference is with rev 1.04 the i dont see the mobo
temperature value.
It show constantly -48 celsius. (bios shows correctly)
MB: -48.0?C (high = +80?C, hyst = +75?C)
With 1.03 mobo the mb temp is showed correcty.
The cpu temp, voltages and fan speed is showed correctly on the two mobos.
I am using same bios on the two mobos.
I tried with kernel 2.6.6 and 2.6.7.
Is it a sensors bug or something wrong with the mobo?
fako
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug?
2005-05-19 6:25 bug? Holub Zoltan
@ 2005-05-19 6:25 ` Rudolf Marek
0 siblings, 0 replies; 42+ messages in thread
From: Rudolf Marek @ 2005-05-19 6:25 UTC (permalink / raw)
To: lm-sensors
Hello,
> The only difference is with rev 1.04 the i dont see the mobo
> temperature value.
> It show constantly -48 celsius. (bios shows correctly)
It seems unconnected.
What about temp3 (you may have this temp commented out) ?
> MB: -48.0?C (high = +80?C, hyst = +75?C)
> With 1.03 mobo the mb temp is showed correcty.
> I am using same bios on the two mobos.
You flashed to same version ?
> Is it a sensors bug or something wrong with the mobo?
It may be change in HW design. Lets try to dump the chip registers.
In "sensors" listing you should see chip address. (2 hex digits) If not
you can try:
I suppose you havent more i2c busses on your computer.
(check with i2cdetect -l)
Run as root to probe the ALI bus:
i2cdetect 0
You should see in 0x20 - 0x2F range some number(s). I would say it can be
on 0x2D
If you are sure about the address from sensors output you can continue
here. Just replace the 0x2d with your address.
then i2cdump 0 0x2d
You can redirect output to file. Please run it on both computers and send
it to us. Could you write also the bios revision you are using ?
Don't forget to CC to a list. You can visit us at IRC #linux-sensors at
freenode.org.
Thanks
Regards
Rudolf
^ permalink raw reply [flat|nested] 42+ messages in thread
* BUG ? :)
@ 2003-10-08 18:08 =?unknown-8bit?q?Jos=E9?= Mans
2003-10-08 19:07 ` Alex Zarochentsev
0 siblings, 1 reply; 42+ messages in thread
From: =?unknown-8bit?q?Jos=E9?= Mans @ 2003-10-08 18:08 UTC (permalink / raw)
To: reiserfs-list
Hello,
please see :
gyptis:/mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1/VDB# ls
A?P?Eq7nVDB@ NEC_6FGnVDB@
ls -l
ls: NEC_6FGnVDB@: No such file or directory
ls: APEq7nVDB@: No such file or directory
total 0
ls -lisaF
ls: .@: No such file or directory
ls: .n: No such file or directory
ls: NEC_6FGnVDB@: No such file or directory
ls: APEq7nVDB@: No such file or directory
gyptis:/mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1# rm -rf VDB/
umount /mnt
fsck /dev/hda4 #(/mnt)
(see end this message)
fsck --rebuild-tree /dev/hda4
fsck.ext3: invalid option -- e :)
rm -rf /mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1/VDB/
rm: cannot remove directory `VDB/': Directory not empty
outch :)
My version reserfs :
reiserfsprogs 1:3.6.11-1 (debian testing)
Linux gyptis 2.4.21
thx :)
# LOG fsck...
Replaying journal..
0 transactions replayed
Checking internal tree../ 1 (of 2)/ 23 (of 97)/ 44 (of 91)bad_directory_item: block 8246: The directory item [4 178 0x1 DIR (3)] has a not properly hashed entry (0)
bad_leaf: block 8246, item 20: The corrupted item found (4 178 0x1 DIR (3), len 264, location 1560 entry count 11, / 24 (of 97)/ 55 (of 85)block 8258: The number of items (17) is incorrect, should be (9)
the problem in the internal node occured (8258), whole subtree is skipped / 53 (of 97)/ 77 (of 170)block 2684348: The level of the node (16385) is not correct, (1) expected
the problem in the internal node occured (2684348), whole subtree is skipped / 84 (of 97)/ 11 (of 102)bad_directory_item: block 4463855: The directory item [52785 52797 0x1 DIR (3)] has a not properly hashed entry (0)
bad_leaf: block 4463855, item 8: The corrupted item found (52785 52797 0x1 DIR (3), len 112, location 676 entry count 4, fsck need 0, format old) / 2 (of 2)/ 63 (of 123)/ 21 (of 132)bad_directory_item: block 8498503: The directory item [107898 113352 0x320a3400 DIR (3)] has a not properly hashed entry (7)
bad_leaf: block 8498503, item 0: The corrupted item found (107898 113352 0x320a3400 DIR (3), len 624, location 3472 entry count 20, fsck need 0, format old)
bad_directory_item: block 8498503: The directory item [107898 118588 0x1 DIR (3)] has a not properly hashed entry (0)
bad_leaf: block 8498503, item 6: The corrupted item found (107898 118588 0x1 DIR (3), len 600, location 1068 entry count 22, fsck need 0, format old) / 70 (of 123)/129 (of 170)bad_directory_item: block 8517201: The directory item [112190 112212 0x1 DIR (3)] has a not properly hashed entry (0)
bad_leaf: block 8517201, item 14: The corrupted item found (112190 112212 0x1 DIR (3), len 944, location 1544 entry count 31, fsck need 0, format old) / 74 (of 123)/ 33 (of 168)bad_directory_item: block 8548003: The directory item [114772 115331 0x1 DIR (3)] has a not properly hashed entry (16)
bad_leaf: block 8548003, item 11: The corrupted item found (114772 115331 0x1 DIR (3), len 1288, location 312 entry count 38, fsck need 0, format old) /155 (of 168)bad_directory_item: block 8556828: The directory item [115105 115131 0x1 DIR (3)] has the corrupted entry structure
bad_leaf: block 8556828, item 1: The corrupted item found (115105 115131 0x1 DIR (3), len 1120, location 2932 entry count 27, fsck need 0, format old) / 75 (of 123)/ 12 (of 170)block 8556855: The level of the node (16385) is not correct, (1) expected
the problem in the internal node occured (8556855), whole subtree is skipped / 76 (of 123)/ 79 (of 170)bad_directory_item: block 8559508: The directory item [115786 115951 0x1 DIR (3)] has the corrupted entry structure
bad_leaf: block 8559508, item 4: The corrupted item found (115786 115951 0x1 DIR (3), len 240, location 152 entry count 5, fsck need 0, format old) / 82 (of 123)/115 (of 170)bad_directory_item: block 8578253: The directory item [119215 119216 0x1 DIR (3)] has a not properly hashed entry (0)
bad_leaf: block 8578253, item 2: The corrupted item found (119215 119216 0x1 DIR (3), len 352, location 3116 entry count 13, fsck need 0, format old)
bad_directory_item: block 8578253: The directory item [119216 119227 0x1 DIR (3)] has a not properly hashed entry (7)
bad_leaf: block 8578253, item 24: The corrupted item found (119216 119227 0x1 DIR (3), len 328, location 2112 entry count 12, fsck need 0, format old) /118 (of 170)bad_indirect_item: block 8578264: The item [119238 119239 0x1 IND (1)] has the bad pointer (0) to the block (1082321204)
bad_indirect_item: block 8578264: The item [119238 119239 0x1 IND (1)] has the bad pointer (1) to the block (1082321205)
bad_indirect_item: block 8578264: The item [119238 119239 0x1 IND (1)] has the bad pointer (2) to the block (1082321206)
bad_indirect_item: block 8578264: The item [119238 119239 0x1 IND (1)] has the bad pointer (3) to the block (1082321207)
bad_indirect_item: block 8578264: The item [119238 119239 0x1 IND (1)] has the bad pointer (4) to the block (1082321203)
bad_indirect_item: block 8578264: The item [102854 102856 0x1 IND (1)] has the bad pointer (0) to the block (1082321209)
bad_indirect_item: block 8578264: The item [102854 102856 0x1 IND (1)] has the bad pointer (1) to the block (1082321210)
bad_indirect_item: block 8578264: The item [102854 102856 0x1 IND (1)] has the bad pointer (2) to the block (1082321211)
bad_indirect_item: block 8578264: The item [102854 102856 0x1 IND (1)] has the bad pointer (3) to the block (1082321212)
bad_indirect_item: block 8578264: The item [102854 102856 0x1 IND (1)] has the bad pointer (4) to the block (1082321208)
bad_leaf: block 8578264, items 7 and 8: The wrong order of items: [119238 119240 0x0 SD (0)], [102854 102856 0x1 IND (1)]
bad_stat_data: The objectid (102857) is shared by at least two files
bad_directory_item: block 8578264: The directory item [102854 102857 0x1 DIR (3)] has the corrupted entry structure
bad_leaf: block 8578264, item 10: The corrupted item found (102854 102857 0x1 DIR (3), len 112, location 460 entry count 4, fsck need 0, format old)
bad_stat_data: The objectid (102858) is shared by at least two files / 84 (of 123)/ 42 (of 170)bad_directory_item: block 8616684: The directory item [120818 120842 0x1 DIR (3)] has the corrupted entry structure
bad_leaf: block 8616684, item 11: The corrupted item found (120818 120842 0x1 DIR (3), len 2128, location 320 entry count 66, fsck need 0, format old) / 87 (of 123)/ 24 (of 166)bad_leaf: block 8714253, items 13 and 14: The wrong order of items: [123731 123735 0x0 SD (0)], [10734finished
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
Bad nodes were found, Semantic pass skipped
17 found corruptions can be fixed only when running with --rebuild-tree
###########
reiserfsck finished at Wed Oct 8 20:05:09 2003
###########
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG ? :)
2003-10-08 18:08 BUG ? :) =?unknown-8bit?q?Jos=E9?= Mans
@ 2003-10-08 19:07 ` Alex Zarochentsev
0 siblings, 0 replies; 42+ messages in thread
From: Alex Zarochentsev @ 2003-10-08 19:07 UTC (permalink / raw)
To: JosИ Mans; +Cc: reiserfs-list
On Wed, Oct 08, 2003 at 08:08:59PM +0200, José Mans wrote:
>
> Hello,
> please see :
>
> gyptis:/mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1/VDB# ls
> A?P?Eq7nVDB@ NEC_6FGnVDB@
> ls -l
> ls: NEC_6FGnVDB@: No such file or directory
> ls: APEq7nVDB@: No such file or directory
> total 0
> ls -lisaF
> ls: .@: No such file or directory
> ls: .n: No such file or directory
> ls: NEC_6FGnVDB@: No such file or directory
> ls: APEq7nVDB@: No such file or directory
probably, running badblocks(8) on /dev/hda4 is not a bad idea.
>
>
> gyptis:/mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1# rm -rf VDB/
>
> umount /mnt
> fsck /dev/hda4 #(/mnt)
> (see end this message)
> fsck --rebuild-tree /dev/hda4
> fsck.ext3: invalid option -- e :)
:-) what did you expect from running fsck.ext3 on reiserfs?
first, backup /dev/hda4 to somewhere,
then run fsck.reiserfs --rebuild-tree /dev/hda4
> rm -rf /mnt/local/Download/Drivers/ATI/RAGE64/11.2560/UTILITY/DISK1/VDB/
> rm: cannot remove directory `VDB/': Directory not empty
>
> outch :)
>
> My version reserfs :
> reiserfsprogs 1:3.6.11-1 (debian testing)
> Linux gyptis 2.4.21
>
>
> thx :)
>
>
>
> # LOG fsck...
--
Alex.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2003-07-17 23:40 WebExplode.com
0 siblings, 0 replies; 42+ messages in thread
From: WebExplode.com @ 2003-07-17 23:40 UTC (permalink / raw)
To: linux-smp
hello, saw the message to report this so here we go.....
This is running a P4 2.4Ghz on a SuperMicro P4SCA
board. RedHat 9.0 and 2.4.21.
Thanks for the great work as always....
Greg
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
....... : Delivery Type: 0
....... : LTS : 0
.... register #01: 00178020
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0020
.... register #02: 00178020
....... : arbitration: 00
An unexpected IO-APIC was found. If this kernel release is less than
three months old please report this to linux-smp@vger.kernel.org
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2003-06-30 10:15 Hrvoje Habjanic
0 siblings, 0 replies; 42+ messages in thread
From: Hrvoje Habjanic @ 2003-06-30 10:15 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
/* do we have a wakeup address for S2 and S3? */
/* Here, we support only S4BIOS, those we set the wakeup address */
/* S4OS is only supported for now via swsusp.. */
if (state == ACPI_STATE_S2 || state == ACPI_STATE_S3 || ACPI_STATE_S4) {
if (!acpi_wakeup_address)
Hmmmm ... ACPI_STATE_S4 will always get to true .... maybe:
/* do we have a wakeup address for S2 and S3? */
/* Here, we support only S4BIOS, those we set the wakeup address */
/* S4OS is only supported for now via swsusp.. */
if (state == ACPI_STATE_S2 || state == ACPI_STATE_S3 || state == ACPI_STATE_S4) {
if (!acpi_wakeup_address)
Hrvoje
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
^ permalink raw reply [flat|nested] 42+ messages in thread
* BUG?
@ 2002-05-21 9:48 alex-n
2002-05-21 10:14 ` BUG? Wilfried Weissmann
0 siblings, 1 reply; 42+ messages in thread
From: alex-n @ 2002-05-21 9:48 UTC (permalink / raw)
To: linux-kernel
Dear Sirs,
this can be lamer's question (I'm sorry rite now!), but...
The report itself is:
################################################################################
[1.] Linux crashes at the 'interactive startup' boot stage.
[2.] Once the system is trying to boot, first stage (which is
*before* msg 'Interactive startup') it is all O.K. Once the
'Interactive startup' stage begins, the bootstrap process
fails with diffirent msgs; all of them begins with "Unable
to handle kernel paging request at address..." or "Unable
to handle kernel dereference at address..." (first 'reason'
is in the majority of cases, the second is quite unusual).
It seems to me that this is a trouble with initrd.img,
because once I've recompiled kernel with ALL OPTIONS (not
suitable to my hardware, i.e. SCSI adapters) turned OFF,
the problem remains.
I've notices that sometimes such a trouble is 'reached'
with 'IH' flag of 'EFLAGS' (bit no 10) set to zero. As far
as I know it's status, it tells CPU ignore any interrupt
requests... The keyboard stops functioning on such a crashes
as usual, but there was TWO TIMES the keyboard remains it's
working state like an echo, not like control-device. :-\
May be, it's lamer's notice, I do not know, but I thought
this may be useful...
I thouht that hardware configuration may be useful too:
M/B: GigaByte GA-7ZX-H
Chipset: VIA Apollo KT133A
Features: VIA AC'97 audio on VT82C686B
CPU: AMD Athlon Thunderbird 900 MHz, FSB 100 MHz
RAM: IBM 256 Mb PC-133
[3.] boot process, initrd, rc.sysinit
[4.] Kernel version (from /proc/version):
Linux version 2.4.7-10BOOT (bhcompile@stripples.devel.redhat.com)
(gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98))
#1 Thu Sep 6 16:15:00 EDT 2001
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
OK, I'm adding one example (hand-written).
---8<-----------------------------------------------------------------------
<1>Unable to handle kernel paging request at virtual address
0ec3df54
Printing eip:
c012b69f
*pde=00000000
CPU: 0
EIP: 0010:[<c012b69f>]
EFLAGS: 00010006
eax: cfcfcfcf ebx: cfcfcfcf ecx: 00000282 edx: cfa4a000
esi: c1723e6c edi: cfbde200 ebp: cfd27bc0 esp: cfa47d58
ds: 0018
es: 0018
ss: 0018
Process rc.sysinit (pid: 29, stackpage=cfa47000)
Stack: c0230979 c011b03e c022c9c7 00000000 cfa47df4 fffffff4
c0146fb8
c1723e6c 000000f0 c1757e88 cfbe5005 11163d8b 00000005
cfa47df4
fffffff1 cfbde200 cfd27bc0 c013ed7c cfd27bc0 cfa47df4
fffffdce
cfd27bc0 cfa14df4 00000000
Call trace: [<c0230979>] [<c022b03c>] [<c022c9c7>] [<c0146fb8>]
[<c013ed7c>] [<c013f4a6>] [<c018c1a3>] [<c013d0f5>]
[<c013dabc>] [<c012e6be>] [<c0204daf>] [<c0123c0a>]
[<c0123c7d>] [<c012439c>] [<c0113450>] [<c01135ca>]
[<c011f717>] [<c011fad3>] [<c013eade>] [<c0105b60>]
[<c0106f2b>]
Code: 8b 44 82 18 0f af 5a 0c 89 42 14 03 5a 0c 40 75 05 8b 02 89
/etc/rc.sysinit: line 49: 29 Segmentation failt /bin/dmesg -n
$LOGLEVEL
---8<-----------------------------------------------------------------------
[6.] A small shell script or example program which triggers the
problem (if possible)
SORRY, it's impossible. I've made about two hundred tried but
I've never got just "localhost login:" message... >:-(((
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old
version.
Compare to the current minimal requirements in
Documentation/Changes.
Linux localhost.localdomain 2.4.7-10BOOT
#1 Thu Sep 6 16:15:00 EDT 2001 i686 unknown
Gnu C 2.96
Gnu make 3.79.1
binutils 2.11.90.0.8
util-linux 2.11f
mount 2.11g
modutils 2.4.6
e2fsprogs tune2fs
reiserfsprogs 3.x.0j
PPP 2.4.1
isdn4k-utils 3.1pre1
Linux C Library 2.2.4
Dynamic linker (ldd) 2.2.4
Procps 2.0.7
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded reiserfs ext3 jbd vfat msdos fat raid5
xor raid1 raid0 usb-storage keybdev hid
input usb-uhci usbcore sr_mod sd_mod scsi_mod
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 902.081
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 mmx fxsr syscall
mmxext
3dnowext 3dnow
bogomips : 1795.68
[7.3.] Module information (from /proc/modules):
reiserfs 142480 0 (unused)
ext3 57456 0
jbd 34560 0 [ext3]
vfat 8400 1
msdos 4624 0 (unused)
fat 29152 0 [vfat msdos]
raid5 16080 0 (unused)
xor 5488 0 [raid5]
raid1 11872 0 (unused)
raid0 3056 0 (unused)
usb-storage 32544 0 (unused)
keybdev 1584 0 (unused)
hid 18224 0 (unused)
input 3136 0 [keybdev hid]
usb-uhci 20080 0 (unused)
usbcore 47552 1 [usb-storage hid usb-uhci]
sr_mod 12944 0 (unused)
sd_mod 10368 0 (unused)
scsi_mod 49488 2 [usb-storage sr_mod sd_mod]
[7.4.] Loaded driver and hardware information (/proc/ioports,
/proc/iomem)
/proc/ioports output:
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0400-040f : PCI device 1106:3057
0c00-0c7f : PCI device 1106:3057
0cf8-0cff : PCI conf1
a000-afff : PCI Bus #01
cc00-cc1f : PCI device 1106:3038
cc00-cc1f : usb-uhci
d000-d01f : PCI device 1106:3038
d000-d01f : usb-uhci
d400-d403 : PCI device 1106:3058
d800-d803 : PCI device 1106:3058
dc00-dcff : PCI device 1106:3058
ffa0-ffaf : PCI device 1106:0571
ffa0-ffa7 : ide0
ffa8-ffaf : ide1
/proc/iomem output:
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-0ffeffff : System RAM
00100000-0021680f : Kernel code
00216810-0022cd8b : Kernel data
0fff0000-0fff7fff : ACPI Tables
0fff8000-0fffffff : ACPI Non-volatile Storage
cdc00000-ddcfffff : PCI Bus #01
d0000000-d7ffffff : PCI device 10de:0110
d0000000-d1ffffff : vesafb
dde00000-dfefffff : PCI Bus #01
de000000-deffffff : PCI device 10de:0110
e0000000-e3ffffff : PCI device 1106:0305
ffff0000-ffffffff : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
Latency: 8
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133
AGP] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: dde00000-dfefffff
Prefetchable memory behind bridge: cdc00000-ddcfffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
South] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at ffa0 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 08
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at cc00 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64, cache line size 08
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
40)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
Controller (rev 50)
Subsystem: Giga-byte Technology: Unknown device a000
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin C routed to IRQ 10
Region 0: I/O ports at dc00 [size=256]
Region 1: I/O ports at d800 [size=4]
Region 2: I/O ports at d400 [size=4]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
(prog-if 00 [VGA])
Subsystem: LeadTek Research Inc.: Unknown device 2830
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at dfef0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=31 SBA- 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
[7.6.] SCSI information (from /proc/scsi/scsi)
Attached devices: none
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
---
[X.] Other notes, patches, fixes, workarounds:
I've tried recompile the kernel from rescue shell, but nothing has
changed.
################################################################################
Thank you in advance.
With kindest regards, Alex Nedovizij.
----
Optimag : Canon PowerShot Pro 90IS : $995
http://pc.optimag.net/browse/27/77/433.html
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: BUG?
2002-05-21 9:48 BUG? alex-n
@ 2002-05-21 10:14 ` Wilfried Weissmann
0 siblings, 0 replies; 42+ messages in thread
From: Wilfried Weissmann @ 2002-05-21 10:14 UTC (permalink / raw)
To: alex-n; +Cc: linux-kernel
alex-n@ua.fm wrote:
> Dear Sirs,
> this can be lamer's question (I'm sorry rite now!), but...
>
> The report itself is:
>
> ################################################################################
>
> [1.] Linux crashes at the 'interactive startup' boot stage.
>
> [2.] Once the system is trying to boot, first stage (which is
> *before* msg 'Interactive startup') it is all O.K. Once the
> 'Interactive startup' stage begins, the bootstrap process
> fails with diffirent msgs; all of them begins with "Unable
> to handle kernel paging request at address..." or "Unable
> to handle kernel dereference at address..." (first 'reason'
> is in the majority of cases, the second is quite unusual).
>
> It seems to me that this is a trouble with initrd.img,
> because once I've recompiled kernel with ALL OPTIONS (not
> suitable to my hardware, i.e. SCSI adapters) turned OFF,
> the problem remains.
[snip]
2.4.7 does not have some VIA chipset workarounds that caused oopses when
the kernel was compiled with K7 optimization. So set the optimization to
AMD K6 or use a more recent kernel version. I think 2.4.16 and later
versions have fixed this problem.
hope this helps,
Wilfried
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug ?
@ 2001-12-31 18:09 Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
0 siblings, 2 replies; 42+ messages in thread
From: Klaus Zerwes @ 2001-12-31 18:09 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 4150 bytes --]
First: my english is realy bad - sorry
My PC hangs sporadicaly (every 2 weeks) after heavy Network traffic.
I tried to work around the problem by changing the NIC (dmfe >
realtek, using new driver 8139too), but it din't help.
Today i had the luck ( :-( ) that the syslog-console was activ, so
that I could get the messages (otherwise the PC hangs completly, and
its no more longer possible to change the console)
The PC akts as a small server.
Main running services:
Kernel-NFS
Samba 2.2.1
mysql
sshd: OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
apache w/ php
ip-filter
squid
Hardware:
lspci -v says:
00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1541 (rev 04)
Subsystem: Acer Laboratories Inc. [ALi] ALI M1541 Aladdin
V/V+ AGP System Controller
Flags: bus master, slow devsel, latency 32
Memory at da000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: [b0] AGP version 1.0
00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5243 (rev 04)
(prog-if 00 [Normal decode])
Flags: bus master, slow devsel, latency 32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: d8000000-d9ffffff
Prefetchable memory behind bridge: db000000-dbffffff
00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA
Bridge [Aladdin IV] (rev c3)
Flags: bus master, medium devsel, latency 0
00:0f.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c1)
(prog-if fa)
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at f000 [size=16]
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139
(rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e000 [size=256]
Memory at dd000000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at dc000000 [disabled] [size=64K]
00:14.0 Network controller: AVM Audiovisuelles MKTG & Computer System
GmbH A1 ISDN [Fritz] (rev 02)
Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH
FRITZ!Card ISDN Controller
Flags: medium devsel, IRQ 11
Memory at dd002000 (32-bit, non-prefetchable) [size=32]
I/O ports at e400 [size=32]
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC
AGP (rev 7a) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc: Unknown device 0084
Flags: bus master, stepping, medium devsel, latency 32, IRQ 11
Memory at db000000 (32-bit, prefetchable) [size=16M]
I/O ports at d000 [size=256]
Memory at d9000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [5c] Power Management version 1
and now the errormessage:
invalid opperand: 0000
CPU: 0
EIP: 0010:[<c010a123>]
------ inserted
(the only simmilar entry in System.map:c010a120 t IRQ0x00_interrupt)
------ continue
EFLAGS: 00010046
eax: d4ac5428 ebx:00000014 ecx:00000054 edx:14c42814
esi: 0402d7c0 edi:26dd33a3 ebp:04040101 esp:c2f23fe8
ds 002b es 002b ss 0018
Process sshd (pid 1407, stackpage=c2f23000)
Stack: ffffff00 08078480 00000023
00000206 bffff236 0000002b
Call Trace:
Code: ff ff eb d9 89 f6 8d bc 27 00 00 00 00 68 01 ff ff ff eb c9
teh error ocured while i was doing a backup via ssh & tar + gzip
( something like:
ssh 192.168.0.1 tar -cSp --numeric-owner -f - /xport/netdata | gzip> \
/var/backup/hdd4/filename.tgz)
but as I said simillar errors ocure not only while running ssh.
Same error i had with earlier Kernelversions (2.4.9, 2.4.8), thats wy
i use a out-of-the-box-kernel of a Distribution (SuSE).
If this error seems to result out of a hardware error, a reply would
be verry nice.
I send you the output of dmesg as a txtfile.
I'w downloaded today aktual Kernel and try it with 2.4.17.
Thank you all for doing such a good work on this nice OS.
I work since 3 years with Linux - and I enjoi it every day.
A happy new year from Berlin
Klaus
--
live free or die :: linux
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 6337 bytes --]
Linux version 2.4.10-4GB (root@Pentium.suse.de) (gcc version 2.95.3 20010315 (SuSE)) #1 Tue Sep 25 12:33:54 GMT 2001
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000007ff0000 (usable)
BIOS-e820: 0000000007ff0000 - 0000000007ff3000 (ACPI NVS)
BIOS-e820: 0000000007ff3000 - 0000000008000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 32752
zone(0): 4096 pages.
zone(1): 28656 pages.
zone(2): 0 pages.
No local APIC present or hardware disabled
Kernel command line: auto BOOT_IMAGE=server ro root=302 BOOT_FILE=/boot/vmlinuz
Initializing CPU#0
Detected 501.141 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 999.42 BogoMIPS
Memory: 126416k/131008k available (1289k kernel code, 4204k reserved, 381k data, 124k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
CPU: Before vendor init, caps: 008021bf 808029bf 00000000, vendor = 2
Enabling new style K6 write allocation for 127 Mb
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: After vendor init, caps: 008021bf 808029bf 00000000 00000002
CPU: After generic, caps: 008021bf 808029bf 00000000 00000002
CPU: Common caps: 008021bf 808029bf 00000000 00000002
CPU: AMD-K6(tm) 3D processor stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: AMD K6
PCI: PCI BIOS revision 2.10 entry at 0xfb2a0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router ALI [10b9/1533] at 00:07.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.14)
Starting kswapd
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
block: 128 slots per queue, batch=16
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller on PCI bus 00 dev 78
PCI: Assigned IRQ 5 for device 00:0f.0
ALI15X3: chipset revision 193
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM BIGFOOT TS12.7A, ATA DISK drive
hdb: FX810S, ATAPI CD/DVD-ROM drive
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hdc: ST320423A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 25075008 sectors (12838 MB) w/418KiB Cache, CHS=1560/255/63, UDMA(33)
hdc: 40011300 sectors (20486 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(33)
hdb: ATAPI 8X CD-ROM drive, 256kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
ide-floppy driver 0.97.sv
Partition check:
hda: hda1 hda2 hda3
hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
ide-floppy driver 0.97.sv
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 124k freed
Adding Swap: 249944k swap-space (priority -1)
Adding Swap: 128480k swap-space (priority -2)
CSLIP: code copyright 1989 Regents of the University of California
ISDN subsystem Rev: 1.114.6.14/1.94.6.7/1.140.6.8/1.85.6.6/1.21.6.1/1.5.6.3 loaded
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (module)
HiSax: Layer1 Revision 2.41.6.4
HiSax: Layer2 Revision 2.25.6.3
HiSax: TeiMgr Revision 2.17.6.2
HiSax: Layer3 Revision 2.17.6.4
HiSax: LinkLayer Revision 2.51.6.5
HiSax: Approval certification valid
HiSax: Approved with ELSA Microlink PCI cards
HiSax: Approved with Eicon Technology Diva 2.01 PCI cards
HiSax: Approved with Sedlbauer Speedfax + cards
HiSax: Approved with HFC-S PCI A based cards
HiSax: Total 1 card defined
HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
HiSax: AVM PCI driver Rev. 1.22.6.5
PCI: Found IRQ 11 for device 00:14.0
AVM PCI: stat 0x20a
AVM PCI: Class A Rev 2
HiSax: AVM Fritz!PCI config irq:11 base:0xE400
AVM PCI: ISAC version (0): 2086/2186 V1.1
AVM Fritz PnP/PCI: IRQ 11 count 0
AVM Fritz PnP/PCI: IRQ 11 count 5
HiSax: DSS1 Rev. 2.30.6.1
HiSax: 2 channels added
HiSax: MAX_WAITING_CALLS added
HiSax: debugging flags card 1 set to 4
isdn: Verbose-Level is 3
ippp, open, slot: 0, minor: 0, state: 0000
ippp_ccp: allocated reset data structure c5427000
8139too Fast Ethernet driver 0.9.18a
PCI: Found IRQ 10 for device 00:10.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc8849000, 00:50:fc:2e:bc:5c, IRQ 10
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
ip_tables: (c)2000 Netfilter core team
ip_conntrack (1023 buckets, 8184 max)
eth0: no IPv6 routers present
OPEN: 192.168.1.99 -> 145.253.2.11 ICMP
ippp0: dialing 1 0192071...
isdn_net: ippp0 connected
nfsd: last server has exited
nfsd: unexporting all filesystems
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug ?
2001-12-31 18:09 bug ? Klaus Zerwes
@ 2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44 ` Klaus Zerwes
2002-01-05 15:37 ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
1 sibling, 2 replies; 42+ messages in thread
From: Stephan von Krawczynski @ 2001-12-31 18:51 UTC (permalink / raw)
To: Klaus Zerwes; +Cc: linux-kernel
On Mon, 31 Dec 2001 19:09:52 +0100
Klaus Zerwes <kzerwes@web.de> wrote:
> My PC hangs sporadicaly (every 2 weeks) after heavy Network traffic.
> I tried to work around the problem by changing the NIC (dmfe >
> realtek, using new driver 8139too), but it din't help.
Hm, I think I saw something the like. The configuration was basically SuSE 7.3
(with 2.4.10-whatever kernel) and two Realtek cards in a not-trusted cheap box.
I saw a good amount of collisions on the network, too. I replaced the Realteks
with DLink and the kernel with 2.4.16 and it did not happen again, although the
network collisions stayed the same. I tend to think it is the old kernel, but I
don't like Realtek cards anyway, so I threw them out in one go.
Tell us if it happens again with 2.4.17, or if you are sure it does not,
declare it as solved.
Regards,
Stephan
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug ?
2001-12-31 18:51 ` Stephan von Krawczynski
@ 2002-01-05 11:44 ` Klaus Zerwes
2002-01-05 15:37 ` Stephan von Krawczynski
1 sibling, 0 replies; 42+ messages in thread
From: Klaus Zerwes @ 2002-01-05 11:44 UTC (permalink / raw)
To: Stephan von Krawczynski; +Cc: linux-kernel
Stephan von Krawczynski wrote:
> On Mon, 31 Dec 2001 19:09:52 +0100
> Klaus Zerwes <kzerwes@web.de> wrote:
>
>
>>My PC hangs sporadicaly (every 2 weeks) after heavy Network traffic.
>>I tried to work around the problem by changing the NIC (dmfe >
>>realtek, using new driver 8139too), but it din't help.
>>
>
> Hm, I think I saw something the like. The configuration was basically SuSE 7.3
> (with 2.4.10-whatever kernel) and two Realtek cards in a not-trusted cheap box.
> I saw a good amount of collisions on the network, too. I replaced the Realteks
> with DLink and the kernel with 2.4.16 and it did not happen again, although the
> network collisions stayed the same. I tend to think it is the old kernel, but I
> don't like Realtek cards anyway, so I threw them out in one go.
>
> Tell us if it happens again with 2.4.17, or if you are sure it does not,
> declare it as solved.
>
> Regards,
> Stephan
>
I have copmpiles 2.4.16 and did some tests with a mirrored system (
only the system, without the harddisks with data) using different
NICs: Davicom FE (dmfe), RT 8139C (8139too) and SMC 9432 EtherPower II
83c172 (epic100).
The System did work fine (the Realtek-NIC I had a huge amount of
collisions, but it did work!, with the SMC-NIC the Tx-speed was not
hipeak, but it did work werry constant).
I testet nearly every protocol I can handle and created a realy hard
networktraffic for a nearly a complete day and the system did not crash!!
Hopefully I was setting my configuration up, connected the
data-harddisks and rebooted - id did not take 30 minutes and the
system crashed again. My knowledge of systems is not the best, but for
me this seems to be a hardwareproblem with the board. From a
retrospektiv point of view: this box did work for nearly 3 years under
Linux (suse, debian, slackware) and with FreeBSD and it worked fine -
but only with one harddisk.
I know that this ALI-board is not the best, but I did not know it is
realy so bad.
--
live free or die :: linux
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug ?
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44 ` Klaus Zerwes
@ 2002-01-05 15:37 ` Stephan von Krawczynski
1 sibling, 0 replies; 42+ messages in thread
From: Stephan von Krawczynski @ 2002-01-05 15:37 UTC (permalink / raw)
To: Klaus Zerwes; +Cc: linux-kernel
On Sat, 05 Jan 2002 12:44:21 +0100
Klaus Zerwes <kzerwes@web.de> wrote:
> Stephan von Krawczynski wrote:
> > Tell us if it happens again with 2.4.17, or if you are sure it does not,
> > declare it as solved.
> >
> > Regards,
> > Stephan
> >
>
>
> I have copmpiles 2.4.16 and did some tests with a mirrored system (
> only the system, without the harddisks with data) using different
> NICs: Davicom FE (dmfe), RT 8139C (8139too) and SMC 9432 EtherPower II
> 83c172 (epic100).
Sorry, but why with 2.4.16? Is this a typo?
Regards,
Stephan
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: bug ?
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
@ 2002-01-02 14:03 ` Simon Richter
1 sibling, 0 replies; 42+ messages in thread
From: Simon Richter @ 2002-01-02 14:03 UTC (permalink / raw)
To: Klaus Zerwes; +Cc: linux-kernel
On Mon, 31 Dec 2001, Klaus Zerwes wrote:
> My PC hangs sporadicaly (every 2 weeks) after heavy Network traffic.
> I tried to work around the problem by changing the NIC (dmfe >
> realtek, using new driver 8139too), but it din't help.
The RealTek 8139 is a bad choice, I had the same effect on one of our
servers until I replaced it with a NE2000. I think this is related to
busmaster DMA.
Simon
--
GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc
Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
^ permalink raw reply [flat|nested] 42+ messages in thread
* bug??
@ 2001-12-08 0:31 wolvie_cobain
0 siblings, 0 replies; 42+ messages in thread
From: wolvie_cobain @ 2001-12-08 0:31 UTC (permalink / raw)
To: linux-kernel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1931 bytes --]
Helo ppl,
I havin trobles compiling the 2.5.1-pre5 and pre6 kernels
more especificaly with the intermezzo filesystem. I dosen't use it for
nothing but i like to test some filesystem in a while and found this error
when compiling the kernel
gcc -D__KERNEL__ -I/thingz/kernelz/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=k6 -c -o psdev.o psdev.c
psdev.c: In function `presto_psdev_ioctl':
psdev.c:269: `TCGETS' undeclared (first use in this function)
psdev.c:269: (Each undeclared identifier is reported only once
psdev.c:269: for each function it appears in.)
psdev.c:270: warning: unreachable code at beginning of switch statement
make[3]: *** [psdev.o] Error 1
make[3]: Leaving directory `/thingz/kernelz/linux/fs/intermezzo'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/thingz/kernelz/linux/fs/intermezzo'
make[1]: *** [_subdir_intermezzo] Error 2
make[1]: Leaving directory `/thingz/kernelz/linux/fs'
make: *** [_dir_fs] Error 2
i could proceed for this point disablin the intermezzo fylesystem
by the by i just want to tell somebody
if o knew how to fix it i would be happy to help but..
cya
Thomas "Wolvie" Andrade
ps: and sorry bout the english.. it's not my first language, i'm brasilian
=)
"Nós também podemos trazer as coisas de volta.Dizem q somos o sonho de uma
raça
carniceira e talvez seja verdade, mas se nós acreditarmos e sonharmos podemos
mudar o mundo. Nós podemos sonha-lo de novo"
"Sonho de mil gatos"
-------------------------------------------------------------------------------
/"\
\ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
/ \
-------------------------------------------------------------------------------
linux user #106516
ICQ #46105730
^ permalink raw reply [flat|nested] 42+ messages in thread
* Bug?
@ 2001-12-07 10:33 Ian Molton
2001-12-07 10:56 ` Bug? DevilKin
0 siblings, 1 reply; 42+ messages in thread
From: Ian Molton @ 2001-12-07 10:33 UTC (permalink / raw)
To: linux-kernel
Hi.
Havent had time to investigate, but I have seen a locup on the ASUS A7M
mobo, with a via-rhine (100Mb/se, fdx) ethernet card.
With the ethernet card in one PCI slot, the USB (95% of the time) will
freeze the system solid when usb-uhci.o is loaded.
Since moving the card to another slot, it seems to works fine.
if anyone suggests 'things to look for' I will have a look (but it isnt my
box, so it may take time).
For reference, I have a (similar) box with the same CPU and mobo, but
different cards, and have never seen this (or any similar) lockup.
the mobo in the machine in question has been replaced, and the replacement
shows the same problem.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: Bug?
2001-12-07 10:33 Bug? Ian Molton
@ 2001-12-07 10:56 ` DevilKin
0 siblings, 0 replies; 42+ messages in thread
From: DevilKin @ 2001-12-07 10:56 UTC (permalink / raw)
To: spyro; +Cc: linux-kernel
At 10:33 7/12/2001 +0000, you wrote:
>Hi.
>
>Havent had time to investigate, but I have seen a locup on the ASUS A7M
>mobo, with a via-rhine (100Mb/se, fdx) ethernet card.
>
>With the ethernet card in one PCI slot, the USB (95% of the time) will
>freeze the system solid when usb-uhci.o is loaded.
>
>Since moving the card to another slot, it seems to works fine.
>
>if anyone suggests 'things to look for' I will have a look (but it isnt my
>box, so it may take time).
>
>For reference, I have a (similar) box with the same CPU and mobo, but
>different cards, and have never seen this (or any similar) lockup.
>
>the mobo in the machine in question has been replaced, and the replacement
>shows the same problem.
I suppose that the USB hub on the mainboard and the PCI slot share IRQ's...
and I've noticed that USB ain't too happy about sharing IRQ's.
Check the manual of the motherboard about this... or do an lspci -v and
report the irq numbers.
DK
^ permalink raw reply [flat|nested] 42+ messages in thread
end of thread, other threads:[~2019-08-05 2:44 UTC | newest]
Thread overview: 42+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-17 14:06 bug ? Andreas Westin
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 2:42 BUG, Su Yanjun
2016-07-24 13:46 Bug: "git log --format='format:%+s%+b'" doesn't insert newline before body Ilya Tumaykin
2016-07-25 6:55 ` Bug: Beat Bolli
2015-04-10 18:27 Bug? Barclay Jameson
2014-04-21 16:16 Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes Andreas Reis
2014-04-21 19:13 ` Andreas Reis
2014-04-22 18:16 ` Andreas Reis
2014-04-23 2:55 ` Duncan
2014-04-25 2:04 ` Bug: Andreas Reis
2014-02-17 10:28 bug? Dirk Winning, junidas GmbH
2014-02-17 14:51 ` bug? Pasi Kärkkäinen
2013-11-20 22:18 BUG?? Bruno Bruzzano
2013-11-21 12:02 ` BUG?? Luiz Augusto von Dentz
2013-11-21 14:07 ` BUG?? Bruno Bruzzano
2013-11-21 14:17 ` BUG?? Bruno Bruzzano
[not found] <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>
2013-01-28 16:37 ` bug? Mathieu Desnoyers
2013-01-23 20:09 bug? Yang Wang
2012-11-23 10:32 Bug? Dirk Winning
2012-11-23 16:46 ` Bug? George Dunlap
2012-04-21 12:53 bug? Thomas Weber
2012-04-24 15:26 ` bug? Josef Bacik
2012-04-24 15:47 ` bug? Thomas Weber
2011-11-23 9:18 Bug? Kormos 'Morc' Gábor
2012-03-22 11:07 ` Bug? Kormos 'Morc' Gábor
2010-02-26 11:15 Bug ;( Ян Программист
2009-08-12 22:07 bug: Dennis Gilmore
2008-08-23 16:17 BUG? Mateyko
2008-08-25 21:35 ` BUG? Luis R. Rodriguez
2007-04-01 13:39 Bug? Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
2005-05-19 6:25 bug? Holub Zoltan
2005-05-19 6:25 ` bug? Rudolf Marek
2003-10-08 18:08 BUG ? :) =?unknown-8bit?q?Jos=E9?= Mans
2003-10-08 19:07 ` Alex Zarochentsev
2003-07-17 23:40 Bug? WebExplode.com
2003-06-30 10:15 Bug? Hrvoje Habjanic
2002-05-21 9:48 BUG? alex-n
2002-05-21 10:14 ` BUG? Wilfried Weissmann
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44 ` Klaus Zerwes
2002-01-05 15:37 ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
2001-12-08 0:31 bug?? wolvie_cobain
2001-12-07 10:33 Bug? Ian Molton
2001-12-07 10:56 ` Bug? DevilKin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.