2GB only with linux

hello!
is there a solution for oracle 8i (or 9i) on linux to use more than 2GB for a sigle user.
i cant create larger tablesspaces. can i combine tablespaces or say "this user can use tbspace1 and tbspace2"??
thanks in advance
thomas otto 2G is only the limit of the size of a data file, not user or even tablespace. You can add additional data files to an existing tablespace, making the tablespace as big as need. Any objects in the tablespace will then start using the additional data file.
Look in the documentation for ALTER TABLESPACE ... ADD DATAFILE

Similar Messages

I have a 2GB IPOD with only 385 songs on it. I downloaded 2 CD's to iTunes but when I try and sync the IPOD I'm getting an error message indicating there isn't enough space. I thought a 2GB would hold at least 500 songs.

I have a 2GB IPOD with only 385 songs on it. I downloaded 2 CD's to iTunes and when I try and sync the IPOD I'm getting an error message that says I don't have enough free space. I thought a 2GB IPOD held at least 500 songs. I've even deleted songs from from iTunes library.

The figures that Apple used to use when saying how many songs coud fit onto any particular iPod were based on a 4 minute song at a Bit Rate of 128Kbps and that's the bit rate that songs sold by iTunes used to be in. However, now the iTunes Store sells songs at 256Kbps (as do many other MP3 stores) - which means that each song now uses twice as much storage space than before.
So if your songs have a bit rate of higher than 128Kbps, and/or they are all longer than four minutes each, that's why 385 songs is filling up your iPod. You can check how much space is being used when the iPod is connected to iTunes Library. Look on the Device panes for the capacity bar at the bottom of the window. How much space is being used by Music?
The solution is either:
Use iTunes to make 128Kbps versions to go onto your iPod - or,
Sync the iPod using Playlists and then choosing which Playlists you want on it. Smart Playlists may be the answer - you can set Smart Playlists up so that they automatically add and remove songs from your iPod, so that there is a constant change of songs (according to the rules you set)

System freezes due to hard disk problems only on Linux (not windows)

Intro/context:
Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
What i've done so far:
The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
I found no firmware update for this hard drive.
So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
Info:
Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
Some logs i've recollected all this time:
journalctl -xfa --system
abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
abr 21 13:51:24 echoes kernel: ata1: hard resetting link
abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
abr 21 13:51:24 echoes kernel: ata1: EH complete
abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
dmesg
[55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[55661.023034] ata1.00: failed command: READ FPDMA QUEUED
[55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[55661.023042] ata1.00: status: { DRDY }
[55661.023046] ata1: hard resetting link
[55666.358537] ata1: link is slow to respond, please be patient (ready=0)
[55671.053813] ata1: COMRESET failed (errno=-16)
[55671.053819] ata1: hard resetting link
[55676.389438] ata1: link is slow to respond, please be patient (ready=0)
[55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[55681.320305] ata1.00: configured for UDMA/100
[55681.320319] ata1.00: device reported invalid CHS sector 0
[55681.320349] ata1: EH complete
[55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
dmesg
[102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
[102884.890333] systemd[1]: systemd-journald.service failed.
[102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
[102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
[102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[104179.117369] ata1.00: failed command: READ FPDMA QUEUED
[104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[104179.117377] ata1.00: status: { DRDY }
[104179.117381] ata1: hard resetting link
[104184.453382] ata1: link is slow to respond, please be patient (ready=0)
[104189.149114] ata1: COMRESET failed (errno=-16)
[104189.149121] ata1: hard resetting link
[104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104189.952982] ata1.00: configured for UDMA/100
[104189.952989] ata1.00: device reported invalid CHS sector 0
[104189.953004] ata1: EH complete
[104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104508.223798] ata1.00: failed command: SMART
[104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[104508.223806] ata1.00: status: { DRDY }
[104508.223810] ata1: hard resetting link
[104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104510.698126] ata1.00: configured for UDMA/100
[104510.698157] ata1: EH complete
One of the latest and worse
journalctl -xfa --system
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
abr 22 12:57:11 echoes kernel: ata1: EH complete
abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1: EH complete
Current smart status:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: Y44MT611T
LU WWN Device Id: 5 000039 5e1a80e85
Firmware Version: AX1P5E
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 3 16:42:06 2015 ART
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 234) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Vendor (0x50) Completed without error 00% 611 -
# 2 Short offline Completed without error 00% 611 -
# 3 Short offline Completed without error 00% 597 -
# 4 Vendor (0x50) Completed without error 00% 583 -
# 5 Short offline Completed without error 00% 583 -
# 6 Vendor (0x50) Completed without error 00% 575 -
# 7 Short offline Completed without error 00% 575 -
# 8 Short offline Completed without error 00% 547 -
# 9 Extended offline Completed without error 00% 529 -
#10 Short offline Completed without error 00% 355 -
#11 Short offline Completed without error 00% 355 -
#12 Extended offline Aborted by host 70% 355 -
#13 Short offline Completed without error 00% 319 -
#14 Vendor (0x50) Completed without error 00% 13 -
#15 Short offline Completed without error 00% 13 -
#16 Short offline Completed without error 00% 12 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
Last edited by jesu (2015-05-03 19:42:53)

Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1000M 0 part
├─sda2 8:2 0 260M 0 part /boot
├─sda3 8:3 0 207,7G 0 part
├─sda4 8:4 0 25G 0 part
├─sda5 8:5 0 14,8G 0 part
├─sda6 8:6 0 80,5G 0 part /
├─sda8 8:8 0 599G 0 part /home
└─sda9 8:9 0 2G 0 part [SWAP]
So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
[ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
[ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
[ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 653.821735] ata1.00: status: { DRDY }
[ 653.821739] ata1: hard resetting link
[ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
[ 663.851604] ata1: COMRESET failed (errno=-16)
[ 663.851610] ata1: hard resetting link
[ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
[ 673.881456] ata1: COMRESET failed (errno=-16)
[ 673.881462] ata1: hard resetting link
[ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
[ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 703.012578] ata1.00: configured for UDMA/100
[ 703.012584] ata1.00: device reported invalid CHS sector 0
[ 703.012599] ata1: EH complete
[ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
[ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
[ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
[ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
[ 742.443506] Buffer I/O error on device sda8, logical block 9323208
[ 742.443508] Buffer I/O error on device sda8, logical block 9323209
[ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
[ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
[ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
[ 742.443524] Buffer I/O error on device sda8, logical block 9323216
[ 742.443526] Buffer I/O error on device sda8, logical block 9323217
[ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
[ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
[ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
[ 742.443540] Buffer I/O error on device sda8, logical block 9323226
[ 742.443542] Buffer I/O error on device sda8, logical block 9323227
[ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
[ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
[ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
[ 742.443555] Buffer I/O error on device sda8, logical block 9323234
[ 742.443557] Buffer I/O error on device sda8, logical block 9323235
[ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
[ 756.188116] systemd[1]: systemd-journald.service failed.
[ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 756.189143] systemd[1]: Listening on Journal Audit Socket.
[ 756.189801] systemd[1]: Starting Journal Service...
[ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
[ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 758.503041] systemd[1]: Started Journal Service.
[ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
[ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867747] ata1.00: status: { DRDY }
[ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867763] ata1.00: status: { DRDY }
[ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867778] ata1.00: status: { DRDY }
[ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867793] ata1.00: status: { DRDY }
[ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867807] ata1.00: status: { DRDY }
[ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867821] ata1.00: status: { DRDY }
[ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867835] ata1.00: status: { DRDY }
[ 974.867841] ata1: hard resetting link
[ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
[ 984.900902] ata1: COMRESET failed (errno=-16)
[ 984.900908] ata1: hard resetting link
[ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
[ 994.930829] ata1: COMRESET failed (errno=-16)
[ 994.930836] ata1: hard resetting link
[ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 997.014012] ata1.00: configured for UDMA/100
[ 997.014020] ata1.00: device reported invalid CHS sector 0
[ 997.014023] ata1.00: device reported invalid CHS sector 0
[ 997.014025] ata1.00: device reported invalid CHS sector 0
[ 997.014026] ata1.00: device reported invalid CHS sector 0
[ 997.014028] ata1.00: device reported invalid CHS sector 0
[ 997.014030] ata1.00: device reported invalid CHS sector 0
[ 997.014031] ata1.00: device reported invalid CHS sector 0
[ 997.014065] ata1: EH complete
There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
root and home partitions are both ext4.

Why do I get Flicker on screen with Linux Standalone Flash Player ?

Hello,
I have a problem with the standalone Linux Flash player. The thing is that when I have a video playing in background and over it I make some tweens, it flickers all the time and it is an annoying flicker. It happens only on Linux Flash Player (it works on Windows Flash Player). The flicker appears when I have a video on background, only when the tween is made and on the portion of the screen where the tween is made. I have Ubuntu 9.04 installed and the latest version of standalone Flash Player (from 2/24/09). I've tried this on several LCD and on all it does the same. My video card has the Intel G31 Express Chipset (the drivers for the video card are the one from Ubuntu). I have generated the swf file from Flash CS3. Any help would be appreciated. Thanks in advance.

See http://kb.mozillazine.org/Error_loading_websites

Access control exception only on Linux/Debian not on Windows!?

We have a rmi server application with a webstart rmi swing client that we have been running successfully on Windows. The client is downloaded and running without any problems on Windows platforms (W2003, Win2K, WinXP). The client webstart jar is signed and all permissions is set in the jnlp file.
As soon as we setup a server on linux/debian sarge we get these access control exceptions when the server tries to send events back to the client. It complains on
file permssions not being set on the server jar file and the strange thing is that the path separator is backslash on linux?
I've tried the following:
1) java.policy. Added All permssions to the server jar file and/or bin the folder.
2) Running without any security manager, i.e., System.setSecurityManager(null)
3) Explicitly setting the policy on the server. Policy.setPolicy(...)
4) Explicitly setting a policy on the client. URL policyUrl = Thread.currentThread().getContextClassLoader().getResource("server.policy");
5) Building the server and client on debian
I'm at my wits end... I've searched these forums and it seems that this is might be a common problem but I've not found a solution yet.
Our system works 100% on Windows without any problems, it's only on linux/debian that we get these access control problems.
2005-sep-19 09:39:19 se.xxx.xxx.admin.AdminManager change
ERROR: java.security.AccessControlException: access denied (java.io.FilePermission \\usr\local\XXX\bin\server.jar read)
java.security.AccessControlContext.checkPermission(Unknown Source)
java.security.AccessController.checkPermission(Unknown Source)
java.lang.SecurityManager.checkPermission(Unknown Source)
java.lang.SecurityManager.checkRead(Unknown Source)
java.io.File.exists(Unknown Source)
sun.net.www.protocol.file.Handler.openConnection(Unknown Source)
sun.net.www.protocol.file.Handler.openConnection(Unknown Source)
java.net.URL.openConnection(Unknown Source)
sun.rmi.server.LoaderHandler.addPermissionsForURLs(Unknown Source)
sun.rmi.server.LoaderHandler.access$300(Unknown Source)
sun.rmi.server.LoaderHandler$Loader.<init>(Unknown Source)
sun.rmi.server.LoaderHandler$Loader.<init>(Unknown Source)
sun.rmi.server.LoaderHandler$1.run(Unknown Source)
java.security.AccessController.doPrivileged(Native Method)
sun.rmi.server.LoaderHandler.lookupLoader(Unknown Source)
sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
java.io.ObjectInputStream.readClassDesc(Unknown Source)
java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
java.io.ObjectInputStream.readObject0(Unknown Source)
java.io.ObjectInputStream.readObject(Unknown Source)
sun.rmi.server.UnicastRef.unmarshalValue(Unknown Source)
sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
sun.rmi.transport.Transport$1.run(Unknown Source)
java.security.AccessController.doPrivileged(Native Method)
sun.rmi.transport.Transport.serviceCall(Unknown Source)
sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
sun.rmi.server.UnicastRef.invoke(Unknown Source)
se.xxx.xxx.client.XXXApplication_Stub.notify(Unknown Source)
)

I have two suggestions. The first is that you didn't indicate the permissions of the file and the directories above it along with the user you're running the program as. In Unix it is easier to get an access issue as you're probably not running as root. In a traditional Windows environment everything runs with admin permission allowing access to anything. While the error comes from the security manager it has nothing to do with traditional J2SE security - it may be an O/S level thing.
But the second suggestion touches on the other question you have - why is this showing up as backslashes? Is there perhaps an issue with the JNLP file? Is there any code that should be using System.getProperty( "file.separator") and is instead just using the backslash?

High temperature after suspend to RAM with linux-3.9.2-1.

After the update to linux-3.9.2-1 my laptop works on higher temperature after resuming from suspend to RAM. Works fine with linux 3.8.7-1.
Normal working temperature is 47~49 degrees Celsius and after resuming it is 59~61. It's not just a false temperature reading. I can actually feel the laptop warmer, and the CPU fun spins up.
I can't see any CPU high load. I tend to believe that the temperature rise has to do with the Intel GPU driver (i915). My CPU has an integrated GPU.
Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
cmdline:
i915.semaphores=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 aspm_force=true acpi_backlight=vendor intel_pstate=disable
Anyone noticed something similar?
Ways to debug it? Apart from kernel GIT bisect.

I got the impression myself, that all the i915 downclock tweaks have been getting counterproductive over time as the driver got better.
Be sure to give the new pstate another go. I had problems too with the upgrade to 3.9.x and the powersave governor. Enabling "performance" in cpupower only and letting intel_pstate manage the idling on its own had an awesome effect. I only have rc6=1 and "sna" accel along with it on a similar cpu. Resuming with fan off.

Install HRCS 9.0 R5 with Linux Issue: upgrade Database HRCS 9.0 from PT8.52 to PT8.53

Folks,
Hello. I have been installing HCM and Campus Solution 9.0 with PeopleTools8.53. Server machine is Oracle Linux 5.10 and client machine is Windows XP. My internet architecture is WebLogic11g/Tuxedo11g/OracleDatabase 11gR1. Peopletools 8.53 runs correctly in browser.
In Oracle Linux 5.10 Database Server machine, I run the scripts "createdb10.sql, utlspace.sql, hrcddl.sql, dbowner.sql, psroles.sql, psadmin.sql and connect.sql" one by one. Then I use Data Mover to load data from Windows XP into Oracle Linux 5.10 DB instance HRCS90. The Data Mover script hrcs90ora.dms completes successfully in Windows XP. Configuration Manager is set up correctly. But when I login into Application Designer, I cannot login and get the message as below:
"Security Table Manager (Get): The database is at release 8.52. The PeopleTools being run require databases at release 8.53."
I have been following the document http://docs.oracle.com/cd/E37306_02/psft/acrobat/PeopleTools-8.53-Upgrade_02-2013.pdf to upgrade HCM and Human Resources 9.0 Revision 5 Database Instance HRCS90 in Oracle Database Server with Linux. I have been following chapter 4 task by task to do. Actually, I have run 4 scripts into HRCS90 as below:
Task 4-3-5: run rel853.sql at SQL> in Linux.
Task 4-3-6: run grant.sql at SQL> in Linux.
Task 4-5-3: run ddlora.dms in Windows XP Data Mover into HRCS90.
Task 4-6: run msgtlsupg.dms in Windows XP Data Mover into HRCS90.
Then need to run Task 4-7 to copy project ppltls84cur Project in Application Designer. When login into Application Designer with Database HRCS90 and UserID and pwd PS, I get the same error message as below:
"The database is at release 8.52. The PeopleTools being run require Database at release 8.53."
Application Designer is supposed to login by Task 4-7 to copy projects but it cannot. I have tried to fing out what's wrong as below:
In task 4-1-3: I cannot run script dbtsfix.sqr in Linux and Windows XP.
In task 4-1-9: script ptupgibdel.sql does not have the string "End of PT8.53". There is no script ptupgibdel853.sql to run.
In task 4-3-6: when run script grant.sql, table PSSTATUS and PSACCESSPRFL don't exist. There is only PSOPRDEFN table.
I continue to do task by task in chapter 4 until task 4-27 that's the end, but Application Designer still cannot login. All of Application Engine Programs and SQR Programs cannot run.
My questions are:
First, does Oracle Database HRCS90 has table PSOPRDEFN only without table PSSTATUS and PSACCESSPRFL ?
Second, what's the error by task 4-7 when Application Designer still cannot login ?
Third, why Application Designer still cannot login a the end of doing chapter 4 task 4-27 ? How to solve the issue ?
Thanks.
Thanks.

I'm not quite sure what you are missing, but it looks like you missed a script which could cause problems. You need to look through your logs for errors. Are you running rel853 as the AccessID user? I don't know how you would trash PSSTATUS in this process.
You don't mention running this.
Task 4-3-2: Creating Tablespaces
This step runs the PTDDLUPG script, which builds new tablespaces as part of the upgrade to the new PeopleSoft release.
It creates tablespace PSIMAGE2, which doesn't exist in the datamover load you did. Oracle moves and puts around 208 tables here when you run rel853 from what I see.
The first line of rel853 is
UPDATE PSSTATUS SET TOOLSREL='8.53',
LASTREFRESHDTTM = SYSDATE
This is what changes the tools release, sometimes people just run this one update to gain quick and dirty access to a different version.
I pulled this download and ran through it myself without incident doing all the steps you say, adding in 4-3-2 which you seemed to have skipped. I built a system database.
My hcengs.log shows
Importing PSSTATUS
Creating Table PSSTATUS
Import PSSTATUS 1
Building required indexes for PSSTATUS
Updating statistics for PSSTATUS
Records remaining: 7686
After import, PSSTATUS is
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.52
After running rel853n it's now
SQL> COMMIT
2 ;
Commit complete.
SQL> SPOOL OFF
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.53
I ran the other 3 quick scripts. Not sure if it was necessary, but I reset the passwords and re-encrypted them with the new 8.53 datamover for the new salted encryption and fired up app designer. It works. By the way, you should probably run rel853n, it utilizes "newer" (for PeopleSoft that is) data-types than just rel853.sql that were delivered with the 9.0 application line. Since this is a new 9.0 based app build it should be used.

Install HRCS 9.0 R5 with Linux Issue: upgrade HRCS 9.0 from PT8.52 to PT8.53

Folks,
Hello. I have been installing HCM and Campus Solution 9.0 with PeopleTools8.53. Server machine is Oracle Linux 5.10 and client machine is Windows XP. My internet architecture is WebLogic11g/Tuxedo11g/OracleDatabase 11gR1. Peopletools 8.53 runs correctly in browser.
In Oracle Linux 5.10 Database Server machine, I run the scripts "createdb10.sql, utlspace.sql, hrcddl.sql, dbowner.sql, psroles.sql, psadmin.sql and connect.sql" one by one. Then I use Data Mover to load data from Windows XP into Oracle Linux 5.10 DB instance HRCS90. The Data Mover script hrcs90ora.dms completes successfully in Windows XP. Configuration Manager is set up correctly. But when I login into Application Designer, I cannot login and get the message as below:
"Security Table Manager (Get): The database is at release 8.52. The PeopleTools being run require databases at release 8.53."
I have been following the document http://docs.oracle.com/cd/E37306_02/psft/acrobat/PeopleTools-8.53-Upgrade_02-2013.pdf to upgrade HCM and Human Resources 9.0 Revision 5 Database Instance HRCS90 in Oracle Database Server with Linux. I have been following chapter 4 task by task to do. Actually, I have run 4 scripts into HRCS90 as below:
Task 4-3-5: run rel853.sql at SQL> in Linux.
Task 4-3-6: run grant.sql at SQL> in Linux.
Task 4-5-3: run ddlora.dms in Windows XP Data Mover into HRCS90.
Task 4-6: run msgtlsupg.dms in Windows XP Data Mover into HRCS90.
Then need to run Task 4-7 to copy project ppltls84cur Project in Application Designer. When login into Application Designer with Database HRCS90 and Username PSADMIN, I get the same error message as below:
"The database is at release 8.52. The PeopleTools being run require Database at release 8.53."
Application Designer is supposed to login by Task 4-7 to copy projects but it cannot. I have tried to fing out what's wrong as below:
In task 4-1-3: I cannot run script dbtsfix.sqr in Linux and Windows XP.
In task 4-1-9: script ptupgibdel.sql does not have the string "End of PT8.53". There is no script ptupgibdel853.sql to run.
In task 4-3-6: when run script grant.sql, table PSSTATUS and PSACCESSPRFL don't exist. There is only PSOPRDEFN table.
I continue to do task by task in chapter 4 and chapter 5, but Application Designer still cannot login and all of Application Engine Programs cannot run. Windows XP cannot run SQR programs. Tuxedo Application Server cannot boot in Linux. Both Application Designer and Tuxedo Application Server gets the same error message: "The database is at release 8.52. The PeopleTools being run require Database at release 8.53."
My questions are:
First, does Oracle Database HRCS90 has table PSOPRDEFN only without table PSSTATUS and PSACCESSPRFL ?
Second, what's the error by task 4-7 when Application Designer still cannot login ?
Third, why Application Designer still cannot login and get the same error message after finish doing chapter 4 and chapter 5 ? How to solve the issue ?
Thanks.

I'm not quite sure what you are missing, but it looks like you missed a script which could cause problems. You need to look through your logs for errors. Are you running rel853 as the AccessID user? I don't know how you would trash PSSTATUS in this process.
You don't mention running this.
Task 4-3-2: Creating Tablespaces
This step runs the PTDDLUPG script, which builds new tablespaces as part of the upgrade to the new PeopleSoft release.
It creates tablespace PSIMAGE2, which doesn't exist in the datamover load you did. Oracle moves and puts around 208 tables here when you run rel853 from what I see.
The first line of rel853 is
UPDATE PSSTATUS SET TOOLSREL='8.53',
LASTREFRESHDTTM = SYSDATE
This is what changes the tools release, sometimes people just run this one update to gain quick and dirty access to a different version.
I pulled this download and ran through it myself without incident doing all the steps you say, adding in 4-3-2 which you seemed to have skipped. I built a system database.
My hcengs.log shows
Importing PSSTATUS
Creating Table PSSTATUS
Import PSSTATUS 1
Building required indexes for PSSTATUS
Updating statistics for PSSTATUS
Records remaining: 7686
After import, PSSTATUS is
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.52
After running rel853n it's now
SQL> COMMIT
2 ;
Commit complete.
SQL> SPOOL OFF
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.53
I ran the other 3 quick scripts. Not sure if it was necessary, but I reset the passwords and re-encrypted them with the new 8.53 datamover for the new salted encryption and fired up app designer. It works. By the way, you should probably run rel853n, it utilizes "newer" (for PeopleSoft that is) data-types than just rel853.sql that were delivered with the 9.0 application line. Since this is a new 9.0 based app build it should be used.

Install HRCS 9.0 R5 with Linux Issue: Upgrade HRCS 9.0 Database PT8.52 to PT8.53

Folks,
Hello. I have been installing HCM and Campus Solution 9.0 with PeopleTools8.53. Server machine is Oracle Linux 5.10 and client machine is Windows XP. My internet architecture is WebLogic11g/Tuxedo11g/OracleDatabase 11gR1. Peopletools 8.53 runs correctly in browser.
In Oracle Linux 5.10 Database Server machine, I run the scripts "createdb10.sql, utlspace.sql, hrcddl.sql, dbowner.sql, psroles.sql, psadmin.sql and connect.sql" one by one. Then I use Data Mover to load data from Windows XP into Oracle Linux 5.10 DB instance HRCS90. The Data Mover script hrcs90ora.dms completes successfully in Windows XP. Configuration Manager is set up correctly. But when I login into Application Designer, I cannot login and get the message as below:
"Security Table Manager (Get): The database is at release 8.52. The PeopleTools being run require databases at release 8.53."
I have been following the document http://docs.oracle.com/cd/E37306_02/psft/acrobat/PeopleTools-8.53-Upgrade_02-2013.pdf to upgrade HCM and Human Resources 9.0 Revision 5 Database Instance HRCS90 in Oracle Database Server with Linux. I have been following chapter 4 task by task to do. Actually, I have run 4 scripts into HRCS90 as below:
Task 4-3-5: run rel853.sql at SQL> in Linux.
Task 4-3-6: run grant.sql at SQL> in Linux.
Task 4-5-3: run ddlora.dms in Windows XP Data Mover into HRCS90.
Task 4-6: run msgtlsupg.dms in Windows XP Data Mover into HRCS90.
Then need to run Task 4-7 to copy project ppltls84cur Project in Application Designer. When login into Application Designer with Database HRCS90 and UserID and pwd PS, I get the same error message as below:
"The database is at release 8.52. The PeopleTools being run require Database at release 8.53."
Application Designer is supposed to login by Task 4-7 to copy projects but it cannot. I have tried to fing out what's wrong as below:
In task 4-1-3: I cannot run script dbtsfix.sqr in Linux and Windows XP.
In task 4-1-9: script ptupgibdel.sql does not have the string "End of PT8.53". There is no script ptupgibdel853.sql to run.
In task 4-3-6: when run script grant.sql, table PSSTATUS and PSACCESSPRFL don't exist. There is only PSOPRDEFN table.
My questions are:
First, does Oracle Database HRCS90 has table PSOPRDEFN only without table PSSTATUS and PSACCESSPRFL ?
Second, what's the error by task 4-7 when Application Designer still cannot login ?
Thanks.

I'm not quite sure what you are missing, but it looks like you missed a script which could cause problems. You need to look through your logs for errors. Are you running rel853 as the AccessID user? I don't know how you would trash PSSTATUS in this process.
You don't mention running this.
Task 4-3-2: Creating Tablespaces
This step runs the PTDDLUPG script, which builds new tablespaces as part of the upgrade to the new PeopleSoft release.
It creates tablespace PSIMAGE2, which doesn't exist in the datamover load you did. Oracle moves and puts around 208 tables here when you run rel853 from what I see.
The first line of rel853 is
UPDATE PSSTATUS SET TOOLSREL='8.53',
LASTREFRESHDTTM = SYSDATE
This is what changes the tools release, sometimes people just run this one update to gain quick and dirty access to a different version.
I pulled this download and ran through it myself without incident doing all the steps you say, adding in 4-3-2 which you seemed to have skipped. I built a system database.
My hcengs.log shows
Importing PSSTATUS
Creating Table PSSTATUS
Import PSSTATUS 1
Building required indexes for PSSTATUS
Updating statistics for PSSTATUS
Records remaining: 7686
After import, PSSTATUS is
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.52
After running rel853n it's now
SQL> COMMIT
2 ;
Commit complete.
SQL> SPOOL OFF
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.53
I ran the other 3 quick scripts. Not sure if it was necessary, but I reset the passwords and re-encrypted them with the new 8.53 datamover for the new salted encryption and fired up app designer. It works. By the way, you should probably run rel853n, it utilizes "newer" (for PeopleSoft that is) data-types than just rel853.sql that were delivered with the 9.0 application line. Since this is a new 9.0 based app build it should be used.

Install HRCS 9.0 R5 with Linux Issue: upgrade HRCS 9.0 PT8.52 to PT8.53

Folks,
Hello. I have been installing HCM and Campus Solution 9.0 with PeopleTools8.53. Server machine is Oracle Linux 5.10 and client machine is Windows XP. My internet architecture is WebLogic11g/Tuxedo11g/OracleDatabase 11gR1. Peopletools 8.53 runs correctly in browser.
In Oracle Linux 5.10 Database Server machine, I run the scripts "createdb10.sql, utlspace.sql, hrcddl.sql, dbowner.sql, psroles.sql, psadmin.sql and connect.sql" one by one. Then I use Data Mover to load data from Windows XP into Oracle Linux 5.10 DB instance HRCS90. The Data Mover script hrcs90ora.dms completes successfully in Windows XP. Configuration Manager is set up correctly. But when I login into Application Designer, I cannot login and get the message as below:
"Security Table Manager (Get): The database is at release 8.52. The PeopleTools being run require databases at release 8.53."
I have been following the document http://docs.oracle.com/cd/E37306_02/psft/acrobat/PeopleTools-8.53-Upgrade_02-2013.pdf to upgrade HCM and Human Resources 9.0 Revision 5 Database Instance HRCS90 in Oracle Database Server with Linux. I have been following chapter 4 task by task to do. Actually, I have run 4 scripts into HRCS90 as below:
Task 4-3-5: run rel853.sql at SQL> in Linux.
Task 4-3-6: run grant.sql at SQL> in Linux.
Task 4-5-3: run ddlora.dms in Windows XP Data Mover into HRCS90.
Task 4-6: run msgtlsupg.dms in Windows XP Data Mover into HRCS90.
Then need to run Task 4-7 to copy project ppltls84cur Project in Application Designer. When login into Application Designer with Database HRCS90 and UserID and pwd PS, I get the same error message as below:
"The database is at release 8.52. The PeopleTools being run require Database at release 8.53."
Application Designer is supposed to login by Task 4-7 to copy projects but it cannot. I have tried to fing out what's wrong as below:
In task 4-1-3: I cannot run script dbtsfix.sqr in Linux and Windows XP.
In task 4-1-9: script ptupgibdel.sql does not have the string "End of PT8.53". There is no script ptupgibdel853.sql to run.
In task 4-3-6: when run script grant.sql, table PSSTATUS and PSACCESSPRFL don't exist. There is only PSOPRDEFN table.
My questions are:
First, does Oracle Database HRCS90 has table PSOPRDEFN only without table PSSTATUS and PSACCESSPRFL ?
Second, what's the error by task 4-7 when Application Designer still cannot login ?
Thanks.

I'm not quite sure what you are missing, but it looks like you missed a script which could cause problems. You need to look through your logs for errors. Are you running rel853 as the AccessID user? I don't know how you would trash PSSTATUS in this process.
You don't mention running this.
Task 4-3-2: Creating Tablespaces
This step runs the PTDDLUPG script, which builds new tablespaces as part of the upgrade to the new PeopleSoft release.
It creates tablespace PSIMAGE2, which doesn't exist in the datamover load you did. Oracle moves and puts around 208 tables here when you run rel853 from what I see.
The first line of rel853 is
UPDATE PSSTATUS SET TOOLSREL='8.53',
LASTREFRESHDTTM = SYSDATE
This is what changes the tools release, sometimes people just run this one update to gain quick and dirty access to a different version.
I pulled this download and ran through it myself without incident doing all the steps you say, adding in 4-3-2 which you seemed to have skipped. I built a system database.
My hcengs.log shows
Importing PSSTATUS
Creating Table PSSTATUS
Import PSSTATUS 1
Building required indexes for PSSTATUS
Updating statistics for PSSTATUS
Records remaining: 7686
After import, PSSTATUS is
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.52
After running rel853n it's now
SQL> COMMIT
2 ;
Commit complete.
SQL> SPOOL OFF
SQL> select toolsrel from sysadm.psstatus;
TOOLSREL
8.53
I ran the other 3 quick scripts. Not sure if it was necessary, but I reset the passwords and re-encrypted them with the new 8.53 datamover for the new salted encryption and fired up app designer. It works. By the way, you should probably run rel853n, it utilizes "newer" (for PeopleSoft that is) data-types than just rel853.sql that were delivered with the 9.0 application line. Since this is a new 9.0 based app build it should be used.

JVM running with LINUX operating system on I686

Is there a JDK that runs in an I686 machine with linux as operating system.
I can't raise a mule server because JVM seems to not recognize the hardware.with I686.
I am not an expert in JAVA but it seems to give the following error.
I am getting this error. I may be wrong about JVM. But I have no problem with
windows 2003 and windows XP.
E/lib/boot/*.jar
Command[0] : java
Command[1] : -Dmule.home=$MULE_HOME
Command[2] : -Dmule.base=$MULE_BASE
Command[3] : -Dmule.bootstrap.library.download.description.1=javax.activation.DataSource,/javax/activation/activation/1.1,activation-1.1.jar
Command[4] : -Dmule.bootstrap.library.download.description.2=javax.mail.Message,/javax/mail/mail/1.4,mail-1.4.jar
Command[5] : -Dm2.repo="$M2_REPO"
Command[6] : -Xmx512m
Command[7] : -Djava.library.path=$LD_LIBRARY_PATH:$MULE_HOME/lib/boot
Command[8] : -classpath
Command[9] : $MULE_LIB:$MULE_EXE/../conf
Command[10] : -Dwrapper.key=TK24FBmV2QO4iL1C
Command[11] : -Dwrapper.port=32000
Command[12] : -Dwrapper.jvm.port.min=31000
Command[13] : -Dwrapper.jvm.port.max=31999
Command[14] : -Dwrapper.debug=TRUE
Command[15] : -Dwrapper.pid=12651
Command[16] : -Dwrapper.version=3.2.3
Command[17] : -Dwrapper.native_library=wrapper
Command[18] : -Dwrapper.cpu.timeout=10
Command[19] : -Dwrapper.jvmid=1
Command[20] : org.mule.module.boot.MuleBootstrap
Command[21] : -config
Command[22] : hello_config.xml
Command[23] : console0
Launching a JVM...
The java class is not found: org/mule/module/boot/MuleBootstrap
Signal trapped. Details:
signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 1, setting the wrapper exit code to 1.
JVM exited while loading the application.
JVM was only running for 0 seconds leading to a failed restart count of 1.
Zeins

If you get something like$ java -version
java version "1.4.2"
gcj (GCC) 3.4.6 20060404 (Red Hat 3.4.6-10)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.maybe you should install a Sun JDK.

Linksys E2000 router is incompatible with Linux?

Hi All, I have Cisco/Linksys E2000 router setup for home wireless network. I had been setup while ago and well working since then. Now the challenge: I need to know or to change the wireless guest network password. Linux support says it can be done ONLY using a local application, not the web interface. And only from Windows computer. In my situation, I have Linuxes, blackberry, players and other network equipment but no Microsoft software. I did not know that router doesn't work with Linux when I bought it. Had anybody resolved similar issue? Thanks Yu

Sorry the software is only supported on Windows or MAC. You will need this to administer the Guest network.

T61 with linux pre-installed in Ireland

I would very much like to buy a T61 but can only do so if linux is pre-installed, I could easily install it myself, but only by buying it with linux pre-installed could I dodge my employers commitment to dell: if I buy a windows computer it has to be a dell. So, is it possible to get a T61 in Ireland with linux pre-installed?
Message Edited by cjhoughton on 04-13-2008 01:51 PM

Did you go to the lenovo site and type "linux" into the search box? That provides some good results in the US site, I don't know about sweden.
P.S. watch the language if you want any more help.
T60 2623-D7U, 3 GB Ram. Dual boot XP and Linux Mint.
T400 2765-T7U Windows 7
Registered Linux User #160145
FYI: I am not employed by Lenovo

HEAVY Problems with Linux x86_64 on K8T Neo

Hello, Community!
I experience *HEAVY* Problems with Linux on my MSI K8T Neo (FSR). Since the customer support of the german dependancy seems to ignore my call for help I'm in good hope that maybe you can help me out or give me some useful advise.
First some Hardware Specs of my system:
MSI K8T Neo FSR, Rev 1.1, BIOS 1.5
AMD Athlon 64 3000+
3x 512MB Kingston DDR400
Enermax EG365P-VE (350W) PSU (3.3V/5V 185W Combinded)
MSI GeForce FX5200 TDR 128
Adaptec ATA RAID AAR1200A (HPT370A) in PCI Slot 3
Hauppauge WinTV PCI in PCI Slot 5
Maxtor 4K040H2 (40GB) as Primary Master
JLMS XJ-HD166S DVD-ROM as Primary Slave
LiteOn LDW-411S DVD+/-RW as Secondary Master
LiteOn LTR-52327S CD-RW as Secondary Slave
2x Maxtor 6Y060L0 (60GB) on HPT370A as Primary Master/Slave
Seagate ST380020A (80GB) on HPT370A as Secondary Master
Maxtor 32049U3 on HPT370A as Secondary Slave
KeyTronic KT2001 USB Keyboard
Microsoft Optical Wheel Mouse Blue USB
I've downloaded Fedora Core 1 x86_64 as well as the lately released Fedora Core 2 test 3 x86_64 distribution. Both CD sets have been burnt ok.
If I try to install Core 1 x86_64 (Kernel 2.4.22-1.2179) the kernel crashes with a "attempted to kill idle task" panic. As far as I've learned the workaround is to give idle=poll as kernel parameter. This resolves the kernel panic, but the installer randomly crashes with segfaults at a random stage; sometimes while loading anaconda, sometimes during package install.
If I try to install Core2 test 3 x86_64 (Kernel 2.6.5) I get a, completely new, error message while the kernel does the PCI Scan:
******* Your BIOS seems to not contain a fix for K8 errata #93
******* Working around it, but it may cause SEGVs or burn power
******* Please consider a BIOS update
******* Disabling USB legacy in the BIOS may also help
I removed my USB keyboard, connected a PS/2 keyboard, disabled to USB Legacy option (I need it enabled in order to use Ghost) in the BIOS and booted again.
The error message is gone now, but as in Core 1 the installer still crashes randomly with segfaults. I'm still unable to go all the way through the installation routine.
I even tried to install Fedora Core 1 "i386": again there are segfaults during install.
Contrary to the problems I experience while trying to install Linux my Windows XP (32-Bit), as well as a test installation of Windows XP 64-Bit, run like a charm without any problems. Strange but true.
Since I already read trough several posts in this forum I already tried running my system with memory sticks from another manufacturers as well as with a more powerful PSU. I even removed my tv-card and raid-controller.
Nogo - Linux still crashes randomly and Windows still works without any flaws.
Has anyone a clue what I can/must do to successfully install Linux?
Might it be that the BIOS has some flaws that might cause the problems?
Has anyone managed to install Linux (what distribution) on this Mainboard?
I would greatly appreciate any help. If you need to know something I haven't provided here please feel free to ask. I'll answer ASAP.
Thank you in advance.
P.S.: The system is *NOT* overclocked in any way.

And now even the last problem is solved ...
Since I was successful in installing a basic Gentoo system but still failed to install Fedora I reflashed BIOS 1.5. This time I cleared the CMOS by unplugging the PSU, setting the jumper and removing the backup battery.
Yesterday I only flashed it with the /a switch, which should have cleared the CMOS as well - so far for the theory. However, it once went fine as I upgraded from BIOS 1.1 to 1.4.
After setting up the BIOS options again I gave it another try and booted from Fedora (Core 2 test 3) install CD: No more complains about the CPU errata, although USB legacy is enabled, and I even went through the installation without any problems.
It seems as I will stick with Gentoo as my primary distribution since the kernel makes a more "mature" impression than the one from Fedora (i.e. the K8 PowerNOW! Driver seems to be missing in Fedora's Kernel 2.6.5).
By using an spare Athlon XP Mainboard I worked out that only one of my three Kingston memory sticks had errors - I'm going to replace the faulty stick tomorrow.
Now for the conclusio:
Thanks, especially you JLP, for helping me with my issue. Without the advise to use Gentoo, and the included MemTest86, I wouldn't have been able to track down the error to a faulty memory stick that fast since Windows always ran fine.

NAC with Linux client

Hi,
I have some Linux clients. When they connects to the trusted network in the first time, they are redirected to NAC login page and are required to download java runtime. I set policies so that linux client can download java and install it, but after that, the web browers (firefox) on linux client still not allow NAC login page to be loaded.
What is the root cause in this case ?
Any guy can help me!
Best regards,
NamNT

Folks, the problem is due to the fact that there are no web agents available for linux at this time. You need to create a new user page for linux with all java options disabled ( such as the one for mac address checking , ip address refresh etc ) . Make this user page on the top of the list. Also, under clean access requirements, make sure 'require use of web agent' is disabled for linux. This way, there will be web redirection and authentication only for linux clients ( no posture possible for linux ).
Thanks,
Mani

2GB only with linux

Similar Messages

Maybe you are looking for