Re: [arch-general] NAS drive revisited

[P .NIKOLIC]

On Mon, 21 May 2012 00:11:38 -0300
Martin Cigorraga  wrote:

> Hi Nikolic,
> If you don't plan to share your NAS with (nasty and mediocre) Windows
> systems you should mount it as a NFS4 share, I use it to access my
> download and media home servers from various PCs in my home and it's
> quite a smooth experience.

Hi 

No windows boxes here apart from my brother laptop but he does not use
the drive so not a problem 

Pete 


-- 
Linux 7-of-9 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012
x86_64 GNU/Linux

Re: [arch-general] NAS drive revisited

[P .NIKOLIC]

On Mon, 21 May 2012 01:20:21 +0200
Damjan  wrote:

> > I have read the Arch Wiki till i am blue in the face already hence
> > the mail ..
> >
> >
> > mounting with SMB  using the line below
> >
> > mount -t cifs //192.168.0.154/backups -o /home/pete/nas/
> >
> > After entering the password  it mounts . mount reports ..
> >
> > //192.168.0.154/backups on /home/pete/nas type cifs
> > (rw,relatime,sec=ntlm,unc=\\192.168.0.154\backups,
> > uid=0,username=root,noforceuid,gid=0,noforcegid,addr=192.168.0.154,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1)
> >
> > i can see one thing but cant alter it  username=root but you can
> > only mount as root  or using sudo as i have been unless of course
> > you know different.
> 
> 
> add uid=pete in the mount options.
> 
> I don't know if it's documented in the wiki, but sure it is in the
> `man mount.cifs` :)
> 
> 

I'll give that a try  thanks ..


Pete .


-- 
Linux 7-of-9 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012
x86_64 GNU/Linux

Re: [arch-general] rubygems, the arch way and the aur

[martin kalcher]

Here [0] it is!

The very very first version of archgems.

It creates/updates an arch repo with some help from the rubygems API. 
You can put a list of gems in a config a it will populate your repo with 
all deps.


The first few tests worked quite well, but there are some issues like 
the missing integrity check of the source files.


For testers: The config file is expected in ~/.config/archgems

cheers, ushi

[0] https://github.com/ushis/archgems

Re: [arch-general] NAS drive revisited

[Martin Cigorraga]

Hi Nikolic,
If you don't plan to share your NAS with (nasty and mediocre) Windows
systems you should mount it as a NFS4 share, I use it to access my download
and media home servers from various PCs in my home and it's quite a smooth
experience.

Re: [arch-general] rubygems, the arch way and the aur

[martin kalcher]

Am 20.05.2012 13:39, schrieb Allan McRae:

On 20/05/12 21:27, Kwpolska wrote:

On Sun, May 20, 2012 at 3:58 AM, martin kalcher
  wrote:

Hmm.. i will figure out what makepkg actually needs to build the gem
packages. Does it call pacman, when i call it with -d? This would a problem
in my case.


-d DOES call pacman,


WRONG.


but you can modify makepkg in order to (a) not do
so; (b) work under another distro (that won't be too hard, because:)


# file -i does not work on Mac OSX unless legacy mode is set
export COMMAND_MODE='legacy'

  -- makepkg; lines 37-38

And in terms of the "-d calls pacman" thing, here comes output from a
modded makepkg, with $PACMAN (variable holding pacman command)
replaced with 'echo PACMAN': every time.  Run under Arch, as I don't
have access to other distros. (yes, my shell server is running Arch.
No, it isn't my idea.  But it is awesome.)

And in case you ask: this is ruby-jekyll with a different name.  I had
to drop all the building, because my server doesn't have ruby.

[kwpolska@*** testpkg]% makepkg-kw -d
PACMAN
==>  Making package: testpkg 0.11.2-1 (Sun May 20 13:11:07 CEST 2012)
==>  WARNING: Skipping dependency checks.
==>  Retrieving Sources...
   ->  Found jekyll-0.11.2.gem
   ->  Found LICENSE
==>  Validating source files with md5sums...
 jekyll-0.11.2.gem ... Passed
 LICENSE ... Passed
==>  Extracting Sources...
==>  Removing existing pkg/ directory...
==>  Entering fakeroot environment...
PACMAN
==>  Starting build()...
BUILD, my server unfortunately doesn't have ruby
==>  Tidying install...
   ->  Purging unwanted files...
   ->  Compressing man and info pages...
   ->  Stripping unneeded symbols from binaries and libraries...
==>  Creating package...
   ->  Generating .PKGINFO file...
   ->  Compressing package...
==>  Leaving fakeroot environment.
==>  Finished making: testpkg 0.11.2-1 (Sun May 20 13:11:09 CEST 2012)
[kwpolska@*** testpkg]%

If anyone from the makepkg team is reading, would you please mind:
(a) making less use of pacman;


You are doing it wrong...   Remove the "run_pacman" function and you
will see when it is called.  Hint: never when using -d...


Thanks for the info! I will try that on a centos box.


(b) adding -v on lines 1292-1295 in order to inform us that the
compressors are still working?


Huh...  Anyway, never by default, but you will be able to configure the
compression options with pacman-4.1.

Allan

Re: [arch-general] NAS drive revisited

[Damjan]

I have read the Arch Wiki till i am blue in the face already hence the
mail ..


mounting with SMB  using the line below

mount -t cifs //192.168.0.154/backups -o /home/pete/nas/

After entering the password  it mounts . mount reports ..

//192.168.0.154/backups on /home/pete/nas type cifs
(rw,relatime,sec=ntlm,unc=\\192.168.0.154\backups,
uid=0,username=root,noforceuid,gid=0,noforcegid,addr=192.168.0.154,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1)

i can see one thing but cant alter it  username=root but you can only
mount as root  or using sudo as i have been unless of course you know
different.



add uid=pete in the mount options.

I don't know if it's documented in the wiki, but sure it is in the
`man mount.cifs` :)


--
дамјан

Re: [arch-general] NAS drive revisited

[P .NIKOLIC]

On Sun, 20 May 2012 23:17:14 +0200
Damjan  wrote:

> 
> > I am still not able to write to my external NAS drive an iomega home
> > media drive
> >
> > So lets approach it from a different angle
> >
> > we will say i have not done anything yet just plugged it into the
> > network
> >
> > What packages am i looking to install   and what configuration
> > changes do i need to make .
> >
> > I am trying this way round as i am chasing my tail up somewhere dark
> > and nasty right now .
> >
> > I know the drive works perfectly i have just tried it with an old
> > Suse distro  on the Laptop and instant read/write no problem now if
> > it can work on there why wont it work on Arch ..
> 
> What protocols does the NAS support, and which of those you want to
> use? If you don't know about protocols, then tell us how do you
> expect it to work.
> 

SMBand to be able to both read and write the device  as i used to
be able to do under suse  ( dont anyone even think of the go back to
suse line that is a non starter) but i would like to know why it just
works on suse and is a dog on here .

Pete .


-- 
Linux 7-of-9 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012
x86_64 GNU/Linux

Re: [arch-general] NAS drive revisited

[P .NIKOLIC]

On Sun, 20 May 2012 18:09:13 -0400
Loui Chang  wrote:

> On Sun 20 May 2012 21:58 +0100, P .NIKOLIC wrote:
> > I am still not able to write to my external NAS drive an iomega home
> > media drive
> 
> You just can't write? If you can mount but can't write, then you have
> the wrong permissions on the drive and/or uid/gid mixups, depending on
> how you want it set up.
> 
> > So lets approach it from a different angle  
> > 
> > we will say i have not done anything yet just plugged it into the
> > network 
> > 
> > What packages am i looking to install and what configuration changes
> > do i need to make .
> 
> See the Arch wiki. The ball's in your court here. What you read
> depends on how you want to access the drive. SMB? NFS?

I have read the Arch Wiki till i am blue in the face already hence the
mail ..


mounting with SMB  using the line below

mount -t cifs //192.168.0.154/backups -o /home/pete/nas/

After entering the password  it mounts . mount reports ..

//192.168.0.154/backups on /home/pete/nas type cifs
(rw,relatime,sec=ntlm,unc=\\192.168.0.154\backups,
uid=0,username=root,noforceuid,gid=0,noforcegid,addr=192.168.0.154,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1)

i can see one thing but cant alter it  username=root but you can only
mount as root  or using sudo as i have been unless of course you know
different.



> 
> > I am trying this way round as i am chasing my tail up somewhere dark
> > and nasty right now .
> >
> > I know the drive works perfectly i have just tried it with an old
> > Suse distro  on the Laptop and instant read/write no problem now if
> > it can work on there why wont it work on Arch ..
> 


> Your description of the problem is much too vague. If you want help,
> you ought to describe more specifically what you're trying to do, and
> what is going wrong.
> 
Hummm what am i trying to do  Write to the drive and being told unable
to write file  

"Your description of the problem is much too vague"  Er what more
is there to tellit mounts i can read from it i am unable to write
to it  .




-- 
Linux 7-of-9 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012
x86_64 GNU/Linux

Re: [arch-general] NAS drive revisited

[Loui Chang]

On Sun 20 May 2012 21:58 +0100, P .NIKOLIC wrote:
> I am still not able to write to my external NAS drive an iomega home
> media drive

You just can't write? If you can mount but can't write, then you have
the wrong permissions on the drive and/or uid/gid mixups, depending on
how you want it set up.

> So lets approach it from a different angle  
> 
> we will say i have not done anything yet just plugged it into the
> network 
> 
> What packages am i looking to install and what configuration changes
> do i need to make .

See the Arch wiki. The ball's in your court here. What you read depends
on how you want to access the drive. SMB? NFS?

> I am trying this way round as i am chasing my tail up somewhere dark
> and nasty right now .
>
> I know the drive works perfectly i have just tried it with an old Suse
> distro  on the Laptop and instant read/write no problem now if it can
> work on there why wont it work on Arch ..

Your description of the problem is much too vague. If you want help, you
ought to describe more specifically what you're trying to do, and what
is going wrong.

Re: [arch-general] NAS drive revisited

[Damjan]

I am still not able to write to my external NAS drive an iomega home
media drive

So lets approach it from a different angle

we will say i have not done anything yet just plugged it into the
network

What packages am i looking to install   and what configuration changes
do i need to make .

I am trying this way round as i am chasing my tail up somewhere dark
and nasty right now .

I know the drive works perfectly i have just tried it with an old Suse
distro  on the Laptop and instant read/write no problem now if it can
work on there why wont it work on Arch ..


What protocols does the NAS support, and which of those you want to use?
If you don't know about protocols, then tell us how do you expect it to 
work.


--
дамјан

[arch-general] NAS drive revisited

[P .NIKOLIC]

Hi ..

I am still not able to write to my external NAS drive an iomega home
media drive

So lets approach it from a different angle  

we will say i have not done anything yet just plugged it into the
network 

What packages am i looking to install   and what configuration changes
do i need to make .

I am trying this way round as i am chasing my tail up somewhere dark
and nasty right now .

I know the drive works perfectly i have just tried it with an old Suse
distro  on the Laptop and instant read/write no problem now if it can
work on there why wont it work on Arch ..

Pete .


-- 
Linux 7-of-9 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012
x86_64 GNU/Linux

Re: [arch-general] pm-suspend stuck at uhci_hcd

[Leonid Isaev]

On Sun, 20 May 2012 12:36:16 +0200
Manne Merak  wrote:

> On 05/17/2012 01:11 AM, Leonid Isaev wrote:
> > On Wed, 16 May 2012 23:50:06 +0200
> > Manne Merak  wrote:
> >
> >> Hi,
> >> Couple of updates ago suspend to RAM stopped working.
> >> Looking at the pm-suspend.log (below) file shows that it gets stuck at
> >> unloading uhci_hcd?
> >> I can unload and load the module by hand just fine.
> >> Anyone else have this?
> > Hmm, 75modules should print something like "done" or "fail". What do you
> > mean by stopped working? What configuration do you have
> > in /etc/pm/config.d/*?
> >
> 
> Ok, some more debugging.
> The first suspend-RAM works file.  Checked the pm-suspend.log and all 
> gets unloaded just fine.
> On second suspend, I get the mentioned stuck at unloading uhci_hcd 
> (leaving it a while gives):
> 
> ---
> Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
> Unloading kernel module uhci_hcd.../usr/lib/pm-utils/functions: line 84: 
> 26341 Killed  modprobe -r "$1"

I am puzzled by this... really. Do you get anything at all in syslog after
this? Or syslog is already stopped at this point?

> /usr/lib/pm-utils/functions: line 89: log: command not found

WTF??? This is a 2 year old bug in pm-utils. OpenSUSE 11.3 fixed that in
1.3.0. Please see if this fix gets rid of the "log" error:
.

> Failed.
> Unloading kernel module ehci_hcd...
> 
> 
> Now stuck at unloading ehci_hcd.
> 
> I get the same behaviour trying to unload uhci_hcd or ehci_hcd after the 
> first successfull suspend and restore.

You mean "unload manually", right?

> 
> There's more; a "oops" in the system log:
> 
> [209624.386398] BUG: unable to handle kernel paging request at 6d0d
> [209624.386404] IP: [] _raw_spin_lock_irqsave+0x2a/0x50
> [209624.386412] *pde = 
> [209624.386414] Oops: 0002 [#1] PREEMPT SMP
> [209624.386418] Modules linked in: uhci_hcd(-) ehci_hcd usb_storage uas 
> rfcomm btusb hidp bnep bluetooth fuse vboxnetadp(O) vboxnetflt(O) usbhid 
> uvcvideo hid videobuf2_vmalloc videobuf2_memops videobuf2_core videodev 
> media nvidia(PO) snd_hda_codec_idt snd_hda_intel firewire_ohci joydev 
> b44 snd_hda_codec r852 sm_common nand snd_pcm nand_ecc nand_ids arc4 
> iwl3945 iwlegacy ssb snd_page_alloc r592 mtd iTCO_wdt firewire_core 
> crc_itu_t pcmcia mii pcmcia_core mac80211 sdhci_pci intel_agp sdhci 
> intel_gtt mmc_core cfg80211 agpgart i2c_i801 i2c_core snd_hwdep 
> snd_timer snd memstick iTCO_vendor_support serio_raw dell_wmi psmouse 
> sparse_keymap soundcore wmi dell_laptop usbcore usb_common rfkill evdev 
> thermal dcdbas button battery ac video vboxdrv(O) cpufreq_powersave 
> acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache sr_mod sd_mod cdrom 
> pata_acpi ata_generic ata_piix ahci libahci libata scsi_mod [last 
> unloaded: ehci_hcd]
> [209624.386476]
> [209624.386479] Pid: 26341, comm: modprobe Tainted: P   O 
> 3.3.6-1-ARCH #1 Dell Inc. Vostro 1700 /0HX767
> [209624.386483] EIP: 0060:[] EFLAGS: 00010002 CPU: 0
> [209624.386486] EIP is at _raw_spin_lock_irqsave+0x2a/0x50
> [209624.386488] EAX: 0100 EBX: 6d0d ECX: 6d0d EDX: e002dd10
> [209624.386490] ESI: 0206 EDI: f24ca4b4 EBP: e002dcf0 ESP: e002dce8
> [209624.386492]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> [209624.386494] Process modprobe (pid: 26341, ti=e002c000 task=c5aeca80 
> task.ti=e002c000)
> [209624.386496] Stack:
> [209624.386497]  6d0d 6d0d e002dd08 c0142d39 e002dd10 f24ca4a8 
>  
> [209624.386503]  e002dd20 c0142eca f8af756a f24ca400  ecdfbc94 
> e002dd38 f8af7461
> [209624.386508]  ecdfbc94 f24ca400 ecdfbcd8 ecdfbc94 e002dd58 f8af7694 
> ecdfb808 ecdfb808
> [209624.386513] Call Trace:
> [209624.386519]  [] lock_timer_base.isra.33+0x29/0x50
> [209624.386522]  [] del_timer+0x2a/0xe0
> [209624.386529]  [] ? hci_conn_del+0x12a/0x1f0 [bluetooth]
> [209624.386534]  [] hci_conn_del+0x21/0x1f0 [bluetooth]
> [209624.386538]  [] hci_conn_hash_flush+0x64/0xb0 [bluetooth]
> [209624.386543]  [] hci_dev_do_close+0x96/0x290 [bluetooth]
> [209624.386548]  [] hci_unregister_dev+0x48/0x140 [bluetooth]
> [209624.386551]  [] btusb_disconnect+0x4f/0xb0 [btusb]
> [209624.386559]  [] usb_unbind_interface+0x3c/0x140 [usbcore]
> [209624.386564]  [] __device_release_driver+0x5d/0xb0
> [209624.386566]  [] device_release_driver+0x24/0x40
> [209624.386569]  [] bus_remove_device+0xa5/0xd0
> [209624.386572]  [] device_del+0xe5/0x150
> [209624.386578]  [] usb_disable_device+0x89/0x1a0 [usbcore]
> [209624.386584]  [] usb_disconnect+0x70/0xe0 [usbcore]
> [209624.386590]  [] usb_disconnect+0x5f/0xe0 [usbcore]
> [209624.386595]  [] usb_disconnect+0x5f/0xe0 [usbcore]
> [209624.386602]  [] usb_remove_hcd+0x9c/0x120 [usbcore]
> [209624.386608]  [] usb_hcd_pci_remove+0x48/0xb0 [usbcore]
> [209624.386611]  [] pci_device_remove+0x2f/0xe0
> [209624.386614]  [] __device_release_drive

Re: [arch-general] rubygems, the arch way and the aur

[Kwpolska]

On Sun, May 20, 2012 at 1:39 PM, Allan McRae  wrote:
> On 20/05/12 21:27, Kwpolska wrote:
>> On Sun, May 20, 2012 at 3:58 AM, martin kalcher
>>  wrote:
>>> Hmm.. i will figure out what makepkg actually needs to build the gem
>>> packages. Does it call pacman, when i call it with -d? This would a problem
>>> in my case.
>>
>> -d DOES call pacman,
>
> WRONG.
>
>> but you can modify makepkg in order to (a) not do
>> so; (b) work under another distro (that won't be too hard, because:)
>>
>>> # file -i does not work on Mac OSX unless legacy mode is set
>>> export COMMAND_MODE='legacy'
>>  -- makepkg; lines 37-38
>>
>> And in terms of the "-d calls pacman" thing, here comes output from a
>> modded makepkg, with $PACMAN (variable holding pacman command)
>> replaced with 'echo PACMAN': every time.  Run under Arch, as I don't
>> have access to other distros. (yes, my shell server is running Arch.
>> No, it isn't my idea.  But it is awesome.)
>>
>> And in case you ask: this is ruby-jekyll with a different name.  I had
>> to drop all the building, because my server doesn't have ruby.
>>
>> [kwpolska@*** testpkg]% makepkg-kw -d
>> PACMAN
>> ==> Making package: testpkg 0.11.2-1 (Sun May 20 13:11:07 CEST 2012)
>> ==> WARNING: Skipping dependency checks.
>> ==> Retrieving Sources...
>>   -> Found jekyll-0.11.2.gem
>>   -> Found LICENSE
>> ==> Validating source files with md5sums...
>>     jekyll-0.11.2.gem ... Passed
>>     LICENSE ... Passed
>> ==> Extracting Sources...
>> ==> Removing existing pkg/ directory...
>> ==> Entering fakeroot environment...
>> PACMAN
>> ==> Starting build()...
>> BUILD, my server unfortunately doesn't have ruby
>> ==> Tidying install...
>>   -> Purging unwanted files...
>>   -> Compressing man and info pages...
>>   -> Stripping unneeded symbols from binaries and libraries...
>> ==> Creating package...
>>   -> Generating .PKGINFO file...
>>   -> Compressing package...
>> ==> Leaving fakeroot environment.
>> ==> Finished making: testpkg 0.11.2-1 (Sun May 20 13:11:09 CEST 2012)
>> [kwpolska@*** testpkg]%
>>
>> If anyone from the makepkg team is reading, would you please mind:
>> (a) making less use of pacman;
>
> You are doing it wrong...   Remove the "run_pacman" function and you
> will see when it is called.  Hint: never when using -d...

I am aware of that, too.  I thought it failed to work and therefore
tried that way.

>> (b) adding -v on lines 1292-1295 in order to inform us that the
>> compressors are still working?
>
> Huh...  Anyway, never by default, but you will be able to configure the
> compression options with pacman-4.1.

And that's awesome.  (normally I just modify the xz line, but I need
to do it every time pacman updates itself)
>
> Allan
>
>



-- 
Kwpolska 
stop html mail      | always bottom-post
www.asciiribbon.org | www.netmeister.org/news/learn2quote.html
GPG KEY: 5EAAEA16   | Arch Linux x86_64, zsh, mutt, vim.
# vim:set textwidth=70:

Re: [arch-general] rubygems, the arch way and the aur

[Allan McRae]

On 20/05/12 21:27, Kwpolska wrote:
> On Sun, May 20, 2012 at 3:58 AM, martin kalcher
>  wrote:
>> Hmm.. i will figure out what makepkg actually needs to build the gem
>> packages. Does it call pacman, when i call it with -d? This would a problem
>> in my case.
> 
> -d DOES call pacman, 

WRONG.

> but you can modify makepkg in order to (a) not do
> so; (b) work under another distro (that won't be too hard, because:)
> 
>> # file -i does not work on Mac OSX unless legacy mode is set
>> export COMMAND_MODE='legacy'
>  -- makepkg; lines 37-38
> 
> And in terms of the "-d calls pacman" thing, here comes output from a
> modded makepkg, with $PACMAN (variable holding pacman command)
> replaced with 'echo PACMAN': every time.  Run under Arch, as I don't
> have access to other distros. (yes, my shell server is running Arch.
> No, it isn't my idea.  But it is awesome.)
> 
> And in case you ask: this is ruby-jekyll with a different name.  I had
> to drop all the building, because my server doesn't have ruby.
> 
> [kwpolska@*** testpkg]% makepkg-kw -d
> PACMAN
> ==> Making package: testpkg 0.11.2-1 (Sun May 20 13:11:07 CEST 2012)
> ==> WARNING: Skipping dependency checks.
> ==> Retrieving Sources...
>   -> Found jekyll-0.11.2.gem
>   -> Found LICENSE
> ==> Validating source files with md5sums...
> jekyll-0.11.2.gem ... Passed
> LICENSE ... Passed
> ==> Extracting Sources...
> ==> Removing existing pkg/ directory...
> ==> Entering fakeroot environment...
> PACMAN
> ==> Starting build()...
> BUILD, my server unfortunately doesn't have ruby
> ==> Tidying install...
>   -> Purging unwanted files...
>   -> Compressing man and info pages...
>   -> Stripping unneeded symbols from binaries and libraries...
> ==> Creating package...
>   -> Generating .PKGINFO file...
>   -> Compressing package...
> ==> Leaving fakeroot environment.
> ==> Finished making: testpkg 0.11.2-1 (Sun May 20 13:11:09 CEST 2012)
> [kwpolska@*** testpkg]%
> 
> If anyone from the makepkg team is reading, would you please mind:
> (a) making less use of pacman;

You are doing it wrong...   Remove the "run_pacman" function and you
will see when it is called.  Hint: never when using -d...

> (b) adding -v on lines 1292-1295 in order to inform us that the
> compressors are still working?

Huh...  Anyway, never by default, but you will be able to configure the
compression options with pacman-4.1.

Allan

Re: [arch-general] rubygems, the arch way and the aur

[Kwpolska]

On Sun, May 20, 2012 at 3:58 AM, martin kalcher
 wrote:
> Hmm.. i will figure out what makepkg actually needs to build the gem
> packages. Does it call pacman, when i call it with -d? This would a problem
> in my case.

-d DOES call pacman, but you can modify makepkg in order to (a) not do
so; (b) work under another distro (that won't be too hard, because:)

> # file -i does not work on Mac OSX unless legacy mode is set
> export COMMAND_MODE='legacy'
 -- makepkg; lines 37-38

And in terms of the "-d calls pacman" thing, here comes output from a
modded makepkg, with $PACMAN (variable holding pacman command)
replaced with 'echo PACMAN': every time.  Run under Arch, as I don't
have access to other distros. (yes, my shell server is running Arch.
No, it isn't my idea.  But it is awesome.)

And in case you ask: this is ruby-jekyll with a different name.  I had
to drop all the building, because my server doesn't have ruby.

[kwpolska@*** testpkg]% makepkg-kw -d
PACMAN
==> Making package: testpkg 0.11.2-1 (Sun May 20 13:11:07 CEST 2012)
==> WARNING: Skipping dependency checks.
==> Retrieving Sources...
  -> Found jekyll-0.11.2.gem
  -> Found LICENSE
==> Validating source files with md5sums...
jekyll-0.11.2.gem ... Passed
LICENSE ... Passed
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
PACMAN
==> Starting build()...
BUILD, my server unfortunately doesn't have ruby
==> Tidying install...
  -> Purging unwanted files...
  -> Compressing man and info pages...
  -> Stripping unneeded symbols from binaries and libraries...
==> Creating package...
  -> Generating .PKGINFO file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: testpkg 0.11.2-1 (Sun May 20 13:11:09 CEST 2012)
[kwpolska@*** testpkg]%

If anyone from the makepkg team is reading, would you please mind:
(a) making less use of pacman;
(b) adding -v on lines 1292-1295 in order to inform us that the
compressors are still working?

-- 
Kwpolska 
stop html mail      | always bottom-post
www.asciiribbon.org | www.netmeister.org/news/learn2quote.html
GPG KEY: 5EAAEA16   | Arch Linux x86_64, zsh, mutt, vim.
# vim:set textwidth=70:

Re: [arch-general] pm-suspend stuck at uhci_hcd

[Manne Merak]

On 05/17/2012 01:11 AM, Leonid Isaev wrote:

On Wed, 16 May 2012 23:50:06 +0200
Manne Merak  wrote:


Hi,
Couple of updates ago suspend to RAM stopped working.
Looking at the pm-suspend.log (below) file shows that it gets stuck at
unloading uhci_hcd?
I can unload and load the module by hand just fine.
Anyone else have this?

Hmm, 75modules should print something like "done" or "fail". What do you mean
by stopped working? What configuration do you have in /etc/pm/config.d/*?



Ok, some more debugging.
The first suspend-RAM works file.  Checked the pm-suspend.log and all 
gets unloaded just fine.
On second suspend, I get the mentioned stuck at unloading uhci_hcd 
(leaving it a while gives):


---
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
Unloading kernel module uhci_hcd.../usr/lib/pm-utils/functions: line 84: 
26341 Killed  modprobe -r "$1"

/usr/lib/pm-utils/functions: line 89: log: command not found
Failed.
Unloading kernel module ehci_hcd...


Now stuck at unloading ehci_hcd.

I get the same behaviour trying to unload uhci_hcd or ehci_hcd after the 
first successfull suspend and restore.


There's more; a "oops" in the system log:

[209624.386398] BUG: unable to handle kernel paging request at 6d0d
[209624.386404] IP: [] _raw_spin_lock_irqsave+0x2a/0x50
[209624.386412] *pde = 
[209624.386414] Oops: 0002 [#1] PREEMPT SMP
[209624.386418] Modules linked in: uhci_hcd(-) ehci_hcd usb_storage uas 
rfcomm btusb hidp bnep bluetooth fuse vboxnetadp(O) vboxnetflt(O) usbhid 
uvcvideo hid videobuf2_vmalloc videobuf2_memops videobuf2_core videodev 
media nvidia(PO) snd_hda_codec_idt snd_hda_intel firewire_ohci joydev 
b44 snd_hda_codec r852 sm_common nand snd_pcm nand_ecc nand_ids arc4 
iwl3945 iwlegacy ssb snd_page_alloc r592 mtd iTCO_wdt firewire_core 
crc_itu_t pcmcia mii pcmcia_core mac80211 sdhci_pci intel_agp sdhci 
intel_gtt mmc_core cfg80211 agpgart i2c_i801 i2c_core snd_hwdep 
snd_timer snd memstick iTCO_vendor_support serio_raw dell_wmi psmouse 
sparse_keymap soundcore wmi dell_laptop usbcore usb_common rfkill evdev 
thermal dcdbas button battery ac video vboxdrv(O) cpufreq_powersave 
acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache sr_mod sd_mod cdrom 
pata_acpi ata_generic ata_piix ahci libahci libata scsi_mod [last 
unloaded: ehci_hcd]

[209624.386476]
[209624.386479] Pid: 26341, comm: modprobe Tainted: P   O 
3.3.6-1-ARCH #1 Dell Inc. Vostro 1700 /0HX767

[209624.386483] EIP: 0060:[] EFLAGS: 00010002 CPU: 0
[209624.386486] EIP is at _raw_spin_lock_irqsave+0x2a/0x50
[209624.386488] EAX: 0100 EBX: 6d0d ECX: 6d0d EDX: e002dd10
[209624.386490] ESI: 0206 EDI: f24ca4b4 EBP: e002dcf0 ESP: e002dce8
[209624.386492]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[209624.386494] Process modprobe (pid: 26341, ti=e002c000 task=c5aeca80 
task.ti=e002c000)

[209624.386496] Stack:
[209624.386497]  6d0d 6d0d e002dd08 c0142d39 e002dd10 f24ca4a8 
 
[209624.386503]  e002dd20 c0142eca f8af756a f24ca400  ecdfbc94 
e002dd38 f8af7461
[209624.386508]  ecdfbc94 f24ca400 ecdfbcd8 ecdfbc94 e002dd58 f8af7694 
ecdfb808 ecdfb808

[209624.386513] Call Trace:
[209624.386519]  [] lock_timer_base.isra.33+0x29/0x50
[209624.386522]  [] del_timer+0x2a/0xe0
[209624.386529]  [] ? hci_conn_del+0x12a/0x1f0 [bluetooth]
[209624.386534]  [] hci_conn_del+0x21/0x1f0 [bluetooth]
[209624.386538]  [] hci_conn_hash_flush+0x64/0xb0 [bluetooth]
[209624.386543]  [] hci_dev_do_close+0x96/0x290 [bluetooth]
[209624.386548]  [] hci_unregister_dev+0x48/0x140 [bluetooth]
[209624.386551]  [] btusb_disconnect+0x4f/0xb0 [btusb]
[209624.386559]  [] usb_unbind_interface+0x3c/0x140 [usbcore]
[209624.386564]  [] __device_release_driver+0x5d/0xb0
[209624.386566]  [] device_release_driver+0x24/0x40
[209624.386569]  [] bus_remove_device+0xa5/0xd0
[209624.386572]  [] device_del+0xe5/0x150
[209624.386578]  [] usb_disable_device+0x89/0x1a0 [usbcore]
[209624.386584]  [] usb_disconnect+0x70/0xe0 [usbcore]
[209624.386590]  [] usb_disconnect+0x5f/0xe0 [usbcore]
[209624.386595]  [] usb_disconnect+0x5f/0xe0 [usbcore]
[209624.386602]  [] usb_remove_hcd+0x9c/0x120 [usbcore]
[209624.386608]  [] usb_hcd_pci_remove+0x48/0xb0 [usbcore]
[209624.386611]  [] pci_device_remove+0x2f/0xe0
[209624.386614]  [] __device_release_driver+0x5d/0xb0
[209624.386616]  [] driver_detach+0x8f/0xa0
[209624.386619]  [] bus_remove_driver+0x62/0xa0
[209624.386621]  [] driver_unregister+0x49/0x80
[209624.386624]  [] pci_unregister_driver+0x32/0x80
[209624.386627]  [] uhci_hcd_cleanup+0xd/0x35 [uhci_hcd]
[209624.386632]  [] sys_delete_module+0x11f/0x280
[209624.386635]  [] ? fput+0x130/0x1d0
[209624.386639]  [] ? filp_close+0x54/0x80
[209624.386642]  [] ? sys_close+0x72/0xc0
[209624.386645]  [] sysenter_do_call+0x12/0x28
[209624.386647] Code: 00 55 89 e5 56 53 3e 8d 74 26 00 89 c1 9c 58 8d 74 
26 00 89 c6 fa 90 8d 74 26 00 89 e0 25 00 e0 ff ff 83 40 14 01 b8 00 01 
00 00  6